llm-council

Coordinate multiple CLI agents to generate, anonymize, and merge implementation plans.

1.0k|56|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/am-will/codex-skills --skill llm-council-am-will
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-council
Source: https://github.com/am-will/codex-skills/tree/main/skills/llm-council
Command: npx skills add https://github.com/am-will/codex-skills --skill llm-council-am-will

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The LLM Council skill coordinates a configurable, multi-member CLI planning workflow to produce independent implementation plans, anonymize outputs, and merge them into a single final plan for auditability.

Core Features & Use Cases

  • Orchestrates multiple CLI agents (Codex, Claude, Gemini, OpenCode) to generate independent plan drafts.
  • Anonymizes and shuffles plans, then runs a judge to synthesize a unified final plan.
  • Produces Markdown outputs suitable for reviews and preserves run artifacts under llm-council/runs for traceability.

Quick Start

Run the council on a task spec:

  • python3 scripts/llm_council.py run --spec path/to/spec.json
  • Optional flags: --timeout, --config, --out to capture and customize the final output.

Frequently Asked Questions about llm-council

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multiple CLI agents to produce a single implementation plan?

Multi-agent planning coordination is handled by orchestrating independent CLI agents like Codex and Claude to generate drafts. The system anonymizes, shuffles, and judges these drafts to synthesize a unified, documented final plan with metadata.

What is bias-resistant planning and how does anonymizing plan drafts work?

Bias-resistant planning prevents model-specific bias by anonymizing and shuffling independently generated implementation drafts. A judge agent evaluates the content blindly, synthesizing a final plan based on merit rather than the originating CLI agent.

How do I run a multi-agent planning council from the command line?

Run the council workflow using python3 scripts/llm_council.py run --spec path/to/spec.json. Optional flags include --timeout, --config, and --out to customize execution parameters and capture the final output.

Can I use this multi-agent planning workflow for non-software initiatives?

Yes, the planning council applies to software projects and broader initiatives requiring bias-resistant planning, auditability, and structured outputs. It enforces task_spec validation and produces Markdown outputs with preserved run artifacts for traceability.

Does the multi-agent council workflow require specific dependencies or environments?

The workflow depends on available CLI agents like Codex, Claude, Gemini, and OpenCode, alongside Python3 for script execution. It requires a valid task spec JSON file to validate and initiate the parallel plan generation process.

Why are run artifacts preserved under llm-council/runs during plan generation?

Run artifacts are preserved under llm-council/runs to ensure auditability and traceability of the multi-agent planning process. This allows users to review anonymized drafts, judge decisions, and final plan metadata post-execution.