# How the 9 PM Skills Plugins Group Skills and Commands by Product Management Domain

> Explore how the 9 PM Skills plugins organize skills and commands by product management domain. Discover modules mirroring the PM lifecycle from discovery to go-to-market.

- Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills)
- Tags: how-to-guide
- Published: 2026-06-12

---

**The 9 PM Skills plugins organize 68 skills and 42 commands into domain-specific modules that mirror the product management lifecycle, from discovery and strategy to execution, analytics, and go-to-market.**

The `phuryn/pm-skills` repository structures product management expertise into nine independent plugins, each targeting a specific phase of the product lifecycle. This domain-driven architecture ensures that **skills** (reusable knowledge components) and **commands** (automated workflows) are grouped logically, allowing teams to install only the capabilities they need via the [`.claude-plugin/marketplace.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/marketplace.json) manifest.

## The Nine Product Management Domains

The plugins map directly to the classic product-management lifecycle, with each module containing a dedicated set of skills and commands:

| Plugin | Domain Phase | Skills | Key Commands |
|--------|-------------|--------|--------------|
| **pm-product-discovery** | Discovery & validation | 13 skills including idea generation, assumption mapping, opportunity-solution-tree, interview scripts | `/discover`, `/brainstorm`, `/triage-requests`, `/interview`, `/setup-metrics` |
| **pm-product-strategy** | Vision & strategic planning | 12 skills including product vision, value-proposition, SWOT, Porter’s Five Forces, pricing | `/strategy`, `/business-model`, `/value-proposition`, `/market-scan`, `/pricing` |
| **pm-execution** | Execution & delivery | 16 skills including PRD authoring, OKR brainstorming, road-mapping, sprint planning, retrospectives | `/write-prd`, `/plan-okrs`, `/transform-roadmap`, `/sprint`, `/pre-mortem`, `/red-team-prd`, `/meeting-notes`, `/stakeholder-map`, `/write-stories`, `/test-scenarios`, `/generate-data` |
| **pm-market-research** | User & market research | 7 skills including personas, segmentation, journey maps, market sizing, competitor analysis | `/research-users`, `/competitive-analysis`, `/analyze-feedback` |
| **pm-data-analytics** | Data-driven insights | 3 skills including SQL query generation, cohort analysis, A/B-test analysis | `/write-query`, `/analyze-cohorts`, `/analyze-test` |
| **pm-go-to-market** | Launch & growth | 6 skills including GTM strategy, beachhead segment, ICP, growth loops, battlecard | `/plan-launch`, `/growth-strategy`, `/battlecard` |
| **pm-marketing-growth** | Marketing & growth metrics | 5 skills including marketing-ideas, positioning, product naming, North-Star metric | `/market-product`, `/north-star` |
| **pm-toolkit** | Utility & support tools | 4 skills including resume review, NDA drafting, privacy-policy, grammar check | `/review-resume`, `/tailor-resume`, `/draft-nda`, `/privacy-policy`, `/proofread` |
| **pm-ai-shipping** | AI-built code shipping | 2 skills including shipping-artifacts, intended-vs-implemented gap analysis | `/ship-check`, `/document-app`, `/derive-tests`, `/security-audit-static`, `/performance-audit-static` |

*Data sourced from the repository's root* [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) *and individual plugin documentation.*

## Architectural Organization of Skills and Commands

### Plugin Structure and Namespacing

Each plugin operates as an independent namespace under its own folder `pm-{name}`. According to the repository structure, every plugin contains:

- A [`.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/plugin.json) manifest defining the plugin's name, version, author, and description
- A dedicated [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) documenting domain-specific skills and commands
- Self-contained functionality that never references external plugin resources

This independence allows selective installation. For example, a startup focusing on early-stage validation can install only `pm-product-discovery` and `pm-product-strategy` without importing execution or analytics modules.

### Skill Definitions

