llm-council
SolidProvider-agnostic multi-LLM deliberation. Three phases — independent responses, cross-model anonymized ranking, chairman synthesis. Provider config from env (OPENAI/ANTHROPIC/FIREWORKS/OPENROUTER/custom OpenAI-compatible base URL). Persists transcript to a wiki page when --wiki <slug> is passed. Use when the user wants multiple AI perspectives, consensus-building, or the "LLM Council" approach for high-stakes reviews, plan critique, or contested learning rules.
Install
Quality Score: 86/100
Skill Content
Details
- Author
- rohitg00
- Repository
- rohitg00/pro-workflow
- Created
- 4 months ago
- Last Updated
- 3 days ago
- Language
- JavaScript
- License
- None
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
council
5-model strategic advisory. Ask the same question to five different LLM seats in parallel, save each response to a persistent file, then synthesize a recommendation. Each seat is locked to a role (Theorist, Validator, Provocateur, Diagnostician, Field Engineer) so the responses disagree by design instead of converging by accident. Use when the user says "ask the council", "get opinions", "council on", "what do they all think", "multi-model opinion", or wants strategic input from multiple LLMs before making a decision.
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.
llm-council
Orchestrate a configurable, multi-member CLI planning council (Codex, Claude Code, Gemini, OpenCode, or custom) to produce independent implementation plans, anonymize and randomize them, then judge and merge into one final plan. Use when you need a robust, bias-resistant planning workflow, structured JSON outputs, retries, and failure handling across multiple CLI agents.