councillisted

# 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. ### 2. Choose council members Prioritize model diversity. A council should not default to three agents on the same model with different angles; use that only when the available launch configuration cannot provide multiple useful models, or when the user explicitly asks for one model. If model diversity is unavailable, say so briefly before falling back to perspective-only diversity. Preferred default roster for a three-member council: - Opus 4.7 or the strongest available Claude/Opus reasoning model: archite