Pm all

Skill wei63w/pm-manager/adapters/cursor/skills/pm-all

Know what to fix next — local .pm governance skill pack for AI coding agents (Spec Kit–inspired).

Install

npx -y skills add wei63w/pm-manager --skill pm-all

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.

What its author says it does

Copied from the file, not written here

Orchestrate full governance scan with prerequisite gates; default noise-filtered summary; rebuild .pm/dashboard aggregate.

SKILL.md

3.1 KB, 751 tokens by cl100k_base, as published. Nobody here has run it

User Input

$ARGUMENTS

Flags: --skip-charter-gate, --modules=..., --path=..., --verbose.

Outline

Gate: .pm initialized? else block → recommend /pm-init.
Gate: new project without charter/outline? wait with choices: outline | charter | skip (--skip-charter-gate).
Run module scans (arch, engineering, env, api, test, release, db, ops, cost) then bugs if log sources/--path/paste exist; else skip bugs with recommendation.
- Architecture step must produce diagrams: run pm arch / /pm-arch → .pm/architecture/*.mmd + overview.md.
Merge findings/todos; write evidence/scans/pm-all-*.json.
Rebuild the dashboard (required):
- Prefer running: pm dashboard (from project root)
- Or regenerate .pm/dashboard/ yourself with the same contents described below
- Output files:
  - .pm/dashboard/index.html — visual KPI / charts / risk tables (open in browser)
  - .pm/dashboard/overview.md (and README.md mirror) — IDE tables: KPI, bars, module risk ranking, hot list, todos
  - .pm/dashboard/findings.md — all open findings across modules
  - .pm/dashboard/todos.md — all open todos across modules
  - .pm/dashboard/stats.json — machine-readable counts (+ health_score, module_risk)
- Purpose: one place to review health without opening each module folder
Chat summary: blocking+high + Top3 only unless --verbose.
Required closing: follow templates/commands/_closing.md — print Summary + Open these links (at least .pm/dashboard/index.html and overview.md; include .pm/architecture/overview.md after arch). Explicitly ask the user to open them.
Finish with /pm-status style health line.

Shared Workflow (all /pm-* commands)

Follow this order when the command mutates .pm/ state:

Read .pm/config/project.yaml and .pm/config/local.yaml (if missing and command is not init → recommend /pm-init).
On-demand scan using sources + extra_scan_roots + --path + conversation paste (highest priority for /pm-fix).
Desensitize evidence → .pm/evidence/scans/{command}-{timestamp}.json (secrets → ***).
Optional charter compare when charter.status != absent (attach confidence).
Incremental merge into module findings.md / todo.md; sync authoritative state/todo.md.
Refresh state/overview.md (include Today's Top3, max 3, blocking+high by default).
After multi-module updates (/pm-all, /pm-discover), rebuild .pm/dashboard/ via pm dashboard.
Output risk summary + recommended next step (≤20 lines). Never auto-write source/SQL/cloud without confirmation.
Closing (required): end the user-facing reply with Summary + Open these links per templates/commands/_closing.md (dashboard and/or architecture overviews). Ask the user to open them.