# How the phuryn/pm-skills Project Is Structured: A Claude Plugin Marketplace > Explore the modular structure of the phuryn/pm-skills project. Discover how each directory functions as a self-contained Claude plugin marketplace with skills, commands, and metadata. - Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills) - Tags: architecture - Published: 2026-06-18 --- **The phuryn/pm-skills repository functions as a modular marketplace of nine Claude plugins, where each top-level directory contains self-contained skills, slash commands, and JSON metadata that Claude Code and Claude Cowork discover automatically.** The phuryn/pm-skills project structure organizes product management expertise into a discoverable plugin ecosystem. Built as a **Claude plugin marketplace**, the repository enables AI assistants to load atomic PM skills and execute complex workflows through slash commands. Each plugin operates as an independent module, allowing users to install specific capabilities or the entire suite based on their product lifecycle needs. ## Repository Architecture Overview The root level of the repository serves as the marketplace index. A **global README** ([`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) lines 6-78) provides installation instructions and catalogs all nine available plugins. Below this, nine top-level folders—`pm-toolkit`, `pm-product-strategy`, `pm-product-discovery`, `pm-market-research`, `pm-data-analytics`, `pm-go-to-market`, `pm-marketing-growth`, `pm-execution`, and `pm-ai-shipping`—each function as independent plugins. This design follows a **self-contained plugin pattern**. Every folder includes all assets necessary for Claude to register and execute the plugin's capabilities without cross-dependencies. Users install the entire marketplace via `claude plugin marketplace add phuryn/pm-skills`, after which Claude parses each plugin's metadata and exposes its commands. ## Plugin Anatomy: The Four Core Components Each plugin in the phuryn/pm-skills repository follows a strict four-part structure that defines how skills are documented, stored, and invoked. ### 1. Plugin Documentation (README.md) Located at `//README.md`, this file provides human-readable context about the plugin's purpose, its contained skills, and available commands. It serves as the entry point for users browsing the repository on GitHub or reviewing plugin capabilities within Claude. ### 2. Atomic Skills (SKILL.md) The `//skills/*/SKILL.md` paths contain markdown files describing single, atomic product management capabilities. Each **SKILL.md** file defines a framework, template, or analysis routine—such as [`pm-execution/skills/create-prd/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/create-prd/SKILL.md) for PRD generation or [`pm-product-strategy/skills/value-proposition/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/skills/value-proposition/SKILL.md) for value proposition design. Claude loads these automatically when a relevant command is invoked. ### 3. Slash Commands (*.md) Stored in `//commands/*.md`, these files define slash-command workflows that chain one or more skills into end-to-end processes. For example, [`pm-execution/commands/write-prd.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/write-prd.md) chains the `create-prd` skill with user input handling, while [`pm-product-discovery/commands/discover.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/commands/discover.md) orchestrates the full discovery workflow from brainstorming to experiment design. ### 4. Plugin Metadata (plugin.json) The `//.claude-plugin/plugin.json` file acts as the machine-readable manifest. This JSON configuration tells Claude Code and Claude Cowork which skills and commands the plugin exposes, enabling automatic discovery and registration within the AI assistant's environment. ## The Nine Plugin Categories The repository organizes product management expertise into nine functional domains: - **pm-toolkit**: General utilities including `draft-nda`, `privacy-policy`, `grammar-check`, and `review-resume` skills. These provide office-type functions not tied to specific product lifecycle stages. - **pm-product-strategy**: Strategic frameworks including product vision, lean canvas, business model canvas, SWOT, PESTLE, Porter's five forces, and Ansoff matrix analysis. - **pm-product-discovery**: Ideation and validation tools covering brainstorming, assumption identification, prioritization, interview scripts, opportunity solution trees, and metrics dashboards. - **pm-market-research**: User and competitive analysis capabilities including user personas, market segmentation, journey maps, market sizing, and sentiment analysis. - **pm-data-analytics**: Data-driven PM functions such as SQL query generation, cohort analysis, and A/B test analysis. - **pm-go-to-market**: Launch planning with beachhead segment identification, ideal customer profiles, growth loops, and competitive battlecards. - **pm-marketing-growth**: Positioning and metrics including marketing ideas, value proposition statements, product naming, and North Star metric definition. - **pm-execution**: Day-to-day delivery workflows including PRD generation, OKR planning, roadmap transformation, sprint planning, retrospectives, user stories, and red-team strategy. - **pm-ai-shipping**: AI-specific shipping artifacts including `intended-vs-implemented` analysis and shipping documentation for AI-generated codebases. ## Installation and Usage Examples Install the complete marketplace using the Claude CLI: ```bash claude plugin marketplace add phuryn/pm-skills ``` Once installed, invoke full workflows using slash commands: ```markdown /discover AI-powered meeting summarizer for remote teams ``` This command triggers the discovery workflow from `pm-product-discovery`, chaining brainstorming, assumption identification, and prioritization skills. Generate product requirements using the execution plugin: ```markdown /write-prd Smart notification system that reduces alert fatigue ``` This executes the command defined in [`pm-execution/commands/write-prd.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/write-prd.md), which loads the `create-prd` skill from [`pm-execution/skills/create-prd/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/create-prd/SKILL.md). Plan a go-to-market strategy: ```markdown /plan-launch AI code review tool targeting mid-size engineering teams ``` Validate AI-generated code shipping: ```markdown /ship-check the payments service ``` This runs the `pm-ai-shipping` plugin to generate documentation, static security audits, and performance audits. ## Key Implementation Files Understanding the phuryn/pm-skills project structure requires examining these specific implementation paths: - **[`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md)** (root): Line 6-78 contains the marketplace overview and installation instructions. - **[`pm-toolkit/README.md`](https://github.com/phuryn/pm-skills/blob/main/pm-toolkit/README.md)**: Demonstrates lightweight utility plugin structure with minimal skill sets. - **[`pm-execution/skills/create-prd/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/create-prd/SKILL.md)**: The core PRD template skill referenced by multiple commands. - **[`pm-execution/commands/write-prd.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/write-prd.md)**: Concrete implementation showing how commands wrap skills. - **[`pm-ai-shipping/.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/pm-ai-shipping/.claude-plugin/plugin.json)**: Exemplifies the metadata format required for plugin registration. - **[`pm-product-strategy/skills/business-model/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/skills/business-model/SKILL.md)**: Shows how strategic frameworks are documented as skills. These files illustrate the **markdown-driven architecture** that separates skill definitions (what Claude knows) from command implementations (how users invoke that knowledge). ## Summary - The phuryn/pm-skills repository is organized as a **marketplace of nine Claude plugins**, each occupying a top-level directory. - Every plugin contains **four standardized components**: a [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md), `skills/*/SKILL.md` files, `commands/*.md` files, and a [`.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/plugin.json) manifest. - **Skills** are atomic markdown files describing PM frameworks, while **commands** orchestrate workflows that chain multiple skills. - The repository supports installation via `claude plugin marketplace add phuryn/pm-skills`, making all nine plugins available immediately. - This modular structure enables users to leverage specific capabilities like `/write-prd` or `/discover` without configuring complex dependencies. ## Frequently Asked Questions ### What is the phuryn/pm-skills project structure? The phuryn/pm-skills project structure is a **Claude plugin marketplace** consisting of nine top-level directories, each representing an independent plugin. Every plugin follows a standardized internal structure containing documentation ([`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md)), atomic skill definitions (`skills/*/SKILL.md`), workflow commands (`commands/*.md`), and machine-readable metadata ([`.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/plugin.json)). This design allows Claude Code and Claude Cowork to automatically discover and load product management capabilities on demand. ### How do I install the phuryn/pm-skills plugins? Install the entire marketplace by running `claude plugin marketplace add phuryn/pm-skills` in your Claude Code or Claude Cowork environment. This single command registers all nine plugins and their respective slash commands immediately. You do not need to install individual plugins separately; the marketplace architecture handles selective loading based on which commands you invoke. ### What is the difference between a skill and a command in pm-skills? **Skills** are atomic markdown files located at `//skills/*/SKILL.md` that define specific product management frameworks or templates—such as creating a PRD or running a SWOT analysis. **Commands** are workflow orchestrators stored in `//commands/*.md` that chain one or more skills into user-facing slash commands like `/write-prd` or `/discover`. Skills represent the knowledge base; commands represent the user interface. ### How do I add a new plugin to the pm-skills marketplace? To extend the marketplace, create a new top-level folder with the four required components: a [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) describing the plugin's purpose, a `skills/` directory containing [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files for each capability, a `commands/` directory with markdown files defining slash commands, and a [`.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/plugin.json) manifest registering the plugin with Claude. Follow the existing structure in `pm-toolkit` or `pm-ai-shipping` as reference implementations.