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

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

At a glancePrimary KPI: time to clear paid invoicesMedian weekly session, Pro users
ItemBaselineTarget
Median time to clear paid invoices6.5 minUnder 2 min
Accidental-archive restoresGuardrailUnder 3%
Invoice list load timeGuardrailUnder 1.5 s

Example for: bulk-archive for invoices in a small-business invoicing web app, 2 engineers, 3-week deadline.

Bulk Archive for Paid Invoices: One-Page PRD

1. Problem

Owners with 200+ invoices archive paid ones one at a time, taking up to 4 clicks each. Cluttered lists make them miss overdue invoices, and 38 support tickets last quarter asked for a faster way.

2. Users

Sole traders and small-agency owners on the Pro plan who send 20+ invoices a month and review the list weekly.

3. Primary KPI

MetricBaselineTargetMeasured by
Median time to clear paid invoices from list (weekly session)6.5 minUnder 2 minSession analytics, Pro users

Guardrails: accidental-archive restores stay under 3% of archived invoices; invoice list load time stays under 1.5 s.

4. Requirements

  1. User can select multiple invoices via checkboxes on the invoice list.
  2. "Select all paid" selects every paid invoice in the current filter.
  3. Archive action handles up to 500 invoices in one request.
  4. A confirmation shows the count before archiving.
  5. An Undo toast appears for 10 seconds after archiving.
  6. Archived invoices appear under the existing Archived filter and stay searchable.
  7. Unpaid or overdue invoices cannot be bulk-archived; the button disables with a tooltip.

5. Non-goals

  • Bulk delete or bulk edit of invoices.
  • Auto-archiving rules on a schedule.
  • Mobile app support in this release.
  • Changes to how archived invoices appear in reports.

6. Open Questions

QuestionOwnerNeeded by
Does archiving 500 invoices at once hit API rate limits?Backend leadDay 3
Should partially paid invoices count as paid?PM + Finance advisorDay 5
Do we log bulk actions in the audit trail?Engineering managerDay 5

7. Rollout

Week 1-2: build behind a feature flag. Week 3: release to 10% of Pro users, check guardrails for 5 days, then full Pro rollout.

Biggest risk: the 6.5-minute baseline comes from one month of session data and may overstate the pain; confirm before committing to the target.

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management