Sous Chef

🧑‍🍳 sous-chef

Fable 5 orchestrates and reviews; Sonnet 5, GPT-5.6, GLM 5.2, or Grok 4.5 implements. Your head chef doesn't chop onions.

A Claude Code plugin that splits coding between two frontier models the way a kitchen
splits work. Fable plans, writes the ticket, reviews every diff line by line, and
re-runs the checks itself. Sonnet, Codex, GLM, or Grok does the implementation, with
no say over what ships. The split is economic:
Fable is the most expensive model on the line, so its tokens go to judgment and
worker tokens go to bulk. In the measured setup this pattern is built on,
Codex did ~20x the implementation work
per orchestration round trip, and two mid-tier subscriptions often beat one top-tier one.

What it looks like

Codex saying "tests pass" is a sentence; pnpm test output is a fact - Claude
re-runs everything itself.

Two commands

/sous-chef:serve is for task-shaped work, done end to end: implement,
cross-review, fix the findings, verify. One announcement up front, one report at the
end, a hard budget of five Codex runs in between. This is the daily driver.

/sous-chef:simmer is for goal-shaped work, looped until a command passes:
"make the suite green", "get the benchmark under 200ms". A fresh Codex run each lap,
Claude judging every lap with real command output, on a dedicated branch, with lap
caps and no-progress detection. The worker never grades its own homework.

Rule of thumb: serve a task, simmer a goal. If a serve runs out of budget and
what remains is goal-shaped, it offers to continue as a simmer.

À la carte, when you want to drive the stations yourself:

Install

Requirements: Codex CLI ≥ 0.134,
authenticated (codex login - a ChatGPT subscription is enough; no API key needed).

(sous-chef@sous-chef is plugin@marketplace - same name for…