Prd Generator Skill for Claude

# Product Requirements Document: [App Name]

**Version**: 1.0.0
**Last Updated**: [Date]
**Status**: Draft / In Review / Approved
**Owner**: Product Manager
**Platform**: iOS / macOS

---

## 1. Product Overview

### 1.1 Vision Statement
[One-paragraph vision for the product - what it aspires to achieve]

### 1.2 Target Audience
**Primary**: [Detailed description of primary users]
**Secondary**: [Secondary audience if applicable]

### 1.3 Success Metrics
- [Metric 1]: [Target value]
- [Metric 2]: [Target value]
- [Metric 3]: [Target value]

---

## 2. User Personas

### 2.1 Primary Persona: [Persona Name]

**Demographics**:
- Age: [Range]
- Occupation: [Description]
- Tech savviness: [Low/Medium/High]
- Location: [Geographic focus]

**Pain Points**:
1. [Pain point 1 - be specific]
2. [Pain point 2]
3. [Pain point 3]

**Goals**:
1. [Goal 1 - what they want to achieve]
2. [Goal 2]
3. [Goal 3]

**Typical Day**:
[Brief narrative of how this persona currently addresses the problem]

**Quote**: "[A quote that captures their frustration or need]"

### 2.2 User Journey Map

**Current State** (Before using the app):
1. [Step 1 of current workflow]
2. [Step 2 - highlight pain points]
3. [Step 3]
4. [Pain point or frustration]

**Future State** (With the app):
1. [Step 1 - how the app improves it]
2. [Step 2 - benefits]
3. [Step 3 - outcomes]

---

## 3. Features & Requirements

### 3.1 Core Features (MVP - Must Have)

#### Feature 1: [Feature Name]

**Priority**: P0 (Critical)
**Complexity**: Low / Medium / High
**Estimated Effort**: [X] weeks

**User Story**:
As a [user type], I want [action], so that [benefit].

**Acceptance Criteria**:

