gsd-audit-milestone

Audit milestone completion against its definition of done.

Updated Mar 1, 2026

Search Tags:#workflow #project management #verification #audit #tech debt #milestone

Ready to run

npx skills add https://github.com/NUbivek/Searchbar3 --skill gsd-audit-milestone-nubivek

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that completed milestones meet their original objectives and requirements before being archived, preventing technical debt and ensuring project integrity.

Core Features & Use Cases

Milestone Verification: Audits if a milestone has achieved its definition of done.
Requirement Coverage: Checks if all necessary requirements have been met.
Cross-Phase Integration: Verifies integration and end-to-end flows across different project phases.
Tech Debt Aggregation: Collects and aggregates technical debt and deferred gaps.
Use Case: Before archiving a development sprint's milestone, use this Skill to confirm all user stories are implemented, tested, and integrated with the main codebase.

Quick Start

Use the gsd-audit-milestone skill to audit 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 audit milestone completion against its original definition of done?▼

Auditing milestone completion involves reading existing verification files and spawning an integration checker to validate requirements coverage and cross-phase integration against the original definition of done.

What is the best way to aggregate technical debt and deferred gaps before archiving a milestone?▼

Aggregating technical debt requires running a milestone audit that collects and consolidates all outstanding gaps for the specified or current milestone before archiving.

How does cross-phase integration verification work for project milestones?▼

Cross-phase integration verification works by spawning an integration checker that reads existing verification files to validate end-to-end flows across different project phases.

Do I need existing verification files to audit a milestone?▼

Yes, existing verification files are required because the milestone audit reads them to verify requirements coverage and cross-phase integration before archiving.

Can I check requirements coverage for a specific milestone instead of the current one?▼

Yes, you can specify a target milestone to check requirements coverage, and the audit will aggregate technical debt and verify end-to-end flows for that milestone.

When should I not use milestone verification for my project management workflow?▼

You should avoid milestone verification when verification files are missing, as the audit relies on reading existing files to validate requirements coverage and cross-phase integration.