One-Page PRD Writer
Turn a rough feature idea into a crisp one-page PRD with open questions.
Product managers use this prompt to convert a rough feature idea into a structured one-page PRD: problem statement, goals and non-goals, user stories, success metrics, and — crucially — the open questions a real PM would need answered before committing.
The prompt
Variables to fill in: {{idea}}{{context}}
You are a senior product manager known for crisp, one-page PRDs. Turn my rough idea into a PRD with exactly these sections:
**Problem** — 2-3 sentences on the user pain, with who feels it and how often.
**Goals** — 3 bullet points max, each measurable.
**Non-goals** — what we are explicitly NOT doing in v1 (this section is mandatory).
**User stories** — 3-5 in "As a ___, I want ___ so that ___" form.
**Success metrics** — 2-3 metrics with target numbers (estimate if needed, mark estimates).
**Open questions** — the questions a skeptical engineer or designer would ask that I haven't answered.
Keep the whole document under 400 words. Do not pad. If my idea is too vague to fill a section, put your assumption in [brackets] so I can correct it.
Feature idea:
{{idea}}
Product context (company, users, constraints):
{{context}}How to use
- 1Brain-dump your idea into {{idea}} — messy is fine, that's the point.
- 2Give real context in {{context}}: who your users are and any hard constraints (platform, timeline, team size).
- 3Review everything in [brackets] first — those are the model's assumptions, and correcting them improves the whole doc.
- 4Iterate: "tighten the problem statement" or "make metric 2 more measurable" work well as follow-ups.
Examples
From idea to PRD
Input
Idea: let users save searches in our job board and get alerts. Context: B2C job board, 200k MAU, 3 engineers, mobile-web heavy.
Output
**Problem** — Job seekers on [Product] repeat the same search on average [4x/week], manually scanning for new posts... **Non-goals** — No push notifications in v1 (email only); no saved-search sharing... **Open questions** — What's the email deliverability setup? Do we cap alerts per user per day?
Pro tips
- Feed the finished PRD back with "play a skeptical engineering lead and poke holes in this" for a free design review.
Frequently asked questions
Why force a Non-goals section?+
Scope creep kills v1s. Making the model commit to explicit non-goals surfaces scope decisions early, and it's the section stakeholders argue with most productively.
Can I use this for internal tools or API features?+
Yes. For API features, add "the users are developers integrating via REST API" to the context and the user stories adapt accordingly.