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](https://github.com/deanpeters/Product-Mana