Roundtable

Multi-agent debate council — spawns 3 specialized sub-agents in parallel (Scholar, Engineer, Muse) for Round 1, then optional Round 2 cross-examination to challenge assumptions and strengthen the final synthesis. Configurable models and templates per role.

# Roundtable 🏛️ — Multi-Agent Debate Council

[![Version](https://img.shields.io/badge/version-0.4.0--beta-green)](./package.json)
[![ClawHub](https://img.shields.io/badge/ClawHub-roundtable-blue)](https://www.clawhub.ai/skills/roundtable)

Spawn 3 specialized sub-agents in parallel to tackle complex problems. You (the main agent) act as **Captain/Coordinator** — decompose the task, dispatch to specialists, run optional cross-examination, and synthesize the final answer.

## When to Use

Activate when the user says any of:
- `/roundtable <question>` or `/council <question>`
- `/roundtable setup` (interactive setup wizard)
- `/roundtable config` (show saved config)
- `/roundtable help` (command quick reference)
- "ask the council", "multi-agent", "get multiple perspectives"
- Or when facing complex, multi-faceted problems that benefit from diverse expertise

**DO NOT use for:** Simple questions, quick lookups, casual chat.

## Architecture

```
User Query
    │
    ▼
┌─────────────────────────────────┐
│  CAPTAIN (Main Agent Session)   │
│  Parse flags + assign roles     │
└────┬──────────┬─────────────────┘
     │          │          │
     ▼          ▼          ▼
┌─────────┐┌─────────┐┌─────────┐
│ SCHOLAR ││ENGINEER ││  MUSE   │
│ Round 1 ││ Round 1 ││ Round 1 │
└────┬────┘└────┬────┘└────┬────┘
     │          │          │
     └──────┬───┴───┬──────┘
            ▼       ▼
     Captain summary of all findings
            │
            ▼
┌─────────┐┌─────────┐┌─────────┐
│ SCHOLAR ││ENGINEER ││  MUSE   │
│ Round 2 ││ Round 2 ││ Round 2 │
│ critique││ critique││ critique│
└────┬────┘└────┬────┘└────┬────┘
     │          │          │
     └──────┬───┴───┬──────┘
            ▼
┌─────────────────────────────────┐
│  CAPTAIN final synthesis        │
│  consensus + dissent + confidence│
└─────────────────────────────────┘
```

## Interactive Setup

When the user sends `/roundtable setup`, run a guided, conversational setup and ask **ONE question at a time**.
Use Telegram-friendly option formatting with inline button style labels (`A)`, `B)`, `C)`).
Do not ask all steps at once.

### Step 1: Models
Ask exactly:

"🏛️ Let's set up your Roundtable! First, how do you want to configure models?
A) 🎯 Single model for all agents (simple, cost-effective)
B) 🔀 Different models per role (maximum diversity)
C) 📦 Use a preset (cheap/balanced/premium/diverse)"

Branching:
- If user picks **A** → ask: which model to use for all roles.
- If user picks **B** → ask one-by-one for: Scholar model, Engineer model, Muse model.
- If user picks **C** → ask which preset: `cheap`, `balanced`, `premium`, or `diverse`.

### Step 2: Round 2
Ask exactly:

"Do you want Round 2 cross-examination by default? (Agents challenge each other's findings — better quality but 2x cost)
A) ✅ Yes, always (recommended for important decisions)
B) ⚡ No, quick mode by default (faster, cheaper)
C) 🤷 Ask me each time"

Interpretation:
- **A** → `round2: true`
- **B** → `round2: false`
- **C** → `round2: "ask"`

### Step 3: Language
Ask exactly:

"What language should the council respond in?
A) 🇬🇧 English
B) 🇩🇪 Deutsch
C) 🇪🇸 Español
D) Other (specify)"

Interpretation:
- **A** → `language: "en"`
- **B** → `language: "de"`
- **C** → `language: "es"`
- **D** → store user-provided language value.

### Step 4: Session Logging
Ask exactly:

"Should I save council sessions for future reference?
A) ✅ Yes, save to memory/roundtable/
B) ❌ No logging"

Interpretation:
- **A** → `log_sessions: true`, `log_path: "memory/roundtable"` (fixed path, not configurable for security)
- **B** → `log_sessions: false`

