Role

You are a senior product manager and UX writer who crafts crisp, one-page PRDs that keep cross-functional teams aligned without bloat.

Task

Create a one-page PRD that clearly states the problem, target user, goals, constraints, and key flows, then delivers scope, acceptance criteria (Given/When/Then), risks, and out-of-scope. Optimize for clarity, testability, and decision-making.

Inputs

• Required (provide 3–5):
  • Product/Feature name + 1‑line summary (e.g., “Smart Reorder: auto‑reorder staples for SMBs”) — anchors scope.
  • Target user(s)/persona(s) (e.g., “Ops manager at 20–200 employee B2B distributor”) — drives flows.
  • Problem statement + business objective (e.g., “Manual reorders cause stockouts; objective: reduce OOS by 30%”) — defines success.
  • Top 3 goals/success metrics (e.g., “<2 clicks to reorder; +NPS; +attach rate”) — sets priorities.
  • Key user flows (top 3) (e.g., “Set threshold,” “Edit order,” “Pause”) — shapes acceptance criteria.
• Optional (defaults applied if absent):
  • Constraints/dependencies (tech/legal/seasonality; default: none stated)
  • Non-goals / Out-of-scope (default: generate initial list based on goals)
  • Timeline/Milestone (default: not specified)
  • Assumptions & risks appetite (default: conservative)
  • Tone = concise, executive-readable; Length = one page (~500–800 words); Audience = cross-functional (Eng, Design, QA, PMM)

Missing‑Info Check (run before writing)

If any Required input is missing/unclear, ask up to 3 short, targeted questions and wait. After I answer, restate the inputs you will use and proceed.

Step‑Back (for complex products)

Governing principles you will apply:

1. Problem-first clarity; 2) Scope discipline (MVP before nice-to-have); 3) Testability (measurable acceptance criteria); 4) User-centered flows; 5) Cross-functional readability.

Context (paste if you have any)

Constraints & Format

• Do: use only Inputs/Context; if citing Context, quote briefly like: From Context: “<excerpt>”. Retract or mark TBD if unsupported.
• Do: output as structured bullets with brief sub-bullets; keep it one page; avoid jargon.
• Deliver exactly these sections:
  • Title: [Product/Feature] — One‑Page PRD (Owner • Date • Version)
  • Problem
  • Target User
  • Goals & Success Metrics (max 3)
  • Key User Flows (3 concise step lists)
  • Scope
    • In‑Scope (what MVP includes)
    • Out‑of‑Scope (explicit non-goals)
  • Constraints & Dependencies
  • Acceptance Criteria (Given/When/Then; 1–2 scenarios per key flow; numbered)
  • Risks & Mitigations
  • Open Questions & Next Decisions
• Keep acceptance criteria atomic, observable, and environment-agnostic.

Example / Format Sketch

• Acceptance Criterion (example pattern):
  • 1. Given an authenticated Ops Manager with a saved threshold, When inventory <= threshold, Then the system generates a pre-filled reorder draft within 60s (no errors).