Claude for Product Managers
Lesson 5
The Requirements Completeness Check
After writing your PRD, run this prompt before sharing with engineering:
Review this PRD as if you are a senior engineer seeing it for the first time.
[Paste PRD]
List:
1. Every requirement that is ambiguous or has two valid interpretations
2. Every scenario or user state the PRD doesn't cover (especially error states, empty states, and permission edge cases)
3. Every success metric that can't be measured within 60 days of launch
4. Every place you would need to ask the PM a question before writing a line of code
Format your response as a numbered list. Be specific don't just say "this is vague," say exactly what's vague and why.
This prompt, run before sharing the PRD, typically catches 3–6 issues that would otherwise be discovered in sprint planning or QA.