Loading...
Create a comprehensive Product Requirements Document that outlines the problem, solution, success metrics, and implementation details for a new product or feature.
# Product Requirements Document (PRD) Generator ## Problem Context Product Managers need to create detailed Product Requirements Documents (PRDs) that clearly communicate the what, why, and how of a product or feature to stakeholders, engineers, designers, and other team members. A well-structured PRD ensures alignment, reduces ambiguity, and sets clear expectations. ## Solution Pattern: Template Pattern The Template Pattern provides a structured framework for creating comprehensive PRDs. This prompt guides you through all essential sections of a PRD, ensuring nothing is missed. ## Prompt Template Act as a Product Manager's assistant. I need to create a Product Requirements Document (PRD) for [product/feature name]. Please guide me through creating a comprehensive PRD with the following sections: ### 1. Overview - **Product Name**: [Name] - **Owner**: [Your name/role] - **Stakeholders**: [List key stakeholders] - **Date**: [Date] - **Status**: [Draft/Review/Approved] ### 2. Problem Statement - What problem are we solving? - Who is affected by this problem? - What is the current state, and why is it problematic? - What evidence do we have that this problem exists? ### 3. Goals & Success Metrics - What are the primary and secondary goals? - How will we measure success? (KPIs, OKRs, metrics) - What are the target metrics and timelines? - What does "done" look like? ### 4. User Stories & Personas - Who are the target users? - Create user personas if needed - Write user stories in format: "As a [user type], I want [goal] so that [benefit]" - Prioritize user stories (Must Have, Should Have, Could Have) ### 5. Solution Overview - High-level description of the solution - Key features and functionality - What's in scope vs. out of scope - Assumptions and constraints ### 6. Functional Requirements - Detailed feature specifications - User flows and interactions - Edge cases and error handling - Dependencies on other features/systems ### 7. Non-Functional Requirements - Performance requirements - Security considerations - Scalability needs - Accessibility requirements - Browser/device compatibility ### 8. Design & UX Considerations - Wireframes or mockups (if available) - Design principles to follow - User experience guidelines - Brand guidelines ### 9. Technical Considerations - Integration points - Data requirements - API specifications (if applicable) - Technical constraints or dependencies ### 10. Go-to-Market & Launch Plan - Launch strategy - Rollout plan (phased, beta, full launch) - Marketing and communication plan - Success criteria for launch ### 11. Timeline & Milestones - Key milestones and deliverables - Dependencies - Estimated timeline - Risks and mitigation strategies ### 12. Open Questions & Decisions Needed - Questions that need answers - Decisions that need to be made - Research needed --- **Instructions:** 1. For each section, ask me clarifying questions if needed 2. Provide clear, actionable content for each section 3. Ensure the PRD is comprehensive yet concise 4. Use markdown formatting for readability 5. Include examples where helpful Once complete, format the PRD in a clean, professional document structure that I can share with stakeholders. --- *This prompt is part of the Engify.ai research-based prompt library. Customize it for your specific context and needs.*
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...
Apply what you learned with these prompts and patterns
Acts as a critical Red Team consultant to pressure-test your product strategy, identify hidden assumptions, uncover potential weaknesses, and validate market fit before presenting to executives or committing resources.
Generate comprehensive API documentation with examples and error cases
Create strategic technical roadmaps aligned with business goals