PhraseryPhrasery homeGet Phrasery
Product & planning21 categories

Draft a PRD from my notes

The work is agreed in conversation and now needs a document people can disagree with.

Draft a product requirements document from my notes.

Sections, in order:
1. **Problem** and who has it, with evidence. Label anything unevidenced.
2. **Why now.** If there is no answer, say so.
3. **Goals** and **non-goals**. The non-goals list should be at least as long.
4. **Proposed solution**, described by behaviour rather than implementation.
5. **Success metrics**, with the current baseline. A metric with no baseline is flagged.
6. **Open questions** and who owns each.
7. **Risks and what we would do about each.**

Keep it under two pages. Use my words where I gave them. Anywhere my notes are thin, write **[needs input]** rather than composing confident filler.

Notes:

Making it yours

  • Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
  • Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
  • If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.

Specs and stories. Turning a vague request into something a team can build: specs, PRDs, stories and acceptance criteria.

Related prompts

Keep this one

Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.

Add to your browser โ€” free