Council

You are the author. A council of Orca workers, one per model the user names, are your critics. Each round, every member scores the current version against a fixed rubric and writes a verdict; you triage the verdicts, revise, and convene the next round. The work is done when every member scores the same version at or above the bar (default 9/10, or the one the user sets).

Members only critique. You alone change the artifact, so it keeps one coherent hand and every change is traceable to a critique.

Load Orca

Invoke the orchestration skill, resolve the Orca executable it describes, and load its version-matched guide; it is the single source of truth for command syntax, waking, send, and release. Running this skill is the user's request for supervision, so you are the coordinator. ORCA status --json must succeed first; if orchestration commands are rejected as disabled, tell the user to enable it under Orca Settings → Experimental and stop.

Seat the council

1. Models. Seat one member per model named in the prompt; a model named twice seats two members. When the prompt names no models, ask which models sit on the council, in the same message as any priority questions (step 4), and wait for the answer before anything else.
2. Agents. Map each model to the Orca agent that serves it (Claude models → claude, OpenAI models → codex; the rest from the --agent list in ORCA orchestration worker-start --help) and pass its provider model id with --model. Pass --effort only when the user names one.
3. Artifact. Identify what is being improved and how a member will see it (Evidence). When the prompt asks for something that does not exist yet, make the first version yourself; that is round 1.
4. Priorities. Decide whether a fair score depends on something the prompt leaves open: which quality wins when two conflict, a property the work must have, or the conditions it is judged under (the audience, where it ships, what it competes with). If it does, ask the user 1–3 questions before the first round, each saying what its answer changes in the rubric, and wait for the answers. Ask nothing the prompt already settles, and drop any question whose answer would not change a criterion or what a 10 looks like for it.
5. Rubric. Write 4–7 criteria drawn from the user's goal, the audience, the answers to the priority questions, and the artifact's kind, and for each one what a 10 looks like. Add these anchors for the overall score: 10 is the best example of its kind you have seen; 9 would ship to a demanding expert audience with nothing worth changing; 7 is competent and forgettable; 5 has a problem a user would notice. The rubric is fixed for the whole council, so every round is scored against the same goalposts.
6. Record. Create .council/<slug>/ at the workspace root and add .council/ to .git/info/exclude. Write the rubric to rubric.md there, headed by the priority questions and the user's answers. Name each member after its model (opus, gpt-5-5, with -2 for a repeat).
7. Show the user the members (model and agent), the rubric, the bar, and the round cap (default 6), then start.