pstack for Claude Code 🤖 Agent Open source

What it does

pstack-claude, by Michael Denyer, ports Lauren Tan's pstack to agents other than Cursor. pstack is an opinionated stack of skills for getting concise, verified work out of a coding agent. You tell its poteto-mode entry point your goal, and it picks a playbook: for a bug it reproduces the failure, investigates, delegates the fix, and reruns the failing case so you get both failing and passing evidence. If a fix crosses a function boundary it brings in an architecture step first.

What is inside

The plugin bundles the poteto-mode router, playbooks for planning, features, refactoring, performance, investigations, prototypes, PR maintenance and shipping, and supporting skills such as how, why, architect, interrogate and unslop. Some Cursor primitives are translated into equivalents for each harness, and some skills from Cursor's team kit are included under their own licence. A setup-pstack command changes model defaults or turns automatic routing off. On Claude Code and Codex the plugin installs a routing hook; Codex asks you to trust it through /hooks first.

Works with

The README gives plugin installs for Claude Code and Codex, and points to shared skills-only instructions for OpenCode, Gemini CLI and Prime Agent. Cursor users should use the original pstack instead.

How to install

/plugin marketplace add michael-denyer/pstack-claude
/plugin install pstack@pstack-claude

codex plugin marketplace add michael-denyer/pstack-claude
codex plugin add pstack@pstack-claude

Maintenance and safety

MIT licensed with the original authors credited in separate licence and notice files, and pushed recently. It has a security policy and contributing guide. The weakness is that it is a port: its value depends on how closely it tracks upstream pstack, and the README itself is brief, pushing most detail into a reference doc.

Who should use it

Claude Code or Codex users who liked pstack's disciplined bug and feature playbooks in Cursor and want the same behaviour elsewhere. If you already use a different workflow pack, compare before stacking them.