Prax Lannister
2.8 KiB
Set up pstack
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.
Install the plugin
Install from the checkout with an Agent Skills-compatible installer. With npx skills, run:
npx skills add ./pstack -g -y
Cursor users may instead install the bundled plugin adapter.
Pick your models
Run:
/setup-pstack
/setup-pstack detects models the current host can actually use, shows you each semantic role (code delegates, judgment, the review panels), and asks what you want. It writes ~/.config/pstack/models.md, a small config every model-routing skill can read.
You only override what you care about. A role with no line inherits the parent chat model. To restore that behavior later, delete the role's line, or just run /setup-pstack again.
Set a role to inherit-parent and pstack omits the subagent model field, so the subagent inherits your parent chat model. This value is not a model slug. 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.
Accept the verification offer, or don't
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 verify-<app>/ under the host-recognized project skill root, 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 when it earns its place.
After setup, start a new chat. The model configuration applies to new sessions.
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.