model-routinglisted

# Model Routing Choose the right model tier before starting a task. Overusing a capable model wastes cost and context. Underusing it produces lower quality on complex work. ## When to Use - Selecting a model for a new task or subagent - Deciding whether to escalate after a failed attempt - Designing a multi-agent pipeline with mixed task complexity ## Tier Definitions (vendor-neutral) | Tier | Typical examples | Task profile | |------|-----------------|--------------| | **Fast** | Haiku, GPT-4o-mini, Gemini Flash | Mechanical, deterministic, narrow | | **Standard** | Sonnet, GPT-4o, Gemini Pro | General implementation and review | | **Deep** | Opus, o1, Gemini Ultra | Architecture, security, root-cause, release | Use your provider's current recommended model for each tier. Do not hard-code model IDs in documentation or scripts; reference tiers instead. ## Routing Table ### Fast tier Use when ALL of: - Single file or single operation - Output is deterministic (rename, format, classify, generate boilerplate) - No ambiguity in the task description - Low blast radius on failure (easy to retry or revert) Examples: rename a variable, convert a data format, generate a changelog entry, classify issue severity. ### Standard tier Use when ANY of: - Multi-file change with known scope - Standard implementation task (add a feature, fix a bug, write tests) - Code review of a bounded change - Refactor with clear before/after contract This is the **default**. When unsure, use St