Menu
Generates comprehensive Product Requirements Document from product plan. Creates PRD.md with features, user stories, acceptance criteria, and success metrics. Use when creating product requirements.
Comprehensive iOS development guidance including Swift best practices, SwiftUI patterns, UI/UX review against HIG, and app planning. Use for iOS code review, best practices, accessibility audits, or planning new iOS apps.
Build, install, and launch an iOS app on a physical iPhone or iPad entirely from the command line (no Xcode GUI), using xcodebuild + devicectl. Use when the user wants to run, test, or screenshot their app on a real device without opening Xcode.
Build, install, launch, and screenshot an iOS app in the Simulator to verify a change visually. Use when the user wants to run the app, see a change live, screenshot the running app, or confirm a UI fix actually works (not just that it compiles).
Guides you through comprehensive iOS/Swift app planning and analysis. Use for new apps (concept to architecture) or existing apps (audit current state, plan improvements, evaluate tech stack). Covers product planning, technical decisions, UI/UX design, and distribution strategy.
Generates technical architecture specification from PRD. Covers architecture pattern, tech stack, data models, and app structure. Use when creating ARCHITECTURE.md or designing system architecture.
Generates detailed implementation guide with pseudo-code and step-by-step development instructions. Creates IMPLEMENTATION_GUIDE.md from PRD, Architecture, and UX specs. Use when creating development roadmap.
| name | prd-generator |
| description | Generates comprehensive Product Requirements Document from product plan. Creates PRD.md with features, user stories, acceptance criteria, and success metrics. Use when creating product requirements. |
| allowed-tools | ["Read","Write","Glob","Grep","AskUserQuestion"] |
Generate comprehensive Product Requirements Document from product development plan.
This skill activates when the user says:
You are a Product Manager AI agent specializing in iOS/macOS app requirements. Your job is to transform a product development plan (generated by the product-agent skill) into a comprehensive, actionable Product Requirements Document (PRD).
Before activating this skill, ensure:
Read and extract information from:
Product development plan markdown file (typically saved as product-plan-*.md)
Competitive Analysis (optional, if exists - from competitive-analysis skill)
Look for: competitive-analysis.md, docs/competitive-analysis.md, or embedded in product plan
Integration: Use competitive insights to:
Market Research (optional, if exists - from market-research skill)
Look for: market-research.md, docs/market-research.md, or embedded in product plan
Integration: Use market research to:
User clarifications (ask if needed):
Generate docs/PRD.md with the following structure:
# 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**:
```gherkin
Given [precondition]
When [action]
Then [expected result]
Given [precondition 2]
When [action 2]
Then [expected result 2]
Description: [Detailed description of what this feature does and why it's needed]
Dependencies:
Success Metrics:
Edge Cases:
[Repeat structure for each MVP feature]
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]
Goal: Help new user understand value and start using core feature
Steps:
Launch Screen
Registration (if user chooses Sign Up)
Welcome Tutorial (optional, skippable)
First Task
Success Criteria: User completes first [action] within first session
Entry Points:
Happy Path:
Alternative Paths:
Exit Points:
| 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 |
Explicitly NOT included in MVP:
Rationale: [Brief explanation of why these are out of scope]
| Service | Purpose | Alternative Considered |
|---|---|---|
| [Service name] | [What it does] | [Why this was chosen] |
Core Entities:
Relationships:
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]Note: This section is populated from competitive analysis. If not available, include basic competitor awareness.
| 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] |
Our Positioning: [How we're different - from positioning analysis]
Key Differentiators:
Note: This section is populated from market research. If not available, include high-level market awareness.
Growth Rate: [X]% CAGR
Tailwinds (positive trends):
Headwinds (challenges):
| Barrier | Level | Our Strategy |
|---|---|---|
| [Barrier 1] | Low/Med/High | [How we'll overcome] |
| [Barrier 2] | Low/Med/High | [How we'll overcome] |
Critical Decisions (block development):
Nice-to-Clarify (doesn't block): 2. [Question 2]
Launch Readiness:
User Success:
Business Success:
Acquisition:
Activation:
Engagement:
Retention:
Quality:
Phase 1: MVP Development ([X] weeks)
Phase 2: Iteration ([X] weeks after launch)
| 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] |
[Include detailed user stories that didn't fit in main sections]
Document History:
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | [Date] | [Name] | Initial PRD created |
## Execution Instructions
When activated, follow these steps:
1. **Locate and Read Product Development Plan**
Look for files matching: product-plan-*.md If multiple exist, use the most recent If none exist, ask user to provide the file path
2. **Look for Market Research and Competitive Analysis** (Optional but Recommended)
Check for competitive analysis:
Check for market research:
If found, read and incorporate these insights. If not found, proceed with product plan data only.
3. **Extract Key Information**
From the product plan, extract:
- App idea/name
- Problem statement
- Target users and personas
- Core features (from MVP scope section)
- Positioning and value proposition
- Success criteria
- Timeline estimate
From competitive analysis (if available), extract:
- Key competitors and their weaknesses
- Feature gaps (opportunities)
- Differentiation strategy
- Pricing insights
From market research (if available), extract:
- TAM/SAM/SOM figures
- Market growth rate
- Entry barriers to address
- Revenue potential for success metrics
4. **Create Output Directory**
```bash
mkdir -p docs
Generate PRD Using the template above:
Write to File
Write the complete PRD to: docs/PRD.md
Present to User After generating the PRD, present a summary:
✅ 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?
Iterate Based on Feedback If user requests changes:
When generating the PRD:
Be Specific: No generic statements like "the app should be user-friendly"
Be Actionable: Every feature should have clear acceptance criteria
Be Complete: Cover all aspects
Be Realistic: Based on MVP scope from product plan
Be Consistent: Terminology should match product plan
User: "Generate PRD from my product plan"
You:
This skill is typically:
The PRD serves as the source of truth for all downstream specifications.