mcpField
C
council

council

github.com/t3dotggAgent workflows2.5k376 installsUpdated 3d ago
Repository

About council

council is a skill for gathering review or feedback from three delegates using strong models from different providers. It collects their responses and summarizes findings, disagreements, and next steps, with extra review-round guidance for code and pull requests.

Key features

  1. 01Parallel delegation to three providers
  2. 02Use named or flagship models
  3. 03Read-only review and feedback
  4. 04Summarize findings and disagreements
  5. 05Track code-review rounds and scores
  6. 06Add results to pull request descriptions

Use cases

  1. 01Get independent feedback on a request
  2. 02Review code with scored delegate assessments
  3. 03Record review rounds in a pull request

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/t3dotgg/tstack --skill council

After installing, type/councilin Claude Code to confirm it loaded.

Details

From the project README

Council

Bring in three delegates to help with the user's request, usually for review or feedback. Use one strong model from each of three different providers, at high reasoning effort. If the user's instructions name council members, use those. Otherwise pick the latest flagship model from each provider, for example Claude Opus, GPT Sol, and Gemini Pro.

In T3 Code, use orchestrator_capabilities to resolve the models, then delegate_task to start one delegate per model in parallel. Elsewhere, use the harness's subagent tools. If you cannot reach three providers, or a named member is unavailable, report it instead of substituting.

Give each delegate the request and relevant context. For review or feedback, keep their work read-only. Collect their responses and summarize the useful findings, disagreements, and recommended next steps.

For a code review, ask each delegate for a score out of 10. Count each full review pass as one round. A fresh review after fixes starts a new round.

If the work ends in a pull request, put the results in the PR description. Put this section before the model and harness line at the end:

## Council review

Rounds: 2

| Delegate | Round 1 | Round 2 |
| --- | --- | --- |
| Claude Opus | 7/10 | 9/10 |
| GPT Sol | 8/10 | 10/10 |
| Gemini Pro | 7/10 | 9/10 |

If a delegate gives no score, write no score. Do not invent one. If the PR is open, edit the description. Do not post a comment for this. If there is no PR, put the same results in the final reply only.

If you agree with their recommendations, make the changes and request a fresh review after. Continue this process until all delegates are satisfied with the outcome.

Do not let repeated reviews result in scope creep. It is your job to fight to keep scope limited.

Comments

Markdown supported