eliott/get-shit-done
1
0
Fork 0
mirror of https://github.com/glittercowboy/get-shit-done synced 2026-04-25 17:25:23 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
1fe3fa427ebc917123f8df1ce0d13ed17889f054
get-shit-done/commands/gsd/complete-milestone.md
Lex Christopherson 1fe3fa427e Initial commit: Get Shit Done - meta-prompting system for Claude Code 
- NPX install: npx get-shit-done-cc
- Slash commands for project management
- Context engineering templates and workflows

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-15 07:44:41 -06:00

2.9 KiB
Raw Blame History

type, description, argument-hint, allowed-tools
type description argument-hint allowed-tools
prompt Archive completed milestone and prepare for next version <version>
Read
Write
Bash
Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md.

Purpose: Create historical record of shipped version, collapse completed work in roadmap, and prepare for next milestone. Output: Milestone archived, roadmap reorganized, git tagged.

<execution_context> Load these files NOW (before proceeding):

  • @~/.claude/get-shit-done/workflows/complete-milestone.md (main workflow)
  • @~/.claude/get-shit-done/templates/milestone-archive.md (archive template) </execution_context>
**Project files:** - `.planning/ROADMAP.md` - `.planning/STATE.md` - `.planning/PROJECT.md`

User input:

  • Version: {{version}} (e.g., "1.0", "1.1", "2.0")

Follow complete-milestone.md workflow:

  1. Verify readiness:

    • Check all phases in milestone have completed plans (SUMMARY.md exists)
    • Present milestone scope and stats
    • Wait for confirmation

  2. Gather stats:

    • Count phases, plans, tasks
    • Calculate git range, file changes, LOC
    • Extract timeline from git log
    • Present summary, confirm

  3. Extract accomplishments:

    • Read all phase SUMMARY.md files in milestone range
    • Extract 4-6 key accomplishments
    • Present for approval

  4. Archive milestone:

    • Create .planning/milestones/v{{version}}-ROADMAP.md
    • Extract full phase details from ROADMAP.md
    • Fill milestone-archive.md template
    • Update ROADMAP.md to one-line summary with link
    • Offer to create next milestone

  5. Update PROJECT.md:

    • Add "Current State" section with shipped version
    • Add "Next Milestone Goals" section
    • Archive previous content in <details> (if v1.1+)

  6. Commit and tag:

    • Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive file
    • Commit: chore: archive v{{version}} milestone
    • Tag: git tag -a v{{version}} -m "[milestone summary]"
    • Ask about pushing tag

  7. Offer next steps:

    • Plan next milestone
    • Archive planning
    • Done for now

<success_criteria>

  • Milestone archived to .planning/milestones/v{{version}}-ROADMAP.md
  • ROADMAP.md collapsed to one-line entry
  • PROJECT.md updated with current state
  • Git tag v{{version}} created
  • Commit successful
  • User knows next steps </success_criteria>

<critical_rules>

  • Load workflow first: Read complete-milestone.md before executing
  • Verify completion: All phases must have SUMMARY.md files
  • User confirmation: Wait for approval at verification gates
  • Archive before collapsing: Always create archive file before updating ROADMAP.md
  • One-line summary: Collapsed milestone in ROADMAP.md should be single line with link
  • Context efficiency: Archive keeps ROADMAP.md constant size </critical_rules>
Reference in New Issue View Git Blame Copy Permalink