←Leaderboard/Business/pm-skills
Last commit on October 30, 2026·Created on January 9, 2026

product-on-purpose/pm-skills

“Guide product discovery, planning, and delivery.”
Combined rank
#513
across all skills
In Business
#13
category rank
Stars
812
+2.6% in last 7d
Forks
102
+1.0% in last 7d
Watchers
10
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

A product-management library organized across discovery, definition, delivery, measurement, and iteration. Templates and sample outputs give agents a concrete quality reference, while workflows connect individual skills into larger pieces of work.

WHO IT'S FOR
AI agent / automation builders
implementing product management capabilities in AI agents
Product Managers
standardizing AI-driven product discovery and delivery
Technical leads / architects
designing AI agent workflows with strict output contracts
AI agent power users
enhancing Claude or Codex with PM-specific skillsets

Use this skill collection

Follow the documented setup, then try a first task.

Setup

Claude Code plugin marketplace

Installs: PM-Skills plugin: all 68 skills and their slash commands, plus workflow commands, templates, sub-agents, and sample outputs. · Claude Code

Before you start
  • Claude Code
  1. Enter both commands in a Claude Code session to add the marketplace and install the PM-Skills plugin.

    /plugin marketplace add product-on-purpose/agent-plugins
    /plugin install pm-skills@product-on-purpose
README.md ↗ · Checked Nov 14, 2026

Give it something to do.

Suggested first task

Frame one product problem

Uses define-problem-statement

  • Notes describing one initiative and its affected user segment
  • Available research, support tickets, or behavioral data
  • Business context, metric baselines and targets, and known constraints
Use define-problem-statement to turn my notes into a concise problem statement for one initiative. Identify the affected user segment, pain points, business impact, success metrics with baselines and targets, constraints, and open questions. Keep the framing focused on the problem rather than prescribing a solution, and ask about missing evidence.
Suggested first task

Draft a one-page solution brief

Uses develop-solution-brief

  • An agreed problem statement or concise problem summary
  • The proposed solution and essential capabilities
  • Success targets, scope limits, alternatives considered, risks, and potential owners
Use develop-solution-brief to draft a one-page brief for my proposed solution to an agreed problem. Include a short problem recap, the proposed solution, 3–5 essential features, measurable success criteria, trade-offs, risks and mitigations, and 3–5 immediate next steps. Use clear language suitable for stakeholder review.
Suggested first task

Turn shipped changes into release notes

Uses deliver-release-notes

  • A changelog, completed tickets, or pull request descriptions for one release with user-visible changes
  • Known issues or limitations
  • Product and audience context
Use deliver-release-notes to draft customer-facing release notes for this release from my changelog. Select 1–3 highlights, translate technical changes into user benefits, and group the remaining items into New Features, Improvements, and Bug Fixes. Keep each item to 1–2 sentences and acknowledge supplied known issues. Return a draft for review.