thinking-model-router

1# Model Router
2 
3**Core rule:** Prefer NONE or one primary skill. Route by mechanism fit, not habit. Combine only when roles are distinct and necessary.
4 
5## When to Use
6 
7- The right thinking skill is unclear and you would otherwise guess or stack tools.
8- Several catalog skills seem plausible and you need a single primary (or explicit NONE).
9- High-stakes work where a wrong frame is costly and a quick domain×type match helps.
10 
11## When NOT to Use
12 
13- The match is already known or obvious ("where's the bottleneck?" → theory-of-constraints) — invoke that skill directly; do not route for show.
14- The task is routine implementation with no analytical unknown — reason directly (NONE).
15- You are mid-execution of an agreed plan and only need the next concrete step.
16- The ask is outside this catalog (pure coding syntax, tool ops with no judgment call) — NONE.
17 
18## Invoking a Model (Skill IDs)
19 
20The router outputs bare slugs (e.g. `id: five-whys-plus`). Invoke a routed skill with the Skill tool using the exact ID `thinking-skills:thinking-<slug>` — never invent a slug not cited in Procedure. `NONE` means no invocation.
21 
22## Procedure
23 
241. **Short-circuit.** If one skill clearly fits by mechanism, return that skill alone. If no skill clearly improves the work, return **NONE** and reason directly. Stop.
25…