gsd-audit-milestone

Audit milestone completion against the original definition of done.

60|23|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/tomascortereal/claude-code-setup --skill gsd-audit-milestone-tomascortereal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/tomascortereal/claude-code-setup/tree/main/skills/gsd-audit-milestone
Command: npx skills add https://github.com/tomascortereal/claude-code-setup --skill gsd-audit-milestone-tomascortereal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of archiving incomplete milestones by ensuring all requirements are met and cross-phase integrations are verified before closure.

Core Features & Use Cases

  • Milestone Verification: Audits milestone completion against the original definition of done.
  • Cross-Phase Integration: Checks the wiring between different project phases (e.g., design, development, testing).
  • Technical Debt Aggregation: Collects and reports on deferred tasks and gaps discovered during the audit.
  • Use Case: After completing a major feature milestone in a software project, use this skill to run a comprehensive audit, ensuring the feature works end-to-end, all acceptance criteria are met, and any technical debt is documented for future sprints.

Quick Start

Use the gsd-audit-milestone command to verify the completion of 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 against original requirements before archiving?

A milestone audit checks if project deliverables match the original definition of done. It validates requirements coverage and verifies cross-phase integration to ensure the milestone goals are fully met before archiving.

What is the best way to check cross-phase integration during project closure?

Checking cross-phase integration involves verifying the wiring between different project phases like design, development, and testing. This validates that all components connect properly and function end-to-end before the milestone is archived.

How do I aggregate technical debt when closing a software milestone?

Aggregating technical debt during project closure involves collecting and reporting on deferred tasks and gaps discovered during the milestone audit. This documentation ensures remaining work is visible for future sprints.

When do I need to run a milestone audit in project management?

You need a milestone audit after completing a major feature or project phase. It is required when your workflow demands milestone validation to confirm all acceptance criteria are met before moving to the next sprint.

Does this milestone verification process work for software projects with deferred tasks?

Yes, milestone verification is designed for software projects with deferred tasks. It audits completion against acceptance criteria while specifically aggregating any technical debt or gaps found during the validation process.