gsd-audit-milestone

To verify project milestone compliance, you can audit the milestone against its definition of done, which checks requirements coverage and validates end-to-end flow integrity before archiving.

Checking requirements coverage involves running an audit on the specific milestone version, ensuring all requirements are met and cross-phase integration aligns with the initial project intent.

Cross-phase integration check works by operating on existing verification files and tech debt logs to validate end-to-end flows, ensuring all project phases are correctly implemented together.

Yes, you need Bash and Agent tools to perform a milestone audit, as these dependencies are required to execute the verification scripts and analyze the project's integration integrity.

You should run a milestone verification audit right before archiving a project milestone, ensuring that the deliverables meet the definition of done and that cross-phase integration is complete.

Auditing milestone compliance depends entirely on the accuracy of existing verification files and tech debt logs; if these inputs are incomplete, the integration check may not reflect actual project state.