gsd-audit-milestone

Name: gsd-audit-milestone
Availability: InStock
Author: roycolumbia-code

Verify project milestone compliance against its definition of done.

Updated Mar 23, 2026

Search Tags:#project management #audit #requirements coverage #integration check #milestone verification

Ready to run

npx skills add https://github.com/roycolumbia-code/claude-global-config --skill gsd-audit-milestone-roycolumbia-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/roycolumbia-code/claude-global-config/tree/main/skills/_audit-disabled-20260706-1136/gsd-audit-milestone
Command: npx skills add https://github.com/roycolumbia-code/claude-global-config --skill gsd-audit-milestone-roycolumbia-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Agent, and includes scripts (resource) components.

What problem does it solve?

This Skill verifies that a project milestone meets its intended goals, ensuring requirements coverage and end-to-end flow integrity before archiving.

Core Features & Use Cases

Milestone Verification: Confirms that the milestone has achieved its definition of done.
Requirements Coverage: Checks that all requirements are met.
Integration Integrity: Validates cross-phase integration and end-to-end flows.
Use Case: Before archiving a project milestone, use this Skill to ensure that all phases are correctly implemented and that the milestone aligns with the initial intent.

Quick Start

Run the gsd-audit-milestone skill with the specific milestone version, e.g., 'gsd-audit-milestone 1.0'.

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 project milestone compliance before archiving?▼

To verify project milestone compliance, you can audit the milestone against its definition of done, which checks requirements coverage and validates end-to-end flow integrity before archiving.

What's the best way to check requirements coverage for a specific milestone version?▼

Checking requirements coverage involves running an audit on the specific milestone version, ensuring all requirements are met and cross-phase integration aligns with the initial project intent.

How does cross-phase integration check work for milestone verification?▼

Cross-phase integration check works by operating on existing verification files and tech debt logs to validate end-to-end flows, ensuring all project phases are correctly implemented together.

Do I need Bash and Agent to perform a milestone audit?▼

Yes, you need Bash and Agent tools to perform a milestone audit, as these dependencies are required to execute the verification scripts and analyze the project's integration integrity.

When should I run a milestone verification audit in the software lifecycle?▼

You should run a milestone verification audit right before archiving a project milestone, ensuring that the deliverables meet the definition of done and that cross-phase integration is complete.

What limitations exist when auditing milestone compliance using existing verification files?▼

Auditing milestone compliance depends entirely on the accuracy of existing verification files and tech debt logs; if these inputs are incomplete, the integration check may not reflect actual project state.