consiliumlisted

Run a consilium - a structured multi-model review of a technical question or design decision. Independent reviewers (Claude, Codex, Open Code and others) each write a review of the same brief, arbiters merge them into a draft decision, and after the user confirms it an implementer makes the authorized changes and verifiers check them. Use ONLY when the user explicitly asks for a consilium, a multi-model review or a second opinion from several models; it sends project files to several model providers and can take many minutes.
kavyrshin/Consilium · ★ 1 · Code & Development · score 72

Install: claude install-skill kavyrshin/Consilium

# Consilium A consilium gets several independent models to look at one question, then merges what they say into a **draft** decision that the human confirms. The human is always the final arbiter; no model decides. ``` brief.md ─┬─► host review (you) ┐ ├─► reviewer 2 (external CLI) ├─► decision.md (DRAFT, two arbiters) ─► you confirm └─► reviewer 3 (external CLI) ┘ │ ▼ only after confirmation implementer ─► verifiers ─► implementer fixes ─► you review the diff ``` Everything is plain files in `consilium/<date>-<slug>/` inside the project. ## Setup you need to know - `SKILL_DIR` is the folder that contains this `SKILL.md`. All scripts are in `$SKILL_DIR/scripts/`. Run them from the **project root** with `bash`. - Set `CM_HOST` to the agent you are: `claude` when you are Claude Code, `codex` when you are Codex. You write the host review yourself, so the script never launches you a second time. Prefix every script call with it, e.g. `CM_HOST=codex bash "$SKILL_DIR/scripts/init-case.sh" ...`. - Settings live in `<project>/.consilium.conf` or `~/.config/consilium/config` (`KEY=VALUE`, see `consilium.example.conf`). The important ones: `CM_LANG` (`en` or `ru`, language of the documents), `CM_REVIEWERS`, `CM_ARBITERS`, `CM_VERIFIERS`, `CM_IMPLEMENTERS`, `CM_OUT_DIR`. Do not change the panel unless the user says so. - Adapters that are not usable (CLI missing, no