pm-execution

A product-management toolkit for turning ideas into plans and planned work into action. It covers product requirement documents, goals, roadmaps, short work cycles, user stories, risk reviews, stakeholder maps, and ways to set priorities.

In plain words
What is it for?
Use it to write requirements, define goals, plan a product roadmap, organise work for a short development cycle, identify risks before starting, map affected people, write user stories, and prioritise a backlog.
Why use it?
It helps teams turn unclear product work into shared plans, decisions, and next steps. This reduces confusion about what to build, why it matters, and what should happen first.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code
/plugin marketplace add killvxk/pm-skills-zh
agentmods
npx agentmods add plugins/killvxk/pm-skills-zh/pm-execution
Clone the repo
git clone --depth 1 https://github.com/killvxk/pm-skills-zh

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

pm-execution scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

pm-execution/.claude-plugin/plugin.json · 26 lines

What it actually says

{
  "name": "pm-execution",
  "version": "1.0.1",
  "description": "执行与产品管理技能:PRD(产品需求文档)、OKR(目标与关键成果)、路线图、Sprint(冲刺)、事前剖析(Pre-mortem)、干系人地图、用户故事、优先级框架等。",
  "author": {
    "name": "Paweł Huryn",
    "email": "[email protected]",
    "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"
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 26 lines scan A 638dbd9f29db

Subscribe to this mod's changes

pm-execution is a plugin published in the GitHub repository killvxk/pm-skills-zh (149 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.