Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automagik-dev/pm
Full PM playbook — triage backlog, prioritize, assign, track, report, escalate. Copilot, autopilot, or pair modes.
Passed 16 of 20 test cases with the skill, and 7 of 20 without it.
and 10 more in the full report
10 fixed8 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
The requirements for adding dark mode are fully finalized and clear. Which routing step should be dispatched to convert this clear scope into per-group tasks?
| Checked | Without skill | With skill |
|---|---|---|
| Routes planning to the wish skill. | Missed | Passed |
The instructions your model reads when the skill loads.
Runtime syntax: invoke the plugin copy through the active runtime's owner-qualified skill selector; use a bare selector only when intentionally selecting a user-tier copy (a separately installed personal copy; Genie no longer seeds this tier). Cross-skill prose below uses bare names as portable semantic routes; the orchestrator resolves the selector for the active runtime.
Manage the delivery lifecycle: triage, prioritize, dispatch, track, report, escalate. The PM orchestrates — it never writes code. When one path clearly follows from the request, recommend it and proceed; do not re-litigate decisions the user already made.
Pick the mode from who makes decisions; switch when that changes.
| Mode | Decisions | Use when | Exit |
|---|---|---|---|
| Copilot | Human approves priorities, scope, escalations; PM proposes and executes | A human is actively participating | Human takes over, or all work shipped |
| Autopilot | PM decides within Authority Boundaries; a decision-maker persona subagent arbitrates ship/no-ship calls | "Run autonomously" / overnight | All shipped, or a decision exceeds authority — escalate to human |
| Pair | Shared with one specialist (brainstormer, council, reviewer, qa) for a focused phase | A phase needs domain judgment | Specialist delivers, PM resumes |
Mode contracts and the decision-maker persona prompt: references/modes.md.
The lifecycle is owned by its skills — route to them, never restate them here:
| Phase | Skill | PM's job |
|---|---|---|
| Triage | — | Prioritize; decide what enters the pipeline |
| Explore | brainstorm | Dispatch when scope is fuzzy |
| Plan | wish | Dispatch when scope is clear; the wish creates per-group tasks |
| Execute | work | Dispatch orchestration; waves come from WISH.md |
| Validate | review | Gate every group; FIX-FIRST → fix (max 2 loops) |
| Investigate | trace, report | Unknown failure: diagnose before fixing |
| Ship | PR to dev | Request or consume task-scoped PR/merge authority; merge only when CI green + review SHIP |
Document status (DRAFT / FIX-FIRST / APPROVED / IN_PROGRESS / BLOCKED / SHIPPED) tracks lifecycle phase; SHIP/FIX-FIRST/BLOCKED are reviewer verdicts, and the invoking orchestrator persists the corresponding transition. The task DB tracks per-group execution state.
test cases passed, vs 7 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.