# LLM Council

Convene a cross-vendor LLM council, the session is Chairman and spawns subagents each...

- Repository: https://github.com/kirodotdev/KiroCrew (4711 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kirodotdev/KiroCrew --skill llm-council -g -a claude-code -y`
Codex: `npx skills add kirodotdev/KiroCrew --skill llm-council -g -a codex -y`
Cursor: `npx skills add kirodotdev/KiroCrew --skill llm-council -g -a cursor -y`
Gemini CLI: `npx skills add kirodotdev/KiroCrew --skill llm-council -g -a gemini-cli -y`

## Description

Convene a cross-vendor LLM council, the session is Chairman and spawns subagents each pinned to a DIFFERENT model family (Anthropic/OpenAI/DeepSeek/Zhipu/Qwen via kiro-cli). Modes, synthesis, vote, adversarial (SHIP/REVISE/REJECT). Use for hard, high-stakes or subjective questions.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# LLM Council

## Overview

Answer with a **panel of different-vendor models** instead of one. The **main
session is the Chairman**: it fans a task out to N subagents, each `spawn_run`
pinned to a different model via the `model` override, collects their outputs, and
produces one result. Cross-vendor is the point (a same-model panel echoes one bias);
kiro-cli is already the gateway (`kiro-cli chat --list-models`), so no external egress.

## Modes at a glance

| Mode | Members do | Chairman does | Use for |
|---|---|---|---|
| **synthesis** (default) | Answer INDEPENDENTLY & blind (MoA) | Merge into one better answer + surface dissent | Open questions, design calls, "am I missing something" |
| **vote** | Cast ONE structured `VOTE:` from a fixed option set | Deterministic majority tally + verdict | Group decisions with discrete options |
| **adversarial** | Red-team a TARGET (critic / defender roles), not blind | Consolidate critiques by severity → SHIP/REVISE/REJECT | Reviewing a design, plan, or PR |

One prompt can't do all three: a blind-independent proposer is wrong for voting
(needs a tallyable verdict) and for review (a critic must SEE the target and attack
it). Design grounded in the multi-agent-debate literature (MoA vs Multi-Persona vs
voting are distinct role structures; "agreement modulation" is the key knob).

## When to use / when NOT

**Use** for hard/high-stakes/ambiguous/subjective questions, group decisions, or
reviews. **Do NOT use** for simple lookups or routine turns, a council costs **N+1
model runs**. It is a deliberate, occasional move. If unsure it's worth it, ask first.

## Procedure (you are the Chairman)

The rest: https://github.com/kirodotdev/KiroCrew/blob/HEAD/src/kiro_crew/builtin_skills/llm-council/SKILL.md