Product Requirements Document
Generate a comprehensive PRD for a new feature or product.
Prompt
Create a Product Requirements Document (PRD) for [feature/product name].
Include:
1. Executive Summary
- Problem statement
- Proposed solution
- Success metrics
2. Background and Context
- Why this feature is needed
- User problems it solves
- Business objectives
3. User Stories and Use Cases
- Primary user personas
- User stories (As a... I want... So that...)
- Key use cases with scenarios
4. Functional Requirements
- Core features and functionality
- User flows
- Edge cases and error handling
5. Non-Functional Requirements
- Performance requirements
- Security considerations
- Accessibility requirements
- Browser/device support
6. Design Considerations
- UI/UX requirements
- Design principles to follow
- Key design patterns to use
7. Success Metrics
- Key performance indicators (KPIs)
- How to measure success
- Baseline and target metrics
8. Timeline and Dependencies
- Phased rollout plan
- Dependencies and blockers
- Risk assessment
Format as a professional PRD document.How to use
- 1Before the prompt, write a brief context paragraph: "Our product is [X]. Target users: [Y]. This feature solves [Z problem]. Business goal: [increase/improve/reduce]."
- 2Replace [feature/product name] with your specific feature. Be descriptive: Instead of "Dashboard", write "Analytics Dashboard for Marketing Teams"
- 3If you have references: Upload screenshots of competitor features or your existing UI to AI tools that support image analysis. Say "Create a PRD for a similar feature to this"
- 4Paste the modified prompt into your preferred AI tool, like ChatGPT or Claude
- 5Review the PRD section by section. For each section, you can ask: "Expand the user stories section" or "Add more technical requirements for mobile"
- 6Copy the final PRD to Notion, Confluence, Google Docs, or your team wiki. Keep the AI chat open to make updates later
Pro Tips
- • Include existing user feedback or support tickets in your context for more grounded requirements
- • If your PM team has a PRD template: Share the template structure and ask AI to match that format
- • For technical PRDs: Specify your tech stack (e.g., "We use React and PostgreSQL") for relevant technical requirements
- • Ask "What edge cases am I missing?" to uncover scenarios you hadn't considered
- • Use follow-ups like "Create user stories in JIRA format" or "Generate acceptance criteria for each requirement"
