gsd-validate-phase

Audit Nyquist validation coverage and generate missing validation artifacts.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-validate-phase-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-validate-phase
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-validate-phase
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-validate-phase-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retroactively audit and fill Nyquist validation gaps for a completed phase, ensuring contracts and tests align with actual execution.

Core Features & Use Cases

  • Audit the completeness of Nyquist validation coverage for a finished phase.
  • Reconstruct missing validation artifacts from existing phase data when VALIDATION.md is absent.
  • Generate updated validation artifacts and tests to close gaps and preserve workflow integrity.

Quick Start

Run the validate-phase workflow for the target phase to audit and fill the validation gaps.

Frequently Asked Questions about gsd-validate-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit validation coverage for a completed development phase?

You audit validation coverage for a completed phase by running a retroactive check that identifies gaps, reconstructs missing artifacts from existing phase data, and generates updated test files to preserve workflow integrity.

What is Nyquist phase validation and when do I need to reconstruct it?

Nyquist phase validation verifies contract and test alignment with execution. You need to reconstruct it when a phase is completed but the VALIDATION.md file is missing and must be rebuilt from existing artifacts.

How do I generate missing VALIDATION.md files from existing phase artifacts?

You generate missing VALIDATION.md files by running a validation audit workflow that extracts data from existing artifacts and SUMMARY.md, then outputs the reconstructed documentation alongside any required test files.

Can I target a specific phase for validation gap auditing?

Yes, you can target a specific phase for validation gap auditing by passing an optional phase argument to the workflow, which restricts the audit and artifact generation to that specific phase.

Does retroactive phase validation preserve existing workflow gates?

Yes, retroactive phase validation preserves all existing workflow gates while outputting the updated VALIDATION.md and generated test files required to close documentation gaps without disrupting the established process.