prd-review

PRD validation involves checking your document against a 13-criteria checklist covering overview, audience, features, API, data model, error handling, testing, dependencies, non-functional requirements, development phases, convention compliance, business context, and business rules. The Skill outputs structured PASS, PARTIAL, or MISSING status with actionable improvement suggestions for each criterion.

Requirements validation ensures Product Requirements Documents meet comprehensive quality criteria before development begins. It evaluates clarity, completeness, and alignment by checking sections like features, API, data model, error handling, and non-functional requirements against a predefined 13-point checklist covering both technical and business contexts.

Yes, CLAUDE.md and CONVENTIONS.md are required to provide context and ensure adherence to project standards during PRD review. These files supply the project conventions and context needed to validate convention compliance, one of the 13 criteria evaluated in the quality checklist.

The best way to check a PRD for completeness is to validate it against a 13-criteria checklist covering overview, audience, features, API, data model, error handling, testing, dependencies, non-functional requirements, development phases, convention compliance, business context, and business rules. This ensures all necessary details are well-defined before engineering handoff.

The PRD review checklist assigns a PARTIAL or MISSING status to incomplete sections. It provides clear, actionable suggestions for improvement, allowing the product manager to identify exactly what needs to be added or refined across all 13 evaluation criteria.

This PRD quality assurance checklist applies to product management workflows requiring rigorous completeness checks. It is designed for newly drafted PRDs for new features, ensuring all necessary details are present and well-defined before handing off to the engineering team.