/model Opus Plan Command

Route strategy to Opus, execution to Sonnet

By the end of this guide, you'll be splitting reasoning and execution across two Claude models in a single workflow — Opus for strategic thinking, Sonnet for repetitive output generation — so you get higher-quality planning without paying premium-model cost for routine execution work.

Who This Is For

• You run long Claude sessions where planning and repetitive execution happen in the same workflow

• You want Opus-quality strategy without paying Opus prices for routine output

• You're comfortable using slash commands in Claude Code or Claude sessions

What You'll Have

• The /model Opus plan command ready to paste into any session

• A two-model workflow: Opus handles strategy and reasoning, Sonnet handles execution and output

• Lower cost per session with no drop in planning quality

What You'll Need

• A Claude session (Claude Code or a plan-enabled Claude workspace) with access to both Opus and Sonnet

• A task that has a clear planning phase followed by repetitive execution

Going Further

— Guide: Claude Code Token Optimization Pipeline (AI Tools)

— Guide: Build Custom Claude Code Skills (AI Tools)

— Guide: Claude CoWork Quick Start (AI Tools)