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.
You getSummary, goals and success metrics and users and main use cases
Prompt
Act as a senior product manager who writes PRDs that engineers and QA can build and test from.
I will paste my raw feature notes right after this prompt. Turn them into a product requirements document.
Rules:
1. Use only what is in my notes. If a detail is missing or unclear (limits, numbers, user roles, edge cases, metrics), do not guess. Add it to Open Questions.
2. Number every requirement (R1, R2, R3). Give each one 2-4 acceptance criteria numbered under it (R1.1, R1.2) in Given/When/Then form, each with a clear pass/fail result a tester could check.
3. One behavior per requirement. Start each with "The system must" or "A user can".
4. Mark each requirement Must, Should or Could.
5. Anything my notes exclude or defer goes under Out of Scope.
Output format:
1. Summary (max 3 sentences: problem, who it is for, expected outcome)
2. Goals and success metrics (only those in my notes)
3. Users and main use cases
4. Requirements: ID, requirement, priority, then numbered acceptance criteria
5. Out of scope
6. Open questions (numbered, each tagged Product, Design, Engineering or Legal)
7. Dependencies and risks
End with one line naming the biggest gap in my notes that would block engineering from starting.Example output
Tips and common edits
Why this works
- Given/When/Then criteria with pass/fail results give QA something to test instead of vague intentions.
- Banning guesses and routing gaps to tagged open questions keeps invented details out of the spec.
- The closing blocker line tells you which question to resolve first before engineering starts.
Use when you have messy meeting notes, Slack threads or a feature brief and need a buildable PRD. Paste the notes right after the prompt in ChatGPT, Claude or Gemini.
Common edits
- Ask for the requirements as a Jira-ready list with one story per requirement.
- Add a section for non-functional requirements such as performance or accessibility.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Turn a Feature Idea into User Stories with Given/When/Then Criteria
Get a backlog-ready set of single-outcome user stories with testable Given/When/Then acceptance criteria, size estimates, and flags on stories too big for one sprint.
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
Draft an Internal Launch FAQ and Enablement Brief for Sales and Support
Turns your launch notes into a sales and support brief with talk tracks, a plain-answer FAQ, objection handling, and flags for claims that need legal or engineering sign-off.
Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.
Define a North Star and Success Metrics for a New Feature with Guardrails
Get a North Star metric, up to three primary metrics each paired with a guardrail, exact formulas from your existing data, targets, and ship or roll-back rules.
Prioritize Your Feature Backlog with RICE Scoring and Flagged Weak Assumptions
Get a ranked RICE scoring table for your pasted backlog, with the math shown, weak assumptions flagged, and a short list of what to build next.