Skip to content

fix(pstack): bug-fix/perf/hillclimb defaults to grok 4.6 - #365

Merged
poteto merged 4 commits into
mainfrom
benny/pstack-grok-defaults-dcfb
Sep 12, 2026
Merged

fix(pstack): bug-fix/perf/hillclimb defaults to grok 4.6#365
poteto merged 4 commits into
mainfrom
benny/pstack-grok-defaults-dcfb

Conversation

@poteto

@poteto poteto commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator

Why

Lauren asked for the bug-fix, perf-issue, and hillclimb roles to default to Grok 4.6 in /setup-pstack, and for the defaults printed in the individual playbooks to match. These three roles are code delegates. Feature and refactoring already run on grok-4.6-fast-xhigh, so this PR points the three remaining code roles at the same slug.

Judgment and prose, hardest tasks, the how explainer, the why synthesizer, reflect judgment, and the arena, architect, and interrogate panels stay on claude-fable-5-1-thinking-max. The grok slug rename discussed in #336 is out of scope. The plugin version stays at 0.15.2.

Scope

  • pstack/skills/setup-pstack/SKILL.md. Rule template lines bug-fix, perf-issue, hillclimb move from claude-fable-5-1-thinking-max to grok-4.6-fast-xhigh.
  • pstack/skills/poteto-mode/playbooks/bug-fix.md, perf-issue.md, hillclimb.md. The (default ...) annotation on each delegate step moves to grok-4.6-fast-xhigh.
  • pstack/README.md. The get-started blurb said precisely-specified code goes to fable and only fast mechanical code goes to grok. It now lists the five code roles (feature, refactoring, bug fix, perf, hillclimb) on grok and keeps the hardest changes, prose, and judgment on fable 5.1. One sentence changed.
  • pstack/docs/guide/** is unchanged. The guide never names fable or grok for these roles.

Blast Radius

Users without a ~/.cursor/rules/pstack-models.mdc line for these roles get Grok 4.6 delegates on their next bug fix, perf fix, or hillclimb attempt. Users with a role line already written keep their choice. Nothing else in the plugin reads these lines.

Verification

  • rg -n 'bug-fix:|perf-issue:|hillclimb:' pstack/skills/setup-pstack/SKILL.md shows grok-4.6-fast-xhigh on all three lines.
  • rg -n 'configured (bug-fix|perf-issue|hillclimb) model \(default' pstack/skills/poteto-mode/playbooks/ shows grok-4.6-fast-xhigh for all three playbooks.
  • rg -n 'claude-fable-5-1-thinking-max' pstack/skills/poteto-mode/playbooks/{bug-fix,perf-issue,hillclimb}.md returns no matches.
  • rg -n -i 'fable|grok' pstack/README.md pstack/docs matches only the corrected blurb and the unrelated /make-bot-ui row.
  • git diff main --stat lists five files and no plugin.json.
  • node scripts/validate-plugins.mjs after npm install --no-save ajv ajv-formats prints "All plugins validated successfully."
Open in Web Open in Cursor 

cursoragent and others added 4 commits September 12, 2026 05:25
Point the three code-delegate roles at grok-4.6-fast-xhigh, the slug feature and refactoring already use. The setup-pstack rule template and the playbook default annotations now agree. Judgment, prose, hardest tasks, explainers, synthesizers, and panels stay on Fable 5.1.

Co-authored-by: lauren <poteto@users.noreply.github.com>
Co-authored-by: lauren <poteto@users.noreply.github.com>
The get-started paragraph said precisely-specified code goes to fable 5.1 and only fast mechanical code goes to grok. Bug fix, perf, and hillclimb now default to grok with feature and refactoring, so the blurb lists the five code roles on grok and keeps the hardest changes, prose, and judgment on fable.

Co-authored-by: lauren <poteto@users.noreply.github.com>
@poteto
poteto merged commit 889ec4b into main Sep 12, 2026
1 check passed
@poteto
poteto deleted the benny/pstack-grok-defaults-dcfb branch September 12, 2026 05:40
github-actions Bot added a commit to SmailG/claude-cursor-plugins that referenced this pull request Sep 12, 2026
… defaults to grok 4.6 (cursor#365)

chore: sync with cursor/plugins — fix(pstack): bug-fix/perf/hillclimb defaults to grok 4.6 (cursor#365)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants