ask-the-council

Solid

Convenes a panel of opinionated advisors (parallel Claude subagents, each with a distinct mandate and a forbidden move so they genuinely diverge), then a Chairman synthesis that COMMITS to one recommendation with explicit tradeoffs. Use proactively for any high-stakes design, architecture, or tradeoff decision where credible options genuinely compete. Also on "ask the council", "the council", "get a panel". Not for fact-finding or decisions with one obvious answer — answer those directly.

AI & Automation 6 stars 0 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
28
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Ask the Council A panel of advisors who are required to disagree, then a Chairman who decides. Use for decisions and tradeoffs, not for gathering facts. ## Proactive use If a decision is high-stakes and the options genuinely compete — architecture choice, buy-vs-build, irreversible migration — invoke this without being asked: announce in one line ("Convening the council: <decision>") and proceed. Never ask permission to run the skill. ## Process 1. **Frame the decision.** Restate the question, the real options, and the binding constraints. If one missing fact would flip the answer, ask it (max 1–2). Otherwise proceed on stated assumptions. 2. **Seat the council — in parallel.** Spawn advisors with the Agent tool, **all in one message**. Default panel of 4; `deep` seats all 6 and adds a critique round. Each advisor returns: **position · core reasoning · biggest risk they see · confidence (low/med/high)**. 3. **(deep only) Cross-critique.** Show each advisor the others' positions (unattributed) and have them name the single strongest opposing point. 4. **Chairman synthesis (you).** Not an average — a judgment. Output where they converge, where they split and *why*, the decisive tradeoff, and **one recommended path** with its rationale and the main risk to watch. ## The seats (mandate + forbidden move = real divergence) - **Pragmatic Executor** — what ships fastest and safest with current resources. *Forbidden:* greenfield / ideal-world answers...

Details

Author
alonbaron
Repository
alonbaron/claude-skills
Created
1 months ago
Last Updated
2 days ago
Language
N/A
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

council

Convenes 7 expert AI personas to debate any decision, idea, or problem and synthesizes a structured verdict with confidence score, minority report, and concrete next steps. Use when the user presents a decision, asks "should I...", "is this a good idea", "help me decide between...", "stress-test this idea", or says "convene the council". Automatically triggers on any genuine tradeoff with stakes. Produces genuine disagreement — not a balanced summary — with a clear verdict and no "it depends" without specifics.

4 Updated 4 days ago
DjordjeMojsilovic
AI & Automation Solid

council

Pressure-tests high-stakes engineering decisions through 5 advisors with distinct thinking styles — independent analysis, anonymous peer review, chairman synthesis. Use when the user says "council this", "run the council", "pressure-test", "stress-test", "red team this", or "devil's advocate" on a real engineering trade-off. Distinct from strategic-analysis — adds adversarial peer review for decisions where the user suspects their first instinct is biased.

0 Updated today
emrecdr
AI & Automation Listed

llm-council

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

0 Updated 1 weeks ago
kochellenk-afk