**Description**:
[Detailed description of what this feature does and why it's needed]

**Dependencies**:
- [Dependency 1]
- [Dependency 2]

**Success Metrics**:
- [Metric 1]: [How to measure success]
- [Metric 2]: [Target value]

**Edge Cases**:
- [Edge case 1 and how to handle]
- [Edge case 2]

---

#### Feature 2: [Feature Name]

[Repeat structure for each MVP feature]

---

### 3.2 Deferred Features (Post-MVP - Phase 2)

**Feature**: [Deferred Feature Name]
**Rationale for Deferral**: [Why this is not in MVP]
**Planned for**: Version 1.1 / Phase 2

[List all deferred features with brief descriptions]

---

## 4. User Flows

### 4.1 Onboarding Flow

**Goal**: Help new user understand value and start using core feature

**Steps**:
1. **Launch Screen**
   - Show: Value proposition and hero image
   - Actions: [Sign Up] [Sign In] [Skip]

2. **Registration** (if user chooses Sign Up)
   - Required: [Email, Name, ...]
   - Optional: [Profile photo, ...]
   - Validation: [Email format, password strength]

3. **Welcome Tutorial** (optional, skippable)
   - Screen 1: [Key feature highlight]
   - Screen 2: [How to use core functionality]
   - Screen 3: [Call to action]

4. **First Task**
   - Guide user to create/do [first meaningful action]
   - Show success state

**Success Criteria**: User completes first [action] within first session

---

### 4.2 Core Feature Flow: [Feature Name]

**Entry Points**:
- From: [Screen/Action]
- Trigger: [User action or event]

**Happy Path**:
1. [Step 1] → [Result]
2. [Step 2] → [Result]
3. [Step 3] → [Success state]

**Alternative Paths**:
- If [condition]: [Alternative flow]
- If [error]: [Error handling]

**Exit Points**:
- Success: Navigate to [Screen]
- Cancel: Return to [Screen]
- Error: Show [Error message] and stay

---

### 4.3 Error States & Edge Cases

| Scenario | User Experience | System Behavior |
|----------|----------------|-----------------|
| No network connection | "Can't connect. Using offline mode." | Show cached data, queue actions |
| API timeout | "Taking longer than usual. Please wait..." | Retry with exponential backoff |
| Invalid input | "Please check [field] and try again" | Highlight invalid field, show helper text |
| Permission denied | "We need [permission] to [reason]" | Link to Settings, graceful degradation |

---

## 5. Non-Functional Requirements

### 5.1 Performance

- **Launch Time**: App cold launch < 1.5 seconds
- **Screen Load**: Screens appear < 300ms
- **API Response**: 95th percentile < 2 seconds
- **Offline Support**: Core features work offline with sync when online

### 5.2 Security & Privacy

- **Data Encryption**: All sensitive data encrypted at rest (Keychain)
- **Communication**: All API calls over HTTPS with TLS 1.2+
- **Authentication**: [Auth method - OAuth, JWT, etc.]
- **Privacy Manifest**: Complete PrivacyInfo.xcprivacy included
- **Data Retention**: [Retention policy]

### 5.3 Accessibility

- **VoiceOver**: All interactive elements have labels
- **Dynamic Type**: Support system text size (from XS to Accessibility XXL)
- **Color Contrast**: Minimum 4.5:1 for text, 3:1 for UI elements
- **Keyboard Navigation**: Full keyboard support (iPad, macOS)
- **Reduced Motion**: Respect system setting, provide alternatives

### 5.4 Localization

- **Launch Languages**: [English (US), ...]
- **Future Languages**: [Planned for Phase 2]
- **Considerations**: RTL support, date/time formats, currency

### 5.5 Platform Requirements

- **iOS Version**: Minimum iOS 26.0 (or iOS 17+ for broader device reach)
- **Devices**: iPhone (all sizes), iPad (if applicable)
- **Orientation**: Portrait (required), Landscape (optional)
- **Dark Mode**: Full support with dedicated assets
- **Size**: Target < 50MB download, < 100MB installed

---

## 6. Out of Scope

**Explicitly NOT included in MVP**:
- [Feature that was considered but excluded]
- [Integration that will come later]
- [Platform that won't be supported initially]

**Rationale**: [Brief explanation of why these are out of scope]

---

## 7. Technical Considerations

### 7.1 Third-Party Services / APIs

| Service | Purpose | Alternative Considered |
|---------|---------|----------------------|
| [Service name] | [What it does] | [Why this was chosen] |

### 7.2 Data Models (High-Level)

**Core Entities**:
- **[Entity 1]**: [Description, key fields]
- **[Entity 2]**: [Description, relationships]

**Relationships**:
- [Entity 1] has many [Entity 2]
- [Entity 3] belongs to [Entity 1]

### 7.3 API Requirements

**Endpoints Needed** (if backend required):
- `GET /api/v1/[resource]` - [Purpose]
- `POST /api/v1/[resource]` - [Purpose]
- `PUT /api/v1/[resource]/:id` - [Purpose]
- `DELETE /api/v1/[resource]/:id` - [Purpose]

---

## 8. Competitive Context

> **Note**: This section is populated from competitive analysis. If not available, include basic competitor awareness.

### 8.1 Key Competitors

| Competitor | Position | Key Strength | Key Weakness |
|------------|----------|--------------|--------------|
| [Competitor 1] | Market leader | [What they do well] | [Gap/opportunity] |
| [Competitor 2] | Challenger | [What they do well] | [Gap/opportunity] |
| [Competitor 3] | Niche | [What they do well] | [Gap/opportunity] |

### 8.2 Differentiation Strategy

**Our Positioning**: [How we're different - from positioning analysis]

**Key Differentiators**:
1. [Feature/approach competitors don't have]
2. [Unique value proposition element]
3. [Target audience we serve better]

### 8.3 Feature Gaps We're Filling

- [Gap 1]: [What competitors miss, how we address it]
- [Gap 2]: [What competitors miss, how we address it]

---

## 9. Market Context

> **Note**: This section is populated from market research. If not available, include high-level market awareness.

### 9.1 Market Sizing

- **TAM** (Total Addressable Market): [$ amount] - [Description]
- **SAM** (Serviceable Available Market): [$ amount] - [iOS/macOS segment]
- **SOM** (Serviceable Obtainable Market): [$ amount] - [Realistic 3-year capture]

### 9.2 Market Trends

**Growth Rate**: [X]% CAGR

**Tailwinds** (positive trends):
- [Trend 1 helping the market]
- [Trend 2 helping the market]

**Headwinds** (challenges):
- [Challenge 1]
- [Challenge 2]

### 9.3 Entry Barriers

| Barrier | Level | Our Strategy |
|---------|-------|--------------|
| [Barrier 1] | Low/Med/High | [How we'll overcome] |
| [Barrier 2] | Low/Med/High | [How we'll overcome] |

### 9.4 Revenue Expectations

- **Year 1 Target**: [$ range] - [User count] at [ARPU]
- **Year 3 Target**: [$ range] - Based on [growth assumptions]
- **Path to Scale**: [Key growth levers]

---

## 10. Open Questions & Decisions Needed

**Critical Decisions** (block development):
1. **[Question 1]**
   - Context: [Why this matters]
   - Options: [Option A / Option B]
   - Owner: [Who decides]
   - Deadline: [When needed]

**Nice-to-Clarify** (doesn't block):
2. **[Question 2]**
   - Context: [Background]
   - Current assumption: [What we're assuming]

---

## 11. Success Criteria & Metrics

### 11.1 MVP Success Criteria

**Launch Readiness**:
- [ ] All P0 features implemented and tested
- [ ] No P0 bugs in production
- [ ] App Store submission approved
- [ ] Performance benchmarks met

**User Success**:
- [ ] > 70% of users complete onboarding
- [ ] > 50% of users perform core action within first week
- [ ] Average session duration > 3 minutes
- [ ] < 2% crash rate

**Business Success**:
- [ ] [Download target] in first month
- [ ] [Active user target] in first 30 days
- [ ] [Retention target] Day 7 retention

### 11.2 Key Metrics to Track

**Acquisition**:
- App Store impressions → downloads conversion rate
- Organic vs paid downloads

**Activation**:
- Onboarding completion rate
- Time to first [core action]

**Engagement**:
- Daily/Weekly Active Users (DAU/WAU)
- Average session length
- Feature usage rates

**Retention**:
- Day 1, Day 7, Day 30 retention rates
- Churn rate and reasons

**Quality**:
- Crash-free rate (target: > 99.5%)
- App Store rating (target: > 4.5)
- Customer support ticket volume

---

## 12. Timeline & Milestones

**Phase 1: MVP Development** ([X] weeks)
- Week 1-2: Core infrastructure
- Week 3-4: Feature 1, Feature 2
- Week 5-6: Feature 3, Feature 4, Testing
- Week 7: Bug fixes, polish, TestFlight
- Week 8: App Store submission

**Phase 2: Iteration** ([X] weeks after launch)
- First update with deferred features
- Performance optimizations based on metrics
- User feedback incorporation

---

## 13. Stakeholders

| Role | Name | Responsibility | Contact |
|------|------|---------------|---------|
| Product Owner | [Name] | Final decisions, priorities | [Email] |
| iOS Developer | [Name] | Implementation | [Email] |
| Designer | [Name] | UI/UX | [Email] |
| QA | [Name] | Testing | [Email] |

---

## 14. References

- Product Development Plan: [Link/filename]
- Market Research: [Link/filename]
- Competitive Analysis: [Link/filename]
- Design Mockups: [Link when ready]
- Technical Architecture: [Link when ready]

---

## Appendix A: Detailed User Stories

[Include detailed user stories that didn't fit in main sections]

---

## Appendix B: Glossary

- **[Term 1]**: [Definition]
- **[Term 2]**: [Definition]

---

**Document History**:
| Version | Date | Author | Changes |
|---------|------|--------|---------|
| 1.0.0 | [Date] | [Name] | Initial PRD created |

   Look for files matching: product-plan-*.md
   If multiple exist, use the most recent
   If none exist, ask user to provide the file path

   Check for competitive analysis:
   - competitive-analysis.md
   - docs/competitive-analysis.md
   - Competitive Analysis section in product plan

   Check for market research:
   - market-research.md
   - docs/market-research.md
   - Market Analysis section in product plan

   If found, read and incorporate these insights.
   If not found, proceed with product plan data only.

   mkdir -p docs

   Write the complete PRD to: docs/PRD.md

   ✅ Product Requirements Document generated!

   📋 **PRD Summary**:
   - Document: docs/PRD.md
   - Features defined: [X] core features
   - User stories: [Y] stories with acceptance criteria
   - User flows: [Z] flows documented
   - Open questions: [N] decisions needed

   📊 **Data Sources Used**:
   - Product Development Plan: ✅
   - Competitive Analysis: [✅ Integrated / ⚠️ Not found - recommend running]
   - Market Research: [✅ Integrated / ⚠️ Not found - recommend running]

   **Next Steps**:
   1. Review the PRD in docs/PRD.md
   2. Answer open questions in Section 8
   3. Provide feedback on any features
   4. Once approved, we can proceed to architecture spec

   Would you like me to make any changes to the PRD?