Product Requirements Document
Create a comprehensive PRD for a feature that [describe feature purpose]. Structure it with these sections: Executive Summary, Problem Statement, Goals & Success Metrics, User Personas, User Journeys, Functional Requirements, Non-Functional Requirements, Technical Considerations, Dependencies, Timeline, and Rollout Strategy. For each section, provide detailed and actionable content relevant to the feature.
How to Use This Prompt
- Copy the prompt using the button above
- Replace placeholders in [brackets] with your specific details
- Paste into your AI assistant (ChatGPT, Claude, Gemini, etc.)
- Iterate as needed - ask follow-up questions to refine the output
Why This Prompt Works
This prompt mirrors the structure used by top product teams at companies like Google and Stripe, covering every essential PRD section from executive summary through rollout strategy. By requiring user personas and user journeys alongside functional and non-functional requirements, it produces a document that keeps customer needs front and center while giving engineers everything they need to build.
When to Use This Prompt
- When kicking off a new feature and need to align engineering, design, and stakeholders on scope
- When writing your first PRD and need a proven template to follow
- When refining an existing feature spec that lacks structure or is missing critical sections
Tips for Better Results
- Replace the feature description placeholder with a detailed problem statement for richer output
- Include any known technical constraints or dependencies to get more realistic requirement specifications
- Specify your target launch date and team size so the AI can suggest an appropriate timeline and scope