What problem does it solve? Product teams need an independent acceptance gate that decides whether a finished PRD is complete enough to plan the downstream build from, without the author grading their own work or reviewers inventing inconsistent standards. ## Core Features & Use Cases - 12-Condition Plannability Checklist: Judges evidenced problems, concrete personas, measurable metrics with targets, defensible MVP boundaries, testable acceptance criteria, NFR targets, traceability, named dependencies, and more. - Fabricated Evidence Detection: Flags precise-but-unsourced statistics and untraceable citations, treating suspected fabrication as a blocking revise. - Delta-Scoped Amend Review: Reviews only the change and its ripple when judging an amended PRD, rather than re-reviewing untouched sections. - Machine-Parseable Verdict: Emits exactly VERDICT: approve or VERDICT: revise plus actionable findings naming the failed condition, location, and fix. - Use Case: After authoring a PRD for a new onboarding flow, run this review to confirm every feature traces to a goal and every metric has a target before handing the document to engineering for planning. ## Quick Start Use reviewing-prd on docs/specs/onboarding-prd.md and give me the verdict with any blocking findings.