UX & Product DesignPromptFree
Cross-Functional Feature PRD Drafter
Drafts a lean product requirements doc tying user problem, scope, UX flow, success metrics, and open questions together.
ROLE: You are a product designer-PM who writes lean PRDs that align design, engineering, and stakeholders fast.
CONTEXT: Feature: [FEATURE_NAME] for [PRODUCT]. The user problem and evidence: [PROBLEM_AND_EVIDENCE]. Target users: [USERS]. Business objective it serves: [OBJECTIVE]. Known constraints (tech, timeline, legal): [CONSTRAINTS].
TASK: Draft a one-page-style PRD.
1. Write the problem statement and who has it, backed by the evidence — not a solution in disguise.
2. State the goal and the measurable success metrics (and a guardrail metric).
3. Define scope: what is in v1, what is explicitly out, and why.
4. Describe the core user flow in plain steps and the key states/edge cases that must be handled.
5. List functional requirements as testable statements ('The system must...').
6. Capture dependencies, risks, and the top open questions blocking a confident build.
7. Define the rollout approach (flag, phased, full) and how we will learn post-launch.
OUTPUT FORMAT: Sections — TL;DR | Problem & Evidence | Goals & Metrics | Scope (In/Out) | User Flow | Requirements (testable list) | Risks & Dependencies | Open Questions | Rollout. Lead with a 2-sentence TL;DR.
CONSTRAINTS: Problem before solution — do not smuggle the solution into the problem statement. Every requirement must be testable. Make 'out of scope' explicit. Surface open questions rather than papering over them. Keep it lean and skimmable.- Built from
- Role
- Context
- Task
- Output format
- Constraints
How to use it
- Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer. The Studio lists the blanks for you and can add your project's background.
- Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
- Not sure what it produces? Give it a test run in the Studio first, then refine with self-critique prompting.
Techniques in this prompt
Role-Based
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueStructured Output
Pins the response to a defined structure so it drops straight into your workflow.
Learn this techniqueStep-by-Step
Forces explicit intermediate reasoning instead of jumping to a conclusion, which improves accuracy on hard tasks.
Learn this techniqueWorks with
Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.
New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.