gsd-audit-milestone

You can verify milestone completion by running a cross-phase audit that checks alignment between original intent and predefined milestones. This process reviews verification artifacts to ensure all objectives are met before project archival.

Cross-phase verification is an audit mechanism that validates milestone completion across different project stages. It aggregates tech debt and gaps by cross-checking verification artifacts against initial objectives to ensure readiness for archiving.

You aggregate tech debt and gaps by orchestrating an integration checker during the milestone audit. This workflow compares your summary artifacts against predefined milestones to surface any outstanding issues requiring remediation.

Yes, a VERIFICATION.md file is required for the milestone audit. The audit workflow applies to project environments where VERIFICATION.md and summary artifacts must align with predefined milestones across phases before archiving.

Yes, you can use this workflow to cross-check your summary artifacts against predefined milestones. It enforces cross-phase verification to ensure your artifacts align with the original intent before proceeding to archival.

You should avoid using an automated audit workflow for archiving if your project lacks predefined milestones or VERIFICATION.md artifacts. The process requires structured verification documentation to properly aggregate gaps and run cross-phase integration checks.