Skip to content

Council Of High Intelligence

Structured multi-perspective deliberation for hard decisions. Run full councils, focused triads, or duo debates across Claude Code, Codex, Gemini CLI, and OpenCode.

Install

$/plugin marketplace add 0xNyk/council-of-high-intelligence

Install command taken from the project's README or registry entry. Always review code before running it.

Council of High Intelligence

Structured multi-perspective deliberation for decisions that deserve more than one reasoning path.

Claude Code · Codex · Gemini CLI · OpenCode

The council assigns a hard question to deliberately different analytical personas, keeps their first positions independent, forces direct disagreement, and returns a verdict that preserves unresolved questions, dissent, kill criteria, and the next concrete action.

Try a council

Claude Code users can install the plugin directly:

/plugin marketplace add 0xNyk/council-of-high-intelligence
/plugin install council@council-of-high-intelligence

Then convene the full council, a faster panel, or a two-member dialectic:

/council Should we open-source our agent framework?
/council --quick Should we add caching here?
/council --duo Should we use microservices or a monolith?

For Codex, Gemini CLI, or OpenCode, clone once and use the matching installer flag:

git clone https://github.com/0xNyk/council-of-high-intelligence.git
cd council-of-high-intelligence

./install.sh --codex-only
./install.sh --gemini-only
./install.sh --opencode-only

Restart the target client after installation. The command remains /council on every supported host.

Use it for the decision boundary

Good council questions have material downside, competing values, incomplete evidence, or an irreversible choice. Write down the decision, constraints, evidence, reversibility, and deadline before adding personas.

The field notes distinguish facts from inference, assumptions, and unknowns. They also make it harder to use a long deliberation as decoration for a decision already made.

When to use something smaller

  • Use a direct answer or primary documentation for factual lookups.
  • Run an experiment when the choice is cheap and reversible.
  • Use --quick when cross-examination will not change the outcome.
  • Use --duo when one tension matters more than broad coverage.
  • Do not convene a council to manufacture support for a preferred answer.

Choose a mode

Mode Shape Use it when
Full Independent analysis, cross-examination, final stance, synthesis Stakes are high and competing frames need contact
Quick Restate, rapid analysis, final positions The decision needs breadth but not a full adversarial round
Duo Opening positions, direct response, final statements One polarity defines the decision
/council --full What is the right pricing model?
/council --quick --triad shipping Should we release today?
/council --duo --members torvalds,ada Is this abstraction worth it?

Named triads select three relevant lenses without assembling the whole council:

/council --triad strategy Where is our defensible advantage?
/council --triad risk What could make this launch irreversible?
/council --triad ai-product Which capability belongs in the product?

Available domains include architecture, strategy, ethics, debugging, risk, shipping, product, founder, ai, ai-product, ai-safety, decision, systems, uncertainty, design, economics, and bias. The canonical routing table lives in SKILL.md.

What the protocol protects

Similar plugs

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…

Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.

The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…

Explore related