Skip to content
SkillCheatSheet Sign in

deanpeters/Product-Manager-Skills

Agent skills in the GitHub repository deanpeters/Product-Manager-Skills, each with its code score out of 100.

Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.

Repository score
62 / 100 C
Skills
77
Verified
1
Average skill score
66
GitHub stars
7,992
License
Not identified by GitHub

Open deanpeters/Product-Manager-Skills on GitHub

77 skills in this repository

  1. user-story

    Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.

    Verified89A
  2. epic-breakdown-advisor

    Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.

    79B
  3. eol-checklist

    Build a phase-gated EOL checklist sized to the sunset, with a named owner on every item. Use when the decision to retire is made and you need the operational plan.

    77B
  4. press-release

    Write an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet.

    76B
  5. positioning-statement

    Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.

    75B
  6. positioning-workshop

    Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.

    75B
  7. skill-authoring-workflow

    Turn raw PM content into a compliant, publish-ready skill. Use when creating or updating a repo skill without breaking standards.

    75B
  8. discovery-interview-prep

    Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product idea…

    74B
  9. product-strategy-session

    Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.

    74B
  10. epic-hypothesis

    Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery plann…

    72B
  11. pol-probe-advisor

    Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.

    72B
  12. problem-statement

    Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.

    72B
  13. feature-investment-advisor

    Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.

    71B
  14. jobs-to-be-done

    Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.

    71B
  15. stakeholder-engagement-advisor

    Plan engagement for a specific stakeholder. Use when preparing an outreach, navigating resistance, or aligning a critical relationship before a key milestone.

    70B
  16. user-story-splitting

    Break a large story or epic into smaller deliverable stories using proven split patterns. Use when backlog items are too big for estimation, sequencing, or independent release.

    70B
  17. customer-journey-map

    Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow.

    69C
  18. pm-skill-creator

    Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.

    69C
  19. pol-probe

    Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product.

    69C
  20. porters-five-forces

    Read an industry's structure through Porter's Five Forces with documented signals per rating, ending at the profit pool. Use when weighing market entry or when margins erode and n…

    69C
  21. product-sense-interview-answer

    Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next intervi…

    69C
  22. storyboard

    Create a six-frame storyboard that shows a user's journey from problem to solution. Use when you need a fast narrative for alignment, concept reviews, or demos.

    69C
  23. tam-sam-som-calculator

    Calculate TAM, SAM, and SOM with explicit assumptions, methods, and caveats. Use when sizing a market for a product idea, business case, or executive review.

    69C
  24. derisk-measurement-advisor

    Identify what to measure, test, or track to de-risk a product or AI idea. Use when stress-testing an idea across internal (DUFV) and external (PESTEL) dimensions.

    68C
  25. eol-process

    Run a product sunset end to end — decide, align, plan, prepare, announce, close. Use when you need the whole EOL process, not just one artifact.

    68C
  26. executive-onboarding-playbook

    Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.

    68C
  27. incoming-request-advisor

    Decode an incoming message into a structured breakdown separating the literal ask from the job-to-be-done. Use when a loaded Slack ping, email, mandate, or escalation needs a repl…

    68C
  28. problem-framing-canvas

    Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions.

    68C
  29. proto-persona

    Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation.

    68C
  30. eol-stakeholder-sequence

    Plan who to talk to about a sunset, in what order, and what each conversation must cover. Use when an EOL decision is made and you want the landmines found before the announcement.

    67C
  31. opportunity-solution-tree

    Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.

    67C
  32. saas-revenue-growth-metrics

    Calculate SaaS revenue, retention, and growth metrics. Use when diagnosing momentum, churn, expansion, or product-market-fit signals.

    67C
  33. battle-card-builder

    Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.

    66C
  34. eol-internal-enablement

    Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Use when customer-facing teams must be ready before customers hear.

    66C
  35. organic-growth-advisor

    Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth leve…

    66C
  36. product-lifecycle-plays

    Map a product's lifecycle stage and choose between extension, replacement, and retirement plays. Use when a product is maturing or declining and the next move isn't obvious.

    66C
  37. recommendation-canvas

    Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning. Use when deciding whether an AI solution deserves investment or recommendation.

    66C
  38. stakeholder-identification

    Map every stakeholder before engaging anyone. Use when launching an initiative, scoping discovery, or building an engagement plan from scratch.

    66C
  39. swot-analysis

    Build an evidence-cited SWOT of one company — yours or a competitor's — from public sources, ending with the S-O/W-T crossings. Use for strategy reviews, board prep, or competitor…

    66C
  40. user-story-mapping

    Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.

    66C
  41. ai-shaped-readiness-advisor

    Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.

    65C
  42. competitive-research-snapshot

    Research a competitive landscape with cited snapshots, a comparison matrix, and so-what implications. Use when a product decision needs competitive grounding, not a market report.

    65C
  43. director-readiness-advisor

    Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating. Use when leadership scope is changing and you need practical coaching.

    65C
  44. pestel-delta-monitor

    Quarterly re-scan of a prior PESTEL analysis. Use when checking which macro factors moved, which assumptions broke, and what's new — turning PESTEL from a workshop artifact into a…

    65C
  45. company-research

    Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry wo…

    64C
  46. context-engineering-advisor

    Diagnose context stuffing vs. context engineering. Use when an AI workflow feels bloated, brittle, or hard to steer reliably.

    64C
  47. prd-development

    Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

    64C
  48. stakeholder-mapping

    Prioritize stakeholders using two complementary grids. Use when setting engagement strategy and surfacing whose voice needs elevating after stakeholder identification.

    64C
  49. user-story-mapping-workshop

    Run a user story mapping workshop with adaptive questions and a structured map output. Use when you need backbone activities, tasks, and release slices for a workflow.

    64C
  50. ansoff-matrix

    Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.

    63C
  51. company-intel

    Research a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.

    63C
  52. competitive-analysis-process

    Orchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card.

    63C
  53. discovery-process

    Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.

    63C
  54. eol-message

    Write a right-sized EOL announcement — brief notice through full phased comms — with rationale, customer impact, and next steps. Use when retiring a product, feature, or plan.

    63C
  55. lifecycle-play-advisor

    Diagnose where a product sits in its lifecycle and which play fits — extend, replace, or retire. Use when a product is fading and you need the call, not just the worry.

    63C
  56. altitude-horizon-framework

    Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

    62C
  57. intel-discipline-advisor

    Triage a competitive or market question into the right intelligence disciplines, cadence, and executing skill. Use when you know something needs researching but not which channel…

    62C
  58. agent-orchestration-advisor

    Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.

    61C
  59. competitive-intel-watch

    Scheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs u…

    61C
  60. market-landscape-scan

    Map a market's segments, players, substitutes, and whitespace with cited evidence. Use when entering or re-evaluating a market before sizing, positioning, or picking competitors t…

    61C
  61. voice-of-customer-miner

    Mine public reviews, app stores, and forums for unmet needs, competitor weaknesses, and switching triggers — with quoted evidence. Use when you want customer voice without waiting…

    61C
  62. vp-cpo-readiness-advisor

    Guide the transition to VP or CPO across preparing, interviewing, landing, and recalibrating. Use when executive product scope is changing fast.

    61C
  63. pricing-packaging-tracker

    Track competitor pricing and packaging as a diffable time series. Use when monitoring tiers, gates, limits, and price moves on a monthly or quarterly cadence.

    60C
  64. workshop-facilitation

    Facilitate workshop sessions in a one-step, multi-turn flow. Use when an interactive skill needs consistent pacing, options, and progress tracking.

    60C
  65. eol-readiness-advisor

    Run a go/no-go assessment for retiring a product or feature, then right-size the effort. Use when someone says "we should probably kill this" and nobody has made the call.

    59C
  66. finance-based-pricing-advisor

    Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback. Use when deciding whether a pricing move should ship.

    59C
  67. prioritization-advisor

    Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.

    59C
  68. autonomous-investigation

    The protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable out…

    58C
  69. customer-journey-mapping-workshop

    Run a customer journey mapping workshop with adaptive questions and outputs. Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and s…

    58C
  70. pestel-analysis

    Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.

    58C
  71. roadmap-planning

    Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.

    58C
  72. acquisition-channel-advisor

    Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.

    57C
  73. business-health-diagnostic

    Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.

    56C
  74. finance-metrics-quickref

    Look up SaaS finance metrics, formulas, and benchmarks fast. Use when you need a quick metric definition, formula, or benchmark during analysis.

    54D
  75. intelligence-collection-disciplines

    Run competitive research like an intelligence agency: eight collection disciplines (OSINT to MASINT), signal-to-inference chains, and fusion. Use when one-source research isn't en…

    54D
  76. lean-ux-canvas

    Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.

    54D
  77. saas-economics-efficiency-metrics

    Evaluate SaaS unit economics and capital efficiency. Use when deciding whether the business can scale efficiently or needs correction.

    54D

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.