--- name: opus-plan-sonnet-implement-workflow description: "User's required multi-model workflow — Opus plans, Sonnet reviews then implements" metadata: node_type: memory type: feedback originSessionId: 0b7c5f41-bb34-4ab4-93be-fdb363f5eb40 --- For non-trivial work (especially coding/debugging), route problem-solving and planning to an **Opus** session first, then hand that plan to a **Sonnet** session to review, then Sonnet implements. Dispatch decides automatically which model to use per step; Opus and Sonnet should work hand-in-hand. Trivial/quick asks don't need the full pipeline. **Why:** User explicitly requested this on 2026-06-25 — wants Opus's stronger reasoning for diagnosis/planning and Sonnet for review + implementation. Earlier, an Opus session repeatedly "verified" CSS fixes that were still broken on the real device, so plans should be reviewed before implementing. **How to apply:** Spin up an Opus session for diagnosis + a written plan (read-only, no git). Then a Sonnet session reviews the plan and implements it through the project's full protocol. Sequence sessions so they don't push to the same repo concurrently (git collisions). Relate to [[robco-uos-project]]. ⭐ **FABLE IS A FIRST-CLASS THIRD MODEL (owner 2026-07-11: "make sure the opus > sonnet handoff knows that Fable can be used as needed too").** The workflow is **Opus / Sonnet / Fable**, not a rigid two-model track. Fable is the DESIGN + CREATIVE model — reach for it whenever the work is generative/aesthetic rather than analytical or mechanical: - Visual/UI design + mockups (it authored the mockups the owner approved and the design overhaul was built from). - Diegetic/in-fiction writing: flavor text, POST lines, persona/greeting copy, ceremony beats, board names, the house voice. - Plain-English changelog prose and other owner-facing wording. - Any "what would the coolest RobCo-native version of this be?" exploration ([[design-overhaul-direction]]). Typical shape: **Fable designs → Opus audits/plans → Sonnet implements → Opus audits the diff.** Dispatch picks the model per stage and may switch mid-run — Fable slots in wherever design/creative judgment is the bottleneck, not just at the start. *Corrected 2026-07-20: stripped protocol numbers and a stale "fold this into CLAUDE.md" to-do. The three-model workflow is the owner's standing requirement and is unchanged; the model names are roles, not a lineup to keep current.*