Help us improve
Share bugs, ideas, or general feedback.
From GSD Core
Archives a completed milestone by creating historical records, updating ROADMAP.md and REQUIREMENTS.md, and tagging the release in git.
npx claudepluginhub open-gsd/gsd-coreHow this command is triggered — by the user, by Claude, or both
Slash command
/gsd-core:complete-milestone <version>gsd/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
<objective>
Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md and REQUIREMENTS.md.
Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone.
Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged.
</objective>
<execution_context>
**Load these files NOW (before proceeding):**
- @~/.claude/gsd-core/workflows/complete-milestone.md (main workflow)
- @~/.claude/gsd-core/templates/milestone-archive.md (archive template)
</execution_context>
<context.../fire-complete-milestoneArchives specified milestone v<version> to .planning/milestones/ as historical VISION.md and REQUIREMENTS.md copies, creates git tag, and prepares for next after WARRIOR validation check.
/complete-milestoneArchives a completed milestone, tags the release using Git, and prepares the repository for the next version via workflow execution with user gates.
Share bugs, ideas, or general feedback.
Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone. Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged.
<execution_context> Load these files NOW (before proceeding):
User input:
Follow complete-milestone.md workflow:
Check for audit:
.planning/v{{version}}-MILESTONE-AUDIT.md/gsd:audit-milestone firstgaps_found: recommend closing the gaps inline
(the audit output already enumerates them — insert closure phases
via /gsd:phase --insert <N> plus the standard
discuss/plan/execute chain) before proceeding.passed: proceed to step 1## Pre-flight Check
{If no v{{version}}-MILESTONE-AUDIT.md:}
⚠ No milestone audit found. Run `/gsd:audit-milestone` first to verify
requirements coverage, cross-phase integration, and E2E flows.
{If audit has gaps:}
⚠ Milestone audit found gaps. The audit output already enumerates the
unsatisfied requirements, cross-phase issues, and broken flows — insert
a closure phase per gap with `/gsd:phase --insert <N>` and run the
standard `/gsd:discuss-phase` → `/gsd:plan-phase` → `/gsd:execute-phase`
chain. Or proceed anyway to accept the gaps as tech debt.
{If audit passed:}
✓ Milestone audit passed. Proceeding with completion.
Verify readiness:
Gather stats:
Extract accomplishments:
Archive milestone:
.planning/milestones/v{{version}}-ROADMAP.mdArchive requirements:
.planning/milestones/v{{version}}-REQUIREMENTS.md.planning/REQUIREMENTS.md (fresh one created for next milestone)Update PROJECT.md:
<details> (if v1.1+)Commit and tag:
chore: archive v{{version}} milestonegit tag -a v{{version}} -m "[milestone summary]"Offer next steps:
/gsd:new-milestone — start next milestone (questioning → research → requirements → roadmap)<success_criteria>
.planning/milestones/v{{version}}-ROADMAP.md.planning/milestones/v{{version}}-REQUIREMENTS.md.planning/REQUIREMENTS.md deleted (fresh for next milestone)git.create_tag enabled)<critical_rules>
/gsd:new-milestone which includes requirements definition
</critical_rules>