setup-pstack

# Setup pstack Read [runtime](../runtime/SKILL.md) for host-specific tools and paths. Write `~/.config/poteto-stack/models.md`, a shared configuration file that sets pstack's model per role. ## Steps ### 1. Detect available models Enumerate the model slugs you can pass to a subagent in this session. That is the dependable source. If the host 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 The default role-to-model mapping is the rule shape shown in step 5 below. If `~/.config/poteto-stack/models.md` 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 critics`, is from a retired role. Drop it. ### 3. Budget, map, and confirm **(a) Ask for a budget.** Prefer the host question tool over free text. Offer these four options with these exact labels, and name the current budget when the rule records one. With no rule, offer `large` as a request for `xhigh` where supported; unconfigured roles inherit the parent's model and effort. - `unlimited — max reasoning` - `large — xhigh reasoning` - `medium — high reasoning` - `small — 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`). `unlimited`, `large`, `medium`, and `small` request `max`, `xhigh`, `high`, or `medium` reasoning. Map that request to the highest supported effort at or below it; use the host default when no effort control exists and say so. Keep effort separate from model identifiers. `inherit-parent` and `auto` do not change. **(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 the host question tool 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 selects one value from it whose model family differs from the parent's when possible. `swarm workers` is the default model for every worker unless a race or comparison assigns another model per arm. ### 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 Write `~/.config/poteto-stack/models.md` with a `# budget` line with the chosen label and its target effort, and one line per role, using the same labels poteto-mode uses. Overwrite the whole file so re-runs stay idempotent. Shape: ``` # 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 the model override). Alias entries in a panel list still count toward its fan-out. # budget: large (xhigh) feature, refactoring: inherit-parent bug-fix: inherit-parent perf-issue: inherit-parent hillclimb: inherit-parent judgment and prose: inherit-parent hardest tasks: inherit-parent how explorer: inherit-parent how explainer: inherit-parent why investigators: inherit-parent why synthesizer: inherit-parent reflect tooling: inherit-parent reflect judgment, divergent, synthesizer: inherit-parent arena runners: inherit-parent, inherit-parent arena cross-judge pool: inherit-parent, inherit-parent swarm workers: inherit-parent architect runners: inherit-parent, inherit-parent interrogate reviewers: inherit-parent, inherit-parent ``` ### 6. Confirm Tell the user the rule was written and that the runtime skill reads it before choosing models. Re-running this skill updates it. ### 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.