gsd-audit-milestone

Verify milestone completion by running an audit workflow that reads VERIFICATION.md files from completed phases to check scope and done criteria. This process aggregates tech debt and deferred gaps to ensure alignment with original intent before archiving.

Surface technical debt and deferred gaps by running a cross-phase milestone audit that reads VERIFICATION.md artifacts from completed phases. The audit aggregates these deferred items and prepares the input needed to validate end-to-end integration readiness.

Cross-phase integration validation works by reading verification artifacts from completed phases and spawning an integration checker. This checker validates end-to-end wiring across planning, execution, and verification phases to ensure project quality before archiving.

Yes, you can use VERIFICATION.md files to check end-to-end readiness. The audit process reads these verification artifacts from completed phases, aggregates any tech debt, and triggers an integration checker to validate cross-phase wiring.

Yes, you need completed VERIFICATION.md files from your finished project phases. The milestone audit relies on reading these verification artifacts to evaluate scope, aggregate deferred gaps, and confirm the definition of done before archiving.