qsd-audit-milestone

To audit a milestone before archiving, you verify its completion against original intent and archiving criteria by reading VERIFICATION.md files from completed phases, aggregating coverage, identifying gaps, and running cross-phase integration checks to ensure the definition of done is met.

The best way to identify gaps and tech debt during milestone verification is to read VERIFICATION.md files produced in completed phases to assess coverage and surface outstanding technical debt before archiving.

Cross-phase integration checking works by spawning an integration-check step that validates wiring and alignment with planning across completed phases, loading phase artifacts and resolving scope via in-workflow definitions during the milestone audit.

To start the milestone verification workflow, run the audit-milestone workflow from the central audit mechanism located at $HOME/.claude/qsd/workflows/audit-milestone.md to begin orchestrating end-to-end verification.

You need to run an end-to-end milestone audit before archiving when you must reduce drift and post-facto rework by ensuring each milestone strictly meets its definition of done against original intent and archiving criteria.