From GSD Core
Archives a completed milestone, updates ROADMAP.md and REQUIREMENTS.md, and prepares for the next version. Useful for GSD workflow users closing a milestone.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gsd-core:gsd-complete-milestone <version><version>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
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>npx claudepluginhub open-gsd/gsd-coreManages project milestones: create new cycles with phases, complete/archive versions, preview changes, audit integration, analyze gaps. For structured delivery checkpoints.
Verifies milestone completion against original intent by reading phase VERIFICATION.md files, aggregating tech debt and gaps, and running cross-phase integration checks before archiving.
Wraps up a finished memex milestone slice by syncing `docs/CONTINUE_HERE.md` (current state, next slice), ticking off `docs/ROADMAP.md` scoreboard items, confirming observations are logged (deferring to memex-observe), and proposing a git tag/commit subject. Use before committing a slice or when handoff docs have drifted from shipped work.