
new-milestone
by XcluEzy7
AG4ONE - Unified agentic engineering workflow combining GWD methodology, Serena semantic analysis, and Ralph autonomous looping for next-generation AI pair programming across multiple platforms
SKILL.md
name: new-milestone description: Start a new milestone cycle — update PROJECT.md and route to requirements argument-hint: "[milestone name, e.g., 'v1.1 Notifications']" allowed-tools:
- Read
- Write
- Bash
- AskUserQuestion
This is the brownfield equivalent of new-project. The project exists, PROJECT.md has history. This command gathers "what's next" and updates PROJECT.md to reflect the new milestone's goals.
Output: Updated PROJECT.md, routes to research-project or define-requirements
<execution_context>
@/.claude/ag4one/references/questioning.md
@/.claude/ag4one/templates/project.md
</execution_context>
Load project context: @.planning/PROJECT.md @.planning/STATE.md @.planning/MILESTONES.md @.planning/config.json
-
Load context:
- Read PROJECT.md (existing project, Validated requirements, decisions)
- Read MILESTONES.md (what shipped previously)
- Read STATE.md (pending todos, blockers)
- Check for MILESTONE-CONTEXT.md (from /ag4:discuss-milestone)
-
Gather milestone goals:
If MILESTONE-CONTEXT.md exists:
- Use features and scope from discuss-milestone
- Present summary for confirmation
If no context file:
- Present what shipped in last milestone
- Ask: "What do you want to build next?"
- Use AskUserQuestion to explore features
- Probe for priorities, constraints, scope
-
Determine milestone version:
- Parse last version from MILESTONES.md
- Suggest next version (v1.0 → v1.1, or v2.0 for major)
- Confirm with user
-
Update PROJECT.md:
Add/update these sections:
## Current Milestone: v[X.Y] [Name] **Goal:** [One sentence describing milestone focus] **Target features:** - [Feature 1] - [Feature 2] - [Feature 3]Update Active requirements section with new goals.
Update "Last updated" footer.
-
Update STATE.md:
## Current Position Phase: Not started (run /ag4:create-roadmap) Plan: — Status: Defining requirements Last activity: [today] — Milestone v[X.Y] started -
Cleanup:
- Delete MILESTONE-CONTEXT.md if exists (consumed)
-
Git commit:
git add .planning/PROJECT.md .planning/STATE.md git commit -m "docs: start milestone v[X.Y] [Name]" -
Route to next step:
Milestone v[X.Y] [Name] initialized. PROJECT.md updated with new goals. --- ## ▶ Next Up Choose your path: **Option A: Research first** (new domains/capabilities) Research ecosystem before scoping. Discovers patterns, expected features, architecture approaches. `/ag4:research-project` **Option B: Define requirements directly** (familiar territory) Skip research, define requirements from what you know. `/ag4:define-requirements` <sub>`/clear` first → fresh context window</sub> ---
<success_criteria>
- PROJECT.md updated with Current Milestone section
- Active requirements reflect new milestone goals
- STATE.md reset for new milestone
- MILESTONE-CONTEXT.md consumed and deleted (if existed)
- Git commit made
- User routed to define-requirements (or research-project) </success_criteria>
Score
Total Score
Based on repository quality metrics
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
Reviews
Reviews coming soon