SKILL.md
Model Combination
Core rule: Combine only when each model answers a different named question. Cap at three, name the conflict rule before applying, then synthesize once.
When to Use
- One model already applied (or clearly primary) still leaves a material blind spot that another mechanism covers.
- Problem spans domains (e.g. risk + choice + system structure) and stakes justify multi-lens work.
- You need independent checks, not confirmation of the same conclusion.
- You can name a distinct role per model before running them.
When NOT to Use
- A single catalog skill fully answers the unknown — apply that skill alone.
- Routine, local, or fully reversible work where multi-lens cost exceeds upside.
- You cannot state what unique question each extra model answers (checkbox / model soup).
- Near-duplicate mechanisms (two diagnosis skills that ask the same causal question).
- Time budget cannot support genuine synthesis — prefer one honest model over contradictory partials.