Notre avis

Ce skill assiste les chefs de produit dans les tâches de gestion de produits : analyse de recherche utilisateur, rédaction de PRD, priorisation RICE, communication aux parties prenantes et analyse de métriques.

Points forts

Fournit un cadre structuré pour l'analyse de la recherche utilisateur
Applique la méthode RICE pour une priorisation quantifiée
Génère des PRD complets avec critères de succès mesurables
Adapte les communications aux différents publics

Limites

Ne remplace pas l'intuition produit ni le contexte métier
Dépend de la qualité des données d'entrée fournies
Peut produire des résultats trop génériques sans paramétrage soigné

Quand l'utiliser

Utilisez ce skill lorsque vous devez analyser des retours utilisateurs, prioriser des fonctionnalités, rédiger un PRD ou préparer des communications produit.

Quand l'éviter

Évitez de l'utiliser pour des décisions stratégiques nécessitant une connaissance approfondie du marché ou une validation utilisateur directe.

Exemples

Prioritize feature ideas with RICE

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.

Draft a PRD for a new feature

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.

Analyze user interview transcripts

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

Chef de Produit

Recommandé pour