with one click
council
// 4-perspective decision evaluation for architecture choices. Triggers: council, evaluate decision, pros cons, multi-angle, alternatives.
// 4-perspective decision evaluation for architecture choices. Triggers: council, evaluate decision, pros cons, multi-angle, alternatives.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | council |
| description | 4-perspective decision evaluation for architecture choices. Triggers: council, evaluate decision, pros cons, multi-angle, alternatives. |
| user-invocable | true |
| effort | high |
| argument-hint | [decision question or proposal to evaluate] |
| agent | orchestrator |
| context | fork |
| allowed-tools | Read, Grep, Glob, Bash, Agent |
$ARGUMENTS
Evaluate a decision from 4 distinct perspectives using parallel sub-agents, then synthesize a weighted recommendation.
/council [decision question or proposal to evaluate]
DO NOT analyze the decision yourself. Your job is to parse the question, spawn 4 sub-agents in parallel via the Agent tool, and synthesize their outputs. If you attempt to provide all perspectives inline, you have failed.
Extract from the user's input:
If the question is too vague to evaluate, ask ONE clarifying question before proceeding.
Before spawning agents, quickly scan the codebase for relevant context:
Include this context in each sub-agent prompt so perspectives are grounded in reality.
Call the Agent tool 4 times in a single response — all agents MUST launch in the same message to run in parallel.
| Agent | Role | Directive |
|---|---|---|
| Advocate | Case FOR | Present the strongest case FOR the proposal. Find evidence, benefits, success stories. Reference relevant code/patterns in the codebase. Be persuasive but honest. |
| Critic | Case AGAINST | Present the strongest case AGAINST. Find risks, hidden costs, failure modes, alternatives that might be better. Be thorough but fair. |
| Pragmatist | Trade-offs | Evaluate practical trade-offs: implementation cost, timeline, team capacity, maintenance burden, migration risk, operational complexity. Ground estimates in the actual codebase size and patterns. |
| User-Proxy | User impact | Consider end-user and customer impact: UX changes, downtime during migration, performance implications, breaking changes, adoption friction, documentation needs. |
Each agent prompt MUST include:
After all 4 agents complete, combine their outputs into the structured format below. Do NOT simply concatenate — identify agreements, contradictions, and conditional factors across perspectives.
## Decision Council: [Question]
### Advocate (FOR)
[Summary of arguments for — key benefits and evidence]
### Critic (AGAINST)
[Summary of arguments against — key risks and alternatives]
### Pragmatist (TRADE-OFFS)
[Practical considerations — cost, timeline, complexity]
### User-Proxy (USER IMPACT)
[End-user perspective — UX, performance, breaking changes]
### Synthesis
**Recommendation:** [FOR / AGAINST / CONDITIONAL]
**Confidence:** [HIGH / MEDIUM / LOW]
**Key condition:** [Primary factor that would change the recommendation]
**Where perspectives agree:** [Common ground across agents]
**Where perspectives conflict:** [Key disagreements and why]
### Decision Matrix
| Factor | Weight | FOR score (1-5) | AGAINST score (1-5) |
|--------|--------|-----------------|---------------------|
| Technical merit | [H/M/L] | [score] | [score] |
| Risk | [H/M/L] | [score] | [score] |
| Cost | [H/M/L] | [score] | [score] |
| Timeline | [H/M/L] | [score] | [score] |
| User impact | [H/M/L] | [score] | [score] |
| **Weighted total** | | **[total]** | **[total]** |
This skill evaluates decisions. It does NOT implement changes.