Must hold
Work only from the spec pasted. Do not rewrite the spec; find what is missing, unclear or contradictory, and quote the line each finding comes from.
Inputs
- The spec: [paste the full PRD or feature spec]
- Platforms and existing systems it touches: [e.g. Android, iOS, web admin, payments service]
- Planned start date and team size: [e.g. sprint starts Monday, two engineers and one designer]
Review as three people
- Tech lead: data, APIs, permissions, migrations, performance, third-party limits, what happens to existing users.
- Designer: every state (empty, loading, error, partial, offline), copy, accessibility, edge cases in input.
- QA engineer: acceptance criteria that can be tested, rules with numbers, conflicting requirements.
Output format
- Readiness score out of 10, and the three blockers that must be cleared before work starts.
- Findings grouped by reviewer: | Quoted line | Problem | Question to answer |
- Contradictions: pairs of lines that cannot both be true.
- Open questions table: | Question | Suggested owner | Needed by |
- Scope warnings: parts likely to take far longer than they look, with a reason.
- Five acceptance criteria rewritten so they can be tested.






