ftm-council

Coordinate three-model majority-vote deliberation with isolated subagents and a final verdict.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-council
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ftm-council
Source: https://github.com/kkudumu/feed-the-machine/tree/main/ftm-council
Command: npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-council

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-AI deliberation council that sends problems to Claude, Codex, and Gemini as equal peers, then loops through rounds of debate until 2-of-3 agree on a decision. Use when the user wants a second (and third) opinion, says "council this", "get other opinions", "what would other AIs think", "debate this", "multi-model", "ftm-council", or wants to cross-check a decision, architecture choice, debugging approach, or any problem where diverse AI perspectives would reduce blind spots. Even if the user just says "I'm not sure about this approach" or "sanity check this", consider invoking the council.

The Protocol

  • The Council uses three peers — Claude, Codex, and Gemini — to independently investigate a problem, deliberate through rounds, and converge on a majority verdict (2-of-3) or a synthesized recommendation.
  • It supports auto-invocation in automated pipelines, frames the problem, and returns a structured verdict suitable for orchestration and blackboard logging.
  • It emphasizes independent research via isolated subagents and a rebuttal process to surface convergence signals and dissent.

Core Features & Use Cases

  • Isolated subagents for Claude, Codex, and Gemini to prevent context leakage
  • Independent research, structured rebuttals, and staged consensus rounds
  • Majority verdict with 2-of-3 agreement or synthesized conclusion after rounds
  • Auto-invocation in CI/CD or pipeline environments for sanity checks and cross-model validation
  • Output includes a formal verdict, alignment notes, and blackboard updates for traceability

Quick Start

Frame a council problem and request a 2-of-3 majority verdict after independent rounds.

Frequently Asked Questions about ftm-council

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

FAQPage Schema
How do I get multiple AI opinions on an architecture decision?

Multi-model deliberation coordinates independent AI perspectives by sending your architecture decision to Claude, Codex, and Gemini as equal peers. They independently investigate and debate through structured rounds until a 2-of-3 majority agrees on a final verdict.

What is a multi-model consensus protocol for code review?

A multi-model consensus protocol for code review uses isolated subagents to prevent context leakage between Claude, Codex, and Gemini. It loops through staged rebuttal rounds to surface dissent and convergence signals, ultimately returning a structured majority verdict.

Can I automate cross-model validation in a CI/CD pipeline?

Yes, you can automate cross-model validation in CI/CD pipelines. The deliberation council supports auto-invocation to perform sanity checks, frame problems automatically, and return structured verdicts suitable for orchestration and blackboard logging.

How do AI agents debate a debugging approach until they reach consensus?

AI agents debate a debugging approach by conducting independent research as isolated subagents, engaging in structured rebuttals, and cycling through consensus rounds. The process continues until 2-of-3 models agree on a majority verdict or produce a synthesized recommendation.

Does multi-model deliberation work without external dependencies?

Multi-model deliberation operates without external dependencies, coordinating Claude, Codex, and Gemini as equal peers internally. The protocol manages the independent subagents, debate rounds, and final verdict output autonomously within the environment.