mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
lauren
424829e3e0
* docs(pstack): complete the poteto-mode route map The guide's route paragraph predates the autopilot playbooks, so a reader browsing routes never learns a PR queue can run on autopilot. Add that route, and give worktree cleanup a prompt in the section that tells readers to fan out worktrees in the first place. Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): teach /no-comments and Comment Sicko in the cleanup chapter The cleanup habit covered /deslop and /unslop but not the comment pass, so readers never met Comment Sicko or the constraint-encoding offer. Add the before-review step and state the deslop / unslop / no-comments division of labor. Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): cover Babysit and Shipping after the PR opens The chapter ended at opening the PR and a note claiming pstack bundles no PR monitoring. That note is stale: Babysit ships with the watch-pr watcher and Shipping lands verified stacks through Graphite merge-when-ready. Replace it with the two playbooks, their prompts, and the merge-ready versus land distinction. Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): teach the autopilots and orchestrate in the overnight chapter The chapter covered one task per night and nothing bigger, so the queue and program playbooks had no home in the guide. Add autopilot-full, autopilot-stack, and orchestrate with prompts and the rule for choosing between them. Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): introduce /technical-writing and /bro in the later chapters Both skills shipped without a guide mention. /technical-writing sits with skill authoring, where readers already write prose that agents and humans consume. /bro joins the recipes as the one-word prompt for a jargon-free restatement. Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): technical-writing pass over the new guide prose Fixes traced to the skill's rules. Split sentences carrying two or three thoughts (STE). Moved 'only' next to what it changes and gave the merge-ready heading a real subject instead of 'it' (Global English). One name per thing: uncommitted work, Autopilot-full, verdict instead of say-so. Replaced unglossed jargon with plain words: 'drains completions' and 'merge frontier' now say what the coordinator does, 'the real surface' is now 'proves the behavior live'. Co-authored-by: lauren <poteto@users.noreply.github.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
The pstack guide
pstack works best when you stop micromanaging the agent. You describe what you want and how you'll know it's done. /poteto-mode picks the playbook, runs the other skills as the steps need them, and shows you the evidence. This guide teaches that habit with realistic prompts.
Here's what you'll learn:
- Set up pstack. Install the plugin and pick your models.
- Route work through
/poteto-mode. Give it a goal and watch it pick a playbook. - Understand the code.
/how,/why,/teach, and/recallbefore you edit anything. - Design the change.
/architect,/arena,/swarm, and/interrogatebefore code locks in a shape. - Build and clean the change. The build playbooks,
/tdd,/unslop, and/no-comments. - Verify and ship. Prove behavior on the real app, then open a focused PR and drive it to merged.
- Run work while you sleep. An overnight contract, a decision log you can audit, and the playbooks that scale past one agent.
- Steer with principle names. The 21 names that redirect an agent mid-task.
- Make it yours. Your own mode, plus how to test a skill change.
- Recipes and pitfalls. Prompts to copy and mistakes to skip.
Read the pages in order the first time. After that, each page stands alone.
If you only remember one thing
Give the agent a goal and a way to check it, in your own words:
/poteto-mode the export writes duplicate rows when a retry lands mid-run. repro first, then fix and verify.
You don't need to name a playbook or list skills. "repro first" and a checkable outcome are all the routing signal /poteto-mode needs. It matches the Bug fix playbook, copies the steps into a todo list, and calls the right skills as each step fires.
Next: Set up pstack.