Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From GSD Core
Audits milestone completion against original intent by reading phase verification files, checking requirements coverage and cross-phase integration, then spawning end-to-end flow checks.
How this command is triggered — by the user, by Claude, or both
Slash command
/gsd-core:audit-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> Verify milestone achieved its definition of done. Check requirements coverage, cross-phase integration, and end-to-end flows. **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. </objective> <execution_context> @~/.claude/gsd-core/workflows/audit-milestone.md </execution_context> <context> Version: $ARGUMENTS (optional — defaults to current milestone) Core planning files are resolved in-workflow (`init mileston...
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/gsd-core/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 end-to-end. Preserve all workflow gates (scope determination, verification reading, integration check, requirements coverage, routing).npx claudepluginhub sometiny/get-shit-done-redux5plugins reuse this command
First indexed Jun 7, 2026
/audit-milestoneAudits milestone completion against original intent by reading phase verification files, checking requirements coverage and cross-phase integration, then spawning end-to-end flow checks.
/audit-milestoneVerifies milestone meets definition of done through requirement coverage checks, integration verification, and stub detection.
/fire-4-verifyVerifies a completed phase by checking must-haves and running a 70-point quality validation checklist, then generates a detailed report and optionally routes to gap closure.
/phase-reviewRuns post-execution quality gate that verifies all deliverables, checks alignment with plan, and generates a Phase Completion Report with PASS/FAIL verdict before marking a track complete.
/flow-gate-checkOrchestrates multi-agent validation for SDLC phase gates like inception, security, or pre-deploy in a project directory, generating comprehensive readiness reports with optional guidance and interactive Q&A.
/verifyVerifies project tests, acceptance criteria from files, or roadmap phases. Dispatches verifier agent to execute checks and report PASS/FAIL with evidence.