PM Skills

<a id="readme-top"></a>

• Quick Start
• Recent Updates
• The Big Idea
  • Who Is This For
  • Key Features
  • Skill Lifecycle Tools
  • Founded On
• Installation and Setup
• How Agent Skills Work
• The Skill Library
  • Foundation Skills
  • Discover Phase Skills
  • Define Phase Skills
  • Develop Phase Skills
  • Deliver Phase Skills
  • Measure Phase Skills
  • Iterate Phase Skills
  • Tool Family: Foundation Sprint
  • Tool Family: Design Sprint
  • Standalone Tool Skill
  • Utility Skills
  • Sub-Agents
  • Workflows
• Library Examples
• Learning and Resources
• Project Status
• Contributing
• Community
• FAQ
• About the Author

Quick Start

After installing, you'll have all 68 skills available (invoke any by name, like /pm-skills:deliver-prd, /pm-skills:define-hypothesis, /pm-skills:deliver-user-stories) plus 10 /workflow-* orchestrator commands and the /chain ad-hoc runner, templates, sub-agents, and 200+ sample outputs.

Claude Code (recommended):

/plugin marketplace add product-on-purpose/agent-plugins
/plugin install pm-skills@product-on-purpose

Already installed via the old pm-skills-marketplace? It keeps working - no action needed. To move to the new home, see the v2.21.0 release notes.

Cross-agent (Cursor, Copilot, Cline, and others via the open skills CLI):

npx skills add product-on-purpose/pm-skills

Clone or download:

git clone https://github.com/product-on-purpose/pm-skills.git

More resources:

• Getting Started Guide - Detailed walkthrough for new users covering clone, sync helper, and first skill run. The path to take if any of the quick start steps above leave gaps.
• Setup by Platform - Step-by-step install for Claude.ai, Codex, Cursor, Windsurf, GitHub Copilot, VS Code extensions, and ChatGPT.
• Quickstart Reference - Short-form reference card for users who just need the commands.

Recent Updates

The companion pm-skills-mcp server is in the v2.9.x maintenance line (latest v2.9.3) and remains available on npm for clients that need MCP transport. The catalog is frozen at the v2.9.2 build; subsequent v2.9.x patches do not change the catalog. Active development on the MCP server is paused; security patches and critical bug fixes will continue.

Recommendation: For new users, we recommend using the plugin. See Installation and Setup for other options.

What's New

Full history: CHANGELOG.md or all GitHub Releases.

The Big Idea

Stop prompt-fumbling. Start shipping. Every time you ask an AI to help with product management, you start from zero. Generic responses. Inconsistent formats. Missing critical sections. Hours lost to repetitive prompt crafting.

PM-Skills gives your AI instant access to professional frameworks refined across hundreds of product launches, production-ready templates that capture institutional PM knowledge, and real-world examples that set the quality bar.

Who Is This For

Key Features

• ✅ 68 Production-Ready Skills covering the complete product lifecycle (30 phase skills + 11 foundation skills + 12 utility skills + 15 tool skills for structured workshop methodologies)
• ✅ Triple Diamond Framework organizing Discover, Define, Develop, Deliver, Measure, and Iterate phases
• ✅ Tool Families for the Foundation Sprint (2-day strategic alignment) and Design Sprint (5-day prototype-and-test) workshop methodologies
• ✅ 5 Active Orchestration Sub-Agents (pm-critic, pm-skill-auditor, pm-changelog-curator, pm-release-conductor, pm-workflow-orchestrator) for Claude Code, with dispatch skills extending the pattern to Codex, Cursor, Windsurf, Copilot, and Gemini CLI
• ✅ 12 Workflows for common PM processes including Feature Kickoff, Lean Startup, Triple Diamond, and foundation-to-design end-to-end arc
• ✅ 10 Workflow Commands for Claude Code users - plus every skill invocable directly by name
• ✅ Auto-Discovery via AGENTS.md in GitHub Copilot, Cursor, and Windsurf
• ✅ Agent Skills Spec compliant - works across AI assistants
• ✅ Apache 2.0 Licensed for commercial and personal use

Skill Lifecycle Tools = Custom Skill Builder

PM-Skills includes three utility skills that form a complete Create - Validate - Iterate lifecycle for building and managing skills:

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#fffbeb', 'primaryBorderColor': '#fde68a', 'lineColor': '#92400e'}}}%%
flowchart LR
    classDef create fill:#ea580c,stroke:#c2410c,color:#fff,font-weight:bold
    classDef validate fill:#0284c7,stroke:#0369a1,color:#fff,font-weight:bold
    classDef decision fill:#374151,stroke:#1f2937,color:#fff
    classDef ship fill:#166534,stroke:#14532d,color:#fff,font-weight:bold
    classDef iterate fill:#7c3aed,stroke:#6d28d9,color:#fff,font-weight:bold

    Create["utility-pm-skill-builder<br/>Create new skill<br/>from an idea"]:::create
    Validate["utility-pm-skill-validate<br/>Audit structure<br/>and quality"]:::validate
    Decision{"Findings?"}:::decision
    Ship["Ship<br/>to library"]:::ship
    Iterate["utility-pm-skill-iterate<br/>Apply targeted<br/>improvements"]:::iterate

    Create --> Validate
    Validate --> Decision
    Decision -- "PASS" --> Ship
    Decision -- "WARN / FAIL" --> Iterate
    Iterate --> Validate

