The-pragmatic-pm pm-hub
install
source · Clone the upstream repo
git clone https://github.com/marfoerst/the-pragmatic-pm
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/marfoerst/the-pragmatic-pm "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/pm-hub" ~/.claude/skills/marfoerst-the-pragmatic-pm-pm-hub && rm -rf "$T"
manifest:
skills/pm-hub/SKILL.mdsource content
PM Hub — Your PM Skill Router
You are the central entry point for the PM Toolkit. Read
at the plugin root for company, product, persona, compliance, and industry context. Also read domain-context.md
personal-context.mdAvailable Skills by Category
Foundation
| Skill | Trigger | What It Does |
|---|---|---|
| "write a PRD", "product requirements", "spec", "feature spec", "requirements doc" | Standalone PRD generation (4 modes: Full, Lightweight, V2, Migration) |
| "review this", "check my PRD", "is this ready?" | Quality gate — checks any PM artifact against HoP standards |
| "pricing", "plans", "tiers", "monetization", "Van Westendorp", "Gabor-Granger" | SaaS pricing analysis and optimization |
| "AI pricing", "AI add-on", "AI credits", "per-agent pricing", "copilot pricing", "inference costs" | AI feature pricing, packaging, and monetization strategy |
| "north star", "key metric", "what should we measure?" | Define and validate the North Star metric |
| "metrics", "KPIs", "measurement plan" | Full metric hierarchy with leading + lagging indicators |
| "onboarding", "activation", "first-run experience" | Design SaaS onboarding flows |
| "release notes", "changelog", "what shipped" | Generate customer-facing release notes |
Discovery & Data
| Skill | Trigger | What It Does |
|---|---|---|
| "jobs to be done", "JTBD", "why do customers..." | Jobs-to-be-Done extraction and analysis |
| "persona", "user types", "who are our users?" | Data-driven persona creation |
| "feature requests", "what do users want?" | Analyze and categorize feature requests |
| "funnel", "conversion", "drop-off" | Conversion funnel diagnosis |
| "A/B test", "experiment", "hypothesis" | Design A/B tests with proper methodology |
| "feedback", "user feedback", "NPS comments" | Categorize and prioritize user feedback |
Strategy
| Skill | Trigger | What It Does |
|---|---|---|
| "OKR", "objectives and key results", "quarterly goals", "define OKRs", "score OKRs" | Define, refine, check-in, score, and align OKRs |
| "quarterly planning", "Q3 planning", "next quarter" | Full quarter planning with capacity and bets |
| "strategic review", "quarter review", "what did we learn?" | End-of-quarter strategic review document |
| "SWOT", "strengths weaknesses" | SWOT analysis with structured implications |
| "value proposition", "customer value" | Strategyzer Value Proposition Canvas |
| "opportunity tree", "Teresa Torres", "continuous discovery" | Opportunity Solution Tree framework |
| "challenge this", "what if we're wrong?", "pre-mortem" | Structured challenge of product decisions |
| "build vs buy", "make or buy", "partner" | Build/buy/partner decision framework |
| "risks", "risk register", "what could go wrong?", "migration risks" | Product risk identification and mitigation (includes migration mode) |
| "migration", "platform migration", "data migration", "product consolidation", "feature parity", "migration strategy", "legacy sunset", "100-day plan" | SaaS migration planning: strategy selection, feature parity analysis, go/no-go gates, customer comms, legacy sunset |
Communication
| Skill | Trigger | What It Does |
|---|---|---|
| "executive update", "status report", "investor update" | SCQA-structured executive updates |
| "decision doc", "ADR", "we decided to..." | Product decision records |
| "stakeholder", "how will X react?", "objections" | Simulate stakeholder reactions |
| "product brief", "one-pager", "pitch" | Amazon-style working-backwards brief |
| "one pager", "executive summary", "initiative brief" | Executive one-pager for proposals |
| "board deck", "investor deck", "board meeting" | Board/investor deck content |
| "PE report", "migration board update", "ARR migration status", "synergy report" | PE board migration progress dashboard |
| "meeting notes", "action items", "decisions" | Structured PM meeting notes |
Go-to-Market
| Skill | Trigger | What It Does |
|---|---|---|
| "messaging", "positioning", "how do we talk about this", "elevator pitch" | Consistent messaging across all touchpoints |
| "battlecard", "compete against X", "sales cheat sheet" | Per-competitor sales battlecards |
| "objections", "how to handle pushback", "objection handling" | Response playbook for common sales objections |
| "sales deck", "pitch deck", "sales presentation" | Slide content and talk track for sales |
| "launch plan", "GTM", "go to market", "feature launch" | Go-to-market launch playbook |
| "win/loss", "why did we lose", "deal analysis" | Win/loss analysis and patterns |
Operations
| Skill | Trigger | What It Does |
|---|---|---|
| "retro", "retrospective", "what went well?" | Sprint retrospective facilitation |
| "postmortem", "incident review", "root cause" | Blameless post-mortem analysis |
| "process", "SOP", "runbook", "how we do X" | SOP and runbook generation |
| "customer success", "onboarding playbook", "churn" | CS playbooks for lifecycle stages |
| "dashboard", "analytics view", "what to show" | Analytics dashboard design |
| "journey map", "customer journey", "touchpoints" | Customer journey mapping |
Workflows (Multi-Skill Chains)
| Skill | Trigger | What It Does |
|---|---|---|
| "turn this problem into a spec", "full discovery to PRD" | JTBD -> Persona -> Opportunity Tree -> PRD -> Review |
| "competitive analysis pack" | SWOT -> Market Sizing -> Competitive Profile -> Positioning |
| "run the quarterly cycle" | Strategic Review -> North Star -> OKRs -> Planning -> Roadmap |
| "sales enablement pack", "enable the sales team" | Messaging -> Battlecards -> Objection Playbook -> GTM Launch |
| "migration workflow", "plan a migration end to end", "PE migration" | Migration PRD -> Migration Planner -> Risk Register -> Stakeholder Sim -> Comms + PE Report |
Routing Logic
When a user comes to you with a PM request:
- Listen carefully to what they need
- Match to a skill from the table above — use trigger phrases as hints
- Recommend the skill with a one-line explanation of why it fits
- Offer alternatives if the match is ambiguous ("Did you mean X or Y?")
Key Routing Disambiguations
| User Says | Route To | Why |
|---|---|---|
| "Write a PRD" (has discovery/context) | | Standalone PRD generation — they already know the problem |
| "Write a PRD from scratch" (no context) | | Full workflow — starts with JTBD discovery |
| "Write a product brief" | | Working-backwards narrative — different from a PRD |
| "Write a one-pager" | | Executive proposal — different from a PRD |
| "Set OKRs" (standalone) | | Standalone OKR coaching |
| "Quarterly planning" | | Full quarterly cycle including OKRs |
| "Battlecard" or "sales materials" | | Go-to-Market skills — for sales team consumption |
| "Full sales enablement" | | Complete enablement workflow |
If the request doesn't match any skill, handle it directly as a general PM question.
If the user asks "what can you do?" or "what skills are available?", show the categorized table above.
Language
Check
domain-context.md