gsd-audit-milestone

Name: gsd-audit-milestone
Availability: InStock
Author: lgwanai

Audit milestone completion against definition of done using verification artifacts.

4|1|Updated Mar 22, 2026

Search Tags:#integration testing #project planning #workflow orchestration #definition of done #requirements coverage #milestone audit #end-to-end verification

Ready to run

npx skills add https://github.com/lgwanai/openforce --skill gsd-audit-milestone-lgwanai

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature archiving by validating that a milestone truly satisfies its original “definition of done,” including cross-phase integration and end-to-end behavior.

Core Features & Use Cases

Milestone completion verification: Checks that the milestone’s outcomes match the documented definition of done.
Requirements coverage & gap aggregation: Aggregates deferred gaps and technical debt from existing verification artifacts.
Cross-phase integration checks: Ensures wiring between phases is correct and that end-to-end flows function as intended.
Tool-gated orchestration: Preserves workflow gates for scope determination, verification reading, integration checking, and routing.

Quick Start

Run gsd-audit-milestone to verify the current milestone’s definition of done and produce an end-to-end integration confirmation.

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 its definition of done?▼

To verify milestone completion against its definition of done, audit requirements coverage, cross-phase integration, and end-to-end flows by aggregating verification artifacts from previously executed project phases.

How does cross-phase integration checking work for project archive readiness?▼

Cross-phase integration checking validates wiring between phases by reading phase VERIFICATION.md files and running an integration checker to confirm end-to-end flows function correctly before project archive readiness.

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

Aggregating deferred gaps and technical debt before archiving a milestone involves consolidating existing verification artifacts and revalidating them against the documented definition of done to prevent premature archiving.

Can I use workflow orchestration gates during milestone audit checks?▼

Workflow orchestration gates are preserved during milestone audit checks to manage scope determination, verification reading, integration checking, and routing while validating end-to-end behavior.

Do I need existing phase verification artifacts to run an end-to-end integration check?▼

Existing phase verification artifacts are required to run an end-to-end integration check because the audit aggregates and revalidates these outputs to confirm the milestone satisfies its original definition of done.