wowprompt

Product spec review with open questions before engineering starts

Reads a pasted product spec or PRD the way a careful tech lead, designer and QA engineer would, and returns every gap, contradiction and unanswered question before a sprint is planned around it. Use it the day before a kickoff so the questions are answered in writing instead of halfway through the build.

A list of spec gaps grouped by reviewer, open questions with owners and deadlines, and a readiness score with the three blockers to clear first
The output this prompt produced, unedited.

The prompt

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

  1. Tech lead: data, APIs, permissions, migrations, performance, third-party limits, what happens to existing users.
  2. Designer: every state (empty, loading, error, partial, offline), copy, accessibility, edge cases in input.
  3. QA engineer: acceptance criteria that can be tested, rules with numbers, conflicting requirements.

Output format

  1. Readiness score out of 10, and the three blockers that must be cleared before work starts.
  2. Findings grouped by reviewer: | Quoted line | Problem | Question to answer |
  3. Contradictions: pairs of lines that cannot both be true.
  4. Open questions table: | Question | Suggested owner | Needed by |
  5. Scope warnings: parts likely to take far longer than they look, with a reason.
  6. Five acceptance criteria rewritten so they can be tested.
prd reviewproduct spec reviewrequirements gapsengineering kickoffproduct managementfeature spec

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity