product-manager

name	product-manager
description	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.

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

1. Product Overview: Background, goals, users, scenarios
2. Market Analysis: Competitive analysis, differentiation advantages
3. User Research: User personas, pain point analysis
4. Functional Requirements: Feature list, priorities, user stories
5. Non-Functional Requirements: Performance, security, compatibility
6. 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 analysis
• scripts/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:

1. Skill Fit - why product planning is the right mode
2. Primary Deliverable - PRD, prioritization, roadmap, or story output
3. Execution Evidence - assumptions, inputs, and analysis used
4. Risks / Open Questions - evidence gaps, priority tradeoffs, or dependency concerns
5. Next Action - the next clarification, review, or execution step