gsd-audit-milestone

Audit milestone completion against definition of done using verification artifacts and integration checks.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-audit-milestone-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-audit-milestone
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-audit-milestone-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents prematurely archiving milestones by verifying that the delivered work matches the original “definition of done,” including requirements coverage, cross-phase integration, and end-to-end flows.

Core Features & Use Cases

  • Milestone definition-of-done audit: Confirms completion by aggregating verification evidence from prior phase checks.
  • Requirements coverage review: Detects gaps where requirements may not be fully satisfied or referenced by the verified outputs.
  • Cross-phase integration verification: Validates wiring between phases by running an integration checker after reading VERIFICATION.md artifacts.
  • End-to-end execution gating: Re-runs the orchestrated audit process to ensure the system behaves correctly as a whole.

Quick Start

Run the gsd-audit-milestone skill for the desired milestone version to generate an end-to-end audit that verifies completion readiness for archiving.

Frequently Asked Questions about gsd-audit-milestone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify milestone completion against the definition of done before archiving?

Milestone definition-of-done verification aggregates prior phase verification artifacts and runs cross-phase integration checks to confirm requirements coverage. This prevents prematurely archiving milestones by validating that delivered work matches original criteria.

What is the best way to audit requirements coverage across multi-phase delivery workflows?

Requirements coverage review detects gaps where requirements are not fully satisfied by verified outputs. The audit aggregates verification evidence from prior phase checks to validate milestone readiness and identify deferred gaps across multi-phase delivery workflows.

How do I validate cross-phase integration wiring for end-to-end workflow orchestration?

Cross-phase integration verification validates wiring between phases by running an integration checker after reading VERIFICATION.md artifacts. This end-to-end execution gating ensures the system behaves correctly as a whole before milestone archiving.

Can I aggregate tech debt and deferred gaps when auditing milestone readiness?

Yes, milestone readiness validation aggregates tech debt and deferred gaps by reading .planning/phases/*/*-VERIFICATION.md summaries. This preserves workflow gates while confirming completion against the original definition of done.

Do I need VERIFICATION.md summaries to run a milestone audit?

Yes, the milestone audit requires reading .planning/phases/*/*-VERIFICATION.md summaries to aggregate verification evidence. These artifacts provide the prior phase checks needed to validate end-to-end flow and requirements coverage.