model-committee-sollisted

# Model Committee (Sol-chaired) Run GPT-5.6 "Terra" and Claude Opus 5 as a deliberating committee with **GPT-5.6 "Sol" as the chair**. Keep the line to `$model-council-voting` sharp: a council measures independent disagreement, while this committee deliberately exposes each member to the other's argument and returns one decision. Read [`references/protocol.md`](references/protocol.md) completely before running a committee. It carries the use-case gate, the brief template, the three round contracts, the decision rule, and the `decision.md` schema. Invoked as `$model-committee-sol` inside a Codex/Sol session, Sol chairs natively — that is this variant's intended home. Sol is neither deliberating member: cross-family to the Opus member, and a distinct 5.6 tier from the Terra member. The GPT member is pinned to Terra rather than Sol precisely because the chair is Sol; a chair identical to a member would defeat the point. Siblings: [`model-committee`](../model-committee/SKILL.md) (Opus 5 chairs) and [`model-committee-fable`](../model-committee-fable/SKILL.md) (Fable 5 chairs). ## Gate the workflow Run only when the user invokes `$model-committee-sol` or asks for a Sol-chaired Terra / Opus deliberation. The external calls draw plan credits or API spend on both providers — surface that and get confirmation unless the user has already accepted it. Apply the protocol's use-case gate first; if the task does not qualify, name the right alternative and call no model. Before the fir