gsd-audit-milestone

Verify milestone completion against original intent and requirements coverage.

Updated Apr 22, 2025
One-click install
npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-audit-milestone-mcampbellr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/gsd-audit-milestone
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-audit-milestone-mcampbellr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the verification of milestone achievements, ensuring alignment with original intent before archiving.

Core Features & Use Cases

  • Audit Milestone Completion: Verifies whether milestones meet their defined 'Definition of Done'.
  • Cross-Phase Integration: Checks requirements coverage and cross-phase integration, ensuring robustness.
  • End-to-End Flows: Orchestrate and preserve workflow gates, maintaining scope determination and verification integrity.
  • Use Case: When closing a project phase, use this Skill to verify all milestones, ensuring that no requirements or integration points have been overlooked.

Quick Start

Activate the 'gsd-audit-milestone' skill with the version you wish to audit, e.g., 'gsd-audit-milestone v1.2'.

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 project requirements?

Milestone verification confirms completed deliverables against original intent by validating requirements coverage and cross-phase integration. This audit process ensures alignment with project scope and confirms the Definition of Done is met before archiving a project phase.

What is cross-phase integration checking in project audits?

Cross-phase integration checking validates that requirements coverage spans across all connected project phases. During milestone audits, it ensures no integration points or dependencies have been overlooked when closing a phase, maintaining overall workflow integrity.

When do I need to run a milestone audit before archiving?

Run a milestone audit before archiving when closing a project phase to verify all milestones meet their defined Definition of Done. This ensures no requirements or cross-phase integration points have been overlooked before final archival.

How do I audit a specific version's milestone completion?

To audit a specific version, activate the skill referencing the version you wish to audit, such as specifying the version number. The audit process then verifies milestone completion and requirements coverage for that targeted version.

What's the best way to ensure no requirements are missed when closing a project phase?

The best way to ensure no requirements are missed is orchestrating an end-to-end milestone audit that checks requirements coverage and cross-phase integration. This verifies alignment with project scope and preserves workflow gates before phase closure.

Does milestone verification preserve workflow gates during project closure?

Yes, milestone verification preserves workflow gates by orchestrating end-to-end audit flows that maintain scope determination and verification integrity. This ensures robust cross-phase integration checks are completed before archiving project phases.