Skip to content
  1. Wiki
  2. How pstack works
  3. The to-do list and skip

The to-do list and skip

The to-do list is the steps it writes down when it starts. Skipped steps stay on it, marked skip: with a reason.

An analogy

Like a pilot's pre-flight checklist. Every item is read out, and the ones that don't apply say why.

In pstack

Reading the list is the easiest way to keep an eye on the AI. Which approach it chose, which steps it plans, what it skipped: all at a glance. If it skipped something it shouldn't, say "don't skip step 3, make the problem happen again first".

The first items are the chosen playbook's steps, copied as-is. In Claude Code, it uses the TodoWrite tool if the session has one. If not, it writes the list in its reply and updates it at each stage.

Common misconceptions

  • "A longer list means more care": the length depends on the type of task. What matters is that no step gets skipped quietly.

Try it: Full guide step 3: Your first task

Related: Playbooks, /pstack:poteto-mode

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.