gsd-audit-milestone

Audit milestone completion against original intent using VERIFICATION.md files.

Updated Mar 27, 2026

Search Tags:#workflow #requirements #verification #audit #archiving #project-management #milestone

Ready to run

npx skills add https://github.com/onelee85/my-skills --skill gsd-audit-milestone-onelee85

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Milestones can drift from original intent, risking incorrect archiving decisions. This skill provides a structured verification to ensure milestones align with defined success criteria.

Core Features & Use Cases

Verifies alignment between milestone outcomes and defined success criteria across multiple phases.
Aggregates verification evidence from VERIFICATION.md files to surface gaps, tech debt, and deferred work.
Orchestrates cross-phase checks by spawning integration verifications to ensure end-to-end consistency.

Quick Start

Run the audit-milestone workflow to verify that the milestone meets its definition of done against VERIFICATION.md files and report gaps.

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 original requirements before archiving?▼

Milestone verification before archiving involves reading VERIFICATION.md files to confirm outcomes align with success criteria, aggregating tech debt, and running cross-phase integration checks to surface any deferred gaps.

What is the best way to audit cross-phase requirements coverage for a project milestone?▼

Auditing cross-phase requirements coverage requires aggregating verification evidence from completed phases and spawning an integration checker to validate end-to-end wiring and ensure the milestone meets its definition of done.

How does project milestone verification handle tech debt and deferred work?▼

Project milestone verification handles tech debt and deferred work by aggregating evidence from VERIFICATION.md files across verified phases, surfacing these gaps to prevent incorrect archiving decisions before the definition of done is met.

Do I need VERIFICATION.md files to run an end-to-end milestone audit?▼

Yes, you need VERIFICATION.md files from phases verified during execute-phase to run an end-to-end milestone audit, as the workflow reads these files to aggregate gaps and orchestrate cross-phase integration checks.

When should I not archive a project milestone in a workflow?▼

You should not archive a project milestone when the audit reveals misaligned outcomes, unresolved tech debt, deferred gaps, or failed cross-phase integration checks indicating it does not meet the defined success criteria.