fusion-review

name

fusion-review

description

Run a pi-fusion review: several models answer in parallel, then one synthesis step returns a single report. Use when the user says "invoke fusion", "run a fusion panel", "discuss this through fusion", "get multi-model opinions", "panel review", "compare <model> and <model> on this", or asks to cover something from several angles ("what did we miss", "audit this release"). Call the start_fusion_review tool with the topic. NOT for routine edits, formatting, or one-step fixes. NOT for arguing one claim from both sides (use dialectic) and NOT for open-ended idea generation (use brainstorming) — Fusion panelists work independently and never talk to each other.

Fusion Review

Call start_fusion_review so the user does not have to type /fusion.

When to use

Use Fusion when independent perspectives are worth the extra latency:

• a hard decision or a design tradeoff
• risk or release review
• tricky debugging
• a research-heavy question
• a breadth sweep, such as an audit or "what did we miss"

Do not use Fusion for routine edits, formatting, obvious one-step fixes, or simple questions. Keep those on the normal Pi path.

Not this skill

• The user wants one claim argued for and against. That is dialectic.
• The user wants options generated, or a draft plan stress-tested. That is brainstorming-ideas.

Fusion differs from both. Panelists run in isolation and never see the answers of the others. The value is uncorrelated errors, not debate.

How to call it

Parameter	Required	Use
prompt	yes	The topic, question, or code excerpt