Why this matters: Skills are living artifacts that evolve. The builder creates them, the validator catches drift and quality gaps, and the iterator applies fixes. Together they keep the library consistent as it grows.

🔗 More resources:

• PM Skill Lifecycle Guide - Full workflow for creating, validating, and iterating skills, including the builder-validator-iterator cycle with worked examples.
• Creating PM Skills - Authoring guide for contributing new skills to the library.
• Skill Template - The canonical three-file template every skill must follow; copy this as your starting point.

Founded On

• Triple Diamond Framework - Six-phase product cycle (extends Design Council's Double Diamond): Discover, Define, Develop, Deliver, Measure, Iterate
• Opportunity Solution Trees (Teresa Torres) - Outcome-driven discovery
• Jobs to be Done Framework - Customer motivation framework
• Foundation Sprint (Knapp/Zeratsky) - 2-day structured workshop methodology for early-stage strategic alignment: basics, differentiation, approach options, magic lenses, founding hypothesis, brief
• Design Sprint (Knapp/Zeratsky/Kowitz) - 5-day structured workshop methodology for prototype-and-test cycles: map-and-target, sketch, decide-and-storyboard, prototype-plan, test-and-score
• Architecture Decision Records (Michael Nygard format) - Technical decision documentation

Installation and Setup

Tool Compatibility

Featured Install Paths

Claude Code - Plugin Marketplace (recommended)

/plugin marketplace add product-on-purpose/agent-plugins
/plugin install pm-skills@product-on-purpose

Already installed via the old pm-skills-marketplace? It keeps working - no action needed. To move to the new home, see the v2.21.0 release notes.

All 68 skills and their slash commands become available immediately. No clone required.

Cross-Agent via skills CLI (Cursor, Copilot, Cline, and others)

npx skills add product-on-purpose/pm-skills

The open skills CLI from Vercel Labs scans the skills/ directory and installs all 68 skills into your agent's default skills directory. Works with Claude Code, Cursor, GitHub Copilot, Cline, and any other agent that supports the skills ecosystem. Discoverable via skills.sh/product-on-purpose/pm-skills.

Telemetry is anonymous and opt-out via DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1.

Git Clone (manual path, everything included)

git clone https://github.com/product-on-purpose/pm-skills.git
cd pm-skills

Gives you the full repo: skill files, slash commands, sample library, workflows, and documentation. Use this path when you want local access to sample outputs, plan to customize skills, or prefer not to depend on a CLI.

Optional: after cloning, run ./scripts/sync-claude.sh (macOS/Linux) or ./scripts/sync-claude.ps1 (Windows) to populate .claude/skills/ for agents that use that discovery path.

Additional Install Methods

For Claude.ai, MCP clients, OpenCode, Windsurf, and ChatGPT, see the full Platform Setup Guide for step-by-step instructions.

More resources:

• Getting Started Guide - Detailed walkthrough for new users covering all install methods, the sync helper script, and your first skill run end-to-end.
• Quickstart Reference - Short-form reference card with just the essential commands.

How Agent Skills Work

Each skill is a self-contained instruction set in three files:

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#f8fafc', 'primaryBorderColor': '#cbd5e1', 'lineColor': '#64748b'}}}%%
flowchart LR
    classDef user fill:#1e293b,stroke:#0f172a,color:#f8fafc,font-weight:bold
    classDef agent fill:#4f46e5,stroke:#3730a3,color:#fff,font-weight:bold
    classDef skillFile fill:#7c3aed,stroke:#5b21b6,color:#fff
    classDef templateFile fill:#0284c7,stroke:#0369a1,color:#fff
    classDef exampleFile fill:#059669,stroke:#047857,color:#fff
    classDef output fill:#166534,stroke:#14532d,color:#fff,font-weight:bold

    User["You<br/>deliver-prd 'topic'"]:::user
    Agent["Your Agent"]:::agent
    SKILL["SKILL.md<br/>the method"]:::skillFile
    TEMPLATE["TEMPLATE.md<br/>the structure"]:::templateFile
    EXAMPLE["EXAMPLE.md<br/>the quality bar"]:::exampleFile
    Output["Complete artifact"]:::output

    User -- invokes --> Agent
    Agent -- reads --> SKILL
    Agent -- fills --> TEMPLATE
    Agent -- mirrors --> EXAMPLE
    SKILL --> Output
    TEMPLATE --> Output
    EXAMPLE --> Output

skills/deliver-prd/
  SKILL.md                  # the method the agent reads
  references/
    TEMPLATE.md             # the structure the output follows
    EXAMPLE.md              # the worked example that anchors quality

When you run /pm-skills:deliver-prd "topic", the agent loads the skill, mirrors the example, fills the template, and produces a complete PRD. No prompt engineering required.

🔗 More resources:

• PM Skill Anatomy - Deep dive into the three-file structure (SKILL.md, TEMPLATE.md, EXAMPLE.md) and what each file contributes to output quality. Essential reading before authoring your first skill.
• Skill Finder - Decision guide for choosing the right skill when you know the outcome you need but aren't sure which skill produces it.
• PM Skill Comparisons - Side-by-side comparison of overlapping skills. Prevents the common mistake of reaching for problem-statement when opportunity-tree is the right fit.
• Sub-Agents - Claude Code also supports spawnable specialist agents for tasks that benefit from a dedicated agent context: adversarial review, catalog auditing, changelog curation, and release orchestration.

<a id="the-skill-library"></a>

The Skill Library

At a Glance

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#f0f4ff', 'primaryBorderColor': '#c7d2fe', 'lineColor': '#6b7280', 'clusterBkg': '#f8fafc', 'clusterBorder': '#e2e8f0'}}}%%
flowchart TB
    classDef discover fill:#0891b2,stroke:#0e7490,color:#fff,font-weight:bold
    classDef define fill:#7c3aed,stroke:#6d28d9,color:#fff,font-weight:bold
    classDef develop fill:#d97706,stroke:#b45309,color:#fff,font-weight:bold
    classDef deliver fill:#16a34a,stroke:#15803d,color:#fff,font-weight:bold
    classDef measure fill:#dc2626,stroke:#b91c1c,color:#fff,font-weight:bold
    classDef iterate fill:#9333ea,stroke:#7e22ce,color:#fff,font-weight:bold
    classDef tool fill:#0284c7,stroke:#0369a1,color:#fff
    classDef foundation fill:#059669,stroke:#047857,color:#fff
    classDef utility fill:#ea580c,stroke:#c2410c,color:#fff

    subgraph PHASE["Triple Diamond Phase Skills (30)"]
        direction LR
        DI["Discover<br/>5 skills"]:::discover
        DE["Define<br/>5 skills"]:::define
        DEV["Develop<br/>4 skills"]:::develop
        DEL["Deliver<br/>6 skills"]:::deliver
        ME["Measure<br/>6 skills"]:::measure
        IT["Iterate<br/>4 skills"]:::iterate

        DI --> DE --> DEV --> DEL --> ME --> IT
        IT -."feedback loop".-> DI
    end

    subgraph WORKSHOP["Workshop Tool Families (15 skills)"]
        direction LR
        FS["Foundation Sprint<br/>7 skills<br/>2-day strategic alignment"]:::tool
        DS["Design Sprint<br/>7 skills<br/>5-day prototype-and-test"]:::tool
        NV["note-and-vote<br/>1 skill<br/>standalone mechanic"]:::tool
        FS --> DS
    end

    subgraph SUPPORT["Cross-Cutting Capabilities (23 skills)"]
        direction LR
        FOUND["Foundation<br/>11 skills<br/>persona, lean-canvas,<br/>OKRs, meetings"]:::foundation
        UTIL["Utility<br/>12 skills<br/>meta-tooling"]:::utility
    end

    PHASE -.uses.-> SUPPORT
    WORKSHOP -.uses.-> SUPPORT

Foundation Skills - Cross-cutting capability (11)

Phase Skills: Triple Diamond

Discover - Find and assess the right problem (5)

Define - Frame the problem (5)

Develop - Explore solutions (4)

Deliver - Ship it (6)

Measure - Validate with data (6)

Iterate - Learn and improve (4)

🔗 More resources:

• Using Skills Guide - Practical guide to invoking skills across different agents, passing context effectively, and getting consistent outputs session to session.
• Using Workflows Guide - How to run multi-skill chains, handle handoffs between skills, and adapt workflows to your team's process.
• Recipes - Curated patterns for common PM scenarios: solo feature launch, quarterly OKR cycle, research-to-delivery arc.
• Prompt Gallery - Real prompts that produce excellent skill outputs, annotated with what makes each one effective.

Tool Family: Foundation Sprint (7)

A Foundation Sprint is a short, structured workshop that clarifies the problem space, target users, success metrics, constraints, and business context before creative exploration begins. It ensures teams start with shared understanding and crisp definitions so downstream design and product decisions move faster and with fewer reversals.

Run the full methodology with the foundation-sprint workflow.

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#eff6ff', 'primaryBorderColor': '#bfdbfe', 'lineColor': '#3b82f6'}}}%%
flowchart LR
    classDef sprint fill:#0284c7,stroke:#0369a1,color:#fff,font-weight:bold
    classDef gate fill:#1d4ed8,stroke:#1e40af,color:#fff,font-weight:bold

    R["1. Readiness<br/>Go / No-Go check"]:::gate
    B["2. Basics<br/>Customer + Problem + Competition"]:::sprint
    Di["3. Differentiation<br/>2x2 advantage map"]:::sprint
    A["4. Approach Options<br/>3-5 high-level paths"]:::sprint
    M["5. Magic Lenses<br/>Score approaches"]:::sprint
    H["6. Founding Hypothesis<br/>Synthesize direction"]:::sprint
    Br["7. Brief<br/>One-page output"]:::gate

    R --> B --> Di --> A --> M --> H --> Br

🔗 More resources:

• Foundation Sprint Concept Primer - A Foundation Sprint is a 2-day structured workshop methodology developed by Jake Knapp and John Zeratsky. This primer explains what it is, when to use it, the 7-step sequence, and how it compares to a Design Sprint.
• Using Foundation Sprint - Operational guide for running the 7-skill Foundation Sprint sequence with an agent, including facilitation notes and output expectations for each step.
• Foundation Sprint FAQ - Answers to common questions about the methodology: how long it takes, who should be in the room, what to do with the brief output, and when not to run it.
• Foundation Sprint Cheat Sheet - One-page quick reference for the day-arc, skill sequence, and key outputs.
• Foundation Sprint Case Studies - Three fictional scenarios showing how different teams used the Foundation Sprint methodology at different stages.
• Foundation Sprint Recovery - What to do when a sprint produces a confusing founding hypothesis, the team disagrees on direction, or you want to redo a step.

Tool Family: Design Sprint (7)

A Design Sprint is a fast, structured process that helps teams understand a problem, explore solutions, build a prototype, and test it with real users in five days. It reduces risk by forcing alignment and validation before any heavy engineering investment.

Run the full methodology with the design-sprint workflow. Chain it after a Foundation Sprint with foundation-to-design.

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#fdf4ff', 'primaryBorderColor': '#e9d5ff', 'lineColor': '#9333ea'}}}%%
flowchart LR
    classDef sprint fill:#7c3aed,stroke:#6d28d9,color:#fff
    classDef gate fill:#581c87,stroke:#3b0764,color:#fff,font-weight:bold
    classDef day fill:#6d28d9,stroke:#5b21b6,color:#fff

    R["Readiness<br/>Go / No-Go"]:::gate
    Br["Brief<br/>Goal + Questions"]:::sprint
    M["Day 1<br/>Map and Target"]:::day
    S["Day 2<br/>Sketch"]:::day
    D["Day 3<br/>Decide and Storyboard"]:::day
    P["Day 4<br/>Prototype Plan"]:::day
    T["Day 5<br/>Test and Score"]:::gate

    R --> Br --> M --> S --> D --> P --> T

🔗 More resources:

• Design Sprint Concept Primer - A Design Sprint is a 5-day structured workshop methodology developed at Google Ventures by Jake Knapp, John Zeratsky, and Braden Kowitz. This primer covers the methodology's heritage, the 5-day arc as implemented in this skill family, and how it differs from a physical in-person workshop.
• Using Design Sprint - Operational guide for running the 7-skill Design Sprint sequence with an agent, including what "realistic-enough" means for the prototype step and how to recruit for test day.
• Design Sprint FAQ - Questions about prototype fidelity, user recruitment, scoring results, and what to do if no clear winner emerges after testing.
• Design Sprint Cheat Sheet - One-page quick reference for the 5-day arc, skill sequence, and key outputs.
• Design Sprint Case Studies - Fictional scenarios applying the Design Sprint to B2C, B2B, and internal-tools product challenges.
• Design Sprint Recovery - What to do when prototype testing produces inconclusive results, the test fails entirely, or the team needs to iterate on the storyboard.
• Workshop Sprints vs Agile Sprints - The disambiguation every Scrum team needs before running their first Design Sprint. Two completely different processes, one unfortunately shared word.
• Workshop Method Comparison - When to use Foundation Sprint vs Design Sprint vs other structured workshop approaches; includes a decision matrix.

Standalone Tool Skill

Utility Skills - Meta-tooling (12)

<a id="sub-agents"></a>

Sub-Agents

Sub-agents are specialist agents that Claude Code can spawn as autonomous sub-tasks within a larger session. Unlike skills - which are instruction files your agent reads inline - a sub-agent is a separate agent instance launched for a focused job. It runs against the skills catalog, produces its output, and returns the result to the orchestrating session. The orchestrator continues with that output as context.

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#f8fafc', 'primaryBorderColor': '#cbd5e1', 'lineColor': '#64748b', 'clusterBkg': '#f1f5f9', 'clusterBorder': '#cbd5e1'}}}%%
flowchart LR
    classDef orchestrator fill:#1e293b,stroke:#0f172a,color:#f8fafc,font-weight:bold
    classDef subagent fill:#4f46e5,stroke:#3730a3,color:#fff,font-weight:bold
    classDef catalog fill:#7c3aed,stroke:#5b21b6,color:#fff
    classDef output fill:#166534,stroke:#14532d,color:#fff,font-weight:bold

    O["Your Claude Code session<br/>(orchestrator)"]:::orchestrator
    subgraph SA["Sub-Agent (spawned instance)"]
        direction LR
        Agent["Specialist agent"]:::subagent
        Cat["Skills catalog"]:::catalog
        Agent -- reads --> Cat
    end
    Out["Focused output<br/>returned to session"]:::output

    O -- "spawns" --> SA
    SA --> Out
    Out -- "informs" --> O

For other platforms (Codex, Cursor, Windsurf, Copilot, Gemini CLI), each sub-agent ships as a paired utility skill with dispatch instructions that replicate the same workflow in standard skill invocation mode.

🔗 More resources:

• Active Orchestration Guide - What sub-agents are, how Claude Code spawns them, the dispatch skill pattern for other platforms, and invocation examples for all five sub-agents.
• v2.16.0 Release Notes - The release that introduced active orchestration, including the rationale for the sub-agent model and how it connects to the broader skill ecosystem.

<a id="workflows"></a>

Workflows (skill chaining)

Workflows combine multiple skills into guided, end-to-end processes that mirror how experienced product managers actually work. Each workflow provides a sequence of skills with handoff guidance between steps so context flows naturally from discovery through delivery.

Ad-hoc chains and building your own. When no curated workflow fits, /chain runs any ordered sequence of skills against shared context (ephemeral, checkpointed by default; it routes to the pm-workflow-orchestrator engine). If a chain proves reusable, utility-pm-workflow-builder guides you from that chain (or a fresh idea) to a complete draft workflow packet, staged for review before anything lands in the repo.

Library Examples

Why Examples Matter More Than You Think

When you ask an AI to write a PRD, the output quality is anchored to its training data average. That average is mediocre. The examples in this library are the floor, not the ceiling. They are the quality signal your agent calibrates against before writing anything.

There are two layers of examples:

1. Skill-level EXAMPLE.md - every skill ships with a worked example sitting right next to the SKILL.md. This is what the agent reads at the moment it runs the skill.
2. Library samples (library/skill-output-samples/) - 200+ full outputs across three narrative threads. These are for you, not just the agent: read them before a skill run to calibrate expectations, or browse them to understand what a skill you haven't used actually produces.

Varied Prompt Maturity to Reflect Reality

The samples in this library intentionally vary in how polished the prompts are... Some use carefully structured, multi-turn context; others are more direct single invocations. This was a deliberate choice for two reasons:

• To reflect real life. The AI tooling landscape is evolving fast. Product managers are figuring out what works in real time. A library full of "perfect" prompts would misrepresent how most people actually work with AI today.
• To lower the bar for experimentation. The goal of this library is to encourage you to try, not to intimidate you with a gallery of polished outputs. If a sample was produced with a rough prompt and still looks good, that's a feature - it means the skill is doing the heavy lifting.

You'll find a natural range across the samples:

• Direct invocations with minimal context (most Brainshelf samples, early-stage framing)
• Single-turn invocations with a short briefing paragraph (most Storevine samples)
• Multi-step structured invocations with full context blocks (most Workbench ADR and stakeholder samples)

Browse the library to find the level of maturity that matches your current practice - then experiment upward from there.

Three Narrative Threads Across Three Fictional Companies

The library isn't a random collection of samples. It's organized around three fictional companies that each operate at a different stage, in a different industry, with different PM challenges. Every sample belongs to one of these threads so you can follow a company's product story across multiple skills.

Brainshelf - Early-Stage B2C Founder

• The company: Brainshelf builds a personal knowledge product - a tool for people who capture notes, articles, and ideas across too many apps and an never find them later. Think early-stage B2C, one PM who is also the founder, zero product-market fit certainty.
• Why this thread exists: Early-stage PM work looks different. Hypotheses are looser. Personas aren't validated by a research team. Foundation Sprints and lean canvases matter more than full PRDs. The Brainshelf samples show how to use PM skills when you have more questions than answers.
• Best samples to start with: define-hypothesis, tool-foundation-sprint-basics, discover-interview-synthesis, tool-foundation-sprint-founding-hypothesis

Storevine - Mid-Stage E-Commerce PM

• The company: Storevine is a mid-market e-commerce SaaS platform. The PM running the checkout-conversion program is three years into the role, works with an engineering team of six, and is accountable to experiment velocity and revenue-per-visit metrics.
• Why this thread exists: Most PM skill work happens in the middle: running experiments, measuring results, writing PRDs for known problems, aligning stakeholders on tradeoffs. The Storevine samples represent the bread-and-butter PM output at a company with enough scale to run rigorous tests but without so much bureaucracy that every artifact becomes a political battle.
• Best samples to start with: deliver-prd, measure-experiment-design, measure-okr-grader, define-opportunity-tree

Workbench - Internal-Tools PM at a Growing Org

• The company: Workbench is the internal tooling and platform team at a 200-person organization moving from startup to scale. The PM's "users" are internal employees and the "product" is the internal tooling layer - blueprints, automation, integrations.
• Why this thread exists: Internal-tools PM is its own discipline. Stakeholders are your co-workers. The cost of ignoring feedback is high because users are captive. ADRs matter more than press releases. Stakeholder updates go to department heads who have opinions. This thread shows PM skills applied to the least-glamorous-but-often-most-impactful area of product work.
• Best samples to start with: develop-adr, foundation-stakeholder-update, foundation-meeting-recap, iterate-retrospective

Browse the Library

Since product management is all about context, there are several ways for you to review the skills and outputs.

1. By skill - organized by skill name: library/skill-output-samples/
2. By company thread - follow one company's story across multiple skills:

3. By scenario - the "resurface" feature (Brainshelf), "campaigns" program (Storevine), and "blueprints" initiative (Workbench) recur across dozens of skills, so you can see how outputs connect and build on each other.

More resources:

• Skill Output Samples - All 200+ sample outputs organized by skill name. Browse to calibrate expectations before running a skill.
• Prompt Gallery - The prompts that generated many of the best library samples, annotated with what makes each one effective. A useful companion when you want to improve your own invocation patterns.

Learning and Resources

PM-Skills isn't just a skill repo. It ships with a full learning layer:

• Concept primers
• How-to guides
• Cheat sheets
• Case studies
• Recovery playbooks
• A prompt gallery
• ... and 200+ real sample outputs.

Learn the Methodologies

These guides explain the why behind the workshop frameworks and PM practices this library encodes:

• Foundation Sprint concept primer - A Foundation Sprint is a structured 2-day workshop methodology developed by Jake Knapp and John Zeratsky for aligning early-stage teams before design begins. This primer explains what it is, when to run one, how the 7 skills fit together, and how it relates to the Design Sprint.
• Design Sprint concept primer - A Design Sprint is a structured 5-day process for understanding a problem, sketching solutions, building a prototype, and testing with real users. This primer covers the Google Ventures heritage, the 5-day arc as implemented in this skill family, and how it differs from running a physical workshop.
• Sprint skills overview - An orientation to both workshop tool families: how Foundation Sprint and Design Sprint relate to each other, to the Triple Diamond framework, and to the rest of the PM-Skills catalog. Start here if you are new to either methodology.
• Workshop sprints vs agile sprints - If your team runs Scrum or any other agile framework, read this before running either workshop methodology. The word "sprint" means two completely different things in these two contexts, and confusing them is the most common source of friction for new users.

Use Skills Effectively

• Using skills guide - Foundational guide to invoking skills across different agents, passing context effectively, and getting consistent outputs. Covers invocation patterns, context blocks, and how to recover from incomplete outputs.
• Using workflows - How to run multi-skill chains, handle handoffs between skills so context flows correctly, and adapt workflow sequences to your team's specific process.
• Skill finder - Decision guide for finding the right skill when you know the outcome you need but not which skill to reach for. Organized by PM activity and phase.
• Skill comparisons - Side-by-side comparison of skills with overlapping scope: when to use problem-statement vs hypothesis vs opportunity-tree, and similar questions that come up repeatedly.
• Recipes - Common patterns and skill combinations for real PM scenarios: solo feature launch, quarterly OKR cycle, research-to-delivery arc, and more.
• Prompt gallery - Real prompts that produce excellent skill outputs, annotated with what makes each one work. A practical reference for getting better results immediately.

Foundation Sprint Resources

The Foundation Sprint tool family ships with five companion guides covering every stage of use:

• Using Foundation Sprint - Operational guide for running the complete 7-skill Foundation Sprint sequence with an agent. Covers facilitation patterns, what to do between steps, and output quality expectations for each skill.
• Foundation Sprint FAQ - Answers to the most common questions about the Foundation Sprint workshop methodology: who should be in the room, how long each step takes, what the founding hypothesis output looks like, and what to do with the brief.
• Foundation Sprint Cheat Sheet - One-page quick reference for the Foundation Sprint arc: skill sequence, key questions, and outputs. Print it or keep it open during a session.
• Foundation Sprint Case Studies - Three fictional scenarios (early-stage B2C, mid-market SaaS, internal tools) showing how different teams applied the Foundation Sprint at different stages and under different constraints.
• Foundation Sprint Recovery - What to do when a sprint goes sideways: confusing founding hypothesis, team disagreement on direction, a step that needs to be redone, or a situation where the readiness check was wrong.

Design Sprint Resources

The Design Sprint tool family ships with five companion guides:

• Using Design Sprint - Operational guide for running the 7-skill Design Sprint sequence with an agent. Covers what "realistic-enough" means for the prototype step, how to structure test-day interview sessions, and how to score results.
• Design Sprint FAQ - Questions about prototype fidelity, participant recruitment for test day, scoring criteria, and what to do when no clear winner emerges from testing.
• Design Sprint Cheat Sheet - One-page quick reference for the 5-day arc: skill sequence, daily outputs, and decision points.
• Design Sprint Case Studies - Fictional scenarios applying the Design Sprint to B2C product discovery, B2B feature validation, and an internal-tools redesign challenge.
• Design Sprint Recovery - What to do when prototype testing is inconclusive, the test fails entirely, the team wants to revisit the storyboard, or time constraints force adjustments.

Reference

• PM skill anatomy - The three-file structure every skill follows (SKILL.md, TEMPLATE.md, EXAMPLE.md) and what each file contributes to output quality. Essential before authoring a new skill.
• Agent skill anatomy - The general Agent Skills Specification anatomy that PM-Skills is built on. Useful context for understanding how skills work across the broader AI ecosystem.
• Mermaid style guide - Using the mermaid-diagrams skill to create consistent, on-brand diagrams. Includes the color palette, classDef patterns, and guidance on when to use LR vs TD layout.
• Sprint methodology glossary - Definitions for terms used across Foundation Sprint and Design Sprint skills. A useful reference when the meaning of a skill output or workshop term isn't clear.
• Workshop method comparison - Decision matrix for when to use Foundation Sprint vs Design Sprint vs other structured workshop approaches.
• Ecosystem overview - How pm-skills, pm-skills-mcp, and the skills CLI relate to each other; which to use for which client and workflow.
• How pm-skills is evaluated - The three eval lanes (trigger fixtures, the controlled router eval, LLM-judged output evals), what each measures, and the honest confound lesson behind why the router eval is the trustworthy instrument.
• Provenance and trust - What ships, what runs at install (nothing, except opt-in hooks), and the supply-chain posture behind every install path.

Project Status

At a Glance

Repo Structure

pm-skills/
├── skills/                  # 68 PM skills (30 phase, 11 foundation, 12 utility, 15 tool)
├── commands/                # Slash commands mapping to skills, workflows, and sub-agents
├── _workflows/              # Workflow chains: feature-kickoff, lean-startup, triple-diamond, and more
├── agents/                  # Sub-agent definitions (v2.16.0+, Claude Code plugin runtime)
├── hooks/                   # Claude Code hooks: house-rule guardrails + phase router (v2.25.0+)
├── library/                 # Sample output library (200+ real skill outputs)
├── scripts/                 # sync-claude, build-release, validate-commands, and CI scripts
├── .github/                 # CI workflows and automation
├── site/                    # Astro docs site, published to product-on-purpose.github.io/pm-skills
│   └── src/content/docs/    # getting-started, concepts, guides, reference, releases
├── docs/
│   └── templates/           # Canonical skill template (copy to author a new skill)
├── AGENTS.md                # Universal agent discovery file
├── CONTRIBUTING.md          # Contribution guidelines
└── CHANGELOG.md             # Version history

Key paths:

See project structure reference for detailed descriptions of every directory.

Changelog

See CHANGELOG.md for full details, or Recent Updates above for the latest highlights and links. The second changelog table that used to live here has folded into the generated Recent Updates mirror, so release history now lives in exactly one place in this file.

License

Distributed under the Apache License 2.0. See LICENSE for more information.

This means you can:

• Use PM-Skills commercially
• Modify and distribute
• Use privately
• Include in proprietary software

The only requirements are attribution and including the license notice.

Contributing

Contributions are what make the open-source community such a meaningful place to learn, create, and improve. Any contributions you make are greatly appreciated.

Quick contribution steps:

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingSkill)
3. Commit your changes using Conventional Commits (git commit -m 'feat: add amazing skill')
4. Push to the Branch (git push origin feature/AmazingSkill)
5. Open a Pull Request

