PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth.
PM Skills Marketplace is a collection of 68 product management skills and 42 chained workflows organized across 9 thematic plugins, covering the full PM lifecycle from discovery and strategy through execution, go-to-market, and shipping AI-built code. It integrates with Claude Code via the CLI plugin system and with Claude Cowork via the in-app plugin browser, where all 9 plugins install in a single step from the GitHub handle `phuryn/pm-skills`. Skills encode frameworks from practitioners like Teresa Torres and Marty Cagan, and commands chain multiple skills together into guided processes; for example, `/discover` sequences four skills covering idea brainstorming, assumption identification, assumption prioritization, and experiment design. Product managers, founders, and teams doing structured product work are the primary audience. A notable detail is that the plugins are also installable on OpenAI's Codex CLI using identical syntax, though slash commands there must be invoked through plain-language descriptions rather than direct command calls.
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Healthy fork ratio
- ✓Clear description
- ✓Topics declared
- ✓Documented (README)
/plugin marketplace add phuryn/pm-skills
/plugin install pm-skills24 items en este repositorio
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'
Identify growth loops (flywheels) for sustainable traction. Evaluates 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral. Use when designing growth mechanisms, building product-led traction, or understanding how growth loops work.
Resumen de Plugins
 [](https://github.com/phuryn/pm-skills/blob/main/LICENSE) [](https://github.com/phuryn/pm-skills/blob/main/CONTRIBUTING.md) [](https://github.com/phuryn/pm-brain) # PM Skills Marketplace: The AI Operating System for Better Product Decisions > 68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code.  Designed for Claude Code and Cowork. Skills compatible with other AI assistants. ## Start Here New idea? → `/discover` Need strategic clarity? → `/strategy` Writing a PRD? → `/write-prd` Planning a launch? → `/plan-launch` Defining metrics? → `/north-star` If this project helps you, ⭐ the repo. ## Why PM Skills Marketplace? Generic AI gives you text. PM Skills Marketplace gives you structure. Each skill encodes a proven PM framework — discovery, assumption mapping, prioritization, strategy — and walks you through it step by step. You get the rigor of Teresa Torres, Marty Cagan, and Alberto Savoia built into your daily workflow, not sitting on a bookshelf. The result: better product decisions, not just faster documents. ## How It Works (Skills, Commands, Plugins)  **Skills** are the building blocks of the marketplace. Each skill gives Claude domain knowledge, analytical frameworks, or a guided workflow for a specific PM task. Some skills also work as reusable foundations that multiple commands share. Skills are loaded automatically when relevant to the conversation — no explicit invocation needed. If needed (e.g., prioritizing skills over general knowledge), you can **force loading skills** with `/plugin-name:skill-name` or `/skill-name` (Claude will add the prefix). **Commands** are user-triggered workflows invoked with `/command-name`. They chain one or more skills into an end-to-end process. For example, `/discover` chains four skills together: brainstorm-ideas → identify-assumptions → prioritize-assumptions → brainstorm-experiments. **Plugins** group related skills and commands into installable packages. Each plugin covers a PM domain — discovery, strategy, execution, and so on. Installing the marketplace gives you all 9 plugins at once. Commands use skills. Some skills serve multiple commands. Some skills (like `prioritization-frameworks` or `opportunity-solution-tree`) are standalone references that Claude draws on whenever relevant — no command needed. Commands are designed to flow into each other, matching the PM workflow. After any command completes, it suggests relevant next commands — just follow the prompts. ## Installation ### Claude Cowork (recommended for non-developers) 1. Open **Customize** (bottom-left) 2. Go to **Browse plugins** → **Personal** → **+** 3. Select **Add marketplace from GitHub** 4. Enter: `phuryn/pm-skills` All 9 plugins install automatically. You get both commands (`/discover`, `/strategy`, etc.) and skills.  ### Claude Code (CLI) ```bash # Step 1: Add the marketplace claude plugin marketplace add phuryn/pm-skills # Step 2: Install individual plugins claude plugin install pm-toolkit@pm-skills claude plugin install pm-product-strategy@pm-skills claude plugin install pm-product-discovery@pm-skills claude plugin install pm-market-research@pm-skills claude plugin install pm-data-analytics@pm-skills claude plugin install pm-marketing-growth@pm-skills claude plugin install pm-go-to-market@pm-skills claude plugin install pm-execution@pm-skills claude plugin install pm-ai-shipping@pm-skills ``` ### Codex CLI (OpenAI) Codex reads the same plugin marketplace file as Claude Code, so you can install PM Skills natively — no conversion or file-copying needed: ```bash # Step 1: Add the marketplace codex plugin marketplace add phuryn/pm-skills # Step 2: Install the plugins you want codex plugin add pm-toolkit@pm-skills codex plugin add pm-product-strategy@pm-skills codex plugin add pm-product-discovery@pm-skills codex plugin add pm-market-research@pm-skills codex plugin add pm-data-analytics@pm-skills codex plugin add pm-marketing-growth@pm-skills codex plugin add pm-go-to-market@pm-skills codex plugin add pm-execution@pm-skills codex plugin add pm-ai-shipping@pm-skills ``` **What you get:** every skill (the PM frameworks), available to Codex and invocable by name. Install whole plugins rather than cherry-picking individual skills — a workflow usually relies on several skills that ship together. **What's different from Claude Code:** the `/slash` commands (`/discover`, `/write-prd`, …) install but don't run as Codex slash commands — Codex plugins don't expose commands. To run a workflow, just describe the steps in plain language, for example: > Run product discovery on *[your idea]*: brainstorm options, map assumptions, prioritize the risky ones, then design experiments — pause between each step. **Optional — let Codex turn the workflows into skills.** Because the command files ship inside each installed plugin, you can ask Codex to convert the ones you use most: > Read the command files in the pm-execution plugin and create equivalent Codex skills for the workflows I use most often. This is a best-effort, model-driven conversion (some Claude-specific command syntax won't translate), but it's a quick way to get the guided workflows on Codex without leaving the CLI. ### Other AI assistants (skills only) The `skills/*/SKILL.md` files follow the universal skill format and work with any tool that reads it. Commands (`/slash-commands`) are Claude-specific. | Tool | How to use | What works | |------|-----------|------------| | **Gemini CLI** | Copy skill folders to `.gemini/skills/` | Skills only | | **OpenCode** | Copy skill folders to `.opencode/skills/` | Skills only | | **Cursor** | Copy skill folders to `.cursor/skills/` | Skills only | | **Kiro** | Copy skill folders to `.kiro/skills/` | Skills only | ```bash # Example: copy all skills for OpenCode (project-level) for plugin in pm-*/; do mkdir -p .opencode/skills/ cp -r "$plugin/skills/"* .opencode/skills/ 2>/dev/null done # Example: copy all skills for Gemini CLI (global) for plugin in pm-*/; do cp -r "$plugin/skills/"* ~/.gemini/skills/ 2>/dev/null done ``` --- ## Available Plugins <details> <summary><strong>1. pm-product-discovery</strong> — Ideation, experiments, assumption testing, OSTs, interviews (13 skills, 5 commands)</summary> **Skills (13):** - `brainstorm-ideas-existing` — Multi-perspective ideation for existing products (PM, Designer, Engineer) - `brainstorm-ideas-new` — Ideation for new products in initial discovery - `brainstorm-experiments-existing` — Design experiments to test assumptions for existing products - `brainstorm-experiments-new` — Design lean startup pretotypes for new products (Alberto Savoia) - `identify-assumptions-existing` — Identify risky assumptions across Value, Usability, Viability, and Feasibility - `identify-assumptions-new` — Identify risky assumptions across 8 risk categories including Go-to-Market, Strategy, and Team - `prioritize-assumptions` — Prioritize assumptions using an Impact × Risk matrix with experiment suggestions - `prioritize-features` — Prioritize a feature backlog based on impact, effort, risk, and strategic alignment - `analyze-feature-requests` — Analyze and categorize customer feature requests by theme and strategic fit - `opportunity-solution-tree` — Build an Opportunity Solution Tree (Teresa Torres) — outcome → opportunities → solutions → experiments - `interview-script` — Create a structured customer interview script with JTBD probing questions - `summarize-interview` — Summarize an interview transcript into JTBD, satisfaction signals, and action items - `metrics-dashboard` — Design a product metrics dashboard with North Star, input metrics, and alert thresholds **Commands (5):** - `/discover` — Full discovery cycle: ideation → assumption mapping → prioritization → experiment design - `/brainstorm` — Multi-perspective ideation (`ideas|experiments` × `existing|new`) - `/triage-requests` — Analyze and prioritize a batch of feature requests - `/interview` — Prepare an interview script or summarize a transcript (`prep|summarize`) - `/setup-metrics` — Design a product metrics dashboard **Examples:** Skills: - `What are the riskiest assumptions for our AI writing assistant idea?` - `Help me build an Opportunity Solution Tree for improving user activation` - `Prioritize these 12 feature requests from our enterprise customers [attach CSV]` Commands: - `/discover AI-powered meeting summarizer for remote teams` - `/brainstorm experiments existing — We need to reduce churn in our onboarding flow` - `/interview prep — We're interviewing enterprise buyers about their procurement workflow` </details> <details> <summary><strong>2. pm-product-strategy</strong> — Vision, business models, pricing, competitive landscape (12 skills, 5 commands)</summary> Product strategy, vision, business models, pricing, and macro environment analysis. Covers the full strategic toolkit from vision crafting through competitive landscape scanning. **Skills (12):** - `product-strategy` — Comprehensive 9-section Product Strategy Canvas (vision → defensibility) - `startup-canvas` — Startup Canvas combining Product Strategy (9 sections) + Business Model — an alternative to BMC and Lean Canvas for new products - `product-vision` — Craft an inspiring, achi
Lo que la gente pregunta sobre pm-skills
¿Qué es phuryn/pm-skills?
+
phuryn/pm-skills es plugins para el ecosistema de Claude AI. PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. Tiene 17k estrellas en GitHub y se actualizó por última vez 6d ago.
¿Cómo se instala pm-skills?
+
Puedes instalar pm-skills clonando el repositorio (https://github.com/phuryn/pm-skills) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar phuryn/pm-skills?
+
Nuestro agente de seguridad ha analizado phuryn/pm-skills y le ha asignado un Trust Score de 100/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.
¿Quién mantiene phuryn/pm-skills?
+
phuryn/pm-skills es mantenido por phuryn. La última actividad registrada en GitHub es de 6d ago, con 24 issues abiertos.
¿Hay alternativas a pm-skills?
+
Sí. En ClaudeWave puedes explorar plugins similares en /categories/plugins, ordenados por popularidad o actividad reciente.
Despliega pm-skills en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/phuryn-pm-skills)<a href="https://claudewave.com/repo/phuryn-pm-skills"><img src="https://claudewave.com/api/badge/phuryn-pm-skills" alt="Featured on ClaudeWave: phuryn/pm-skills" width="320" height="64" /></a>Más Plugins
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A Claude Code plugin that shows what's happening - context usage, active tools, running agents, and todo progress
Create beautiful slides on the web using a coding agent's frontend skills
A 100% free modern JS SaaS boilerplate (React, NodeJS, Prisma). Full-featured: Auth (email, google, github, slack, MS), Email sending, Background jobs, Landing page, Payments (Stripe, Polar.sh), Shadcn UI, S3 file upload. AI-ready with tailored AGENTS.md, skills, and Claude Code plugin. One cmd deploy. Powered by Wasp full-stack framework.
A theoretical reconstruction of the Claude Mythos architecture, built from first principles using the available research literature.