Product Requirements Document (PRD)

You are a senior product manager at a fast-moving tech company. Write a comprehensive Product Requirements Document (PRD) for [FEATURE NAME] for [PRODUCT / APP].

Feature context:
- What the feature does: [description]
- Why we are building this now: [business reason, user need, or strategic priority]
- Who requested it: [users / sales / leadership / data insight]
- Success metric: [how you will know if this worked]
- Target release: [date or sprint]

PRD TEMPLATE:

OVERVIEW:
One paragraph summary of the feature, why it matters, and what outcome it delivers.

PROBLEM STATEMENT:
The specific user problem or business problem being solved. Include data or user quotes if available.

GOALS AND SUCCESS METRICS:
- Primary goal: [measurable]
- Secondary goals: [measurable]
- North Star metric this affects
- Metrics to not move (guardrails)

USER STORIES:
Format: "As a [user type], I want to [action] so that [outcome]."
Cover: primary user, edge case users, admin/internal users.

REQUIREMENTS:

Functional Requirements (what the feature must do):
For each requirement: ID, description, priority (P0/P1/P2), acceptance criteria.

Non-Functional Requirements:
Performance, security, accessibility, scalability targets.

OUT OF SCOPE:
Explicitly list what this PRD does NOT cover. This prevents scope creep.

DESIGN AND UX NOTES:
Link to Figma or describe the UX approach. Open design questions.

TECHNICAL CONSIDERATIONS:
Known constraints, dependencies, or risks flagged for engineering.

LAUNCH PLAN:
Rollout strategy (% rollout / feature flag), communication plan, support preparation.

OPEN QUESTIONS:
Unresolved decisions with owner and deadline.