pm-skills Documentation

Technical Documentation: phuryn/pm-skills

ℹ️ Provenance: Multi-Tier Ingestion · CodeWiki Reference

Overview (`README.md`) Copy Section

PM Skills Marketplace: The AI Operating System for Better Product Decisions

69 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 Copy Chapter

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? Copy Chapter

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) Copy Chapter

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 Copy Chapter

Claude Cowork (recommended for non-developers) Copy Section

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) Copy Section

# 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) Copy Section

Codex reads the same plugin marketplace file as Claude Code, so you can install PM Skills natively — no conversion or file-copying needed:

# 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) Copy Section

The skills/*/SKILL.md files follow the universal skill format and work with any tool that reads it. Commands (/slash-commands) are Claude-specific.

# 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 Copy Chapter

1. pm-product-discovery — Ideation, experiments, assumption testing, OSTs, interviews (13 skills, 5 commands)

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

2. pm-product-strategy — Vision, business models, pricing, competitive landscape (12 skills, 5 commands)

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, achievable, and emotional product vision
• value-proposition — 6-part JTBD value proposition (Who, Why, What before, How, What after, Alternatives)
• lean-canvas — Lean Canvas business model for startups and new products
• business-model — Business Model Canvas with all 9 building blocks
• monetization-strategy — Brainstorm 3–5 monetization strategies with validation experiments
• pricing-strategy — Pricing models, competitive analysis, willingness-to-pay, and price elasticity
• swot-analysis — SWOT analysis with actionable recommendations
• pestle-analysis — Macro environment: Political, Economic, Social, Technological, Legal, Environmental
• porters-five-forces — Competitive forces analysis (rivalry, suppliers, buyers, substitutes, new entrants)
• ansoff-matrix — Growth strategy mapping across markets and products

Commands (5):

• /strategy — Create a complete 9-section Product Strategy Canvas
• /business-model — Explore business models (lean|full|startup|value-prop|all)
• /value-proposition — Design a value proposition using the 6-part JTBD template
• /market-scan — Macro environment analysis combining SWOT + PESTLE + Porter's + Ansoff
• /pricing — Design a pricing strategy with competitive analysis and experiments

Examples:

Skills:

• Compare Lean Canvas vs Business Model Canvas vs Startup Canvas for my marketplace startup
• Design a value proposition for our AI writing assistant targeting non-native English speakers
• Run a Porter's Five Forces analysis for the project management SaaS market

Commands:

• /strategy B2B project management tool for agencies
• /business-model startup — AI writing tool for non-native English speakers
• /value-proposition SaaS onboarding tool for enterprise customers

3. pm-execution — PRDs, OKRs, roadmaps, sprints, retros, release notes, stakeholder management (16 skills, 11 commands)

Day-to-day product management: PRDs, OKRs, roadmaps, sprints, retrospectives, release notes, pre-mortems, stakeholder management, user stories, and prioritization frameworks.

Skills (16):

• create-prd — Lean 8-section PRD template (a fuller spec on request)
• brainstorm-okrs — Team-level OKRs aligned with company objectives
• outcome-roadmap — Transform a feature list into an outcome-focused roadmap
• sprint-plan — Sprint planning with capacity estimation, story selection, and risk identification
• retro — Structured sprint retrospective facilitation
• release-notes — User-facing release notes from tickets, PRDs, or changelogs
• pre-mortem — Risk analysis with Tigers/Paper Tigers/Elephants classification
• stakeholder-map — Power × Interest grid with tailored communication plan
• summarize-meeting — Meeting transcript → decisions + action items
• user-stories — User stories following the 3 C's and INVEST criteria
• job-stories — Job stories: When [situation], I want to [motivation], so I can [outcome]
• wwas — Product backlog items in Why-What-Acceptance format
• test-scenarios — Test scenarios: happy paths, edge cases, error handling
• dummy-dataset — Realistic dummy datasets as CSV, JSON, SQL, or Python
• prioritization-frameworks — Reference guide to 9 prioritization frameworks (Opportunity Score, ICE, RICE, MoSCoW, Kano, etc.)
• strategy-red-team — Adversarial stress-test of a plan: surface load-bearing assumptions, name what would make each one fail, and rank by cheapest test

Commands (11):

• /write-prd — Create a PRD from a feature idea or problem statement
• /plan-okrs — Brainstorm team-level OKRs
• /transform-roadmap — Convert a feature-based roadmap into outcome-focused
• /sprint — Sprint lifecycle (plan|retro|release)
• /pre-mortem — Pre-mortem risk analysis on a PRD or launch plan
• /red-team-prd — Adversarially stress-test a PRD, roadmap, or strategy and rank the riskiest assumptions by cheapest test
• /meeting-notes — Summarize a meeting transcript into structured notes
• /stakeholder-map — Map stakeholders and create a communication plan
• /write-stories — Break features into backlog items (user|job|wwa)
• /test-scenarios — Generate test scenarios from user stories
• /generate-data — Create realistic dummy datasets

Examples:

Skills:

• Which prioritization framework should I use for a 50-item backlog?
• Map our stakeholders for the platform migration project
• What's the difference between Opportunity Score, ICE, and RICE?

Commands:

• /write-prd Smart notification system that reduces alert fatigue
• /sprint retro — Here are the notes from our last sprint
• /write-stories job — Break down the "team dashboard" feature into job stories

4. pm-market-research — Personas, segmentation, journey maps, market sizing, competitor analysis (7 skills, 3 commands)

User research and competitive analysis: personas, segmentation, journey maps, market sizing, competitor analysis, and feedback analysis.

Skills (7):

• user-personas — Create refined user personas from research data
• market-segments — Identify 3–5 customer segments with demographics, JTBD, and product fit
• user-segmentation — Segment users from feedback data based on behavior, JTBD, and needs
• customer-journey-map — End-to-end journey map with stages, touchpoints, emotions, and pain points
• market-sizing — TAM, SAM, SOM with top-down and bottom-up approaches
• competitor-analysis — Competitor strengths, weaknesses, and differentiation opportunities
• sentiment-analysis — Sentiment analysis and theme extraction from user feedback

Commands (3):

• /research-users — Build personas, segment users, and map the customer journey
• /competitive-analysis — Analyze the competitive landscape
• /analyze-feedback — Sentiment analysis and segment insights from user feedback

Examples:

Skills:

• Estimate TAM/SAM/SOM for an AI code review tool in the US market
• Create a customer journey map for our e-commerce checkout flow
• Segment these survey respondents by behavior and needs [attach CSV]

Commands:

• /research-users We have interview data from 12 users of our fitness app
• /competitive-analysis Figma competitors in the design tool space
• /analyze-feedback Here's 200 NPS responses from Q4 [attach file]

5. pm-data-analytics — SQL generation, cohort analysis, A/B test analysis (3 skills, 3 commands)

Data analytics for PMs: SQL query generation, cohort analysis, and A/B test analysis.

Skills (3):

• sql-queries — Generate SQL from natural language (BigQuery, PostgreSQL, MySQL)
• cohort-analysis — Retention curves, feature adoption, and engagement trends by cohort
• ab-test-analysis — Statistical significance, sample size validation, and ship/extend/stop recommendations

Commands (3):

• /write-query — Generate SQL queries from natural language
• /analyze-cohorts — Cohort analysis on user engagement data
• /analyze-test — Analyze A/B test results

Examples:

Skills:

• How large a sample do I need for 95% confidence with a 2% MDE?
• What retention metrics should I track for a subscription app?

Commands:

• /write-query Show me monthly active users by country for Q4 2025 (BigQuery)
• /analyze-test Here are the results from our checkout flow A/B test [attach CSV]
• /analyze-cohorts Weekly retention for users who signed up in January vs February

6. pm-go-to-market — Beachhead segments, ICPs, messaging, growth loops, GTM motions, battlecards (6 skills, 3 commands)

Go-to-market strategy: beachhead segments, ideal customer profiles, messaging, growth loops, GTM motions, and competitive battlecards.

Skills (6):

• gtm-strategy — Full GTM strategy: channels, messaging, success metrics, and launch plan
• beachhead-segment — Identify the first beachhead market segment
• ideal-customer-profile — ICP with demographics, behaviors, JTBD, and needs
• growth-loops — Design sustainable growth loops (flywheels)
• gtm-motions — Evaluate GTM motions and tools (product-led, sales-led, etc.)
• competitive-battlecard — Sales-ready battlecard with objection handling and win strategies

Commands (3):

• /plan-launch — Full GTM strategy from beachhead to launch plan
• /growth-strategy — Design growth loops and evaluate GTM motions
• /battlecard — Create a competitive battlecard

Examples:

Skills:

• What's the best beachhead segment for a developer productivity tool?
• Design a growth loop for a B2B SaaS with a freemium tier
• Define our ICP for an AI-powered HR screening platform

Commands:

• /plan-launch AI code review tool targeting mid-size engineering teams
• /battlecard Our CRM vs Salesforce for the SMB market
• /growth-strategy Two-sided marketplace for connecting freelancers with startups

7. pm-marketing-growth — Marketing ideas, positioning, value props, naming, North Star metrics (5 skills, 2 commands)

Product marketing and growth: marketing ideas, positioning, value proposition statements, product naming, and North Star metrics.

Skills (5):

• marketing-ideas — Creative, cost-effective marketing ideas with channels and messaging
• positioning-ideas — Product positioning differentiated from competitors
• value-prop-statements — Value proposition statements for marketing, sales, and onboarding
• product-name — Product name brainstorming aligned to brand values and audience
• north-star-metric — North Star Metric + input metrics with business game classification

Commands (2):

• /market-product — Brainstorm marketing ideas, positioning, value props, and product names
• /north-star — Define your North Star Metric and supporting input metrics

Examples:

Skills:

• Brainstorm 5 positioning angles that differentiate us from Notion
• What's a good North Star Metric for a two-sided marketplace?
• Generate value prop statements for our sales team's pitch deck

Commands:

• /market-product B2B analytics dashboard for e-commerce managers
• /north-star Two-sided marketplace connecting freelancers with clients

8. pm-toolkit — Resume review, legal documents, proofreading (4 skills, 5 commands)

PM utilities beyond core product work: resume review, legal documents, and proofreading.

Skills (4):

• review-resume — PM resume review and tailoring against 10 best practices (XYZ+S formula, keywords, structure)
• draft-nda — Non-Disclosure Agreement with jurisdiction-appropriate clauses
• privacy-policy — Privacy policy covering GDPR/CCPA compliance
• grammar-check — Grammar, logic, and flow checking with targeted fixes

Commands (5):

• /review-resume — Comprehensive PM resume review
• /tailor-resume — Tailor a resume to a specific job description
• /draft-nda — Draft an NDA
• /privacy-policy — Draft a privacy policy
• /proofread — Check grammar, logic, and flow

Examples:

Skills:

• Review my PM resume against best practices [attach PDF]
• Check this product announcement for grammar and clarity

Commands:

• /review-resume [attach your PM resume]
• /tailor-resume [attach resume + paste job description]
• /proofread Here's the draft of our Q1 investor update

9. pm-ai-shipping — AI Shipping Kit: document a vibe-coded app, review it for correctness, security and performance defects, map test coverage, compile a shipping packet (3 skills, 5 commands)

For PMs and founders accountable for AI-built code. AI agents write code fast but leave no record of intent — what the system should do, who may do what, where the secrets live, which rules are actually verified. This kit restores reviewability: it documents the system, then audits the gap between what the docs say and what the code actually does — the class of bug generic scanners miss.

Skills (2):

• shipping-artifacts — The durable documentation set that makes an AI-built app reviewable: a core every app needs (architecture, user/permission flows, permissions, variables/secrets, test-coverage map) plus conditional docs added only when they apply (emails, cron, SEO, embedded agents/automation). Defines what each doc must capture and how a reviewer uses it
• intended-vs-implemented — The method for finding the gap between what a system is documented to do and what the code actually does, with cited evidence on both sides

Commands (5):

• /ship-check — Turn a vibe-coded repo into a reviewer-ready shipping packet: document, wire agent context, run security and performance audits, map test coverage, and compile the results
• /document-app — Reverse-engineer a codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply; check writes nothing and reports where existing docs and code disagree
• /derive-tests — Turn documented intent into a test-coverage map: inventory the tests that exist today, separate them from proposed tests and unverified gaps, and recommend a gate that follows the repo's stated gate policy (a green-before-merge CI gate where it states none); check writes nothing and reports where the map is stale
• /security-audit-static — Static security audit: map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks; a git range or changes audits only a change
• /performance-audit-static — Static performance audit: find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact; a git range or changes audits only a change

Examples:

Skills:

• What documentation does my Supabase app need before someone can review it?
• Where does what this code does diverge from what the docs say it should do?

Commands:

• /ship-check the payments service
• /document-app — Reverse-engineer the system docs for this repo
• /derive-tests — Which documented rules have no test yet?
• /security-audit-static src/api

About Copy Chapter

This marketplace evolves with product practice and AI capabilities.

Selected skills based on the work of:

• Teresa Torres — Continuous Discovery Habits
• Marty Cagan — INSPIRED and TRANSFORMED
• Alberto Savoia — The Right It
• Dan Olsen — The Lean Product Playbook
• Roger L. Martin — Playing to Win
• Ash Maurya — Running Lean
• Strategyzer — Business Model Generation and Value Proposition Design
• Christina Wodtke — Radical Focus
• Anthony W. Ulwick — Jobs to Be Done
• Alistair Croll & Benjamin Yoskovitz — Lean Analytics
• Sean Ellis — Hacking Growth
• Maja Voje — Go-To-Market Strategist

Curated by Paweł Huryn from The Product Compass Newsletter.

Compose with PM Brain Copy Chapter

PM Brain a second brain for product managers. Plain markdown files in a folder on your laptop. Claude reads them before answering, writes to them after, sweeps them every Friday. No vector DB. No cloud. No agent memory tricks.

Contributing Copy Chapter

See CONTRIBUTING.md.

Known Issue on Windows Copy Chapter

If your Cowork is unstable and can't start a VM (claude-code/issues/27010), try:

$action = New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-WindowStyle Hidden -Command `"if ((Get-Service CoworkVMService).Status -ne 'Running') { Start-Service CoworkVMService }`""

$trigger = New-ScheduledTaskTrigger -RepetitionInterval (New-TimeSpan -Minutes 1) -Once -At (Get-Date)

$settings = New-ScheduledTaskSettingsSet -AllowStartIfOnBatteries -DontStopIfGoingOnBatteries

Register-ScheduledTask -TaskName "CoworkVMServiceMonitor" `
  -Action $action `
  -Trigger $trigger `
  -Settings $settings `
  -RunLevel Highest `
  -User "SYSTEM"

It solves 90% of the issues on Windows.
The remaining 10%: open services.msc > start "Claude" service manually

License Copy Chapter

MIT — see LICENSE.

Overview (`pm-ai-shipping/README.md`) Copy Section

pm-ai-shipping — AI Shipping Kit

For PMs and founders accountable for AI-built code. Document a vibe-coded app, review it for correctness, security and performance defects, and produce a reviewer-ready shipping packet.

Overview Copy Chapter

AI agents write code fast but leave no record of intent — what the system should do, who may do what, where the secrets live. Without that record, no human and no auditing agent can tell whether the code is safe to ship. This kit restores reviewability: it documents the system, then audits the gap between what the docs say and what the code does — the class of bug generic scanners miss because they have no model of intent.

Start with /ship-check for the full sequence, or run a single stage with the specialist commands.

Folders and file names are defaults. The kit follows the repo's own setup — its agent instructions, its docs folder, and the documents and test-coverage file it already has — and falls back to documentation/, documentation/tests.md and reports/ only where the repo has none, saying so in its output.

The two static audits take a git range (..<head>, such as a release's unreleased commits) or changes (the uncommitted working tree) and then audit only the change: the changed files plus what the change makes newly reachable or newly wrong elsewhere. A release normally audits only its changes; audit the whole repository for the first release, or after a large refactor.

For a repo that keeps its docs and coverage map by hand as intent, /document-app check and /derive-tests check are the release-time form: they write no file, list each disagreement with file:line on both sides, leave the owner to decide whether the code or the doc is wrong, and end with a one-line summary a release checklist can cite.

Install Copy Chapter

Install from the pm-skills marketplace and enable the pm-ai-shipping plugin. Each command can be triggered with /pm-ai-shipping:<command> or its short /<command> form; skills auto-load when the topic matches.

Skills (3) Copy Chapter

• shipping-artifacts — The durable documentation set that makes an AI-built app reviewable: a core every app needs (architecture, user/permission flows, permissions, variables/secrets, test-coverage map) plus conditional docs added only when they apply (emails, cron, SEO, embedded agents/automation). Defines what each doc must capture and how a reviewer uses it.
• code-review — The top-level review skill. Correctness is its core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary — the defects that are invisible file-by-file because each side looks reasonable alone — forces a violating execution, and refutes every candidate before reporting.
• intended-vs-implemented — The method for finding the gap between what a system is documented to do and what the code actually does, with cited evidence on both sides and without hand-wavy findings.

Commands (5) Copy Chapter

• /pm-ai-shipping:ship-check — Turn a vibe-coded repo into a reviewer-ready shipping packet: document, wire agent context, run correctness, security and performance reviews, add an independent unsteered pass by a second model, map test coverage, and compile the results.
• /pm-ai-shipping:document-app — Reverse-engineer a codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply. /document-app check writes nothing and reports where the existing docs and the code disagree.
• /pm-ai-shipping:derive-tests — Turn documented intent into a test-coverage map: inventory the tests that exist today, separate them from proposed tests and unverified gaps, mark each unit / guarded-live / manual, and recommend a gate that follows the repo's stated gate policy (a green-before-merge CI gate where it states none). /derive-tests check writes nothing and reports where the coverage map is stale against the docs and the test suite.
• /pm-ai-shipping:security-audit-static — Static security audit: map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks. /security-audit-static ..<head> or changes audits only a change.
• /pm-ai-shipping:performance-audit-static — Static performance audit: find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact. /performance-audit-static ..<head> or changes audits only a change.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

Overview (`pm-data-analytics/README.md`) Copy Section

pm-data-analytics

Data analytics skills for PMs: SQL query generation and cohort analysis. Analyze user data, generate queries, and identify retention patterns.

Skills (3) Copy Chapter

• ab-test-analysis — Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and actionable recommendations.
• cohort-analysis — Perform cohort analysis on user engagement data.
• sql-queries — Generate SQL queries from natural language descriptions.

Commands (3) Copy Chapter

• /pm-data-analytics:analyze-cohorts — Perform cohort analysis on user data — retention curves, feature adoption, and engagement trends.
• /pm-data-analytics:analyze-test — Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
• /pm-data-analytics:write-query — Generate SQL queries from natural language — supports BigQuery, PostgreSQL, MySQL, and more.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

Overview (`pm-execution/README.md`) Copy Section

pm-execution

Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.

Skills (16) Copy Chapter

• brainstorm-okrs — Brainstorm team-level OKRs aligned with company objectives.
• create-prd — Create a lean, decision-ready Product Requirements Document with an 8-section template covering summary, background, objectives, market segments, value propositions, solution details, and release planning. Lean by default (about one to two pages), with a fuller spec on request.
• dummy-dataset — Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script).
• job-stories — Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria.
• outcome-roadmap — Transform an output-focused roadmap into an outcome-focused one.
• pre-mortem — Run a pre-mortem analysis on a PRD.
• prioritization-frameworks — Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates.
• release-notes — Generate user-facing release notes from tickets, PRDs, or changelogs.
• retro — Facilitate a structured sprint retrospective.
• sprint-plan — Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification.
• stakeholder-map — Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan.
• strategy-red-team — Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions; rank failure modes and return the cheapest test and kill criteria for each.
• summarize-meeting — Summarize a meeting transcript into a structured template with date, participants, topic, summary points, and action items.
• test-scenarios — Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
• user-stories — Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria.
• wwas — Create product backlog items in Why-What-Acceptance format.

Commands (11) Copy Chapter

• /pm-execution:generate-data — Generate realistic dummy datasets for testing — CSV, JSON, SQL inserts, or Python scripts.
• /pm-execution:meeting-notes — Summarize a meeting transcript into structured notes with decisions, action items, and follow-ups.
• /pm-execution:plan-okrs — Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
• /pm-execution:pre-mortem — Run a pre-mortem risk analysis on a PRD, launch plan, or feature — identify what could go wrong before it does.
• /pm-execution:red-team-prd — Red-team a PRD, roadmap, or strategy — attack its load-bearing assumptions and return the cheapest test for each before you commit.
• /pm-execution:sprint — Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
• /pm-execution:stakeholder-map — Map stakeholders on a Power × Interest grid and create a tailored communication plan.
• /pm-execution:test-scenarios — Generate comprehensive test scenarios from user stories or feature specs — happy paths, edge cases, and error handling.
• /pm-execution:transform-roadmap — Convert a feature-based roadmap into an outcome-focused roadmap that communicates strategic intent.
• /pm-execution:write-prd — Create a lean Product Requirements Document from a feature idea or problem statement, with a fuller spec on request.
• /pm-execution:write-stories — Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

Overview (`pm-go-to-market/README.md`) Copy Section

pm-go-to-market

Go-to-market skills for PMs: GTM strategy, growth loops, GTM motions, beachhead segments, and ideal customer profiles.

Skills (6) Copy Chapter

• beachhead-segment — Identify the first beachhead market segment for a product launch.
• competitive-battlecard — Create sales-ready competitive battlecards comparing your product against a specific competitor.
• growth-loops — Identify growth loops (flywheels) for sustainable traction.
• gtm-motions — Identify the best GTM motions and tools.
• gtm-strategy — Create a go-to-market strategy for a product launch covering marketing channels, messaging, success metrics, and launch plan.
• ideal-customer-profile — Identify the Ideal Customer Profile (ICP) from research data with demographics, behaviors, JTBD, and needs.

Commands (3) Copy Chapter

• /pm-go-to-market:battlecard — Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
• /pm-go-to-market:growth-strategy — Design sustainable growth mechanisms — growth loops and GTM motions for product-led and sales-led strategies.
• /pm-go-to-market:plan-launch — Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

Overview (`pm-market-research/README.md`) Copy Section

pm-market-research

Market research skills for PMs: user personas, market segmentation, sentiment analysis, and competitive analysis.

Skills (7) Copy Chapter

• competitor-analysis — Analyze competitors with strengths, weaknesses, and differentiation opportunities.
• customer-journey-map — Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities.
• market-segments — Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis.
• market-sizing — Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approaches.
• sentiment-analysis — Analyze user feedback data to identify market segments with sentiment scores, JTBD, and product satisfaction insights.
• user-personas — Create refined user personas from research data.
• user-segmentation — Segment users from feedback data based on behavior, JTBD, and needs.

Commands (3) Copy Chapter

• /pm-market-research:analyze-feedback — Analyze user feedback at scale — sentiment analysis, theme extraction, and segment-level insights.
• /pm-market-research:competitive-analysis — Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differentiation opportunities.
• /pm-market-research:research-users — Comprehensive user research — build personas, segment users, and map the customer journey from research data.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

Overview (`pm-marketing-growth/README.md`) Copy Section

pm-marketing-growth

Product marketing and growth skills: marketing ideas, value proposition statements, North Star metrics, product naming, and positioning.

Skills (5) Copy Chapter

• marketing-ideas — Generate 5 creative, cost-effective marketing ideas with channels, messaging, and engagement rationale.
• north-star-metric — Identify a North Star Metric and 3-5 Input Metrics.
• positioning-ideas — Brainstorm product positioning ideas differentiated from competitors.
• product-name — Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.
• value-prop-statements — Generate value proposition statements for marketing, sales, and onboarding from existing value propositions.

Commands (2) Copy Chapter

• /pm-marketing-growth:market-product — Brainstorm marketing ideas, positioning, value prop statements, and product names — creative marketing toolkit.
• /pm-marketing-growth:north-star — Define your North Star Metric and supporting input metrics — classify the business game and validate against best practices.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

Overview (`pm-product-discovery/README.md`) Copy Section

pm-product-discovery

Product discovery skills for PMs: ideation, experiments, assumption testing, feature prioritization, and customer interview synthesis.

Skills (13) Copy Chapter

• analyze-feature-requests — Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk.
• brainstorm-experiments-existing — Design experiments to test assumptions for an existing product.
• brainstorm-experiments-new — Design lean startup experiments (pretotypes) for a new product.
• brainstorm-ideas-existing — Brainstorm product ideas for an existing product using multi-perspective ideation (PM, Designer, Engineer).
• brainstorm-ideas-new — Brainstorm feature ideas for a new product in initial discovery.
• identify-assumptions-existing — Identify risky assumptions for a feature idea in an existing product across Value, Usability, Viability, and Feasibility.
• identify-assumptions-new — Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team.
• interview-script — Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections.
• metrics-dashboard — Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds.
• opportunity-solution-tree — Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments.
• prioritize-assumptions — Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each.
• prioritize-features — Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment.
• summarize-interview — Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items.

Commands (5) Copy Chapter

• /pm-product-discovery:brainstorm — Brainstorm product ideas or experiments from PM, Designer, and Engineer perspectives — for existing or new products.
• /pm-product-discovery:discover — Run a full product discovery cycle — from ideation through assumption mapping to experiment design.
• /pm-product-discovery:interview — Prepare a customer interview script or summarize an interview transcript into structured insights.
• /pm-product-discovery:setup-metrics — Design a product metrics dashboard with North Star metric, input metrics, health metrics, and alert thresholds.
• /pm-product-discovery:triage-requests — Analyze, categorize, and prioritize a batch of feature requests from customers or stakeholders.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

Overview (`pm-product-strategy/README.md`) Copy Section

pm-product-strategy

Product strategy skills for PMs: vision, strategy canvas, startup canvas, value propositions, lean canvas, business model canvas, SWOT, PESTLE, Ansoff Matrix, Porter's Five Forces, pricing, and monetization.

Skills (12) Copy Chapter

• ansoff-matrix — Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification.
• business-model — Generate a Business Model Canvas with all 9 building blocks.
• lean-canvas — Generate a Lean Canvas business model with sections for problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue.
• monetization-strategy — Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments.
• pestle-analysis — Perform a PESTLE analysis covering Political, Economic, Social, Technological, Legal, and Environmental factors.
• porters-five-forces — Perform Porter's Five Forces analysis evaluating competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants.
• pricing-strategy — Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity considerations.
• product-strategy — Generate a comprehensive product strategy using the 9-section Product Strategy Canvas covering vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.
• product-vision — Brainstorm an inspiring, achievable, and emotional product vision that motivates teams.
• startup-canvas — Generate a Startup Canvas combining Product Strategy (9 sections) and Business Model (Cost Structure + Revenue Streams) for a new product. An alternative to Business Model Canvas and Lean Canvas that separates strategy from business model.
• swot-analysis — Perform a detailed SWOT analysis identifying strengths, weaknesses, opportunities, and threats with actionable recommendations.
• value-proposition — Generate a detailed value proposition using a 6-part JTBD template (Who, Why, What before, How, What after, Alternatives).

Commands (5) Copy Chapter

• /pm-product-strategy:business-model — Explore business models using Lean Canvas, Business Model Canvas, Startup Canvas, or Value Proposition frameworks.
• /pm-product-strategy:market-scan — Comprehensive macro environment analysis — SWOT, PESTLE, Porter's Five Forces, and Ansoff Matrix in one scan.
• /pm-product-strategy:pricing — Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing experiments.
• /pm-product-strategy:strategy — Create a comprehensive product strategy using the 9-section Strategy Canvas — from vision to defensibility.
• /pm-product-strategy:value-proposition — Design a value proposition using the 6-part JTBD template — Who, Why, What before, How, What after, Alternatives.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

Overview (`pm-toolkit/README.md`) Copy Section

pm-toolkit

PM utility skills: resume review, NDA drafting, privacy policy generation, and grammar/flow checking. Essential tools for product managers beyond core product work.

Skills (4) Copy Chapter

• draft-nda — Draft a detailed Non-Disclosure Agreement between two parties.
• grammar-check — Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text.
• privacy-policy — Draft a detailed privacy policy for a product covering data types, jurisdiction, compliance considerations, and clauses needing legal review.
• review-resume — Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure.

Commands (5) Copy Chapter

• /pm-toolkit:draft-nda — Draft a Non-Disclosure Agreement between two parties with jurisdiction-appropriate clauses.
• /pm-toolkit:privacy-policy — Draft a privacy policy covering data collection, usage, storage, and compliance requirements.
• /pm-toolkit:proofread — Check grammar, logic, and flow in any text — targeted fixes without rewriting.
• /pm-toolkit:review-resume — Comprehensive PM resume review against 10 best practices — structure, impact metrics, keywords, and actionable feedback.
• /pm-toolkit:tailor-resume — Tailor a PM resume to a specific job description — keyword alignment, experience reframing, and strategic optimization.

Author Copy Chapter

Paweł Huryn — The Product Compass Newsletter

License Copy Chapter

MIT

--- METRICS ---

• Files Extracted: 10
• Estimated Token Budget: ~12138 tokens
• Canonical Reference: https://codewiki.google/github.com/phuryn/pm-skills