lauren
e8d856f027
* docs(pstack): port the September skill audit cuts from the internal tree Port of the 2026-09-01 to 2026-09-07 audit program on the internal skill tree. Deletion-only density cuts and the mannered prose pass applied wherever the OSS sentence is the same sentence. Two new principle leaves, Attack the Premise and Test Behavior Not Implementation, with their index lines. Critique mode removed from how and its callers. PR-body briefing rules in opening-a-pr and technical-writing. Model pins stay on the setup-pstack role mechanism. No internal path, slug, or name added. * docs(pstack): restore the autopilot chooser rule that multi-phase-plan cites multi-phase-plan step 4 picks between autopilot-full and autopilot-stack "per the rule at the end of playbooks/autopilot-stack.md". The density pass removed that paragraph and left the pointer dangling. Restore the paragraph verbatim. The chooser is a rule, not a restatement, and no other file states it. Addresses the Bugbot finding on PR #329. --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
2.7 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
In a Cursor chat, run:
/add-plugin pstack
Cursor confirms the plugin is installed.
Pick your models
Run:
/setup-pstack
/setup-pstack detects the models you have access to, shows you each role (code delegates, judgment, the review panels), and asks what you want. Answer the questions. It writes ~/.cursor/rules/pstack-models.mdc, a small rule every pstack skill reads.
You only override what you care about. A role with no line in the rule keeps the skill's default. To restore a default later, delete that role's line, or just run /setup-pstack again.
You might be wondering what happens if you use Auto. Set a role to inherit-parent or auto and pstack omits the subagent model field, so the subagent inherits your parent chat model. Both values mean the same thing, and neither is 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 .cursor/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 when it earns its place.
After setup, start a new chat. The model rule 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. 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. /poteto-mode is sticky. It stays on for the conversation until you opt out by saying so.