pm-ops
A Claude Code skills plugin for solo technical builders who want thoughtful product planning before writing code. 57 curated PM skills across 7 categories.
Built from my own workflow — pulled together, reorganized, and tuned around how I actually plan and ship as a solo builder, so the loop from idea to implementation runs faster and tighter. References and adapts material from phuryn/pm-skills, deanpeters/Product-Manager-Skills, and GStack by Garry Tan.
Install
claude plugin install songdu/pm-ops
Skills
All skills follow the deanpeters interactive style [asking clarifying questions before generating output] for the 35 interactive skills. Provide an argument to skip to direct output mode.
pm-explore — Discovery & Problem Framing (13 skills)
| Skill | What it does |
|---|
/pm-explore:problem-frame | Structure an ambiguous problem into a clear problem statement [using hypothesis-driven framing] |
/pm-explore:risk-assumptions | Surface and map assumptions by importance vs. evidence [assumption mapping matrix] |
/pm-explore:experiment-validation | Design lightweight experiments to test a hypothesis before building |
/pm-explore:opportunity-tree | Build an opportunity solution tree [connecting outcomes to opportunities to solutions] |
/pm-explore:jtbd-interview | Generate JTBD interview questions and synthesize findings [Jobs to Be Done framework] |
/pm-explore:user-persona | Create a user persona from research data or assumptions |
/pm-explore:customer-journey | Map the customer journey [touchpoints, emotions, pain points per stage] |
/pm-explore:market-sizing | Estimate market size [TAM/SAM/SOM — total/serviceable/obtainable addressable market] |
/pm-explore:market-segment | Identify and profile target market segments |
/pm-explore:competitor-analysis | Analyze competitors with a structured comparison framework |
/pm-explore:problem-storyboard | Narrate the user problem as a before/during/after story |
/pm-explore:company-research | Research a company for partnership, competitive, or job context |
/pm-explore:discovery-workflow | Design a discovery sprint [short focused research cycle] plan |
pm-strategy — Product Strategy (9 skills)
| Skill | What it does |
|---|
/pm-strategy:product-strategy | Write a product strategy doc [vision, bets, tradeoffs] |
/pm-strategy:product-positioning | Craft a positioning statement and narrative |
/pm-strategy:customer-value | Define the value proposition [what customer gains, what pains it relieves] |
/pm-strategy:business-canvas | Fill out a Business Model Canvas [9-block framework for business model design] |
/pm-strategy:business-model | Analyze or design a business model with revenue and cost logic |
/pm-strategy:pricing-strategy | Develop a pricing strategy with model options and rationale |
/pm-strategy:market-analysis | Write a market analysis covering size, trends, dynamics |
/pm-strategy:success-metric | Define success metrics and a measurement plan [north star + supporting metrics] |
/pm-strategy:product-name | Generate and evaluate product name options |
pm-planning — Product Planning (9 skills)
| Skill | What it does |
|---|
/pm-planning:product-spec | Write a product spec [PRD — product requirements document] |
/pm-planning:roadmap-planning | Build a product roadmap [now/next/later or quarterly view] |
/pm-planning:user-stories | Write user stories with acceptance criteria [in As a/I want/So that format] |
/pm-planning:scope-planning | Define scope using MoSCoW [must/should/could/won't] |
/pm-planning:backlog-priority | Prioritize a backlog using RICE or ICE scoring [reach/impact/confidence/effort] |
/pm-planning:objective-planning | Write OKRs [Objectives and Key Results] for a team or product area |
/pm-planning:sprint-planning | Plan a sprint [2-week iteration] with goals and task breakdown |
/pm-planning:risk-planning | Identify and mitigate risks with a risk register |
/pm-planning:test-scenarios | Write test scenarios for a feature before development |
pm-engineering — Engineering Collaboration (5 skills)
| Skill | What it does |
|---|
/pm-engineering:eng-review | Structure a technical review conversation for a PM working with engineers |
/pm-engineering:code-review | Review code from a product perspective [correctness, scope, risk] |
/pm-engineering:design-build | Translate a design into implementation tasks |
/pm-engineering:security-audit | Identify security considerations for a feature or architecture |
/pm-engineering:safe-mode | Pre-flight checklist before shipping [risk, rollback, monitoring] |
pm-release — Launch & Go-to-Market (7 skills)
