Set up pstack
August 25, 2026 · View on GitHub
In this page you install the plugin, pick which models pstack uses, and run your first task. Setup is one command, then the Settings page if you want per-role routes.
Install the plugin
In DSH, run:
dsh plugin add github:aa2246740/pstack-dsh
Reload the DSH Web page after install so the client half can register.
Pick your models
Open Settings (sidebar gear) → pstack (nav pstack 角色 / pstack roles).
The page lists only logged-in DSH routes. Save writes $DSH_HOME/pstack-dsh.json. A missing file means every role inherits this conversation.
You only override what you care about. A role left as inherit-parent keeps the parent route. auto means the same inherit. For a panel role the value is a list, and one subagent runs per entry. Setup also configures swarm-workers, the default route for every /swarm worker unless a race names a selectable catalog route for each arm.
/setup-pstack is a pointer to that page. It is not a TUI editor.
If the project has no way to prove app behavior, you can generate one with /create-verification-skill. Verify and ship covers when it earns its place.
New pstack_spawn calls pick up the overlay in this session.
Run your first task
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. The first item is always "read the Principles section". The rest 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. /poteto-mode is sticky. It stays on for the conversation until you opt out by saying so.