Work & business

PRD from idea

Use this when the idea is too early for specs but ready for structured product thinking.

Before you start

  • Rough feature or product idea
  • Target user or customer
  • Business or user goal
  • Known constraints
Focus on one step at a time
8 min active prompt time

Frame the problem

Separate the user problem from the proposed solution before the PRD takes shape.

Inline prompt text

Problem framing

problem-frame-prompt.md70 tokens · 0.3 KB
You are a senior product manager. Frame this product idea as a problem statement. Inputs: - Idea: - Target user: - User pain: - Business goal: - Constraints: Return: - Problem statement - Target user - Current workaround - Desired outcome - Why now - Assumptions to validate

Deliverables

  • Problem statement
  • Assumption list

Tips

  • Do not let the solution define the problem.
  • Call out assumptions early.
8 min active prompt time

Write user scenarios

Define the main flows before listing requirements.

Inline prompt text

User scenarios

user-scenarios-prompt.md62 tokens · 0.2 KB
Create user scenarios for this product idea. Inputs: - Problem statement: - Target user: - Desired outcome: Return: - 3 primary user scenarios - Trigger for each scenario - User goal - Happy path - Failure or edge case - What success looks like

Deliverables

  • Primary scenarios
  • Edge cases

Tips

  • Use scenarios to keep requirements grounded.
  • Include at least one failure case.
10 min active prompt time

Draft requirements

Convert scenarios into clear requirements and non-goals.

Inline prompt text

PRD requirements

requirements-prompt.md65 tokens · 0.3 KB
Turn these scenarios into PRD requirements. Return: - Functional requirements - Non-functional requirements - Non-goals - Open questions - Acceptance criteria Rules: - Keep requirements testable - Avoid implementation details unless they are true constraints

Deliverables

  • Requirements
  • Acceptance criteria
  • Non-goals

Tips

  • Make each requirement testable.
  • Write non-goals to protect scope.
8 min active prompt time

Find risks and tradeoffs

Stress-test the PRD before it reaches design or engineering.

Inline prompt text

PRD risk review

prd-risks-prompt.md47 tokens · 0.2 KB
Review this PRD draft for risks. Return: - Product risks - UX risks - Engineering risks - Measurement risks - Decisions that need owner input - Suggested scope cuts if timeline is tight

Deliverables

  • Risk list
  • Decision list
  • Scope cuts

Tips

  • Ask for tradeoffs, not only improvements.
  • Use this before estimating effort.
6 min quick pass

Prepare the handoff

Package the PRD into a short handoff note that people will read.

Inline prompt text

PRD handoff note

prd-handoff-prompt.md41 tokens · 0.2 KB
Create a concise handoff note from this PRD. Return: - Summary - User problem - Proposed solution - Requirements - Key risks - Open questions - Next meeting agenda

Deliverables

  • Handoff note
  • Meeting agenda

Tips

  • Keep the handoff shorter than the PRD.
  • Put open questions near the top.