Write a Product Requirements Document for {{feature_name}}.
Product Context
- Product:
{{product_name}} - Target Users:
{{target_users}} - Problem Statement:
{{problem_statement}}
PRD Structure
1. Overview
- Feature name
- One-sentence description
- Problem we're solving
- Why now?
2. Goals & Success Metrics
Primary Goal:
[Measurable outcome]
Success Metrics:
Metric Current Target Timeframe ... ... ... ...Non-Goals (explicitly out of scope):
- ...
3. User Stories
Format: "As a [user type], I want to [action] so that [benefit]"
Must Have (P0):
- ...
Should Have (P1):
- ...
Nice to Have (P2):
- ...
4. Requirements
Functional Requirements ID Requirement Priority Notes FR-1 ... P0 ... Non-Functional Requirements- Performance: ...
- Security: ...
- Accessibility: ...
- Scalability: ...
5. User Flow
Step-by-step user journey:
- User starts at...
- User clicks...
- System responds...
6. UI/UX Considerations
- Key screens/components needed
- Interaction patterns
- Mobile considerations
- Accessibility requirements
7. Technical Considerations
- Architecture impact
- API changes needed
- Data model changes
- Third-party dependencies
- Migration requirements
8. Launch Plan
- Phase 1: MVP scope
- Phase 2: Enhancements
- Rollout strategy: (% rollout, feature flags, etc.)
9. Risks & Mitigations
Risk Impact Likelihood Mitigation ... High/Med/Low High/Med/Low ...10. Open Questions
- Questions that need answers before dev
- Decisions pending stakeholder input
Variables 4
Feature Name
e.g., Team Collaboration Workspaces, Advanced Search{{feature_name}}Product Name
e.g., Promptlyb, Acme CRM{{product_name}}Target Users
e.g., Marketing teams at SMBs, Enterprise IT administrators{{target_users}}Problem Statement
e.g., Users cant easily share prompts with teammates, leading to duplicated effort{{problem_statement}}You are a senior product manager at a fast-growing tech company. Write PRDs that are comprehensive yet concise.