Please read CONTRIBUTING.md for detailed guidelines on:

• Code of conduct
• Development process
• Skill contribution guidelines
• Testing requirements
• Documentation standards

Resources:

• Creating PM Skills - Authoring guide for new skills
• Skill Template - The expected three-file structure
• Security Policy - How to report a vulnerability, what's in scope, and what ships

Community

Have ideas for making PM-Skills better? Here are ways to contribute and connect:

💡 Feature Ideas

• Open a feature request to suggest new skills or improvements
• Join the Discussions to brainstorm with the community

🐞 Reporting Bugs. Please try to create bug reports that are:

• ✅ Reproducible - Include steps to reproduce the problem
• ✅ Specific - Include as much detail as possible (version, environment, etc.)
• ✅ Unique - Do not duplicate existing opened issues
• ✅ Scoped - One bug per report

📣 Spread the Word

• Give the repo a star if you find it useful
• Share PM-Skills on Twitter, LinkedIn, or your favorite PM community
• Write a blog post about how you use PM-Skills in your workflow

💬 Feedback

• Found something confusing? Open an issue
• Want to chat? Start a discussion

FAQ

Foundation Sprint is a 2-day strategic alignment workshop. It answers: "Do we know our problem, customer, and direction well enough to start designing?" Output: a founding hypothesis and a sprint brief.

