gsd-audit-milestone

To verify milestone completion, audit the milestone against its original defined done criteria and acceptance intent. This validation process reads VERIFICATION.md files to confirm cross-phase alignment and prevent silent scope creep before project archiving.

Cross-phase validation is the process of aggregating VERIFICATION.md data across planning, execution, and verification phases. It identifies technical debt, surfaces deferred gaps, and triggers integration checks to ensure milestones satisfy original intent.

Track technical debt and deferred gaps by aggregating VERIFICATION.md files across project phases. The milestone audit workflow reads these files to surface risk flags, identify gaps, and produce a consolidated readiness report for remediation.

Yes, milestone audits apply directly to multi-phase projects with planning, execution, and verification stages. The workflow orchestrates end-to-end verification by triggering cross-phase integration checks to confirm alignment with original done criteria.

The best way to prevent silent scope creep is to validate that each milestone satisfies its defined done criteria before archiving. Running a milestone audit confirms alignment with original intent and surfaces risk flags for remediation.

Milestone verification fails to catch integration issues when it lacks cross-phase alignment checks. The audit workflow solves this by triggering integration checks across phases and aggregating VERIFICATION.md data to identify deferred gaps before archiving.