Skip to content

feat(orchestrate): pin orchestration brain to Opus via skill model field#65

Merged
produtoramaxvision merged 1 commit into
mainfrom
feat/orchestrate-pin-opus
May 31, 2026
Merged

feat(orchestrate): pin orchestration brain to Opus via skill model field#65
produtoramaxvision merged 1 commit into
mainfrom
feat/orchestrate-pin-opus

Conversation

@produtoramaxvision
Copy link
Copy Markdown
Owner

@produtoramaxvision produtoramaxvision commented May 31, 2026

Summary

Pin the orchestration brain to Opus regardless of session model by adding model: opus to the orchestrate skill frontmatter (1 line).

When the session runs on Sonnet, the orchestration reasoning (routing, judging, approval gates, dispatch decisions) now always runs on Opus — across both activation surfaces (/maxvision:orchestrate slash command and when_to_use auto-activation).

Why this, not a subagent

The original idea was to convert the skill into a subagent to pin the model. That breaks the core function: subagents cannot spawn subagents (no-nesting rule), and the orchestrate flow's Phase 8 dispatches specialist subagents. Keeping it a main-thread skill with model: opus achieves the model pin while preserving dispatch.

Scope

  • Pinned to Opus: the main-thread orchestrator brain only.
  • Unaffected: dispatched specialists — analyze-candidates still selects model per task (sonnet/haiku/opus). Per-task cost optimization is preserved.

Changes

File Change
skills/orchestrate/SKILL.md + model: opus in frontmatter

No version bump (stays 0.1.2). test_orchestrate_anti_skip_wiring passes (3/3).

@codex @copilot @CodeRabbit — please review.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated orchestrate skill to use the Opus model.

Copilot AI review requested due to automatic review settings May 31, 2026 01:04
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 31, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 40c0e97f-03a5-4707-a237-cdc8eb673427

📥 Commits

Reviewing files that changed from the base of the PR and between 53a8d7f and 4ac1bc2.

📒 Files selected for processing (1)
  • skills/orchestrate/SKILL.md

📝 Walkthrough

Walkthrough

The orchestrate skill's frontmatter configuration is updated to explicitly set model: opus, specifying which language model the skill targets during execution.

Changes

Orchestrate Model Configuration

Layer / File(s) Summary
Orchestrate skill model configuration
skills/orchestrate/SKILL.md
Frontmatter updated to specify model: opus for the orchestrate skill, directing runtime execution to the Opus model.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A whisker-twitch, a model declared,
Opus now leads where choices are shared,
One line of skill, orchestration refined—
The rabbit's touch keeps flows aligned! 🐰✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly describes the main change: pinning the orchestrate skill to use the Opus model via the skill model field, which matches the single-line addition of model: opus to the skill frontmatter.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/orchestrate-pin-opus

Comment @coderabbitai help to get the list of available commands and usage tips.

Add `model: opus` to the orchestrate skill frontmatter so the orchestration
reasoning (routing, judging, approval, dispatch decisions) always runs on
Opus regardless of the session model — including both the `/maxvision:orchestrate`
slash command and `when_to_use` auto-activation paths.

Dispatched specialist subagents are unaffected: analyze-candidates still
selects model per task (sonnet/haiku/opus). This pins only the main-thread
orchestrator brain. The skill remains main-thread, so subagent dispatch
(Phase 8) is preserved — unlike converting it to a subagent, which the
no-nesting rule would break.

No version bump (stays 0.1.2).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep them coming!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@produtoramaxvision produtoramaxvision merged commit 24f1ed1 into main May 31, 2026
16 of 17 checks passed
@produtoramaxvision produtoramaxvision deleted the feat/orchestrate-pin-opus branch May 31, 2026 01:09
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