gaia-validate-prd

Redirect legacy PRD validation calls to the gaia-val-validate validator.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-validate-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-validate-prd
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-validate-prd
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-validate-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a backward-compatible redirect for PRD validation by forwarding calls from the legacy gaia-validate-prd entry point to the canonical gaia-val-validate validator, ensuring existing integrations continue to function during migration.

Core Features & Use Cases

  • Thin redirect: no validation logic is implemented here; it delegates all work to gaia-val-validate.
  • Backward compatibility: preserves ADR-045 and FR-330 compliance by keeping the original invocation path available.
  • Consistent results: guarantees that PRD validation results come from the centralized validator.

Quick Start

Invoke /gaia-validate-prd with the PRD artifact path to be forwarded to gaia-val-validate.

Frequently Asked Questions about gaia-validate-prd

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

FAQPage Schema
How do I redirect legacy PRD validation calls to the new validator?

Redirect legacy PRD validation calls by invoking the gaia-validate-prd entry point with your PRD artifact path, which forwards the request unchanged to the canonical gaia-val-validate validator and returns its results.

Does the gaia-validate-prd entry point still work after migration?

Yes, the gaia-validate-prd entry point remains functional for backward compatibility, forwarding PRD artifact paths directly to gaia-val-validate so existing integrations continue working without modification during migration.

What is backward-compatible PRD validation redirect used for?

Backward-compatible PRD validation redirect preserves ADR-045 and FR-330 compliance by keeping the original invocation path available while delegating all validation logic to the centralized gaia-val-validate validator.

Do I need to install gaia-val-validate separately to use this redirect?

Yes, gaia-val-validate is required because this skill contains no validation logic itself; it relies on the standard GAIA plugin scripts and gaia-val-validate to perform the actual PRD checks.

Can I use gaia-validate-prd for PRD validation in existing workflows?

Yes, you can use gaia-validate-prd within PRD development workflows by passing the PRD artifact path, which is forwarded unchanged to gaia-val-validate to guarantee consistent validation results from the centralized validator.

Why does gaia-validate-prd return the same results as gaia-val-validate?

gaia-validate-prd returns identical results because it is a thin redirect that delegates all validation work to gaia-val-validate, ensuring PRD validation results always come from the centralized validator.