# How Many Chained Workflows Are Available in pm-skills? > Discover the 42 chained workflows in the phuryn/pm-skills repository. Explore 9 distinct plugins designed to streamline your development process. - Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills) - Tags: how-to-guide - Published: 2026-06-29 --- **The pm-skills repository provides 42 chained workflows across 9 independent plugins, as explicitly documented in the project's README.** The pm-skills repository is an open-source collection of product management automation tools that structures its capabilities into discrete skills and high-level orchestrated workflows. According to the repository's documentation in [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md), the project maintains exactly **42 chained workflows** distributed across **9 independent plugins**, working alongside 68 individual PM skills. These workflows function as markdown-based command files that chain multiple skills into cohesive, end-to-end product management processes. ## What Are Chained Workflows in pm-skills? In the pm-skills architecture, **chained workflows** are high-level commands implemented as markdown files that sequence multiple individual skills into complete business processes. Unlike single skills that perform isolated tasks, these workflows connect dependencies—such as brainstorming, assumption identification, and prioritization—using declarative markdown syntax to deliver automated product management capabilities. The repository organizes these workflows under plugin-specific `commands/` directories, ensuring each of the 9 plugins maintains its own domain-specific workflow library while contributing to the total count of 42. ## The 42 Chained Workflows Across 9 Plugins As stated in line 10 of [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md): > "68 PM skills and **42 chained workflows** across 9 plugins." This distribution ensures that each plugin focuses on a specific domain of product management—such as discovery, execution, or toolkit utilities—while the aggregated 42 workflows provide comprehensive coverage of PM automation needs. ### Repository Structure for Workflow Files Each plugin maintains its workflows in a dedicated `commands/` folder. Key locations documented in the source include: - `pm-product-discovery/commands/` - Contains discovery-phase workflows - `pm-execution/commands/` - Houses execution-phase workflows like PRD generation - `pm-toolkit/commands/` - Stores utility workflows for administrative tasks ### Example Workflow Implementations **Discover Workflow** ([`pm-product-discovery/commands/discover.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/commands/discover.md)) This workflow chains four distinct skills into a complete discovery process: ```markdown # Discover workflow – chains four skills: # brainstorm-ideas → identify-assumptions → prioritize-assumptions → brainstorm-experiments /discover ``` **Write PRD Workflow** ([`pm-execution/commands/write-prd.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/write-prd.md)) This command generates Product Requirements Documents by sequencing: ```markdown # Write a Product Requirements Document (PRD) – chains: # product-vision → product-strategy → user-stories → test-scenarios /write-prd ``` **Toolkit Workflows** (`pm-toolkit/commands/*.md`) The toolkit plugin contains multiple utility workflows for tasks such as resume tailoring and privacy policy generation, each implemented as markdown files following the same chaining pattern. ## How to Invoke Chained Workflows While the workflow files reside as markdown documents in the repository's `commands/` directories, they are invoked through the CLI using slash-prefixed commands. The workflow file defines the skill chain, and the execution engine processes the sequence: ```markdown # Prioritize features – chains: # prioritize-features → prioritize-assumptions → prioritize-experiments /prioritize-features ``` Each markdown file in the `commands/` folders represents one of the 42 available chained workflows, providing a declarative approach to complex product management automation. ## Summary - The pm-skills repository contains exactly **42 chained workflows** distributed across **9 independent plugins** - These workflows are implemented as markdown files located in `commands/` subdirectories within each plugin - According to the source code, the repository pairs these 42 workflows with **68 individual PM skills** - Example workflows include [`discover.md`](https://github.com/phuryn/pm-skills/blob/main/discover.md) in `pm-product-discovery/commands/` and [`write-prd.md`](https://github.com/phuryn/pm-skills/blob/main/write-prd.md) in `pm-execution/commands/` - Workflows chain multiple skills together using markdown-based command definitions stored in plugin-specific directories ## Frequently Asked Questions ### What is the difference between skills and chained workflows in pm-skills? Individual skills in pm-skills represent discrete, single-purpose capabilities—such as brainstorming ideas or identifying assumptions. **Chained workflows** orchestrate these individual skills into sequential processes, using markdown command files to define execution order and dependencies. While the repository offers 68 individual skills, the 42 chained workflows combine these into end-to-end automation for product management tasks. ### Where are the chained workflow files located in the repository? The 42 chained workflows are distributed across plugin-specific `commands/` directories. For example, discovery workflows reside in `pm-product-discovery/commands/`, execution workflows in `pm-execution/commands/`, and utility workflows in `pm-toolkit/commands/`. Each workflow is implemented as a standalone markdown file (e.g., [`discover.md`](https://github.com/phuryn/pm-skills/blob/main/discover.md), [`write-prd.md`](https://github.com/phuryn/pm-skills/blob/main/write-prd.md)) within these folders. ### How many plugins contain the 42 chained workflows? The 42 chained workflows are distributed across exactly **9 independent plugins**, as documented in the repository's README. This modular architecture allows users to install only the plugins relevant to their specific product management needs while maintaining access to the complete workflow library. ### What file format are the chained workflows written in? All 42 chained workflows are implemented as **markdown files** (`.md`) containing command definitions and skill orchestration logic. These markdown files reside in the `commands/` subdirectories of each respective plugin and define the workflow chains using declarative syntax that references the underlying PM skills.