> ## Documentation Index
> Fetch the complete documentation index at: https://docs.automagik.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# /council

> Convene real AI agents for multi-perspective deliberation on architecture, design, and strategy decisions.

# /council — Multi-Perspective Review

Convene a panel of 10 specialist perspectives to brainstorm, critique, and vote on a decision.

## When to Use

* Architecture decisions needing diverse viewpoints
* During `/wish` to generate approaches with tradeoffs
* During `/review` to surface risks and blind spots
* Deadlocked discussions needing fresh angles

## Council Members

| Member          | Focus                  | Lens                                              |
| --------------- | ---------------------- | ------------------------------------------------- |
| **questioner**  | Challenge assumptions  | "Why? Is there a simpler way?"                    |
| **benchmarker** | Performance evidence   | "Show me the benchmarks."                         |
| **simplifier**  | Complexity reduction   | "Delete code. Ship features."                     |
| **sentinel**    | Security oversight     | "Where are the secrets? What's the blast radius?" |
| **ergonomist**  | Developer experience   | "If you need to read the docs, the API failed."   |
| **architect**   | Systems thinking       | "Talk is cheap. Show me the code."                |
| **operator**    | Operations reality     | "No one wants to run your code."                  |
| **deployer**    | Zero-config deployment | "Zero-config with infinite scale."                |
| **measurer**    | Observability          | "Measure, don't guess."                           |
| **tracer**      | Production debugging   | "You will debug this in production."              |

## Modes

### Lightweight Mode (Default)

When no council members are hired in the team, all perspectives are simulated in a single session. One agent plays all roles — faster, lower cost, good for most decisions.

### Full Spawn Mode

When council members are hired in the team (`genie team hire council`), real agents deliberate via `genie chat` and reach consensus. Higher-quality since each member runs in its own context.

```bash theme={"dark"}
# Hire all 10 council members
genie team hire council
```

## Smart Routing

Not every decision needs all 10 perspectives. Topics are routed to the relevant subset:

| Topic         | Members                                        |
| ------------- | ---------------------------------------------- |
| Architecture  | questioner, benchmarker, simplifier, architect |
| Performance   | benchmarker, questioner, architect, measurer   |
| Security      | questioner, simplifier, sentinel               |
| API Design    | questioner, simplifier, ergonomist, deployer   |
| Operations    | operator, tracer, measurer                     |
| Observability | tracer, measurer, benchmarker                  |
| Full Review   | all 10                                         |

**Default:** Core trio — questioner, benchmarker, simplifier.

## Output Format

```markdown theme={"dark"}
## Council Advisory

### Topic: [Detected Topic]
### Mode: [Lightweight / Full Spawn]
### Members Consulted: [List]

### Perspectives

**questioner:**
- [Key point]
- Vote: [APPROVE/REJECT/MODIFY]

**simplifier:**
- [Key point]
- Vote: [APPROVE/REJECT/MODIFY]

### Vote Summary
- Approve: X | Reject: X | Modify: X

### Synthesized Recommendation
[Council's collective advisory]

### User Decision Required
The council advises [recommendation]. Proceed?
```

## Auto-Invocation Triggers

The council can be triggered automatically by other skills:

* **During `/review`**: when an architecture decision has significant tradeoffs, `/review` may invoke `/council` for specialist input before rendering a verdict.
* **During `/brainstorm`**: when the Decisions dimension stays unfilled after 2+ exchanges, `/brainstorm` suggests running `/council` to break the deadlock.

## Rules

* Advisory only — never block progress based on council vote
* Never invoke all 10 for simple decisions
* Each perspective must be distinct — no rubber-stamping
* Always synthesize votes into a recommendation
* The council advises, the user decides