Prompt pack4 steps11 prompts
Write a PRD / Product Spec
Use this when the bet is chosen and you need a spec people can build from. Problem and user first, then requirements and cuts, then how you will know it worked.
01Problem and user
One problem, why now, who feels it, what they do today. Align on that before requirements.
- ProductProblem Statement FrameworkCreate clear, actionable problem statements that align teams and drive focused solutions.
- ProductAmazon PR/FAQ (Working Backwards)Create an Amazon-style PR/FAQ document using the Working Backwards framework for product innovation.
- UX designUser Journey MappingCreate detailed user journey maps with touchpoints, emotions, and opportunities.
- ResearchMixed-Source Research SynthesisCombine already-coded interviews, surveys, and analytics into one report. For a single session use Session Debrief From Transcript. To cluster interview notes, use Affinity Mapping Assistant, then Research Insight Statement Writer.
02Requirements and scope
Stories, must vs nice, and an explicit out-of-scope list. Get engineering on constraints before you decorate.
- ProductProject Scope DefinitionDefine clear project scope with explicit in/out boundaries and assumptions.
- ProductUser Story WritingWrite effective user stories with clear acceptance criteria, personas, and value statements.
- ProductFeature Prioritization MatrixPrioritize product features using structured frameworks like RICE, Value vs. Effort, or Kano Model.
03Metrics and UX
How you will know it worked, plus the UX requirements that are not “make it nice.” Empty, error, and success states belong here.
- ProductSMART Goal CreatorTurn a vague objective into clear goals using the SMART framework: Specific (clear outcome and scope), Measurable (metrics or observable signals), Achievable (realistic given constraints), Relevant (aligned to user or business value), and Time-bound (deadline or milestones). Includes success criteria and checkpoints.
- ProductAcceptance Criteria GeneratorGenerate comprehensive, testable acceptance criteria for user stories and features.
04Review
Walk the spec. Capture launch criteria that are actually gates. Then hand off; do not keep rewriting in Slack.
Frequently asked questions
Do I need this after a design sprint?
If you are building, yes. The sprint shareout is evidence. The PRD is the contract.
We are still discovering the problem. Write a PRD anyway?
No. Run a research study or a sprint. A spec written to look busy will be rewritten after the first customer conversation.
How short can it be?
Short enough that engineering can build without Slack archaeology. Problem, who, in/out, success metric. If that fits in two pages, stop.