Pm fix
Know what to fix next — local .pm governance skill pack for AI coding agents (Spec Kit–inspired).
npx -y skills add wei63w/pm-manager --skill pm-fixAssembled 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
Analyze pasted logs/stacks/slow SQL from chat (or --path) into bugs findings and todos.
SKILL.md
1.9 KB, 424 tokens by cl100k_base, as published. Nobody here has run it
User Input
$ARGUMENTS
Outline
- Prefer current conversation paste as evidence; else
--path/ sources /.pm/inbox/stacks/. - Desensitize; write evidence JSON; optionally copy redacted snippet to inbox.
- Classify severity (blocking/high/medium/low/suggestion) per design rules.
- Append
bugs/findings.md+state/todo.mdentry with next action. - Charter compare for availability/success criteria with confidence.
- Summarize: severity, owner guess, estimate, suggested
/pm-donelater.
Do not modify application code unless user confirms.
Shared Workflow (all /pm-* commands)
Follow this order when the command mutates .pm/ state:
-
Read
.pm/config/project.yamland.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(attachconfidence). -
Incremental merge into module
findings.md/todo.md; sync authoritativestate/todo.md. -
Refresh
state/overview.md(include Today's Top3, max 3, blocking+high by default). -
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.
Design baseline: repo root pm-manager-v2.md (or packaged copy under memory/).