gsd-audit-milestone

Audit milestone completion by aggregating verification artifacts and checking requirements coverage.

1|Updated Apr 4, 2026

Search Tags:#workflow #verification #audit #compliance #project-management #milestone

Ready to run

npx skills add https://github.com/nnexai/git-stacks --skill gsd-audit-milestone-nnexai

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of incomplete project milestones by automating the audit of verification artifacts and ensuring all requirements are met before archiving.

Core Features & Use Cases

Automated Verification: Aggregates and audits existing VERIFICATION.md and SUMMARY.md files across project phases.
Integration Checking: Spawns specialized agents to verify cross-phase wiring and end-to-end flow integrity.
Use Case: Before closing a major feature milestone, use this skill to automatically detect missing requirements or deferred technical debt that would otherwise be overlooked.

Quick Start

Invoke the gsd-audit-milestone skill to perform a full audit of the current project 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 project milestone completion and verify requirements coverage?▼

To audit milestone completion, you can aggregate phase-specific verification artifacts like VERIFICATION.md and SUMMARY.md files to check requirements coverage and validate cross-phase integration. This ensures all project requirements are met before archiving.

What is the best way to detect deferred technical debt before closing a feature milestone?▼

Detecting deferred technical debt before closing a feature milestone requires auditing verification artifacts across project phases to identify gaps in requirements coverage. Automated aggregation of these files highlights overlooked debt before archiving.

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

Cross-phase integration checking works by spawning specialized agents to verify end-to-end flow integrity and wiring across project phases. This validates that all components connect properly within the workflow framework before milestone completion.

Do I need project planning directories to verify milestone integrity?▼

Yes, verifying milestone integrity requires access to project planning directories to aggregate phase-specific verification artifacts and spawn integration-checking agents. These directories provide the necessary context for end-to-end validation.

Can I automate compliance verification for missing requirements across project phases?▼

You can automate compliance verification by aggregating existing SUMMARY.md and VERIFICATION.md files across project phases to detect missing requirements. This automated auditing process ensures full requirements coverage before archiving milestones.