Skip to content

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.

Tuan Tran Van
1 min read
Contents (6 sections)
  1. What is pstack for?
  2. How does pstack work?
  3. How is pstack different from other skill sets?
  4. When should you use pstack?
  5. How do you start with pstack?
  6. References

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.
23
playbooks
34
situational skills
24
principles
1
command to start
Start with /poteto-mode <task>

How does pstack work?

Take a guess first
In the Bug fix playbook, when can a fix ship?
What do you need to do?
Explored 1/6
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
/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?

bash
/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

Check yourself

Three quick questions to see whether the main ideas stuck.

  1. How does pstack organize its processes?
  2. In the Bug fix playbook, what must every shipped line have?
  3. What happens to a step needing a Cursor-only feature on Claude Code?

Share this article