prd-validator

Validate PRD documents against PRD Template v2.0 structural and content rules.

Updated Aug 27, 2026

Search Tags:#validation #schema #prd #EARS #FR identifiers

Ready to run

npx skills add https://github.com/turbobeest/dev-system --skill prd-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-validator
Source: https://github.com/turbobeest/dev-system/tree/main/skills/prd-validator
Command: npx skills add https://github.com/turbobeest/dev-system --skill prd-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validates PRD documents against the PRD Template v2.0 specification, including schema checks, layer dependencies, interface contracts, and EARS format verification.

Core Features & Use Cases

Schema & layer validation: Ensure all required sections exist and adhere to layer rules.
Interface contracts: Check imports/exports compatibility between PRDs.
EARS format & RFC 2119: Verify that requirements use proper syntax and keywords.

Quick Start

Run PRD validation with "validate PRD" during Phase 3 to ensure PRD readiness.

Frequently Asked Questions about prd-validator

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

FAQPage Schema

How do I validate a PRD document against the PRD Template v2.0 specification?▼

PRD validation checks your document against the PRD Template v2.0 schema, verifying all 17 required sections exist, layer dependencies are correct, interface contracts match, and EARS formatting complies with RFC 2119 keywords. Run validation during Phase 3 to confirm PRD readiness before handoff.

What does EARS format validation check in PRD requirements?▼

EARS format validation ensures requirements use proper RFC 2119 compliant syntax—keywords like MUST, SHOULD, MAY—and follow the EARS structured language pattern. This standardizes requirement phrasing across your PRD for consistency and clarity.

Can I check interface export and import consistency between multiple PRDs?▼

Yes, interface contract validation verifies that exports from one PRD layer match imports in dependent layers, catching misalignment early. This prevents integration issues by ensuring interface compatibility across your PRD structure.

What happens if my PRD is missing required sections or has layer dependency violations?▼

Validation identifies missing sections from the 17 required fields and flags layer dependency violations, providing explicit feedback on what's broken. You can then fix structural gaps before the PRD moves to review or downstream systems.

Do I need any special tools or setup to run PRD validation?▼

No dependencies or special environment setup is required. Validation works directly on PRD documents during your product development pipeline, integrating with Phase 3 workflows for PRD authors, reviewers, and automation systems.