---
name: product-requirements-document
description: "A PRD with the problem and evidence first, requirements written as observable behaviour with edge cases, a firm out-of-scope list, and open questions with owners. Use when a product manager needs a requirements document precise enough that two engineers would build the same thing. Do not use for a one-page pitch or sprint-level user stories. Related topics: Product, Planning, Writing."
---

# Product Requirements Document

A PRD with the problem and evidence first, requirements written as observable behaviour with edge cases, a firm out-of-scope list, and open questions with owners.

## When to use

Use this skill when a product manager needs a requirements document precise enough that two engineers would build the same thing. Do not use it for a one-page pitch or sprint-level user stories.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Write the problem and evidence section first and mark plainly where the evidence is thin.
3. Describe the solution as observable behaviour step by step, done when an engineer could test each line.
4. Add edge cases and error states, including what happens to existing data.
5. Write a prominent out-of-scope section naming what people will otherwise assume.
6. Close with success metric and check date, constraints, and open questions each with an owner and a date.

## Inputs

- **What is wrong today** (longer free text)
- **Evidence** (longer free text)
- **Who is affected and roughly how many** (longer free text)
- **What we would build** (longer free text)
- **User-visible behaviour** (longer free text)
- **Edge cases and error states** (longer free text)
- **Explicitly out of scope** (longer free text)
- **Constraints** (longer free text)
- **Deadline and what drives it** (free text, e.g. "Date and why")
- **Success metric and target** (free text, e.g. "Metric and number")
- **Date to check results** (free text, e.g. "Date")

## Output

A PRD with sections for problem and evidence, solution and behaviour, edge cases, out of scope, constraints, success, and open questions with owners.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Product Requirements Document

Write a PRD from the details below.

- What is wrong today: {{What is wrong today}}
- Evidence: {{Evidence}}
- Who is affected and roughly how many: {{Who is affected and roughly how many}}
- What we would build: {{What we would build}}
- User-visible behaviour: {{User-visible behaviour}}
- Edge cases and error states: {{Edge cases and error states}}
- Explicitly out of scope: {{Explicitly out of scope}}
- Constraints: {{Constraints}}
- Deadline and what drives it: {{Deadline and what drives it}}
- Success metric and target: {{Success metric and target}}
- Date to check results: {{Date to check results}}

Lead with the problem and the evidence, not the solution. If the evidence is thin, say so in the document rather than burying it.

Write the requirements as observable behaviour including the edge cases, because that is the part engineers otherwise have to invent. Say what happens to data that already exists. Make the out-of-scope section prominent: it is the cheapest scope-argument prevention available. End with open questions, each with an owner and a date.

## Pitfalls

- Describing the solution before the problem, which invites debate about the design instead of the need.
- Leaving edge cases and existing data unaddressed, so engineers invent the answer.
- Setting a success metric with no target or date, so nobody can call it a win or a miss.
