Your First Week and a Glossary
The guide gives two pieces of advice about adoption. One is to “start smaller than you think”: prompt plainly, watch where agents fail, and add a skill or a check only when the same failure appears twice. The other is to earn trust before running a loop, because a loop you do not trust only produces unchecked work faster.
The week below is this book’s suggested order for building that trust. It is not a schedule from pstack itself, but every step uses a skill or playbook that pstack ships, and the sequence follows the guide: one supervised task first, a verification skill early, autonomous runs last.
Day 1: run one task with /poteto-mode
Run /setup-pstack, start a new chat, and turn /poteto-mode into a Custom Mode (Option+Enter or Alt+Enter from the / menu). Then run one real, small task while you watch. Give only the goal and the done check, and observe 2 things: the playbook’s steps appearing in the todo list, and the principle names in the replies. When it finishes, confirm for yourself that the evidence it shows is real. See Installation and setup and Using /poteto-mode.
Day 2: restate first, then investigate
Practice the restatement habit: ask /poteto-mode to restate a noisy report in its own words before it changes any code. Then pick a past bug and use the two investigation skills the guide pairs in its first recipe: /how for the mechanism, then /why for the history recorded in commits and PR discussions.
Try two small helpers on the same day. /bro restates the last message in plain language without jargon, and /sharpen deepens a prompt before you send it.
Day 3: create a verification skill
Run /create-verification-skill to generate verify-<app>, a project-local skill that launches your app, checks that the instance is healthy (its “doctor” step), drives features the way a user would, captures evidence, and cleans up. It also seeds a feature map with one file per user-facing feature. The generator runs the skill once end to end before handing it over; run it once more yourself and check that the evidence survives cleanup. The guide singles this skill out as the one that pays off the most, so the rest of the week depends on it. See Verification skills.
Day 4: daily work through playbooks
Route ordinary work (a bug fix, a feature, a PR) through /poteto-mode and let it pick the playbook. Ask /interrogate to review a diff: other models try to break it, and only findings that a run proves survive.
If you notice yourself correcting the same mistake again, run /correct. It groups repeated mistakes into classes and fixes each one at the strongest level that works: architecture first, then types, lint, or CI, then tests, and written rules last. Let /no-comments run before review; it spawns Comment Sicko and applies the accepted findings.
Day 5: parallel work and PR follow-through
Use /swarm for independent checks, for example one worker per package, and confirm that you receive one aggregated report. For an open PR, ask about its status and let the Babysit playbook drive it to merge-ready through conflicts, review threads, and CI. Give each parallel agent its own worktree or a cloud subagent, so that no 2 agents share a working tree.
Day 6: a short autonomous run
While you can still watch, start a short run under the Autonomous run playbook. State the exit condition as a checkable predicate, since the guide warns that a duration such as “work on this for 4 hours” gives the agent nothing to check. Confirm that /show-me-your-work writes one row per decision.
Then tell it to pause. Check that Pause safely leaves a wip: commit and a resume note, and that a fresh chat continues from that note through Session pickup.
Day 7: a queue overnight
Before leaving a loop alone, check the guide’s 4 conditions: you have done the task once or watched an agent do it, the agent has the tools you would use, every stage proves its work and can stop the line, and you have turned repeated failures from a few transcripts into tools, skills, or checks.
For a queue of independent changes, start with Autopilot-stack, which builds and verifies PRs but leaves the merging to you. In the morning, ask /show-me-your-work to catch you up and read its Attention section first, or run /ketchup for a quicker status. Move to Autopilot-full, which also merges, once you have reviewed a few Autopilot-stack mornings and trust the verdicts. Irreversible actions still require a pause in every mode. See Running work while you sleep.
Glossary
| Term | Meaning |
|---|---|
| slop | The README’s word for low-value AI output: code and prose that look plausible but add little. pstack’s answer is less, but higher-quality, code. |
/unslop, /deslop | /unslop (a pstack skill) cuts AI tells from writing. /deslop comes from the cursor-team-kit plugin and runs before a commit. |
| skill | A folder with a SKILL.md that tells an agent how to do one kind of task. pstack ships 58, 24 of them principles. |
/poteto-mode | The entry-point skill. It matches the task to a playbook, copies its steps into the todo list, and calls other skills as the steps need them. |
| playbook | One of 22 ordered procedures under skills/poteto-mode/playbooks/, each for one type of work. Playbooks are not slash commands. |
| principle | A skill named principle-* that states one rule, such as Prove It Works or Laziness Protocol. /poteto-mode names the principles behind its decisions, and you can name them to steer. |
| leaf | The full SKILL.md of a principle, as opposed to its one-line entry in the index inside /poteto-mode. |
| Custom Mode | A Cursor feature that keeps a skill in context on every turn. You enter it by choosing the skill with Option+Enter or Alt+Enter. |
| session override | A phrase such as “going to bed” or “run until done” that tells the agent to keep working without checking in. |
| role | A kind of delegated work (for example bug-fix, judgment and prose, swarm workers) that /setup-pstack maps to a model. |
| reasoning budget | The large, medium, or small setting in /setup-pstack. It lowers each role’s effort level by 0, 1, or 2 steps. |
| panel | A list role, such as interrogate reviewers, where one subagent runs per entry. The default panel mixes Fable 5.2, Opus 5.5, and Gemini 4 Neon. |
poteto-agent | The subagent type for delegates in a /poteto-mode run. It reads poteto-mode in full before any work. |
| operator | In worker.md, the person the whole run works for, as distinct from the agent that wrote a worker’s kickoff. |
| Comment Sicko | A read-only subagent that flags comments for deletion and marks code that needs a comment to be understood as MUST KILL. /no-comments spawns it. |
| verification skill | A project-local verify-<app> skill made by /create-verification-skill. It launches the app, checks its health, drives features as a user would, and captures evidence, guided by a feature map. |
| formal verification skill | A project-local skill made by /create-formal-verification-skill that checks one property in every case within a stated scope, using whichever verification tool fits. |
| inconclusive | A verdict that is neither a pass nor a fail. Playbooks state that inconclusive is not a pass, and /benchmark-checklist uses it when it cannot name what limits a number. |
| decision log | The TSV file kept by /show-me-your-work, one row per decision, with columns for timestamp, phase, decision, reason, evidence pointer, and result. |
/ketchup | A read-only catch-up on what changed in the chat since your last message, ending with every decision waiting on you. |
/swarm | Runs N parallel workers across different slices or races and returns one aggregated report. |
/arena | Runs N parallel attempts at the same task, picks a base, and grafts the strongest parts of the other attempts into it. |
/interrogate | Asks different models to break a change or design and keeps only findings that a run proves. |
wip: commit | The checkpoint commit that the Pause safely playbook makes so that unfinished work is not lost. |
| worktree | A separate Git working tree of the same repository. pstack uses one per task or agent so parallel work does not collide. |
| benny | A dormant automation pack for Slack issue reports, with one automation for triage and one for reproducing confirmed bugs and drafting small fixes. It runs only on Cursor Automations. |