Verified:GitHub

gsd-audit-milestone

Verify milestone completion against the original definition of done.

264|11|Updated Apr 25, 2026

Search Tags:#verification #workflow orchestration #tech debt #requirements coverage #milestone audit #integration checks

Ready to run

npx skills add https://github.com/coco-research/coco --skill gsd-audit-milestone-coco-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-audit-milestone
Command: npx skills add https://github.com/coco-research/coco --skill gsd-audit-milestone-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps confirm that a milestone truly meets its original definition of done before it is closed or archived, reducing the risk of shipping incomplete work.

Core Features & Use Cases

Milestone Verification: Reviews completed phase evidence and checks whether requirements were actually satisfied.
Cross-Phase Integration Review: Looks for wiring gaps between phases, unresolved dependencies, and end-to-end breakpoints.
Debt and Gap Aggregation: Collects deferred issues, tech debt, and unfinished follow-ups into a single audit outcome.
Use Case: A project lead can use this Skill to validate that all planned phases are covered, integration is sound, and the milestone is ready for archive.

Quick Start

Ask the assistant to audit the current milestone and report whether it fully satisfies the original requirements.

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 original definition of done?▼

Milestone verification reviews completed phase evidence and checks whether requirements were actually satisfied before archive approval. It aggregates phase verification and confirms end-to-end coverage across planning artifacts to ensure the original definition of done is met.

What is the best way to audit cross-phase integration before archiving a milestone?▼

Cross-phase integration audits look for wiring gaps between phases, unresolved dependencies, and end-to-end breakpoints. This process routes an integration checker to inspect cross-phase integration and preserve workflow gates for scope and requirements coverage before milestone closure.

How does requirements coverage inspection work during a milestone audit?▼

Requirements coverage inspection confirms end-to-end coverage across planning artifacts by reading existing verification summaries. It preserves workflow gates to ensure scope and deferred gaps are fully accounted for before granting archive approval.

Can I aggregate deferred issues and tech debt into a single milestone audit outcome?▼

Yes, milestone audits collect deferred issues, tech debt, and unfinished follow-ups into a single audit outcome. This debt and gap aggregation ensures all unresolved dependencies and deferred gaps are preserved within workflow gates before the milestone is archived.

What do I need to run an integration checker for milestone verification?▼

Milestone verification requires reading existing verification summaries and routing an integration checker. The process needs completed phase evidence and planning artifacts to inspect cross-phase integration and confirm end-to-end coverage against the original definition of done.

Why does milestone verification fail before archive approval?▼

Milestone verification fails when cross-phase integration audits reveal wiring gaps, unresolved dependencies, or insufficient requirements coverage. The audit catches deferred gaps and unfinished follow-ups that violate the original definition of done, preventing premature archival.