Top pickProduct
PRD from messy notes
Turns call notes, Slack threads and a rough idea into a tight PRD with scope, non-goals and open questions.
Use it when
You know what you want to build but have not written it down properly.
What you fill in
- notes Everything you have: notes, quotes, screenshots described in words
- users Who it is for
- constraints Deadline, team, technical limits
The prompt
Write a product requirements document from these notes. Notes: notes For: users Constraints: constraints Sections: 1. Problem: who has it, how often, what it costs them. Quote the notes where you can. 2. Goal and success metric (one primary, two guardrails). 3. User stories, as "As a ___, I want ___ so that ___", at most 8, ordered by importance. 4. Scope for v1 and explicit non-goals. 5. UX: the main flow, step by step, and the empty, loading and error states. 6. Open questions, each with who can answer it. 7. Risks and how we will know early. Do not invent user quotes or data. Where the notes are silent, write "Unknown" and add it to open questions. Before you answer, check your draft against every instruction above and fix anything that misses.
Why it works
- Separates evidence (quotes) from assumptions (open questions).
- Non-goals keep scope honest.
- Asks for empty, loading and error states, which PRDs usually skip.