councildebatelisted

# /council debate ## Instructions Specialised council mode for **multi-round debates**. Each enabled member produces an initial position in Round 1, then rebuts the strongest opposing position in subsequent rounds. The orchestrator pauses between rounds and asks the user to continue (progressive cost disclosure). Hard cap: `ai_council.cost_budget.max_total_usd` aborts the next round if the projection breaches the cap, persisting the partial debate. This is **not a flag** on `/council default` — debate mode changes the orchestration shape (N members × R rounds = N×R calls) and the cost UX, so it earns its own sub-command per the R4 verdict. ### 1. Resolve the topic The user invoked `/council debate "<topic>"` or `/council debate <path-to-artefact>`. Treat the argument as the **topic** of the debate (a question, a proposal, an architectural call). If missing, ask (one question per turn, per `ask-when-uncertain`): > What is the topic of the debate? > > 1. Inline topic (e.g. "Should we adopt event sourcing for the orders module?") > 2. Path to a file containing the topic / artefact > 3. Cancel Capture the resolved topic as `original_ask` verbatim. Do **not** add the agent's framing. ### 2. Decide round count + auto-continue Default: 2 rounds (initial position + one rebuttal). Cap: the value of `defaults.debate_max_rounds` in [`agents/settings/.ai-council.yml`](../../../agents/settings/.ai-council.yml) (default 4). `--rounds N` overrides the default; values above the cap