Create comprehensive Product Requirements Documents (PRD) from high-level product ideas with structured market analysis, feature definition, and success metrics for both greenfield and brownfield contexts. Use when defining product vision for new projects (greenfield) or formalizing requirements for existing systems (brownfield).
Create comprehensive Product Requirements Documents (PRD) from high-level product ideas with structured market analysis, feature definition, and success metrics for both greenfield and brownfield contexts. Use when defining product vision for new projects (greenfield) or formalizing requirements for existing systems (brownfield).
acceptance
[{"prd_complete":"PRD document created with all required sections"},{"features_prioritized":"Features prioritized using MoSCoW method (Must/Should/Could/Won't)"},{"success_metrics_defined":"Success criteria and KPIs clearly defined"},{"user_personas_documented":"Target users and personas identified"},{"ready_for_architecture":"PRD ready for architecture phase or epic breakdown"}]
inputs
{"product_name":{"type":"string","required":true,"description":"Name of the product or feature"},"product_vision":{"type":"string","required":true,"description":"High-level vision and value proposition"},"problem_statement":{"type":"string","required":true,"description":"Problem this product solves"},"target_users":{"type":"string","required":false,"description":"Target user personas or segments"},"business_objectives":{"type":"string","required":false,"description":"Business goals and objectives"},"success_metrics":{"type":"string","required":false,"description":"Initial success metrics or KPIs"},"competitive_landscape":{"type":"string","required":false,"description":"Competitive context and differentiation"},"project_type":{"type":"string","required":false,"description":"greenfield (new) or brownfield (existing system). Defaults to greenfield.","default":"greenfield"}}
outputs
{"prd_created":{"type":"boolean","description":"Whether PRD was successfully created"},"prd_location":{"type":"string","description":"File path to created PRD (e.g., docs/prd.md or workspace/prds/{product-name}-prd.md)"},"feature_count":{"type":"number","description":"Number of features identified and prioritized"},"persona_count":{"type":"number","description":"Number of user personas documented"}}
Create comprehensive Product Requirements Documents (PRD) from high-level product ideas. This skill guides systematic requirements gathering, market analysis, feature definition, and success metrics documentation to produce PRDs ready for architecture design or epic breakdown.
Core Principles:
Structured requirements elicitation
Market-driven feature prioritization
Clear success metrics and KPIs
User-centric design approach
Supports both greenfield (new products) and brownfield (existing systems) contexts
Prerequisites
Product vision or initial concept defined
Access to stakeholder input (if available)
Understanding of target market and users
workspace/ directory exists for PRD storage
Workflow
Step 1: Requirements Gathering
Action: Elicit product vision, objectives, and constraints through structured inquiry.
Key Activities:
Product Vision & Value Proposition
What problem does this solve?
What value does it provide to users?
What makes it unique or different?
Target Users & Personas
Who are the primary users?
What are their goals, needs, pain points?
What user segments exist?
Business Objectives
What are the business goals?
How does this align with strategy?
What's the expected ROI or impact?
Constraints & Considerations
Timeline constraints
Budget limitations
Technical constraints
Regulatory requirements
Team capabilities
Example Questions:
- "What problem are we solving for users?"
- "How will users discover and access this?"
- "What success looks like in 6 months?"
- "What are we explicitly NOT building?"
See:references/market-analysis-template.md for detailed framework
Step 3: Feature Definition
Action: Define and prioritize features using MoSCoW method.
Key Activities:
Identify Core Features
What must the product do? (Must-haves)
What should it do? (Should-haves)
What could it do? (Could-haves)
What won't it do? (Won't-haves)
Feature Specifications
Brief description of each feature
User value/benefit
Dependencies between features
Technical complexity estimate (if known)
MoSCoW Prioritization
Must Have: Critical features, MVP blockers
Should Have: Important but not launch blockers
Could Have: Nice-to-haves, future enhancements
Won't Have: Explicitly out of scope
Feature Validation
Does each feature solve user problem?
Is each feature aligned with objectives?
Are must-haves achievable within constraints?
Example Feature Definition:
MUST HAVE (MVP):
1. User Registration & Login
- Users can create accounts with email/password
- Enables personalization and data security
- Depends on: Database, authentication service
2. Dashboard Overview
- Users see key metrics at a glance
- Provides immediate value on login
- Depends on: Data collection, visualization
SHOULD HAVE:
3. Advanced Filtering
- Users can filter data by multiple criteria
- Improves data discovery
- Depends on: Dashboard, search infrastructure
COULD HAVE:
4. Data Export (CSV, PDF)
- Users can export reports
- Convenience feature, not core value
- Depends on: Dashboard, report generation
WON'T HAVE (v1):
5. Real-time Collaboration
- Out of scope for v1, planned for v2
- Significant technical complexity
Output: Prioritized feature list with specifications
See:references/moscow-prioritization-guide.md for detailed prioritization framework
Step 4: Success Metrics
Action: Define measurable success criteria and KPIs.
Key Activities:
User Adoption Metrics
Sign-ups, active users (DAU/MAU/WAU)
User retention (D1, D7, D30 retention)
User engagement (sessions, time-on-site)
Feature adoption rates
Business Impact Metrics
Revenue (if applicable)
Conversion rates
Cost savings
Market share
Customer satisfaction (NPS, CSAT)
Technical Performance Metrics
Page load time
API response time
Uptime/availability
Error rates
Scalability metrics
Success Criteria
Specific targets for each metric
Timeframes for achievement
How metrics will be measured
Baseline vs target values
Example Success Metrics:
USER ADOPTION:
- 1,000 sign-ups in first month
- 60% D7 retention
- 40% MAU engagement
BUSINESS IMPACT:
- 70% conversion rate (free → paid)
- NPS score >40
- $100K ARR by month 6
TECHNICAL PERFORMANCE:
- <2s page load time (p95)
- 99.9% uptime SLA
- <1% error rate
Output: Success metrics and KPIs documented
See:references/success-metrics-framework.md for comprehensive metrics catalog
Step 5: PRD Document Generation
Action: Compile all gathered information into comprehensive PRD document.
Document Structure:
Executive Summary
Product overview (1-2 paragraphs)
Problem statement
Value proposition
Target users
Product Vision & Objectives
Vision statement
Business objectives
Success criteria
User Personas & Stories
Persona definitions
User journeys
Key use cases
Market Analysis
Competitive landscape
Market positioning
Differentiation strategy
Feature Specifications
Prioritized feature list (MoSCoW)
Feature descriptions and user value
Dependencies and relationships
User Flows & Journeys
Key user flows
Entry points and conversions
Edge cases
Non-Functional Requirements
Performance requirements
Security requirements
Scalability requirements
Accessibility requirements
Success Metrics & KPIs
Adoption metrics
Business impact metrics
Technical metrics
Success criteria with targets
Timeline & Milestones
High-level roadmap
Key milestones
Launch criteria
Assumptions & Constraints
Technical assumptions
Business assumptions
Known constraints
Dependencies
Open Questions & Risks
Unresolved questions
Identified risks
Mitigation strategies
File Location:
Greenfield: docs/prd.md or workspace/prds/{product-name}-prd.md
