Topics
- CLI
- llm
- multi-agent
- planning
- orchestration
- codex
- claude
- gemini
- json
- markdown
What it does
Orchestrates a multi-agent planning council (Codex, Claude, Gemini, OpenCode, or custom) that produces independent implementation plans, anonymizes them, and judges them into a single final plan. Use this skill when you need bias-resistant planning with structured JSON outputs, retries, and failure handling across multiple CLI agents running in parallel.
Generated from the current SKILL.md.
Frequently asked
Can I use different LLM providers (Claude, GPT, Gemini) in the same council?
Yes. The skill supports configuring multiple planners with different providers via the task spec — Codex, Claude Code, Gemini, OpenCode, or custom CLI commands. Each planner runs independently in parallel.
How long does the council take to run?
Plans can take significant time to build. The skill enforces a 30-minute session window to allow all phases (planning, anonymization, judging) to complete. You should not close the session until the final-plan.md is saved.
What output format does the council produce?
Plans are produced as Markdown files saved under ./llm-council/runs/<timestamp>, including individual planner outputs, a judge.md, and a final merged final-plan.md for auditability.
Do I need to configure agents before running?
The skill checks for an existing agents.json config file first. If none exists, you must run ./setup.sh to configure which planning agents to use. You can also pass agent config inline via the task spec.
What happens if a planner agent fails?
The skill retries failed agents up to 2 times. If any agent still fails after retries, the council yields and alerts you to fix the issue before the judge phase can proceed.
Generated from the current SKILL.md. These answers refresh after source changes.