/ Annuaire / Playground / Product-Manager-Skills
● Communauté deanpeters ⚡ Instantané

Product-Manager-Skills

par 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.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

product-manager-skill.replay ▶ prêt
0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "product-manager-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/deanpeters/Product-Manager-Skills",
        "~/.claude/skills/Product-Manager-Skills"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "product-manager-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/deanpeters/Product-Manager-Skills",
        "~/.claude/skills/Product-Manager-Skills"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "product-manager-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/deanpeters/Product-Manager-Skills",
        "~/.claude/skills/Product-Manager-Skills"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "product-manager-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/deanpeters/Product-Manager-Skills",
        "~/.claude/skills/Product-Manager-Skills"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "product-manager-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/deanpeters/Product-Manager-Skills",
        "~/.claude/skills/Product-Manager-Skills"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json
{
  "context_servers": {
    "product-manager-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/deanpeters/Product-Manager-Skills",
          "~/.claude/skills/Product-Manager-Skills"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add product-manager-skill -- git clone https://github.com/deanpeters/Product-Manager-Skills ~/.claude/skills/Product-Manager-Skills

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : Product-Manager-Skills

Run a customer discovery session without leading the witness

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

Quand l'utiliser : You have customer calls scheduled and want a question set that actually tests assumptions.

Déroulement
  1. Start the discovery interactive skill
    Use the customer-discovery skill. We're exploring expansion into SMB for our enterprise invoicing tool.✓ Copié
    → 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.✓ Copié
    → JTBD-style script, no leading questions
  3. Synthesize after calls
    Here are my notes from 6 calls. Synthesize themes and invalidated assumptions.✓ Copié
    → Pattern recognition grounded in notes, not wish-thinking

Résultat : Discovery notes your team can actually debate.

Pièges
  • 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

Quand l'utiliser : Feature is scoped; you need a crisp doc the team can commit to.

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

Résultat : A PRD that makes it through eng review without a rewrite.

Pièges
  • PRD is framework-perfect but lifeless — Include real customer quotes in the context
Combiner avec : linear · notion

Pick the right prioritization framework for the decision at hand

👤 PMs facing a roadmap tradeoff ⏱ ~30 min intermediate

Quand l'utiliser : The team is debating what to build next and 'just rank the backlog' isn't working.

Déroulement
  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.✓ Copié
    → 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.✓ Copié
    → Applied scores with reasoning

Résultat : A defensible prioritization call, not a thought-exercise.

Pièges
  • Score the framework picks without team buy-in — Run the scoring live in a team session, not solo

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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'.✓ Copié
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.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
2-8k per skill load
Monétaire
Free — skills are local files
Astuce
Pick one skill per task; don't try to load the whole library.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials — skill is prompts
Sortie de données : None

Dépannage

Erreurs courantes et correctifs

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.

Alternatives

Product-Manager-Skills vs autres

AlternativeQuand l'utiliserCompromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills