Getting Started

Fastest path (one command)

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

Installs all 63 skills into your agent’s default skills directory. Works with Claude Code, Cursor, GitHub Copilot, Cline, and any agent supported by the open skills CLI. Shipped in v2.11.1 and now the recommended install path.

Alternative: Clone-based Quick Start (3 steps)

Clone or download the latest ZIP: git clone https://github.com/product-on-purpose/pm-skills.git (or get the ZIP from Releases).
(Claude Code/openskills only) Run the sync helper to populate .claude/skills and .claude/commands:
- macOS/Linux: ./scripts/sync-claude.sh
- Windows: ./scripts/sync-claude.ps1
Use a slash command: /prd "Feature description" or /hypothesis "Assumption to test".

Prefer the full walkthrough? Read on.

Welcome to PM-Skills! This guide will help you understand what this repository offers and how to use it, regardless of your technical background.

What is PM-Skills?
Core Concepts
Ways to Use PM-Skills
Method 1: Claude Code (Slash Commands)
Method 2: Git Clone (Any AI Assistant)
Method 3: Claude.ai / Claude Desktop
Method 4: Copy-Paste (Universal)
Method 5: openskills CLI
Choosing the Right Method
Your First Skill
Workflows
Troubleshooting
Next Steps

What is PM-Skills?

PM-Skills is an open-source collection of 63 product management skills that teach AI assistants how to create professional PM documents. The current repo includes 26 phase skills, 8 foundation skills, 10 utility skills, plus the v2.15.0 tool classification (Foundation Sprint family of 7, Design Sprint family of 7, and the tool-note-and-vote standalone). Think of it as a playbook that transforms generic AI responses into polished, consistent PM artifacts.

The Problem It Solves

Without PM-Skills:

You: "Write me a PRD"
AI: *Produces a generic document missing key sections, inconsistent format*

With PM-Skills:

You: "Write me a PRD"
AI: *Produces a comprehensive PRD with problem statement, success metrics,
    user stories, scope boundaries, technical considerations.all in a
    professional, consistent format*

What You Get

63 skills in skills/ covering the PM lifecycle (26 phase skills + 8 foundation skills + 10 utility skills)
Professional templates based on industry best practices
Real-world examples showing what good looks like
Works with any AI assistant (Claude, ChatGPT, Copilot, etc.)

Core Concepts

What are Skills?

A skill is a structured instruction set that teaches an AI assistant how to create a specific type of PM artifact.

For Non-Technical Users

Think of a skill like a recipe card for an AI chef:

The instructions tell the AI what questions to ask and what sections to include
The template shows the exact format to use
The example demonstrates what a great result looks like

When you ask the AI to create a PRD, it reads the “PRD recipe” and follows it step by step.

For Technical Users

Each skill is a directory containing:

skills/<skill-name>/
├── SKILL.md              # Prompt instructions for the AI
├── references/
│   ├── TEMPLATE.md       # Output structure/format
│   └── EXAMPLE.md        # Annotated real-world example

The SKILL.md file contains:

YAML frontmatter with metadata (name, description, version, updated, license, and either phase or classification)
Structured instructions the AI follows
Guidance on information gathering and output formatting

Skills follow the Agent Skills Specification for interoperability across AI platforms.

What are Slash Commands?

A slash command is a shortcut that invokes a skill in AI assistants that support them.

For Non-Technical Users

Instead of typing:

“Please use the PRD skill to create a product requirements document for a search feature”

You can simply type:

/prd search feature for e-commerce platform

The slash (/) tells the AI “use this skill” and everything after is your context.

For Technical Users

Slash commands are defined in the commands/ directory as markdown files:

---
description: Create a Product Requirements Document
---

Use the `prd` skill to create a comprehensive Product Requirements Document.

Read the skill instructions from `skills/<skill-name>/SKILL.md` and follow them.

Context from user: $ARGUMENTS

The $ARGUMENTS variable captures everything typed after the command name.

Note: Slash commands are platform-specific. They work natively in Claude Code but require different invocation methods on other platforms.

How Skills and Commands Relate

flowchart TD
    A["/prd 'search feature'\nSlash Command"] --> C["SKILL.md\nInstructions"]
    B["'Use the prd skill for...'\nNatural Language"] --> C
    C --> D["TEMPLATE.md\nStructure"]
    C --> E["EXAMPLE.md\nQuality Reference"]
    C --> F["Your Context"]
    D --> G["AI-Generated\nPM Artifact"]
    E --> G
    F --> G

