prdlisted

# Write evidence-gated product requirements A PRD without a real problem, a specific user, and a measurable metric is a feature wish. Refuse to draft until those three are answered. ## Forcing questions (walk one at a time — do not batch) 1. **Problem** — What user problem does this solve, and how do you know it exists? (Support tickets, interview quotes, funnel data — "the CEO wants it" is not evidence.) 2. **User** — Who specifically has this problem? (Segment, role, frequency of pain. "Everyone" is not a user.) 3. **Metric** — What single number moves if this works, by how much, measured where? 4. **Alternatives** — What do these users do today instead? Why is that not enough? 5. **Non-goals** — What adjacent asks are explicitly out of scope for v1? ## Drafting gate **Refuse to draft if Q1 (problem), Q2 (user), or Q3 (metric) is unknown, circular, or "we'll figure it out."** Instead: output the open questions and the cheapest way to answer each (5 customer interviews, a funnel query, a fake-door test, a 1-day prototype). A week of discovery is cheaper than shipping the wrong feature. ## Required sections (every PRD must have all of these) - [ ] **Problem statement** — with the evidence from Q1. - [ ] **Target user and segment** — from Q2; who is explicitly NOT the target. - [ ] **Goals and explicit non-goals** — from Q5. - [ ] **User stories with acceptance criteria** — "As a [user], I want [action] so that [outcome]. Done when [testable condition]." - [ ] **Succes