Each playbook is one lane, read left to right. Point at a step or a labelled connector and its details open in the panel on the right. Click to pin them; click again to release. Esc closes the panel. The address of the page records a pinned selection, so a link to it shares it. A step with no icon is done from the playbook's own text.

Understand or planBuildCheckCommit, PR, mergeRecordA human decides herenext step / loop backstarts a new passour inference, not stated in the playbooka decision on this connector; point at itprompt files the model reads (skills, playbooks, references)programs that run (scripts, CLIs, built-in commands)

Entry

How a request reaches a playbook

cursor/plugins @2f87c85

/poteto-mode

The human types /poteto-mode; the model matches the request to one of 22 titles and copies that playbook's steps into the todo tool. PR status and landing are separate requests.
How it is chosenthe model reads a list of titles; no code
"Match the task to a playbook and open its steps at playbooks/<title>.md, with the title in kebab case. Copy its steps into the todolist tool first. Large, cross-cutting, or unattended work, or a task no playbook fits, routes to the /figure-it-out skill."

figure-it-out (the fallback)

cursor/plugins @2f87c85

/figure-it-out · a skill, not a playbook

"When the task matches no playbook, design one. The deliverable before any code is the workflow itself."
Ends witha reply and a decision trail
Reply: the playbook you designed, the rigor level and why, the decision-trail path, what is verified against the predicate, and what is still open.

Understand

investigation

"You own the answer. Plan, route, write." Read-only: a cited explanation or a recommendation, not a code change.
Ends witha reply; no PR
Reply: the investigation output. For "are we sure?" answers, your real judgment with reasons; push back if the premise is wrong. "No PR, no babysit, no /architect unless the investigation precedes a code change."

Runtime forensics

cursor/plugins @2f87c85

runtime-forensics

"You own the diagnosis. Instrument the live process, don't theorize from source." The deliverable is a cited diagnosis, not a fix.
Ends witha diagnosis; no fix unless asked
Reply: the signal captured, the reduced finding, how you proved the mechanism, the source location, artifact paths. "Hand back to Bug fix or Perf once the cause is known."

trace-forensics

"You own the diagnosis from the artifact." The capture already exists: "read it, don't re-run it."
Ends witha diagnosis; no fix unless asked
Reply: the artifact and format, the reduced finding, the source location, the artifact paths, and whether a paired capture confirmed it. "Route to Bug fix or Perf issue once the cause is known."

Change code

bug-fix

"You own this task. Plan, review, verify." "Every shipped line traces to runtime evidence… When evidence refutes a hypothesis, revert what it motivated."
Ends withOpening a PR
Reply: what was broken, root cause, fix, how you verified. "Paste failing-then-passing repro output verbatim."

feature

"You own the design. Plan, review, verify." Delegate implementation; stay in the lead.
Ends withOpening a PR
Reply: what you built, what you chose and why, the throughput checkpoint, open decisions. Tables for design alternatives.

refactoring

"You own the contract. The structure changes. The behavior does not." A redesign routes to Feature; large structural work routes to /figure-it-out.
Ends withOpening a PR
Reply: the structure that changed, the pin you held it against, the equivalence proof, the reader-load delta, what shipped and what got reverted. No new behavior.

perf-issue

"You own the measurement story." "Tie every fix to a measurement, don't read source instead of measuring." Sustained improvement belongs to Hillclimb.
Ends withOpening a PR
Reply: baseline number, post-fix number, delta, artifact path.

hillclimb

"You own the metric and the experiment's integrity." For sustained improvement of one measurable thing. "One change, one measurement, keep or revert."
Ends withOpening a PR
Reply: the metric and target, baseline to final with the percent delta, iterations run (kept vs reverted), each accepted fix on one line, the decision.tsv path, and the best idea you would try next.

prototype

"You own the design decision, not the code. The prototype is a throwaway instrument." Speed over polish; no planning, no tests.
Ends witha decision; the real build follows Feature
Reply: the variants explored, the evidence, tradeoffs, your recommendation, and the scratch path. "Say plainly that the prototype is throwaway."

visual-parity

"You own pixel-exact equivalence. The baseline is the spec. You do not touch it." Equivalence is verified by image diff, not by eye.
Ends withOpening a PR per component
Reply: components migrated, the diff result for each, the baseline harness location, what is left.

Skills

Authoring a skill

cursor/plugins @2f87c85

authoring-a-skill

"You own the skill's voice." "When in doubt, delete. Keep only prose that changes a decision."
Ends withOpening a PR
Reply: summary of the skill, key design decisions, validation notes.

eval

"You own the experiment design. Plan, blind, run, synthesize." Candidates must not learn they are being tested.
Ends witha recommendation; no PR
Reply: variant under test, rubric, per-candidate notes, judge's verdict, your synthesis, and a recommendation for whether to promote the variant.

Pull requests

opening-a-pr

"Invoked at the end of every other playbook." Ends at an open, ready PR. " Opening a PR does not start a babysit."
Ends witha ready PR; no babysit
No Reply line. The PR body is the output: Why, What changed, Scope, Tradeoffs, Blast Radius, Verification.

babysit

"You own the merge frontier. Declare a mode, clear one PR at a time, stop where the human's call begins."
Ends withmerge-ready, never merged
No Reply line. "Owner approval is a wait. Babysitting never authorizes merging."

shipping

"You own what lands. Verify each PR independently, land only the verified run from the root, then keep your hands off the stack."
Ends withmerged PRs up to the ceiling
Reply: the verified run and its ceiling, each PR's verdict and who produced it, what landed and how you confirmed it, and what the next gap needs.

Long runs

Multi-phase plan

cursor/plugins @2f87c85

multi-phase-plan

"You own the plan, not the code. The plan is a checklist an owner runs box by box and the operator audits from the evidence." "The plan is the deliverable. Do not implement."
Ends witha plan file; waits for the operator
Reply: the plan path, the PR ids with their dependencies and the review-gated set, and what stays unproven.

autonomous-run

"You own the exit condition. Define done, then drive to it without stopping."
Ends withthe predicate met
Reply: the exit condition, iterations run, what landed, what was discarded, final predicate state.

autopilot-full

"You own the verdicts, never the PRs. One owner carries each PR from build to merge, and nothing merges until your swarm, which never wrote the code, has proven the code that lands."
Ends withowners merge verified PRs
Reply: catch the operator up per the /ketchup skill: each PR's state and verdict, what merged, countersigns and why, open operator gates, parked follow-ups, with links to each PR and the trails.

autopilot-stack

"Run the Autopilot-full playbook, but do not merge."
Ends withverified, unmerged PRs
Reply: list each PR with its verdict, in place of what merged.

Session

session-pickup

"You own the resume point. Read the prior trail, don't redo it."
Ends witha routed playbook
Reply: where the prior agent stopped, what you inherited vs redid (ideally nothing redone), the resume point, and the outcome.

pause-safely

"You own a clean stop. Leave a checkpoint a cold-start agent can resume from." Explicit only: on "keep going" or "don't stop", do not pause.
Ends witha pause, not a final report
Reply: where you are in the loop, what is on disk versus still in your head (paths, no diff dumps), the commits you made and whether the tree is clean, and the first action on resume.

Worktree cleanup

cursor/plugins @2f87c85

worktree-cleanup

"This is the one playbook that deletes user state with no code review to catch a slip, so the gates above are the review."
Ends withpruned worktrees; space reclaimed
Reply: df -h / before and after with space reclaimed, the worktrees pruned, and a one-line reason for each held back.

My reading