Key insight: Skills are the underlying content. Commands are just one way to invoke them.

Ways to Use PM-Skills

Method	Best For	Setup Time	Technical Level
Claude Code	Developers using Claude Code	None	Low
Git Clone	Copilot, Cursor, Windsurf users	1 minute	Low
Claude.ai	Claude web/desktop users	2 minutes	Low
Copy-Paste	Any AI (ChatGPT, etc.)	None	None
openskills CLI	Advanced users managing multiple skill sets	5 minutes	Medium

Method 1: Claude Code (Slash Commands)

Best for: Developers using Claude Code CLI or IDE extension

For Non-Technical Users

If you’re using Claude Code, skills work automatically. Just type a slash command:

/prd "Search feature for our e-commerce platform"

That’s it! Claude will create a full PRD using the skill.

For Technical Users

How It Works

Claude Code discovers the registered skill set via AGENTS.md and command definitions in commands/. The full repo catalog lives under skills/, including any path-only skills that have not been wired into AGENTS.md or slash commands yet.

Setup

Navigate to a directory containing pm-skills (clone it or work within the repo)
Start using slash commands immediately

Usage

# Basic usage
/prd "feature description"

# With more context
/prd "We need a search feature for our e-commerce platform.
      Users currently can't find products easily.
      Target: 20% improvement in product discovery."

# Chain skills
/problem-statement "checkout abandonment issue"
# ... review output ...
/hypothesis "from the problem statement above"
# ... review output ...
/prd "based on the hypothesis above"

Available Commands

The repo currently ships 73 command markdown files: 60 skill commands, 10 workflow commands, and 3 sub-agent companion commands.

Phase	Commands
Discover	`/interview-synthesis`, `/competitive-analysis`, `/stakeholder-summary`
Define	`/problem-statement`, `/hypothesis`, `/opportunity-tree`, `/jtbd-canvas`
Develop	`/solution-brief`, `/spike-summary`, `/adr`, `/design-rationale`
Deliver	`/prd`, `/user-stories`, `/acceptance-criteria`, `/edge-cases`, `/launch-checklist`, `/release-notes`
Measure	`/experiment-design`, `/instrumentation-spec`, `/dashboard-requirements`, `/experiment-results`, `/okr-grader`
Iterate	`/retrospective`, `/lessons-log`, `/refinement-notes`, `/pivot-decision`
Utility	`/pm-skill-builder`, `/pm-skill-validate`, `/pm-skill-iterate`, `/mermaid-diagrams`, `/slideshow-creator`, `/update-pm-skills`
Foundation	`/persona`, `/lean-canvas`, `/okr-writer`, `/stakeholder-update`, `/meeting-agenda`, `/meeting-brief`, `/meeting-recap`, `/meeting-synthesize`

Plus workflows: /workflow-feature-kickoff, /workflow-customer-discovery, /workflow-sprint-planning, /workflow-product-strategy, /workflow-post-launch-learning, /workflow-stakeholder-alignment, /workflow-technical-discovery

Method 2: Git Clone (Any AI Assistant)

Best for: GitHub Copilot, Cursor, Windsurf, and other AGENTS.md-compatible tools

For Non-Technical Users

Download the repository:
- Go to github.com/product-on-purpose/pm-skills
- Click the green “Code” button
- Click “Download ZIP”
- Unzip to a folder you’ll remember
Open in your coding tool:
- Open VS Code, Cursor, or your editor
- Open the pm-skills folder
Use the skills:
- Your AI assistant will automatically see the skills
- Ask: “Use the prd skill to create a PRD for [your feature]“

For Technical Users

Setup

# Clone the repository
git clone https://github.com/product-on-purpose/pm-skills.git

# Or add as a submodule to your project
git submodule add https://github.com/product-on-purpose/pm-skills.git .pm-skills

How It Works

Modern AI coding assistants discover skills through the AGENTS.md file at the repository root. This file:

Lists all 63 registered skills with paths and descriptions
Provides workflows
Documents available commands

When you ask the AI to use a skill, it:

Reads AGENTS.md to locate the skill
Reads SKILL.md for instructions
Reads TEMPLATE.md and EXAMPLE.md from references
Generates output following the instructions

Usage

You: "Use the prd skill to create a PRD for adding dark mode"

AI: *Reads skills/deliver-prd/SKILL.md and follows the instructions*

Or reference skills directly:

You: "Read skills/deliver-prd/SKILL.md and create a PRD for dark mode"

Keeping Updated

# If cloned directly
cd pm-skills
git pull origin main

# If using submodule
git submodule update --remote .pm-skills

Method 3: Claude.ai / Claude Desktop

Best for: Users of Claude’s web interface or desktop application

For Non-Technical Users

Download the skills:
- Go to the Releases page
- Download the latest pm-skills-vX.X.X.zip file
Upload to Claude:
- Open Claude.ai or Claude Desktop
- Go to Settings (gear icon)
- Find Projects or Capabilities
- Click Add files or Upload
- Select the ZIP file you downloaded
Use the skills:
- In any conversation, type: “Use the prd skill to create a PRD for [your feature]”
- Claude will read the skill files and follow them

For Technical Users

Setup Options

Option A: Project Knowledge

Create a new Project in Claude
Upload skill files to Project Knowledge
Skills persist across conversations in that project

Option B: Conversation Upload

Upload individual skill files at conversation start
Reference them: “Using the uploaded prd skill…”

Structuring Uploads

For best results, upload:

The specific SKILL.md you need
Its references/TEMPLATE.md
Its references/EXAMPLE.md

Or upload the entire skills/ directory if your use case varies.

Usage

You: "I've uploaded the prd skill. Please use it to create a PRD
      for a feature that adds collaborative editing to our docs app."

Claude: *Reads the skill files and produces a structured PRD*

Method 4: Copy-Paste (Universal)

Best for: Any AI assistant (ChatGPT, Gemini, local LLMs, etc.)

For Non-Technical Users

This method works with any AI.no setup required.

Find the skill you need:
- Go to github.com/product-on-purpose/pm-skills
- Navigate to skills/ → choose a skill (names are prefixed by phase, e.g., deliver-prd)
- Example: skills/deliver-prd/
Copy the skill content:
- Click on SKILL.md
- Click “Raw” to see plain text
- Select all and copy (Ctrl+A, Ctrl+C)
Paste into your AI:
- Start a new chat
- Paste the skill content
- Add your request: “Now create a PRD for [your feature]”
Optional: Add template and example:
- Also copy references/TEMPLATE.md for structure
- Copy references/EXAMPLE.md for quality reference

For Technical Users

Minimal Copy-Paste

[Paste contents of SKILL.md]

---

Now use these instructions to create a PRD for: [your context]

Full Copy-Paste (Recommended)

# SKILL INSTRUCTIONS
[Paste contents of SKILL.md]

# OUTPUT TEMPLATE
[Paste contents of references/TEMPLATE.md]

# QUALITY EXAMPLE
[Paste contents of references/EXAMPLE.md]

---

Using the above skill instructions, template, and example as reference,
create a PRD for: [your context]

Automating Copy-Paste

Create a script to concatenate files:

#!/bin/bash
# Usage: ./get-skill.sh prd

SKILL=$1
cat skills/$SKILL/SKILL.md
echo -e "\n---\n# TEMPLATE\n"
cat skills/$SKILL/references/TEMPLATE.md
echo -e "\n---\n# EXAMPLE\n"
cat skills/$SKILL/references/EXAMPLE.md

Method 5: openskills CLI

Best for: Power users managing multiple skill repositories

For Non-Technical Users

This method requires comfort with command-line tools. If that’s not you, use one of the earlier methods instead.

For Technical Users

Prerequisites

Node.js 18+ installed
npm or yarn

Setup

# Install openskills globally
npm install -g openskills

# Install pm-skills
openskills install product-on-purpose/pm-skills

# Sync to your environment
openskills sync

Known Issues

Note: openskills previously had issues with nested directories. pm-skills now ships flat skills/phase-skill/ plus a sync helper that populates .claude/skills/. After cloning, run ./scripts/sync-claude.sh (or .ps1) before using openskills or Claude Code.

Usage

Once installed, skills are available globally:

# List installed skills
openskills list

# Use in conversations
# Skills are auto-discovered by compatible AI assistants

Managing Multiple Skill Sets

