Generates comprehensive PRDs for new features within existing products. Guides you through defining vision, user needs, technical requirements, and success criteria before implementation begins.
Generate production-ready PRDs that provide engineers with everything they need to design and build new features. Ensures critical questions are asked systematically and answers are structured for both human review and AI consumption.
Start by understanding what problem this solves:
Get specific about how users will interact with this:
Understand how this fits with what already exists:
What are the key technical decisions:
What will users actually see and interact with:
How will we know this works:
What still needs to be resolved:
After gathering all the information above, create a comprehensive PRD with these sections:
# Feature PRD: [Feature Name]
## Vision
[The high-level vision and strategic value of this feature. Why are we building this?]
## User Need
[What user problem this solves and who benefits. Be specific about the pain point.]
## User Stories and Workflows
**Primary User Stories:**
- As a [user type], I want to [action] so that [benefit]
- As a [user type], I want to [action] so that [benefit]
**Main Workflow:**
1. [Step-by-step description of the primary user journey]
2. [Include decision points and alternate paths]
**Edge Cases:**
- [List important edge cases or alternate flows]
## Technical Requirements
**Data Model:**
[Describe database changes, new tables, field modifications, relationships]
**APIs and Endpoints:**
[List new or modified API endpoints with methods]
**Technical Approach:**
[Overall architecture and key technical decisions]
**Integration Points:**
[How this connects with existing features, systems, or external services]
**Performance Considerations:**
[Caching, background jobs, async processing, scalability concerns]
## UI/UX Requirements
**Main Screens/Views:**
[Describe the key screens or UI components]
**User Interactions:**
[Key actions users can take, form inputs, buttons, navigation]
**Design Patterns:**
[Any specific design system components or patterns to follow]
**Responsive/Mobile:**
[Mobile considerations if applicable]
## Success Criteria
**Functional Requirements:**
- [What must work for this to be considered complete]
- [Specific acceptance criteria]
**Performance Requirements:**
- [Response time, throughput, or other performance metrics]
**Quality Standards:**
- [Test coverage expectations, error handling, logging requirements]
## Open Questions
**Technical Decisions:**
- [List unresolved technical choices that need to be made]
**Dependencies:**
- [Other teams, external services, or features this depends on]
**Risks:**
- [Known risks or unknowns that need to be addressed]
**Approvals Needed:**
- [Who needs to review: design, security, compliance, etc.]
docs/features/[feature-name]/PRD.md)