Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.
npx skills add https://github.com/deanpeters/product-manager-skills --skill product-strategy-sessionInstale esta skill com a CLI e comece a usar o fluxo de trabalho SKILL.md em seu espaço de trabalho.
╔════════════════════════════════════════════════════════════════════╗
║ ║
║ ██████╗ ███╗ ███╗ ███████╗██╗ ██╗██╗██╗ ██╗ ███████╗
║ ██╔══██╗████╗ ████║ ██╔════╝██║ ██╔╝██║██║ ██║ ██╔════╝
║ ██████╔╝██╔████╔██║ ███████╗█████╔╝ ██║██║ ██║ ███████╗
║ ██╔═══╝ ██║╚██╔╝██║ ╚════██║██╔═██╗ ██║██║ ██║ ╚════██║
║ ██║ ██║ ╚═╝ ██║ ███████║██║ ██╗██║███████╗███████╗███████║
║ ╚═╝ ╚═╝ ╚═╝ ╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝╚══════╝
║ ║
║ 47 battle-tested skills + 6 command workflows ║
║ Claude Code • Cursor • Codex • n8n • OpenClaw • and more ... ║
║ ║
║ v0.75 • Mar 17, 2026 • CC BY-NC-SA 4.0 ║
╚════════════════════════════════════════════════════════════════════╝
Help product managers become more awesome at their craft — and help them send the ladder down to others.
Battle-tested PM frameworks that teach both you and your AI agents how to do product management work at a professional level. You learn the why. Your agents execute the how. Everyone gets better.
Frame problems, hunt opportunities, scaffold validation experiments, and kill bad bets fast. With frameworks from Teresa Torres, Geoffrey Moore, Amazon, MITRE, and much more from product management's greatest hits.
I want to apologize to a contributor who recently submitted a well-intentioned and well-coded improvement that stripped learning scaffolding in favor of tighter copy. It wasn't their fault — the docs they read never crisply stated that pedagogic value is non-negotiable. We fixed that. I will work with that contribution to bring in its efficiencies while retaining the learning aspects of the skills.
What this repo is actually for: As much as this repo is for adding skills to your agent, it's equally tasked to help product managers become more awesome at their craft, and helping them send the ladder down to others. Skills here serve both goals: they make your agent more capable, and they make you more knowledgeable about why the framework works. Neither is a byproduct of the other.
ABC — Always Be Coaching is a key governing principle. Every skill should leave the person using it knowing more than when they started. Stripping explanation to tighten output is a defect, not an improvement.
What changed in v0.75:
README.md — Mission statement updated to name both audiences: human PMs and AI agentsCONTRIBUTING.md — New Design Philosophy section so contributors know what they're protectingCLAUDE.md — Pedagogic-first added to the agent's mandate, not just the style guideAGENTS.md — New Operating Philosophy section so coding agents don't optimize away the teachingRelease note: docs/announcements/2026-03-17-v0-75-pedagogic-first.md
Now available: Install skills directly from Claude Code via the plugin marketplace:
/plugin marketplace add deanpeters/Product-Manager-Skills
/plugin install jobs-to-be-done@pm-skills
This release is about making the library easier to trust and easier to use.
As this repo grows, the standard has to rise with it. So v0.7 focuses on the parts users actually feel:
intent frontmatter field so every skill can keep a sharp trigger description and a richer deeper-purpose summaryscripts/check-skill-triggers.pyscripts/test-library.shfind-a-skill.sh --mode trigger for discovering skills by use-case language, best_for, and scenariosFind My Skill mode so users can describe a situation in plain English and get recommended skills with clear next actionsLearn, Find My Skill, and Run Skills so first-time users can move from confusion to action fasterRelease note: docs/announcements/2026-03-09-v0-7-skill-quality-trigger-clarity.md
You asked, we listened. We took a moment to create comprehensive instructions on how to install, integrate, or otherwise use any one or all of these skills.
What shipped:
docs/Using PM Skills 101.md as the complete beginner-first guidedocs/Platform Guides for PMs.md as the pick-your-tool indexdocs/Using PM Skills with Slash Commands 101.md for Claude /slash workflows like /pm-story and /pm-prdSTART_HERE.md with comfort-level paths (chat-first, terminal-first, automation-first)How to make the best use of this release:
docs/Using PM Skills 101.mddocs/Platform Guides for PMs.mdRelease note: docs/announcements/2026-03-08-v0-65-onboarding-integration-guides.md
We added a command layer and fast navigation system while keeping skills as the source of truth.
What shipped:
START_HERE.md for 60-second onboardingcommands/ directory with reusable multi-skill workflowscatalog/ generated indexes for quick browsingrun-pm.sh, find-a-command.sh, test-library.sh, and generate-catalog.pyscripts/check-command-metadata.pyRelease note draft: docs/announcements/2026-03-06-v0-6-navigation-commands.md
We launched a new Streamlit (beta) interface for local skill test-driving.
What shipped:
app/main.py with guided browsing and session flowsapp/.env.example) for safer defaultsDocs:
Feedback welcome:
Four new skills covering the full product leadership career arc — from PM to Director to VP/CPO — distilled from two episodes of The Product Porch podcast.
Based on Episode 42 — From PM to Director: How to Make the Shift (Part 1):
altitude-horizon-framework (Component) — The core mental model: altitude (scope) and horizon (time), the waiter-to-operator shift, four transition zones, named failure modes, and the Cascading Context Mapdirector-readiness-advisor (Interactive) — Coaches PMs and new Directors across four situations: preparing, interviewing, newly landed, and recalibratingBased on Episode 43 — Becoming a VP & CPO: Leading Product at the Executive Level (Part 2):
executive-onboarding-playbook (Workflow) — A 30-60-90 day diagnostic playbook for VP/CPO transitions: diagnose before acting, surface unwritten strategy, assess people, act with evidencevp-cpo-readiness-advisor (Interactive) — Coaches Directors and executives through the VP/CPO transition, including the CEO interview framework for evaluating roles before acceptingWe found and fixed a facilitation regression in interactive flows.
What happened:
What we changed in v0.4:
skills/workshop-facilitation/SKILL.md.Context dump bypass, and Best guess mode.Credit:
Announcement draft: docs/announcements/2026-02-10-v0-4-facilitation-fix.md
Post title: Product Management Skills for Your Agents
Subtitle: Because "just prompt better" is not a strategy.
Still rewriting PM prompts and getting generic AI output? I built a reusable PM Skills repo to help you make sharper decisions, docs, and outcomes faster.
docs/announcements/2026-02-08-linkedin-launch.mddocs/announcements/2026-02-08-substack-savage-launch.mddocs/announcements/README.md47 ready-to-use PM skills + reusable command workflows that teach both you and your AI agents how to do product management work at a professional level — so the PM understands the why and the agent can execute the how.
Instead of saying "Write a PRD" and hoping for the best, you and your agent both know:
Result: You work faster, with better consistency, at a higher strategic level — and you can explain why.
Works with: Claude Code, Cowork, OpenAI Codex, ChatGPT, Gemini, and any AI agent that can read structured knowledge.
As much as this repo is for adding skills to your agent, it's equally tasked to help product managers become more awesome at their craft — and to help them send the ladder down to others.
Skills here serve both goals simultaneously. They equip AI agents to do PM work at a professional level, and they teach the human PM the why behind the framework — so they can explain it, adapt it, and pass it on.
ABC — Always Be Coaching is a key governing principle. Every skill should leave the person using it knowing more than when they started.
This means:
An edit that strips learning scaffolding to tighten copy is a defect, not an improvement.
New here? Start with START_HERE.md.
# Run a skill (artifact/analysis)
./scripts/run-pm.sh skill prioritization-advisor "We have 12 requests and one sprint"
# Run a command (multi-skill workflow)
./scripts/run-pm.sh command discover "Reduce onboarding drop-off for self-serve users"
Need discovery first?
./scripts/find-a-skill.sh --keyword onboarding
./scripts/find-a-command.sh --keyword roadmap
Commands make using skills easier without replacing skills.
/discover or /write-prd and learn the skill system while shipping.In short: skills provide expertise; commands provide momentum.
Want a quick local test-drive before using skills in your agent workflow?
pip install -r app/requirements.txt
streamlit run app/main.py
What you can do in v0.7:
Learn setup and integration paths without leaving the appFind My Skill by describing your situation in plain EnglishRun Skills with your own scenario once you know what you wantThis beta interface is a feature in flight. Feedback is welcome via GitHub Issues or LinkedIn.
Before using any skill:
scripts/, read them before running.name and description for better discoverability.python3 scripts/check-skill-triggers.py --show-cases before packaging if you want a quick trigger-readiness pass.Some skills include a scripts/ folder with deterministic helpers for calculations or formatting. These are optional, should be audited before running, and should avoid network calls or external dependencies.
Examples:
skills/tam-sam-som-calculator/scripts/market-sizing.pyskills/user-story/scripts/user-story-template.pyWant to create your own skills? Choose one of these utilities:
scripts/add-a-skill.sh - Content-first, AI-assisted generation from notes/frameworks.scripts/build-a-skill.sh - Guided "build-a-bear" wizard that prompts section-by-section.scripts/find-a-skill.sh - Search skills by name/type/keyword with ranked results.scripts/find-a-command.sh - Search commands by name/keyword/used skills.scripts/run-pm.sh - Fast runner for either a skill or a command.scripts/test-a-skill.sh - Run strict conformance checks and optional smoke checks.scripts/check-skill-triggers.py - Audit frontmatter descriptions and scenario prompts for Claude-style triggering.scripts/test-library.sh - Validate skills, commands, and regenerate catalogs.scripts/zip-a-skill.sh - Build upload-ready .zip files by skill, type, or all skills.scripts/generate-catalog.py - Regenerate skill/command navigation indexes.New to terminals? See scripts/README.md for a plain-language walkthrough.
Power users: These scripts are designed to chain together into fast end-to-end workflows (idea -> prompt -> validation -> packaging).
What it does:
Usage:
# From a file
./scripts/add-a-skill.sh research/your-framework.md
# Guided wizard
./scripts/build-a-skill.sh
# Find a skill
./scripts/find-a-skill.sh --keyword pricing --type interactive
# Find a command
./scripts/find-a-command.sh --keyword roadmap
# Run a command workflow
./scripts/run-pm.sh command write-prd "Mobile onboarding redesign"
# Test one skill
./scripts/test-a-skill.sh --skill finance-based-pricing-advisor --smoke
# Test full library surface
./scripts/test-library.sh
# Build Claude upload zip for one skill
./scripts/zip-a-skill.sh --skill finance-based-pricing-advisor
# Build Claude upload zips for all skills
./scripts/zip-a-skill.sh --all --output dist/skill-zips
# Build Claude upload zips for one category (component|interactive|workflow)
./scripts/zip-a-skill.sh --type component --output dist/skill-zips
# Build curated starter pack
./scripts/zip-a-skill.sh --preset core-pm --output dist/skill-zips
# Show available curated presets
./scripts/zip-a-skill.sh --list-presets
# From clipboard
pbpaste | ./scripts/add-a-skill.sh
# Check available adapters
./scripts/add-a-skill.sh --list-agents
Agent support: Claude Code, Manual mode (works with any CLI), and custom adapters via scripts/adapters/ADAPTER_TEMPLATE.sh
Learn more: See docs/Add-a-Skill Utility Guide.md for complete guide.
Cloning locally? Start with docs/Building PM Skills.md#local-clone-quickstart.
name <= 64 chars and description <= 200 chars.intent for the richer repo-facing explanation of the skill, while keeping description short and trigger-oriented.name value.scripts/zip-a-skill.sh --skill <skill-name> (or --type component, --preset core-pm) to generate upload-ready ZIPs.scripts/package-claude-skills.sh if you need unpacked upload-ready folders.scripts/check-skill-metadata.py.docs/Using PM Skills with Claude.md.These 47 skills are organized into three types that build on each other:
┌───────────────────────────────────────────────────────────┐
│ WORKFLOW SKILLS (6) │
│ Complete end-to-end PM processes │
│ Example: "Run a product strategy session" │
│ Timeline: 2-4 weeks │
└───────────────────────────────────────────────────────────┘
↓ orchestrates
┌───────────────────────────────────────────────────────────┐
│ INTERACTIVE SKILLS (20) │
│ Guided discovery with adaptive questions │
│ Example: "Which prioritization framework should I use?" │
│ Timeline: 30-90 minutes │
└───────────────────────────────────────────────────────────┘
↓ uses
┌───────────────────────────────────────────────────────────┐
│ COMPONENT SKILLS (21) │
│ Templates for specific PM deliverables │
│ Example: "Write a user story" │
│ Timeline: 10-30 minutes │
└───────────────────────────────────────────────────────────┘
What: Reusable templates for creating specific PM deliverables (user stories, positioning statements, epics, personas, PRDs, etc.)
When to use: You need a standard template or format for a specific deliverable.
Example: "Write a user story with acceptance criteria" → Use user-story.md
What: Multi-turn conversational flows where AI asks you 3-5 adaptive questions, then offers smart recommendations based on your context.
When to use: You need help deciding which approach to take or gathering context before executing.
Example: "Which prioritization framework should I use?" → Run prioritization-advisor.md, which asks about your product stage, team size, data availability, then recommends RICE, ICE, Kano, or other frameworks.
How they work:
What: Complete PM processes that orchestrate multiple component and interactive skills over days/weeks.
When to use: You need to run a full PM workflow from start to finish (strategy session, discovery cycle, roadmap planning, PRD creation).
Example: "Align stakeholders on product strategy" → Run product-strategy-session.md, which guides you through positioning → problem framing → solution exploration → roadmap planning over 2-4 weeks.
Now that you understand the three types, here's the complete catalog:
| Skill | Use When You Need To... |
|---|---|
| altitude-horizon-framework | Understand the PM→Director mindset shift: altitude (scope), horizon (time), four transition zones, failure modes, and the Cascading Context Map. Based on The Product Porch E42 |
| company-research | Deep-dive competitor or company analysis |
| customer-journey-map | Map customer experience across all touchpoints (NNGroup framework) |
| eol-message | Communicate product/feature deprecation gracefully |
| epic-hypothesis | Turn vague initiatives into testable hypotheses with success metrics |
| finance-metrics-quickref | Fast lookup table for 32+ SaaS finance metrics with formulas, benchmarks, and when to use each |
| jobs-to-be-done | Understand what customers are trying to accomplish (JTBD framework) |
| pestel-analysis | Analyze external factors (Political, Economic, Social, Tech, Environmental, Legal) |
| pol-probe | Define lightweight, disposable validation experiments to test hypotheses before building (Dean Peters PoL framework) |
| positioning-statement | Define who you serve, what problem you solve, and how you're different (Geoffrey Moore framework) |
| press-release | Write a future press release to clarify product vision (Amazon Working Backwards) |
| problem-statement | Frame a customer problem with evidence before jumping to solutions |
| product-sense-interview-answer | Structure a spoken product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs |
| proto-persona | Create hypothesis-driven personas before doing full research |
| recommendation-canvas | Document AI-powered product recommendations |
| saas-economics-efficiency-metrics | Evaluate unit economics and capital efficiency (CAC, LTV, payback, margins, burn rate, Rule of 40, magic number) |
| saas-revenue-growth-metrics | Calculate and interpret revenue, retention, and growth metrics (revenue, ARPU, MRR/ARR, churn, NRR, expansion) |
| storyboard | Visualize user journeys with 6-frame narrative storyboards |
| user-story | Write user stories with proper acceptance criteria (Mike Cohn + Gherkin) |
| user-story-mapping | Organize stories by user workflow (Jeff Patton framework) |
| user-story-splitting | Break down large stories using 8 proven patterns |
| Skill | What It Does |
|---|---|
| acquisition-channel-advisor | Evaluate acquisition channels using unit economics, customer quality, and scalability. Recommends scale/test/kill decisions |
| ai-shaped-readiness-advisor | Assess if you're "AI-first" (automating tasks) or "AI-shaped" (redesigning how you work). Evaluates 5 competencies and recommends which to build first |
| business-health-diagnostic | Diagnose SaaS business health using key metrics, identify red flags, and prioritize actions. Analyzes growth, retention, efficiency, and capital health |
| context-engineering-advisor | Diagnose context stuffing (volume without intent) vs. context engineering (structure for attention). Guides memory architecture, retrieval strategies, and Research→Plan→Reset→Implement cycle |
| customer-journey-mapping-workshop | Guides journey mapping with pain point identification |
| director-readiness-advisor | Coaches PMs and new Directors through the transition across four situations: preparing, interviewing, newly landed, recalibrating. Based on The Product Porch E42 |
| discovery-interview-prep | Plans customer interviews (Mom Test style) based on your research goals |
| epic-breakdown-advisor | Splits epics into user stories using Richard Lawrence's 9 patterns |
| feature-investment-advisor | Evaluate feature investments using revenue impact, cost structure, ROI, and strategic value. Delivers build/don't build recommendations |
| finance-based-pricing-advisor | Evaluate pricing changes using financial impact analysis (ARPU/ARPA, conversion, churn risk, NRR, payback) |
| lean-ux-canvas | Sets up hypothesis-driven planning (Jeff Gothelf Lean UX Canvas v2) |
| opportunity-solution-tree | Generates opportunities and solutions, recommends best proof-of-concept to test |
| pol-probe-advisor | Recommends which of 5 prototype types to use based on your hypothesis and risk (Feasibility, Task-Focused, Narrative, Synthetic Data, Vibe-Coded) |
| positioning-workshop | Guides you through defining your positioning with adaptive questions |
| prioritization-advisor | Recommends the right prioritization framework (RICE, ICE, Kano, etc.) for your situation |
| problem-framing-canvas | Leads you through MITRE Problem Framing (Look Inward/Outward/Reframe) |
| tam-sam-som-calculator | Projects market size (TAM/SAM/SOM) with real-world data and citations |
| user-story-mapping-workshop | Walks you through creating story maps with backbone and release slices |
| vp-cpo-readiness-advisor | Coaches Directors and executives through the VP/CPO transition — includes CEO interview framework for evaluating roles before accepting. Based on The Product Porch E43 |
| workshop-facilitation | Adds one-step-at-a-time facilitation with numbered recommendations for workshop skills |
| Skill | What It Does | Timeline |
|---|---|---|
| discovery-process | Complete discovery cycle: frame problem → research → synthesize → validate solutions | 3-4 weeks |
| executive-onboarding-playbook | 30-60-90 day diagnostic playbook for VP/CPO transitions: diagnose before acting, surface unwritten strategy, assess people, act with evidence. Based on The Product Porch E43 | 90 days |
| prd-development | Structured PRD: problem statement → personas → solution → metrics → user stories | 2-4 days |
| product-strategy-session | Full strategy: positioning → problem framing → solution exploration → roadmap | 2-4 weeks |
| roadmap-planning | Strategic roadmap: gather inputs → define epics → prioritize → sequence → communicate | 1-2 weeks |
| skill-authoring-workflow | Meta workflow: choose add/build path → validate conformance → update docs → package/publish | 30-90 minutes |
Possible skills in development:
Detailed concept notes live in PLANS.md.
Confused by setup options? Start here: PM Skills Rule-of-Thumb Guide.
# Skill mode
./scripts/run-pm.sh skill user-story "Checkout improvements for returning customers"
# Command mode
./scripts/run-pm.sh command plan-roadmap "Q3-Q4 roadmap for enterprise reporting"
Command definitions live in commands/, and generated browse indexes live in catalog/.
cd product-manager-skills
claude "Using the PRD Development workflow, create a PRD for our mobile feature"
You can discover via npx skills find <query> and npx skills add deanpeters/Product-Manager-Skills --list, then install for Claude Code. See Using PM Skills with Claude.
Use local workspace paths, GitHub-connected Codex on ChatGPT, or discover/install directly with npx skills. See Using PM Skills with Codex.
Use GitHub app connections (formerly connectors), Custom GPT Knowledge uploads, or Project files. See Using PM Skills with ChatGPT.
Cowork: Import skills as knowledge modules, invoke via natural language.
Other agents: Follow your agent's docs for loading custom knowledge.
/pm-story and /pm-prd.→ Workflow: product-strategy-session (2-4 weeks, orchestrates positioning → roadmap)
→ Workflow: discovery-process (3-4 weeks, interviews → synthesis → validation)
→ Interactive: pol-probe-advisor (recommends which prototype type: Feasibility, Task-Focused, Narrative, Synthetic Data, or Vibe-Coded)
→ Component: pol-probe (template for documenting validation experiments)
→ Interactive: ai-shaped-readiness-advisor (assesses 5 competencies: Context Design, Agent Orchestration, Outcome Acceleration, Team-AI Facilitation, Strategic Differentiation)
→ Interactive: context-engineering-advisor (diagnose context stuffing vs. engineering, define boundaries, implement Research→Plan→Reset→Implement cycle)
→ Workflow: prd-development (2-4 days, problem → solution → stories)
→ Workflow: roadmap-planning (1-2 weeks, epics → prioritization → sequencing)
→ Interactive: prioritization-advisor (asks questions, recommends RICE/ICE/Kano)
→ Interactive: epic-breakdown-advisor (Richard Lawrence's 9 patterns)
→ Component: user-story (template + examples)
| Prompts | Skills |
|---|---|
| One-time instructions per task | Reusable frameworks learned once |
| "Write a PRD for X" | Agent knows PRD structure, asks smart questions, handles edge cases |
| You repeat yourself constantly | Agent remembers best practices |
| Inconsistent outputs | Consistent, professional results |
Skills = Less explaining, more strategic work.
Built on proven methods from Geoffrey Moore, Jeff Patton, Teresa Torres, Amazon, Richard Lawrence, MITRE, and more.
Based on decades of PM consulting across healthcare, finance, manufacturing, and tech.
Optimized for AI comprehension—not blog posts, not books, not courses. Executable frameworks.
Every word earns its keep. No filler, no buzzwords, no generic advice.
Shows both "good" and "bad" examples so you know what works and what to avoid.
Every skill follows the same format:
## Purpose
What this skill does and when to use it.
## Key Concepts
Core frameworks, definitions, anti-patterns.
## Application
Step-by-step instructions (with examples).
## Examples
Real-world cases (good and bad).
## Common Pitfalls
What to avoid and why.
## References
Related skills and external frameworks.
Clean. Practical. Zero fluff.
Found a gap? Have a PM framework you'd like to see included?
Ways to contribute:
See CONTRIBUTING.md for detailed guidelines.
Principles:
No hype. No buzzwords. Just frameworks that work.
CC BY-NC-SA 4.0 — non-commercial use with share-alike.
See LICENSE for full details.
v0.7 — March 9, 2026
Highlights in this release:
intent as a repo-standard frontmatter field to separate trigger metadata from deeper purposescripts/check-skill-triggers.py and wired trigger-readiness auditing into test-library.shfind-a-skill.sh --mode trigger so users can discover skills through description, best_for, and scenariosFind My Skill mode with plain-English discovery, recommended-first results, and direct preview/run actionsv0.65 — March 8, 2026
Highlights in this release:
docs/Using PM Skills 101.mddocs/Platform Guides for PMs.mddocs/Using PM Skills with Slash Commands 101.mdSTART_HERE.md and docs navigation so new users can pick the right setup path fasterv0.6 — March 6, 2026
Highlights in this release:
commands/ with reusable workflow wrappers over local skills (discover, strategy, write-prd, plan-roadmap, prioritize, leadership-transition)START_HERE.md for 60-second onboardingcatalog/ artifacts for fast skill and command navigationfind-a-command.sh, run-pm.sh, check-command-metadata.py, test-library.sh, generate-catalog.pyv0.5 — February 27, 2026
Highlights in this release:
app/ with multi-provider/model selectionv0.4 — February 10, 2026
Highlights in this release:
workshop-facilitation to canonical source of truth for interactive facilitationv0.3 — February 9, 2026
Highlights in this release:
skill-authoring-workflowadd-a-skill, build-a-skill, find-a-skill, test-a-skill, zip-a-skillBuilt by Dean Peters (Principal Consultant and Trainer at Productside.com) with Anthropic Claude and OpenAI Codex.
Helping product managers work smarter with AI.