duolahypercho/fusion-fable

# Fusion

Fusion turns one prompt into a panel. The question goes to several models **at the same time**, each
answering independently — with web search and bash, and with no knowledge of the others. Then Opus 4.8
(this very session — the orchestrator) reads every answer, extracts the structure of the panel's reasoning
(what they agree on, where they conflict, what only one saw, what they all missed), and writes a final
answer grounded in that analysis.

The whole mechanism is **independence, then synthesis**. The diversity that makes a panel beat a single
model is harvested, not manufactured: running the same prompt independently yields different reasoning
paths, tool calls, and sources. So there are **no assigned "lenses" or personas** — every panelist gets the
user's task **verbatim** and answers it straight. (See `references/panel.md`.)

**One hard rule: Opus 4.8 always judges and writes the final answer — the pipeline can't be reversed.** The

# Fusion-Plan — OMC interview, then a 3-round iterative panel

This skill follows the **OMC plan system**: requirements are gathered by OMC's real interview FIRST, then
the fusion panel deepens the resulting plan, and the output flows back into OMC's review → execution
pipeline. The fusion panel replaces only the *plan-thinking* step; storage, format, the quality gate, and
execution all stay on OMC's rails.

**Hard rule (same as fusion): Opus 4.8 always judges and synthesizes. You are the judge — stay separate
from the panelists.** The Opus panelist is always a *spawned subagent*, never you.

## Step 0 — Requirements (pick the mode FIRST)

**Decide interactive vs non-interactive before doing anything — this determines whether you may interview.**