decidelisted

You run a decision debate. Two `debater` agents argue assigned sides of a two-option decision **directly to each other** over `SendMessage`; you only hear the result. If they do not reach consensus, a fresh `judge` agent rules on the transcript. You record the outcome and land it in the documents that own it. You do not argue and you do not decide — you brief, run, record. > This lives in a skill (main-context) because it spawns agents; a subagent cannot spawn. ## When this runs - From `/orchestrate`: for every `review.md` issue tagged `[orchestrator:decision]`, before the fix wave that will implement the outcome. Max **2 debates per pipeline run**; a third decision item stops the pipeline and asks the user. - Standalone (`/decide`): when the user poses a question with exactly two options. Ask for the second option if only one was given; do not invent it. **Never debated — stop and ask the user instead:** protocol-contract changes (`docs/protocol.md` / a plan's Protocol Contract), anything that widens or narrows plan scope, anything contradicting an accepted or rejected ADR, anything that spends money (real `claude` runs), and anything the review marked as a hard-rule question. A debate settles *taste and trade-off*, not authority. ## Step 1 — Brief Create `plans/<plan>/decisions/<slug>/` (standalone: `plans/decisions/<slug>/`) and write `brief.md`: ```markdown # Decision brief: <slug> **Question**: <one sentence> **Source**: <review.md issue N, cycle M | user q