Product Requirements Review Checklist
Check a PRD before engineering starts.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review a product requirements document. The document: [PRD_TEXT]. The team and timeline: [TEAM_AND_TIMELINE]. Check each item and mark it pass, gap, or unclear, with the evidence quoted from the document: problem is evidenced; target users defined; goals and non-goals stated; success metrics with baseline and target; requirements prioritized and uniquely identified; acceptance criteria testable; edge cases and errors considered; non-functional requirements present (performance, security, accessibility, privacy); dependencies and owners; analytics defined; rollout and rollback plan; open questions with owners; no solution disguised as a requirement. Output format: 1. A table: Item | Status | Evidence | Fix. 2. Readiness percentage = passes / items, with the arithmetic, and a suggested threshold for starting work, noted as a judgment. 3. A recommendation: ready, ready with changes, or not ready. 4. The five most important gaps, each with the question the author must answer before engineering starts. Do not add content that is not in the document.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.