gsd-audit-milestone

To verify milestone completion before archiving, audit the work against its original intent to ensure full requirements coverage, identify gaps, and confirm end-to-end flows are complete across all phases.

Aggregating tech debt during a milestone audit involves consolidating deferred gaps and outstanding issues from VERIFICATION.md files across all project phases to provide traceable evidence for archiving decisions.

A cross-phase integration checker validates end-to-end flows across all project phases. You need it during milestone audits to spawn verification workflows that ensure no integration gaps remain before archiving.

Yes, you can use VERIFICATION.md files to check requirements coverage. The audit workflow reads these files to aggregate verification status and ensure original project milestones are fully covered across all phases.

The best way to audit project milestones for gaps and deferred tech debt is to run an orchestrated workflow that reads verification files, triggers cross-phase integration checks, and consolidates all outstanding issues before archiving.