Council

When you need multiple models to weigh in on the same technical decision, this orchestrates a structured investigation with model diversity first, perspective diversity second. Default roster is Opus for correctness and edge cases, GPT for implementation feasibility, and an open-source model as contrarian critic. Each agent gets the same brief but a different angle, then you synthesize their reports into one recommendation. Best for judgment calls where you want evidence from different reasoning systems: architecture tradeoffs, risky merges, incident analysis, or "should we pursue this alternative" questions. It's explicit orchestration, not magic consensus, so you still own the final call.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 9
skills.sh installs: 28.1K
GitHub stars: 684
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add warpdotdev/common-skills --skill council --agent claude-code

Installs into .claude/skills of the current project.

Files

Council

Use this skill to coordinate multiple subagents investigating the same question, with different models first and different assigned perspectives second, then synthesize their reports into one recommendation.

This skill is best for judgment-heavy tasks: architecture tradeoffs, risky bug fixes, code review red-teaming, rollout decisions, incident analysis, and “is this alternative worth pursuing?” questions.

Workflow

1. Frame the council question

State the decision the council should answer in one sentence. Identify:

the competing options or hypothesis under review;
the codebase, branch, PR, issue, design, or artifact to inspect;
whether agents should be read-only or may make code changes;
the final decision criteria, such as correctness, risk, implementation cost, testability, rollout safety, or product behavior.

If the user’s request is ambiguous, ask only the minimum clarification needed. Otherwise choose sensible defaults and proceed.