Product-Manager-Skills

Why use it

Key features

47 PM skills across components, interactive flows, and multi-day workflows
Covers strategy, discovery, prioritization, PRDs, positioning, pricing, roadmapping
Interactive skills ask adaptive questions before recommending frameworks
Director and VP/CPO readiness coaching flows
Pedagogic SKILL.md structure: purpose → key concepts → application → pitfalls

Live Demo

What it looks like in practice

product-manager-skill.replay ▶ ready

0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use Product-Manager-Skills

Run a customer discovery session without leading the witness

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

When to use: You have customer calls scheduled and want a question set that actually tests assumptions.

Flow

Start the discovery interactive skill

Use the customer-discovery skill. We're exploring expansion into SMB for our enterprise invoicing tool.✓ Copied

→ Claude asks about target segment, hypotheses, and constraints before recommending
Get the interview script

Generate a 45-minute interview guide — warm-up, problem, context, workarounds, willingness-to-pay.✓ Copied

→ JTBD-style script, no leading questions
Synthesize after calls

Here are my notes from 6 calls. Synthesize themes and invalidated assumptions.✓ Copied

→ Pattern recognition grounded in notes, not wish-thinking

Outcome: Discovery notes your team can actually debate.

Pitfalls

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

When to use: Feature is scoped; you need a crisp doc the team can commit to.

Flow

Use the PRD component skill

Use the prd skill. Feature: bulk-edit for our admin panel. Here's what we know [paste context].✓ Copied

→ Structured PRD with user stories, success metrics, non-goals
Pressure test

What would a skeptical staff engineer push back on?✓ Copied

→ Specific gaps in edge cases, data model, non-functional requirements

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

Pitfalls

PRD is framework-perfect but lifeless — Include real customer quotes in the context

Combine with: linear · notion

Pick the right prioritization framework for the decision at hand

👤 PMs facing a roadmap tradeoff ⏱ ~30 min intermediate

When to use: The team is debating what to build next and 'just rank the backlog' isn't working.

Flow

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.✓ Copied

→ Skill recommends a specific framework (RICE/ICE/Kano/cost-of-delay) based on the situation
Apply it

Walk us through scoring each bet with that framework.✓ Copied

→ Applied scores with reasoning

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

Pitfalls

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

Combinations

Pair with other MCPs for X10 leverage

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'.✓ Copied

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.✓ Copied

Tools

What this MCP exposes

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

Cost & Limits

What this costs to run

API quota: None
Tokens per call: 2-8k per skill load
Monetary: Free — skills are local files
Tip: Pick one skill per task; don't try to load the whole library.

Security

Permissions, secrets, blast radius

Credential storage: No credentials — skill is prompts

Data egress: None

Troubleshooting

Common errors and fixes

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