gsd-audit-milestone

Audit milestone completion against its original definition of done.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-audit-milestone-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-audit-milestone
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-audit-milestone-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits milestone completion to ensure it aligns with the original definition of done before archiving, reducing risk of uncaptured requirements and misaligned progress.

Core Features & Use Cases

  • Definition alignment check: compares milestone criteria with planning and verification artifacts.
  • Cross-phase integration validation: verifies end-to-end wiring across phases and ensures verifications exist.
  • Gap and technical debt aggregation: aggregates findings from SUMMARY.md and VERIFICATION.md across phases to highlight gaps.

Quick Start

Run the audit-milestone workflow to generate the integrated verification report for the current milestone.

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 aligns with the original definition of done?

Milestone verification compares your completion criteria against planning and verification artifacts to validate definitions and ensure end-to-end flows are intact before archiving.

What is cross-phase integration validation for software milestones?

Cross-phase integration validation verifies end-to-end wiring across project phases and ensures verifications exist, triggering an integration-check step to confirm all phase definitions are met.

How do I aggregate technical debt and gaps across project phases?

Aggregating technical debt and gaps involves reading SUMMARY.md and VERIFICATION.md artifacts across phases to collect findings and highlight uncaptured requirements or misaligned progress.

When do I need to run a milestone audit before archiving?

Run a milestone audit before archiving to reduce the risk of uncaptured requirements and misaligned progress, ensuring your definition of done is fully satisfied across all workflow phases.

Can I use SUMMARY.md and VERIFICATION.md artifacts for cross-phase verification?

SUMMARY.md and VERIFICATION.md artifacts are read by the audit workflow to aggregate gaps, validate phase definitions, and trigger cross-phase wiring checks for milestone completion.