Setup pstack

Write ~/.claude/pstack-models.md and reference it from ~/.claude/CLAUDE.md, so pstack's per-role model choices apply to every session. The skills read it and fall back to their inline defaults when a line is absent, so this is an override layer, not a requirement.

Claude / Cowork note: This skill was ported from Cursor. Cursor stored the rule at ~/.cursor/rules/pstack-models.mdc (an "always-applied rule"). On Claude the equivalent is user-level memory: ~/.claude/CLAUDE.md. Keep the pstack mapping in its own file (~/.claude/pstack-models.md) and add one line to ~/.claude/CLAUDE.md importing it: @~/.claude/pstack-models.md. pstack skills spawn subagents with the Agent tool (subagent_type + model), not Cursor's Task tool — read "Agent" wherever the skills say Task.

Steps

1. Detect available models

Enumerate the model slugs you can pass to an Agent subagent in this session; that is the dependable source. 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 (or, on Claude, sonnet / opus / haiku as the friendly names) 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 ~/.claude/pstack-models.md already exists, read it and treat its values as the current choices. Otherwise start from those defaults.

3. Map and confirm

Show every role with its current model, marking any real slug not in the detected set as needing a choice. 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) as the options. Prefer AskUserQuestion over free text. For panel roles (how critics, 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. A rule pointing at a model the user cannot use breaks every delegation that reads it.

5. Write the rule

Write ~/.claude/pstack-models.md with one line per role, using the same labels poteto-mode uses. Overwrite the whole file so re-runs stay idempotent. Then ensure ~/.claude/CLAUDE.md contains the import line @~/.claude/pstack-models.md (add it once if missing). 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 Agent `model`). Alias entries in a panel list still count toward its fan-out.
# On Claude, valid friendly aliases are also: sonnet, opus, haiku.
feature, refactoring: sonnet
bug-fix: opus
perf-issue: opus
hillclimb: opus
judgment and prose: opus
hardest tasks: opus
how explorer: sonnet
how explainer: opus
how critics: opus, sonnet, haiku
why investigators: sonnet
why synthesizer: opus
reflect tooling: sonnet
reflect judgment, divergent, synthesizer: opus
arena runners: opus, sonnet, haiku
arena cross-judge pool: opus, sonnet, haiku
swarm workers: sonnet
architect runners: opus, sonnet, haiku
interrogate reviewers: opus, sonnet, haiku

The defaults above use Claude's own model family so the plugin works out of the box on Claude. If you have access to non-Claude models through your setup, you can substitute their slugs — pstack's multi-model panels benefit from mixing families where you can.

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)

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.