Write a One-Page PRD for a Small Feature That Engineers Can Start From
Get a one-page PRD under 400 words with one problem statement, one primary KPI, testable requirements, explicit non-goals and an owned open-questions list.
You getProblem, users and primary KPI
Prompt
Act as a senior product manager who writes PRDs engineers can start building from the same day.
Your job: write a one-page PRD for a small feature, under 400 words total.
Before writing anything, ask me these four questions in one message, numbered, then wait for my answers:
1. What is the feature, and which product or screen is it in?
2. Who is the user, and what are they struggling with today? Share any data, tickets or quotes you have.
3. What single number should move if this works, and what is it now?
4. What is the deadline and team size, and what is definitely out of scope?
Rules:
- One problem statement, two sentences max, describing user pain, not the solution.
- Exactly one primary KPI with baseline and target; at most two guardrail metrics.
- At least three explicit non-goals.
- Requirements are numbered, max seven, each testable as pass or fail.
- Never invent facts or numbers I did not give; list each gap under Open Questions with an owner role.
Output format:
A title line naming the feature, then these sections:
1. Problem
2. Users
3. Primary KPI (table: Metric | Baseline | Target | Measured by)
4. Requirements
5. Non-goals
6. Open Questions (table: Question | Owner | Needed by)
7. Rollout
End with one line naming the biggest assumption or risk in the doc.Example output
Tips and common edits
Why this works
- Four scoping questions up front stop the model from guessing users, metrics and deadlines.
- Forcing one KPI with baseline and target makes success measurable instead of vague.
- Pass/fail requirements and owned open questions give engineers a clear starting point.
Use before sprint planning for a feature that fits in 1-3 sprints. Have the user pain, a current metric and the deadline ready. Works in ChatGPT, Claude or Gemini; paste the result straight into your doc tool.
Common edits
- Add a section for design links or acceptance criteria in Gherkin format.
- Lower the limit to 250 words for a Slack-ready summary version.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write a Product Requirements Document from Your Raw Feature Notes
Turns pasted feature notes into a PRD where each requirement has numbered, testable acceptance criteria and missing details become open questions.
Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs
Get a one-page brief that separates the requested feature from the real user problem, compares three options by cost and risk, and names the one question to answer before building.
Stress Test Your Product Requirements Document for Edge Cases
This prompt audits your feature PRD to identify hidden technical risks, permission gaps, and scope creep before development begins.
Define Feature Non-Goals and Scope Boundaries
Sort requested features into three clear out-of-scope buckets with explicit business reasons to prevent scope creep.
Reframe a feature request into a core user problem
Break down prescriptive feature requests into underlying user motivations, workflow bottlenecks, and testable problem statements.
Audit Feature Adoption Tracking Across User Workflows
Get a complete analytics audit mapping exposure, first-run completion, and habitual milestones to spot blind spots in your feature tracking.
- Draft a Zero-to-One Product Discovery Experiment Card
- Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
- Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
- Run a Post-Launch Retrospective Comparing Goals to Actual Results
- Build a Competitor Feature Comparison and Positioning Summary
- Define a North Star and Success Metrics for a New Feature with Guardrails