jp-prd-review

To review a PRD for feasibility, compare it against the original prompt to identify coverage gaps, contradictions, and ambiguities. Evaluating requirement implementability and testability produces a formal PASS, REVISE, or ESCALATE verdict to prevent downstream mistakes.

A PRD coverage assessment maps each item from the original prompt to the PRD to determine whether it is fully, partially, or not addressed. You need this before kickoff to catch missing requirements and scope inconsistencies early.

Checking a Product Requirements Document for contradictions involves structural analysis of each requirement to evaluate completeness and consistency. This process identifies missing edge cases, feasibility concerns, and scope inconsistencies before generating an actionable review document.

Yes, you can review a PRD within phase directories under .plans/ that contain prompt.md and prd.md files. The process evaluates implementation viability against these structured inputs and outputs a formal review document with actionable feedback.

The best way to generate a formal verdict for a PRD review is to assess requirement implementability, testability, and consistency, then produce a PASS, REVISE, or ESCALATE verdict. This outputs a structured review document with guidance for next steps.

Your PRD review may fail to catch downstream implementation mistakes if it lacks a requirement interview phase to gather feedback for edits or approvals. Without evaluating implementation viability per requirement, contradictions and feasibility issues remain unresolved.