PRD
A PRD generator that writes the document the way it should be read: what people will be able to do when this ships, what is deliberately out, and what has to be decided before anyone builds. From a few paragraphs of an idea, or from a BRD you already approved.
- Asks for
- The idea, the problem it solves, and who it is for
- An approved BRD, if the case has already been made somewhere
- Anything already decided — constraints, dates, the things that are not up for discussion
- Gives back
- Goals stated so you could tell whether you hit them
- What people will be able to do, in user terms
- An explicit out-of-scope list
- Requirements precise enough to argue with, and the open decisions named as decisions
- Plan
- Free
- Use next
- BRD, FRD, Epic, Document to tickets, One-pager
What it gives you
2. What people will be able to do 2.1 Import a backlog from a CSV and see it ranked before saving anything. 2.2 Correct any score by hand; the ranking updates and records that it was edited. 3. Out of scope for this release — Two-way sync back to Jira. One-way import only. — Team permissions. One person, their own backlog. 5. Open decisions 5.1 What happens to a row with a missing effort value? Not decided. Owner: you.
How it works
A PRD earns its length in two places: scope and open questions. The user-facing part — what somebody will be able to do that they cannot do today — is what the team builds against, and the out-of-scope list is what stops the quarter expanding by a feature a week. Everything else in a typical PRD template is padding.
So that is what this writes, in that order. Goals you could tell whether you hit, the capabilities in user terms rather than component terms, the explicit out-of-scope list, the requirements precise enough to disagree with, and the decisions still outstanding named as decisions rather than buried as caveats.
It will not fill a gap it was not given. If you have not said what happens when the import fails, the document carries that as an open question with your name on it rather than inventing a sensible-sounding rule that an engineer will then implement. That is the difference between a document that surfaces the work and one that hides it.
Who it is for
A PM who has an agreed idea and needs the document that lets design and engineering start, without spending two days formatting a template.
Where it stops
A PRD is a decision record, not a decision maker: it cannot settle a scope argument you have not had, and it will hand the unresolved ones back to you as open questions. It also does not write the technical design — what people can do, not how it is built, which is the FRD’s job.
Questions people ask
What is the difference between a PRD, a BRD and an FRD?
A BRD makes the case: why do this at all, what it is worth, what it costs. A PRD says what people will be able to do if you say yes, and what is out of scope. An FRD says exactly how it behaves, including the unhappy paths, in enough detail to build and test against. They are written in that order because each one is cheaper to change than the next, and skipping the first is how teams build something that works perfectly and should not exist.
Can it write a PRD from a BRD I already have?
Yes, and that is the cleaner path. Hand it the BRD and the PRD is written against the case that was actually approved, so the scope answers the problem somebody signed off rather than a fresh interpretation of it. Where the BRD leaves something undecided, the PRD says so instead of choosing for you, because a PRD quietly resolving a business question is how a decision gets made by whoever typed fastest.
Will it invent requirements I did not mention?
No. Where something is unspecified — what happens when the import fails, whether an edited score is remembered — the document carries it as an open decision with an owner rather than filling it with a plausible rule. That is deliberate: an invented requirement reads exactly like an agreed one three weeks later, and somebody will build it. The open-decisions section is usually the most useful page in the document.
Run it on your own work
PRD needs an account, because it writes against what you give it and remembers what you have told it before. It runs on the Free plan. Or see what the plans cost first.