← ClaudeAtlas

councillisted

/council — get a dissent-preserving council verdict on any decision. Use when the user runs /council "should we do X" (optionally --full). Generic decisions only; no person, no profiles.
elliotboney/Parley-Voo · ★ 0 · DevOps & Infrastructure · score 72
Install: claude install-skill elliotboney/Parley-Voo
# /council — Generic Verdicts Runs the deliberation engine on a decision and prints a verdict document. Zero setup: no profiles, no transcripts, no database (FR3, FR8). ## Inputs - **The decision** — the quoted argument, e.g. `/council "should we drop the enterprise tier?"`. Captured VERBATIM, including newlines if the user wrote a multi-line decision. If no decision text was given — or the quoted text is empty or whitespace-only — ask for one in a single line; never run the engine on an empty input, and do not guess. - **`--full` (optional)** — escalate to full mode. Recognized ONLY as a standalone token outside the quoted decision text; the substring `--full` INSIDE the quotes is part of the decision, not a flag (`/council "should the CLI default to --full mode?"` runs quick). - **Any other flag** (`--quick`, `--jury`, `-f`, …) → STOP and name it: `Unknown flag '--quick' — /council takes only --full.` Never silently fold an unrecognized flag into the decision text. ## Step 1: Resolve mode — forward, never decide Default is quick. If the user passed `--full` (as a flag, per Inputs), the mode is full. That is the ENTIRE mode logic this command owns: what each mode means (which seats, peer review, devil's advocate) is defined by the council-engine skill and the roster — never here (the engine's hard rule). ## Step 2: Run the engine Invoke the **council-engine** skill with: 1. Roster: `councils/council-default.md` 2. Framed input: the decision text, ve