In this page you install the plugin, pick which models pstack uses, and run your first task. Setup is one command plus a short conversation.
In a terminal, run:
droid plugin marketplace add https://github.com/pstack-ports/droid-pstack
droid plugin install pstack@droid-pstack --scope user
Run:
/setup-pstack
/setup-pstack detects the models you have access to, asks for a reasoning budget, shows you each role (code delegates, judgment, the review panels), and asks what you want. Answer the questions. It writes the pstack-models section into ~/.factory/AGENTS.md, a small rule every pstack skill reads.
The defaults are the same as the large budget. The code seat runs at xhigh effort and the judgment seat runs at max. unlimited raises each seat one level, up to max. medium lowers each seat one level and small lowers it two, and both spend fewer tokens.
You only override what you care about. A role with no line in the rule keeps the skill's default. To restore a default, delete that role's line. A rerun of /setup-pstack keeps any role whose model differs from the default. When a default changes, a rule written before the change still pins the old default until you run /setup-pstack again. That run replaces the old defaults it recognizes, tells you which, and keeps your other choices. To drop a pin it does not recognize, delete that role's line or the section first.
You might be wondering what happens if you use Auto. Set a role to inherit-parent or auto and that role spawns the built-in worker droid, which inherits the parent chat model. Both values mean the same thing, and neither is a model ID. For a panel role the value is a list, and one subagent runs per entry, so the list length sets the panel size. Setup also configures swarm workers, the default model for every /swarm worker unless a race names a model for each arm.
At the end of setup, /setup-pstack looks for a way to prove app behavior in your project, either a verify-* skill or an existing harness. If it finds neither, it offers once to generate one with /create-verification-skill.
Say yes and it writes .factory/skills/verify-<app>/, a project-local skill that teaches agents to drive your app the way a user does. It proves the skill works once before handing it over. Say no and setup moves on. You can run /create-verification-skill yourself any time. Verify and ship covers it in depth.
If you're new to pstack, say yes. An agent that can check its own work keeps going until the check passes. An agent that can't hands every result back to you to check by hand. Of everything in this guide, the verification skill pays off the most.
Then setup offers once to generate a formal verification skill with /create-formal-verification-skill, unless the project already has one. Tests check the cases someone thought to write. A formal verification skill checks one key property of your code, such as "a job never runs twice at once", in every case within a stated scope. Say yes when your code has concurrency, retries, a state machine, or a parser, where a bug is costly and tests rarely reach the case that breaks. Otherwise say no, and run it later if that changes. Verify and ship covers it.
After setup, start a new chat. The model rule applies to new sessions.
pstack spends extra tokens on subagents and review panels. That's the price of the rigor. To spend fewer:
- Rerun
/setup-pstackand pick a smaller reasoning budget or cheaper models. A strong model in the main chat with cheaper, faster models in the code roles is a good split. - Set a role to
autoorinherit-parentso it runs on the chat's own model. - Shorten a panel list. Each entry runs one subagent.
- Save
/poteto-modefor work that needs rigor. A small, obvious edit doesn't.
Pick something real but small, and describe it the way you'd describe it to a colleague:
/poteto-mode add a --json flag to this command. text output stays byte-identical. verify both.
Watch the todo list. Its first items are the matched playbook's steps copied in, the Feature playbook for this prompt. If /poteto-mode skips a step, the step stays in the list with skip: <reason>, so you can see what it chose not to do.
From here you can type normal follow-ups. Droid attaches a skill to the message that names it, so start each new task with /poteto-mode.