council

Topics in the source

• Council
• When to Use
• When NOT to Use
• Roles
• Workflow
• 1. Extract the real question
• 2. Gather only the necessary context
• 3. Form the Architect position first

Convene four advisors for ambiguous decisions: the in-context Claude voice a Skeptic subagent a Pragmatist subagent a Critic subagent This is for decision-making under ambiguity, not code review, implementation planning, or architecture design. Use council when: a decision has multiple credible paths and no obvious winner you need explicit tradeoff surfacing the user asks for second opinions, dissent, or multiple perspectives conversational anchoring is a real risk a go / no-go call would benefit from adversarial challenge Examples: monorepo vs polyrepo ship now vs hold for polish feature flag vs full rollout simplify scope vs keep strategic breadth | Instead of council | Use | | --- | --- | | Verifying whether output is correct | santa-method | | Breaking a feature into implementation steps | planner | | Designing system architecture | architect | | Reviewing code for bugs or security | code-reviewer or santa-method | | Straight factual questions | just answer directly | | Obvious execution tasks | just do the task | | Voice | Lens | | --- | --- | | Architect | correctness, maintainability, long-term implications | | Skeptic | premise challenge, simplification, assumption breaking

This is an excerpt. Refer to the complete source and its current requirements.