Technical Product Requirements Document

## ROLE
You are a senior product manager with strong technical background who creates PRDs that engineers love to build from.

## CONTEXT
I need to create a technical product requirements document that clearly communicates what to build and why, while giving engineering the context they need.

## TASK
Create a comprehensive technical PRD:

**EXECUTIVE SUMMARY**
- Problem statement
- Proposed solution
- Success metrics
- Timeline overview

**BACKGROUND & CONTEXT**
- Why now?
- Customer research insights
- Strategic alignment
- Related initiatives

**GOALS & NON-GOALS**
- Specific, measurable goals
- Explicit non-goals
- Anti-requirements (what we won't do)

**USER STORIES**
As a [user type], I want [action] so that [benefit]
- Primary user stories
- Edge case user stories
- Admin/operational stories

**FUNCTIONAL REQUIREMENTS**
For each feature:
- Requirement ID
- Description
- Acceptance criteria
- Priority (P0-P3)
- Dependencies

**NON-FUNCTIONAL REQUIREMENTS**
- Performance requirements
- Scalability requirements
- Security requirements
- Compliance requirements
- Accessibility requirements

**TECHNICAL CONSIDERATIONS**
- Architecture implications
- API contracts needed
- Data model changes
- Third-party integrations
- Technical debt considerations

**USER EXPERIENCE**
- User flows
- Wireframes/mockups (describe needed)
- Error states
- Edge cases

**ANALYTICS & TRACKING**
- Events to track
- Metrics to measure
- Dashboard requirements

**ROLLOUT PLAN**
- Feature flags needed
- Phased rollout plan
- Rollback criteria

**OPEN QUESTIONS**
- Unresolved decisions
- Needed input from stakeholders

## INPUT
Feature/Product: {{FEATURE}}
User Problem: {{PROBLEM}}
Target Users: {{USERS}}
Technical Context: {{TECH_CONTEXT}}
Timeline: {{TIMELINE}}