Skip to content
  1. Wiki
  2. How pstack works
  3. /pstack:poteto-mode

/pstack:poteto-mode

/pstack:poteto-mode is the main entry point. You say what you want; it plans the steps and does the work.

An analogy

Like an experienced project manager. They repeat the request back, pick the right process, and only hand it over after checking.

In pstack

Its first reply repeats what you want and the problem you're solving. It also names the smallest change it expects. It doesn't wait for your OK before carrying on. If it misread you, interrupt right away.

After that, "continue" or "go ahead" is enough, and it keeps going. In Cursor, you can also set it as a Custom Mode so it stays on.

Common misconceptions

  • "Use it for everything": the author says save it for work that needs rigor. For a one-line text change, just ask.
  • "I need to write long requirements": you don't. One sentence each: what you want, what counts as done, and any leads.
  • "It'll ask me a pile of questions first": if running something can answer it, it tries a quick test. It only asks you when it needs your call.

Try it: Full guide step 3: Your first task

Related: Playbooks, The to-do list and skip, The 24 principles, Custom Mode (always on)

An unofficial beginner's guide to pstack, not its official docs. pstack is made by poteto; the official repo is the source of truth for commands and behavior. The original guide source is on GitHub.

Hosted by airali. Adapted from Xiaoxiaodong's MIT-licensed guide.