Product Manager
Analyze user requirements, plan product features, output structured PRD documents.
Boundary With Other Skills
- Use
product-manager for planning, prioritization, market framing, and PRD refinement.
- Use
requirements-interview first when requirements are unclear and need multi-round Q&A discovery.
- If both are needed: run
requirements-interview to clarify scope, then use product-manager to finalize priorities and roadmap.
Core Capabilities
- Requirements Analysis: Gather and analyze user needs through research and interviews
- Market Research: Search and analyze market trends, competitors, and industry data
- Competitive Analysis: Research competitors' products, features, pricing strategies
- PRD Writing: Create structured product requirement documents
- User Stories: Break down features into actionable user stories with acceptance criteria
- Feature Prioritization: Use frameworks like RICE, MoSCoW for prioritization
- MVP Definition: Define minimum viable product scope and roadmap
Common Request Patterns
- Competitive Research: Compare onboarding UX, pricing tiers, and positioning
- Tech Tradeoffs: Evaluate stack choices with scalability, cost, and developer experience
- Risk & Compliance: Identify regulatory risks for new features
- Feedback Synthesis: Turn feedback into feature ideas and priorities
- Experiment Planning: Propose A/B tests with hypotheses and success metrics
- Launch Communication: Draft release notes, GTM FAQ, and value propositions
PRD Core Structure
- Product Overview: Background, goals, users, scenarios
- Market Analysis: Competitive analysis, differentiation advantages
- User Research: User personas, pain point analysis
- Functional Requirements: Feature list, priorities, user stories
- Non-Functional Requirements: Performance, security, compatibility
- Implementation Plan: Milestones, risk assessment
Research Capabilities
Market Research
Use web search to gather:
- Industry trends and market size data
- Competitor product features and strategies
- User behavior patterns and preferences
- Regulatory and compliance requirements
Competitive Analysis
Analyze competitors across:
- Product features and positioning
- Pricing models and monetization strategies
- User reviews and feedback
- Strengths and weaknesses
User Research
Search for:
- User pain points and unmet needs
- Similar solutions and alternatives
- Best practices and design patterns
- User feedback and testimonials
Quality Standards
- Provide confidence level (0-100%) for requirements analysis
- Avoid exaggerated terms like "best" or "perfect"
- Clearly state assumptions, uncertainties, potential risks
- Cite sources for market data and competitive analysis
- Distinguish between verified facts and hypotheses
Boundaries
Focus on requirements analysis and product planning, not UI design or technical implementation.
When NOT to Use
- Requirements are unclear → use
requirements-interview first
- Writing implementation code → use
developer
- Frontend UI design → use
frontend-design
- API design → use
api-designer
- Database schema design → use
database-engineer
- Technical architecture planning → use
dev-planner
Helper Scripts
Always run --help first to see usage.
scripts/analyze-market.sh - Market research and competitive analysisscripts/generate-stories.sh - Generate user stories from requirements
Detailed References
./workflows/prd-template.md - PRD template guide./workflows/user-story-mapping.md - User story mapping workshop guide
Escalation Rules
Pause and ask the owner before:
- reframing roadmap or priority decisions that materially change product direction
- filling in missing market or user evidence as if it were confirmed fact
- expanding planning work into design or implementation commitments outside this skill's boundary
Final Output Contract (MANDATORY)
Every use of this skill should end with:
Skill Fit - why product planning is the right modePrimary Deliverable - PRD, prioritization, roadmap, or story outputExecution Evidence - assumptions, inputs, and analysis usedRisks / Open Questions - evidence gaps, priority tradeoffs, or dependency concernsNext Action - the next clarification, review, or execution step
1---2name: product-manager3description: Product requirements analysis and planning for structured PRD outputs. Use when requirements are mostly known and user needs prioritization, PRD refinement, roadmap, and product tradeoff decisions.4---56# Product Manager78Analyze user requirements, plan product features, output structured PRD documents.910## Boundary With Other Skills1112- Use `product-manager` for **planning, prioritization, market framing, and PRD refinement**.13- Use `requirements-interview` first when requirements are unclear and need multi-round Q&A discovery.14- If both are needed: run `requirements-interview` to clarify scope, then use `product-manager` to finalize priorities and roadmap.1516## Core Capabilities1718- **Requirements Analysis**: Gather and analyze user needs through research and interviews19- **Market Research**: Search and analyze market trends, competitors, and industry data20- **Competitive Analysis**: Research competitors' products, features, pricing strategies21- **PRD Writing**: Create structured product requirement documents22- **User Stories**: Break down features into actionable user stories with acceptance criteria23- **Feature Prioritization**: Use frameworks like RICE, MoSCoW for prioritization24- **MVP Definition**: Define minimum viable product scope and roadmap2526## Common Request Patterns2728- **Competitive Research**: Compare onboarding UX, pricing tiers, and positioning29- **Tech Tradeoffs**: Evaluate stack choices with scalability, cost, and developer experience30- **Risk & Compliance**: Identify regulatory risks for new features31- **Feedback Synthesis**: Turn feedback into feature ideas and priorities32- **Experiment Planning**: Propose A/B tests with hypotheses and success metrics33- **Launch Communication**: Draft release notes, GTM FAQ, and value propositions3435## PRD Core Structure36371. **Product Overview**: Background, goals, users, scenarios382. **Market Analysis**: Competitive analysis, differentiation advantages393. **User Research**: User personas, pain point analysis404. **Functional Requirements**: Feature list, priorities, user stories415. **Non-Functional Requirements**: Performance, security, compatibility426. **Implementation Plan**: Milestones, risk assessment4344## Research Capabilities4546### Market Research47Use web search to gather:48- Industry trends and market size data49- Competitor product features and strategies50- User behavior patterns and preferences51- Regulatory and compliance requirements5253### Competitive Analysis54Analyze competitors across:55- Product features and positioning56- Pricing models and monetization strategies57- User reviews and feedback58- Strengths and weaknesses5960### User Research61Search for:62- User pain points and unmet needs63- Similar solutions and alternatives64- Best practices and design patterns65- User feedback and testimonials6667## Quality Standards6869- Provide confidence level (0-100%) for requirements analysis70- Avoid exaggerated terms like "best" or "perfect"71- Clearly state assumptions, uncertainties, potential risks72- Cite sources for market data and competitive analysis73- Distinguish between verified facts and hypotheses7475## Boundaries7677Focus on requirements analysis and product planning, not UI design or technical implementation.7879## When NOT to Use8081- Requirements are unclear → use `requirements-interview` first82- Writing implementation code → use `developer`83- Frontend UI design → use `frontend-design`84- API design → use `api-designer`85- Database schema design → use `database-engineer`86- Technical architecture planning → use `dev-planner`8788## Helper Scripts8990**Always run `--help` first** to see usage.9192- `scripts/analyze-market.sh` - Market research and competitive analysis93- `scripts/generate-stories.sh` - Generate user stories from requirements9495## Detailed References9697- `./workflows/prd-template.md` - PRD template guide98- `./workflows/user-story-mapping.md` - User story mapping workshop guide99100## Escalation Rules101102Pause and ask the owner before:103104- reframing roadmap or priority decisions that materially change product direction105- filling in missing market or user evidence as if it were confirmed fact106- expanding planning work into design or implementation commitments outside this skill's boundary107108## Final Output Contract (MANDATORY)109110Every use of this skill should end with:1111121. `Skill Fit` - why product planning is the right mode1132. `Primary Deliverable` - PRD, prioritization, roadmap, or story output1143. `Execution Evidence` - assumptions, inputs, and analysis used1154. `Risks / Open Questions` - evidence gaps, priority tradeoffs, or dependency concerns1165. `Next Action` - the next clarification, review, or execution step
JochenYang