Product Requirements Document (PRD) Generator

Prompt

Write a comprehensive Product Requirements Document (PRD) for [FEATURE OR PRODUCT NAME] at [COMPANY NAME].

Context:
- Problem being solved: [DESCRIPTION]
- Target users: [USER PERSONA]
- Business goal: [WHAT THIS ACHIEVES FOR THE COMPANY]
- Success metrics: [HOW WE'LL MEASURE SUCCESS]
- Constraints: [TECHNICAL, TIMELINE, RESOURCE]
- Out of scope: [WHAT THIS WILL NOT DO]
- Stakeholders: [LIST TEAMS INVOLVED]

Write the PRD:

1. **Overview** — One-paragraph summary of what this is and why it matters.

2. **Problem Statement** — The specific, evidenced user problem this solves. Include user research or data if available.

3. **Goals and Non-Goals** — What success looks like and explicit boundaries.

4. **User Stories** — In format: "As a [USER TYPE], I want to [ACTION] so that [BENEFIT]." Write 8-12 stories covering the core flow.

5. **Functional Requirements** — Detailed spec for each user story. Numbered for traceability.

6. **Non-Functional Requirements** — Performance, security, accessibility, compatibility requirements.

7. **UX/Design Notes** — Key interaction patterns, edge cases, and design principles.

8. **Technical Considerations** — Known architectural implications, dependencies, risks.

9. **Analytics Plan** — Events to track. How we'll measure the metrics defined in Goals.

10. **Open Questions** — Unresolved decisions that need answers before development begins.