ai-debate

AI Debate Review workflow

The review workspace is a file-based, multi-agent debate space: agents (Claude, Codex) exchange design → attack → rebuttal → decision documents about one topic, adversarially verifying each other's claims, and converge on a decision delivered to the user. It is NOT a finished-docs store; confirmed knowledge graduates to the wiki, in-flight argument stays in the workspace. Default workspace folder: llm_wiki/ai_debate/ (configurable; the coordinator is folder-name-agnostic).

Default happy path — one command, hands-free to the verdict

When the user names something to debate/review ("X를 토론해봐", "debate whether we should X", "리뷰 붙여줘"), the ENTIRE flow is one command — /review-new <topic> — which:

1. scaffolds the workspace if missing (no separate init step),
2. creates the topic in one shot — slug derived from the user's phrase, topic.md written from conversation context (do not interrogate the user; one clarifying question max), auto=true,
3. starts the coordinator in the background (run_auto.ps1 -Watch; the single-instance mutex makes a duplicate start harmless), so the agents cycle design → attack → rebuttal → decision by themselves,
4. waits in the background (wait_for_review.ps1 <topic> -UntilStatusLike decided*, run_in_background) and, on completion, reports the decision.md verdict: adopted findings, ruling, residual risks, next step.

Do NOT hand-write rounds yourself, do NOT poll. Multiple topics? Run /review-new for each; the queue drains by priority. A round cap (default 5 numbered docs, per-topic max_rounds) forces a JUDGE verdict if the debate ping-pongs, so autonomous runs always terminate.

Round count control — "이 주제 5라운드로" applies immediately

1 round = 1 numbered doc (design = round 1, attack = round 2, rebuttal = round 3, …). "5 rounds" means 5 numbered docs, then a forced JUDGE writes decision.md.

• At creation — user says "5라운드로 토론해줘" / "debate this in 5 rounds": pass --rounds 5 to /review-new (sets max_rounds: 5 in the topic's status.json).
• Existing / already-running topic — user says "해당 주제 5라운드로 해줘" / "make that topic 5 rounds": update the topic's status.json immediately via the workspace script: update_status.ps1 -TopicDir <topic-path> -Set @{ max_rounds = 5 } -Force This takes effect on the coordinator's very next poll — no restart needed (the cap is re-read from status.json every turn). Confirm to the user: current numbered-doc count vs the new cap (if the topic already has ≥ N docs, the next turn becomes the JUDGE round).
• max_rounds: 0 (or absent) = coordinator default (-MaxNumberedDocs, 5).