Product-Manager-Skills

Product Manager Skills

╔════════════════════════════════════════════════════════════════════╗
║                                                                    ║
║   ██████╗ ███╗   ███╗    ███████╗██╗  ██╗██╗██╗     ██╗     ███████╗
║   ██╔══██╗████╗ ████║    ██╔════╝██║ ██╔╝██║██║     ██║     ██╔════╝
║   ██████╔╝██╔████╔██║    ███████╗█████╔╝ ██║██║     ██║     ███████╗
║   ██╔═══╝ ██║╚██╔╝██║    ╚════██║██╔═██╗ ██║██║     ██║     ╚════██║
║   ██║     ██║ ╚═╝ ██║    ███████║██║  ██╗██║███████╗███████╗███████║
║   ╚═╝     ╚═╝     ╚═╝    ╚══════╝╚═╝  ╚═╝╚═╝╚══════╝╚══════╝╚══════╝
║                                                                    ║
║   77 battle-tested skills + 6 command workflows                    ║
║   Claude Code • Cursor • Codex  • n8n • OpenClaw • and more ...    ║
║                                                                    ║
║   v0.84 • August 10, 2026 • CC BY-NC-SA 4.0                        ║
╚════════════════════════════════════════════════════════════════════╝

77 battle-tested PM frameworks, ready for Claude, Codex, ChatGPT, and any agent that can read structured knowledge.

---

Why This Exists

Generic AI output is a PM's worst enemy. When you tell your agent "write a PRD" without shared context, you get a generic document that no stakeholder trusts and no engineer can act on.

This library gives both you and your AI agent the same professional foundation: the why behind each framework, the failure modes to avoid, and the judgment to apply them correctly. You stop repeating yourself. Your agent stops guessing. The work gets better.

The goal is dual — functional and pedagogic in equal measure. Skills equip agents to do PM work at a professional level, and they teach the human PM the reasoning behind each framework — so you can explain it, adapt it, and pass it on. Neither is a byproduct of the other.

---

What You Can Get Done

Navigate by what you're actually trying to accomplish:

Framing and strategy

• problem-framing-canvas — MITRE's Look Inward / Look Outward / Reframe sequence; stops teams from solving the wrong problem
• positioning-statement — Geoffrey Moore's template for defining who you serve, what you solve, and how you're different
• product-strategy-session — full strategy arc: positioning → problem framing → solution exploration → roadmap (2-4 weeks)

Stakeholder alignment

• stakeholder-identification — map every stakeholder before engaging anyone: broad brainstorm → allies/audiences/influencers → R/P/D marking → equity lens → narrow to priority targets
• stakeholder-mapping — run two complementary grids (Power × Interest for engagement strategy; Impact × Power for whose voice to elevate) and compare to find the gaps
• stakeholder-engagement-advisor — per-stakeholder engagement planning: diagnoses their profile and context, then delivers tailored message framing, medium, cadence, and a named next action

Customer discovery and research

• discovery-interview-prep — plans Mom Test-style interviews based on your research goals
• opportunity-solution-tree — generates opportunities and solutions, then recommends the best proof-of-concept to test first
• discovery-process — complete discovery cycle: frame → research → synthesize → validate (3-4 weeks)

Prioritization and roadmapping

• prioritization-advisor — asks 3-5 questions about your context, then recommends RICE, ICE, Kano, or the right alternative
• epic-breakdown-advisor — splits large epics using Richard Lawrence's 9 patterns
• roadmap-planning — gather inputs → define epics → prioritize → sequence → communicate (1-2 weeks)

Writing PM deliverables

• user-story — Mike Cohn format + Gherkin acceptance criteria, with anti-patterns
• prd-development — structured PRD: problem → personas → solution → metrics → stories (2-4 days)
• press-release — Amazon Working Backwards: clarify product vision before writing a line of spec

Validation and experimentation

• pol-probe-advisor — recommends which prototype type to run based on your hypothesis and risk level
• pol-probe — template for documenting lightweight validation experiments before building

Finance and growth

• business-health-diagnostic — diagnoses SaaS health across growth, retention, efficiency, and capital using your real metrics
• organic-growth-advisor — McKinsey Growth Pyramid triage: diagnoses whether your constraint is in new segments, geographies, channels, or products
• feature-investment-advisor — build / don't build recommendation using revenue impact, cost, ROI, and strategic value

Market and competitive intelligence