# Install additional skill repositories
openskills install another-org/their-skills

# Update all skills
openskills update

# Remove a skill set
openskills remove product-on-purpose/pm-skills

Choosing the Right Method

Decision Tree

flowchart TD
    A{"Using Claude Code?"} -- Yes --> M1["Method 1\nSlash Commands"]
    A -- No --> B{"Using Copilot,\nCursor, or Windsurf?"}
    B -- Yes --> M2["Method 2\nGit Clone"]
    B -- No --> C{"Using Claude.ai\nor Claude Desktop?"}
    C -- Yes --> M3["Method 3\nZIP Upload"]
    C -- No --> D{"Quick, one-time use?"}
    D -- Yes --> M4["Method 4\nCopy-Paste"]
    D -- No --> M5["Method 5\nopenskills CLI"]

Comparison Matrix

Feature	Claude Code	Git Clone	Claude Upload	Copy-Paste	openskills
Setup time	None	1 min	2 min	None	5 min
Slash commands	Yes	No	No	No	Varies
Auto-updates	Yes	Manual	Manual	N/A	Yes
Works offline	Yes	Yes	Yes	Yes	Yes
Any AI platform	No	Most	Claude only	Yes	Most
Skill chaining	Easy	Easy	Medium	Hard	Easy

Your First Skill

Let’s walk through using a skill for the first time.

Scenario

You’re starting a new feature and want to create a proper problem statement.

Step 1: Choose Your Method

Pick the method that matches your setup (see above).

Step 2: Invoke the Skill

Claude Code:

/problem-statement "Users are abandoning checkout because the process
is too long. We lose about $50k/month in abandoned carts."

Other AI assistants:

Use the problem-statement skill to create a problem statement for:
Users are abandoning checkout because the process is too long.
We lose about $50k/month in abandoned carts.

Step 3: Provide More Context

The AI will likely ask clarifying questions:

Who specifically experiences this problem?
What have you tried before?
What constraints exist?

Answer these to improve the output.

Step 4: Review and Iterate

The AI produces a structured problem statement. Review it and ask for:

More detail in specific sections
Different framing
Additional considerations

Step 5: Chain to Next Skill

Once satisfied, use another skill:

Now use the hypothesis skill to create a testable hypothesis
based on this problem statement.

Workflows

Workflows are pre-defined sequences of skills for common PM processes.

Feature Kickoff Workflow

Use when: Starting a new feature from scratch

Skills included:

problem-statement → Frame the problem
hypothesis → Define testable assumptions
prd → Specify requirements
user-stories → Break down for engineering
launch-checklist → Prepare for release

Invocation:

# Claude Code
/workflow-feature-kickoff "New search feature for e-commerce platform"

# Other assistants
"Run the feature kickoff workflow for: [your feature]"

Lean Startup Workflow

Use when: Rapid experimentation and validation

Skills included:

hypothesis → State your assumption
experiment-design → Plan validation
experiment-results → Analyze outcomes
pivot-decision → Decide next steps

Triple Diamond Workflow

Use when: Comprehensive product development

Skills included: All 26 phase skills across 6 phases

Additional Workflows (v2.9.0)

Workflow	Command	Use When
Customer Discovery	`/workflow-customer-discovery`	Transforming raw research into a validated problem
Sprint Planning	`/workflow-sprint-planning`	Preparing sprint-ready stories from a backlog
Product Strategy	`/workflow-product-strategy`	Framing a major strategic initiative
Post-Launch Learning	`/workflow-post-launch-learning`	Measuring results and capturing learnings after launch
Stakeholder Alignment	`/workflow-stakeholder-alignment`	Getting leadership buy-in before committing resources
Technical Discovery	`/workflow-technical-discovery`	Evaluating technical feasibility and architecture

See _workflows/ directory for detailed workflow documentation.

Troubleshooting

”The AI doesn’t seem to know about the skills”

Cause: Skills aren’t properly loaded or discovered.

Solutions:

Ensure AGENTS.md is visible to the AI
Try explicit paths: “Read skills/deliver-prd/SKILL.md”
Upload files directly in Claude.ai/Desktop
Check that you’re in the correct directory

”The output doesn’t match the template”

Cause: AI didn’t read the template file.

Solutions:

Explicitly reference the template: “Use the template in references/TEMPLATE.md”
Upload/paste the template alongside the skill
Ask: “Reformat the output to match the template structure"

