setup-pstack
name: setup-pstackdescription: Configure which models pstack uses per role and at what reasoning budget. Detects your available models and writes an always-applied rule that overrides the skill defaults. Use for /setup-pstack, "configure pstack models", "pstack budget", or changing pstack's model choices.Setup pstack
Section titled “Setup pstack”Write ~/.cursor/rules/pstack-models.mdc, an always-applied rule that sets pstack’s model per role.
1. Detect available models
Section titled “1. Detect available models”Enumerate the model slugs you can pass to a Task subagent in this session. That is the dependable source. If Cursor also exposes a models API or CLI that lists the user’s entitled models, prefer it for completeness. If you cannot detect any, ask the user to paste the slugs they have access to. Never write a real slug you have not confirmed is available. The aliases inherit-parent and auto are always valid even though they are not detected slugs.
2. Load current state
Section titled “2. Load current state”The default role-to-model mapping is the rule shape shown in step 5 below. If ~/.cursor/rules/pstack-models.mdc already exists, read it and treat its # budget line and its role values as the current choices. Otherwise start from those defaults. A line whose role is not in step 5, such as how explorer or why investigators, is from a retired role. Drop it.
A rule without the # defaults: 2 line comes from an older setup. That setup wrote a line for every role, so some of its values are old defaults, not choices. An old slug is one that matches grok-*. Before step 3, replace these values:
- An old slug in
feature, refactoring,bug-fix,perf-issue,hillclimb,reflect tooling, orswarm workerstakes the role’s step 5 default. - A
claude-opus-*value inhardest taskstakes the role’s step 5 default. - In a panel role (
arena runners,arena cross-judge pool,architect runners,interrogate reviewers), a list of exactly oneclaude-opus-*entry and one old slug, in either order, takes the role’s step 5 list. In any other list, each old slug becomesclaude-opus-5-5-high-fast.
Every other value is the user’s choice and stays, including an old slug in any other role and every inherit-parent or auto value. Tell the user which values you replaced.
3. Budget, map, and confirm
Section titled “3. Budget, map, and confirm”(a) Ask for a budget. Prefer AskQuestion over free text. Offer these four options with these exact labels, and name the current budget when the rule records one. With no rule, say that large matches the skill defaults.
unlimited — max reasoninglarge — xhigh reasoningmedium — high reasoningsmall — medium reasoning
(b) Apply it. Build the working table from the skill defaults, and on a re-run keep any role you changed by family, list, or alias (inherit-parent, auto). Families are the ones Phase A of the arena skill defines, so Fable is its own family. Each role has a target effort, which is its default’s effort moved by the budget. large keeps it, unlimited raises it one step, medium lowers it one step, and small lowers it two steps, on the ladder max > xhigh > high > medium > low. A target at either end of the ladder stays there. Most defaults are at xhigh, and each budget label names where those land. Set the effort token of every real slug in the role, panel entries included, to the role’s target. The effort token is the last token, or the one before a trailing fast. If the result is not a detected slug, use the same family’s detected slug with the highest effort at or below the target, else mark the role as needing a choice. inherit-parent and auto do not change. So unlimited turns claude-opus-5-5-xhigh into claude-opus-5-5-max and claude-opus-5-5-high-fast into claude-opus-5-5-xhigh-fast, and it keeps claude-fable-5-2-max. Gemini tops out at high, so under unlimited the fallback keeps gemini-4-carbon-high as it is. small turns the first two into claude-opus-5-5-medium and claude-opus-5-5-low-fast. Fable 5.2 and Gemini have no fast slug, so never write one.
(c) Show the roles and confirm. Show every role with its model, marking any real slug not in the detected set as needing a choice. Also list each line step 2 dropped. Ask whether to accept as-is or change specific roles, offering the detected models plus inherit-parent and auto (both mean: this role runs on the parent chat model, which is how Auto users stay on Auto) as the options. Prefer AskQuestion over free text. For panel roles (arena runners, architect runners, interrogate reviewers) the value is a list, and one subagent runs per entry, alias entries included, so the list length sets the count. arena cross-judge pool is also a list, but Arena runs one judge. It tries only values from a vendor other than the parent’s, in list order, so order it by preference. Fable and the other Claude models are one vendor. An inherit-parent or auto value never judges. swarm workers is the default model for every worker unless a race or comparison assigns another model per arm.
4. Validate
Section titled “4. Validate”Every real slug written must be in the detected set. inherit-parent and auto always pass. If a chosen real slug is not available, stop and ask again.
5. Write the rule
Section titled “5. Write the rule”Write ~/.cursor/rules/pstack-models.mdc with alwaysApply: true, the # defaults: 2 line, a # budget line with the chosen label and the effort that label names, and one line per role, using the same labels poteto-mode uses. Overwrite the whole file so re-runs stay idempotent. Shape:
---description: pstack per-role model choices (overrides skill defaults)alwaysApply: true---# pstack model configuration. One line per role. Delete a line to fall back to the skill default.# `inherit-parent` or `auto` as a value: the role runs on the parent chat model (omit Task `model`). Alias entries in a panel list still count toward its fan-out.# defaults: 2# budget: large (xhigh)feature, refactoring: claude-opus-5-5-xhighbug-fix: claude-opus-5-5-xhighperf-issue: claude-opus-5-5-xhighhillclimb: claude-opus-5-5-xhighjudgment and prose: claude-opus-5-5-xhighhardest tasks: claude-fable-5-2-maxreflect tooling: claude-opus-5-5-high-fastreflect judgment, divergent, synthesizer: claude-opus-5-5-xhigharena runners: claude-fable-5-2-high, claude-opus-5-5-high-fast, gemini-4-carbon-higharena cross-judge pool: claude-fable-5-2-high, claude-opus-5-5-high-fast, gemini-4-carbon-highswarm workers: claude-opus-5-5-high-fastarchitect runners: claude-fable-5-2-high, claude-opus-5-5-high-fast, gemini-4-carbon-highinterrogate reviewers: claude-fable-5-2-high, claude-opus-5-5-high-fast, gemini-4-carbon-high6. Confirm
Section titled “6. Confirm”Tell the user the rule was written and that it applies to new sessions. Re-running this skill updates it.
7. Offer a verification skill (optional)
Section titled “7. Offer a verification skill (optional)”Check whether the project has a way to drive the real app for proof (a verify-* skill, or an existing harness). If not, offer once: “want a project-local verification skill, so agents can drive the app the way a user does and prove changes work? I can generate one with /create-verification-skill.” On yes, invoke /create-verification-skill (resolves wherever pstack is installed: workspace, user, or plugin). On no, move on without pushing.
8. Offer a formal verification skill (optional)
Section titled “8. Offer a formal verification skill (optional)”Check whether the project already has a formal verification skill (a project skill that runs a model checker, a proof, or another verifier against the code). If not, offer once: “want a formal verification skill, so agents can prove a key property of your code holds in every case in scope, not only the cases tests reach? I can generate one with /create-formal-verification-skill.” On yes, invoke /create-formal-verification-skill (resolves wherever pstack is installed: workspace, user, or plugin). On no, move on without pushing.
