validate-prd

Validates PRD quality against eight structured checks before architecture design begins.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/alessioroberto82/claude-plugin-circle --skill validate-prd-alessioroberto82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-prd
Source: https://github.com/alessioroberto82/claude-plugin-circle/tree/main/plugins/circle/skills/validate-prd
Command: npx skills add https://github.com/alessioroberto82/claude-plugin-circle --skill validate-prd-alessioroberto82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Weak or incomplete PRDs cause costly rework when discovered during architecture or implementation. This Skill acts as an independent quality gate that catches missing sections, untestable acceptance criteria, vague metrics, and implementation leakage before design work starts. ## Core Features & Use Cases - Eight Structured Checks: Validates completeness, requirements coverage, traceability, measurability, density, implementation leakage, domain compliance, and overall quality. - Automatic PRD Discovery: Resolves the most recent PRD from the refine output directory, with path-traversal-safe filename handling and optional requirements coverage checking. - Clear Verdicts and Reports: Produces a PASS, PASS with notes, or NEEDS REVISION verdict with a saved Markdown report listing blockers and suggestions. - Use Case: After running the refine step to draft a PRD, run this validator to confirm every functional requirement maps to a work item with testable acceptance criteria before handing off to the Architecture Owner. ## Quick Start Validate the latest PRD in my project and tell me whether it is ready for architecture design.

Frequently Asked Questions about validate-prd

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

FAQPage Schema
How do I validate a PRD before architecture design?▼

Run the validator after the refine step and before architecture work. It loads the most recent PRD from your project output, runs eight quality checks, and returns a PASS, PASS with notes, or NEEDS REVISION verdict with a saved report.

What checks does PRD validation include?▼

Eight checks: completeness of required sections, requirements coverage against FR items, traceability of acceptance criteria, measurability of success metrics, density without placeholders, implementation leakage, domain compliance, and an overall weighted quality verdict.

What happens if no PRD file is found?▼

The validator looks for the most recent PRD-*.md file in the refine output directory, falling back to PRD.md. If none exists, it reports that the PRD is missing and instructs you to run the refine step first.

Can I validate a specific PRD file by name?▼

Yes, you can provide a filename and only that file is validated. Path separators and parent-directory segments are stripped, so only files inside the refine output directory are accessible.

What causes a PRD to fail validation?▼

Any failure in the first four checks blocks approval: missing required sections, uncovered functional requirements, missing or untestable acceptance criteria, or goals without quantifiable metric targets. Warnings on later checks produce PASS with notes instead.