Our review
This skill assists product managers with core workflows: user research analysis, PRD writing, RICE prioritization, stakeholder communication, and metrics interpretation.
Strengths
- Provides structured frameworks for user research synthesis
- Applies the RICE method for data-driven feature prioritization
- Generates complete PRDs with measurable success criteria
- Tailors stakeholder communications to different audiences
Limitations
- Does not replace product intuition or business context
- Depends on quality of input data provided by the user
- May produce overly generic outputs if not carefully prompted
Use this skill when you need to analyze user feedback, prioritize features, write a PRD, or prepare product communications.
Avoid using it for strategic decisions requiring deep market knowledge or direct user validation.
Security analysis
SafeThe skill only uses read, write, and grep tools for analyzing and generating product management documents; there are no destructive commands, network access, or exfiltration risks.
No concerns found
Examples
I have three features: 'Dark mode' (reaches 5000 users/month, impact high, confidence 80%, effort 2 person-months), 'Export to PDF' (reaches 2000 users/month, impact medium, confidence 90%, effort 1 person-month), 'Real-time collaboration' (reaches 10000 users/month, impact massive, confidence 50%, effort 4 person-months). Use RICE to prioritize them and present a table with scores and reasoning.Write a PRD for a 'Saved Search' feature in a job search app. Include problem statement, success metrics, user stories, acceptance criteria, edge cases, and out-of-scope items. The problem: users repeat the same search filters daily, wasting time.Here are transcripts from 5 user interviews about our mobile app's onboarding. Identify top pain points, group by themes, and suggest 2-3 opportunity areas. Include relevant quotes.name: product-manager description: Product management: PRDs, RICE prioritization, metrics allowed-tools: Read, Write, Grep
Product Manager
Assists with core product management workflows including research synthesis, requirement documentation, feature prioritization, and strategic communication.
When to Use
- Analyzing user interviews, surveys, or feedback
- Writing or reviewing PRDs and product requirements
- Prioritizing features or roadmap items
- Preparing stakeholder updates or presentations
- Interpreting product metrics and analytics
- Conducting competitive analysis
Instructions
User Research Analysis
When analyzing user research:
- Read the provided transcripts, feedback, or survey data
- Identify the top 3-5 pain points with supporting quotes
- Group insights by themes (not by individual users)
- Prioritize by frequency AND impact
- Suggest 2-3 actionable opportunity areas
- Include specific quotes to support each finding
Feature Prioritization
When prioritizing features, use the RICE framework:
- Reach: How many users impacted per time period?
- Impact: Confidence score (0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive)
- Confidence: Data quality (0-100%)
- Effort: Person-months required
- RICE Score = (Reach × Impact × Confidence) / Effort
Present results in a table with reasoning for each score.
PRD Writing
When creating or reviewing PRDs, ensure these sections:
- Problem Statement: Clear user problem with evidence
- Success Metrics: Quantifiable measures (not "improve UX")
- User Stories: Format: "As a [user], I want [action] so that [benefit]"
- Acceptance Criteria: Testable, specific conditions
- Edge Cases: Error states, boundary conditions, empty states
- Out of Scope: What we're explicitly NOT building
Flag any missing or unclear sections.
Stakeholder Communication
When drafting communications:
- Lead with impact/outcome, not features
- Match tone to audience (C-level: business impact; Eng: technical details)
- Use specific metrics, not vague terms like "better" or "improved"
- Include next steps with owners and timelines
- Be transparent about blockers/challenges
Metrics Analysis
When analyzing metrics:
- Calculate key ratios (DAU/MAU, retention cohorts, conversion rates)
- Identify trends (week-over-week, month-over-month)
- Flag anomalies requiring investigation
- Distinguish between correlation and causation
- Provide 2-3 actionable recommendations
Quick Reference
Problem Validation Checklist:
- [ ] Problem clearly articulated?
- [ ] Validated with real users (not assumptions)?
- [ ] Frequent/painful enough to solve?
- [ ] Users will pay/engage more if solved?
- [ ] Technically feasible within constraints?
Go/No-Go Decision Criteria:
- Strategic alignment with company vision?
- Solves a validated user problem?
- Moves key metrics meaningfully?
- Team can build and maintain it?
- Strengthens competitive differentiation?
Guidelines
- Focus on outcomes (metrics moved) over outputs (features shipped)
- Validate assumptions with data before building
- Write testable, specific requirements (avoid "intuitive" or "easy to use")
- Consider edge cases: errors, empty states, loading states
- Question vanity metrics (prioritize engagement over page views)
- Be explicit about trade-offs in prioritization decisions
Automatic Triggers:
- User pastes interview transcripts or feedback
- User asks to prioritize features or compare options
- User mentions "PRD", "product requirements", or "user stories"
- User shares metrics data or analytics
- User requests stakeholder updates or presentations
Task Prioritizer
Productivity
Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.
Weekly Status Report Generator
Productivity
Generate structured and concise weekly status reports.
Daily Standup Report
Productivity
Generates structured and concise daily standup reports.