Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Introduction: What pstack Is

pstack is a collection of skills that shapes how an AI coding agent works. Instead of improvising instructions in every prompt, it packages working methods as reusable files: 58 skills and 22 playbooks, all written as plain Markdown that an agent reads and follows.

A skill is a folder with a SKILL.md file that tells an agent how to carry out one kind of task. A playbook is a short, ordered procedure for one type of work, such as fixing a bug or opening a pull request. The next chapter explains how the two fit together.

About this book

This book is an independent reconstruction. It was written from the public pstack files in the pstack directory of the cursor/plugins repository at commit e58dd04 (full hash e58dd043600587dbaf58ba315e7f2b38373eeb43). The plugin manifest at that commit gives the version as 0.15.44.

Every fact in the book comes from those files: the README, the guide under docs/guide/, the skill and playbook definitions, the subagent definitions, and the automation pack. The book explains them in its own words and links each skill or playbook to its source file at that commit. pstack changes often, so a newer version may differ from what is described here.

pstack is released under the MIT License. The license file and the plugin manifest name Lauren Tan as the author. The README is written in the first person by an author who signs as “poteto” and gives the skills their names (poteto-mode, poteto-agent, poteto-help).

The problem pstack addresses

The README opens with a familiar complaint: AI agents tend to produce too much “slop”, code and prose that look plausible but carry little value. An agent can write a large diff quickly, yet every unverified line adds to the reviewer’s burden.

The author describes pstack as the set of skills used every day to ship code at Cursor, and states the guiding idea in one line: “if you want to go fast, go deep first.” The README also introduces the author as someone who has worked with millions of lines of code at Meta, Netflix, and Cursor, and who helps build and maintain React Compiler as a member of the React core team.

Three promises

The README makes three claims, each of which the rest of the book returns to.

  1. Less, but better, code. The goal is explicitly not to maximize lines of code. pstack aims for smaller changes of higher quality.
  2. Fearless parallelism. Once you can trust one agent to write good, verifiable code, you can run several agents at once with confidence. Quality is presented as the precondition for speed.
  3. Many models, each used for its strengths. pstack works with any model, and several skills deliberately send the same work to models from different vendors and compare the results.

Ideas that recur across the skills

Five ideas appear again and again in the skills, playbooks, and principles. Each corresponds to one or more of the 24 principle skills, which later chapters cover in detail.

  1. No evidence, no “done”. “It compiles” is not proof. The Prove It Works principle asks for verification against the real artifact: run the feature, read the actual value, inspect the diff. A result that is neither a pass nor a fail is reported as “inconclusive”, never rounded up to success.
  2. The author does not grade its own work. /poteto-mode treats a second opinion as “the same prompt on another vendor’s model”. Review panels mix vendors, and in the Autopilot-full playbook no owner merges a PR on its own verdict.
  3. Subtract before you add. Remove dead weight first, then build on the simpler base. When a new internal API replaces an old one, callers are migrated and the old API is deleted in the same wave.
  4. The human is not a bottleneck. Reversible work proceeds without asking; the human corrects course after seeing the result. Confirmation is reserved for irreversible actions such as a force-push to a shared branch, a deploy, data deletion, or a message to a customer.
  5. Lessons go into structure. When you notice yourself writing the same instruction a second time, encode it as a lint, a runtime check, a metadata flag, or a script instead of adding more text.

Who this book is for

The book assumes you use Cursor or Claude Code and want to hand larger tasks to an agent with less anxiety. Familiarity with Git, branches, and pull requests will help.

Read the next chapter, Overview and the four layers, before anything else. It gives you the map that the remaining chapters fill in.