• intel-discipline-advisor — start here: triages the question on your desk into the right intelligence disciplines, cadence, and executing skill
• competitive-analysis-process — the six-step umbrella: landscape → product comparison → customer needs → business baseline → positioning → strategic direction
• The investigation chain: market-landscape-scan → competitive-research-snapshot → competitive-intel-watch → battle-card-builder — each consumes the prior's schema, so research becomes a cadence instead of a one-off deck
• tam-sam-som-calculator — market sizing three ways: your own numbers, guided interview, or autonomous bottom-up research a skeptical CFO can attack one assumption at a time

Aging products: extend, replace, or retire

• lifecycle-play-advisor — start here when a product stops growing: seven transition questions establish the stage, then it picks the play — extend, replace, or retire — and tells you when the honest answer is "nothing yet"
• product-lifecycle-plays — the framework behind that call: the PLC strategy grid, the seven replacement hazards, and a risk register whose last column asks what is Plan B?
• eol-process — the whole sunset in six phases, decide → align → plan → prepare → announce → close, including the post-EOL review everyone skips
• The EOL chain: eol-readiness-advisor → eol-stakeholder-sequence → eol-checklist → eol-internal-enablement → eol-message — every one runs standalone, sized Light/Standard/Heavy by you

Career and leadership transitions

• director-readiness-advisor — coaches PMs through the PM→Director shift across four situations: preparing, interviewing, newly landed, recalibrating
• vp-cpo-readiness-advisor — coaches Directors through VP/CPO transition, including a CEO interview framework for evaluating roles before you accept
• executive-onboarding-playbook — 30-60-90 day diagnostic playbook for VP/CPO transitions

AI product work

• ai-shaped-readiness-advisor — assesses whether you're automating tasks (AI-first) or redesigning how you work (AI-shaped), then tells you which competency to build first
• context-engineering-advisor — diagnoses context stuffing vs. context engineering and guides memory architecture for AI-powered products
• agent-orchestration-advisor — guides multi-agent workflow design across four dimensions

---

Get Started

Choose your setup:

I use...	Get this	Notes
Claude Desktop or Claude Web	pm-skills-starter-pack.zip	Unzip, then upload the individual skill ZIPs to Claude Skills
Claude Code	Plugin marketplace	/plugin marketplace add deanpeters/Product-Manager-Skills, then /plugin install product-manager-skills@pm-skills for everything (or install skills one at a time)
Codex	pm-skills-codex.zip	Installs .agents/skills and AGENTS.md
Not sure	pm-skills-starter-pack.zip	Start here

All downloads: GitHub Releases

Start here by situation

Don't know where to begin? Find the line that sounds like your week. Each route is a suggested order, not a pipeline — every skill runs on its own, so skip ahead, reorder, or stop after one. The first prompt is real: paste it, swap in your details, and go.

If this is you...	Try, in this order	Time	Paste this first
"I have an idea and I don't know if it's real."	problem-framing-canvas → discovery-interview-prep → pol-probe-advisor	~1–1.5 hr	Frame this problem: field sales reps 'don't use the CRM' and leadership wants gamification.
"A request or mandate just landed on my desk."	incoming-request-advisor → stakeholder-mapping → prioritization-advisor	~1 hr	My VP DM'd me: "Any chance the dashboard redesign lands next sprint? Board's asking." Analyze this before I reply.
"I need to understand the market, fast."	market-landscape-scan → competitive-research-snapshot → swot-analysis	~1–2 hr	Run a market landscape scan on [your market], and tell me the decision it should support.
"We keep getting compared and losing."	positioning-workshop → roadmap-planning (going bigger: product-strategy-session, a 2–4 week workflow)	~2–3 hr	Run a positioning workshop for our API monitoring tool — we keep getting compared to Datadog and losing.
"Time to write it down."	prd-development → epic-breakdown-advisor → user-story	~1.5–3 hr	Build a PRD for self-serve workspace provisioning — here are my discovery notes and the OKR it ladders to.
"Our product is getting old."	lifecycle-play-advisor → eol-readiness-advisor → eol-process	~30–50 min to a decision	Help me decide what to do with [product]. Here's what makes me think it's fading: [signals].
"I'm stepping up a level."	director-readiness-advisor or vp-cpo-readiness-advisor — pick by where you're headed	~10–20 min	I'm 60 days into a Director role and my old peers now report to me — it's awkward and I'm still doing PM work. Coach me.
"I'm new here, or not sure."	The Starter pack — six skills across the craft	—	Install it, then ask: Which of these skills fits what's on my desk this week?

Why these orders (so you can break them on purpose):

