DemoWhat a reviewer sees
One short paragraph or a static storyboard of the artifact/feature: the screen, the flow, the one thing a reviewer reacts to first. For a real PRD, embed a Tier-1 wireframe or prototype screenshot here — copied inline, never hot-linked.
- Entry surface / trigger
- Main interaction in 2-3 steps
- Success state (what “done” looks like)
PitchWhy now, why this
Problem
[One honest paragraph on the current friction. Name the pain concretely; no adjectives without evidence.]
Why now
[Timing or dependency that makes today the moment: a seam exists, a cost went down, a partner is ready, a deadline bites.]
Outcome we are buying
- [Measurable or at least observable outcome 1]
- [Measurable or at least observable outcome 2]
Scope
| In scope | Out of scope (now) | Explicitly refused |
|---|---|---|
| [core behavior] | [deferred to next slice] | [by policy / non-goal — state why in one line] |
GF / BF alternatives
One line per alternative considered and why the PRD picks what it picks. (A full side-by-side compare belongs to a Tier-1 exploration artifact; link or describe it here.)
- GF: [greenfield option] → [verdict in a sentence]
- BF: [brownfield option] → [verdict in a sentence]
- Do nothing: [cost of standing still]
Objections pre-answered
The pitch's credibility lives here: name the objections a skeptical maintainer actually raises, then answer them before they ask.
“…scope/effort — this is bigger than it looks.”
[What is actually small/shared/already-built; where the real boundary is.]
“…maintenance — who owns this after the slice closes?”
[Owner, regeneration path, and what health checks exist.]
“…this duplicates [existing thing].”
[One-line diff vs the existing thing; why the existing thing is not the right layer.]
Canonical source
The markdown source of record for this pitch lives at
docs/plans/...[slug]-prd.md (see the
<meta name="source"> header of this file). Edit the
.md; regenerate this render. Changes to this page without
a matching change to the source are a drift bug.