PRD Generator

Overview

This prompt helps product managers create a clear and strategic Product Requirements Document (PRD) with guidance from a Head of Product perspective. It provides a structured framework, covering objectives, target customer, strategic fit, key hypotheses, and solution principles, ensuring alignment with company goals. Users can customize the document by adding sections like success metrics or timelines, making it adaptable to their specific needs. This approach transforms ideas into actionable plans, driving product development success. This prompt is built for teams who need a fast, practical way to move from intention to execution.

In a delivery context, this prompt helps you align stakeholders, surface the right constraints, and structure the output so it is immediately actionable.

Prompt template

As Head of Product, I want you to approach this task with the mindset of crafting a world-class PRD. I'll provide context and insights; your role is to guide me in building a clear, actionable, and strategic PRD.

## PRD Template

### 1. Overview
- **Product name:** {{product_name}}
- **Author:** {{author}}
- **Last updated:** {{date}}
- **Status:** Draft / In Review / Approved

### 2. Problem Statement
- What problem are we solving? Why does it matter now?
- Who experiences this problem? How frequently and severely?
- What is the cost of not solving it?

### 3. Goals & Success Metrics
- **Primary objective:** One sentence describing the desired outcome
- **Key results:** 3-5 measurable success criteria with targets and timelines
- **Non-goals:** What this PRD explicitly does NOT cover

### 4. User Stories & Requirements
For each core user flow:
- **User story:** As a , I want  so that 
- **Acceptance criteria:** Given/When/Then format
- **Priority:** P0 (must-have) / P1 (should-have) / P2 (nice-to-have)

### 5. Solution Design
- High-level approach and key design decisions
- User flow diagram (describe the critical path)
- Edge cases and error states to handle

### 6. Technical Considerations
- Architecture dependencies or constraints
- API requirements and data model changes
- Performance, security, and scalability requirements

### 7. Launch Plan
- **Rollout strategy:** Big bang / phased / feature flag
- **Dependencies:** Cross-team, vendor, or infrastructure
- **Timeline:** Key milestones with dates

### 8. Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|

### 9. Open Questions
- Decisions pending stakeholder input
- Assumptions that need validation

## Additional Sections (optional)
[Add sections from your own preferred template, e.g., Success Metrics, Timeline, Risks, etc.]

## Your Input
[Feel free to input key objectives, hypotheses, ideas, and other elements related to product development.]

How to use this prompt

• State the objective and the product context in one sentence.
• Add any constraints such as timeline, target users, or business metrics.
• Ask for a structured output (framework, checklist, or decision summary).

Prompt details