Council

Convene four advisors for decisions under ambiguity:

• Architect — correctness, maintainability, long-term implications
• Skeptic — premise challenge, simplification, assumption breaking
• Pragmatist — shipping speed, user impact, operational reality
• Critic — edge cases, downside risk, failure modes

This is for decision-making under ambiguity, not code review, architecture design, or implementation planning.

When to Use

• A decision has multiple credible paths and no obvious winner
• You need explicit tradeoff surfacing before committing
• Conversational anchoring is a risk (you've been going in one direction too long)
• 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