Verified:GitHub

gsd-validate-phase

Audits missing Nyquist validation coverage and generates VALIDATION.md updates and test files for completed phases.

Updated Feb 11, 2026

Search Tags:#workflow automation #validation #test generation #github actions #documentation audit #nyquist #phase reconstruction

Ready to run

npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-validate-phase-artriv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-validate-phase
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-validate-phase
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-validate-phase-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents phases from having missing or incomplete Nyquist validation by retroactively auditing what already exists and filling in the required validation documentation and tests.

Core Features & Use Cases

Validation audit and gap filling: Reviews whether VALIDATION.md exists and updates it to cover missing Nyquist validation items.
Reconstruction from artifacts: When VALIDATION.md is missing but SUMMARY.md exists, it reconstructs validation details using available project artifacts.
Guarded phase handling: If the phase was never executed, it stops and returns guidance for the next appropriate action.

Quick Start

Use the gsd-validate-phase skill with the completed phase number to audit Nyquist validation and generate the missing VALIDATION.md updates and test files.

Frequently Asked Questions about gsd-validate-phase

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

FAQPage Schema

What is Nyquist validation coverage for a completed development phase?▼

Nyquist validation coverage retroactively audits completed project phases to ensure VALIDATION.md or SUMMARY.md files exist and accurately document the validated scope. It identifies missing validation items and generates required test files to fill documentation gaps.

How do I retroactively audit missing validation files for a completed project phase?▼

To retroactively audit missing validation files, execute the validate-phase workflow entrypoint with the completed phase number. This generates missing VALIDATION.md updates and test files by reconstructing validation details from existing project artifacts like SUMMARY.md.

Can I reconstruct validation documentation if only SUMMARY.md exists?▼

Yes, validation documentation can be reconstructed when VALIDATION.md is missing but SUMMARY.md exists. The process extracts validation details from available project artifacts to rebuild the required coverage and generate matching test files.

What happens if I try to validate a phase that was never executed?▼

If the phase was never executed, the validation process stops and returns guidance for the next appropriate action. This guarded handling prevents retroactively filling gaps for phases lacking actual development artifacts.

Does the validate-phase workflow work with GitHub Actions to preserve workflow gates?▼

Yes, the validate-phase workflow executes through GitHub Actions while preserving workflow gates. It ensures automated validation checks remain intact while updating VALIDATION.md to reflect the newly generated test coverage.