Front page / By role / Write a PRD
Write a PRD
From your notes to a reviewed PRD: the problem first, then a draft and its edge cases, an engineering and a design review, and the final spec.
For Product manager, Technical product manager, Product owner
What are you specifying?
One line is enough. Step 1 asks the rest in your AI app, and nothing is done until you approve the brief it writes.
In the case folder's materials/: Interview notes, support tickets, past specs or a meeting transcript in materials/.
The 6 steps
- 01
Frame the problem
Then you approve, before the next step starts.
- 02
Draft the PRD
- 03
Find the edge cases
Steps 2 to 3 run at the same time, one agent each.
- 04
Engineering review
- 05
Design review
Then you approve, before the next step starts.
Steps 4 to 5 run at the same time, one agent each.
- 06
Write the final PRD
The agents
design-reviewer- Reviews a PRD draft as a product designer would and writes outputs/05-design-review.md.
edge-case-finder- Lists the edge cases, risks and dependencies for the problem in the brief and writes outputs/03-edge-cases.md.
eng-reviewer- Reviews a PRD draft as an engineering lead would and writes outputs/04-eng-review.md.
prd-writer- Drafts a product requirements document from the approved problem statement and the notes in materials/, and writes outputs/02-prd-draft.md.
Where things stay
- On your computer
- Your files in materials/, every result in outputs/, the work itself. It runs in your AI app, on the plan you already pay for.
- With Cheatcode
- The steps, the gates and how far each case has come, so a case survives closing the app. See your cases.