Design Sprint is a 5-day prototype-and-test workshop. It answers: "Is this particular solution right for this particular problem?" Output: a prototype and test results.

Run a Foundation Sprint first if you don't have strong conviction on the problem space. Run a Design Sprint when you have the problem defined and need to validate a solution approach. Neither of these is an agile iteration sprint.

See Foundation Sprint vs Design Sprint and Workshop Sprints vs Agile Sprints for detailed comparisons.

No. You can use individual skills as needed. Each skill is self-contained and works independently. If you only need PRDs, just reference skills/deliver-prd/. The workflows are optional guides, not requirements.

Yes, with some limitations. Copy the contents of any SKILL.md file into your ChatGPT conversation as context and ask it to follow the skill instructions. ChatGPT doesn't support the Agent Skills Specification natively, so you won't get automatic skill discovery or slash commands. For the best experience, use Claude Code, GitHub Copilot, Cursor, or Windsurf.

Fork the repository and modify the SKILL.md, TEMPLATE.md, or EXAMPLE.md files to match your team's standards. You can add company-specific sections, change terminology, or adjust the output format. The Apache 2.0 license allows commercial use and modification.

Skills are atomic units - each produces one PM artifact (a PRD, a hypothesis, user stories, etc.). Workflows chain multiple skills together in a recommended sequence. Use skills when you need a specific output; use workflows when you want guided end-to-end processes.

