PM Playbook

Plugin pm-playbook from marketplace pm-playbook in hoodiecollin/ai-pm-playbook. Commands read from the repo's manifest — 1 month ago.

Skills (9)

• check

  Lint the backlog against the pm-playbook invariants and fix what it finds, using the executable fix each violation carries. Use before finishing any task that touched issues, or when asked to audit tracking. Keywords - check, lint, invariants, violations, PM010, PM013, PM018, PM020, migrate.

• experiment

  Run an experiment under pm-playbook: a charter whose question can come back no, a fair method, a bounded scope, then a verdict that commits, kills, or is inconclusive. Use for spikes, benchmarks, evaluations and any work whose deliverable is a finding. Keywords - experiment, spike, benchmark, evalua

• file

  File a new issue under pm-playbook: check for duplicates, pick exactly one type, write the need in plain English, and link it to its epic. Use whenever new work is identified or the user asks to open an issue. Keywords - new issue, file, create, gh issue create, type label, epic, triage.

• fix

  Fix a bug under pm-playbook: reproduce it as a failing test, fix it, and land one PR whose test proves it; for a hotfix, write the warrant gate first. Use for any bugfix or hotfix work item. Keywords - bug, bugfix, hotfix, regression test, reproduction, root cause, warrant, patch release.

• intent

  Write an improvement's intent gate with the user: the problem, the outcome, acceptance examples and non-goals, short enough to approve by reading. Use when an improvement is at intent-next or intent-pending. Keywords - intent, gate:intent, requirements, acceptance criteria, scope, non-goals, what an

• next

  See where work stands and what comes next under pm-playbook: the derived ladder, what is left on a milestone, and the context pack an agent needs before working an issue or fanning out across several. Keywords - what's next, status, ladder, milestone, roadmap, what is left, context, neighbourhood, p

• pm-playbook

  How this repo tracks work in GitHub Issues: milestones say when, one type label says what kind, and gates are sub-issues a human closes. Use for any issue-tracking task, then load the workflow skill it points to. Keywords - issue, backlog, milestone, label, epic, gate, intent, proof, hotfix, experim

• prove

  Write an improvement's proof gate: the approach plus evidence for every claim it rests on — commands run, code read at a commit — then close it with pm-playbook prove or hand it to the user. Use when an improvement is at proof-next or proof-pending. Keywords - proof, gate:proof, claims, evidence, sp

• release

  Decide whether a milestone can be tagged and keep the release-gate asset ledger current; covers the release spine, patch milestones, and which branch a change targets. Use when preparing a release, landing a change that touches a published asset, or choosing a PR's base branch. Keywords - release, t

Hooks (1)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/guard-issue-mutation.mjs"

Similar plugins