council

/council [task]

Invoke the council on [task].

Requirements

Agent teams are experimental and disabled by default. This command needs them:

{ "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } }

Without it, no team is set up at session start, and the lead can neither spawn teammates nor propose them. Check this first and fail loudly — a silent fallback to fire-and-forget subagents removes the synthesizer↔clarity cross-talk that is the entire point of the council.

When to use

• Question requires both cited evidence (research) and rigorous reasoning (logic)
• Answer needs gap-checking before delivery
• Task is complex enough that a single pass will miss something
• You want the synthesis reconciled live against the evidence before it ships

How it runs

captain = the session lead (Fable 5) — frames a research question
  │
  └── /deep-research <question>  (dynamic workflow — fans out searches, returns a cited report)
        │
        └── captain spawns teammates; the team forms on the first spawn
              │
              ├── synthesizer (Opus 5 teammate) reasons over the report + task
              └── clarity     (Opus 5 teammate) gap-checks the synthesis against the report
                    → asks synthesizer live follow-ups via SendMessage
                    → synthesizer responds in real time (reactive cross-pollination)
              │
              └── captain reads report + team messages → produces draft
                    │
                    └── janitor (Opus 5 teammate) → BLOAT_FLAG + CUTS via SendMessage
                          │
                          └── captain removes cuts → final output
                          │
                          └── shutdown requests; team dirs cleaned up on session exit

/deep-research is a dynamic workflow, not a live SendMessage teammate — it returns a report. The live cross-pollination is between the synthesizer and clarity reconciling that report.

Orchestration