The pstack guide

Source

This page reprints the English original.

pstack/docs/guide/README.md (cursor/plugins 12d587d).

中文页

The pstack guide

pstack works best when you stop micromanaging the agent. You describe what you want and how you’ll know it’s done. /poteto-mode picks the playbook, runs the other skills as the steps need them, and shows you the evidence. This guide teaches that habit with realistic prompts.

Here’s what you’ll learn:

1. Set up pstack. Install the plugin and pick your models.
2. Route work through /poteto-mode. Give it a goal and watch it pick a playbook.
3. Understand the code. /how, /why, /teach, and /recall before you edit anything.
4. Design the change. /architect, /arena, /swarm, and /interrogate before code locks in a shape.
5. Build and clean the change. The build playbooks, /tdd, /unslop, and /no-comments.
6. Verify and ship. Prove behavior on the real app, then open a focused PR and drive it to merged.
7. Run work while you sleep. An overnight contract, a decision log you can audit, and the playbooks that scale past one agent.
8. Steer with principle names. The 23 names that redirect an agent mid-task.
9. Make it yours. Your own mode, plus how to test a skill change.
10. Recipes and pitfalls. Prompts to copy and mistakes to skip.

Read the pages in order the first time. After that, each page stands alone.

If you only remember one thing

Give the agent a goal and a way to check it, in your own words:

/poteto-mode the export writes duplicate rows when a retry lands mid-run. repro first, then fix and verify.

You don’t need to name a playbook or list skills. “repro first” and a checkable outcome are all the routing signal /poteto-mode needs. It matches the Bug fix playbook, copies the steps into a todo list, and calls the right skills as each step fires.

Next: Set up pstack.