Model Council

---
name: model-council
description: Use only for an explicitly requested council of named models or agents with a judge. Ordinary review and brainstorming do not need a council.
---

# Model Council

Run the same task through user-selected independent members, then a selected
judge. Preserve every member's full report and the judge's consolidation.

Resolve members and judge from this request or its existing explicit selections;
ask only for missing choices or unreachable members. Inspect current runtime
configuration and the available permitted dispatch interfaces. Do not infer
cross-provider access from a model name, put effort only in prose when a runtime
control exists, or silently substitute a member. Follow shared delegation policy.
For Codex members from Claude Code, call the Codex CLI directly (`codex exec`),
never the retired codex-adapter plugin; see `AGENTS.md` §Running Codex.

1. Write one common brief: question, relevant source pointers, constraints,
   acceptance and report format. Use a neutral brief without preferred conclusions.
2. Give each member that brief independently. Parallelism is useful but optional;
   isolation means members do not see one another's answers. Save full attributed
   reports under the supplied run directory or `scratchpad/council/<topic>/`.
3. Give a fresh judge the brief and all attributed reports. Request a synthesis
   of agreement, disputes, evidence, best-supported conclusion and uncovered gaps.
   Majority agreement is not proof; the judge may favor a supported minority view.
4. Deliver a concise consolidation, member-position summaries and paths to every
   full report. Include full text inline when requested, rather than discarding it.

Record actual model identities where the runtime provides evidence. A failed
member gets bounded safe recovery; report any missing member and whether the
judge saw an incomplete council. Never backfill a member with your own answer.
A council-only request does not authorize implementing its recommendations.