Updated 1w ago
by product-on-purpose
pm-skills
68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus 6 sub-agents, workflows, 200+ output samples, guides, and CI-enforced contracts. Apache 2.0.
728 GitHub stars (728)
+29 in 20 days
| Period | New stars |
|---|---|
| Sep 27 | +1 |
| Sep 28 | 0 |
| Sep 29 | 0 |
| Sep 30 | +3 |
| Oct 1 | +1 |
| Oct 2 | +3 |
| Oct 3 | +1 |
| Oct 4 | 0 |
| Oct 5 | +1 |
| Oct 6 | +1 |
| Oct 7 | +3 |
| Oct 8 | +1 |
| Oct 9 | +1 |
| Oct 10 | +1 |
| Oct 11 | −1 |
| Oct 12 | +1 |
| Oct 13 | +3 |
| Oct 14 | +4 |
| Oct 15 | +2 |
| Oct 16 | +3 |
- 30 skills (30 skills found in its SKILL.md files)
- 95 forks (95 forks)
- 1w ago last update (Last updated 1w ago)
Install
Skills CLI
npx skills add product-on-purpose/pm-skills
Asks which skills and agents to install. Just one: npx skills add product-on-purpose/pm-skills --skill define-hypothesis — add -g for every project.
Claude Code
git clone https://github.com/product-on-purpose/pm-skillscp -r "pm-skills/skills/define-hypothesis" ~/.claude/skills/
Copies the define-hypothesis skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add product-on-purpose/pm-skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 78 files.
-
define-hypothesis
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
skills/define-hypothesis/SKILL.md on GitHub (opens in a new tab) -
define-jtbd-canvas
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
skills/define-jtbd-canvas/SKILL.md on GitHub (opens in a new tab) -
define-opportunity-tree
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it…
skills/define-opportunity-tree/SKILL.md on GitHub (opens in a new tab) -
define-prioritization-framework
Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estim…
skills/define-prioritization-framework/SKILL.md on GitHub (opens in a new tab) -
define-problem-statement
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
skills/define-problem-statement/SKILL.md on GitHub (opens in a new tab) -
deliver-acceptance-criteria
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-e…
skills/deliver-acceptance-criteria/SKILL.md on GitHub (opens in a new tab) -
deliver-edge-cases
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which w…
skills/deliver-edge-cases/SKILL.md on GitHub (opens in a new tab) -
deliver-launch-checklist
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed before release. Use for significant or cross-team launches, not a small single-team change. For the customer-facing announcement of what shipped, use deliver-release-notes instead.
skills/deliver-launch-checklist/SKILL.md on GitHub (opens in a new tab) -
deliver-prd
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
skills/deliver-prd/SKILL.md on GitHub (opens in a new tab) -
deliver-release-notes
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.
skills/deliver-release-notes/SKILL.md on GitHub (opens in a new tab) -
deliver-user-stories
Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.
skills/deliver-user-stories/SKILL.md on GitHub (opens in a new tab) -
develop-adr
Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.
skills/develop-adr/SKILL.md on GitHub (opens in a new tab) -
develop-design-rationale
Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.
skills/develop-design-rationale/SKILL.md on GitHub (opens in a new tab) -
develop-solution-brief
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.
skills/develop-solution-brief/SKILL.md on GitHub (opens in a new tab) -
develop-spike-summary
Documents the results of a completed technical or design spike, capturing the original question, approach, evidence-backed findings, and a clear proceed-or-not recommendation so the team does not re-litigate the exploration. Use once a time-boxed investigation has concluded. For the architecture decision the spike informs, use develop-adr instead; for research-based exploration, use discover-inte…
skills/develop-spike-summary/SKILL.md on GitHub (opens in a new tab) -
discover-competitive-analysis
Creates a structured competitive analysis comparing features, pricing, and positioning across 3-5 direct and indirect competitors, with a 2x2 map and actionable strategic recommendations. Use before entering a market, planning differentiation, or after losing deals. For market size rather than competitor positioning, use discover-market-sizing instead.
skills/discover-competitive-analysis/SKILL.md on GitHub (opens in a new tab) -
discover-interview-synthesis
Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to extract and communicate findings across participants. Distinct from foundation-meeting-recap, which summarizes one internal meeting for its attendees; this skill aggregates research conversations into evidence-backed findings.
skills/discover-interview-synthesis/SKILL.md on GitHub (opens in a new tab) -
discover-journey-map
Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart. Use when synthesizing existing research into the shape of a customer's experience, end-to-end or for one phase. Without research signal yet, run discover-interview-synthesis or measure-survey-analysis first; refuses to fabr…
skills/discover-journey-map/SKILL.md on GitHub (opens in a new tab) -
discover-market-sizing
Estimate market opportunity (TAM, SAM, SOM) using multiple sizing frameworks (top-down, bottom-up, comparable company, analogous market). Triangulates across frameworks, highlights where they converge and diverge as signal, and produces a calibrated range with source-graded confidence labels. Refuses unbounded fabrications; always offers a labeled lower-confidence path when data is thin. Used for…
skills/discover-market-sizing/SKILL.md on GitHub (opens in a new tab) -
discover-stakeholder-summary
Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach. Use at project kickoff, when taking over from another PM, or when resistance signals misalignment. For the update you send to those stakeholders, use foundation-stakeholder-update instead; this skill maps them, that one talks to them.
skills/discover-stakeholder-summary/SKILL.md on GitHub (opens in a new tab) -
foundation-build-risk-review
Runs a fast pre-build risk review on a product idea, feature request, or scope change, naming the single assumption most likely to make it fail and returning a clear verdict (build small, validate first, pivot first, or don't build yet) with a no-code validation step. Use before committing build effort, when triaging whether to honor a feature request, or when deciding whether to expand scope, ah…
skills/foundation-build-risk-review/SKILL.md on GitHub (opens in a new tab) -
foundation-lean-canvas
Produces a one-page lean canvas across nine interlocking blocks (problem, customer, UVP, solution, channels, revenue, cost, metrics, unfair advantage) with optional inline HTML and SVG visual rendering. Use when framing a new product thesis, stress-testing an existing strategy, comparing strategic options side-by-side, or aligning a team on business-model assumptions. Works as a strategic hub tha…
skills/foundation-lean-canvas/SKILL.md on GitHub (opens in a new tab) -
foundation-meeting-agenda
Produces an attendee-facing agenda that sets what will be discussed, who owns each topic, and how time will be spent. Supports ten meeting type variants (standup, planning, review, decision-making, brainstorm, 1-on-1, stakeholder-review, project-kickoff, working-session, exec-briefing). Emits a shareable summary suitable for Slack or email plus a full agenda with time-boxed topics, type tags, own…
skills/foundation-meeting-agenda/SKILL.md on GitHub (opens in a new tab) -
foundation-meeting-brief
Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key messages, anticipated questions with prepared responses, risks and tensions, specific asks, and success signals. Distinct from meeting-agenda because this artifact is not shared with attendees; it is the user's personal tactic…
skills/foundation-meeting-brief/SKILL.md on GitHub (opens in a new tab) -
foundation-meeting-recap
Produces a topic-segmented post-meeting summary for attendees with decisions highlighted and actions captured inline per topic (plus a consolidated action view at the end). Auto-populates topic skeleton from a sibling meeting-agenda when available and reconciles planned vs. actual topics. Accepts transcripts from Zoom, Meet, Otter, Fireflies, Krisp MCP, or manual notes; runs on variable-quality i…
skills/foundation-meeting-recap/SKILL.md on GitHub (opens in a new tab) -
foundation-meeting-synthesize
Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, cont…
skills/foundation-meeting-synthesize/SKILL.md on GitHub (opens in a new tab) -
foundation-okr-writer
Drafts, reviews, rewrites, and coaches outcome-based OKR sets across team, department, product, or company scopes. Supports five entry modes (Guided default, One-Shot via --oneshot, Sustained Coach, Audit Only, Rewrite). Diagnoses empowered-team context and adjusts framing; refuses to fabricate baselines or targets; refuses to use OKR scores for compensation; reframes feature-delivery KRs into ou…
skills/foundation-okr-writer/SKILL.md on GitHub (opens in a new tab) -
foundation-persona
Generates an evidence-calibrated product or marketing persona using the canonical v2.5 output contract. Use when shaping artifact perspective, stress-testing decisions, or framing product and GTM strategy.
skills/foundation-persona/SKILL.md on GitHub (opens in a new tab) -
foundation-prioritized-action-plan
Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation). Outputs one saveable document with an executive summary, input mirror, situation classification (Cynefin), the binding constraint (Theory of Constraints), prioritized questions and open decisions, a ranked action plan with the critic…
skills/foundation-prioritized-action-plan/SKILL.md on GitHub (opens in a new tab) -
foundation-stakeholder-briefings
Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of audience-tailored briefings, each re-pitched to a stakeholder lens (executive, board, engineering, UX, PMM, sales, CS, legal, data, or a custom audience). Every briefing is a traceable projection of the master, so the versions never disagree. Us…
skills/foundation-stakeholder-briefings/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.