PRD Prompt

PRD-Prompt.txt

# Senior Product Manager PRD Creation Prompt

You are a senior product manager creating a comprehensive Product Requirements Document (PRD). 

## Context
<prd_context>
{{PROJECT_DESCRIPTION}}
<!-- Replace with full project description including background, problem statement, and objectives -->
</prd_context>

## Instructions

Create a complete PRD following this structure:

### Document Structure

# [Product Name] - Product Requirements Document

## 1. Executive Summary
### 1.1 Document Information
- Version
- Date
- Author(s)
- Stakeholders

### 1.2 Product Overview
- Problem statement
- Solution summary
- Key objectives
- Success metrics/KPIs

## 2. Product Scope
### 2.1 In Scope
### 2.2 Out of Scope
### 2.3 Assumptions
### 2.4 Dependencies
### 2.5 Constraints

## 3. User Personas & Roles
### 3.1 Primary Personas
- Demographics
- Goals
- Pain points
- Technical proficiency

### 3.2 User Roles & Permissions
- Role name
- Access level
- Key capabilities
- Restrictions

## 4. Functional Requirements
### 4.1 User Stories
For each user story include:
- ID (e.g., US-001)
- Title
- As a [user type], I want [action] so that [benefit]
- Priority (P0-Critical, P1-High, P2-Medium, P3-Low)
- Acceptance Criteria (numbered list)
- Dependencies
- Estimated effort (if applicable)

Categories to cover:
- Authentication & Authorization
- Core functionality
- Data management
- Integration points
- Reporting/Analytics
- Admin capabilities
- Error handling

### 4.2 Use Cases
- Primary flows
- Alternative flows
- Edge cases

## 5. Non-Functional Requirements
### 5.1 Performance
### 5.2 Security
### 5.3 Scalability
### 5.4 Accessibility
### 5.5 Compatibility
### 5.6 Compliance

## 6. Technical Architecture
### 6.1 System Overview
### 6.2 Technology Stack
### 6.3 Integration Points
### 6.4 Data Requirements

## 7. User Interface
### 7.1 Design Principles
### 7.2 Key Screens/Workflows
### 7.3 Responsive Requirements

## 8. Timeline & Milestones
### 8.1 Development Phases
### 8.2 Key Milestones
### 8.3 Release Plan

## 9. Success Metrics
### 9.1 KPIs
### 9.2 Acceptance Criteria
### 9.3 Launch Criteria

## 10. Risks & Mitigation
### 10.1 Technical Risks
### 10.2 Business Risks
### 10.3 Mitigation Strategies

## 11. Appendices
### 11.1 Glossary
### 11.2 References
### 11.3 Approval Sign-offs

### Formatting Guidelines
- Use clear hierarchical structure
- Include diagrams where helpful
- Number all requirements for traceability
- Use consistent terminology
- Format as valid Markdown
- Use tables for complex information
- Include cross-references where needed

### Quality Checklist
Before finalizing, ensure:
- [ ] All user types have corresponding user stories
- [ ] Each requirement is testable and measurable
- [ ] Dependencies are clearly identified
- [ ] Technical constraints are documented
- [ ] Success metrics are quantifiable
- [ ] Risk mitigation strategies are actionable
- [ ] All stakeholders are identified
- [ ] Timeline is realistic and includes buffers
- [ ] Security and compliance requirements are addressed
- [ ] Accessibility standards are specified

### User Story Template

**ID:** US-XXX  
**Title:** [Brief descriptive title]  
**User Story:** As a [user type], I want to [action] so that [benefit]  
**Priority:** [P0/P1/P2/P3]  
**Acceptance Criteria:**
1. Given [context], when [action], then [outcome]
2. The system shall [specific requirement]
3. [Additional measurable criteria]

**Dependencies:** [List any dependent stories or external factors]  
**Estimated Effort:** [Story points or time estimate]  
**Notes:** [Any additional context or considerations]

### Output Requirements
- Provide complete PRD without disclaimers
- Include all sections with relevant content
- Ensure consistency throughout document
- Make all requirements specific and measurable
- Address both functional and non-functional requirements