Skip to content
Productivity
Skill

/thinking-model-combination

When one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.

From plugin
thinking-skills
1.7k28 skills

Claude Code

$ npx -y skills add tjboudreaux/cc-thinking-skills --skill thinking-model-combination --agent claude-code

SKILL.md

thinking-model-combination.SKILL.md
name: thinking-model-combination
description: When one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.
disable-model-invocation: true

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.

Procedure

1. **State the unknown and the gap.** Write the decision question. If one model already covers it, stop and use that model alone. Otherwise name the specific blind spot (e.g. "failure modes unexamined", "displaced alternative unknown"). 2. **Pick 2–3 models with distinct roles.** For each, record: model id, role (narrow / decide / stress / cost / …), and the unique question it answers. Drop any model that only rephrases another. Prefer sequential pipeline (narrow → stress → decide) over parallel unless independent concurrent checks are required. 3. **Lock the relation and conflict rule before applying.** Choose pattern: sequential, parallel, nested (macro→meso→micro), or adversarial (for/against). Predeclare the tiebreaker (e.g. reversibility class, evidence strength, ruin constraint, primary decision owner). Incompatible worldviews run sequential or adversarial — never blended. 4. **Apply each model fully for its role only.** Capture one key insight per model plus what only that model revealed. Do not re-run a model that adds no new insight. 5. **Synthesize once.** Record convergence, divergence, how the conflict rule resolves divergence, and a single combined recommendation with residual uncertainty. Stop when the recommendation is decision-ready or when further models would only reconfirm.

Output

problem: <decision question>
gap: <named blind spot justifying combination>
pattern: sequential | parallel | nested | adversarial
models:
  - id: <skill>
    role: <named job>
    unique_question: <what only this answers>
    insight: <key finding>
conflict_rule: <predeclared tiebreaker>
convergence: <where models agree>
divergence: <where they conflict + resolution>
recommendation: <single decision-ready answer>
stop_reason: gap_closed | single_model_suffices | budget

Verification

  • **Falsify / stop:** Remove a model only when it changes none of the recommendation, supporting evidence, confidence, residual risks, or mitigations; then re-synthesize with fewer. If no predeclared conflict rule exists and models disagree, do not average — pick one primary model or stop and re-route.
  • **Over-application guard:** Never exceed three models. Never add a model for thoroughness theater. If the first adequate single model already closes the gap, combination is wrong for this task.
Read more
@tjboudreaux
Ships withthinking-skills

28 portable Agent Skills for structured reasoning in Claude Code, GitHub Copilot, Codex, Cursor, and other compatible tools Claude Code Thinking Skills is a public catalog of Agent Skills.

Stars on GitHub

Momentum

stars in total
1.7k
Star history of tjboudreaux/cc-thinking-skills on GitHub, a chart by star-history.com

Other skills on thinking-skills.

More skills from other plugins.

i-have-adhd

i-have-adhd

Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…

@ayghri@ayghriInstall Skill
ab-test-analysis

ab-test-analysis

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop…

@phuryn@phurynInstall Skill
distilly

distilly

Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…

Questions about thinking-model-combination.

Which coding agents can use thinking-model-combination?
thinking-model-combination installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.