model-gear-routerlisted

# model-gear-router Most people pick a model once, at the start of a session, and then run everything through it — research, bulk edits, code, review. That is one setting doing five jobs. This skill replaces it with an **orchestrator layer** that picks a model per task, the way you would assign work to different people. You are not choosing a favourite model. You are choosing a **gear**. --- ## 1. A gear is two dials, not one | Dial | What it is | Who sets it | |---|---|---| | **TIER** | Horsepower — `(model, effort)`. Keep this to a handful of levels. | The harness, on dispatch | | **MISSION** | The verb — what the worker is *told to do*. | Your prompt | Two gears can share a tier and still behave completely differently, because the mission is injected as orders, not as a setting. **Same engine, different instructions** is a real difference in output, and it is the dial most people never touch. Name your gears. A named gear is a job class you can say out loud — "send that one to the red-team gear" — instead of a model string you have to remember and retype. --- ## 2. Pick the mission first, then the tier follows Write down your verbs before you write down your models. A workable starting set: | Mission | What it means | Typical tier | |---|---|---| | **grind** | Bulk mechanical work — reformat, extract, rename across many files | cheapest · low effort | | **quick** | Small standard task where minimal effort is correct | small · low | | **build** | Standard impleme