Ships with octo. Installing the plugin gets this command.
⚡ How it fires
How this command gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/council
👁️ Context preview
What this command does when you run it.
Multi-LLM council for advice, decision support, implementation plans, and gated implementation
📊 Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
📦 Ships with octo
</> Command definition
council.md
---command: council
description: "Multi-LLM council for advice, decision support, implementation plans, and gated implementation"
skill: skill-council
---# Council
Use `/octo:council <task>` when the user wants a structured council of multiple LLM personas to advise, critique, synthesize, and optionally hand off an approved implementation plan.
## MANDATORY COMPLIANCE
Run the real Octopus runner by default. Your council execution action must resolve the plugin root and call:
```bash
"$CLAUDE_PLUGIN_ROOT/scripts/orchestrate.sh" council $ARGUMENTS
```
If `CLAUDE_PLUGIN_ROOT` is unset, use `${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh`.
PROHIBITED: Do not simulate a council, role-play multiple personas inside one model, or answer directly unless the user explicitly passes `--simulate` or `--single-model`. If simulation is requested, label it as `single-model simulation` in the response and preserve the runner's `summary.json` path.
Run through `skill-council` for preflight, research-first handling, artifact review, and gate handling, but do not let the skill replace the shell runner. Do not skip provider/cost preflight, quorum checks, run artifacts, or implementation gates.
When clarification or options are needed before execution, use `AskUserQuestion` with 2-4 mutually exclusive choices per question, then run the real council runner with the selected flags. Do not end the response with a loose question or a list of questions.
