gsd-audit-milestone

Audit milestone completion by verifying requirements coverage, integration wiring, and end-to-end flows.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-audit-milestone-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-audit-milestone
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-audit-milestone-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from archiving a milestone that hasn’t fully met its definition of done, ensuring verification evidence and cross-phase wiring are actually complete.

Core Features & Use Cases

  • Requirements coverage validation: Aggregates existing verification artifacts to confirm the milestone’s intended checks are covered.
  • Cross-phase integration auditing: Confirms integration points and end-to-end flows are correctly wired across phases, not just locally tested.
  • Tech-debt and deferred gap accounting: Surfaces deferred gaps and accumulated tech debt from the verification sources to inform the final audit result.

Use case: Before archiving a release milestone, audit whether all required verification files exist, whether integration checks pass, and whether any deferred gaps remain unaddressed.

Quick Start

Run the gsd-audit-milestone skill with the target milestone version to perform an end-to-end audit of completion and integration readiness.

Frequently Asked Questions about gsd-audit-milestone

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

FAQPage Schema
How do I audit milestone completion before archiving a release?

Milestone audit validates release readiness by aggregating existing verification artifacts to confirm requirements coverage, cross-phase integration wiring, and end-to-end flow completion before archiving.

What is milestone audit and when do I need it for release readiness?

Milestone audit is a release readiness check needed when prior phases have produced verification artifacts that must be aggregated and validated. It confirms cross-phase wiring is complete and surfaces deferred gaps before archiving.

How do I verify cross-phase integration wiring and end-to-end flows?

Verify cross-phase integration wiring by running integration checks against existing VERIFICATION.md files to confirm end-to-end flows are correctly wired across phases, not just locally tested, ensuring full release readiness.

Does milestone audit require existing VERIFICATION.md files to work?

Yes, milestone audit requires reading existing VERIFICATION.md files produced by prior phases to aggregate verification artifacts, validate requirements coverage, and produce a final audit decision aligned with the milestone definition of done.

How does milestone audit handle tech debt and deferred gaps?

Milestone audit surfaces deferred gaps and accumulated tech debt from verification sources to inform the final audit result, preventing teams from archiving a milestone that hasn't fully met its definition of done.

Why should I use a milestone audit instead of just checking local tests?

A milestone audit checks that integration points and end-to-end flows are correctly wired across phases, not just locally tested. It preserves workflow gates and scope determination while aggregating verification evidence for a final audit decision.