Files
msd-core/commands/gsd/new-milestone.md
Lex Christopherson 2d3a1eadda refactor(milestone): rework milestone cycle for proper requirements flow
- complete-milestone: archive + delete ROADMAP.md and REQUIREMENTS.md
- new-milestone: brownfield new-project (updates PROJECT.md, routes to requirements)
- discuss-milestone: now required before new-milestone (creates context file)
- research-project: milestone-aware (focuses on new features, not validated ones)
- create-roadmap: continues phase numbering from previous milestone

Flow: complete → discuss → new-milestone → research → requirements → roadmap

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-15 12:57:33 -06:00

3.4 KiB

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
gsd:new-milestone Start a new milestone cycle — update PROJECT.md and route to requirements [milestone name, e.g., 'v1.1 Notifications']
Read
Write
Bash
AskUserQuestion
Start a new milestone by updating PROJECT.md with new goals, then routing to the requirements → roadmap cycle.

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/get-shit-done/references/questioning.md @/.claude/get-shit-done/templates/project.md </execution_context>

Milestone name: $ARGUMENTS (optional - will prompt if not provided)

Load project context: @.planning/PROJECT.md @.planning/STATE.md @.planning/MILESTONES.md @.planning/config.json

  1. 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 /gsd:discuss-milestone)
  2. 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
  3. Determine milestone version:

    • Parse last version from MILESTONES.md
    • Suggest next version (v1.0 → v1.1, or v2.0 for major)
    • Confirm with user
  4. 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.

  5. Update STATE.md:

    ## Current Position
    
    Phase: Not started (run /gsd:create-roadmap)
    Plan: —
    Status: Defining requirements
    Last activity: [today] — Milestone v[X.Y] started
    
  6. Cleanup:

    • Delete MILESTONE-CONTEXT.md if exists (consumed)
  7. Git commit:

    git add .planning/PROJECT.md .planning/STATE.md
    git commit -m "docs: start milestone v[X.Y] [Name]"
    
  8. Route to next step:

    Milestone v[X.Y] [Name] initialized.
    
    PROJECT.md updated with new goals.
    
    ---
    
    ## ▶ Next Up
    
    **Define Requirements** — scope v[X.Y] features
    
    `/gsd:define-requirements`
    
    <sub>`/clear` first → fresh context window</sub>
    
    ---
    
    **Or research first:**
    - `/gsd:research-project` — investigate ecosystem before scoping
    
    **Full flow:**
    1. `/gsd:define-requirements` — create REQUIREMENTS.md
    2. `/gsd:create-roadmap` — create ROADMAP.md with phases
    3. `/gsd:plan-phase [N]` — start execution
    
    ---
    

<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>