pstack, Mapped: One Command That Picks the Right Playbook pstack by poteto on one map: pick a type of work, see the steps /poteto-mode runs, how it differs from other skill sets, and when to use it.
pstack is Lauren Tan's (poteto) skill set that uses one command to pick the right process for
each coding task.
You only type /poteto-mode, because that command calls the other skills when they are needed.
What is pstack for?
pstack · by Lauren Tan (poteto)
Picks a process for each coding task and requires evidence that the result is correct, so you can run several agents in parallel.
You type one command with a description of the task. It picks a playbook and runs the skills each step needs.
Start with /poteto-mode <task>
How does pstack work?
Take a guess first
In the Bug fix playbook, when can a fix ship?
When the tests pass When it traces to runtime evidence When another model agrees
Every shipped line traces to runtime evidence. A fix without evidence is only a hypothesis.
Guess again
What do you need to do?
Explored 1/6
Build a feature Fix a bug Speed it up Understand the code Run overnight Find bugs in a diff
/poteto-mode
The Feature playbook
The agent names the data shape first and verifies the result on the product itself.
1 howUnderstand the affected subsystem 2 architectExplore designs in parallel 3 delegateA subagent writes the code 4 verifyVerify on the matching surface 5 interrogateSeveral models look for flaws in a contested design The Bug fix playbook
Every shipped line traces to runtime evidence.
1 reproduceThe agent reproduces it itself 2 how + whyBinary-search the cause 3 fixThe smallest fix the evidence justifies 4 verifyThe original repro now passes 5 tddThe failing repro lands before the fix The Perf playbook
The agent must tie every fix to a measurement.
1 baselineCapture a baseline trace 2 benchmark-checklistVet whether the number can be trusted 3 howGround the hypotheses 4 mantrasTries the cheapest option first, which is to drop work nothing uses The Investigation playbook
Read-only. The result is a cited answer.
1 howHow it works 2 whyWhy it was built this way 3 unslopStrips AI tells from the answer The Autonomous run playbook
You define a checkable exit condition, and the agent runs until it is met.
1 predicateA checkable exit condition 2 /loopRestarts the work on a schedule or event 3 show-me-your-workLogs every iteration Call /interrogate directly
No playbook needed. Any skill can be called on its own.
1 interrogateDifferent models try to break it, keeping only findings a run proves ▶ Play ← Back Next →
/setup-pstack sets which model plays each role.
How is pstack different from other skill sets?
When should you use pstack?
Use it when
✓ Hard work where quality matters more than speed
✓ You want to run many agents in parallel
✓ You use Cursor, or Claude Code with a few steps skipped
Skip it when
✕ Small work that needs little proof
✕ You need low costs, because many subagents and models use a lot of tokens
How do you start with pstack?
/plugin marketplace add cursor/plugins
/plugin install pstack@cursor-plugins
Choose pstack for hard work where proof matters more than speed. Run /setup-pstack once, then start your next task with /poteto-mode. On Claude Code, commands take a pstack: prefix, and pstack skips steps that need a Cursor-only feature.
References