Skills are instruction files (SKILL.md + TEMPLATE.md + EXAMPLE.md) that your agent reads inline when you invoke a slash command. The agent doing the work IS your current session.

Sub-agents are separate agent instances that Claude Code spawns as sub-tasks. When you invoke a sub-agent, a new agent context is launched for that specific job, runs against the skills catalog, returns its output to your session, and exits. This separation is useful for tasks that benefit from a clean context - like adversarial review, where the same session that wrote the artifact might not be the best critic.

Sub-agents are currently Claude Code-only. For other platforms, the same four capabilities ship as paired utility skills you invoke like any other skill.

Watch the GitHub Releases page for new versions, or use the /pm-skills:utility-update-pm-skills slash command from within your agent to check for and apply updates. Major releases are summarized in the Recent Updates section above.

The openskills CLI discovers skills in .claude/skills/ directories. PM-Skills ships a flat skills/{phase-skill}/ structure plus a sync helper. Clone the repo and run ./scripts/sync-claude.sh (or .ps1) to populate .claude/skills/ locally, and openskills or Claude Code discovery will find all skills.

Yes. Read the authoring guide for the full process. Submit a proposal via GitHub issue first, then create your skill following the template structure. All contributions are reviewed for quality and alignment with PM best practices.

Slash commands (like /pm-skills:deliver-prd or /pm-skills:define-hypothesis) are shortcuts that invoke the corresponding skill. When you type /pm-skills:deliver-prd "my feature", Claude Code reads the skill instructions from skills/deliver-prd/SKILL.md and generates output following the template. No additional setup required after install; the commands are defined in the commands/ directory.

pm-skills (this repo) is the source skill library with all 68 PM skills as markdown files. Best for Claude Code slash commands, file browsing, and customization.

pm-skills-mcp wraps the same skills in an MCP server for programmatic access. Best for Claude Desktop, Cursor, and any MCP-compatible client when you want tool-based invocation rather than slash commands.

Both give you access to the same skills; choose based on your preferred client and workflow. See the Ecosystem Overview for a detailed comparison.

About the Author

Howdy, I'm Jonathan Prisant, a product leader/manager/nerd in the church technology space who gets unreasonably excited about understanding and solving problems, serving humans, designing elegant systems, and getting stuff done. I enjoy optimizing and scaling workflows more than is probably healthy - not because I'm particularly fond of "business process definition," but because I think in systems and value the outcomes of increased effectiveness and efficiency.

I am a follower of Jesus Christ, grateful husband, proud (and exhausted) daddy, D&D geek, 3D printing enthusiast, formerly-consistent strength trainer, smart home enthusiast, insatiable learner, compulsive tech-experimenter, and a bunch of other things. I have too many projects going on across too many domains - but hopefully you find this open-source repo helpful and useful.

If PM-Skills has helped you ship better products, consider giving the repo a star and sharing it with your team.