/ Directorio / Playground / Product-Manager-Skills
← Todos los servidores ↗ GitHub
● Comunidad deanpeters ⚡ Instantáneo

Product-Manager-Skills

por deanpeters · deanpeters/Product-Manager-Skills

47 battle-tested PM skills covering PRDs, discovery, prioritization, roadmaps, positioning, and exec coaching — turns Claude into a credible PM partner.

A three-tier Product Management skills framework: 21 Component skills (PRD/user story/persona templates), 20 Interactive skills (guided discovery flows), and 6 Workflow skills (multi-week processes). Each SKILL.md teaches the reasoning behind frameworks so Claude doesn't just produce boilerplate — it applies the right tool for the task.

▶ Ver demo 📦 Instalar 💡 Casos de uso

Por qué usarlo

Características clave

Demo en vivo

Cómo se ve en la práctica

product-manager-skill.replay ▶ listo
0/0

Instalación

Repositorio del autor · Documentación oficial de Skills de Claude

Casos de uso

Usos del mundo real: Product-Manager-Skills

Run a customer discovery session without leading the witness

👤 PMs scoping a new feature area ⏱ ~60 min intermediate

Cuándo usarlo: You have customer calls scheduled and want a question set that actually tests assumptions.

Flujo
  1. Start the discovery interactive skill
    Use the customer-discovery skill. We're exploring expansion into SMB for our enterprise invoicing tool.✓ Copiado
    → Claude asks about target segment, hypotheses, and constraints before recommending
  2. Get the interview script
    Generate a 45-minute interview guide — warm-up, problem, context, workarounds, willingness-to-pay.✓ Copiado
    → JTBD-style script, no leading questions
  3. Synthesize after calls
    Here are my notes from 6 calls. Synthesize themes and invalidated assumptions.✓ Copiado
    → Pattern recognition grounded in notes, not wish-thinking

Resultado: Discovery notes your team can actually debate.

Errores comunes
  • Synthesis becomes confirmation bias — Ask Claude to explicitly list what was invalidated, not just validated

Draft a PRD that survives engineering review

👤 PMs writing specs for eng to build ⏱ ~45 min intermediate

Cuándo usarlo: Feature is scoped; you need a crisp doc the team can commit to.

Flujo
  1. Use the PRD component skill
    Use the prd skill. Feature: bulk-edit for our admin panel. Here's what we know [paste context].✓ Copiado
    → Structured PRD with user stories, success metrics, non-goals
  2. Pressure test
    What would a skeptical staff engineer push back on?✓ Copiado
    → Specific gaps in edge cases, data model, non-functional requirements

Resultado: A PRD that makes it through eng review without a rewrite.

Errores comunes
  • PRD is framework-perfect but lifeless — Include real customer quotes in the context
Combinar con: linear · notion

Pick the right prioritization framework for the decision at hand

👤 PMs facing a roadmap tradeoff ⏱ ~30 min intermediate

Cuándo usarlo: The team is debating what to build next and 'just rank the backlog' isn't working.

Flujo
  1. Describe the decision
    Use the prioritization-advisor skill. We're choosing between 3 bets: expand TAM, fix churn hotspot, ship a must-have for our largest deal.✓ Copiado
    → Skill recommends a specific framework (RICE/ICE/Kano/cost-of-delay) based on the situation
  2. Apply it
    Walk us through scoring each bet with that framework.✓ Copiado
    → Applied scores with reasoning

Resultado: A defensible prioritization call, not a thought-exercise.

Errores comunes
  • Score the framework picks without team buy-in — Run the scoring live in a team session, not solo

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

product-manager-skill + linear

Draft a PRD then push the stories into Linear as epics

Turn this PRD's user stories into Linear issues under epic 'Bulk Admin Edit'.✓ Copiado
product-manager-skill + notion

Store PRDs and discovery notes in a structured Notion database

Save this PRD to the Product > Specs Notion database with the right properties.✓ Copiado

Herramientas

Lo que expone este MCP

HerramientaEntradasCuándo llamarCoste
Component skills (21) feature / product context You need a specific deliverable 0
Interactive skills (20) PM decision / question You're not sure which framework applies 0
Workflow skills (6) multi-week goal Running a real team process, not a one-off 0
Leadership readiness coaching role transition question Career planning / promotion prep 0

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API
None
Tokens por llamada
2-8k per skill load
Monetario
Free — skills are local files
Consejo
Pick one skill per task; don't try to load the whole library.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: No credentials — skill is prompts
Salida de datos: None

Resolución de problemas

Errores comunes y soluciones

Interactive skill feels over-engineered for a simple task

Use the component skill (deliverable-focused) instead of the interactive one.

Output too generic — lacks product specifics

Paste in actual customer quotes, competitive context, or past retros to ground the work.

Alternativas

Product-Manager-Skills vs otros

AlternativaCuándo usarlaContrapartida
claude-skill (alirezarezvani)You want PM skills bundled with eng, marketing, and complianceBroader but less PM-specific depth
Custom PRD templatesYou've already standardized your team's templatesLess framework variety

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills