gsd-validate-phase

Audit and fill Nyquist validation gaps in completed GSD project phases.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-validate-phase-pear-commerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-validate-phase
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-validate-phase
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-validate-phase-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completed GSD project phases often have missing or incomplete Nyquist validation documentation, leading to undetected quality gaps and non-compliant work being archived without proper review.

Core Features & Use Cases

  • Retroactive Validation Audit: Assess Nyquist validation coverage for any completed GSD phase, regardless of existing documentation status.
  • Gap Reconstruction: Rebuild full validation records from phase summary artifacts when no formal VALIDATION.md file exists.
  • Unexecuted Phase Guidance: Provide clear next steps for phases that were planned but never executed, avoiding unnecessary validation work.
  • Use Case: A project manager using the GSD workflow can run this skill after marking a phase complete to ensure all validation requirements are met before archiving, eliminating manual review of validation gaps.

Quick Start

Invoke the gsd-validate-phase skill to automatically audit and fill any Nyquist validation gaps for your last completed GSD phase.

Frequently Asked Questions about gsd-validate-phase

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

FAQPage Schema
How do I retroactively audit and fill missing validation gaps for completed GSD phases?

Retroactive validation audits assess completed GSD phases to identify Nyquist validation gaps, generating updated VALIDATION.md files and test artifacts to ensure compliance before archiving. It handles existing validation files, summary-only phases, and unexecuted phase states automatically.

What happens if my completed GSD phase has a SUMMARY.md but no VALIDATION.md file?

When a phase has a SUMMARY.md without formal validation docs, the skill reconstructs full validation records from the available summary artifacts. It rebuilds the missing VALIDATION.md file to meet phase validation standards without requiring manual reconstruction.

Do I need to manually create validation documentation before archiving a GSD project phase?

Manual validation documentation is not required before archiving GSD phases. The skill automatically audits Nyquist validation coverage, fills existing documentation gaps, and generates required test artifacts to ensure compliance without manual review.

How does phase validation handle GSD phases that were planned but never executed?

Unexecuted GSD phases receive clear guidance delivery instead of validation work. The skill recognizes the unexecuted state and provides next steps rather than attempting to audit or reconstruct validation documentation for work that was never started.

Can I run phase validation on any completed GSD phase regardless of its documentation status?

Phase validation supports three distinct states: existing VALIDATION.md files for gap filling, SUMMARY.md files without validation docs for reconstruction, and unexecuted phases for guidance. It audits Nyquist validation coverage across any completed phase state.

What is the best way to ensure workflow compliance before archiving completed GSD phases?

Running a retroactive phase validation audit ensures workflow compliance by checking Nyquist validation coverage and generating required test artifacts. It eliminates manual review by automatically filling documentation gaps and producing compliant VALIDATION.md files.