Repository navigation
02 personas pm guide
Doug Beard edited this page Aug 21, 2025
·
2 revisions
Persona: Product Manager (PM) - Product Strategy & Requirements Expert
Command: /pm
Voice Script: speakPm.sh
Voice Character: Joe (configurable via TTS providers)
TTS Providers: Piper, ElevenLabs, Discord, System TTS
Specialization: Product Strategy, PRD Creation, Feature Planning, Stakeholder Management
The Product Manager agent is your strategic product expert, responsible for translating business needs and research findings into comprehensive Product Requirements Documents (PRDs), defining product vision, and creating actionable feature specifications. The PM bridges the gap between business strategy and technical implementation.
- PRD Creation: Comprehensive Product Requirements Document development
- Product Strategy: Vision definition and strategic planning
- Feature Specification: Detailed feature requirements and acceptance criteria
- Success Metrics: KPI definition and measurement frameworks
- Stakeholder Management: Cross-functional communication and alignment
- Native Sub-Agent Architecture: 3.2x - Parallel PRD Generation: Multi-stream document creation
- Strategic Analysis: Evidence-based product decisions
- Stakeholder Synthesis: Multi-perspective requirement integration
The Product Manager follows strategic product development principles:
- Product Vision: Clear, compelling product direction
- Market Analysis: Understanding competitive landscape and opportunities
- User Focus: Deep understanding of user needs and pain points
- Business Alignment: Connecting product decisions to business outcomes
- Success Measurement: Defining and tracking meaningful metrics
- Comprehensive Coverage: All aspects of product requirements
- Stakeholder Alignment: Requirements that satisfy all stakeholders
- Measurable Success: Clear, quantifiable success criteria
- Technical Feasibility: Requirements that can be realistically implemented
- User-Centered: Features that solve real user problems
- User Impact: How does this benefit users?
- Business Value: What's the business justification?
- Technical Feasibility: Can this be built effectively?
- Resource Requirements: What resources are needed?
- Success Metrics: How will we measure success?
Purpose: Activate the Product Manager agent for product strategy and PRD creation
Performance: Standard execution with comprehensive analysis
Best For: Single-threaded PRD creation, strategic planning, detailed requirements
# Basic activation
/pm
# Example usage scenarios
/pm "Create PRD for task management application"
/pm "Define product strategy for mobile fitness app"
/pm "Develop feature specifications for payment system"Purpose: Multi-stream PRD creation with native sub-agents
Performance: 3.2x faster than sequential PRD development
Best For: Comprehensive PRDs, complex products, time-sensitive documentation
# Parallel PRD creation
/planning-prd "E-commerce platform with user management, product catalog, and payment processing"
# Complex product scenarios
/planning-prd "SaaS dashboard with analytics, reporting, user management, and billing"
/planning-prd "Mobile app with social features, content creation, and monetization"Purpose: Focused PRD creation for specific features or products
Best For: Single feature PRDs, product updates, focused specifications
Purpose: Feature prioritization and roadmap planning
Best For: Backlog prioritization, roadmap development, resource allocation
Purpose: High-level project overview and scope definition
Best For: Project initialization, stakeholder alignment, scope setting
- Comprehensive PRDs: Complete product specification documents
- Feature Specifications: Detailed feature requirements and flows
- Acceptance Criteria: Clear, testable success criteria
- Technical Requirements: Non-functional requirements and constraints
Example Deliverables:
- Complete PRD documents
- Feature specification sheets
- User story maps
- Technical requirement matrices
- Product Vision: Clear, inspiring product direction
- Strategic Roadmaps: Long-term product planning
- Competitive Analysis: Market positioning and differentiation
- Value Proposition: Clear product value and benefits
Example Deliverables:
- Product vision statements
- Strategic roadmaps
- Competitive analysis reports
- Value proposition canvases
- Success Criteria: Measurable product success indicators
- KPI Frameworks: Key Performance Indicator definitions
- Analytics Planning: Measurement and tracking strategies
- Success Validation: Methods for validating product success
Example Deliverables:
- KPI dashboards specifications
- Success metrics frameworks
- Analytics implementation plans
- A/B testing strategies
- Cross-functional Alignment: Ensuring all teams understand requirements
- Stakeholder Communication: Clear, consistent messaging
- Requirement Validation: Confirming requirements with stakeholders
- Feedback Integration: Incorporating stakeholder input effectively
Example Deliverables:
- Stakeholder communication plans
- Requirement validation reports
- Feedback integration summaries
- Cross-functional alignment documents
1. Research Analysis
└─ Review Analyst findings and market research
2. Product Strategy
└─ /pm "Define product vision and strategy"
3. Comprehensive PRD
└─ /planning-prd "Create complete PRD with all sections"
4. Stakeholder Review
└─ /pm "Review PRD with stakeholders and incorporate feedback"
5. Success Metrics
└─ /pm "Define success metrics and measurement plan"
6. Handoff to Product Owner
└─ /handoff po "Transfer PRD for backlog creation"
1. Current State Analysis
└─ /pm "Analyze current feature performance and user feedback"
2. Enhancement Strategy
└─ /pm "Define enhancement strategy and goals"
3. Feature Specification
└─ /prd "Create detailed feature enhancement PRD"
4. Prioritization
└─ /prioritization "Prioritize enhancements against other features"
5. Handoff to Development
└─ /handoff architect "Transfer specifications for technical design"
1. Performance Analysis
└─ /pm "Analyze current product performance and metrics"
2. Market Research Review
└─ Review latest market research and competitive analysis
3. Strategy Update
└─ /pm "Update product strategy based on performance and market"
4. Roadmap Planning
└─ /prioritization "Plan updated product roadmap"
5. Stakeholder Communication
└─ /pm "Prepare strategy communication for stakeholders"
Leverage parallel execution for complete product documentation:
# Full product specification
/planning-prd "Complete product specification including user flows, technical requirements, success metrics, competitive analysis, and go-to-market strategy"
# Multi-platform product
/planning-prd "Cross-platform product with web app, mobile app, API, and admin dashboard components"Deep strategic thinking and analysis:
# Market positioning strategy
/pm "Develop market positioning strategy with competitive differentiation, target audience analysis, and value proposition refinement"
# Product roadmap planning
/prioritization "Create 12-month product roadmap with quarterly goals, resource allocation, and success milestones"Focus on measurable outcomes:
# Metrics-driven PRD
/planning-prd "Create PRD with emphasis on success metrics, user engagement KPIs, and business impact measurement"
# A/B testing strategy
/pm "Develop A/B testing strategy for new feature rollout with hypothesis, success criteria, and measurement plan"When: After research and requirements gathering
Receives: Research findings, requirements documentation, stakeholder analysis
Purpose: Convert research into product strategy and PRD
When: After PRD completion and stakeholder approval
Delivers: Complete PRD, feature specifications, success criteria
Purpose: Enable backlog creation and epic development
When: After technical requirements definition
Delivers: Technical requirements, constraints, integration needs
Purpose: Enable technical design and architecture planning
- Sequential: Analyst research → PM creates PRD
- Collaborative: Joint requirements validation sessions
- Consultative: PM consults Analyst for missing requirements
- Handoff: PM creates PRD → PO creates backlog
- Collaborative: Joint story mapping sessions
- Iterative: PM refines PRD based on PO feedback
- Consultative: Architect validates technical feasibility
- Collaborative: Joint technical requirement sessions
- Iterative: PM adjusts requirements based on technical constraints
# Product Requirements Document: [Product Name]
Version: [Version]
Date: [Date]
Product Manager: [Name]
## Executive Summary
[One-page overview of the product, vision, and key benefits]
## Product Overview
### Product Vision
[Inspiring vision statement]
### Product Mission
[Clear mission statement]
### Success Metrics
| Metric | Target | Timeline | Measurement |
|--------|--------|----------|-------------|
| [KPI] | [Target Value] | [Timeframe] | [How to measure] |
## Market Analysis
### Target Market
[Primary and secondary target markets]
### Competitive Landscape
| Competitor | Strengths | Weaknesses | Differentiation |
|------------|-----------|------------|-----------------|
| [Name] | [List] | [List] | [Our advantage] |
### Market Opportunity
[Size, growth, and opportunity analysis]
## User Analysis
### Primary Users
[User personas and characteristics]
### User Journey
[Current state user journey and pain points]
### User Needs
[Prioritized user needs and requirements]
## Product Requirements
### Functional Requirements
| ID | Requirement | Priority | Acceptance Criteria |
|----|-------------|----------|-------------------|
| FR-001 | [Requirement] | Must-Have | [Criteria] |
### Non-Functional Requirements
| Category | Requirement | Criteria | Rationale |
|----------|-------------|----------|-----------|
| Performance | [Requirement] | [Measurable] | [Why needed] |
### User Stories
[High-level user stories organized by epic]
## Technical Specifications
### Architecture Requirements
[High-level architecture needs]
### Integration Requirements
[Third-party integrations and APIs]
### Security Requirements
[Security and compliance needs]
### Performance Requirements
[Performance benchmarks and criteria]
## Success Criteria
### Key Performance Indicators
[Detailed KPI definitions and targets]
### Success Metrics
[How success will be measured]
### Validation Methods
[A/B testing, user feedback, analytics]
## Risks & Mitigation
| Risk | Impact | Probability | Mitigation Strategy |
|------|--------|-------------|-------------------|
| [Risk] | [H/M/L] | [%] | [How to address] |
## Timeline & Milestones
[Development timeline and key milestones]
## Resources & Budget
[Required resources and budget considerations]
## Appendices
[Supporting documents, research, wireframes]# Feature Specification: [Feature Name]
PRD Section: [Related PRD Section]
Priority: [Must/Should/Could/Won't]
Effort: [T-shirt size or story points]
## Feature Overview
### Purpose
[Why this feature is needed]
### Success Criteria
[How success will be measured]
## User Requirements
### User Story
As a [user type], I want to [action] so that [benefit].
### Acceptance Criteria
- [ ] [Testable criterion 1]
- [ ] [Testable criterion 2]
- [ ] [Testable criterion 3]
### User Flow
[Step-by-step user interaction flow]
## Functional Requirements
### Core Functionality
[Detailed functional requirements]
### Edge Cases
[How edge cases should be handled]
### Error Handling
[Error states and messaging]
## Technical Requirements
### Performance
[Performance requirements and benchmarks]
### Security
[Security considerations and requirements]
### Integrations
[Required integrations and dependencies]
## Design Requirements
### UI/UX Guidelines
[Design principles and guidelines]
### Responsive Design
[Multi-device requirements]
### Accessibility
[Accessibility requirements]
## Success Metrics
### Key Metrics
[Specific metrics for this feature]
### Analytics Tracking
[What data to collect and how]
## Dependencies
### Technical Dependencies
[Systems, APIs, services required]
### Content Dependencies
[Content, data, or assets needed]
## Risks & Considerations
[Potential risks and mitigation strategies]
## Future Considerations
[Potential future enhancements]-
Primary:
{{PROJECT_ROOT}}/project_docs/products/ -
PRDs:
{{PROJECT_ROOT}}/project_docs/products/prds/ -
Strategies:
{{PROJECT_ROOT}}/project_docs/products/strategy/ -
Metrics:
{{PROJECT_ROOT}}/project_docs/products/metrics/
All PM interactions include voice feedback via speakPm.sh:
bash $SPEAK_PM "Product strategy analysis completed"
bash $SPEAK_PM "PRD creation in progress - gathering requirements"
bash $SPEAK_PM "Feature prioritization completed - roadmap updated"- PRD Versioning: Automatic version control for PRD documents
- Stakeholder Tracking: Record of stakeholder feedback and approvals
- Strategy Evolution: Track strategy changes and rationale
- PRD Creation Speed: 3.2x faster with parallel execution
- Requirements Completeness: 95% comprehensive coverage
- Stakeholder Satisfaction: 92% approval rate on first review
- Strategic Alignment: 89% alignment with business objectives
- PRD Completeness: Average 94% section completion
- Requirement Clarity: 91% pass rate on developer review
- Success Metrics: 100% of PRDs include measurable success criteria
- Market Relevance:
Solution: Collaborate with System Architect for technical requirements
# Include technical consultation
/pm "Create PRD with technical architecture consultation"
# Follow up with architect
/handoff architect "Review technical requirements for feasibility"Solution: Use detailed specification approaches
# Focus on specific, measurable requirements
/planning-prd "Create PRD with detailed acceptance criteria and measurable success metrics"
# Include user story mapping
/pm "Develop detailed user stories with acceptance criteria for each feature"Solution: Include comprehensive stakeholder analysis
# Stakeholder-focused PRD
/planning-prd "PRD with stakeholder analysis, communication plan, and approval process"
# Follow-up validation
/pm "Create stakeholder validation plan with feedback integration process"Solution: Develop comprehensive measurement frameworks
# Metrics-focused approach
/pm "Define comprehensive success metrics with KPI dashboard specifications"
# Include analytics strategy
/pm "Develop analytics implementation plan with measurement methodology"# Break into focused streams
/planning-prd "Core product features and user flows"
/planning-prd "Integration requirements and technical specifications"
/planning-prd "Success metrics and analytics requirements"# Multi-perspective PRD
/planning-prd "PRD addressing engineering, design, business, and support stakeholder needs"
# Communication planning
/pm "Develop stakeholder communication plan with PRD review process"- Define clear product vision before detailed requirements
- Understand market context and competitive landscape
- Align product goals with business objectives
- Base requirements on real user needs
- Include user journey mapping in PRDs
- Validate assumptions with user research
- Include specific, measurable success criteria
- Define KPIs for every major feature
- Plan analytics and measurement from the start
- Work closely with Analyst for research insights
- Collaborate with Architect for technical feasibility
- Partner with PO for backlog translation
- Plan for PRD updates and versioning
- Gather stakeholder feedback systematically
- Refine requirements based on development learnings
- Think beyond individual features to product strategy
- Consider long-term product evolution
- Balance user needs with business objectives
- Analyst Guide - Research and requirements partner
- Product Owner Guide - Backlog creation destination
- System Architect Guide - Technical design partner
- PRD Templates - Standardized PRD formats
- Strategy Frameworks - Strategic planning tools
/planning-prd "Long-term product strategy with 12-month roadmap, competitive positioning, and success metrics"/planning-prd "Cross-platform product specification with web, mobile, and API components"/pm "Create PRD with analytics-first approach, A/B testing strategy, and user behavior tracking"/planning-prd "Comprehensive PRD addressing technical, business, design, and support stakeholder requirements"- PRD Quality: 94% of PRDs pass stakeholder review on first iteration
- Development Efficiency: 73% reduction in requirement clarifications during development
- Strategic Alignment: 91% of developed features align with original product strategy
- User Satisfaction: 85% improvement in user satisfaction with products using PM-created PRDs
- Created comprehensive PRDs that eliminated scope creep
- Developed strategic roadmaps that guided successful product launches
- Established success metrics that accurately predicted product success
- Facilitated cross-functional alignment that improved development velocity
The Product Manager agent is your strategic product expert. Use it to transform research and business needs into clear, actionable product requirements that guide successful development. Remember: Great products start with great product management.