gsd-audit-milestone

Audit milestone completion against acceptance criteria using planning and verification files.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-audit-milestone-dobrinz123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-audit-milestone
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-audit-milestone-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure a milestone truly meets its original intent and definition of done before it is archived by systematically verifying requirement coverage, cross-phase integration, and end-to-end flows. The Skill aggregates verification artifacts, surfaces deferred gaps and technical debt, and preserves workflow gates so no verification step is skipped.

Core Features & Use Cases

  • Orchestrated Verification: Reads phase SUMMARY and VERIFICATION files to confirm each completed phase met its acceptance criteria.
  • Cross-Phase Integration Checks: Spawns integration checkers to validate wiring between phases and end-to-end flows.
  • Gap & Tech‑Debt Aggregation: Collects unresolved issues, routes remediation tasks, and preserves audit context for archival decisions. Use case: run this Skill before archiving a milestone to generate a consolidated verification report that highlights missing requirements, integration failures, and outstanding technical debt.

Quick Start

Run the gsd-audit-milestone skill (optionally specifying a version) to audit the current milestone and produce an integration, coverage, and tech-debt report.

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 acceptance criteria before archiving?

Milestone completion verification requires scanning phase SUMMARY.md and VERIFICATION.md files to check requirements coverage, cross-phase integration, and end-to-end flows before archiving. The audit reads planning files to confirm each phase met its acceptance criteria.

What is cross-phase integration checking in a milestone audit?

Cross-phase integration checking validates the wiring between completed project phases and end-to-end flows. It spawns integration checkers to ensure components work together correctly and that no phase introduced broken connections before a milestone is archived.

How do I track technical debt and deferred gaps when archiving a milestone?

Tracking technical debt during milestone archival involves aggregating unresolved issues and deferred gaps from verification artifacts. The audit collects these items, routes remediation tasks, and preserves the audit context for archival decisions.

Do I need specific planning files to run an automated milestone audit?

Yes, an automated milestone audit requires read access to .planning/phases/* directories containing SUMMARY.md and VERIFICATION.md files. The orchestrator workflow needs these files to aggregate gaps and execute integration checks.

What happens if a milestone audit finds missing requirements or integration failures?

When an audit finds missing requirements or integration failures, it routes remediation tasks and preserves the workflow gates. The consolidated verification report highlights these gaps and outstanding technical debt to prevent skipping verification steps.