Write PRD

Goal: produce a PRD that is precise, self-contained, and unambiguous. A reader should know exactly what to build and why without asking follow-up questions.

Process

Step 1 — Gather context

Ask the user these questions. Do not proceed until questions 1–3 are answered with specifics.

1. What problem are you solving? State it as a user or business problem, not as a feature request.
2. Who has this problem? Name the user type, their context, and how often they face it.
3. What does success look like? What measurable outcome signals this worked?
4. What is explicitly out of scope? What related problems are you intentionally not solving?
5. What constraints exist? Hard limits on compatibility, compliance, budget, or technical non-negotiables.
6. What assumptions are you making? Things you're treating as true that could turn out false.

Questions 4–6 may be answered with "none" but must be explicitly addressed.