gsd-audit-milestone

Audit milestone completion against definition of done and cross-phase integration.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-audit-milestone-tinner-deinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-audit-milestone
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-audit-milestone-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature archiving by verifying that a milestone fully matches its original intent and completion criteria.

Core Features & Use Cases

  • Requirements-to-Completion Audit: Checks whether the milestone’s definition of done is actually satisfied, not just partially implemented.
  • Cross-Phase Integration Verification: Ensures execute-phase verification outputs are correctly wired into end-to-end flows and routing.
  • Tech Debt & Deferred Gap Aggregation: Collects deferred gaps and technical debt signals from existing verification artifacts before declaring completion.

Use Case: Before archiving an engineering milestone, run this Skill to ensure all planned phases have matching verification coverage and the integrated workflow still routes correctly.

Quick Start

Run gsd-audit-milestone for the current milestone version to audit verification coverage, cross-phase wiring, and end-to-end readiness before 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 before archiving engineering workflows?▼

Milestone verification requires auditing planned requirements against the original definition of done and validating end-to-end flow integrity. You aggregate per-phase verification artifacts to confirm cross-phase integration and enforce routing gates before archiving.

What is cross-phase integration verification for execute-phase workflows?▼

Cross-phase integration verification ensures execute-phase verification outputs are correctly wired into end-to-end flows and routing. It aggregates per-phase artifacts to confirm the integrated workflow maintains functional integrity across all planned milestone phases.

How do I aggregate technical debt and deferred gaps before declaring milestone done?▼

Aggregating technical debt involves reading existing milestone verification files and collecting deferred gap signals from per-phase artifacts. This ensures all technical debt is documented and routing gates are enforced before declaring the milestone complete.

Does milestone audit work without existing per-phase verification artifacts?▼

Milestone audit requires existing per-phase verification artifacts to function correctly. The process depends on reading milestone verification files to aggregate technical debt and enforce requirements coverage, so missing artifacts prevent proper cross-phase integration checks.

What's the best way to prevent premature archiving of engineering milestones?▼

Preventing premature archiving requires auditing milestone completion against the original definition of done by verifying planned requirements and end-to-end flow integrity. This approach catches partially implemented phases and unresolved technical debt before archiving occurs.