claude-model-orchestrator

A Claude Code skill that implements a 3-tier model routing pattern:

| Tier | Model | When | |------|-------|------| | Orchestrator | Opus 4.8 | Analysis, architecture, frontend/backend design, decisions | | Executor | Sonnet 4.6 | Implementation, code writing, file edits, tests | | Mechanic | Haiku 4.5 | Mechanical tasks: imports, renames, boilerplate, DTOs |

Opus thinks. Sonnet builds. Haiku grinds.

How it works

1. Opus handles Phase 1 inline — no delegation. It reads the codebase, defines architecture, designs frontend/backend structure, and breaks work into tasks with exact file paths and acceptance criteria.
2. Sonnet handles Phase 2 — one fresh agent per task (or parallel agents for independent tasks). It receives pre-resolved context from Opus and executes without exploring.
3. Haiku handles Phase 3 — pure mechanical tasks where the rule is explicit and zero judgment is needed.

Critical rule

subagent_type: "fork"  →  inherits parent model  →  NEVER use for sub-agents
Agent({ model: "sonnet" })  →  Sonnet 4.6  ✓
Agent({ model: "haiku" })   →  Haiku 4.5   ✓

Install

npx claude-model-orchestrator

The installer will ask whether to install globally (~/.claude/skills/) or locally (.claude/skills/ in the current project). It also patches your CLAUDE.md automatically.

Manual install

1. Copy SKILL.md to ~/.claude/skills/claude-model-orchestrator/SKILL.md
2. Add this row to the Skills table in ~/.claude/CLAUDE.md:

| Multi-model orchestration, Opus+Sonnet+Haiku delegation | `~/.claude/skills/claude-model-orchestrator/SKILL.md` |

Usage

In any Claude Code session:

/claude-model-orchestrator

Or describe a task that involves planning + implementation — Claude will auto-load the skill when it detects the orchestration context.

Routing decision tree

New task arrives
│
├── Requires analysis/planning/design?
│   ├── Architecture, scope, decisions      → Opus inline
│   ├── Frontend design (components, state) → Opus inline
│   ├── Backend design (API, schema, modules) → Opus inline
│   └── Clear task breakdown ready?         → delegate below
│
├── Logic, context, judgment needed?        → Sonnet agent
│
└── Mechanical, zero-ambiguity, rule-based? → Haiku agent

Haiku task checklist

All must be true before routing to Haiku:

• Could a regex almost solve it?
• Zero business logic involved
• Output is deterministic given the input
• No need to understand surrounding context
• Failure is immediately obvious and cheap to fix

Examples: add imports, rename symbols, generate types from JSON, write DTOs, sort barrel exports, translate comments, apply naming conventions, generate unit tests for pure functions.

License

Apache-2.0