• Idea → problem → people → probe. Name the problem before you ask anyone about it, and ask people before you build anything. The probe comes last because it's the most expensive of the three.
• Request → decode → map → decide. Understand what's really being asked before replying, know who else is in the room, then ask where it fits. Prioritizing first is how a loud VP becomes your roadmap.
• Market → competitors → SWOT. Evidence first, framework last. SWOT on top of no research is opinion with a 2×2 around it.
• Positioning → roadmap. Decide who you're for and why you win before choosing what to build. The strategy session is the full-length version when the question is bigger than a quarter.
• PRD → epics → stories. The why first, then slices, then the smallest writeable pieces. Writing stories first is how a backlog loses its reason.
• Aging → play → readiness → process. The first skill may say "nothing yet" — extending or harvesting is a legitimate answer, and starting here does not commit you to a sunset.

On Claude Desktop or Web? Several of these skills aren't in a themed pack. Grab them one at a time from the download shelf, or take the All-skills pack.

Themed packs for Claude Desktop / Web

Each pack below is a ZIP of upload-ready skill ZIPs — unzip, then upload individuals to Claude Skills:

Pack	Download	What's inside
Starter	pm-skills-starter-pack.zip	Core skills across all categories
Discovery	02-discovery-pack.zip	Research, interviewing, synthesis
Strategy	03-strategy-pack.zip	Positioning, roadmapping, prioritization
Delivery	04-delivery-pack.zip	PRDs, stories, epics
AI PM	05-ai-pm-pack.zip	Context engineering, orchestration, readiness
Market Intel	06-market-intel-pack.zip	The full Market Intelligence Suite: disciplines, investigation chain, frameworks, monitors
Lifecycle & EOL	07-lifecycle-eol-pack.zip	Aging products: extend, replace, or retire — plus the full sunset process
All skills	99-all-skills-pack.zip	All 77 skills

Install guides

• Claude Desktop / Web
• Claude Code
• Codex
• Platform chooser for non-technical PMs

---

Try It First — Streamlit (beta)

Not ready to wire skills into your agent setup? Run the local playground first and kick the tires in your browser.

pip install -r app/requirements.txt
streamlit run app/main.py

What you can do:

• Learn — browse setup and integration paths without leaving the app
• Find My Skill — describe your situation in plain English and get recommended skills
• Run Skills — run a skill with your own scenario once you know what you want

Multi-provider support: Anthropic, OpenAI, Ollama. API keys via environment variables only (no in-app key entry).

Docs: app/STREAMLIT_INTERFACE.md · app/.env.example

Feedback welcome via GitHub Issues or LinkedIn.

---

70 Skills, 3 Types

Skills are organized in three tiers that build on each other:

┌────────────────────────────────────────────────────────┐
│  WORKFLOW SKILLS (19)                                  │
│  Complete end-to-end PM processes (days to weeks)      │
│  Example: run a full discovery cycle or write a PRD    │
└────────────────────────────────────────────────────────┘
                       ↓ orchestrates
┌────────────────────────────────────────────────────────┐
│  INTERACTIVE SKILLS (27)                               │
│  Guided discovery — 3-5 questions, then recommendations│
│  Example: "Which prioritization framework fits here?"  │
└────────────────────────────────────────────────────────┘
                       ↓ uses
┌────────────────────────────────────────────────────────┐
│  COMPONENT SKILLS (24)                                 │
│  Templates for specific PM deliverables (30-90 min)    │
│  Example: write a user story with acceptance criteria  │
└────────────────────────────────────────────────────────┘

Interactive skills use an Adaptive Decision Ladder. Instead of dumping a framework at you, an interactive skill asks 3-5 targeted questions about your specific context, then offers numbered recommendations — each with a clear "use this when" rationale. You pick a path. The skill executes it and explains the why as it goes. If you want to just learn the framework without doing the work, you can ask that too — the skill coaches you either way. This is ABC — Always Be Coaching — in practice.

Full catalog: catalog/INDEX.md — all 77 skills with descriptions, or browse skills/ directly.

---

How a Skill File Works

Every SKILL.md follows the same structure:

Section	What it contains
Frontmatter	name, description, type, intent, best_for, scenarios
Purpose	What this skill does and when to reach for it
Input	What you can bring (with example invocations) — inline input is used, not re-asked, and arriving empty-handed is fine: the skill walks you through it
Key Concepts	Frameworks, definitions, anti-patterns — with vocabulary explained
Application	Step-by-step instructions an agent (or human) can follow
Examples	Real-world cases showing both good and bad versions
Common Pitfalls	Named failure modes with consequences and corrections
References	Related skills and external frameworks

The best_for frontmatter field lists 3-5 specific scenarios where the skill is most useful — helpful for quickly scanning whether a skill fits your situation.

Why no $ARGUMENTS templating? Other skill libraries use Claude Code's $ARGUMENTS substitution for input. We deliberately don't: it only expands in Claude Code (it renders as literal syntax in Claude Desktop/Web, Codex, and the Streamlit playground), and it teaches the human reader nothing. Instead, every skill has a plain-language ## Input section that works on every runtime — and makes clear you can show up with full context, partial context, or nothing at all and be guided through the rest. Full rationale in CONTRIBUTING.md.

---

Works With

Claude Code · Claude Desktop · Claude Web · OpenAI Codex · ChatGPT · Cursor · Windsurf · n8n · LangFlow · CrewAI · Gemini · any agent that reads structured markdown

See docs/Platform Guides for PMs.md for platform-specific setup.

---

Docs

Document	Purpose
Using PM Skills 101	Beginner-friendly orientation — setup without technical overload
Platform Guides for PMs	Tool-by-tool setup chooser for every supported platform
Using PM Skills with Claude	Claude Code + GitHub ZIP upload for Claude Desktop/Web
Using PM Skills with Codex	Local workspace + GitHub-connected Codex on ChatGPT
Using PM Skills with ChatGPT	GitHub app, Custom GPT Knowledge, and Project-based usage
Using PM Skills with Slash Commands 101	Turn skills into reusable slash commands like /pm-story
Add-a-Skill Utility Guide	End-to-end guide for generating and validating new skills
Market Intelligence Suite Summary	The 14-skill competitive/market research suite: disciplines, chain, and which skill to run when
Lifecycle & EOL Suite Summary	The 8-skill lifecycle/sunset suite: the three plays, the EOL chain, and right-sizing
Building PM Skills	How raw PM content gets distilled into agent-ready skills
START_HERE.md	60-second onboarding for local repo users

---

What's New

v0.84 — August 10, 2026 · The Lifecycle & End-of-Life Suite

• 7 new skills + 1 upgrade for the part of product management nobody trains you on: what to do with a product that has stopped growing, and how to retire one without losing the customer
• Start upstream of the kill decision. lifecycle-play-advisor and product-lifecycle-plays diagnose where a product actually sits using seven transition questions, then pick between the three plays — extend, replace, or retire. Includes the seven replacement hazards and a risk register whose contingency column asks the question everyone skips: what is Plan B?
• The EOL chain: eol-readiness-advisor (go/no-go, and it will tell you to hold) → eol-stakeholder-sequence (Legal before Finance before Sales — get the order wrong and you find the landmines after the announcement) → eol-checklist (phase-gated, an owner on every item) → eol-internal-enablement (your teams ready before customers hear) → eol-message (upgraded: three transition paths including the honest no-replacement case) → eol-process (the whole thing, six phases, including the post-EOL review everybody skips)
• Right-sizing is a dial you set, not a verdict handed to you. Every skill offers Light / Standard / Heavy, defaults to Standard, and names what a lighter choice leaves uncovered. A feature deprecation should never get a flagship playbook — that's how teams learn to ignore EOL process on the sunset that actually matters
• No tight coupling. Every skill runs standalone; the workflow is a recommended route through independent stops, not a pipeline. Enter wherever you actually are — including mid-sunset, with a diagnostic that maps symptoms ("Support is drowning") to the phase that got skipped
• Library now at 77 skills · full story in the release note

v0.83 — July 17, 2026 · The Market Intelligence Suite

• 14 new skills + 2 major upgrades — the biggest single addition in the library's history. Run competitive and market research like an intelligence agency instead of a term paper: eight collection disciplines (OSINT → MASINT), signal → inference chains, confidence stacking, and a fusion cadence
• New interaction mode: autonomous-investigation — the protocol for research that proceeds without you. Question budgets, a search-plan gate, Fact / Inference / Assumption labels on every claim, do-not-invent lists, and stable diffable schemas, so investigations can run on a schedule and you can diff this quarter against last
• The investigation chain (market-landscape-scan → competitive-research-snapshot → competitive-intel-watch → battle-card-builder), evidence-cited strategy frameworks (swot-analysis, porters-five-forces, ansoff-matrix), monitors and miners (voice-of-customer-miner, pricing-packaging-tracker, pestel-delta-monitor), and the six-step umbrella competitive-analysis-process
• Upgraded: tam-sam-som-calculator (three entry modes, including autonomous bottom-up research) and company-intel (Executive Signal Refresh rerun pattern — Then/Now diffs and Dropped Language: what leaders stop saying is often the strongest signal)
• Library now at 70 skills · full story in the release note

