Back to Skills

council

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

189,255stars29,267forksUpdated 5/24/2026

Security Assessment

Safe(100/100)
Security Score100/100

About council

The council skill is designed to support decision-making under ambiguity by convening a structured four-voice advisory process. It helps users evaluate complex choices where multiple credible options exist and no obvious answer is available. Instead of producing a single immediate recommendation, the skill creates deliberate disagreement and adversarial analysis before reaching a conclusion. Its primary purpose is to reduce conversational anchoring, expose hidden tradeoffs, and improve confidence in strategic decisions such as go/no-go calls, rollout strategies, or scope prioritization.

The skill operates through four distinct perspectives: Architect, Skeptic, Pragmatist, and Critic. Each voice evaluates the same decision question through a different lens, including long-term maintainability, assumption testing, execution speed, and downside risk. The workflow includes extracting the real question, gathering only relevant context, forming an initial position independently, launching isolated subagent perspectives in parallel, and synthesizing the results with explicit bias guardrails. The process emphasizes compact context sharing, structured reasoning, visible dissent, and transparent synthesis rather than consensus-driven discussion.

This skill is intended for product leaders, technical decision-makers, strategists, engineering managers, and teams facing uncertain tradeoffs. Typical use cases include choosing between architectural approaches, deciding whether to ship or delay a feature, evaluating rollout strategies, or testing assumptions in high-impact planning discussions. It is not intended for implementation planning, code review, factual Q&A, or system architecture design, and should instead be used when structured disagreement and multi-perspective reasoning are valuable.

FAQ

When should I use the council skill?

Use it when a decision has multiple credible options, tradeoffs are unclear, or you want structured dissent and second opinions before choosing a direction.

Can the council skill be used for code review or architecture design?

No. The skill is specifically designed for ambiguous decision-making rather than implementation planning, code review, or system architecture tasks.

How does the skill reduce conversational bias?

The external voices receive only the decision question and minimal relevant context instead of the full conversation history, which helps reduce anchoring and bias.

What perspectives are included in the council process?

The process includes Architect, Skeptic, Pragmatist, and Critic perspectives, each focusing on different aspects such as maintainability, assumption testing, execution speed, and downside risk.

Does the skill require repository or codebase context?

Only when the decision depends on codebase-specific information. Otherwise, the workflow recommends keeping context minimal and focused on the decision itself.

Install council

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill