Showing preview only (500K chars total). Download the full file or copy to clipboard to get everything.
Repository: phuryn/pm-skills
Branch: main
Commit: 36ccefdc6c2e
Files: 124
Total size: 464.4 KB
Directory structure:
gitextract__yxe0xfm/
├── .claude-plugin/
│ └── marketplace.json
├── .gitattributes
├── .gitignore
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── pm-data-analytics/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── README.md
│ ├── commands/
│ │ ├── analyze-cohorts.md
│ │ ├── analyze-test.md
│ │ └── write-query.md
│ └── skills/
│ ├── ab-test-analysis/
│ │ └── SKILL.md
│ ├── cohort-analysis/
│ │ └── SKILL.md
│ └── sql-queries/
│ └── SKILL.md
├── pm-execution/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── README.md
│ ├── commands/
│ │ ├── generate-data.md
│ │ ├── meeting-notes.md
│ │ ├── plan-okrs.md
│ │ ├── pre-mortem.md
│ │ ├── sprint.md
│ │ ├── stakeholder-map.md
│ │ ├── test-scenarios.md
│ │ ├── transform-roadmap.md
│ │ ├── write-prd.md
│ │ └── write-stories.md
│ └── skills/
│ ├── brainstorm-okrs/
│ │ └── SKILL.md
│ ├── create-prd/
│ │ └── SKILL.md
│ ├── dummy-dataset/
│ │ └── SKILL.md
│ ├── job-stories/
│ │ └── SKILL.md
│ ├── outcome-roadmap/
│ │ └── SKILL.md
│ ├── pre-mortem/
│ │ └── SKILL.md
│ ├── prioritization-frameworks/
│ │ └── SKILL.md
│ ├── release-notes/
│ │ └── SKILL.md
│ ├── retro/
│ │ └── SKILL.md
│ ├── sprint-plan/
│ │ └── SKILL.md
│ ├── stakeholder-map/
│ │ └── SKILL.md
│ ├── summarize-meeting/
│ │ └── SKILL.md
│ ├── test-scenarios/
│ │ └── SKILL.md
│ ├── user-stories/
│ │ └── SKILL.md
│ └── wwas/
│ └── SKILL.md
├── pm-go-to-market/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── README.md
│ ├── commands/
│ │ ├── battlecard.md
│ │ ├── growth-strategy.md
│ │ └── plan-launch.md
│ └── skills/
│ ├── beachhead-segment/
│ │ └── SKILL.md
│ ├── competitive-battlecard/
│ │ └── SKILL.md
│ ├── growth-loops/
│ │ └── SKILL.md
│ ├── gtm-motions/
│ │ └── SKILL.md
│ ├── gtm-strategy/
│ │ └── SKILL.md
│ └── ideal-customer-profile/
│ └── SKILL.md
├── pm-market-research/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── README.md
│ ├── commands/
│ │ ├── analyze-feedback.md
│ │ ├── competitive-analysis.md
│ │ └── research-users.md
│ └── skills/
│ ├── competitor-analysis/
│ │ └── SKILL.md
│ ├── customer-journey-map/
│ │ └── SKILL.md
│ ├── market-segments/
│ │ └── SKILL.md
│ ├── market-sizing/
│ │ └── SKILL.md
│ ├── sentiment-analysis/
│ │ └── SKILL.md
│ ├── user-personas/
│ │ └── SKILL.md
│ └── user-segmentation/
│ └── SKILL.md
├── pm-marketing-growth/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── README.md
│ ├── commands/
│ │ ├── market-product.md
│ │ └── north-star.md
│ └── skills/
│ ├── marketing-ideas/
│ │ └── SKILL.md
│ ├── north-star-metric/
│ │ └── SKILL.md
│ ├── positioning-ideas/
│ │ └── SKILL.md
│ ├── product-name/
│ │ └── SKILL.md
│ └── value-prop-statements/
│ └── SKILL.md
├── pm-product-discovery/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── README.md
│ ├── commands/
│ │ ├── brainstorm.md
│ │ ├── discover.md
│ │ ├── interview.md
│ │ ├── setup-metrics.md
│ │ └── triage-requests.md
│ └── skills/
│ ├── analyze-feature-requests/
│ │ └── SKILL.md
│ ├── brainstorm-experiments-existing/
│ │ └── SKILL.md
│ ├── brainstorm-experiments-new/
│ │ └── SKILL.md
│ ├── brainstorm-ideas-existing/
│ │ └── SKILL.md
│ ├── brainstorm-ideas-new/
│ │ └── SKILL.md
│ ├── identify-assumptions-existing/
│ │ └── SKILL.md
│ ├── identify-assumptions-new/
│ │ └── SKILL.md
│ ├── interview-script/
│ │ └── SKILL.md
│ ├── metrics-dashboard/
│ │ └── SKILL.md
│ ├── opportunity-solution-tree/
│ │ └── SKILL.md
│ ├── prioritize-assumptions/
│ │ └── SKILL.md
│ ├── prioritize-features/
│ │ └── SKILL.md
│ └── summarize-interview/
│ └── SKILL.md
├── pm-product-strategy/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── README.md
│ ├── commands/
│ │ ├── business-model.md
│ │ ├── market-scan.md
│ │ ├── pricing.md
│ │ ├── strategy.md
│ │ └── value-proposition.md
│ └── skills/
│ ├── ansoff-matrix/
│ │ └── SKILL.md
│ ├── business-model/
│ │ └── SKILL.md
│ ├── lean-canvas/
│ │ └── SKILL.md
│ ├── monetization-strategy/
│ │ └── SKILL.md
│ ├── pestle-analysis/
│ │ └── SKILL.md
│ ├── porters-five-forces/
│ │ └── SKILL.md
│ ├── pricing-strategy/
│ │ └── SKILL.md
│ ├── product-strategy/
│ │ └── SKILL.md
│ ├── product-vision/
│ │ └── SKILL.md
│ ├── startup-canvas/
│ │ └── SKILL.md
│ ├── swot-analysis/
│ │ └── SKILL.md
│ └── value-proposition/
│ └── SKILL.md
├── pm-toolkit/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── README.md
│ ├── commands/
│ │ ├── draft-nda.md
│ │ ├── privacy-policy.md
│ │ ├── proofread.md
│ │ ├── review-resume.md
│ │ └── tailor-resume.md
│ └── skills/
│ ├── draft-nda/
│ │ └── SKILL.md
│ ├── grammar-check/
│ │ └── SKILL.md
│ ├── privacy-policy/
│ │ └── SKILL.md
│ └── review-resume/
│ └── SKILL.md
└── validate_plugins.py
================================================
FILE CONTENTS
================================================
================================================
FILE: .claude-plugin/marketplace.json
================================================
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "pm-skills",
"version": "1.0.1",
"description": "Structured AI workflows for better product decisions. 65 domain-specific skills and 36 chained workflows across 8 PM plugins — from discovery to strategy, execution, launch, and growth.",
"owner": {
"name": "Paweł Huryn",
"email": "pawel@productcompass.pm",
"url": "https://www.productcompass.pm"
},
"plugins": [
{
"name": "pm-product-discovery",
"description": "Product discovery skills for PMs: ideation, experiments, assumption testing, feature prioritization, and customer interview synthesis.",
"source": "./pm-product-discovery",
"category": "product-management"
},
{
"name": "pm-product-strategy",
"description": "Product strategy skills for PMs: vision, strategy canvas, value propositions, lean canvas, business model canvas, SWOT, PESTLE, Ansoff Matrix, Porter's Five Forces, and monetization.",
"source": "./pm-product-strategy",
"category": "product-management"
},
{
"name": "pm-execution",
"description": "Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.",
"source": "./pm-execution",
"category": "product-management"
},
{
"name": "pm-market-research",
"description": "Market research skills for PMs: user personas, market segmentation, sentiment analysis, and competitive analysis.",
"source": "./pm-market-research",
"category": "product-management"
},
{
"name": "pm-data-analytics",
"description": "Data analytics skills for PMs: SQL query generation and cohort analysis. Analyze user data, generate queries, and identify retention patterns.",
"source": "./pm-data-analytics",
"category": "product-management"
},
{
"name": "pm-go-to-market",
"description": "Go-to-market skills for PMs: GTM strategy, growth loops, GTM motions, beachhead segments, and ideal customer profiles.",
"source": "./pm-go-to-market",
"category": "product-management"
},
{
"name": "pm-marketing-growth",
"description": "Product marketing and growth skills: marketing ideas, value proposition statements, North Star metrics, product naming, and positioning.",
"source": "./pm-marketing-growth",
"category": "product-management"
},
{
"name": "pm-toolkit",
"description": "PM utility skills: resume review, NDA drafting, privacy policy generation, and grammar/flow checking. Essential tools for product managers beyond core product work.",
"source": "./pm-toolkit",
"category": "product-management"
}
]
}
================================================
FILE: .gitattributes
================================================
# Auto detect text files and perform LF normalization
* text=auto
*.py linguist-detectable=false
================================================
FILE: .gitignore
================================================
_Internal/
CLAUDE.md
================================================
FILE: CONTRIBUTING.md
================================================
# Contributing
PM Skills Marketplace is maintained by [Paweł Huryn](https://www.productcompass.pm) (pawel@productcompass.pm). Contributions are welcome — whether it's a bug fix, a typo, or a new skill idea.
## How to Contribute
- **Bugs and small fixes** — open a PR directly.
- **New skills, commands, or larger changes** — open an issue first so we can discuss the approach.
## Guidelines
- Keep PRs focused — one change per PR.
- Follow existing patterns: skills are nouns (domain knowledge), commands are verbs (workflows).
- Every skill needs frontmatter with `name` and `description`. Every command needs `description` and `argument-hint`.
- Skill `name` must match its directory name.
- No cross-plugin references in commands. Suggest follow-ups in natural language only.
- Every contributor will be listed publicly.
- Run the validator before submitting: `python3 validate_plugins.py`
## License
By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).
================================================
FILE: LICENSE
================================================
MIT License
Copyright (c) 2026 Pawel Huryn
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
================================================
FILE: README.md
================================================
[](https://github.com/phuryn/pm-skills/blob/main/LICENSE)
[](https://github.com/phuryn/pm-skills/blob/main/CONTRIBUTING.md)
# PM Skills Marketplace: The AI Operating System for Better Product Decisions
> 65 PM skills and 36 chained workflows across 8 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, and growth.
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 8 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 8 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
```
### 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 |
| **Codex CLI** | Copy skill folders to `.codex/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, 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`
</details>
<details>
<summary><strong>3. pm-execution</strong> — PRDs, OKRs, roadmaps, sprints, retros, release notes, stakeholder management (15 skills, 10 commands)</summary>
Day-to-day product management: PRDs, OKRs, roadmaps, sprints, retrospectives, release notes, pre-mortems, stakeholder management, user stories, and prioritization frameworks.
**Skills (15):**
- `create-prd` — Comprehensive 8-section PRD template
- `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.)
**Commands (10):**
- `/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
- `/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`
</details>
<details>
<summary><strong>4. pm-market-research</strong> — Personas, segmentation, journey maps, market sizing, competitor analysis (7 skills, 3 commands)</summary>
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]`
</details>
<details>
<summary><strong>5. pm-data-analytics</strong> — SQL generation, cohort analysis, A/B test analysis (3 skills, 3 commands)</summary>
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`
</details>
<details>
<summary><strong>6. pm-go-to-market</strong> — Beachhead segments, ICPs, messaging, growth loops, GTM motions, battlecards (6 skills, 3 commands)</summary>
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`
</details>
<details>
<summary><strong>7. pm-marketing-growth</strong> — Marketing ideas, positioning, value props, naming, North Star metrics (5 skills, 2 commands)</summary>
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`
</details>
<details>
<summary><strong>8. pm-toolkit</strong> — Resume review, legal documents, proofreading (4 skills, 5 commands)</summary>
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`
</details>
---
## About
This marketplace evolves with product practice and AI capabilities.
Selected skills based on the work of:
- Teresa Torres — [*Continuous Discovery Habits*](https://www.amazon.com/Continuous-Discovery-Habits-Discover-Products/dp/1736633309/)
- Marty Cagan — [*INSPIRED*](https://www.amazon.com/INSPIRED-Create-Tech-Products-Customers/dp/1119387507/) and [*TRANSFORMED*](https://www.amazon.com/dp/1119697336/)
- Alberto Savoia — [*The Right It*](https://www.amazon.com/Right-Many-Ideas-Yours-Succeed/dp/0062884654)
- Dan Olsen — [*The Lean Product Playbook*](https://www.amazon.com/dp/1118960874/)
- Roger L. Martin — [*Playing to Win*](https://www.amazon.com/Playing-Win-Expanded-Bonus-Articles/dp/B0F25SDYWV/)
- Ash Maurya — [*Running Lean*](https://www.amazon.com/dp/B004J4XGN6/)
- Strategyzer — [*Business Model Generation*](https://www.amazon.com/dp/0470876417/) and [*Value Proposition Design*](https://www.amazon.com/dp/1118968050/)
- Christina Wodtke — [*Radical Focus*](https://www.amazon.com/Radical-Focus-Achieving-Important-Objectives/dp/0996006052)
- Anthony W. Ulwick — [*Jobs to Be Done*](https://jobs-to-be-done-book.com/)
- Alistair Croll & Benjamin Yoskovitz — [*Lean Analytics*](https://www.amazon.com/Lean-Analytics-Better-Startup-Faster/dp/1449335675/)
- Sean Ellis — [*Hacking Growth*](https://www.amazon.com/Hacking-Growth-Fastest-Growing-Companies-Breakout/dp/045149721X/)
- Maja Voje — [*Go-To-Market Strategist*](https://gtmstrategist.com/)
Curated by Paweł Huryn from [The Product Compass Newsletter](https://www.productcompass.pm).
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md).
## Known Issue on Windows
If your Cowork is unstable and can't start a VM ([claude-code/issues/27010](https://github.com/anthropics/claude-code/issues/27010)), try:
```powershell
$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
MIT — see [LICENSE](LICENSE).
================================================
FILE: pm-data-analytics/.claude-plugin/plugin.json
================================================
{
"name": "pm-data-analytics",
"version": "1.0.1",
"description": "Data analytics skills for PMs: SQL query generation and cohort analysis. Analyze user data, generate queries, and identify retention patterns.",
"author": {
"name": "Paweł Huryn",
"email": "pawel@productcompass.pm",
"url": "https://www.productcompass.pm"
},
"keywords": [
"product-management",
"data-analytics",
"sql",
"cohort-analysis",
"retention"
],
"homepage": "https://www.productcompass.pm",
"license": "MIT"
}
================================================
FILE: pm-data-analytics/README.md
================================================
# 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)
- **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)
- `/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
Paweł Huryn — [The Product Compass Newsletter](https://www.productcompass.pm)
## License
MIT
================================================
FILE: pm-data-analytics/commands/analyze-cohorts.md
================================================
---
description: Perform cohort analysis on user data — retention curves, feature adoption, and engagement trends
argument-hint: "<data file or description of what to analyze>"
---
# /analyze-cohorts -- Cohort Analysis
Analyze user retention and engagement patterns by cohort. Upload your data or describe what you need, and get retention curves, feature adoption trends, and actionable insights.
## Invocation
```
/analyze-cohorts [upload a CSV of user activity data]
/analyze-cohorts Monthly retention for users who signed up in Jan-Jun, grouped by acquisition channel
/analyze-cohorts Help me set up a cohort analysis for our onboarding redesign
```
## Workflow
### Step 1: Accept Data or Define Analysis
Two paths:
- **With data**: User uploads a CSV/spreadsheet with user-level data (user_id, signup_date, activity_date, event_type, etc.)
- **Without data**: User describes the analysis they need → generate the SQL query and analysis framework
### Step 2: Define Cohorts
Ask:
- What defines a cohort? (signup week/month, acquisition channel, plan tier, first feature used)
- What is the retention event? (login, core action, any activity, purchase)
- What time granularity? (daily, weekly, monthly)
- What time range?
### Step 3: Analyze
Apply the **cohort-analysis** skill:
**If data is provided:**
- Process the data using Python (pandas) to create cohort tables
- Calculate retention rates per cohort per period
- Generate retention curves
- Identify patterns: improving/declining cohorts, seasonal effects, anomalies
- Compare feature adoption across cohorts
**If describing an analysis:**
- Design the cohort analysis framework
- Generate SQL queries to extract the data
- Create a template spreadsheet for the analysis
- Define the metrics and visualization approach
### Step 4: Generate Report
```
## Cohort Analysis: [Description]
**Date**: [today]
**Cohort definition**: [e.g., signup month]
**Retention event**: [e.g., completed a project]
**Granularity**: [weekly/monthly]
### Retention Table
| Cohort | Size | Week 1 | Week 2 | Week 3 | ... | Week 12 |
|--------|------|--------|--------|--------|-----|---------|
### Key Findings
1. **[Finding]** — [supporting data]
2. ...
### Cohort Comparison
- **Best-performing cohort**: [which, why]
- **Worst-performing cohort**: [which, why]
- **Trend**: [improving/declining/stable over time]
### Retention Benchmarks
| Period | Your Rate | Industry Benchmark | Gap |
|--------|----------|-------------------|-----|
### Recommendations
1. [What to investigate or change based on findings]
2. ...
### Follow-Up Queries
[SQL queries for deeper investigation]
```
If data was provided, save analysis as both markdown report and CSV/spreadsheet.
### Step 5: Offer Next Steps
- "Want me to **segment this further** by another dimension?"
- "Should I **set up metrics alerts** based on these retention thresholds?"
- "Want me to **design experiments** to improve retention for the weakest cohort?"
## Notes
- Cohort analysis is only as good as the retention event definition — push for a meaningful action, not just "logged in"
- Early cohorts often look different due to founding user bias — note this when comparing
- If retention is calculated using a Python script, save the script so the user can re-run with new data
- Seasonal effects can masquerade as trends — flag if cohort differences might be calendar-driven
================================================
FILE: pm-data-analytics/commands/analyze-test.md
================================================
---
description: Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations
argument-hint: "<test results as data, screenshot, or description>"
---
# /analyze-test -- A/B Test Analysis
Evaluate experiment results with statistical rigor and translate findings into a clear product decision: ship, extend, or stop.
## Invocation
```
/analyze-test Control: 4.2% conversion (n=5000), Variant: 4.8% conversion (n=5100)
/analyze-test [upload a CSV of test results]
/analyze-test [screenshot from your experimentation platform]
```
## Workflow
### Step 1: Accept Test Data
Accept in any format:
- Summary statistics (conversion rates, sample sizes per variant)
- Raw event data (CSV with user_id, variant, converted, timestamp)
- Screenshot from an experimentation platform (Optimizely, LaunchDarkly, etc.)
- Description of the experiment and results
### Step 2: Validate Test Design
Before analyzing results, check:
- Was sample size sufficient? (run a power analysis)
- Was the test run long enough? (capture weekly cycles, minimum 1-2 business cycles)
- Was randomization clean? (check for sample ratio mismatch)
- Were there any external factors during the test period?
Flag issues if found — results from a flawed test can be misleading.
### Step 3: Analyze Results
Apply the **ab-test-analysis** skill:
- **Statistical significance**: Calculate p-value and confidence interval
- **Effect size**: Absolute and relative difference between variants
- **Practical significance**: Is the effect large enough to matter for the business?
- **Confidence interval**: What's the range of plausible true effects?
- **Segment analysis**: If data allows, check for differential effects by user segment
### Step 4: Generate Analysis
```
## A/B Test Analysis: [Test Name]
**Date**: [today]
**Test duration**: [X days/weeks]
**Total sample**: [N users]
### Results Summary
| Variant | Sample | Metric | Rate | 95% CI |
|---------|--------|--------|------|--------|
| Control | [n] | [metric] | [X%] | [X% - Y%] |
| Variant | [n] | [metric] | [X%] | [X% - Y%] |
### Statistical Analysis
- **Relative lift**: [+X%] ([CI range])
- **P-value**: [X]
- **Statistically significant**: [Yes/No] at 95% confidence
- **Minimum detectable effect**: [X%] (what the test was powered to detect)
### Sample Size Check
- **Required sample**: [N] per variant (for [X%] MDE at 80% power)
- **Actual sample**: [N] per variant
- **Verdict**: [Sufficiently powered / Underpowered / Overpowered]
### Decision
**Recommendation: [SHIP / EXTEND / STOP]**
[Clear explanation of why, considering both statistical and practical significance]
### Business Impact Estimate
If shipped to 100% of users:
- **Expected impact**: [metric change per month/quarter]
- **Revenue impact**: [if applicable]
- **Confidence**: [How certain we are about this estimate]
### Caveats
- [Any concerns about the test validity]
- [Segments where results differ]
- [Novelty effects or other biases to consider]
### Follow-Up
- [What to test next based on learnings]
- [Monitoring plan if shipping the variant]
```
### Step 5: Offer Next Steps
- "Want me to **design a follow-up experiment** based on these findings?"
- "Should I **run the analysis for specific segments**?"
- "Want me to **generate the SQL** to monitor this metric post-launch?"
## Notes
- Statistical significance ≠ practical significance — a 0.1% lift can be significant with enough data but not worth shipping
- Always check for sample ratio mismatch before trusting results
- Novelty effects can inflate short-term results — recommend monitoring for 2-4 weeks post-launch
- If the test is underpowered, the right answer is usually "extend" not "no effect"
- For revenue metrics, use confidence intervals to estimate best-case and worst-case business impact
- If data is provided as CSV, generate the full analysis using Python with scipy.stats
================================================
FILE: pm-data-analytics/commands/write-query.md
================================================
---
description: Generate SQL queries from natural language — supports BigQuery, PostgreSQL, MySQL, and more
argument-hint: "<what you want to know, in plain English>"
---
# /write-query -- SQL Query Generator
Describe what data you need in plain English and get an optimized SQL query. Supports multiple dialects and can read your schema from uploaded files.
## Invocation
```
/write-query Show me daily active users for the last 30 days, broken down by plan tier
/write-query Find users who signed up last month but never completed onboarding
/write-query [upload a schema diagram] What's the conversion rate from trial to paid by cohort?
```
## Workflow
### Step 1: Understand the Question
Parse the user's natural language request to identify:
- What data is being requested (metrics, dimensions, filters)
- Time range and granularity
- Grouping and ordering preferences
- Output expectations (raw data, aggregated, ranked)
### Step 2: Determine Schema
If a schema is available (uploaded diagram, DDL, or description):
- Map the request to specific tables and columns
- Identify necessary joins
If no schema is provided:
- Ask for the database type (BigQuery, PostgreSQL, MySQL, etc.)
- Infer a reasonable schema from the question and ask the user to confirm
- Use common SaaS data model conventions as defaults
### Step 3: Generate Query
Apply the **sql-queries** skill:
- Write the SQL query in the correct dialect
- Optimize for readability and performance
- Include comments explaining key logic
- Add CTEs for complex queries to improve readability
- Handle edge cases (NULLs, timezone considerations, duplicate handling)
### Step 4: Present and Iterate
```
## SQL Query: [What It Does]
**Dialect**: [BigQuery / PostgreSQL / MySQL / etc.]
**Tables used**: [list]
### Query
[SQL code block with comments]
### What This Returns
[Description of the output: columns, rows, expected result shape]
### Assumptions
- [Schema assumptions made]
- [Business logic assumptions]
### Notes
- [Performance considerations for large datasets]
- [Edge cases handled or flagged]
```
Offer:
- "Want me to **modify this** — add filters, change grouping, extend the time range?"
- "Should I **create a companion query** for a related metric?"
- "Want me to **build a dashboard** around this query?"
- "Need a **cohort analysis** version of this?"
## Notes
- Always include comments in the SQL — PMs share queries with analysts who need to understand intent
- Default to readable over clever — CTEs over nested subqueries
- Flag queries that might be slow on large datasets and suggest optimization
- If the request is ambiguous (e.g., "active users"), ask the user to define the metric precisely
- Offer to generate the query in multiple dialects if the user is unsure which database they're using
================================================
FILE: pm-data-analytics/skills/ab-test-analysis/SKILL.md
================================================
---
name: ab-test-analysis
description: "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."
---
## A/B Test Analysis
Evaluate A/B test results with statistical rigor and translate findings into clear product decisions.
### Context
You are analyzing A/B test results for **$ARGUMENTS**.
If the user provides data files (CSV, Excel, or analytics exports), read and analyze them directly. Generate Python scripts for statistical calculations when needed.
### Instructions
1. **Understand the experiment**:
- What was the hypothesis?
- What was changed (the variant)?
- What is the primary metric? Any guardrail metrics?
- How long did the test run?
- What is the traffic split?
2. **Validate the test setup**:
- **Sample size**: Is the sample large enough for the expected effect size?
- Use the formula: n = (Z²α/2 × 2 × p × (1-p)) / MDE²
- Flag if the test is underpowered (<80% power)
- **Duration**: Did the test run for at least 1-2 full business cycles?
- **Randomization**: Any evidence of sample ratio mismatch (SRM)?
- **Novelty/primacy effects**: Was there enough time to wash out initial behavior changes?
3. **Calculate statistical significance**:
- **Conversion rate** for control and variant
- **Relative lift**: (variant - control) / control × 100
- **p-value**: Using a two-tailed z-test or chi-squared test
- **Confidence interval**: 95% CI for the difference
- **Statistical significance**: Is p < 0.05?
- **Practical significance**: Is the lift meaningful for the business?
If the user provides raw data, generate and run a Python script to calculate these.
4. **Check guardrail metrics**:
- Did any guardrail metrics (revenue, engagement, page load time) degrade?
- A winning primary metric with degraded guardrails may not be a true win
5. **Interpret results**:
| Outcome | Recommendation |
|---|---|
| Significant positive lift, no guardrail issues | **Ship it** — roll out to 100% |
| Significant positive lift, guardrail concerns | **Investigate** — understand trade-offs before shipping |
| Not significant, positive trend | **Extend the test** — need more data or larger effect |
| Not significant, flat | **Stop the test** — no meaningful difference detected |
| Significant negative lift | **Don't ship** — revert to control, analyze why |
6. **Provide the analysis summary**:
```
## A/B Test Results: [Test Name]
**Hypothesis**: [What we expected]
**Duration**: [X days] | **Sample**: [N control / M variant]
| Metric | Control | Variant | Lift | p-value | Significant? |
|---|---|---|---|---|---|
| [Primary] | X% | Y% | +Z% | 0.0X | Yes/No |
| [Guardrail] | ... | ... | ... | ... | ... |
**Recommendation**: [Ship / Extend / Stop / Investigate]
**Reasoning**: [Why]
**Next steps**: [What to do]
```
Think step by step. Save as markdown. Generate Python scripts for calculations if raw data is provided.
---
### Further Reading
- [A/B Testing 101 + Examples](https://www.productcompass.pm/p/ab-testing-101-for-pms)
- [Testing Product Ideas: The Ultimate Validation Experiments Library](https://www.productcompass.pm/p/the-ultimate-experiments-library)
- [Are You Tracking the Right Metrics?](https://www.productcompass.pm/p/are-you-tracking-the-right-metrics)
================================================
FILE: pm-data-analytics/skills/cohort-analysis/SKILL.md
================================================
---
name: cohort-analysis
description: "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."
---
# Cohort Analysis & Retention Explorer
## Purpose
Analyze user engagement and retention patterns by cohort to identify trends in user behavior, feature adoption, and long-term engagement. Combine quantitative insights with qualitative research recommendations.
## How It Works
### Step 1: Read and Validate Your Data
- Accept CSV, Excel, or JSON data files with user cohort information
- Verify data structure: cohort identifier, time periods, engagement metrics
- Check for missing values and data quality issues
- Summarize key statistics (cohort sizes, date ranges, metrics available)
### Step 2: Generate Quantitative Analysis
- Calculate cohort retention rates and engagement trends
- Identify retention curves, drop-off patterns, and anomalies
- Compute feature adoption rates across cohorts
- Calculate month-over-month or period-over-period changes
- Generate Python analysis scripts using pandas and numpy if requested
### Step 3: Create Visualizations
- Generate retention heatmaps (cohorts vs. time periods)
- Create line charts showing cohort progression
- Build comparison charts for feature adoption
- Visualize drop-off points and engagement trends
- Output as interactive charts or static images
### Step 4: Identify Insights & Patterns
- Spot one or more significant patterns:
- Early churn in specific cohorts
- Late-stage engagement changes
- Feature adoption clusters
- Seasonal or temporal trends
- Highlight surprising findings and deviations
- Compare cohort performance to establish baselines
### Step 5: Suggest Follow-Up Research
- Recommend qualitative research methods:
- Targeted user interviews with churning users
- Feature usage surveys with engaged cohorts
- Session replays of key interaction patterns
- Win/loss analysis for high vs. low retention cohorts
- Design follow-up quantitative studies
- Suggest A/B tests or feature experiments
## Usage Examples
**Example 1: Upload CSV Data**
```
Upload cohort_engagement.csv with columns: cohort_month, weeks_active,
user_id, feature_x_usage, engagement_score
Request: "Analyze retention patterns and identify why Q4 2025 cohorts
underperform compared to Q3"
```
**Example 2: Describe Data Format**
```
"I have monthly user cohorts from Jan-Dec 2025. Each row shows:
cohort date, user ID, purchase frequency, and support tickets.
Analyze which cohorts show best long-term retention."
```
**Example 3: Feature Adoption Analysis**
```
Upload feature_usage.xlsx with cohort adoption data.
Request: "Compare adoption curves for our new feature across cohorts.
Which cohorts adopted fastest? Any patterns?"
```
## Key Capabilities
- **Data Reading**: Import CSV, Excel, JSON, SQL query results
- **Retention Analysis**: Calculate and visualize retention rates over time
- **Cohort Comparison**: Compare metrics across cohort groups
- **Anomaly Detection**: Flag unusual patterns or drop-offs
- **Python Scripts**: Generate reusable analysis code for ongoing analysis
- **Visualizations**: Create heatmaps, charts, and interactive dashboards
- **Research Design**: Suggest targeted follow-up studies and interview approaches
- **Statistical Summary**: Provide quantitative metrics and correlation analysis
## Tips for Best Results
1. **Include time dimension**: Provide data across multiple time periods
2. **Define cohort clearly**: Make cohort grouping explicit (signup month, feature launch date, etc.)
3. **Provide context**: Explain product changes, launches, or events during the period
4. **Multiple metrics**: Include retention, engagement, feature usage, revenue, etc.
5. **Sufficient data**: At least 3-4 cohorts for meaningful pattern identification
6. **Request specific output**: Ask for visualizations, Python scripts, or research recommendations
## Output Format
You'll receive:
- **Data Summary**: Cohort overview and data quality assessment
- **Quantitative Findings**: Key metrics, retention rates, and trend analysis
- **Visualizations**: Charts showing retention curves, adoption patterns
- **Pattern Identification**: 2-3 significant insights from the data
- **Research Recommendations**: Specific qualitative and quantitative follow-ups
- **Analysis Scripts** (if requested): Python code for reproducible analysis
- **Next Steps**: Prioritized actions based on findings
---
### Further Reading
- [Cohort Analysis 101: How to Reduce Churn and Make Better Product Decisions](https://www.productcompass.pm/p/cohort-analysis)
- [The Product Analytics Playbook: AARRR, HEART, Cohorts & Funnels for PMs](https://www.productcompass.pm/p/the-product-analytics-playbook-aarrr)
- [Are You Tracking the Right Metrics?](https://www.productcompass.pm/p/are-you-tracking-the-right-metrics)
================================================
FILE: pm-data-analytics/skills/sql-queries/SKILL.md
================================================
---
name: sql-queries
description: "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."
---
# SQL Query Generator
## Purpose
Transform natural language requirements into optimized SQL queries across multiple database platforms. This skill helps product managers, analysts, and engineers generate accurate queries without manual syntax work.
## How It Works
### Step 1: Understand Your Database Schema
- If you provide a schema file (SQL, documentation, or diagram description), I will read and analyze it
- Extract table names, column definitions, data types, and relationships
- Identify primary keys, foreign keys, and indexing strategies
### Step 2: Process Your Request
- Clarify the exact data you need to retrieve or analyze
- Confirm the SQL dialect (BigQuery, PostgreSQL, MySQL, Snowflake, etc.)
- Ask for any additional requirements (filters, aggregations, sorting)
### Step 3: Generate Optimized Query
- Write efficient SQL that leverages your database structure
- Include comments explaining complex logic
- Add performance considerations for large datasets
- Provide alternative approaches if applicable
### Step 4: Explain and Test
- Explain the query logic in plain English
- Suggest how to test or validate results
- Offer tips for performance optimization
- If you want, generate a test script or sample data
## Usage Examples
**Example 1: Query from Schema File**
```
Upload your database_schema.sql file and say:
"Generate a query to find users who signed up in the last 30 days
and had at least 5 active sessions"
```
**Example 2: Query from Diagram Description**
```
"Here's my database: Users table (id, email, created_at), Sessions table
(id, user_id, timestamp, duration). Generate a query for average session
duration per user in January 2026."
```
**Example 3: Complex Analysis Query**
```
"Create a BigQuery query to analyze our revenue by region and customer tier,
including year-over-year growth rates."
```
## Key Capabilities
- **Multi-Dialect Support**: Works with BigQuery, PostgreSQL, MySQL, Snowflake, SQL Server
- **File Reading**: Reads schema files, SQL dumps, and data documentation
- **Query Optimization**: Suggests indexes, partitioning, and performance improvements
- **Explanation**: Breaks down queries for learning and documentation
- **Testing**: Can generate test queries and sample data scripts
- **Script Execution**: Create executable SQL scripts for your database
## Tips for Best Results
1. **Provide context**: Share your database schema or structure
2. **Be specific**: Clearly describe what data you need and any filters
3. **Mention database**: Specify which SQL dialect you're using
4. **Include constraints**: Mention data volume, time ranges, and performance needs
5. **Request format**: Ask for the query result format if you need specific output
## Output Format
You'll receive:
- **SQL Query**: Production-ready SQL code with comments
- **Explanation**: What the query does and how it works
- **Performance Notes**: Optimization tips and considerations
- **Test Script** (if requested): Sample data and validation queries
---
### Further Reading
- [The Product Analytics Playbook: AARRR, HEART, Cohorts & Funnels for PMs](https://www.productcompass.pm/p/the-product-analytics-playbook-aarrr)
- [How to Become a Technology-Literate PM](https://www.productcompass.pm/p/how-to-become-a-technology-literate)
================================================
FILE: pm-execution/.claude-plugin/plugin.json
================================================
{
"name": "pm-execution",
"version": "1.0.1",
"description": "Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.",
"author": {
"name": "Paweł Huryn",
"email": "pawel@productcompass.pm",
"url": "https://www.productcompass.pm"
},
"keywords": [
"product-management",
"execution",
"prd",
"okrs",
"roadmap",
"sprint",
"pre-mortem",
"user-stories",
"backlog",
"prioritization",
"agile"
],
"homepage": "https://www.productcompass.pm",
"license": "MIT"
}
================================================
FILE: pm-execution/README.md
================================================
# pm-execution
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.
## Skills (15)
- **brainstorm-okrs** — Brainstorm team-level OKRs aligned with company objectives.
- **create-prd** — Create a Product Requirements Document using a comprehensive 8-section template covering summary, background, objectives, market segments, value propositions, solution details, and release planning.
- **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.
- **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 (10)
- `/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: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 comprehensive Product Requirements Document from a feature idea or problem statement.
- `/pm-execution:write-stories` — Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
## Author
Paweł Huryn — [The Product Compass Newsletter](https://www.productcompass.pm)
## License
MIT
================================================
FILE: pm-execution/commands/generate-data.md
================================================
---
description: Generate realistic dummy datasets for testing — CSV, JSON, SQL inserts, or Python scripts
argument-hint: "<description of the data you need>"
---
# /generate-data -- Test Data Generator
Create realistic dummy datasets for development, testing, demos, or prototyping. Outputs as ready-to-use files in your preferred format.
## Invocation
```
/generate-data 1000 users with names, emails, plan tier, signup date, and activity score
/generate-data E-commerce orders dataset: products, customers, timestamps, amounts
/generate-data Sample data matching this schema: [paste table definition]
```
## Workflow
### Step 1: Define the Dataset
Understand:
- What entities? (users, orders, events, products, etc.)
- What columns? (with data types and constraints)
- How many rows?
- Any relationships between tables?
- Any specific distributions? (e.g., "80% should be on the free plan")
- Any realistic constraints? (emails should be unique, dates should be chronological)
### Step 2: Generate the Data
Apply the **dummy-dataset** skill:
- Create a Python script that generates the dataset
- Use realistic-looking data (not random strings): proper names, valid email formats, real-seeming dates
- Respect constraints: unique IDs, foreign key relationships, chronological ordering
- Apply specified distributions
- Execute the script and produce the output file
### Step 3: Deliver
Output in the requested format (or ask):
- **CSV**: Most common, works everywhere
- **JSON**: For API testing or frontend development
- **SQL INSERT**: For populating test databases
- **Python script**: For reproducible generation (user can tweak and re-run)
```
## Generated Dataset: [Description]
**Rows**: [count]
**Columns**: [list]
**Format**: [CSV / JSON / SQL / Python]
### Schema
| Column | Type | Constraints | Distribution |
|--------|------|-----------|-------------|
### Sample (first 5 rows)
[Preview of the data]
### Files
- [data file]
- [generator script, if applicable]
```
Save data file and generator script to the user's workspace.
### Step 4: Offer Follow-ups
- "Want me to **add more columns** or **increase the dataset size**?"
- "Should I **create related tables** (e.g., orders for these users)?"
- "Want me to **write test scenarios** that use this data?"
- "Should I **create SQL queries** to analyze this dataset?"
## Notes
- Always provide the generator script so the user can regenerate with different parameters
- For demo datasets, make the data tell a story (e.g., seasonal trends, a retention problem, a power user segment)
- Respect realistic cardinality: 1000 users don't have 1000 unique cities
- For financial data, use realistic price distributions — not uniform random
- Never include real personal data — all names, emails, and identifiers must be fake
================================================
FILE: pm-execution/commands/meeting-notes.md
================================================
---
description: Summarize a meeting transcript into structured notes with decisions, action items, and follow-ups
argument-hint: "<transcript or meeting notes>"
---
# /meeting-notes -- Meeting Summary
Transform a raw meeting transcript or rough notes into clear, structured meeting minutes with decisions captured and action items assigned.
## Invocation
```
/meeting-notes [paste transcript]
/meeting-notes [upload transcript file, audio summary, or notes]
```
## Workflow
### Step 1: Accept the Transcript
Accept in any format:
- Full transcript (from Otter, Fireflies, Google Meet, Zoom, etc.)
- Rough notes taken during the meeting
- Audio summary or meeting recap from a transcription tool
- Multiple inputs (e.g., transcript + the user's own notes)
If the input is sparse, work with what's available and flag gaps.
### Step 2: Extract and Structure
Apply the **summarize-meeting** skill:
Parse the content to identify:
- **Participants**: Who was present (from introductions, speaker labels, or mentions)
- **Topics discussed**: Major agenda items or conversation threads
- **Decisions made**: Explicit agreements or conclusions reached
- **Action items**: Tasks assigned, with owner and deadline if mentioned
- **Open questions**: Unresolved items that need follow-up
- **Key quotes**: Important statements worth preserving verbatim
- **Context**: Meeting type, project, and background
### Step 3: Generate Meeting Summary
```
## Meeting Summary
**Date**: [date if known]
**Participants**: [names/roles]
**Meeting type**: [standup, planning, review, 1:1, stakeholder, etc.]
**Topic**: [primary subject]
### Summary
[3-5 sentence overview of what was discussed and concluded]
### Key Decisions
1. **[Decision]** — [context and rationale]
2. ...
### Action Items
| # | Action | Owner | Deadline | Status |
|---|--------|-------|----------|--------|
### Discussion Highlights
**[Topic 1]**: [key points, different perspectives, conclusion]
**[Topic 2]**: [key points, different perspectives, conclusion]
### Open Questions
- [Question] — needs input from [person/team]
### Next Steps
- [What happens next]
- Next meeting: [if mentioned]
```
Save as markdown.
### Step 4: Offer Follow-ups
- "Want me to **email these notes** to participants?"
- "Should I **create tickets** from the action items?"
- "Want me to **draft a stakeholder update** based on the decisions made?"
## Notes
- Decisions are the most valuable output — make sure every decision is captured clearly
- Action items without owners are useless — if no owner was mentioned, flag it
- Keep the summary concise — people who weren't in the meeting should get the gist in 30 seconds
- If the transcript is very long (60+ min meeting), offer a TL;DR before the full summary
- Distinguish between "discussed" and "decided" — many topics are explored without reaching a conclusion
================================================
FILE: pm-execution/commands/plan-okrs.md
================================================
---
description: Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results
argument-hint: "<team, product area, or company objective>"
---
# /plan-okrs -- Team OKR Planning
Generate well-structured OKRs that connect team work to company strategy. Produces 3 OKR sets with qualitative objectives and quantitative key results.
## Invocation
```
/plan-okrs Growth team Q2 — company goal is 50% ARR increase
/plan-okrs Onboarding squad aligned to "improve activation rate"
/plan-okrs [upload company OKRs or strategy doc]
```
## Workflow
### Step 1: Gather Context
Ask the user:
- What team or product area are these OKRs for?
- What time period? (quarterly is standard, but could be annual or custom)
- What are the company-level objectives these should ladder up to?
- What happened last quarter? (hits, misses, learnings)
- Any constraints or known priorities?
Accept company OKRs or strategy documents as uploads.
### Step 2: Generate OKRs
Apply the **brainstorm-okrs** skill:
- Create 3 OKR sets (Objective + 3-5 Key Results each)
- **Objectives**: Qualitative, inspiring, ambitious but achievable, action-oriented
- **Key Results**: Quantitative, measurable, time-bound, have clear owners
- Ensure OKRs ladder to company objectives with visible connection
- Balance leading indicators (activity) with lagging indicators (outcomes)
### Step 3: Validate Quality
Check each OKR against best practices:
- Is the Objective inspiring? (Would you rally a team around it?)
- Are Key Results measurable? (Can you check completion with data, not judgment?)
- Are targets ambitious but not demoralizing? (70% achievement = well-calibrated)
- Are there 3-5 KRs per Objective? (More = unfocused)
- Do KRs avoid gaming? (e.g., "ship 5 features" incentivizes shipping junk)
Flag any issues and suggest improvements.
### Step 4: Present and Iterate
```
## Team OKRs: [Team Name] — [Period]
**Aligned to**: [Company Objective(s)]
### Objective 1: [Inspiring qualitative statement]
| # | Key Result | Baseline | Target | Owner |
|---|-----------|----------|--------|-------|
| KR1 | [measurable result] | [current] | [target] | [team/person] |
| KR2 | ... | ... | ... | ... |
| KR3 | ... | ... | ... | ... |
### Objective 2: [Inspiring qualitative statement]
[same format]
### Objective 3: [Inspiring qualitative statement]
[same format]
### Alignment Map
Company Objective → Team Objective → Key Results → Expected Impact
### Scoring Guide
- 0.0-0.3: Significant miss — investigate and learn
- 0.4-0.6: Progress made but fell short
- 0.7-0.9: Well-calibrated stretch goal — this is the target zone
- 1.0: Either nailed it or target wasn't ambitious enough
### Check-in Cadence
- **Weekly**: Quick traffic-light update on each KR
- **Mid-quarter**: Deep review, adjust targets if context changed
- **End of quarter**: Score, reflect, feed into next quarter
```
Offer:
- "Want me to **adjust ambition levels** — make them more/less aggressive?"
- "Should I **create a metrics dashboard** for tracking these?"
- "Want me to **draft a stakeholder update** introducing these OKRs?"
## Notes
- OKRs should describe outcomes, not outputs ("Increase activation by 20%" not "Ship onboarding redesign")
- If the user doesn't have company OKRs, help them derive team objectives from product strategy or business goals
- Maximum 3 objectives per team per quarter — more means less focus
- Key Results should be stretch goals — if you're certain you'll hit them, they're not ambitious enough
- Flag any KR that could be gamed and suggest a counter-metric
================================================
FILE: pm-execution/commands/pre-mortem.md
================================================
---
description: Run a pre-mortem risk analysis on a PRD, launch plan, or feature — identify what could go wrong before it does
argument-hint: "<PRD, plan, or feature description>"
---
# /pre-mortem -- Pre-Launch Risk Analysis
Imagine your launch has failed. Now work backward to figure out why. This command applies the Tigers/Paper Tigers/Elephants framework to surface real risks and create mitigation plans.
## Invocation
```
/pre-mortem [paste or upload a PRD, launch plan, or feature spec]
/pre-mortem We're launching a self-serve billing portal next month
```
## Workflow
### Step 1: Accept the Plan
Accept in any format: PRD, feature spec, launch plan, project brief, or verbal description. The more detail provided, the sharper the risk analysis.
### Step 2: Risk Identification
Apply the **pre-mortem** skill:
Imagine the product has launched and failed. Generate risks across categories:
- **Technical**: Performance, scalability, integration failures, data issues
- **User**: Adoption barriers, usability problems, unmet expectations
- **Business**: Revenue impact, competitive response, market timing
- **Operational**: Support load, documentation gaps, training needs
- **Dependencies**: Third-party services, cross-team handoffs, regulatory
### Step 3: Classify Risks
Categorize each risk:
**Tigers** — Real, substantive risks that could cause failure
- Assess severity: Launch-blocking / Fast-follow / Track
- For launch-blocking Tigers: immediate mitigation required
- For fast-follow Tigers: plan to address within first sprint post-launch
- For track Tigers: monitor but don't delay launch
**Paper Tigers** — Risks that feel scary but are overblown
- Explain why the concern is manageable
- Note what would need to change for this to become a real Tiger
**Elephants** — Unspoken risks the team knows about but avoids discussing
- Surface political, organizational, or uncomfortable risks
- Frame constructively with suggested conversation starters
### Step 4: Generate Pre-Mortem Report
```
## Pre-Mortem: [Feature/Launch]
**Date**: [today]
**Status**: [Draft / Reviewed]
### Risk Summary
- **Tigers**: [count] ([launch-blocking], [fast-follow], [track])
- **Paper Tigers**: [count]
- **Elephants**: [count]
### Launch-Blocking Tigers
| # | Risk | Likelihood | Impact | Mitigation | Owner | Deadline |
|---|------|-----------|--------|-----------|-------|----------|
### Fast-Follow Tigers
| # | Risk | Likelihood | Impact | Planned Response | Owner |
|---|------|-----------|--------|-----------------|-------|
### Track Tigers
[Risks to monitor post-launch with trigger conditions]
### Paper Tigers
[Concerns that seem big but are manageable — with reasoning]
### Elephants in the Room
[Uncomfortable truths the team should discuss]
### Go/No-Go Checklist
- [ ] All launch-blocking Tigers mitigated
- [ ] Fast-follow plan documented and assigned
- [ ] Monitoring in place for Track Tigers
- [ ] Rollback plan defined
- [ ] Support team briefed
```
Save as markdown.
### Step 5: Offer Next Steps
- "Want me to **update the PRD** with risk mitigations?"
- "Should I **create test scenarios** for the riskiest areas?"
- "Want me to **draft a launch checklist** from these findings?"
## Notes
- The best pre-mortems happen when the plan is 80% done — early enough to change course, late enough to have substance
- Push past the obvious risks — the most dangerous risks are the ones nobody mentions
- Elephants are the highest-value output — surfacing what the team avoids discussing
- For each Tiger, the mitigation should be specific and assignable, not "be careful"
- If the pre-mortem reveals too many launch-blocking Tigers, recommend delaying or phasing the launch
================================================
FILE: pm-execution/commands/sprint.md
================================================
---
description: Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes
argument-hint: "[plan|retro|release-notes] <context>"
---
# /sprint -- Sprint Lifecycle
Three modes covering the sprint lifecycle: **plan** for sprint planning, **retro** for retrospectives, **release-notes** for shipping communication.
## Invocation
```
/sprint plan 2-week sprint, 4 engineers, focus on checkout improvements
/sprint retro [paste team feedback or sprint data]
/sprint release-notes [paste tickets, changelog, or PRD]
/sprint # asks which phase you're in
```
## Modes
---
### Plan Mode
Prepare for sprint planning with capacity estimation, story selection, and risk identification.
#### Workflow
**Step 1: Gather Sprint Context**
- Sprint duration (1 or 2 weeks)
- Team composition (engineers, designers, QA — and availability)
- Sprint goal or focus area
- Backlog items to consider (paste, upload, or describe)
- Any carry-over from last sprint
- Known interruptions (holidays, on-call, meetings)
**Step 2: Estimate Capacity**
Apply the **sprint-plan** skill:
- Calculate available engineering hours/points after meetings, on-call, PTO
- Apply a velocity adjustment based on historical data (if provided) or industry standard (70% of theoretical capacity)
- Show capacity breakdown per team member
**Step 3: Select and Sequence Stories**
- Recommend which stories fit within capacity
- Flag dependency chains (A must complete before B starts)
- Identify risks: stories that are underspecified, have external dependencies, or need design input
- Balance quick wins with larger items
- Ensure every story has acceptance criteria
**Step 4: Generate Sprint Plan**
```
## Sprint Plan: [Sprint Name/Number]
**Duration**: [dates]
**Sprint Goal**: [one sentence]
**Team**: [members and availability]
### Capacity
| Member | Available Days | Points/Hours | Notes |
|--------|--------------|-------------|-------|
**Total capacity**: [X] points/hours
**Recommended commitment**: [Y] points/hours (with buffer)
### Selected Stories
| # | Story | Points | Owner | Dependencies | Risk |
|---|-------|--------|-------|-------------|------|
### Sprint Risks
1. [Risk] — Mitigation: [action]
### Definition of Done
- [ ] Code reviewed
- [ ] Tests passing
- [ ] Deployed to staging
- [ ] QA approved
- [ ] Documentation updated (if applicable)
```
---
### Retro Mode
Facilitate a structured retrospective that produces actionable improvements.
#### Workflow
**Step 1: Gather Sprint Feedback**
Accept input as:
- Team feedback (pasted from a survey, Slack, or collaborative doc)
- Sprint metrics (velocity, bugs, incidents)
- The user's own observations
Ask: "Which retro format do you prefer?"
- **Start/Stop/Continue** (simple, fast)
- **4Ls** (Liked, Learned, Lacked, Longed for)
- **Sailboat** (Wind = helps, Anchor = slows, Rocks = risks, Island = goals)
**Step 2: Analyze and Structure**
Apply the **retro** skill:
- Categorize feedback into the chosen framework
- Identify themes and patterns
- Separate symptoms from root causes
- Highlight wins worth celebrating
**Step 3: Generate Retro Summary**
```
## Sprint Retrospective: [Sprint Name]
**Date**: [today]
**Format**: [Start/Stop/Continue | 4Ls | Sailboat]
**Participants**: [if known]
### What Went Well
[Grouped themes with supporting evidence]
### What Didn't Go Well
[Grouped themes with root cause analysis]
### Key Insights
[2-3 patterns that emerged]
### Action Items
| # | Action | Owner | Deadline | Priority |
|---|--------|-------|----------|----------|
### Metrics This Sprint
| Metric | This Sprint | Last Sprint | Trend |
|--------|-----------|------------|-------|
```
---
### Release Notes Mode
Generate user-facing release notes from technical artifacts.
#### Workflow
**Step 1: Accept Release Content**
Accept:
- Jira/Linear tickets or changelog
- PRD or feature specs
- Git commit messages or PR descriptions
- Team's internal summary of what shipped
**Step 2: Transform**
Apply the **release-notes** skill:
- Translate technical language into user benefits
- Categorize as: New Features, Improvements, Bug Fixes
- Write in the product's voice (ask about tone if not clear)
- Highlight the most impactful change first
**Step 3: Generate Release Notes**
```
## What's New — [Version/Date]
### Highlights
[1-2 sentence summary of the most important change]
### New Features
- **[Feature Name]** — [user-facing benefit in plain language]
### Improvements
- **[Improvement]** — [what's better now]
### Bug Fixes
- Fixed [issue] that caused [user impact]
### Coming Soon
[Optional teaser for next release]
```
Save as markdown and offer to format for different channels (blog post, in-app, email, Slack announcement).
## Notes
- For plan mode: protect 20% buffer for unplanned work — teams that plan at 100% capacity always miss
- For retro mode: focus on 2-3 high-impact action items, not 10 things nobody will do
- For release notes: always frame changes as user benefits, not technical implementations
- Each mode can chain to the others: plan → (sprint happens) → retro → release-notes
================================================
FILE: pm-execution/commands/stakeholder-map.md
================================================
---
description: Map stakeholders on a Power × Interest grid and create a tailored communication plan
argument-hint: "<project, initiative, or launch>"
---
# /stakeholder-map -- Stakeholder Mapping & Communication Plan
Identify all stakeholders for a project, map them by influence and interest, and generate a communication plan that ensures the right people get the right information at the right time.
## Invocation
```
/stakeholder-map New analytics platform launch
/stakeholder-map Pricing model change affecting all customers
/stakeholder-map [upload a project brief or org chart]
```
## Workflow
### Step 1: Understand the Initiative
Ask:
- What is the project or initiative?
- What phase is it in? (planning, building, launching, post-launch)
- Who are the obvious stakeholders you already know about?
- Are there any politically sensitive dynamics to be aware of?
### Step 2: Identify Stakeholders
Brainstorm stakeholders the user might not have considered:
- **Internal**: Engineering, Design, QA, Data, Legal, Finance, Marketing, Sales, Support, Leadership
- **External**: Customers, partners, vendors, regulators, board members
- **Often missed**: Adjacent teams, on-call engineers, customer success, documentation team
### Step 3: Map to Power × Interest Grid
Apply the **stakeholder-map** skill:
Place each stakeholder in a quadrant:
```
HIGH INTEREST
│
KEEP SATISFIED │ MANAGE CLOSELY
(High Power, │ (High Power,
Low Interest) │ High Interest)
│
──────────────────────┼──────────────────────
│
MONITOR │ KEEP INFORMED
(Low Power, │ (Low Power,
Low Interest) │ High Interest)
│
LOW INTEREST
```
### Step 4: Generate Communication Plan
```
## Stakeholder Map: [Initiative]
### Stakeholder Grid
| Stakeholder | Role | Power | Interest | Quadrant | Stance |
|------------|------|-------|----------|----------|--------|
### Communication Plan
#### Manage Closely (High Power, High Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Keep Satisfied (High Power, Low Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Keep Informed (Low Power, High Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Monitor (Low Power, Low Interest)
[Minimal communication — include in broad updates only]
### Potential Conflicts
[Where stakeholder interests may clash — with mitigation strategies]
### Escalation Path
[Who to go to when decisions are blocked]
### RACI Matrix
| Decision Area | Responsible | Accountable | Consulted | Informed |
|--------------|-------------|-------------|-----------|----------|
```
Save as markdown.
### Step 5: Offer Next Steps
- "Want me to **draft the first stakeholder update** for the 'Manage Closely' group?"
- "Should I **create a meeting prep brief** for key stakeholder conversations?"
- "Want me to **set up a communication cadence** as a recurring checklist?"
## Notes
- The "Manage Closely" quadrant is where PMs spend most of their political capital — get these relationships right
- "Stance" (supportive, neutral, resistant) helps prioritize where to invest relationship-building effort
- Don't forget downstream stakeholders: support, docs, and sales enablement teams are often surprised by launches
- Update the map as the project evolves — stakeholder interest shifts with project phase
================================================
FILE: pm-execution/commands/test-scenarios.md
================================================
---
description: Generate comprehensive test scenarios from user stories or feature specs — happy paths, edge cases, and error handling
argument-hint: "<user stories, feature spec, or description>"
---
# /test-scenarios -- Test Scenario Generator
Turn user stories or feature descriptions into comprehensive test scenarios that QA can execute immediately. Covers happy paths, edge cases, error handling, and cross-browser/device considerations.
## Invocation
```
/test-scenarios [paste user stories or acceptance criteria]
/test-scenarios [upload a PRD or feature spec]
/test-scenarios User can reset their password via email link
```
## Workflow
### Step 1: Accept Input
Accept: user stories, acceptance criteria, PRD sections, feature descriptions, or any specification of expected behavior.
### Step 2: Generate Test Scenarios
Apply the **test-scenarios** skill:
For each user story or requirement, generate:
**Happy Path Scenarios**: The expected user flow works correctly
**Edge Cases**: Boundary conditions, unusual inputs, concurrent operations
**Error Scenarios**: What happens when things go wrong
**Security Scenarios**: If applicable (auth, permissions, data access)
**Performance Scenarios**: If applicable (load, timeout, large data)
### Step 3: Structure Output
```
## Test Scenarios: [Feature]
**Source**: [user stories / PRD / description]
**Total scenarios**: [count]
**Coverage**: [happy path / edge cases / errors / security / performance]
### Scenario 1: [Title]
**Tests**: [which story or requirement]
**Preconditions**: [setup needed]
**User role**: [who is performing this]
| Step | Action | Expected Result |
|------|--------|----------------|
| 1 | [user action] | [expected system response] |
| 2 | [user action] | [expected system response] |
**Postconditions**: [state after completion]
**Priority**: [Critical / High / Medium / Low]
---
[Repeat for each scenario]
### Coverage Matrix
| Requirement | Happy Path | Edge Cases | Error Handling | Notes |
|------------|-----------|-----------|---------------|-------|
### Test Data Requirements
[What test data is needed to execute these scenarios]
```
Save as markdown.
### Step 4: Offer Next Steps
- "Want me to **generate the test data** for these scenarios?"
- "Should I **add more edge cases** for any specific scenario?"
- "Want me to **create the user stories** that these scenarios test?"
## Notes
- Happy paths first, then layer in edge cases — ensure basic flows work before testing boundaries
- Every acceptance criterion from the original story should map to at least one test scenario
- Include both positive tests (it works) and negative tests (it fails gracefully)
- For APIs, include scenarios for rate limiting, timeout, malformed requests, and auth failures
- Flag scenarios that require specific test environments or third-party service mocking
================================================
FILE: pm-execution/commands/transform-roadmap.md
================================================
---
description: Convert a feature-based roadmap into an outcome-focused roadmap that communicates strategic intent
argument-hint: "<roadmap as text, file, or list of planned features>"
---
# /transform-roadmap -- Outcome-Focused Roadmap
Take a list of planned features or an output-focused roadmap and rewrite it as an outcome-focused roadmap that communicates *why* instead of *what*.
## Invocation
```
/transform-roadmap [paste your feature list or roadmap]
/transform-roadmap [upload a roadmap doc, spreadsheet, or screenshot]
```
## Workflow
### Step 1: Accept the Current Roadmap
Accept in any format:
- Feature list or backlog items
- Roadmap document (Now/Next/Later, quarterly, timeline)
- Spreadsheet or Gantt chart export
- Screenshot of a roadmap tool
Parse each item to extract: feature name, description, target date/timeframe, and any context.
### Step 2: Understand Strategic Context
Ask:
- What are the product goals or OKRs for this period?
- Who is the audience for this roadmap? (execs, engineering, customers, board)
- What format do you prefer? (Now/Next/Later, quarterly, timeline)
### Step 3: Transform Each Item
Apply the **outcome-roadmap** skill:
For each feature/output on the roadmap:
1. Identify the **user or business outcome** it's trying to achieve
2. Rewrite as an outcome statement: "[Verb] [metric/experience] for [user segment]"
3. Group features that serve the same outcome under one initiative
4. Add success metrics to each outcome
**Before → After examples:**
- "Build SSO integration" → "Reduce enterprise onboarding friction — target: 50% faster time-to-first-value for enterprise accounts"
- "Redesign dashboard" → "Help power users find insights faster — target: 30% reduction in time-to-insight"
- "Add CSV export" → "Enable teams to share data outside the product — target: 25% increase in report sharing"
### Step 4: Generate Transformed Roadmap
```
## Outcome-Focused Roadmap: [Product] — [Period]
**Strategic themes**: [2-3 high-level themes]
### Now (Current Quarter)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Status |
|---------|---------------|----------------|--------|
### Next (Next Quarter)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Confidence |
|---------|---------------|----------------|------------|
### Later (Future)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Dependencies |
|---------|---------------|----------------|-------------|
### Transformation Notes
| Original Feature | Transformed Outcome | Why This Framing |
|-----------------|--------------------|-----------------|
### What Changed
[Summary of how the roadmap narrative shifted]
```
Save as a markdown file.
### Step 5: Review
Offer:
- "Want me to **add OKR alignment** for each outcome?"
- "Should I **draft a stakeholder presentation** of this roadmap?"
- "Want me to **identify risks** for the Now items?"
## Notes
- Outcomes should be measurable and have a clear "done" state
- Multiple features can map to one outcome — this is a feature, not a bug
- If an output doesn't clearly serve an outcome, flag it for the user to justify or deprioritize
- The audience matters: exec roadmaps should be outcome-only, engineering roadmaps can include deliverables under each outcome
- "Later" items should be less specific — outcomes without committed solutions
================================================
FILE: pm-execution/commands/write-prd.md
================================================
---
description: Create a comprehensive Product Requirements Document from a feature idea or problem statement
argument-hint: "<feature or problem statement>"
---
# /write-prd -- Product Requirements Document
Create a structured PRD that aligns stakeholders and guides development. Accepts anything from a vague idea to a detailed brief.
## Invocation
```
/write-prd SSO support for enterprise customers
/write-prd Users are dropping off during onboarding — we need to fix step 3
/write-prd [upload a brief, research doc, or strategy deck]
```
## Workflow
### Step 1: Understand the Feature
Accept the input in any form:
- A feature name ("SSO support")
- A problem statement ("Enterprise customers keep asking for centralized auth")
- A user request ("Users want to export their data as CSV")
- A vague idea ("We should do something about onboarding drop-off")
- An uploaded document (brief, research, Slack thread, email)
### Step 2: Gather Context
Ask conversationally — most important questions first, fill gaps as you go:
1. **User problem**: What problem does this solve? Who experiences it? How painful is it?
2. **Target users**: Which user segment(s)? How many? What's their current workaround?
3. **Success metrics**: How will we know this worked? What moves if we nail it?
4. **Constraints**: Technical constraints, timeline, regulatory, dependencies on other teams?
5. **Prior art**: Has this been attempted before? Existing solutions in the market?
6. **Scope preference**: Full solution or phased approach?
If the user provides a document with context, extract what's available and only ask about gaps.
### Step 3: Generate the PRD
Apply the **create-prd** skill to produce an 8-section document:
```
## Product Requirements Document: [Feature Name]
**Author**: [user]
**Date**: [today]
**Status**: Draft
**Stakeholders**: [if known]
### 1. Executive Summary
[2-3 sentences: what, for whom, why now]
### 2. Background & Context
[Problem space, prior research, market context, what prompted this]
### 3. Objectives & Success Metrics
**Goals** (what success looks like):
1. [Specific, measurable goal]
2. [...]
**Non-Goals** (explicitly out of scope):
1. [What we're not doing, and why]
2. [...]
**Success Metrics**:
| Metric | Current | Target | Measurement |
|--------|---------|--------|-------------|
### 4. Target Users & Segments
[Who this serves, user profiles, segment sizing]
### 5. User Stories & Requirements
**P0 — Must Have**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
**P1 — Should Have**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
**P2 — Nice to Have / Future**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
### 6. Solution Overview
[High-level approach, key design decisions, technical approach if known]
### 7. Open Questions
| Question | Owner | Deadline |
|----------|-------|----------|
### 8. Timeline & Phasing
[Milestones, dependencies, phasing if applicable]
```
### Step 4: Review and Iterate
After generating, offer:
- "Want me to **tighten the scope**? I can challenge which P1s should really be P2s."
- "Should I **run a pre-mortem** on this PRD?"
- "Want me to **break this into user stories** for engineering?"
- "Should I **create a stakeholder update** to socialize this?"
Save the PRD as a markdown file to the user's workspace.
## Notes
- Be opinionated about scope — a tight PRD is better than an expansive vague one
- If the idea is too big, proactively suggest phasing and spec only Phase 1
- Non-goals are as important as goals — they prevent scope creep
- Success metrics must be specific: "improve NPS" is bad, "increase NPS from 32 to 45 within 90 days of launch" is good
- Open questions should be genuinely unresolved — don't list things you can answer from context
- If the user provides research, weave insights into the Background section with attribution
================================================
FILE: pm-execution/commands/write-stories.md
================================================
---
description: Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria
argument-hint: "[user|job|wwa] <feature description or PRD>"
---
# /write-stories -- Backlog Item Generator
Break a feature into well-structured backlog items. Choose from three formats based on your team's preference, each with full acceptance criteria.
## Invocation
```
/write-stories user Allow users to export reports as PDF and CSV
/write-stories job Notification system for task deadlines
/write-stories wwa Dark mode for the mobile app
/write-stories [upload a PRD or feature spec] # asks format preference
/write-stories # asks for feature and format
```
## Formats
### User Stories
**Format**: "As a [user type], I want [capability], so that [benefit]"
Apply the **user-stories** skill:
- Follow the 3 C's: Card (brief), Conversation (context), Confirmation (acceptance criteria)
- Validate against INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable
- Include design links or mockup references where relevant
### Job Stories
**Format**: "When [situation], I want to [motivation], so I can [outcome]"
Apply the **job-stories** skill:
- Focus on the situation and context, not the user role
- Ground in real user scenarios observed in research
- Ideal for JTBD-oriented teams
### WWA (Why-What-Acceptance)
**Format**: Why [strategic context] → What [deliverable] → Acceptance [criteria]
Apply the **wwas** skill:
- Includes strategic reasoning (why we're building this)
- Produces independent, valuable, testable items
- Good for cross-functional teams that need business context
## Workflow
### Step 1: Accept the Feature
Accept in any form: PRD, feature description, user research finding, or verbal idea. If a PRD is provided, extract the requirements to decompose.
### Step 2: Determine Format
If not specified in the invocation, ask:
- "Which format does your team use? **User stories**, **Job stories**, or **WWA**?"
- If unsure, recommend user stories as the default
### Step 3: Decompose the Feature
- Break the feature into 5-15 independent stories (small enough to complete in one sprint)
- Ensure each story is independently valuable (delivers user value on its own)
- Order by dependency and priority
- Write 3-5 acceptance criteria per story
- Flag stories that need design input or technical spikes
### Step 4: Generate Stories
```
## Backlog: [Feature Name]
**Format**: [User Stories / Job Stories / WWA]
**Total stories**: [count]
**Estimated total effort**: [if possible]
### Stories
#### Story 1: [Short title]
**[The story in chosen format]**
Acceptance Criteria:
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
Priority: [P0/P1/P2] | Effort: [S/M/L] | Dependencies: [none or list]
---
[Repeat for each story]
### Story Map
[Visual ordering: must-have → should-have → nice-to-have]
### Technical Notes
[Cross-cutting concerns: API changes, data migration, infrastructure]
### Open Questions
[Things that need answers before implementation can start]
```
Save as markdown.
### Step 5: Offer Next Steps
- "Want me to **generate test scenarios** for these stories?"
- "Should I **create dummy data** for development and testing?"
- "Want me to **estimate sprint capacity** for these stories?"
- "Should I **convert to a different format** (user stories ↔ job stories ↔ WWA)?"
## Notes
- One story = one deployable unit of value — if it needs another story to be useful, they should be combined
- Acceptance criteria should be testable by QA without additional interpretation
- Error handling and edge cases deserve their own stories, not bullet points within a happy-path story
- If the feature is large (15+ stories), suggest grouping into epics or phases
- Flag any story that requires a spike (technical investigation before estimation is possible)
================================================
FILE: pm-execution/skills/brainstorm-okrs/SKILL.md
================================================
---
name: brainstorm-okrs
description: "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."
---
# Brainstorm Team OKRs
## Purpose
You are a veteran product leader responsible for defining Objectives and Key Results (OKRs) for the team working on $ARGUMENTS. Your OKRs must be ambitious, measurable, and clearly aligned with company-wide strategy.
## Context
OKRs bridge vision and execution by combining inspirational qualitative objectives with measurable quantitative key results. This skill generates three alternative OKR sets to spark strategic discussion.
## Domain Context
**OKR** (Christina Wodtke, *Radical Focus*):
- **Objective** (Why, What, When): Qualitative, inspirational, time-bound goal. Typically quarterly. Should be SMART.
- **Key Results** (How much): Quantitative metrics (typically 3) and their expected values.
**OKRs, KPIs, and NSM are interconnected — not alternatives.** Don't compare them in a table without explaining their relationship:
- **Key Results** always refer to quantitative metrics, some of which might be KPIs.
- **KPIs** = a few key quantitative metrics tracked over a longer period. Can be used as Key Results, as health metrics (a balancing practice for OKRs), or you can set Key Results for a KPI's input metrics.
- **North Star Metric** = a single, customer-centric KPI. A leading indicator of business success. You can use Key Results to express expected change in NSM.
OKRs are fundamentally about: (1) Setting a single, inspiring goal. (2) Empowering a team to determine the optimal approach. (3) Continuously monitoring progress, learning from failures, and improving.
## Instructions
1. **Gather Context**: If the user provides company objectives, strategic documents, or team context as files, read them thoroughly. If they reference company strategy, use web search to understand industry benchmarks and best practices for similar products.
2. **Understand the Framework**: OKRs have two components:
- **Objective**: A qualitative, inspirational goal describing the directional intent
- **Key Results**: 3 quantitative metrics (typically) measuring progress toward the objective
3. **Think Step by Step**:
- What is the company strategy?
- What are the 3-5 most impactful areas the team can influence?
- How do team efforts ladder up to company goals?
- What would success look like for customers and the business?
4. **Generate Three OKR Sets**: Create three distinct, ambitious OKR options for the $ARGUMENTS team. For each set:
- Start with a clear, inspiring Objective statement
- Define exactly 3 Key Results that are:
- Measurable (can be tracked numerically)
- Achievable but ambitious (60-70% confidence level)
- Aligned with company strategy
5. **Example Format**:
```
Objective: Delight new users with an effortless onboarding experience
Key Results:
- CSAT score >= 75% on onboarding survey
- 66%+ of onboardings completed within two days
- Average time-to-value (TTV) <= 20 minutes
```
6. **Structure Output**: Present all three OKR sets with equal weight. For each, include:
- Objective (1-2 sentences)
- Three Key Results (specific metrics with targets)
- Brief rationale (why this matters to the company and team)
7. **Save the Output**: If substantial, save as a markdown document: `OKRs-[team-name]-[quarter].md`
## Notes
- Ensure each Key Result is independently measurable
- Avoid output-focused metrics (e.g., "launch 5 features"); focus on outcomes
- All three OKR sets should be credible, not one clearly better than others
- Flag any assumptions about data availability
---
### Further Reading
- [Objectives and Key Results (OKRs) 101](https://www.productcompass.pm/p/okrs-101-advanced-techniques)
- [OKR vs KPI: What's the Difference?](https://www.productcompass.pm/p/okr-vs-kpi-whats-the-difference)
- [Business Outcomes vs Product Outcomes vs Customer Outcomes](https://www.productcompass.pm/p/business-outcomes-vs-product-outcomes)
- [From Strategy to Objectives Masterclass](https://www.productcompass.pm/p/product-vision-strategy-objectives-course) (video course)
================================================
FILE: pm-execution/skills/create-prd/SKILL.md
================================================
---
name: create-prd
description: "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."
---
# Create a Product Requirements Document
## Purpose
You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.
## Context
A well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.
## Instructions
1. **Gather Information**: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.
2. **Think Step by Step**: Before writing, analyze:
- What problem are we solving?
- Who are we solving it for?
- How will we measure success?
- What are our constraints and assumptions?
3. **Apply the PRD Template**: Create a document with these 8 sections:
**1. Summary** (2-3 sentences)
- What is this document about?
**2. Contacts**
- Name, role, and comment for key stakeholders
**3. Background**
- Context: What is this initiative about?
- Why now? Has something changed?
- Is this something that just recently became possible?
**4. Objective**
- What's the objective? Why does it matter?
- How will it benefit the company and customers?
- How does it align with vision and strategy?
- Key Results: How will you measure success? (Use SMART OKR format)
**5. Market Segment(s)**
- For whom are we building this?
- What constraints exist?
- Note: Markets are defined by people's problems/jobs, not demographics
**6. Value Proposition(s)**
- What customer jobs/needs are we addressing?
- What will customers gain?
- Which pains will they avoid?
- Which problems do we solve better than competitors?
- Consider the Value Curve framework
**7. Solution**
- 7.1 UX/Prototypes (wireframes, user flows)
- 7.2 Key Features (detailed feature descriptions)
- 7.3 Technology (optional, only if relevant)
- 7.4 Assumptions (what we believe but haven't proven)
**8. Release**
- How long could it take?
- What goes in the first version vs. future versions?
- Avoid exact dates; use relative timeframes
4. **Use Accessible Language**: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
5. **Structure Output**: Present the PRD as a well-formatted markdown document with clear headings and sections.
6. **Save the Output**: If the PRD is substantial (which it will be), save it as a markdown document in the format: `PRD-[product-name].md`
## Notes
- Be specific and data-driven where possible
- Link each section back to the overall strategy
- Flag assumptions clearly so the team can validate them
- Keep the document concise but complete
---
### Further Reading
- [How to Write a Product Requirements Document? The Best PRD Template.](https://www.productcompass.pm/p/prd-template)
- [A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)](https://www.productcompass.pm/p/ai-prd-template)
================================================
FILE: pm-execution/skills/dummy-dataset/SKILL.md
================================================
---
name: dummy-dataset
description: "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."
---
# Dummy Dataset Generation
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Creates executable scripts or direct data files for immediate use.
**Use when:** Creating test data, generating sample datasets, building realistic mock data for development, or populating test environments.
**Arguments:**
- `$PRODUCT`: The product or system name
- `$DATASET_TYPE`: Type of data (e.g., customer feedback, transactions, user profiles)
- `$ROWS`: Number of rows to generate (default: 100)
- `$COLUMNS`: Specific columns or fields to include
- `$FORMAT`: Output format (CSV, JSON, SQL, Python script)
- `$CONSTRAINTS`: Additional constraints or business rules
## Step-by-Step Process
1. **Identify dataset type** - Understand the data domain
2. **Define column specifications** - Names, data types, and value ranges
3. **Determine row count** - How many sample records needed
4. **Select output format** - CSV, JSON, SQL INSERT, or Python script
5. **Apply realistic patterns** - Ensure data looks authentic and valid
6. **Add business constraints** - Respect business logic and relationships
7. **Generate or script data** - Create executable output
8. **Validate output** - Ensure data quality and completeness
## Template: Python Script Output
```python
import csv
import json
from datetime import datetime, timedelta
import random
# Configuration
ROWS = $ROWS
FILENAME = "$DATASET_TYPE.csv"
# Column definitions with realistic value generators
columns = {
"id": "auto-increment",
"name": "first_last_name",
"email": "email",
"created_at": "timestamp",
# Add more columns...
}
def generate_dataset():
"""Generate realistic dummy dataset"""
data = []
for i in range(1, ROWS + 1):
record = {
"id": f"U{i:06d}",
# Generate values based on column definitions
}
data.append(record)
return data
def save_as_csv(data, filename):
"""Save dataset as CSV"""
with open(filename, 'w', newline='') as f:
writer = csv.DictWriter(f, fieldnames=data[0].keys())
writer.writeheader()
writer.writerows(data)
if __name__ == "__main__":
dataset = generate_dataset()
save_as_csv(dataset, FILENAME)
print(f"Generated {len(dataset)} records in {FILENAME}")
```
## Example Dataset Specification
**Dataset Type:** Customer Feedback
**Columns:**
- feedback_id (auto-increment, U001, U002...)
- customer_name (realistic names)
- email (valid email format)
- feedback_date (dates last 90 days)
- rating (1-5 stars)
- category (Bug, Feature Request, Complaint, Praise)
- text (realistic feedback)
- product (electronics, clothing, home)
**Constraints:**
- Ratings skewed: 40% 5-star, 30% 4-star, 20% 3-star, 10% 1-2 star
- Bug category only with ratings 1-3
- Feature requests only with ratings 3-5
- Email domains realistic (gmail, yahoo, company.com)
## Output Deliverables
- Ready-to-execute Python script OR direct data file
- CSV file with proper headers and formatting
- JSON file with valid structure and types
- SQL INSERT statements for database population
- Data validation and constraint compliance
- Realistic, business-appropriate values
- Documentation of data generation logic
- Quick-start instructions for using the dataset
## Output Formats
**CSV:** Flat tabular format, easy to import into spreadsheets and databases
**JSON:** Nested structure, ideal for APIs and NoSQL databases
**SQL:** INSERT statements, directly executable on relational databases
**Python Script:** Executable generator for custom or large datasets
================================================
FILE: pm-execution/skills/job-stories/SKILL.md
================================================
---
name: job-stories
description: "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."
---
# Job Stories
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format. Generates stories with detailed acceptance criteria focused on user situations and outcomes.
**Use when:** Writing job stories, expressing user situations and motivations, creating JTBD-style backlog items, or focusing on user context rather than roles.
**Arguments:**
- `$PRODUCT`: The product or system name
- `$FEATURE`: The new feature to break into job stories
- `$DESIGN`: Link to design files (Figma, Miro, etc.)
- `$CONTEXT`: User situations or job scenarios
## Step-by-Step Process
1. **Identify user situations** that trigger the need
2. **Define motivations** underlying the user's behavior
3. **Clarify outcomes** the user wants to achieve
4. **Apply JTBD framework:** Focus on the job, not the role
5. **Create acceptance criteria** that validate the outcome is achieved
6. **Use observable, measurable language**
7. **Link to design mockups** or prototypes
8. **Output job stories** with detailed acceptance criteria
## Story Template
**Title:** [Job outcome or result]
**Description:** When [situation], I want to [motivation], so I can [outcome].
**Design:** [Link to design files]
**Acceptance Criteria:**
1. [Situation is properly recognized]
2. [System enables the desired motivation]
3. [Progress or feedback is visible]
4. [Outcome is achieved efficiently]
5. [Edge cases are handled gracefully]
6. [Integration and notifications work]
## Example Job Story
**Title:** Track Weekly Snack Spending
**Description:** When I'm preparing my weekly allowance for snacks (situation), I want to quickly see how much I've spent so far (motivation), so I can make sure I don't run out of money before the weekend (outcome).
**Design:** [Figma link]
**Acceptance Criteria:**
1. Display Spending Summary with 'Weekly Spending Overview' section
2. Real-Time Update when expense logged
3. Progress Indicator (progress bar showing 0-100% of weekly budget)
4. Remaining Budget Highlight in prominent color
5. Detailed Spending Log with breakdown by category
6. Notifications at 80% budget threshold
7. Weekend-Specific Reminder at 90% by Thursday evening
8. Easy Access and Navigation to detailed breakdown
## Output Deliverables
- Complete set of job stories for the feature
- Each story follows the 'When...I want...so I can' format
- 6-8 acceptance criteria focused on outcomes
- Stories emphasize user situations and motivations
- Clear links to design and prototypes
---
### Further Reading
- [Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar](https://www.productcompass.pm/p/jobs-to-be-done-masterclass-with) (video course)
================================================
FILE: pm-execution/skills/outcome-roadmap/SKILL.md
================================================
---
name: outcome-roadmap
description: "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."
---
# Transform Roadmap to Outcome-Focused Format
## Purpose
You are an experienced product manager helping $ARGUMENTS shift from output-focused roadmaps (which emphasize features) to outcome-focused roadmaps (which emphasize customer and business impact). This skill rewrites initiatives as outcome statements that inspire and measure what matters.
## Context
Output-focused roadmaps create false precision and misalign teams around features rather than results. Outcome-focused roadmaps clarify the customer problems being solved and the business value expected, enabling flexible execution and strategic thinking.
## Instructions
1. **Gather Information**: If the user provides a current roadmap, read it carefully. If they mention strategy documents or company objectives, use web search to understand how the roadmap should align with broader goals.
2. **Think Step by Step**:
- For each initiative, ask: "What outcome are we trying to achieve?"
- What customer problem are we solving?
- What business metric will improve?
- How will this impact the customer experience or business?
- Is there a better, different way to achieve the same outcome?
3. **Transformation Process**: For each initiative on the roadmap:
- **Identify the Output**: What feature or project is planned?
- **Uncover the Outcome**: Why are we building it? What changes for customers or business?
- **Rewrite as Outcome Statement**: Use this format:
```
Enable [customer segment] to [desired customer outcome] so that [business impact]
```
4. **Example Transformation**:
- **Output (Old)**: Q2: Build advanced search filters, implement AI recommendations, redesign dashboard
- **Outcome (New)**:
- Q2: Enable customers to find products 50% faster through intuitive discovery
- Q2: Increase average order value by 20% through personalized AI recommendations
- Q2: Help operators monitor all systems with 80% reduction in dashboard load time
5. **Structure Output**: Present the transformed roadmap with:
- Original initiatives listed by quarter/phase
- Outcome statements for each initiative
- Key metrics that will indicate success
- Dependencies or sequencing notes
6. **Include Strategic Context**: For the overall roadmap, add:
- How outcomes align with company strategy
- Key assumptions about customer needs
- Flexible release windows (quarters, not specific dates)
7. **Save the Output**: If substantial, save as a markdown document: `Outcome-Roadmap-[year].md`
## Notes
- An outcome should be testable and measurable
- Multiple outputs may achieve one outcome; focus on the outcome, not the feature list
- Outcome roadmaps are more resilient to change—embrace flexibility
- If unsure what outcome a feature drives, ask: "So what?" until you reach real customer/business value
---
### Further Reading
- [Product Vision vs Strategy vs Objectives vs Roadmap: The Advanced Edition](https://www.productcompass.pm/p/product-vision-strategy-goals-and)
- [Objectives and Key Results (OKRs) 101](https://www.productcompass.pm/p/okrs-101-advanced-techniques)
- [Business Outcomes vs Product Outcomes vs Customer Outcomes](https://www.productcompass.pm/p/business-outcomes-vs-product-outcomes)
================================================
FILE: pm-execution/skills/pre-mortem/SKILL.md
================================================
---
name: pre-mortem
description: "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."
---
# Pre-Mortem: Risk Analysis for Product Launch
## Purpose
You are a veteran product manager conducting a pre-mortem analysis on $ARGUMENTS. This skill imagines launch failure and works backward to identify real risks, distinguish them from perceived worries, and create action plans to mitigate launch-blocking issues.
## Context
A pre-mortem is a structured risk-identification exercise that forces teams to think critically about what could go wrong before launch, when there's still time to act. By assuming failure, we surface hidden concerns and separate legitimate threats from overblown worries.
## Instructions
1. **Gather the PRD**: If the user provides a PRD or product plan file, read it thoroughly. Understand the product, target market, key assumptions, and timeline. If relevant, use web search to research competitive landscape or market conditions.
2. **Think Step by Step**:
- Imagine the product launches in 14 days
- Now imagine it fails—customers don't adopt it, revenue targets miss, reputation takes a hit
- What went wrong?
- What did we miss or not execute well?
- What were we overconfident about?
3. **Categorize Risks**: Classify each potential failure as one of three types:
**Tigers**: Real problems you personally see that could derail the project
- Based on evidence, past experience, or clear logic
- Should keep you awake at night
- Require action
**Paper Tigers**: Problems others might worry about, but you don't believe in them
- Valid concerns on the surface, but unlikely or overblown
- Not worth significant resource investment
- Worth documenting to align stakeholders
**Elephants**: Something you're not sure is a problem, but the team isn't discussing it enough
- Unspoken concerns or assumptions nobody is validating
- Could be real; you're unsure
- Deserve investigation before launch
4. **Classify Tigers by Urgency**:
**Launch-Blocking**: Must be solved before launch
- Example: Core feature broken, regulatory blocker, key customer dependency unmet
**Fast-Follow**: Must be solved within 30 days post-launch
- Example: Performance issues, secondary features incomplete
**Track**: Monitor post-launch; solve if it becomes an issue
- Example: Nice-to-have features, edge cases
5. **Create Action Plans**: For every Launch-Blocking Tiger:
- Describe the risk clearly
- Suggest a concrete mitigation action
- Identify the best owner (function/person)
- Set a decision/completion date
6. **Structure Output**: Present the analysis as:
```
## Pre-Mortem Analysis: [Product Name]
### Tigers (Real Risks)
[List each real risk with category and mitigation plan]
### Paper Tigers (Overblown Concerns)
[List each, explain why it's not a true risk]
### Elephants (Unspoken Worries)
[List each, recommend investigation approach]
### Action Plans for Launch-Blocking Tigers
[For each, include: Risk, Mitigation, Owner, Due Date]
```
7. **Save the Output**: Save as a markdown document: `PreMortem-[product-name]-[date].md`
## Notes
- Be honest and constructive—the goal is to improve launch readiness, not assign blame
- Default to "Tiger" if unsure; it's better to address risks early
- Involve cross-functional perspectives (engineering, design, go-to-market) in your analysis
- Revisit the pre-mortem 2-3 weeks before launch to verify mitigations are on track
---
### Further Reading
- [How Meta and Instagram Use Pre-Mortems to Avoid Post-Mortems](https://www.productcompass.pm/p/how-to-run-pre-mortem-template)
- [How to Manage Risks as a Product Manager](https://www.productcompass.pm/p/how-to-manage-risks-as-a-product-manager)
================================================
FILE: pm-execution/skills/prioritization-frameworks/SKILL.md
================================================
---
name: prioritization-frameworks
description: "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."
---
## Prioritization Frameworks Reference
A reference guide to help you select and apply the right prioritization framework for your context.
### Core Principle
Never allow customers to design solutions. Prioritize **problems (opportunities)**, not features.
### Opportunity Score (Dan Olsen, *The Lean Product Playbook*)
The recommended framework for prioritizing customer problems.
Survey customers on **Importance** and **Satisfaction** for each need (normalize to 0–1 scale).
Three related formulas:
- **Current value** = Importance × Satisfaction
- **Opportunity Score** = Importance × (1 − Satisfaction)
- **Customer value created** = Importance × (S2 − S1), where S1 = satisfaction before, S2 = satisfaction after
High Importance + low Satisfaction = highest Opportunity Score = best opportunities. Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot. Prioritizes customer problems, not solutions.
### ICE Framework
Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.
- **I** (Impact) = Opportunity Score × Number of Customers affected
- **C** (Confidence) = How confident are we? (1-10). Accounts for risk.
- **E** (Ease) = How easy is it to implement? (1-10). Accounts for economic factors.
**Score** = I × C × E. Higher = prioritize first.
### RICE Framework
Splits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.
- **R** (Reach) = Number of customers affected
- **I** (Impact) = Opportunity Score (value per customer)
- **C** (Confidence) = How confident are we? (0-100%)
- **E** (Effort) = How much effort to implement? (person-months)
**Score** = (R × I × C) / E
### 9 Frameworks Overview
| Framework | Best For | Key Insight |
|-----------|----------|-------------|
| Eisenhower Matrix | Personal tasks | Urgent vs Important — for individual PM task management |
| Impact vs Effort | Tasks/initiatives | Simple 2×2 — quick triage, not rigorous for strategic decisions |
| Risk vs Reward | Initiatives | Like Impact vs Effort but accounts for uncertainty |
| **Opportunity Score** | Customer problems | **Recommended.** Importance × (1 − Satisfaction). Normalize to 0–1. |
| Kano Model | Understanding expectations | Must-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing. |
| Weighted Decision Matrix | Multi-factor decisions | Assign weights to criteria, score each option. Useful for stakeholder buy-in. |
| **ICE** | Ideas/initiatives | Impact × Confidence × Ease. Recommended for quick prioritization. |
| **RICE** | Ideas at scale | (Reach × Impact × Confidence) / Effort. Adds Reach to ICE. |
| MoSCoW | Requirements | Must/Should/Could/Won't. Caution: project management origin. |
### Templates
- [Opportunity Score intro (PDF)](https://drive.google.com/file/d/1ENbYPmk1i1AKO7UnfyTuULL5GucTVufW/view)
- [Importance vs Satisfaction Template — Dan Olsen (Google Slides)](https://docs.google.com/presentation/d/1jg-LuF_3QHsf6f1nE1f98i4C0aulnRNMOO1jftgti8M/edit#slide=id.g796641d975_0_3)
- [ICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1LUfnsPolhZgm7X2oij-7EUe0CJT-Dwr-/edit?usp=share_link&ouid=111307342557889008106&rtpof=true&sd=true)
- [RICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1S-6QpyOz5MCrV7B67LUWdZkAzn38Eahv/edit?usp=sharing&ouid=111307342557889008106&rtpof=true&sd=true)
---
### Further Reading
- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
================================================
FILE: pm-execution/skills/release-notes/SKILL.md
================================================
---
name: release-notes
description: "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."
---
## Release Notes Generator
Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.
### Context
You are writing release notes for **$ARGUMENTS**.
If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience.
### Instructions
1. **Gather raw material**: Read all provided tickets, changelogs, or descriptions. Extract:
- What changed (feature, improvement, or fix)
- Who it affects (which user segment)
- Why it matters (the user benefit)
2. **Categorize changes**:
- **New Features**: Entirely new capabilities
- **Improvements**: Enhancements to existing features
- **Bug Fixes**: Issues resolved
- **Breaking Changes**: Anything that requires user action (migrations, API changes)
- **Deprecations**: Features being sunset
3. **Write each entry** following these principles:
- Lead with the user benefit, not the technical change
- Use plain language — avoid jargon, internal codenames, or ticket numbers
- Keep each entry to 1-3 sentences
- Include visuals or screenshots if the user provides them
**Example transformations**:
- Technical: "Implemented Redis caching layer for dashboard API endpoints"
- User-facing: "Dashboards now load up to 3× faster, so you spend less time waiting and more time analyzing."
- Technical: "Fixed race condition in concurrent checkout flow"
- User-facing: "Fixed an issue where some orders could fail during high-traffic periods."
4. **Structure the release notes**:
```
# [Product Name] — [Version / Date]
## New Features
- **[Feature name]**: [1-2 sentence description of what it does and why it matters]
## Improvements
- **[Area]**: [What got better and how it helps]
## Bug Fixes
- Fixed [issue description in user terms]
## Breaking Changes (if any)
- **Action required**: [What users need to do]
```
5. **Adjust tone** to match the product's voice — professional for B2B, friendly for consumer, developer-focused for APIs.
Save as a markdown document. If the user wants HTML or another format, convert accordingly.
================================================
FILE: pm-execution/skills/retro/SKILL.md
================================================
---
name: retro
description: "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."
---
## Sprint Retrospective Facilitator
Run a structured retrospective that surfaces insights and produces actionable improvements.
### Context
You are facilitating a retrospective for **$ARGUMENTS**.
If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.
### Instructions
1. **Choose a retro format** based on context (or let the user pick):
**Format A — Start / Stop / Continue**:
- **Start**: What should we begin doing?
- **Stop**: What should we stop doing?
- **Continue**: What's working well that we should keep?
**Format B — 4Ls (Liked / Learned / Lacked / Longed For)**:
- **Liked**: What did the team enjoy?
- **Learned**: What new knowledge was gained?
- **Lacked**: What was missing?
- **Longed For**: What do we wish we had?
**Format C — Sailboat**:
- **Wind (propels us)**: What's driving us forward?
- **Anchor (holds us back)**: What's slowing us down?
- **Rocks (risks)**: What dangers lie ahead?
- **Island (goal)**: Where are we trying to get to?
2. **If the user provides raw feedback** (e.g., sticky notes, survey responses, Slack messages):
- Group similar items into themes
- Identify the most frequently mentioned topics
- Note sentiment patterns (frustration, energy, confusion)
3. **Analyze the sprint performance**:
- Sprint goal: achieved or not?
- Velocity vs. commitment (over-committed? under-committed?)
- Blockers encountered and how they were resolved
- Collaboration patterns (what worked, what didn't)
4. **Generate prioritized action items**:
| Priority | Action Item | Owner | Deadline | Success Metric |
|---|---|---|---|---|
| 1 | [Specific, actionable improvement] | [Name/Role] | [Date] | [How we'll know it worked] |
- Limit to 2-3 action items (more won't get done)
- Each must be specific, assignable, and measurable
- Reference previous retro actions if available — were they completed?
5. **Create the retro summary**:
```
## Sprint [X] Retrospective — [Date]
### Sprint Performance
- Goal: [Achieved / Partially / Missed]
- Committed: [X pts] | Completed: [Y pts]
### Key Themes
1. [Theme] — [summary]
### Action Items
1. [Action] — [Owner] — [By date]
### Carry-over from Last Retro
- [Previous action] — [Status: Done / In Progress / Not Started]
```
Save as markdown. Keep the tone constructive — the goal is improvement, not blame.
================================================
FILE: pm-execution/skills/sprint-plan/SKILL.md
================================================
---
name: sprint-plan
description: "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."
---
## Sprint Planning
Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
### Context
You are helping plan a sprint for **$ARGUMENTS**.
If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.
### Instructions
1. **Estimate team capacity**:
- Number of team members and their availability (PTO, meetings, on-call)
- Historical velocity (average story points per sprint from last 3 sprints)
- Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
- Calculate available capacity in story points or ideal hours
2. **Review and select stories**:
- Pull from the prioritized backlog (highest priority first)
- Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
- Flag stories that need refinement before committing
- Stop adding stories when capacity is reached
3. **Map dependencies**:
- Identify stories that depend on other stories or external teams
- Sequence dependent stories appropriately
- Flag external dependencies and owners
- Identify the critical path
4. **Identify risks and mitigations**:
- Stories with high uncertainty or complexity
- External dependencies that could slip
- Knowledge concentration (only one person can do it)
- Suggest mitigations for each risk
5. **Create the sprint plan summary**:
```
Sprint Goal: [One sentence describing what success looks like]
Duration: [2 weeks / 1 week / etc.]
Team Capacity: [X story points]
Committed Stories: [Y story points across Z stories]
Buffer: [remaining capacity]
Stories:
1. [Story title] — [points] — [owner] — [dependencies]
...
Risks:
- [Risk] → [Mitigation]
```
6. **Define the sprint goal**: A single, clear sentence that captures the sprint's primary value delivery.
Think step by step. Save as markdown.
---
### Further Reading
- [Product Owner vs Product Manager: What's the difference?](https://www.productcompass.pm/p/product-manager-vs-product-owner)
================================================
FILE: pm-execution/skills/stakeholder-map/SKILL.md
================================================
---
name: stakeholder-map
description: "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."
---
## Stakeholder Mapping & Communication Plan
Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
### Context
You are helping build a stakeholder map for **$ARGUMENTS**.
If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.
### Instructions
1. **Identify stakeholders**: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
2. **Classify each stakeholder** on two dimensions:
- **Power** (High/Low): Their ability to influence decisions, resources, or outcomes
- **Interest** (High/Low): How much the project directly affects them or how engaged they are
3. **Place stakeholders in the Power × Interest grid**:
| | High Interest | Low Interest |
|---|---|---|
| **High Power** | **Manage Closely** — Regular 1:1s, involve in decisions, seek their input early | **Keep Satisfied** — Periodic updates, escalate only critical issues |
| **Low Power** | **Keep Informed** — Regular status updates, invite to demos, gather feedback | **Monitor** — Light-touch updates, available on request |
4. **For each quadrant**, recommend:
- Communication frequency (daily, weekly, bi-weekly, monthly)
- Communication format (1:1, email, Slack, meeting, dashboard)
- Key messages and framing
- Potential risks if this stakeholder is neglected
5. **Create a communication plan table**:
| Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message |
|---|---|---|---|---|---|---|---|
6. **Flag potential conflicts**: Identify stakeholders with competing interests and suggest alignment strategies.
Think step by step. Save the stakeholder map as a markdown document.
---
### Further Reading
- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
- [Team Topologies: A Handbook to Set and Scale Product Teams](https://www.productcompass.pm/p/team-topologies-a-handbook-to-set)
================================================
FILE: pm-execution/skills/summarize-meeting/SKILL.md
================================================
---
name: summarize-meeting
description: "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."
---
# Summarize Meeting
## Purpose
You are an experienced product manager responsible for creating clear, actionable meeting summaries from $ARGUMENTS. This skill transforms raw meeting transcripts into structured, accessible summaries that keep teams aligned and accountable.
## Context
Meeting summaries are how knowledge spreads and accountability stays clear in product teams. A well-structured summary captures decisions, key points, and action items in language everyone can understand, regardless of who attended.
## Instructions
1. **Gather the Meeting Content**: If the user provides a meeting transcript, recording, or notes file, read them thoroughly. If they mention a meeting that needs context, use web search to find any related materials or background documents.
2. **Think Step by Step**:
- Who attended and what were their roles?
- What was the main topic or agenda?
- What decisions were made?
- What are the next steps and who owns them?
- Are there open questions or blockers?
3. **Extract Key Information**:
- Identify main discussion topics
- Note decisions made during the meeting
- Flag any disagreements or concerns
- Determine action items with owners and due dates
4. **Create Structured Summary**: Use this template:
```
## Meeting Summary
**Date & Time**: [Date and start/end time]
**Participants**: [Full names and roles, if available]
**Topic**: [Short title—what was the meeting about?]
**Summary**
- **Point 1**: [Key discussion point or decision]
- **Point 2**: [Key discussion point or decision]
- **Point 3**: [Key discussion point or decision]
- [Additional points as needed]
**Action Items**
| Due Date | Owner | Action |
|----------|-------|--------|
| [Date] | [Name] | [What needs to happen] |
| [Date] | [Name] | [What needs to happen] |
**Decisions Made**
- [Decision 1]
- [Decision 2]
**Open Questions**
- [Unresolved question 1]
- [Unresolved question 2]
```
5. **Use Accessible Language**: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.
6. **Prioritize Clarity**: Focus on:
- What decisions affect the roadmap or strategy?
- What does each person need to do?
- By when do they need to do it?
7. **Save the Output**: Save as a markdown document: `Meeting-Summary-[date]-[topic].md`
## Notes
- Be objective—summarize what was discussed, not personal opinions
- Highlight action items clearly so nothing falls through the cracks
- If the meeting was large or complex, consider breaking points into sections by topic
- Use "we" language to keep the team feel inclusive and collaborative
================================================
FILE: pm-execution/skills/test-scenarios/SKILL.md
================================================
---
name: test-scenarios
description: "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."
---
# Test Scenarios
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.
**Use when:** Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations.
**Arguments:**
- `$PRODUCT`: The product or system name
- `$USER_STORY`: The user story to test (title and acceptance criteria)
- `$CONTEXT`: Additional testing context or constraints
## Step-by-Step Process
1. **Review the user story** and acceptance criteria
2. **Define test objectives** - What specific behavior to validate
3. **Establish starting conditions** - System state, data setup, configurations
4. **Identify user roles** - Who performs the test actions
5. **Create test steps** - Break down interactions step-by-step
6. **Define expected outcomes** - Observable results after each step
7. **Consider edge cases** - Invalid inputs, boundary conditions
8. **Output detailed test scenarios** - Ready for QA execution
## Scenario Template
**Test Scenario:** [Clear scenario name]
**Test Objective:** [What this test validates]
**Starting Conditions:**
- [System state required]
- [Data or configuration needed]
- [User setup or permissions]
**User Role:** [Who performs the test]
**Test Steps:**
1. [First action and its expected result]
2. [Second action and observable outcome]
3. [Third action and system behavior]
4. [Completion action and final state]
**Expected Outcomes:**
- [Observable result 1]
- [Observable result 2]
- [Observable result 3]
## Example Test Scenario
**Test Scenario:** View Recently Viewed Products on Product Page
**Test Objective:** Verify that the 'Recently viewed' section displays correctly and excludes the current product.
**Starting Conditions:**
- User is logged in or has browser history enabled
- User has viewed at least 2 products in the current session
- User is now on a product page different from previously viewed items
**User Role:** Online Shopper
**Test Steps:**
1. Navigate to any product page → Section should appear at bottom with previously viewed items
2. Scroll to bottom of page → "Recently viewed" section is visible with product cards
3. Verify product thumbnails → Images, titles, and prices are displayed correctly
4. Check current product → Current product is NOT in the recently viewed list
5. Click on a product card → User navigates to the corresponding product page
**Expected Outcomes:**
- Recently viewed section appears only after viewing at least 1 prior product
- Section displays 4-8 product cards with complete information
- Current product is excluded from the list
- Each card shows "Viewed X minutes/hours ago" timestamp
- Clicking cards navigates to correct product pages
- Performance: Section loads within 2 seconds
## Output Deliverables
- Comprehensive test scenarios for each acceptance criterion
- Clear test objectives aligned with user story intent
- Detailed step-by-step test actions
- Observable expected outcomes after each step
- Edge case and error scenario coverage
- Ready for QA team execution and documentation
================================================
FILE: pm-execution/skills/user-stories/SKILL.md
================================================
---
name: user-stories
description: "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."
---
# User Stories
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.
**Use when:** Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.
**Arguments:**
- `$PRODUCT`: The product or system name
- `$FEATURE`: The new feature to break into stories
- `$DESIGN`: Link to design files (Figma, Miro, etc.)
- `$ASSUMPTIONS`: Key assumptions or context
## Step-by-Step Process
1. **Analyze the feature** based on provided design and context
2. **Identify user roles** and distinct user journeys
3. **Apply 3 C's framework:**
- Card: Simple title and one-liner
- Conversation: Detailed discussion of intent
- Confirmation: Clear acceptance criteria
4. **Respect INVEST criteria:** Independent, Negotiable, Valuable, Estimable, Small, Testable
5. **Use plain language** a primary school graduate can understand
6. **Link to design files** for visual reference
7. **Output user stories** in structured format
## Story Template
**Title:** [Feature name]
**Description:** As a [user role], I want to [action], so that [benefit].
**Design:** [Link to design files]
**Acceptance Criteria:**
1. [Clear, testable criterion]
2. [Observable behavior]
3. [System validates correctly]
4. [Edge case handling]
5. [Performance or accessibility consideration]
6. [Integration point]
## Example User Story
**Title:** Recently Viewed Section
**Description:** As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.
**Design:** [Figma link]
**Acceptance Criteria:**
1. The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
2. It is not displayed for users visiting the first product page of their session.
3. The current product itself is excluded from the displayed items.
4. The section showcases product cards or thumbnails with images, titles, and prices.
5. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
6. Clicking on a product card leads the user to the corresponding product page.
## Output Deliverables
- Complete set of user stories for the feature
- Each story includes title, description, design link, and 4-6 acceptance criteria
- Stories are independent and can be developed in any order
- Stories are sized for one sprint cycle
- Stories reference related design documentation
---
### Further Reading
- [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)
================================================
FILE: pm-execution/skills/wwas/SKILL.md
================================================
---
name: wwas
description: "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."
---
# Why-What-Acceptance (WWA)
Create product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context.
**Use when:** Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams.
**Arguments:**
- `$PRODUCT`: The product or system name
- `$FEATURE`: The new feature or capability
- `$DESIGN`: Link to design files (Figma, Miro, etc.)
- `$ASSUMPTIONS`: Key assumptions and strategic context
## Step-by-Step Process
1. **Define the strategic Why** - Connect work to business and team objectives
2. **Describe the What** - Keep descriptions concise, reference designs
3. **Write Acceptance Criteria** - High-level, not detailed specifications
4. **Ensure independence** - Items can be developed in any order
5. **Keep items negotiable** - Invite team conversation, not constraints
6. **Make items valuable** - Each delivers measurable user or business value
7. **Ensure testability** - Outcomes are observable and verifiable
8. **Size appropriately** - Small enough for one sprint estimate
## Item Template
**Title:** [What will be delivered]
**Why:** [1-2 sentences connecting to strategic context and team objectives]
**What:** [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]
**Acceptance Criteria:**
- [Observable outcome 1]
- [Observable outcome 2]
- [Observable outcome 3]
- [Observable outcome 4]
## Example WWA Item
**Title:** Implement Real-Time Spending Tracker
**Why:** Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.
**What:** Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.
**Acceptance Criteria:**
- Spending totals update within 2 seconds of logging an expense
- Budget progress is visually indicated with a progress bar
- Users can see remaining budget amount at a glance
- System handles multiple expense categories correctly
## Output Deliverables
- Complete set of backlog items for the feature
- Each item includes Why, What, and Acceptance Criteria sections
- Items are independent and deliverable in any order
- Items are sized for estimation and completion in one sprint
- Strategic context is clear for team decision-making
- Design references are included for implementation guidance
---
### Further Reading
- [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)
================================================
FILE: pm-go-to-market/.claude-plugin/plugin.json
================================================
{
"name": "pm-go-to-market",
"version": "1.0.1",
"description": "Go-to-market skills for PMs: GTM strategy, growth loops, GTM motions, beachhead segments, and ideal customer profiles.",
"author": {
"name": "Paweł Huryn",
"email": "pawel@productcompass.pm",
"url": "https://www.productcompass.pm"
},
"keywords": [
"product-management",
"go-to-market",
"gtm",
"growth-loops",
"icp",
"launch"
],
"homepage": "https://www.productcompass.pm",
"license": "MIT"
}
================================================
FILE: pm-go-to-market/README.md
================================================
# pm-go-to-market
Go-to-market skills for PMs: GTM strategy, growth loops, GTM motions, beachhead segments, and ideal customer profiles.
## Skills (6)
- **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)
- `/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
Paweł Huryn — [The Product Compass Newsletter](https://www.productcompass.pm)
## License
MIT
================================================
FILE: pm-go-to-market/commands/battlecard.md
================================================
---
description: Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies
argument-hint: "<your product> vs <competitor>"
---
# /battlecard -- Competitive Battlecard
Create a concise, sales-ready battlecard that helps your team win deals against a specific competitor. Includes positioning, feature comparison, objection handling, and conversation strategies.
## Invocation
```
/battlecard Our CRM vs Salesforce
/battlecard ProjectFlow vs Monday.com for mid-market teams
/battlecard [upload competitor materials or win/loss data]
```
## Workflow
### Step 1: Identify the Matchup
Ask:
- Your product and the specific competitor
- Who is the typical buyer choosing between you?
- Do you have win/loss data or sales feedback?
- What deal stage does this typically come up? (early evaluation, final decision, displacement)
### Step 2: Research the Competitor
Apply the **competitive-battlecard** skill with web research:
- Current product capabilities and recent launches
- Pricing model and published pricing
- Target market and positioning
- Known weaknesses (from reviews, forums, customer feedback)
- Recent company news (funding, leadership, strategy shifts)
### Step 3: Generate Battlecard
```
## Competitive Battlecard: [Your Product] vs [Competitor]
**Last updated**: [today]
**Use when**: [situation where this competitor comes up]
### Quick Summary
**We win when**: [buyer profile and situation where you have advantage]
**We lose when**: [buyer profile and situation where competitor has advantage]
**Key differentiator**: [one sentence]
### Positioning
**How they position**: [their messaging]
**How we position against them**: [our counter-positioning]
### Feature Comparison
| Capability | Us | Them | Verdict |
|-----------|-----|------|---------|
| [capability] | [status] | [status] | [advantage] |
### Pricing Comparison
| Dimension | Us | Them | Notes |
|----------|-----|------|-------|
### Objection Handling
| Objection | Response | Proof Point |
|----------|---------|------------|
| "They have [feature]" | [response] | [evidence] |
| "They're cheaper" | [response] | [TCO analysis] |
| "They're more established" | [response] | [counter] |
### Landmines to Plant
[Questions to ask the prospect that expose competitor weaknesses]
1. "Ask them about [topic] — their answer will reveal [weakness]"
### Trap Questions to Expect
[Questions the competitor will encourage the prospect to ask you]
1. "[Question]" — How to respond: [response]
### Win/Loss Patterns
**We typically win because**: [top 3 reasons]
**We typically lose because**: [top 3 reasons]
### Conversation Starters
**If they're already using [Competitor]**:
- [approach for displacement deals]
**If they're evaluating both**:
- [approach for competitive evaluations]
### Resources
- [Customer story / case study that counters this competitor]
- [Third-party comparison or review]
- [Demo script optimized for this competitive situation]
```
Save as markdown.
### Step 4: Offer Next Steps
- "Want me to **create battlecards for other competitors**?"
- "Should I **run a full competitive analysis** of the market?"
- "Want me to **draft customer-facing comparison content** based on this?"
- "Should I **update the positioning** based on competitive insights?"
## Notes
- Battlecards should be updated quarterly — competitors change fast
- "Landmines" are the most valuable section for sales — teach reps what questions to ask
- Never trash the competitor in front of the prospect — position on your strengths, not their weaknesses
- Win/loss data from real deals is worth 10x any analysis — encourage the user to add it
- Keep it to one page equivalent — sales reps won't read a 10-page document during a call
================================================
FILE: pm-go-to-market/commands/growth-strategy.md
================================================
---
description: Design sustainable growth mechanisms — growth loops and GTM motions for product-led and sales-led strategies
argument-hint: "<product or growth challenge>"
---
# /growth-strategy -- Growth Loops & GTM Motions
Identify and design the growth mechanisms that will drive sustainable traction. Evaluates five growth loop types and seven GTM motions to build a balanced acquisition and expansion strategy.
## Invocation
```
/growth-strategy B2B collaboration tool — growth has stalled at 5K users
/growth-strategy Consumer fitness app looking for viral growth
/growth-strategy [upload product metrics or growth data]
```
## Workflow
### Step 1: Understand Growth Context
Ask:
- What is the product? Who uses it?
- Current growth metrics: user count, growth rate, acquisition channels
- What's working? What's not?
- Business model: how does revenue relate to user growth?
- Team and budget: what resources can you put toward growth?
### Step 2: Evaluate Growth Loops
Apply the **growth-loops** skill:
Analyze five growth loop types for your product:
1. **Viral Loop**: Users invite others as part of natural product use
2. **Usage Loop**: More usage creates more value, bringing users back
3. **Collaboration Loop**: Product becomes more valuable when used with others
4. **User-Generated Content Loop**: Users create content that attracts new users
5. **Referral Loop**: Satisfied users actively recommend to others
For each applicable loop: mechanism, requirements, expected impact, implementation effort.
### Step 3: Evaluate GTM Motions
Apply the **gtm-motions** skill:
Assess seven GTM approaches:
1. **Inbound**: Content, SEO, thought leadership
2. **Outbound**: Sales, cold outreach, account-based
3. **Paid Digital**: SEM, social ads, display, retargeting
4. **Community**: Forums, events, user groups, developer relations
5. **Partners**: Integrations, resellers, co-marketing
6. **ABM (Account-Based Marketing)**: Targeted enterprise acquisition
7. **PLG (Product-Led Growth)**: Free tier, self-serve, product virality
For each: fit for your product, expected CAC, timeline to results, tools needed.
### Step 4: Design Growth Strategy
```
## Growth Strategy: [Product]
**Date**: [today]
**Current state**: [user count, growth rate, key channels]
**Growth goal**: [target]
### Recommended Growth Loops
| Loop Type | Mechanism | Fit | Impact | Effort | Priority |
|----------|-----------|-----|--------|--------|----------|
### Primary Growth Loop: [Type]
**How it works**: [step-by-step mechanism]
**Requirements**: [what needs to be true/built]
**Key metrics**: [how to measure loop health]
**Implementation plan**: [concrete next steps]
### Secondary Growth Loop: [Type]
[same format]
### GTM Motion Mix
| Motion | Investment | Expected ROI | Timeline | Tools |
|--------|-----------|-------------|----------|-------|
### Growth Experiments
| # | Experiment | Tests What | Effort | Expected Learning |
|---|-----------|-----------|--------|------------------|
### Growth Metrics Framework
- **North Star**: [growth metric]
- **Loop health**: [metrics per loop]
- **CAC by channel**: [tracking approach]
- **Payback period**: [target]
### 90-Day Growth Plan
**Month 1**: [focus areas and experiments]
**Month 2**: [scale what works, cut what doesn't]
**Month 3**: [optimize and systematize]
```
Save as markdown.
### Step 5: Offer Next Steps
- "Want me to **plan a specific launch campaign**?"
- "Should I **create marketing content** for the inbound motion?"
- "Want me to **set up metrics** to track growth loop health?"
- "Should I **design a referral program** based on the referral loop?"
## Notes
- Growth loops compound; growth tactics don't — prioritize loops over one-off campaigns
- The best growth loop uses the product itself as the channel (PLG, viral, collaboration)
- Not every loop works for every product — a B2B analytics tool won't go viral on TikTok
- Budget should follow learning: invest small in experiments, then scale what proves out
- CAC should be < 1/3 of LTV for sustainable growth — flag if projected CAC is too high
================================================
FILE: pm-go-to-market/commands/plan-launch.md
================================================
---
description: Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan
argument-hint: "<product or feature to launch>"
---
# /plan-launch -- Go-to-Market Strategy
Build a complete GTM plan from first principles: identify your beachhead market, define the ideal customer, craft messaging, choose channels, and create a launch timeline.
## Invocation
```
/plan-launch AI-powered proposal writer for consulting firms
/plan-launch New enterprise tier for our project management tool
/plan-launch [upload a PRD, strategy doc, or pitch deck]
```
## Workflow
### Step 1: Understand the Launch
Ask:
- What are you launching? (new product, new feature, new tier, market expansion)
- What stage? (pre-launch planning, imminent launch, post-launch optimization)
- Do you have existing customers? Or starting from zero?
- What's the timeline? Any hard deadlines?
- Budget constraints? Team size?
### Step 2: Define Beachhead Segment
Apply the **beachhead-segment** skill:
- Evaluate potential market segments against:
- Burning pain (how urgently they need this)
- Willingness to pay (budget and purchase authority)
- Winnable market share (can you reach and win them)
- Referral potential (will they tell others)
- Recommend the single best starting segment with rationale
- Map adjacent segments for expansion after beachhead is secured
### Step 3: Define Ideal Customer Profile
Apply the **ideal-customer-profile** skill:
- Demographics: company size, industry, geography, tech stack
- Behaviors: how they discover solutions, buying process, decision makers
- JTBD: specific jobs they're hiring your product for
- Current alternatives: what they use today and why it falls short
- Qualification criteria: how to identify them quickly
### Step 4: Build GTM Strategy
Apply the **gtm-strategy** skill:
- **Positioning**: How you describe yourself to this segment
- **Messaging**: Key messages for different stakeholders (buyer, user, influencer)
- **Channels**: Where and how to reach your ICP (ranked by expected ROI)
- **Launch tactics**: Specific actions for pre-launch, launch day, and post-launch
- **Pricing alignment**: How pricing supports the GTM motion
- **Success metrics**: How you'll know the launch worked
### Step 5: Generate GTM Plan
```
## Go-to-Market Plan: [Product/Feature]
**Launch date**: [target]
**Type**: [new product / feature / tier / market expansion]
### Beachhead Segment
**Who**: [specific segment definition]
**Why them first**: [rationale against criteria]
**Size**: [TAM/SAM/SOM estimate]
### Ideal Customer Profile
| Attribute | Definition |
|-----------|-----------|
| Company size | [range] |
| Industry | [specific] |
| Decision maker | [title/role] |
| Key JTBD | [job they need done] |
| Current solution | [what they use today] |
| Qualification signal | [how to identify them] |
### Positioning & Messaging
**Positioning statement**: For [who] who [need], [product] is [category] that [benefit]. Unlike [alternative], we [differentiator].
**Key messages by stakeholder**:
| Audience | Message | Proof Point |
|----------|---------|------------|
### Channel Strategy
| Channel | Tactic | Reach | Cost | Priority |
|---------|--------|-------|------|----------|
### Launch Timeline
| Phase | Timing | Actions | Owner |
|-------|--------|---------|-------|
| Pre-launch | [dates] | [list] | [who] |
| Launch week | [dates] | [list] | [who] |
| Post-launch | [dates] | [list] | [who] |
### Success Metrics
| Metric | 30-day target | 90-day target |
|--------|-------------|-------------|
### Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|-----------|
### Expansion Plan
[After beachhead: which adjacent segments, in what order, with what adaptations]
```
Save as markdown.
### Step 6: Offer Next Steps
- "Want me to **design growth loops** for post-launch traction?"
- "Should I **create competitive battlecards** for sales?"
- "Want me to **draft marketing copy** for the launch?"
- "Should I **build a metrics dashboard** for launch tracking?"
## Notes
- "Everyone" is not a segment — the tighter the beachhead, the faster you learn
- The ICP should be specific enough that sales/marketing can identify prospects in 30 seconds
- Messaging should use the customer's language, not your internal terminology
- Pre-launch activities (waitlist, beta, early access) are as important as launch day
- Plan for post-launch: the first 90 days after launch determine long-term trajectory
================================================
FILE: pm-go-to-market/skills/beachhead-segment/SKILL.md
================================================
---
name: beachhead-segment
description: "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."
---
# Beachhead Segment
## Overview
Identify the first beachhead market segment for product launch. This skill evaluates potential market segments against key criteria to find your initial winning segment that enables fast PMF validation and adjacent expansion.
## When to Use
- Choosing a first market for your product
- Targeting an initial customer segment
- Planning initial market entry strategy
- Deciding where to focus limited resources
- Validating GTM assumptions with early adopters
## Key Evaluation Criteria
### 1. Burning Pain Point
Does this segment experience an acute, unmet problem?
- Daily frustration with the status quo
- Significant productivity loss or cost impact
- Emotional urgency to find a solution
- Current workarounds are expensive or fragile
- Problem is getting worse over time
### 2. Willingness to Pay
Does this segment have budget and motivation to pay for a solution?
- Documented budget allocation for this problem area
- ROI is clear and compelling (value > cost)
- Economic impact of problem justifies solution cost
- Decision-maker has autonomy or influence over budget
- No free or DIY alternatives that fully satisfy need
### 3. Winnable Market Share
Can you realistically capture 60-70% of this segment in 3-18 months?
- Segment is large enough but not oversaturated
- Limited competition or easy differentiation
- Market players are fragmented or complacent
- Your product has clear competitive advantage
- You have unique access or distribution advantage
### 4. Referral Potential
Will customers naturally refer or recommend to others?
- Segment contains professional communities
- Customers interact with adjacent segments (expansion opportunity)
- High word-of-mouth culture in this industry
- Network effects within the segment
- Solving problem for one creates demand in adjacent segments
## How It Works
### Step 1: List Potential Segments
Brainstorm all possible target segments:
- Industry verticals (SaaS, healthcare, manufacturing, etc.)
- Company size (SMB, mid-market, enterprise)
- Job titles or roles
- Geographic regions
- Use cases or use-case variations
- Customer maturity level
### Step 2: Research Pain Points
Validate burning pain in each segment:
- Customer interviews and discovery calls
- Problem validation through surveys
- Market research and analyst reports
- Competitor positioning and customer reviews
- Quantify cost/impact of the problem
- Identify current workarounds and limitations
### Step 3: Assess Willingness to Pay
Determine budget and economic viability:
- Segment's budget for this problem category
- ROI calculation (value gained vs cost)
- Current spending on solutions or workarounds
- Budget decision-making process
- Typical deal size expectations
- Pricing sensitivity in the segment
### Step 4: Evaluate Winnability
Assess realistic market share potential:
- Total addressable market (TAM) size
- Competitive landscape and positioning
- Your differentiation or unfair advantage
- Distribution access to this segment
- Time and resources required
- Market growth and momentum
### Step 5: Identify Referral Pathways
Map expansion opportunities:
- Adjacent segments that reference segment influences
- Network effects within the segment
- Professional communities and associations
- Customer-to-customer recommendations
- Natural expansion path to adjacent markets
- Viral or network effects from solving core pain
### Step 6: Select Beachhead
Choose your primary launch segment:
- Highest combined score across four criteria
- Most achievable for your current resources
- Shortest path to PMF and revenue
- Best reference for adjacent expansion
- Most enthusiastic early customer cohort
## Input Format
Use $ARGUMENTS to pass:
- Product description and capabilities
- Initial market research and validation data
- Potential segment options
- Constraints and limitations
- Timeline and resource constraints
- Current customer data or feedback
## Output
A beachhead segment analysis including:
- Top 3-5 recommended segments with scoring
- Primary beachhead segment recommendation
- Pain point validation and evidence
- Willingness to pay assessment and pricing guidance
- Realistic market share and revenue projections
- Referral and expansion pathways to adjacent segments
- 90-day customer acquisition plan for beachhead
- Post-beachhead expansion roadmap
## Framework
Based on Geoffrey Moore's beachhead market strategy in "Crossing the Chasm." Focuses on finding the smallest winnable, referenceable market that validates PMF and enables expansion.
## Tips
- Start absurdly specific. A niche beachhead is better than a vague mass market
- Choose the segment most likely to evangelize your solution
- Validate all four criteria with at least 10 customer interviews
- Select segment with fastest path to revenue and references
- Ensure beachhead can reference to adjacent market segments
- Focus all resources on dominating the beachhead (not diluting efforts)
- Plan exit from beachhead only after 60%+ market share
---
### Further Reading
- [5 GTM Principles You Should Know as a PM](https://www.productcompass.pm/p/5-gtm-principles-with-frameworks-templates)
- [Product-Led Growth 101, Part 1/2](https://www.productcompass.pm/p/product-led-growth-101-12)
- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
- [How to Achieve Product-Market Fit? Part I: Market and Value Proposition](https://www.productcompass.pm/p/how-to-achieve-the-product-market)
================================================
FILE: pm-go-to-market/skills/competitive-battlecard/SKILL.md
================================================
---
name: competitive-battlecard
description: "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?'"
---
## Competitive Battlecard
Create a concise, sales-ready battlecard for use against a specific competitor.
### Context
You are creating a competitive battlecard for **$ARGUMENTS**.
Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.
### Instructions
1. **Research the competitor** (use web search):
- Current product offerings and features
- Pricing tiers and model
- Target market and positioning
- Recent product launches or changes
- Known strengths and weaknesses
- Customer reviews and sentiment (G2, Capterra, Reddit)
2. **Create the battlecard** with these sections:
### Company Overview
- Founded, HQ, funding/revenue (if public)
- Target market and ICP
- Positioning in one sentence
### Quick Comparison
| Capability | Us | Them | Winner |
|---|---|---|---|
| [Feature area 1] | [Our approach] | [Their approach] | [Us/Them/Tie] |
| [Feature area 2] | ... | ... | ... |
| Pricing | ... | ... | ... |
| Support | ... | ... | ... |
### Where We Win
- [Advantage 1]: [Proof point or customer quote]
- [Advantage 2]: [Specific capability they lack]
- [Advantage 3]: [Better approach with reasoning]
### Where They Win
- [Their strength 1]: [Our counter-positioning]
- [Their strength 2]: [How we mitigate this gap]
### Common Objections & Responses
| Prospect Says | Respond With |
|---|---|
| "Competitor X has [feature]" | "[Our alternative approach and why it's better for them]" |
| "They're cheaper" | "[Value framing: total cost of ownership, ROI, hidden costs]" |
| "They're more established" | "[Our advantages: speed, innovation, focus, support]" |
### Landmines to Plant
Questions to ask the prospect that highlight competitor weaknesses:
- "How important is [area where we excel] to your team?"
- "Have you evaluated [specific capability they lack]?"
### Win/Loss Patterns
- We tend to win when: [pattern]
- We tend to lose when: [pattern]
- Key differentiator in competitive deals: [what tips the scale]
3. **Keep it scannable**: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.
Save as markdown. Format for easy printing or sharing in Notion/Confluence.
---
### Further Reading
- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
================================================
FILE: pm-go-to-market/skills/growth-loops/SKILL.md
================================================
---
name: growth-loops
description: "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."
---
# Growth Loops
## Overview
Identify and design growth loops (flywheels) that create sustainable traction. This skill evaluates five proven growth loop mechanisms to reduce reliance on paid acquisition and build product-led growth.
## When to Use
- Designing growth mechanisms for a product
- Building sustainable viral or referral traction
- Reducing reliance on paid acquisition
- Analyzing competitor growth strategies
- Optimizing product for product-led growth
## The 5 Growth Loop Types
### 1. Viral Loop
Product content created by users gets shared on external platforms, bringing new users back to the product.
- **Mechanism**: Users create content in-product → Share on social/external platforms → New users discover and signup
- **Example**: Figma designs shared as links, Loom videos shared in emails
- **Strength**: Exponential user acquisition if content is inherently shareable
- **Challenge**: Requires highly shareable output and strong incentive to share
### 2. Usage Loop
Users create content or value within the product, then share it, which invites new users or drives re-engagement.
- **Mechanism**: User creates → Shares creation → Others consume → Become engaged users
- **Example**: Twitter threads, Medium articles, Notion templates shared publicly
- **Strength**: Growth tied directly to product usage and network effects
- **Challenge**: Requires content creation friction to be very low
### 3. Collaboration Loop
Users invite colleagues to co-create or collaborate within the product, expanding the user base within organizations.
- **Mechanism**: User creates → Invites colleagues for collaboration → Colleagues discover product value
- **Example**: Google Docs invitations, Figma team projects, Slack channels
- **Strength**: Deep organizational penetration and high retention
- **Challenge**: Works best for collaborative/team-based products
### 4. User-Generated Loop
Users discover new content or features through other users' creations, then create and share their own content.
- **Mechanism**: User discovers content → Creates similar content → Shares creation → Others discover
- **Example**: TikTok, Pinterest, YouTube trends driving creator participation
- **Strength**: Creates content flywheel and network effects
- **Challenge**: Requires critical mass of quality content to sustain
### 5. Referral Loop
Users invite other potential users in exchange for rewards, incentives, or social recognition.
- **Mechanism**: User refers → Referred user joins → Referrer gets reward → Shares more referrals
- **Example**: Dropbox referral bonus, Uber rider referrals, PayPal signup bonuses
- **Strength**: Directly incentivizes acquisition; easy to measure ROI
- **Challenge**: Requires valuable incentive without eroding unit economics
## How It Works
### Step 1: Define Product Value
Clarify the core value users experience:
- Primary action users take in your product
- Value created per user action
- Network effects present (if any)
- Friction points in the experience
### Step 2: Evaluate Loop Fit
Assess which growth loops align with your product:
- Product type (collaborative, content-based, utility, etc.)
- Target user behavior and sharing habits
- Network effects already present
- Existing user base and engagement
### Step 3: Design Loop Mechanics
Create specific loop implementation:
- Trigger that initiates sharing or invitations
- Incentive for participation (intrinsic or extrinsic)
- Ease of sharing mechanism
- Conversion rate from invite to activation
- Frequency of loop repetition per user
### Step 4: Calculate Loop Coefficient
Estimate growth velocity:
- Invites/shares per user per cycle
- Conversion rate of invites to new users
- Net new users per cycle
- Time per cycle iteration
### Step 5: Build the Loop
Implement the highest-leverage loop first:
- Start with the most natural loop for your product
- Optimize messaging and friction
- Measure loop metrics and conversion rates
- Compound results over time
## Input Format
Use $ARGUMENTS to pass:
- Product description and primary user action
- Target user demographics and behavior
- Existing sharing/collaboration features
- Current growth channels and metrics
- Constraints or opportunities
## Output
A growth loops analysis including:
- Ranked evaluation of all 5 loop types for your product
- Recommended primary growth loop with implementation plan
- Secondary loops to layer over time
- Key metrics and measurement framework
- 30-60-90 day implementation roadmap
- Potential loop coefficient and growth projections
## Framework
Based on growth loops research by Ognjen Bošković. Focuses on compounding user acquisition through built-in, product-native sharing and collaboration mechanisms.
## Tips
- Start with one loop and master it before adding complexity
- Viral loops compound fastest but take time to build
- Collaboration loops create strongest retention and LTV
- Measure loop health weekly during optimization phase
- Combine loops for multiplicative effect once operating at scale
---
### Further Reading
- [Product-Led Growth 101, Part 1/2](https://www.productcompass.pm/p/product-led-growth-101-12)
- [OpenAI’s Product Leader Shares 3-Layer Distribution Framework To Win Mind & Market Share in the AI World](https://www.productcompass.pm/p/distribution-framework-ai-products)
- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
================================================
FILE: pm-go-to-market/skills/gtm-motions/SKILL.md
================================================
---
name: gtm-motions
description: "Identify the best GTM motions and tools across 7 motion types: Inbound, Outbound, Paid Digital, Community, Partners, ABM, and PLG. Use when selecting marketing channels, choosing between inbound and outbound strategy, or planning cross-channel campaigns."
---
# GTM Motions
## Overview
Identify and evaluate the best go-to-market motions for your product. This skill analyzes seven proven GTM approaches with specific tools and tactics to help you build a balanced acquisition strategy.
## When to Use
- Selecting marketing channels for your product
- Choosing between inbound vs outbound strategy
- Building your GTM toolkit and tech stack
- Evaluating PLG vs traditional sales motion
- Planning cross-channel marketing campaigns
## The 7 GTM Motions
### 1. Inbound Marketing
Attract customers through valuable content and thought leadership.
- **Tools**: LinkedIn, SEMRush, Grammarly, HubSpot, Airtable
- **Tactics**: Blog content, webinars, whitepapers, SEO, email nurture sequences
- **Best For**: B2B SaaS, technical products, long sales cycles
- **Strength**: Builds brand authority and attracts high-intent prospects
- **Challenge**: Requires consistent content creation; slower to show results
### 2. Outbound Sales
Proactively reach target prospects through direct engagement.
- **Tools**: LinkedIn Sales Navigator, ZoomInfo, Lemlist, Apollo, Hunter
- **Tactics**: Cold email campaigns, LinkedIn outreach, phone prospecting, personalized demos
- **Best For**: Enterprise sales, high-value contracts, niche markets
- **Strength**: Predictable pipeline generation; control over target selection
- **Challenge**: Low response rates; resource-intensive; requires skilled sales team
### 3. Paid Digital Advertising
Reach target audiences through paid channels with precision targeting.
- **Tools**: Google Ads, Meta Ads, LinkedIn Ads, Newswire, Retargeting platforms
- **Tactics**: Search ads, display advertising, social ads, video advertising, retargeting
- **Best For**: Products with clear target demographics, competitive keywords
- **Strength**: Fast results; scalable; measurable ROI; precise targeting
- **Challenge**: Can be expensive; requires continuous optimization; competitive
### 4. Community Marketing
Build engaged communities where customers help each other and spread the word.
- **Tools**: Slack, Reddit, Discord, Circle, Mighty Networks, WhatsApp
- **Tactics**: Community forums, user groups, events, mentorship, ambassador programs
- **Best For**: Developer products, communities of practice, loyal user bases
- **Strength**: Builds loyalty; organic word-of-mouth; valuable feedback; low CAC
- **Challenge**: Requires active moderation; time to build critical mass
### 5. Partner Marketing
Leverage partner networks to co-market and reach new audiences.
- **Tools**: Miro, AWS Startups, Oracle Partners, Stripe, Shopify App Store
- **Tactics**: Partner integrations, co-marketing agreements, channel partnerships, resellers
- **Best For**: Complementary products, platform ecosystems, expanding market reach
- **Strength**: Access to established customer bases; shared costs; credibility
- **Challenge**: Partner alignment; revenue sharing; dependency on partners
### 6. Account-Based Marketing (ABM)
Treat high-value accounts as individual markets with personalized campaigns.
- **Tools**: Pipedrive, Hunter, Clay, 6sense, Terminus, Demandbase
- **Tactics**: Personalized messaging, account-targeted content, coordinated sales/marketing
- **Best For**: Enterprise deals, limited target accounts, high deal values
- **Strength**: Higher conversion rates; larger deal sizes; strong sales-marketing alignment
- **Challenge**: Requires detailed account research; resource intensive; not scalable to SMB
### 7. Product-Led Growth (PLG)
Drive adoption through the product experience itself with minimal sales friction.
- **Tools**: Hotjar, Amplitude, Sentry, PostHog, Intercom, Appcues
- **Tactics**: Free trials, freemium models, in-app onboarding, self-serve demos, product analytics
- **Best For**: Self-service products, SMB market, low ACV, viral potential
- **Strength**: Low CAC; aligns product and growth; strong PMF signals; scalable
- **Challenge**: Requires excellent product experience; lower price points; longer ROI
## How It Works
### Step 1: Understand Your Product
Define product characteristics:
- Price point and ACV (contract value)
- Sales cycle length
- Buyer type and decision-making process
- Product complexity and learning curve
- Target market size and concentration
### Step 2: Evaluate Market Conditions
Assess your market dynamics:
- Competitive intensity of your keywords/channels
- Target audience location and accessibility
- Budget availability for paid channels
- Your team size and capabilities
- Timeline to revenue generation
### Step 3: Score Each Motion
Rate fit for your product (1-10 scale):
- Inbound: Content creation capability, brand building timeline
- Outbound: Prospect list availability, sales team capacity
- Paid: Budget flexibility, target audience clarity, conversion potential
- Community: Existing communities, product network effects
- Partners: Complementary products, channel availability
- ABM: Deal size and account concentration
- PLG: Product trial-ability, pricing flexibility
### Step 4: Design Motion Stack
Select and prioritize 2-4 motions to execute:
- Primary motion (highest potential for your business)
- Secondary motions (complementary acquisition channels)
- Motion sequencing (which to start first)
- Resource allocation across channels
### Step 5: Build Execution Plan
Create 90-day implementation roadmap:
- Quick wins and early validation
- Team and tool requirements
- Success metrics for each motion
- Optimization and scaling strategy
- Budget and resource allocation
## Input Format
Use $ARGUMENTS to pass:
- Product description and positioning
- Target customer profile and market
- Price point and sales cycle
- Team size and capabilities
- Budget and timeline constraints
- Existing channels or data
## Output
A comprehensive GTM motions analysis including:
- Scoring of all 7 motions for your product
- Recommended motion stack (primary and secondary)
- Tool recommendations for each motion
- 90-day execution plan with milestones
- Resource and budget requirements
- Success metrics and measurement framework
- Competitive differentiation through motion choice
## Framework
Based on Product Compass GTM motion analysis. Provides a systematic approach to balancing customer acquisition across multiple channels.
## Tips
- Most successful products use 2-4 complementary motions
- Start with your strongest motion; add complexity gradually
- Paid channels fund growth while organic channels build long-term value
- Revisit motion mix quarterly as company scales
- Combine inbound (brand) with outbound (sales) for B2B strength
- Use PLG to reduce CAC; use paid to accelerate proven channels
---
### Further Reading
- [5 GTM Principles You Should Know as a PM](https://www.productcompass.pm/p/5-gtm-principles-with-frameworks-templates)
- [OpenAI’s Product Leader Shares 3-Layer Distribution Framework To Win Mind & Market Share in the AI World](https://www.productcompass.pm/p/distribution-framework-ai-products)
- [Product Management vs. Product Marketing vs. Product Growth 101](https://www.productcompass.pm/p/product-management-vs-product-marketing)
- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
================================================
FILE: pm-go-to-market/skills/gtm-strategy/SKILL.md
================================================
---
name: gtm-strategy
description: "Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline. Use when planning a product launch, creating a GTM plan from scratch, or defining a launch strategy for a new market."
---
# GTM Strategy
## Overview
Create a comprehensive go-to-market strategy for a product launch. This skill covers marketing channels, messaging development, success metrics definition, and launch planning.
## When to Use
- Planning a product launch
- Creating a GTM plan from scratch
- Defining a launch strategy for a new market
- Developing product-to-market fit strategy
- Preparing a product go-live roadmap
## How It Works
### Step 1: Gather Research Data
The system will help you load and analyze early research about your product and target market. Provide:
- Product description and key features
- Target market segment details
- Market research or validation data
- Competitive landscape information
- Any available customer interviews or survey data
### Step 2: Define Marketing Channels
Evaluate which channels best reach your target audience:
- Digital marketing channels (paid search, social media, display)
- Content and inbound channels (blog, SEO, thought leadership)
- Sales and outbound channels (direct outreach, partnerships)
- Community and grassroots channels
- Product-led and viral channels
### Step 3: Develop Messaging
Create audience-specific messaging that resonates:
- Core value proposition for target segment
- Key differentiators and competitive advantages
- Pain point validation and solution mapping
- Proof points and social proof strategies
- Channel-specific messaging variations
### Step 4: Define Success Metrics
Establish measurable KPIs to track launch success:
- Awareness metrics (impressions, reach, brand recall)
- Engagement metrics (CTR, cost per engagement, time on site)
- Conversion metrics (signups, demos requested, trials started)
- Revenue metrics (MRR, customer acquisition cost, lifetime value)
- Market metrics (market share, segment penetration)
### Step 5: Create Launch Plan
Build a phased launch timeline:
- Pre-launch preparation (messaging, channels, timeline)
- Launch day activities and announcements
- Post-launch momentum (content, partnerships, communities)
- Measurement and optimization cadence
- Success criteria and go/no-go decision points
## Input Format
Use $ARGUMENTS to pass:
- Product name and description
- Target market segment
- Research data or file path
- Launch timeline and constraints
- Budget or resource limitations
## Output
A structured GTM strategy document including:
- Recommended marketing channels with justification
- Channel-specific messaging and positioning
- Launch timeline with key milestones
- KPI targets and measurement framework
- Risk mitigation strategies
- 90-day execution roadmap
## Framework
This skill applies Product Compass GTM strategy methodology, focusing on market selection, channel fit, and message-market fit for sustainable product growth.
## Tips
- Start with your most confident customer segment
- Validate assumptions through customer interviews before full launch
- Focus on a few channels excellently rather than many channels poorly
- Establish baseline metrics before launch to measure impact
- Plan for feedback loops and optimization
---
### Further Reading
- [5 GTM Principles You Should Know as a PM](https://www.productcompass.pm/p/5-gtm-principles-with-frameworks-templates)
- [OpenAI’s Product Leader Shares 3-Layer Distribution Framework To Win Mind & Market Share in the AI World](https://www.productcompass.pm/p/distribution-framework-ai-products)
- [Product-Led Growth 101, Part 1/2](https://www.productcompass.pm/p/product-led-growth-101-12)
- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
- [How to Achieve Product-Market Fit? Part I: Market and Value Proposition](https://www.productcompass.pm/p/how-to-achieve-the-product-market)
================================================
FILE: pm-go-to-market/skills/ideal-customer-profile/SKILL.md
================================================
---
name: ideal-customer-profile
description: "Identify the Ideal Customer Profile (ICP) from research data with demographics, behaviors, JTBD, and needs. Use when defining your ICP, analyzing PMF survey data, or understanding who your best customers are."
---
# Ideal Customer Profile
## Overview
Identify your Ideal Customer Profile (ICP) from research and survey data. This skill synthesizes customer research to define the customer most likely to find value, retain, and expand with your product.
## When to Use
- Defining ICP from product-market fit survey data
- Targeting high-value customer segments
- Analyzing customer success and expansion patterns
- Prioritizing sales and marketing efforts
- Evaluating new customer opportunities for fit
- Refining target market definition
## ICP Framework Components
### Demographics
Who are they from a firmographic and personal perspective?
- Company size (employees, revenue)
- Industry or vertical
- Geographic location
- Job title and department
- Years of experience in role
- Education and background
- Organizational structure and reporting
### Behaviors
How do they work and make decisions?
- How they discover and evaluate solutions
- Buying process and decision-making timeline
- Technical literacy and product adoption speed
- Collaboration style (solo decision vs committee)
- Change management and adoption style
- Tool switching frequency
- Community involvement and peer influence
### Jobs to Be Done (JTBD)
What are they trying to accomplish?
- Primary job/goal they're trying to achieve
- Secondary jobs that support the primary job
- Emotional jobs (how they want to feel)
- Social jobs (status and perception)
- Jobs they avoid or want to eliminate
- Frequency and importance of each job
- Success metrics for completing job
### Needs and Pain Points
What problems does your product solve?
- Specific pain points they experience
- Current workarounds and limitations
- Impact on productivity or outcomes
- Cost or time burden of the problem
- Emotional frustration levels
- Barriers to solving the problem
- Available budget to solve
- Competing priorities
## How It Works
### Step 1: Gather Customer Data
Collect research about actual and potential customers:
- Product-market fit survey responses
- Customer interview transcripts
- Trial or freemium user behavior data
- Customer feedback and support tickets
- Churn analysis and customer lifecycle data
- Win/loss analysis from sales
- Competitor customer analysis
### Step 2: Segment by Value
Identify customer cohorts and their value:
- Highest LTV (lifetime value) customers
- Fastest time-to-value customers
- Lowest churn rate customers
- Highest expansion/upsell customers
- Most enthusiastic/engaged customers
- Best reference/case study potential
- Most aligned with product vision
### Step 3: Profile Demographics
Extract firmographic patterns:
- Common company sizes (employee count, revenue)
- Industry verticals and sub-verticals
- Geographic concentrations
- Typical department and reporting structure
- Budget holders and budget available
- Company stage (startup, growth, enterprise)
- Company culture indicators
### Step 4: Identify Behaviors
Map decision-making and adoption patterns:
- How they discovered your product (channel)
- Evaluation process and timeline
- Key stakeholders in decision
- Obstacles during sales process
- Product adoption speed and breadth
- Team involvement in onboarding
- Frequency of feature usage
- Support and service needs
### Step 5: Define JTBD
Articulate what they're trying to accomplish:
- Primary job/goal (functional job)
- Emotional dimensions (how they want to feel)
- Social dimensions (team and stakeholder impact)
- Success metrics (how they measure success)
- Context and constraints (when, where, with whom)
- Competing jobs and priorities
- Importance ranking of various jobs
### Step 6: Document Pain Points and Needs
Synthesize specific problem areas:
- Before state (current situation and frustrations)
- Desired after state (ideal future state)
- Gap size and impact quantification
- Emotional dimensions of the problem
- Resource constraints preventing solutions
- Skepticism or hesitations
- Success criteria for solution
## Input Format
Use $ARGUMENTS to pass:
- Research data (surveys, interviews, transcripts)
- Customer success/metrics data
- Product usage analytics
- Sales activity and win/loss data
- Existing customer database
- Competitive intelligence
## Output
A comprehensive ICP definition including:
- Firmographic profile (company size, industry, location)
- Behavioral profile (buying patterns, adoption style)
- Complete JTBD mapping (functional, emotional, social jobs)
- Top 5-7 pain points and specific needs
- Quantified impact metrics (cost of problem, value of solution)
- Decision-making process and key stakeholders
- Typical customer journey and timeline
- Go-to-market implications and messaging
- Disqualification criteria (who is NOT a good fit)
- High-value segment within ICP (ideal-of-the-ideal)
## Framework
Based on Jobs to Be Done theory by Clayton Christensen and customer profiling methodology. Combines behavioral data with motivational insights to define actionable customer profiles.
## Tips
- Use quantitative and qualitative data together
- Interview 10+ high-value customers for pattern identification
- Look for non-obvious demographic patterns (outliers can be high-value)
- Define both ideal ICP and acceptable secondary segments
- Revisit ICP quarterly as you gather more customer data
- Use ICP to evaluate all new sales opportunities
- Share ICP across entire organization (marketing, sales, product)
- Remember: ICP should drive focus, not exclude all others
---
### Further Reading
- [5 GTM Principles You Should Know as a PM](https://www.productcompass.pm/p/5-gtm-principles-with-frameworks-templates)
- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
================================================
FILE: pm-market-research/.claude-plugin/plugin.json
================================================
{
"name": "pm-market-research",
"version": "1.0.1",
"description": "Market research skills for PMs: user personas, market segmentation, sentiment analysis, and competitive analysis.",
"author": {
"name": "Paweł Huryn",
"email": "pawel@productcompass.pm",
"url": "https://www.productcompass.pm"
},
"keywords": [
"product-management",
"market-research",
"personas",
"segmentation",
"competitor-analysis",
"market-sizing",
"TAM",
"SAM",
"SOM"
],
"homepage": "https://www.productcompass.pm",
"license": "MIT"
}
================================================
FILE: pm-market-research/README.md
================================================
# pm-market-research
Market research skills for PMs: user personas, market segmentation, sentiment analysis, and competitive analysis.
## Skills (7)
- **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)
- `/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
Paweł Huryn — [The Product Compass Newsletter](https://www.productcompass.pm)
## License
MIT
================================================
FILE: pm-market-research/commands/analyze-feedback.md
================================================
---
description: Analyze user feedback at scale — sentiment analysis, theme extraction, and segment-level insights
argument-hint: "<feedback data as CSV, text, or file>"
---
# /analyze-feedback -- User Feedback Analysis
Process large volumes of user feedback (reviews, surveys, support tickets, NPS responses) into structured insights with sentiment analysis and segment-level patterns.
## Invocation
```
/analyze-feedback [upload a CSV of NPS responses]
/analyze-feedback [paste app store reviews or survey responses]
/analyze-feedback [upload support ticket export]
```
## Workflow
### Step 1: Accept Feedback Data
Accept in any format:
- CSV/Excel with feedback text (and optional metadata: date, segment, rating)
- Pasted text (reviews, survey responses, Slack messages)
- Uploaded documents or exports from feedback tools
Ask:
- What kind of feedback is this? (NPS, reviews, support tickets, survey, etc.)
- Any segments to analyze separately? (user tier, plan, geography)
- What are you looking for? (general themes, specific issues, trends over time)
### Step 2: Analyze
Apply the **sentiment-analysis** skill:
- **Sentiment scoring**: Classify each piece of feedback (positive, neutral, negative)
- **Theme extraction**: Identify recurring topics and cluster related feedback
- **Frequency analysis**: Count how often each theme appears
- **Segment analysis**: Break down sentiment and themes by user segment (if data available)
- **Trend detection**: If dates are available, identify sentiment shifts over time
### Step 3: Generate Analysis Report
```
## Feedback Analysis Report
**Date**: [today]
**Feedback analyzed**: [count] responses
**Source**: [NPS survey / app reviews / support tickets / etc.]
**Period**: [date range if available]
### Overall Sentiment
- Positive: [X%] | Neutral: [Y%] | Negative: [Z%]
- Average sentiment score: [X/10]
- Trend: [improving / stable / declining]
### Top Themes
| # | Theme | Mentions | Sentiment | Segments Most Affected |
|---|-------|----------|-----------|----------------------|
### Theme Deep-Dive
#### Theme 1: [Name] — [X] mentions, [sentiment]
- **What users are saying**: [summary with representative quotes]
- **Root cause**: [what's driving this feedback]
- **Impact**: [how this affects retention, satisfaction, or revenue]
- **Recommendation**: [what to do about it]
[Repeat for top 5-8 themes]
### Segment Analysis
| Segment | Volume | Avg Sentiment | Top Theme | Key Difference |
|---------|--------|-------------|-----------|---------------|
### Notable Quotes
> "[quote]" — [segment, sentiment]
### Trends Over Time
[If date data available: chart-ready data showing sentiment shifts]
### Actionable Insights
1. [Insight + recommended action]
2. ...
### Gaps
[What this feedback doesn't tell you — suggested follow-up research]
```
Save as markdown. If input was structured data (CSV), also save enriched data with sentiment scores as CSV.
### Step 4: Offer Next Steps
- "Want me to **create user personas** from these feedback patterns?"
- "Should I **triage the top themes as feature requests**?"
- "Want me to **design an interview script** to go deeper on a specific theme?"
## Notes
- Sentiment analysis is approximate — flag edge cases (sarcasm, mixed sentiment, non-English tex
gitextract__yxe0xfm/ ├── .claude-plugin/ │ └── marketplace.json ├── .gitattributes ├── .gitignore ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── pm-data-analytics/ │ ├── .claude-plugin/ │ │ └── plugin.json │ ├── README.md │ ├── commands/ │ │ ├── analyze-cohorts.md │ │ ├── analyze-test.md │ │ └── write-query.md │ └── skills/ │ ├── ab-test-analysis/ │ │ └── SKILL.md │ ├── cohort-analysis/ │ │ └── SKILL.md │ └── sql-queries/ │ └── SKILL.md ├── pm-execution/ │ ├── .claude-plugin/ │ │ └── plugin.json │ ├── README.md │ ├── commands/ │ │ ├── generate-data.md │ │ ├── meeting-notes.md │ │ ├── plan-okrs.md │ │ ├── pre-mortem.md │ │ ├── sprint.md │ │ ├── stakeholder-map.md │ │ ├── test-scenarios.md │ │ ├── transform-roadmap.md │ │ ├── write-prd.md │ │ └── write-stories.md │ └── skills/ │ ├── brainstorm-okrs/ │ │ └── SKILL.md │ ├── create-prd/ │ │ └── SKILL.md │ ├── dummy-dataset/ │ │ └── SKILL.md │ ├── job-stories/ │ │ └── SKILL.md │ ├── outcome-roadmap/ │ │ └── SKILL.md │ ├── pre-mortem/ │ │ └── SKILL.md │ ├── prioritization-frameworks/ │ │ └── SKILL.md │ ├── release-notes/ │ │ └── SKILL.md │ ├── retro/ │ │ └── SKILL.md │ ├── sprint-plan/ │ │ └── SKILL.md │ ├── stakeholder-map/ │ │ └── SKILL.md │ ├── summarize-meeting/ │ │ └── SKILL.md │ ├── test-scenarios/ │ │ └── SKILL.md │ ├── user-stories/ │ │ └── SKILL.md │ └── wwas/ │ └── SKILL.md ├── pm-go-to-market/ │ ├── .claude-plugin/ │ │ └── plugin.json │ ├── README.md │ ├── commands/ │ │ ├── battlecard.md │ │ ├── growth-strategy.md │ │ └── plan-launch.md │ └── skills/ │ ├── beachhead-segment/ │ │ └── SKILL.md │ ├── competitive-battlecard/ │ │ └── SKILL.md │ ├── growth-loops/ │ │ └── SKILL.md │ ├── gtm-motions/ │ │ └── SKILL.md │ ├── gtm-strategy/ │ │ └── SKILL.md │ └── ideal-customer-profile/ │ └── SKILL.md ├── pm-market-research/ │ ├── .claude-plugin/ │ │ └── plugin.json │ ├── README.md │ ├── commands/ │ │ ├── analyze-feedback.md │ │ ├── competitive-analysis.md │ │ └── research-users.md │ └── skills/ │ ├── competitor-analysis/ │ │ └── SKILL.md │ ├── customer-journey-map/ │ │ └── SKILL.md │ ├── market-segments/ │ │ └── SKILL.md │ ├── market-sizing/ │ │ └── SKILL.md │ ├── sentiment-analysis/ │ │ └── SKILL.md │ ├── user-personas/ │ │ └── SKILL.md │ └── user-segmentation/ │ └── SKILL.md ├── pm-marketing-growth/ │ ├── .claude-plugin/ │ │ └── plugin.json │ ├── README.md │ ├── commands/ │ │ ├── market-product.md │ │ └── north-star.md │ └── skills/ │ ├── marketing-ideas/ │ │ └── SKILL.md │ ├── north-star-metric/ │ │ └── SKILL.md │ ├── positioning-ideas/ │ │ └── SKILL.md │ ├── product-name/ │ │ └── SKILL.md │ └── value-prop-statements/ │ └── SKILL.md ├── pm-product-discovery/ │ ├── .claude-plugin/ │ │ └── plugin.json │ ├── README.md │ ├── commands/ │ │ ├── brainstorm.md │ │ ├── discover.md │ │ ├── interview.md │ │ ├── setup-metrics.md │ │ └── triage-requests.md │ └── skills/ │ ├── analyze-feature-requests/ │ │ └── SKILL.md │ ├── brainstorm-experiments-existing/ │ │ └── SKILL.md │ ├── brainstorm-experiments-new/ │ │ └── SKILL.md │ ├── brainstorm-ideas-existing/ │ │ └── SKILL.md │ ├── brainstorm-ideas-new/ │ │ └── SKILL.md │ ├── identify-assumptions-existing/ │ │ └── SKILL.md │ ├── identify-assumptions-new/ │ │ └── SKILL.md │ ├── interview-script/ │ │ └── SKILL.md │ ├── metrics-dashboard/ │ │ └── SKILL.md │ ├── opportunity-solution-tree/ │ │ └── SKILL.md │ ├── prioritize-assumptions/ │ │ └── SKILL.md │ ├── prioritize-features/ │ │ └── SKILL.md │ └── summarize-interview/ │ └── SKILL.md ├── pm-product-strategy/ │ ├── .claude-plugin/ │ │ └── plugin.json │ ├── README.md │ ├── commands/ │ │ ├── business-model.md │ │ ├── market-scan.md │ │ ├── pricing.md │ │ ├── strategy.md │ │ └── value-proposition.md │ └── skills/ │ ├── ansoff-matrix/ │ │ └── SKILL.md │ ├── business-model/ │ │ └── SKILL.md │ ├── lean-canvas/ │ │ └── SKILL.md │ ├── monetization-strategy/ │ │ └── SKILL.md │ ├── pestle-analysis/ │ │ └── SKILL.md │ ├── porters-five-forces/ │ │ └── SKILL.md │ ├── pricing-strategy/ │ │ └── SKILL.md │ ├── product-strategy/ │ │ └── SKILL.md │ ├── product-vision/ │ │ └── SKILL.md │ ├── startup-canvas/ │ │ └── SKILL.md │ ├── swot-analysis/ │ │ └── SKILL.md │ └── value-proposition/ │ └── SKILL.md ├── pm-toolkit/ │ ├── .claude-plugin/ │ │ └── plugin.json │ ├── README.md │ ├── commands/ │ │ ├── draft-nda.md │ │ ├── privacy-policy.md │ │ ├── proofread.md │ │ ├── review-resume.md │ │ └── tailor-resume.md │ └── skills/ │ ├── draft-nda/ │ │ └── SKILL.md │ ├── grammar-check/ │ │ └── SKILL.md │ ├── privacy-policy/ │ │ └── SKILL.md │ └── review-resume/ │ └── SKILL.md └── validate_plugins.py
SYMBOL INDEX (18 symbols across 1 files)
FILE: validate_plugins.py
class C (line 49) | class C:
function parse_yaml_frontmatter (line 62) | def parse_yaml_frontmatter(content: str) -> Optional[dict]:
function count_words (line 84) | def count_words(content: str) -> int:
class ValidationResult (line 96) | class ValidationResult:
method __init__ (line 97) | def __init__(self):
method error (line 102) | def error(self, msg: str):
method warn (line 105) | def warn(self, msg: str):
method note (line 108) | def note(self, msg: str):
method ok (line 112) | def ok(self) -> bool:
function validate_manifest (line 116) | def validate_manifest(plugin_dir: str) -> ValidationResult:
function validate_skill (line 182) | def validate_skill(skill_dir: str) -> ValidationResult:
function validate_command (line 232) | def validate_command(cmd_path: str) -> ValidationResult:
function validate_readme (line 268) | def validate_readme(plugin_dir: str) -> ValidationResult:
function validate_cross_references (line 289) | def validate_cross_references(plugin_dir: str, skill_names: list[str]) -...
function validate_plugin (line 315) | def validate_plugin(plugin_dir: str) -> dict:
function print_validation_result (line 356) | def print_validation_result(label: str, vr: ValidationResult, indent: in...
function print_report (line 370) | def print_report(all_results: list[dict]):
function main (line 464) | def main():
Condensed preview — 124 files, each showing path, character count, and a content snippet. Download the .json file or copy for the full structured content (498K chars).
[
{
"path": ".claude-plugin/marketplace.json",
"chars": 2813,
"preview": "{\n \"$schema\": \"https://anthropic.com/claude-code/marketplace.schema.json\",\n \"name\": \"pm-skills\",\n \"version\": \"1.0.1\","
},
{
"path": ".gitattributes",
"chars": 98,
"preview": "# Auto detect text files and perform LF normalization\n* text=auto\n*.py linguist-detectable=false \n"
},
{
"path": ".gitignore",
"chars": 21,
"preview": "_Internal/\nCLAUDE.md\n"
},
{
"path": "CONTRIBUTING.md",
"chars": 1013,
"preview": "# Contributing\n\nPM Skills Marketplace is maintained by [Paweł Huryn](https://www.productcompass.pm) (pawel@productcompas"
},
{
"path": "LICENSE",
"chars": 1068,
"preview": "MIT License\n\nCopyright (c) 2026 Pawel Huryn\n\nPermission is hereby granted, free of charge, to any person obtaining a cop"
},
{
"path": "README.md",
"chars": 21716,
"preview": "\n[![License: MIT](https://img.shields.io/badge/Lice"
},
{
"path": "pm-data-analytics/.claude-plugin/plugin.json",
"chars": 534,
"preview": "{\n \"name\": \"pm-data-analytics\",\n \"version\": \"1.0.1\",\n \"description\": \"Data analytics skills for PMs: SQL query genera"
},
{
"path": "pm-data-analytics/README.md",
"chars": 1036,
"preview": "# pm-data-analytics\n\nData analytics skills for PMs: SQL query generation and cohort analysis. Analyze user data, generat"
},
{
"path": "pm-data-analytics/commands/analyze-cohorts.md",
"chars": 3403,
"preview": "---\ndescription: Perform cohort analysis on user data — retention curves, feature adoption, and engagement trends\nargume"
},
{
"path": "pm-data-analytics/commands/analyze-test.md",
"chars": 3932,
"preview": "---\ndescription: Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recom"
},
{
"path": "pm-data-analytics/commands/write-query.md",
"chars": 2809,
"preview": "---\ndescription: Generate SQL queries from natural language — supports BigQuery, PostgreSQL, MySQL, and more\nargument-hi"
},
{
"path": "pm-data-analytics/skills/ab-test-analysis/SKILL.md",
"chars": 3570,
"preview": "---\nname: ab-test-analysis\ndescription: \"Analyze A/B test results with statistical significance, sample size validation,"
},
{
"path": "pm-data-analytics/skills/cohort-analysis/SKILL.md",
"chars": 5024,
"preview": "---\nname: cohort-analysis\ndescription: \"Perform cohort analysis on user engagement data — retention curves, feature adop"
},
{
"path": "pm-data-analytics/skills/sql-queries/SKILL.md",
"chars": 3628,
"preview": "---\nname: sql-queries\ndescription: \"Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreS"
},
{
"path": "pm-execution/.claude-plugin/plugin.json",
"chars": 624,
"preview": "{\n \"name\": \"pm-execution\",\n \"version\": \"1.0.1\",\n \"description\": \"Execution and product management skills: PRDs, OKRs,"
},
{
"path": "pm-execution/README.md",
"chars": 3545,
"preview": "# pm-execution\n\nExecution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, u"
},
{
"path": "pm-execution/commands/generate-data.md",
"chars": 2804,
"preview": "---\ndescription: Generate realistic dummy datasets for testing — CSV, JSON, SQL inserts, or Python scripts\nargument-hint"
},
{
"path": "pm-execution/commands/meeting-notes.md",
"chars": 2870,
"preview": "---\ndescription: Summarize a meeting transcript into structured notes with decisions, action items, and follow-ups\nargum"
},
{
"path": "pm-execution/commands/plan-okrs.md",
"chars": 3607,
"preview": "---\ndescription: Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key"
},
{
"path": "pm-execution/commands/pre-mortem.md",
"chars": 3717,
"preview": "---\ndescription: Run a pre-mortem risk analysis on a PRD, launch plan, or feature — identify what could go wrong before "
},
{
"path": "pm-execution/commands/sprint.md",
"chars": 5144,
"preview": "---\ndescription: Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes\nargument-hint: \"[plan|"
},
{
"path": "pm-execution/commands/stakeholder-map.md",
"chars": 3734,
"preview": "---\ndescription: Map stakeholders on a Power × Interest grid and create a tailored communication plan\nargument-hint: \"<p"
},
{
"path": "pm-execution/commands/test-scenarios.md",
"chars": 2864,
"preview": "---\ndescription: Generate comprehensive test scenarios from user stories or feature specs — happy paths, edge cases, and"
},
{
"path": "pm-execution/commands/transform-roadmap.md",
"chars": 3413,
"preview": "---\ndescription: Convert a feature-based roadmap into an outcome-focused roadmap that communicates strategic intent\nargu"
},
{
"path": "pm-execution/commands/write-prd.md",
"chars": 3955,
"preview": "---\ndescription: Create a comprehensive Product Requirements Document from a feature idea or problem statement\nargument-"
},
{
"path": "pm-execution/commands/write-stories.md",
"chars": 3900,
"preview": "---\ndescription: Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria\n"
},
{
"path": "pm-execution/skills/brainstorm-okrs/SKILL.md",
"chars": 4337,
"preview": "---\nname: brainstorm-okrs\ndescription: \"Brainstorm team-level OKRs aligned with company objectives — qualitative objecti"
},
{
"path": "pm-execution/skills/create-prd/SKILL.md",
"chars": 3551,
"preview": "---\nname: create-prd\ndescription: \"Create a Product Requirements Document using a comprehensive 8-section template cover"
},
{
"path": "pm-execution/skills/dummy-dataset/SKILL.md",
"chars": 3930,
"preview": "---\nname: dummy-dataset\ndescription: \"Generate realistic dummy datasets for testing with customizable columns, constrain"
},
{
"path": "pm-execution/skills/job-stories/SKILL.md",
"chars": 2969,
"preview": "---\nname: job-stories\ndescription: \"Create job stories using the 'When [situation], I want to [motivation], so I can [ou"
},
{
"path": "pm-execution/skills/outcome-roadmap/SKILL.md",
"chars": 3599,
"preview": "---\nname: outcome-roadmap\ndescription: \"Transform an output-focused roadmap into an outcome-focused one that communicate"
},
{
"path": "pm-execution/skills/pre-mortem/SKILL.md",
"chars": 4078,
"preview": "---\nname: pre-mortem\ndescription: \"Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers ("
},
{
"path": "pm-execution/skills/prioritization-frameworks/SKILL.md",
"chars": 4201,
"preview": "---\nname: prioritization-frameworks\ndescription: \"Reference guide to 9 prioritization frameworks with formulas, when-to-"
},
{
"path": "pm-execution/skills/release-notes/SKILL.md",
"chars": 2562,
"preview": "---\nname: release-notes\ndescription: \"Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clea"
},
{
"path": "pm-execution/skills/retro/SKILL.md",
"chars": 2787,
"preview": "---\nname: retro\ndescription: \"Facilitate a structured sprint retrospective — what went well, what didn't, and prioritize"
},
{
"path": "pm-execution/skills/sprint-plan/SKILL.md",
"chars": 2357,
"preview": "---\nname: sprint-plan\ndescription: \"Plan a sprint with capacity estimation, story selection, dependency mapping, and ris"
},
{
"path": "pm-execution/skills/stakeholder-map/SKILL.md",
"chars": 2498,
"preview": "---\nname: stakeholder-map\ndescription: \"Build a stakeholder map using a power/interest grid, identify communication stra"
},
{
"path": "pm-execution/skills/summarize-meeting/SKILL.md",
"chars": 2993,
"preview": "---\nname: summarize-meeting\ndescription: \"Summarize a meeting transcript into structured notes with date, participants, "
},
{
"path": "pm-execution/skills/test-scenarios/SKILL.md",
"chars": 3462,
"preview": "---\nname: test-scenarios\ndescription: \"Create comprehensive test scenarios from user stories with test objectives, start"
},
{
"path": "pm-execution/skills/user-stories/SKILL.md",
"chars": 2991,
"preview": "---\nname: user-stories\ndescription: \"Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVE"
},
{
"path": "pm-execution/skills/wwas/SKILL.md",
"chars": 3084,
"preview": "---\nname: wwas\ndescription: \"Create product backlog items in Why-What-Acceptance format — independent, valuable, testabl"
},
{
"path": "pm-go-to-market/.claude-plugin/plugin.json",
"chars": 511,
"preview": "{\n \"name\": \"pm-go-to-market\",\n \"version\": \"1.0.1\",\n \"description\": \"Go-to-market skills for PMs: GTM strategy, growth"
},
{
"path": "pm-go-to-market/README.md",
"chars": 1364,
"preview": "# pm-go-to-market\n\nGo-to-market skills for PMs: GTM strategy, growth loops, GTM motions, beachhead segments, and ideal c"
},
{
"path": "pm-go-to-market/commands/battlecard.md",
"chars": 3781,
"preview": "---\ndescription: Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and "
},
{
"path": "pm-go-to-market/commands/growth-strategy.md",
"chars": 4100,
"preview": "---\ndescription: Design sustainable growth mechanisms — growth loops and GTM motions for product-led and sales-led strat"
},
{
"path": "pm-go-to-market/commands/plan-launch.md",
"chars": 4538,
"preview": "---\ndescription: Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan\nargu"
},
{
"path": "pm-go-to-market/skills/beachhead-segment/SKILL.md",
"chars": 5876,
"preview": "---\nname: beachhead-segment\ndescription: \"Identify the first beachhead market segment for a product launch. Evaluates se"
},
{
"path": "pm-go-to-market/skills/competitive-battlecard/SKILL.md",
"chars": 2884,
"preview": "---\nname: competitive-battlecard\ndescription: \"Create sales-ready competitive battlecards comparing your product against"
},
{
"path": "pm-go-to-market/skills/growth-loops/SKILL.md",
"chars": 5758,
"preview": "---\nname: growth-loops\ndescription: \"Identify growth loops (flywheels) for sustainable traction. Evaluates 5 loop types:"
},
{
"path": "pm-go-to-market/skills/gtm-motions/SKILL.md",
"chars": 7554,
"preview": "---\nname: gtm-motions\ndescription: \"Identify the best GTM motions and tools across 7 motion types: Inbound, Outbound, Pa"
},
{
"path": "pm-go-to-market/skills/gtm-strategy/SKILL.md",
"chars": 4045,
"preview": "---\nname: gtm-strategy\ndescription: \"Create a go-to-market strategy covering marketing channels, messaging, success metr"
},
{
"path": "pm-go-to-market/skills/ideal-customer-profile/SKILL.md",
"chars": 6002,
"preview": "---\nname: ideal-customer-profile\ndescription: \"Identify the Ideal Customer Profile (ICP) from research data with demogra"
},
{
"path": "pm-market-research/.claude-plugin/plugin.json",
"chars": 573,
"preview": "{\n \"name\": \"pm-market-research\",\n \"version\": \"1.0.1\",\n \"description\": \"Market research skills for PMs: user personas,"
},
{
"path": "pm-market-research/README.md",
"chars": 1530,
"preview": "# pm-market-research\n\nMarket research skills for PMs: user personas, market segmentation, sentiment analysis, and compet"
},
{
"path": "pm-market-research/commands/analyze-feedback.md",
"chars": 3630,
"preview": "---\ndescription: Analyze user feedback at scale — sentiment analysis, theme extraction, and segment-level insights\nargum"
},
{
"path": "pm-market-research/commands/competitive-analysis.md",
"chars": 3525,
"preview": "---\ndescription: Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differ"
},
{
"path": "pm-market-research/commands/research-users.md",
"chars": 4254,
"preview": "---\ndescription: Comprehensive user research — build personas, segment users, and map the customer journey from research"
},
{
"path": "pm-market-research/skills/competitor-analysis/SKILL.md",
"chars": 4814,
"preview": "---\nname: competitor-analysis\ndescription: \"Analyze competitors with strengths, weaknesses, and differentiation opportun"
},
{
"path": "pm-market-research/skills/customer-journey-map/SKILL.md",
"chars": 3262,
"preview": "---\nname: customer-journey-map\ndescription: \"Create an end-to-end customer journey map with stages, touchpoints, emotion"
},
{
"path": "pm-market-research/skills/market-segments/SKILL.md",
"chars": 3623,
"preview": "---\nname: market-segments\ndescription: \"Identify 3-5 potential customer segments with demographics, JTBD, and product fi"
},
{
"path": "pm-market-research/skills/market-sizing/SKILL.md",
"chars": 4418,
"preview": "---\nname: market-sizing\ndescription: \"Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approache"
},
{
"path": "pm-market-research/skills/sentiment-analysis/SKILL.md",
"chars": 3500,
"preview": "---\nname: sentiment-analysis\ndescription: \"Analyze user feedback data to identify segments with sentiment scores, JTBD, "
},
{
"path": "pm-market-research/skills/user-personas/SKILL.md",
"chars": 3045,
"preview": "---\nname: user-personas\ndescription: \"Create refined user personas from research data — 3 personas with JTBD, pains, gai"
},
{
"path": "pm-market-research/skills/user-segmentation/SKILL.md",
"chars": 4102,
"preview": "---\nname: user-segmentation\ndescription: \"Segment users from feedback data based on behavior, JTBD, and needs. Identifie"
},
{
"path": "pm-marketing-growth/.claude-plugin/plugin.json",
"chars": 541,
"preview": "{\n \"name\": \"pm-marketing-growth\",\n \"version\": \"1.0.1\",\n \"description\": \"Product marketing and growth skills: marketin"
},
{
"path": "pm-marketing-growth/README.md",
"chars": 1185,
"preview": "# pm-marketing-growth\n\nProduct marketing and growth skills: marketing ideas, value proposition statements, North Star me"
},
{
"path": "pm-marketing-growth/commands/market-product.md",
"chars": 3445,
"preview": "---\ndescription: Brainstorm marketing ideas, positioning, value prop statements, and product names — creative marketing "
},
{
"path": "pm-marketing-growth/commands/north-star.md",
"chars": 4001,
"preview": "---\ndescription: Define your North Star Metric and supporting input metrics — classify the business game and validate ag"
},
{
"path": "pm-marketing-growth/skills/marketing-ideas/SKILL.md",
"chars": 2178,
"preview": "---\nname: marketing-ideas\ndescription: \"Generate 5 creative, cost-effective marketing ideas with channels, messaging, an"
},
{
"path": "pm-marketing-growth/skills/north-star-metric/SKILL.md",
"chars": 4152,
"preview": "---\nname: north-star-metric\ndescription: \"Define a North Star Metric and 3-5 supporting input metrics that form a metric"
},
{
"path": "pm-marketing-growth/skills/positioning-ideas/SKILL.md",
"chars": 3002,
"preview": "---\nname: positioning-ideas\ndescription: \"Brainstorm product positioning ideas differentiated from competitors. Identifi"
},
{
"path": "pm-marketing-growth/skills/product-name/SKILL.md",
"chars": 2194,
"preview": "---\nname: product-name\ndescription: \"Brainstorm 5 unique, memorable product names with rationale aligned to brand values"
},
{
"path": "pm-marketing-growth/skills/value-prop-statements/SKILL.md",
"chars": 3030,
"preview": "---\nname: value-prop-statements\ndescription: \"Generate value proposition statements for marketing, sales, and onboarding"
},
{
"path": "pm-product-discovery/.claude-plugin/plugin.json",
"chars": 527,
"preview": "{\n \"name\": \"pm-product-discovery\",\n \"version\": \"1.0.1\",\n \"description\": \"Product discovery skills for PMs: ideation, "
},
{
"path": "pm-product-discovery/README.md",
"chars": 2776,
"preview": "# pm-product-discovery\n\nProduct discovery skills for PMs: ideation, experiments, assumption testing, feature prioritizat"
},
{
"path": "pm-product-discovery/commands/brainstorm.md",
"chars": 4951,
"preview": "---\ndescription: Brainstorm product ideas or experiments from PM, Designer, and Engineer perspectives — for existing or "
},
{
"path": "pm-product-discovery/commands/discover.md",
"chars": 4904,
"preview": "---\ndescription: Run a full product discovery cycle — from ideation through assumption mapping to experiment design\nargu"
},
{
"path": "pm-product-discovery/commands/interview.md",
"chars": 5287,
"preview": "---\ndescription: Prepare a customer interview script or summarize an interview transcript into structured insights\nargum"
},
{
"path": "pm-product-discovery/commands/setup-metrics.md",
"chars": 4398,
"preview": "---\ndescription: Design a product metrics dashboard with North Star metric, input metrics, health metrics, and alert thr"
},
{
"path": "pm-product-discovery/commands/triage-requests.md",
"chars": 4471,
"preview": "---\ndescription: Analyze, categorize, and prioritize a batch of feature requests from customers or stakeholders\nargument"
},
{
"path": "pm-product-discovery/skills/analyze-feature-requests/SKILL.md",
"chars": 2269,
"preview": "---\nname: analyze-feature-requests\ndescription: \"Analyze and prioritize a list of feature requests by theme, strategic a"
},
{
"path": "pm-product-discovery/skills/brainstorm-experiments-existing/SKILL.md",
"chars": 2404,
"preview": "---\nname: brainstorm-experiments-existing\ndescription: \"Design experiments to test assumptions for an existing product —"
},
{
"path": "pm-product-discovery/skills/brainstorm-experiments-new/SKILL.md",
"chars": 2536,
"preview": "---\nname: brainstorm-experiments-new\ndescription: \"Design lean startup experiments (pretotypes) for a new product. Creat"
},
{
"path": "pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md",
"chars": 2943,
"preview": "---\nname: brainstorm-ideas-existing\ndescription: \"Brainstorm product ideas for an existing product using multi-perspecti"
},
{
"path": "pm-product-discovery/skills/brainstorm-ideas-new/SKILL.md",
"chars": 2431,
"preview": "---\nname: brainstorm-ideas-new\ndescription: \"Brainstorm feature ideas for a new product in initial discovery from PM, De"
},
{
"path": "pm-product-discovery/skills/identify-assumptions-existing/SKILL.md",
"chars": 2100,
"preview": "---\nname: identify-assumptions-existing\ndescription: \"Identify risky assumptions for a feature idea in an existing produ"
},
{
"path": "pm-product-discovery/skills/identify-assumptions-new/SKILL.md",
"chars": 3225,
"preview": "---\nname: identify-assumptions-new\ndescription: \"Identify risky assumptions for a new product idea across 8 risk categor"
},
{
"path": "pm-product-discovery/skills/interview-script/SKILL.md",
"chars": 4793,
"preview": "---\nname: interview-script\ndescription: \"Create a structured customer interview script with JTBD probing questions, warm"
},
{
"path": "pm-product-discovery/skills/metrics-dashboard/SKILL.md",
"chars": 5128,
"preview": "---\nname: metrics-dashboard\ndescription: \"Define and design a product metrics dashboard with key metrics, data sources, "
},
{
"path": "pm-product-discovery/skills/opportunity-solution-tree/SKILL.md",
"chars": 4250,
"preview": "---\nname: opportunity-solution-tree\ndescription: \"Build an Opportunity Solution Tree (OST) to structure product discover"
},
{
"path": "pm-product-discovery/skills/prioritize-assumptions/SKILL.md",
"chars": 2283,
"preview": "---\nname: prioritize-assumptions\ndescription: \"Prioritize assumptions using an Impact × Risk matrix and suggest experime"
},
{
"path": "pm-product-discovery/skills/prioritize-features/SKILL.md",
"chars": 2489,
"preview": "---\nname: prioritize-features\ndescription: \"Prioritize a backlog of feature ideas based on impact, effort, risk, and str"
},
{
"path": "pm-product-discovery/skills/summarize-interview/SKILL.md",
"chars": 2029,
"preview": "---\nname: summarize-interview\ndescription: \"Summarize a customer interview transcript into a structured template with JT"
},
{
"path": "pm-product-strategy/.claude-plugin/plugin.json",
"chars": 595,
"preview": "{\n \"name\": \"pm-product-strategy\",\n \"version\": \"1.0.1\",\n \"description\": \"Product strategy skills for PMs: vision, stra"
},
{
"path": "pm-product-strategy/README.md",
"chars": 3088,
"preview": "# pm-product-strategy\n\nProduct strategy skills for PMs: vision, strategy canvas, startup canvas, value propositions, lea"
},
{
"path": "pm-product-strategy/commands/business-model.md",
"chars": 5987,
"preview": "---\ndescription: Explore business models using Lean Canvas, Business Model Canvas, Startup Canvas, or Value Proposition "
},
{
"path": "pm-product-strategy/commands/market-scan.md",
"chars": 4575,
"preview": "---\ndescription: Comprehensive macro environment analysis — SWOT, PESTLE, Porter's Five Forces, and Ansoff Matrix in one"
},
{
"path": "pm-product-strategy/commands/pricing.md",
"chars": 4557,
"preview": "---\ndescription: Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing ex"
},
{
"path": "pm-product-strategy/commands/strategy.md",
"chars": 4194,
"preview": "---\ndescription: Create a comprehensive product strategy using the 9-section Strategy Canvas — from vision to defensibil"
},
{
"path": "pm-product-strategy/commands/value-proposition.md",
"chars": 2822,
"preview": "---\ndescription: Design a value proposition using the 6-part JTBD template — Who, Why, What before, How, What after, Alt"
},
{
"path": "pm-product-strategy/skills/ansoff-matrix/SKILL.md",
"chars": 5684,
"preview": "---\nname: ansoff-matrix\ndescription: \"Generate an Ansoff Matrix analysis mapping growth strategies across market penetra"
},
{
"path": "pm-product-strategy/skills/business-model/SKILL.md",
"chars": 5781,
"preview": "---\nname: business-model\ndescription: \"Generate a Business Model Canvas with all 9 building blocks. Use when creating a "
},
{
"path": "pm-product-strategy/skills/lean-canvas/SKILL.md",
"chars": 4857,
"preview": "---\nname: lean-canvas\ndescription: \"Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair "
},
{
"path": "pm-product-strategy/skills/monetization-strategy/SKILL.md",
"chars": 6660,
"preview": "---\nname: monetization-strategy\ndescription: \"Brainstorm 3-5 monetization strategies with audience fit, risks, and valid"
},
{
"path": "pm-product-strategy/skills/pestle-analysis/SKILL.md",
"chars": 4647,
"preview": "---\nname: pestle-analysis\ndescription: \"Perform a PESTLE analysis covering Political, Economic, Social, Technological, L"
},
{
"path": "pm-product-strategy/skills/porters-five-forces/SKILL.md",
"chars": 8183,
"preview": "---\nname: porters-five-forces\ndescription: \"Perform Porter's Five Forces analysis — competitive rivalry, supplier power,"
},
{
"path": "pm-product-strategy/skills/pricing-strategy/SKILL.md",
"chars": 3652,
"preview": "---\nname: pricing-strategy\ndescription: \"Analyze and design pricing strategies including pricing models, competitive pri"
},
{
"path": "pm-product-strategy/skills/product-strategy/SKILL.md",
"chars": 4831,
"preview": "---\nname: product-strategy\ndescription: \"Create a comprehensive product strategy using the 9-section Product Strategy Ca"
},
{
"path": "pm-product-strategy/skills/product-vision/SKILL.md",
"chars": 2516,
"preview": "---\nname: product-vision\ndescription: \"Brainstorm an inspiring, achievable, and emotional product vision that motivates "
},
{
"path": "pm-product-strategy/skills/startup-canvas/SKILL.md",
"chars": 6327,
"preview": "---\nname: startup-canvas\ndescription: \"Generate a Startup Canvas combining Product Strategy (9 sections) and Business Mo"
},
{
"path": "pm-product-strategy/skills/swot-analysis/SKILL.md",
"chars": 3811,
"preview": "---\nname: swot-analysis\ndescription: \"Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threa"
},
{
"path": "pm-product-strategy/skills/value-proposition/SKILL.md",
"chars": 5827,
"preview": "---\nname: value-proposition\ndescription: \"Design a detailed value proposition using a 6-part JTBD template — Who, Why, W"
},
{
"path": "pm-toolkit/.claude-plugin/plugin.json",
"chars": 555,
"preview": "{\n \"name\": \"pm-toolkit\",\n \"version\": \"1.0.1\",\n \"description\": \"PM utility skills: resume review, NDA drafting, privac"
},
{
"path": "pm-toolkit/README.md",
"chars": 1539,
"preview": "# pm-toolkit\n\nPM utility skills: resume review, NDA drafting, privacy policy generation, and grammar/flow checking. Esse"
},
{
"path": "pm-toolkit/commands/draft-nda.md",
"chars": 2050,
"preview": "---\ndescription: Draft a Non-Disclosure Agreement between two parties with jurisdiction-appropriate clauses\nargument-hin"
},
{
"path": "pm-toolkit/commands/privacy-policy.md",
"chars": 2172,
"preview": "---\ndescription: Draft a privacy policy covering data collection, usage, storage, and compliance requirements\nargument-h"
},
{
"path": "pm-toolkit/commands/proofread.md",
"chars": 1800,
"preview": "---\ndescription: Check grammar, logic, and flow in any text — targeted fixes without rewriting\nargument-hint: \"<text to "
},
{
"path": "pm-toolkit/commands/review-resume.md",
"chars": 3149,
"preview": "---\ndescription: Comprehensive PM resume review against 10 best practices — structure, impact metrics, keywords, and act"
},
{
"path": "pm-toolkit/commands/tailor-resume.md",
"chars": 2508,
"preview": "---\ndescription: Tailor a PM resume to a specific job description — keyword alignment, experience reframing, and strateg"
},
{
"path": "pm-toolkit/skills/draft-nda/SKILL.md",
"chars": 7464,
"preview": "---\nname: draft-nda\ndescription: \"Draft a detailed Non-Disclosure Agreement between two parties covering information typ"
},
{
"path": "pm-toolkit/skills/grammar-check/SKILL.md",
"chars": 9673,
"preview": "---\nname: grammar-check\ndescription: \"Identify grammar, logical, and flow errors in text and suggest targeted fixes with"
},
{
"path": "pm-toolkit/skills/privacy-policy/SKILL.md",
"chars": 10659,
"preview": "---\nname: privacy-policy\ndescription: \"Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compl"
},
{
"path": "pm-toolkit/skills/review-resume/SKILL.md",
"chars": 11289,
"preview": "---\nname: review-resume\ndescription: \"Comprehensive PM resume review and tailoring against 10 best practices including X"
},
{
"path": "validate_plugins.py",
"chars": 17241,
"preview": "#!/usr/bin/env python3\n\"\"\"\nPlugin Collection Validator\n===========================\nValidates all plugins in the collecti"
}
]
About this extraction
This page contains the full source code of the phuryn/pm-skills GitHub repository, extracted and formatted as plain text for AI agents and large language models (LLMs). The extraction includes 124 files (464.4 KB), approximately 109.3k tokens, and a symbol index with 18 extracted functions, classes, methods, constants, and types. Use this with OpenClaw, Claude, ChatGPT, Cursor, Windsurf, or any other AI tool that accepts text input. You can copy the full output to your clipboard or download it as a .txt file.
Extracted by GitExtract — free GitHub repo to text converter for AI. Built by Nikandr Surkov.