v0.82 — July 8, 2026

• Added incoming-request-advisor (Interactive) — drop in a Slack ping, email, mandate, or escalation and get a structured breakdown that separates the literal ask from the real job-to-be-done, reads sender power and stake, and points you toward a reply. Ships with a copy/paste template so you can run it by hand too
• New: a browsable download shelf at /dist — no terminal, no Releases tab. Read the plain-language README, scan the CATALOG, and download any skill or pack straight from the repo. Built for PMs who just want the skills
• Library now at 56 skills

v0.81 — July 4, 2026

• Every skill now has a required ## Input section: what to bring, what happens to context you supply up front (it's used, not re-asked), and reassurance that arriving empty-handed is fine — the guided flow covers the rest
• Added argument-hint autocomplete for Claude Code users; deliberately no $ARGUMENTS templating — it breaks on every other runtime and teaches the reader nothing (why)
• Validator now enforces the convention: skills fail without an Input section or with bare $ARGUMENTS in the body
• Streamlit playground shows each skill's "What to bring (all optional)" before you start a session
• Restored agent-orchestration-advisor (Interactive) — the multi-agent workflow design skill was referenced everywhere but only existed on an orphaned commit; recovered from git history and brought up to current standards

v0.80 — June 19, 2026

• Added stakeholder-identification (Component) — comprehensive stakeholder brainstorm using allies/audiences/influencers, R/P/D marking, equity lens, and bias check; narrows to priority targets
• Added stakeholder-mapping (Component) — two complementary grids (Power × Interest + Impact × Power); comparing outputs reveals who you're under-engaging relative to how much the product affects them
• Added stakeholder-engagement-advisor (Interactive) — per-stakeholder engagement planning via Adaptive Decision Ladder: three questions on profile, power/impact, and context deliver tailored message framing, medium, cadence, and a named next action

All three adapted from the MITRE Innovation Toolkit via the companion repo MITRE ITK Skills — worth a bookmark if you work in discovery, facilitation, or cross-functional product strategy.

v0.79 — May 15, 2026

• Added organic-growth-advisor — McKinsey Growth Pyramid triage for new segments, geographies, channels, or products
• Added pm-skill-creator — interactive skill for designing repo-compliant skills via guided conversation
• Fixed missing .claude-plugin/plugin.json that silently blocked Claude Code skill discovery
• Added configurable input length guard (PM_MAX_INPUT) and path traversal protection to helper scripts

→ Full changelog

---

Contributing

Found a gap? Have a PM framework worth formalizing? The bar is pedagogic — skills must teach the why, not just the how.

See CONTRIBUTING.md for guidelines, or open an issue to start a conversation.

---

License

CC BY-NC-SA 4.0 — non-commercial use with share-alike.

Everything in this repository — every skill, template, and doc — is licensed CC BY-NC-SA 4.0. There is no mix of licenses here.

Some skills note in their Provenance sections that they were adapted from product-manager-prompts, Dean's earlier prompt library. That repo has the same author, so there is no license conflict: a license grants permissions to other people, and a copyright holder is free to adapt and relicense their own work. Those Provenance lines are lineage — a breadcrumb back to where an idea started — not a license dependency. No third-party MIT-licensed text is incorporated anywhere in this library.

In plain terms:

• ✅ Use these skills in your day job — at a for-profit company, with your team, in your agents. That's what they're for.
• ✅ Adapt and remix them — share what you build under this same license, with credit.
• ✅ Teach with them — workshops, brown bags, mentoring, sending the ladder down.
• ❌ Don't sell them — no repackaging the skills themselves into a paid product, course, or service without expressed written permission.
• 🤔 Not sure your use qualifies? Open an issue and ask. If you're using these in the spirit they were built — to get better at the craft and help others do the same — the answer is almost certainly yes.

The companion prompt library, product-manager-prompts, carries the same CC BY-NC-SA 4.0 license as of its v2.3.0, with its own plain-language permissions (stricter on commercial use) — see its LICENSING.md, which governs that repo.

---

Questions

• GitHub Issues: Report bugs or suggest features
• LinkedIn: Dean Peters
• Productside: AI PM consulting and training