skills.rest
electroheadfx
electroheadfxCOMMUNITY
Explore all skills by this author →
GitHub

gsd-audit-milestone

Audit milestone completion evidence and cross-phase integration against definition of done.

4|Updated Apr 11, 2026
Search Tags:#verification#technical debt#requirements coverage#milestone audit#integration check
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-audit-milestone-electroheadfx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-audit-milestone
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-audit-milestone-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps confirm whether a milestone has actually met its definition of done before it is archived, reducing the risk of shipping incomplete work or overlooking unresolved gaps.

Core Features & Use Cases

  • Milestone Verification: Reviews completed work evidence, verification files, and scope coverage to assess whether the milestone is truly finished.
  • Cross-Phase Integration Check: Examines how phases connect end to end so hidden wiring issues, deferred gaps, and dependency mismatches are caught early.
  • Use Case: Use this Skill when a project team wants a final audit of milestone status after execution work is complete and before closing it out.

Quick Start

Ask the skill to audit the current milestone and summarize any missing coverage, integration risks, or deferred technical debt.

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 before archiving a development phase?▼

To verify milestone completion, audit your verification artifacts, requirement coverage, and cross-phase integration to ensure the definition of done is met. This catches deferred gaps and hidden wiring issues before final archival.

What is the best way to audit requirements coverage for technical debt at a milestone?▼

The best way to audit requirements coverage is to read verification files and aggregate any deferred technical debt gaps. This ensures unresolved work is documented rather than overlooked during milestone closeout.

How do I check end-to-end integration across project phases to catch hidden wiring issues?▼

You check end-to-end integration by examining how development phases connect and verifying dependency alignment. This cross-phase integration check surfaces hidden wiring issues before the milestone is archived.

Can I use a milestone audit to ensure workflow gates are not skipped during project closeout?▼

Yes, a milestone audit confirms workflow gates are satisfied by validating completion evidence without defaulting past unanswered checkpoints. This reduces the risk of shipping incomplete work or unresolved gaps.

When do I need to perform a milestone audit in a structured development project?▼

You need a milestone audit during end-of-cycle review workflows, specifically after execution work is complete and before closing out the phase. It confirms the project is ready for archival and meets its definition of done.

Related Skills

Explore More Software Engineering Skills→
ArtRivArtRiv

gsd-audit-milestone

Audit milestone completion by verifying requirements coverage, integration wiring, and end-to-end flows.

Community
Intermediate
jasonmichaelbell78-creatorjasonmichaelbell78-creator

verify-technical-debt

Verify technical debt items and triage VERIFIED ones into ROADMAP sprints.

Community
Advanced
wangqianCAIwangqianCAI

openclaw-parallels-smoke

Automate cross-platform smoke testing and regression verification for OpenClaw Parallels guests.

Community
Advanced
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced