gsd-audit-milestone

Check milestone completion by reviewing phase artifacts against the original definition of done, verifying requirements coverage, and validating cross-phase integration before archiving.

A milestone audit aggregates phase summaries to verify requirements coverage and validate cross-phase integration. Run it before archiving to confirm end-to-end workflow readiness and avoid shipping incomplete work.

Detect deferred gaps by reading prior verification artifacts and checking for missing verification outputs. This identifies deferred debt and end-to-end issues that could block confident closure before archiving.

Yes, milestone auditing requires reading prior verification artifacts to check deferred gaps, confirm requirements coverage, and validate cross-phase wiring across the whole workflow before archiving.

The best way to validate cross-phase integration is to run a milestone audit that checks requirements coverage, wiring, and integration behavior across the entire workflow against the original intent.

Milestone archiving fails because hidden gaps, deferred debt, and missing verification block confident closure. A milestone audit identifies these end-to-end issues by reviewing completed phase artifacts against the definition of done.