product-manager
Product Manager
Analyze user requirements, plan product features, output structured PRD documents.
Boundary With Other Skills
- Use
product-managerfor planning, prioritization, market framing, and PRD refinement. - Use
requirements-interviewfirst when requirements are unclear and need multi-round Q&A discovery. - If both are needed: run
requirements-interviewto clarify scope, then useproduct-managerto 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.
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
More from jochenyang/jochen-ai-rules
ui-ux-pro-max
UI/UX design-system reasoning and UX quality audit skill. Use when user needs style direction, palette/typography selection, UX review, or design optimization before implementation. Do NOT use for backend logic or database design.
24devops-engineer
CI/CD pipeline design, containerization, and infrastructure management. Handles Docker, Kubernetes, monitoring setup (Prometheus/Grafana), and infrastructure-as-code (Terraform/Pulumi). Use when user asks to deploy, configure CI/CD, set up Docker/K8s, or manage infrastructure.
19handoff
Create and resume structured manual session handoffs for long-running development work. Use when approaching context limits, before manual reset, before switching models or IDEs, after a milestone, or when automatic compact would lose important implementation state.
1reflect
Review current conversation, analyze tasks, errors, and user feedback, extract learning opportunities for skill improvement. Use when user says "reflect", "review session", "what did we learn", "session summary", or after completing a complex task.
1developer
Comprehensive full-stack development for web, mobile, and game projects. Handles frontend (React/Vue/Angular), backend (Node.js/Python/Go/Java), mobile (Flutter/React Native/Swift/Kotlin), and game development (Unity/Unreal/Godot). Use when user asks to build, create, develop, implement, debug, or fix any web, mobile, or game project. Do NOT use for design-only tasks (use frontend-design or ui-ux-pro-max instead).
1mcp-builder
MCP server development for AI agents. Designs tool schemas, implements Python/TypeScript servers, creates evaluation tests. Use when user asks to build MCP server, create tool integration, or develop Claude plugins. Supports GitHub/Notion/Slack integrations.
1