Archive completed milestone and prepare for next version
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./pi/package-skills/gsd-complete-milestone/SKILL.mdInvoke this Pi skill with /skill:gsd-complete-milestone.
Pi dispatch (fail closed). Pi has no built-in subagent API; GSD provides the gsd_dispatch tool. Where a workflow step dispatches a named gsd-* role, call gsd_dispatch with role (the installed role name) and task (the full task text). A workflow that still writes the step as an Agent(...) call means the same: its subagent_type is the role and its prompt is the task. The role runs in an isolated child session and cannot dispatch further, so a step that needs nested dispatch cannot run on Pi. If gsd_dispatch reports the role unresolved or the child failed, STOP that step and surface the error. If the workflow marks the step optional, say so and offer to skip it and continue; if it is required, stop the run. Never execute the role's work inline as a substitute.
Pi includes. Pi does not expand @path references in a skill. Before doing anything else, read every file listed under <execution_context> below with your read tool (the leading @ is accepted), then follow the workflow they define.
(the text typed after the skill name)
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
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/skill:gsd-audit-milestone firstgaps_found: recommend closing the gaps inline
(the audit output already enumerates them — insert closure phases
via /skill: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 `/skill: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 `/skill:gsd-phase --insert <N>` and run the
standard `/skill:gsd-discuss-phase` → `/skill:gsd-plan-phase` → `/skill: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:
/skill: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>
/skill:gsd-new-milestone which includes requirements definition
</critical_rules>open-gsd/gsd-core
99bbbac
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.