**⚠️ SECURITY:** The log path is ALWAYS `memory/roundtable/` relative to the workspace. Custom paths are NOT allowed to prevent path traversal attacks.

### Step 5: Confirmation + Write
Show a concise summary of all collected choices and ask user to confirm.
Only after confirmation, write `config.json` in this skill directory.

Required command behavior:
- `/roundtable config` → Show current `config.json` if it exists, otherwise: `No config found, run /roundtable setup to configure.`
- `/roundtable help` → Show quick reference:
  - `/roundtable <question>` — ask the council
  - `/roundtable setup` — interactive setup wizard
  - `/roundtable config` — show current config
  - `/roundtable help` — this help

## Model Configuration

Users can specify models per role. Parse from the command or use defaults.

### Modes

**Single-model mode** (same model, different perspectives):
```
/roundtable <question>
/roundtable <question> --all=sonnet
```
All 3 agents use the SAME model but with different system prompts and focus areas. This is the simplest setup — the value comes from the **different perspectives**, not necessarily different models.

**Multi-model mode** (different models per role):
```
/roundtable <question> --scholar=codex --engineer=codex --muse=sonnet
```
Each agent runs on a different model optimized for its role. This is the power configuration — different models bring genuinely different reasoning patterns.

### Syntax
```
/roundtable <question>                                         # defaults (balanced preset)
/roundtable <question> --all=sonnet                            # single model, 3 perspectives
/roundtable <question> --scholar=codex --engineer=opus         # mix (unset roles use default)
/roundtable <question> --preset=premium                        # all opus
/roundtable <question> --preset=cheap --quick                  # all haiku, skip Round 2
```

### Defaults (if no model specified)
| Role | Default Model | Why |
|------|--------------|-----|
| 🎖️ Captain | User's current session model | Coordinates & synthesizes |
| 🔍 Scholar | `codex` | Cheap, fast, good at web search |
| 🧮 Engineer | `codex` | Strong at logic & code |
| 🎨 Muse | `sonnet` | Creative, nuanced writing |

**Note:** Even with `--all=<model>`, each agent still gets its own specialized system prompt. The model is the same but the focus is different — Scholar searches and verifies, Engineer reasons and calculates, Muse thinks creatively. One model, three expert lenses.

### Model Aliases (use in --flags)
- `opus` → Claude Opus 4.6
- `sonnet` → Claude Sonnet 4.5
- `haiku` → Claude Haiku 4.5
- `codex` → GPT-5.3 Codex
- `grok` → Grok 4.1
- `kimi` → Kimi K2.5
- `minimax` → MiniMax M2.5
- Or any full model string (e.g. `anthropic/claude-opus-4-6`)

### Presets
- **`--preset=cheap`** → all haiku (fast, minimal cost)
- **`--preset=balanced`** → scholar=codex, engineer=codex, muse=sonnet (default)
- **`--preset=premium`** → all opus (max quality, high cost)
- **`--preset=diverse`** → scholar=codex, engineer=sonnet, muse=opus (different perspectives)
- **`--preset=single`** → all use session's current model (cheapest multi-perspective)

## Budget Controls

Before dispatching, Captain shows a quick estimate:

```
📊 Estimated cost: ~3x single-agent (Quick mode)
📊 Estimated cost: ~6-10x single-agent (Full with Round 2)
```

- `--confirm`: when set, Captain asks **"Proceed? (Y/N)"** before dispatching (especially useful for premium presets).
- `--budget=low|medium|high`:
  - `low`: forces `--preset=cheap --quick` (haiku, no Round 2)
  - `medium`: default balanced preset with Round 2
  - `high`: premium preset with Round 2
- `config.json` may include optional `max_budget` (`"low"`, `"medium"`, or `"high"`) to cap spending globally.

## Flag Precedence

When multiple model/budget flags are present, resolve in this exact order:

1. `--budget`
2. `--preset`
3. `--all`
4. Role-specific flags (`--scholar`, `--engineer`, `--muse`)
5. `config.json` defaults

## Templates

Use templates to customize each role’s emphasis for specific domains.

| Template | Scholar Focus | Engineer Focus | Muse Focus |
|----------|--------------|----------------|------------|
| `--template=code-review` | Check docs, similar issues, best practices | Review logic, find bugs, security | UX, naming, readability |
| `--template=investment` | Market da