PM decision frameworks and callable skills
PM Skills Marketplace is compiled by Paweł Huryn from his The Product Compass newsletter. It contains 9 plugins, 68 skills and 42 commands, turning common PM frameworks such as opportunity solution trees, risk-assumption matrices, Lean Canvas, PRD, OKR, GTM and North Star Metric into structured workflows loadable by Claude Code and Claude Cowork.
It is neither a new IDE nor an LLM replacement. A Skill is structured guidance for a PM task, automatically loaded when relevant; force-load one with /外掛名:技能名 or /技能名. Commands are manually called with slashes, such as /discover, /strategy, /write-prd, /plan-launch and /north-star.
Workflows are repeatable; 9 plugins cover discovery, strategy, execution, market research, data analytics, launch, marketing growth, a toolkit and AI shipping. Commands chain according to typical PM work rhythms and suggest the next command after completion. The marketplace is also designed to work with PM Brain, a Markdown second brain.
Discovery
Strategy
Research
Execution
Go-to-Market
Growth
Marketplace registration and plugin installation
First add the marketplace, then install the plugins you need. Choose plugins for your current work stage; you do not need all nine. These are the Claude Cowork and Claude Code CLI procedures.
Claude Cowork (official recommendation)
Use the interface without a command line: ① Open Customize at the lower left → ② Browse plugins → Personal → + → ③ Add marketplace from GitHub → ④ Enter phuryn/pm-skills.
Claude Code (CLI)
Add the marketplace, then install needed plugins individually:
# Add the marketplace
claude plugin marketplace add phuryn/pm-skills
# Install the plugins you need (you can select just a few)
claude plugin install pm-product-discovery@pm-skills
claude plugin install pm-product-strategy@pm-skills
claude plugin install pm-market-research@pm-skills
claude plugin install pm-execution@pm-skills
claude plugin install pm-data-analytics@pm-skills
claude plugin install pm-go-to-market@pm-skills
claude plugin install pm-marketing-growth@pm-skills
claude plugin install pm-toolkit@pm-skills
claude plugin install pm-ai-shipping@pm-skillsCodex CLI (OpenAI)
OpenAI Codex and other assistants are compatible. Replace claude with codex and install with add:
codex plugin marketplace add phuryn/pm-skills
codex plugin add pm-product-discovery@pm-skills
codex plugin add pm-product-strategy@pm-skills
# ...install the remaining plugins with codex plugin add <plugin-name>@pm-skillsProduct stages and plugins
9 stage-specific plugins contain 68 skills and 42 commands. Each card names a plugin, its stage and its skill and command counts. Install according to your current work without installing all nine.
Discovery · 01
pm-product-discovery
Product discovery
Brainstorm ideas, design experiments to validate assumptions, prioritize assumptions with Impact × Risk, build opportunity solution trees, write interview scripts, plan metric dashboards and prioritize feature backlogs. 13 skills · 5 commands.
Strategy · 02
pm-product-strategy
Product strategy
Define vision and value propositions, build Lean Canvas/Business Model Canvas/Startup Canvas, plan pricing and monetization, perform Porter five forces/SWOT/PESTLE analysis and use the Ansoff growth matrix. 12 skills · 5 commands.
Market research · 03
pm-market-research
Market research
Create personas from research, segment by behavior and JTBD, map customer journeys, estimate TAM/SAM/SOM and analyze competitors and sentiment from user feedback. 7 skills · 3 commands.
Execution · 04
pm-execution
Product execution
Write complete PRDs, brainstorm team OKRs, build outcome-oriented roadmaps, plan sprints and retrospectives, generate release notes and pre-mortems, map stakeholders, write user/job stories and test scenarios, and red-team plan assumptions. 16 skills · 11 commands.
Data analytics · 05
pm-data-analytics
Data analytics
Generate SQL from natural language, analyze retention and engagement cohorts, and evaluate A/B results with statistical significance. 3 skills · 3 commands.
Launch · 06
pm-go-to-market
Launch strategy
Build complete GTM strategy and channel messaging, find beachhead segments, define ICPs, design sustainable growth loops and create competitive battlecards. 6 skills · 3 commands.
Marketing growth · 07
pm-marketing-growth
Marketing growth
Brainstorm low-cost marketing, develop differentiated positioning, write value propositions, name products from brand values and define North Star Metric with supporting input metrics. 5 skills · 2 commands.
Toolkit · 08
pm-toolkit
PM toolkit
Review and revise PM resumes, draft NDAs and privacy policies, and check grammar and logic. Everyday miscellaneous tools. 4 skills · 5 commands.
AI shipping · 09
pm-ai-shipping
AI shipping
Create reviewable documentation for AI-built applications, audit security and performance gaps, inspect test coverage and compile evidence-backed shipping packets. 2 skills · 5 commands.
Common commands
Call commands manually with slashes; they suggest the next step after completion. These commands cover a PM workflow:
| Command | Purpose | Example |
|---|---|---|
/discover | Full discovery cycle | /discover 給遠端團隊的 AI 會議摘要工具 |
/strategy | Complete product strategy canvas | /strategy 給代理商用的 B2B 專案管理工具 |
/write-prd | Create a PRD | /write-prd 降低警示疲勞的智慧通知系統 |
/plan-launch | Complete GTM strategy | /plan-launch 鎖定中型工程團隊的 AI 程式碼審查工具 |
/north-star | Define North Star Metric | Continue the strategy conversation to define the main metric and input metrics |
Skill and command triggers
These tips follow the official README, covering triggers, command chaining and companion tools. Skills load when relevant to a conversation, so memorizing command names is optional.
Skills load automatically without memorizing names
Skills load when relevant. Force-load with /外掛名:技能名 or /技能名; ordinary questions also trigger them, such as "What is the biggest risk assumption for our AI writing assistant?"
Source · Official README
Commands chain and suggest next steps
Commands match typical PM work rhythms. /discover completes discovery, /strategy provides a strategy canvas and /write-prd defines requirements; completion suggests suitable follow-up commands.
Source · Official README
Install by stage instead of all nine
Plugins are split by product stage. Start discovery and strategy with pm-product-discovery and pm-product-strategy; add pm-execution for execution and pm-go-to-market before launch.
Source · Official README · Installation
Commands as workflow entry points
Use five commands across the workflow, /discover, /strategy, /write-prd, /plan-launch and /north-star. Each includes a full cycle or canvas to turn an idea into structured output.
Source · Official README · Examples
Persistent knowledge with PM Brain
The marketplace is designed to work with PM Brain, a Markdown second brain. Save discovery and strategy output there to accumulate a product knowledge base across sessions.
Source · Official README
Share skills across assistants
The common skills-only format supports Claude Code, Cowork, Codex, Gemini CLI, OpenCode, Cursor and Kiro. Workflows continue when switching assistants.
Source · Official README · Compatibility
Idea discovery and launch planning example
You want an AI meeting-summary tool for remote teams but have not defined target customers or differentiation. Use /discover for discovery, /strategy for a strategy canvas, /write-prd for requirements and /plan-launch for launch planning. Every command suggests the next step after completion.
$ You › /discover An AI meeting-summary tool for remote teams
claude: Claude(product discovery)›
Don't rush to define features. I will guide you through a discovery cycle:
assumptions, risks, and opportunities, then decide what to build.
[Impact × Risk matrix · the three assumptions to validate first]
hl: 1. Remote teams will give meeting recordings to a third-party tool (high risk)
hl: 2. "Summaries" are the pain point, rather than "identifying action items" (high risk)
3. Users will pay instead of using built-in free summaries (medium risk)
[Opportunity solution tree · work backward from outcomes]
Outcome: No action items missed after meetings
├─ Opportunity: Summaries are too long for anyone to read
└─ Opportunity: Action items have no assigned owners
ok: Recommendation: Validate assumption 2 first. Narrow the initial focus to
ok: "automatically extracting action items with owners", rather than general summaries.
$ You › /strategy
claude: Claude ›
Complete the strategy canvas using the discovery findings:
· Customer segment: Remote SaaS teams of 15–50 people
· Value proposition: Action items with owners as soon as a meeting ends
· Differentiation: Task-system integration, instead of text summaries alone
· Monetization: Pricing by workspace seat
$ You › /write-prd Automatically extract meeting action items with owners
claude: Claude ›
Produce a PRD: problem statement, goals and non-goals, user story,
success metrics, edge cases, and open questions.
hl: Success metrics: Action-item adoption rate ≥ 60%, higher completion rate within 24 hours after meetings
$ You › /plan-launch Target remote SaaS teams
ok: Beachhead: Remote teams already using task systems
ok: Channels: Integration marketplaces + founder communities
ok: North Star: Number of action items adopted per week
Four commands take a one-sentence idea to a launch plan with an ICP and growth loops. Each step's output is the next step's input.
Command chaining and stage outputs
Chaining passes discovery conclusions into strategy, positioning into the PRD and PRD scope into the launch plan. Each command suggests the next step according to the product workflow, avoiding independent runs.
Skills turn opportunity solution trees, Lean Canvas, PRD and GTM into repeatable steps. Decisions remain your responsibility; the steps ensure each stage's questions are asked and outputs retained.
Decision responsibility when using frameworks
PM skills workflow integration
After installation, integrate skills into existing product workflows instead of using them only for one-off questions.
Advanced uses
1. Start each stage with commands. Begin new features with /discover, then continue with /strategy, /write-prd and /plan-launch after decisions, retaining structured outputs from every discussion.
2. Trigger individual skills with questions. Full commands are optional for each task. Ask "What is the biggest risk assumption for our AI writing assistant?" to load the relevant skill for an ad hoc decision.
3. Accumulate knowledge in PM Brain. The marketplace is designed to work with PM Brain, a Markdown second brain. Store personas, competitor analysis and strategy canvases for reuse across projects.
4. Share skills across assistants. The common format supports Codex, Gemini CLI, OpenCode, Cursor and Kiro. Teams can share PM frameworks across different tools.
5. Choose plugins for team stages. Use pm-product-discovery and pm-market-research during discovery; pm-execution and pm-data-analytics during delivery; pm-go-to-market and pm-marketing-growth during launch.
Further reading
① github.com/phuryn/pm-skills: Marketplace source, complete plugin and command lists, and installation instructions. ② The Product Compass newsletter: Source of the frameworks and PM methodology. ③ LICENSE in the repo: MIT terms.
Skills organize frameworks, and commands chain workflows. The decisions remain yours. It ensures that the questions for each stage are not missed.