Overview
Verify that a milestone achieved its definition of done by checking requirements coverage, cross-phase integration, and end-to-end flows. This command orchestrates the audit process by reading existing VERIFICATION.md files from completed phases, aggregating technical debt and deferred gaps, then spawning an integration checker for cross-phase wiring.Syntax
The milestone version to audit (e.g., “1.0”, “1.1”). Defaults to the current milestone if not provided.
Process
The command executes the audit-milestone workflow which:- Scope Determination - Identifies the milestone version to audit
- Verification Reading - Reads all phase VERIFICATION.md files from completed phases
- Integration Check - Spawns integration checker to validate cross-phase wiring
- Requirements Coverage - Validates all requirements from REQUIREMENTS.md are addressed
- Gap Identification - Aggregates technical debt and deferred work
- Routing - Creates audit report and recommends next steps
Input Files
The command reads:.planning/phases/*/*-SUMMARY.md- Completed phase summaries.planning/phases/*/*-VERIFICATION.md- Phase verification results- Core planning files loaded as needed via workflow initialization
Output
Creates.planning/v{version}-MILESTONE-AUDIT.md with:
- Requirements coverage analysis
- Cross-phase integration verification
- Technical debt summary
- Identified gaps
- Audit status (passed/gaps_found)
Examples
Audit Current Milestone
Audit Specific Version
Next Steps
After auditing:- If audit passed: Run
/gsd:complete-milestoneto archive the milestone - If gaps found: Run
/gsd:plan-milestone-gapsto create phases that close the gaps - Alternatively: Accept gaps as technical debt and proceed with completion
Allowed Tools
- Read
- Glob
- Grep
- Bash
- Task
- Write