gsd-audit-milestone

Audit milestone completion against defined done criteria using phase verification artifacts.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-audit-milestone-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-audit-milestone
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-audit-milestone-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature milestone archiving by ensuring the work truly meets its defined completion criteria across planning, verification, and end-to-end integration.

Core Features & Use Cases

  • Milestone completion verification: Aggregates phase verification artifacts (e.g., phase summaries and verification files) to confirm requirements coverage.
  • Cross-phase integration checking: Validates that wiring and flows work across phases, not just within isolated sections.
  • Gap and tech-debt surfacing: Collects deferred gaps and tech debt so they’re visible before the milestone is considered complete.

Use case: Before archiving a delivery milestone, verify that all planned phases have completed verification and that the combined flows work end-to-end with no missing requirements.

Quick Start

Run the milestone audit workflow to verify the current version’s completion and integration 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 a delivery workflow?

Milestone completion verification aggregates existing phase verification artifacts and checks requirements coverage to confirm the delivery meets its defined done criteria before archiving.

What is cross-phase integration checking for milestone audits?

Cross-phase integration checking validates that wiring and flows work across multiple phases end-to-end, ensuring combined workflow integration works correctly rather than just within isolated sections.

How do I surface deferred gaps and tech debt before milestone archival?

Gap and tech-debt surfacing collects deferred gaps and technical debt during the milestone audit, making them visible so they are tracked before the milestone is considered complete.

Can I audit requirements coverage across multiple workflow phases?

Yes, the audit reads existing phase verification files and aggregates requirements coverage across all planned phases to validate that no missing requirements exist before archiving.

What's the best way to prevent premature milestone archiving in workflow-driven delivery?

Prevent premature archiving by running a milestone audit that orchestrates verification reading, integration checking, and requirements coverage validation to preserve workflow gates across the selected milestone version.

Do I need existing phase verification artifacts to run a milestone audit?

Yes, the audit requires existing phase verification artifacts such as phase summaries and verification files to read and aggregate, as it validates completion against already generated phase outputs.