From gsd
Verifies milestone completion against original intent by checking requirements coverage, cross-phase integration, and end-to-end flows before archiving.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gsd:audit-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>
This command IS the orchestrator. Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring.
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/audit-milestone.md </execution_context>
Version: $ARGUMENTS (optional — defaults to current milestone)Core planning files are resolved in-workflow (init milestone-op) and loaded only as needed.
Completed Work: Glob: .planning/phases//-SUMMARY.md Glob: .planning/phases//-VERIFICATION.md
Execute the audit-milestone workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/audit-milestone.md end-to-end. Preserve all workflow gates (scope determination, verification reading, integration check, requirements coverage, routing).npx claudepluginhub jnuyens/gsd-pluginVerifies milestone completion against original intent by reading phase summaries and VERIFICATION.md files, aggregating tech debt, and running integration checks for cross-phase wiring.
Manages project milestones: create new cycles with phases, complete/archive versions, preview changes, audit integration, analyze gaps. For structured delivery checkpoints.
Reviews a completed phase against STANDARDS.md Definition of Done by rerunning project commands and either approving (flips to done) or filing a bug.