"The AI asks too many questions”

Cause: Not enough context provided upfront.

Solutions:

Provide more detail in your initial request
Include: who, what, why, constraints, prior attempts
Pre-answer common questions in your prompt

”Slash commands aren’t working”

Cause: Platform doesn’t support them or commands aren’t discovered.

Solutions:

Verify you’re using Claude Code (not Claude.ai)
Check commands/ directory exists
Use natural language: “Use the prd skill…” instead

”I get different results each time”

Cause: AI variance is normal; context matters.

Solutions:

Provide consistent, detailed context
Save good outputs as additional examples
Use the same conversation thread for related artifacts

Next Steps

Learn More

Categories Reference . Understand skill organization
Frontmatter Schema . Technical skill structure
Triple Diamond Framework . The organizing methodology

Explore Skills

Browse by phase:

Discover: interview-synthesis, competitive-analysis, stakeholder-summary
Define: problem-statement, hypothesis, opportunity-tree, jtbd-canvas
Develop: solution-brief, spike-summary, adr, design-rationale
Deliver: prd, user-stories, edge-cases, launch-checklist, release-notes
Measure: experiment-design, instrumentation-spec, dashboard-requirements, experiment-results
Iterate: retrospective, lessons-log, refinement-notes, pivot-decision

Contribute

Have ideas for new skills or improvements?

See contribution guidelines in README (Contributing section)
Open an issue on GitHub
Submit a pull request

Quick Reference Card

Skill Invocation Cheat Sheet

Platform	How to Invoke
Claude Code	`/skill-name "context"`
Copilot/Cursor	”Use the skill-name skill to…”
Claude.ai	Upload ZIP, then “Use the skill-name skill to…”
ChatGPT/Other	Copy-paste SKILL.md, then “Create a…”

Most-Used Skills

Need	Skill	Command
Define the problem	problem-statement	`/problem-statement`
Write requirements	prd	`/prd`
Create user stories	user-stories	`/user-stories`
Plan an experiment	experiment-design	`/experiment-design`
Prepare for launch	launch-checklist	`/launch-checklist`

Skill → Output Mapping

Skill	Produces
problem-statement	Problem framing document
prd	Product Requirements Document
user-stories	User stories with acceptance criteria
hypothesis	Testable hypothesis statement
experiment-design	A/B test plan
retrospective	Team retro summary with actions

Built by Product on Purpose for PMs who ship.

Getting Started

Table of Contents

What is PM-Skills?

The Problem It Solves

What You Get

Core Concepts

What are Skills?

For Non-Technical Users

For Technical Users

What are Slash Commands?

For Non-Technical Users

For Technical Users

How Skills and Commands Relate

Ways to Use PM-Skills

Method 1: Claude Code (Slash Commands)

For Non-Technical Users

For Technical Users

How It Works

Setup

Usage

Available Commands

Method 2: Git Clone (Any AI Assistant)

For Non-Technical Users

For Technical Users

Setup

How It Works

Usage

Keeping Updated

Method 3: Claude.ai / Claude Desktop

For Non-Technical Users

For Technical Users

Setup Options

Structuring Uploads

Usage

Method 4: Copy-Paste (Universal)

For Non-Technical Users

For Technical Users

Minimal Copy-Paste

Full Copy-Paste (Recommended)

Automating Copy-Paste

Method 5: openskills CLI

For Non-Technical Users

For Technical Users

Prerequisites

Setup

Known Issues

Usage

Managing Multiple Skill Sets

Choosing the Right Method

Decision Tree

Comparison Matrix

Your First Skill

Scenario

Step 1: Choose Your Method

Step 2: Invoke the Skill

Step 3: Provide More Context

Step 4: Review and Iterate

Step 5: Chain to Next Skill

Workflows

Feature Kickoff Workflow

Lean Startup Workflow

Triple Diamond Workflow

Additional Workflows (v2.9.0)

Troubleshooting

”The AI doesn’t seem to know about the skills”

”The output doesn’t match the template”

"The AI asks too many questions”

”Slash commands aren’t working”

”I get different results each time”

Next Steps

Learn More

Explore Skills

Contribute

Quick Reference Card

Skill Invocation Cheat Sheet

Most-Used Skills

Skill → Output Mapping