gsd-audit-milestone

To audit milestone completion before archiving, you validate artifacts like VERIFICATION.md files and orchestrate checks against defined criteria. This verifies that planning, verification, and integration phases meet original project intent.

Aggregating tech debt and deferred gaps involves reading existing VERIFICATION.md and SUMMARY files across phases. This collects phase verification results to provide a comprehensive view of outstanding issues before archiving.

Verifying cross-phase wiring and requirements coverage during an audit is done by spawning an integration checker. This orchestrated check ensures that all phases are properly connected and that requirements are fully satisfied.

Yes, the milestone audit workflow operates without external dependencies. It reads existing VERIFICATION.md files, aggregates gaps, and spawns integration checks natively to validate artifacts against defined criteria.

You need to run an end-to-end milestone audit when preparing to archive a completed phase. It validates artifact presence and completeness across planning, verification, and integration to ensure accuracy against original intent.