gsd-audit-milestone

Milestone verification reviews completed phase evidence and checks whether requirements were actually satisfied before archive approval. It aggregates phase verification and confirms end-to-end coverage across planning artifacts to ensure the original definition of done is met.

Cross-phase integration audits look for wiring gaps between phases, unresolved dependencies, and end-to-end breakpoints. This process routes an integration checker to inspect cross-phase integration and preserve workflow gates for scope and requirements coverage before milestone closure.

Requirements coverage inspection confirms end-to-end coverage across planning artifacts by reading existing verification summaries. It preserves workflow gates to ensure scope and deferred gaps are fully accounted for before granting archive approval.

Yes, milestone audits collect deferred issues, tech debt, and unfinished follow-ups into a single audit outcome. This debt and gap aggregation ensures all unresolved dependencies and deferred gaps are preserved within workflow gates before the milestone is archived.

Milestone verification requires reading existing verification summaries and routing an integration checker. The process needs completed phase evidence and planning artifacts to inspect cross-phase integration and confirm end-to-end coverage against the original definition of done.

Milestone verification fails when cross-phase integration audits reveal wiring gaps, unresolved dependencies, or insufficient requirements coverage. The audit catches deferred gaps and unfinished follow-ups that violate the original definition of done, preventing premature archival.