Skills are individual markdown files stored at `skills/<skill-name>/SKILL.md` within each plugin directory. The [`pm-product-discovery/skills/opportunity-solution-tree/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/opportunity-solution-tree/SKILL.md) file exemplifies the universal front-matter format that makes skills consumable by any AI assistant.

Skills can be force-loaded using the syntax `/plugin-name:skill-name` or simply `/skill-name` when the context is clear. Each skill is purpose-built for a specific PM activity, such as `pricing-strategy` in the strategy domain or `cohort-analysis` in analytics.

### Command Workflows

Commands are markdown files located at `commands/<command-name>.md` that describe multi-step workflows chaining one or more skills within the same plugin. When invoked (e.g., `/discover`), the assistant sequentially runs the associated skills, prompting the user at each stage.

Importantly, **commands never reference skills in other plugins**, enforcing strict domain boundaries. The [`pm-product-discovery/commands/discover.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/commands/discover.md) file demonstrates how a command chains four skills: `brainstorm-ideas`, `identify-assumptions`, `prioritize-assumptions`, and `brainstorm-experiments`.

## Invoking Domain-Specific Workflows

Install the entire marketplace or select specific domains using the Claude Code CLI:

```bash

# Install the complete marketplace (all 9 plugins)

claude plugin marketplace add phuryn/pm-skills

# Install specific domains only

claude plugin install pm-product-discovery@pm-skills
claude plugin install pm-execution@pm-skills

```

Run domain-specific workflows by invoking the command associated with each phase:

```bash

# Discovery phase: Run full discovery workflow

/discover AI-powered meeting summarizer for remote teams

# Strategy phase: Create product strategy canvas

/strategy B2B project-management tool for agencies

# Execution phase: Draft a PRD for a new feature

/write-prd Smart notification system that reduces alert fatigue

# Analytics phase: Generate SQL queries

/write-query Show me monthly active users by country for Q4 2025 (BigQuery)

# AI Shipping phase: Validate shipped code

/ship-check the payments service

```

Each command automatically loads the relevant skills from its respective plugin directory. For instance, `/write-prd` runs the `create-prd` skill from `pm-execution` and suggests follow-up commands like `/plan-okrs`.

## Summary

- The **9 plugins** mirror the product management lifecycle: Discovery, Strategy, Execution, Market Research, Data Analytics, Go-to-Market, Marketing & Growth, Utility Toolkit, and AI Shipping.
- **68 skills** are stored as markdown files in `skills/<skill-name>/SKILL.md` with standardized front-matter for AI consumption.
- **42 commands** are defined in `commands/<command-name>.md` as workflows that chain domain-specific skills without cross-plugin dependencies.
- Each plugin maintains independence through its own [`.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/plugin.json) manifest, enabling modular installation via the marketplace.
- Commands like `/discover`, `/strategy`, and `/write-prd` provide immediate access to domain expertise without requiring manual skill selection.

## Frequently Asked Questions

### How do I install only specific product management domains from the pm-skills repository?

You can install individual plugins using the Claude Code CLI with the syntax `claude plugin install pm-plugin-name@pm-skills`. For example, run `claude plugin install pm-product-discovery@pm-skills` to install only the discovery domain, or `claude plugin install pm-data-analytics@pm-skills` for analytics capabilities. This modular approach prevents loading unnecessary skills and commands.

### What is the difference between a skill and a command in the pm-skills plugins?

**Skills** are atomic, reusable knowledge components stored in `skills/<skill-name>/SKILL.md` that encode specific PM methodologies (e.g., opportunity-solution-tree mapping). **Commands** are executable workflows stored in `commands/<command-name>.md` that automate multi-step processes by chaining multiple skills together. When you type `/discover`, you invoke a command that runs several skills sequentially.

### Can commands reference skills from other plugins?

No. According to the repository architecture, commands remain strictly self-contained within their respective plugins. A command in `pm-product-discovery` cannot load skills from `pm-execution`, ensuring domain boundaries remain clear and plugins function independently. This design prevents dependency conflicts and keeps the marketplace modular.

### How are the skills and commands documented within each plugin?

Each plugin contains a [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) file in its root directory (e.g., [`pm-product-strategy/README.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/README.md)) that lists all available skills and commands for that domain. Additionally, every skill and command has its own markdown file with detailed usage instructions. The root [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) provides a comprehensive overview of all 68 skills and 42 commands across the nine plugins.