gsd-audit-milestone

Verifying milestone completion before archiving requires checking requirements coverage, cross-phase integration, and end-to-end flows. This Skill automates that verification by aggregating tech debt and deferred gaps to confirm milestones have achieved their definition of done.

An automated audit workflow for project milestone verification checks original intent against actual completion. It uses existing verification files to validate requirement coverage and spawns an integration checker to evaluate end-to-end flows before archiving.

Checking requirement coverage and cross-phase integration for a release involves validating original requirements against implementation. This Skill aggregates existing verification files and tech debt records to ensure all definition of done criteria are met.

Yes, you can run a milestone audit using only the version number as input. Executing the command with a version argument like v1.2 triggers the verification process, which relies on existing verification files to assess completion status.

The integration checker uses existing verification files to validate milestone completion. It aggregates tech debt and deferred gaps from these files before executing cross-phase wiring checks, ensuring no new manual verification data is required.

The best way to aggregate tech debt and deferred gaps before archiving is through an automated milestone audit. This process validates requirement coverage and end-to-end flows, ensuring all deferred gaps are documented before the project is archived.