council

Convenes four subagent roles to analyze ambiguous technical decisions.

1|Updated Apr 6, 2026

Search Tags:#architecture #strategy #consensus #decision-making #adversarial #tradeoffs

Ready to run

npx skills add https://github.com/vrcms/everything-qwen-code --skill council-vrcms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: council
Source: https://github.com/vrcms/everything-qwen-code/tree/main/.qwen/skills/council
Command: npx skills add https://github.com/vrcms/everything-qwen-code --skill council-vrcms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of decision-making under ambiguity by preventing cognitive biases like anchoring and groupthink when choosing between multiple valid paths.

Core Features & Use Cases

Adversarial Perspectives: Automatically convenes four distinct roles (Architect, Skeptic, Pragmatist, Critic) to stress-test a decision.
Anti-Anchoring Mechanism: Uses fresh subagents to ensure independent, unbiased feedback on complex trade-offs.
Use Case: Use this when deciding between architectural patterns like monorepo vs. polyrepo, or when determining if a feature is ready for production rollout.

Quick Start

Invoke the council skill to evaluate the trade-offs of migrating our current database to a distributed architecture.

Frequently Asked Questions about council

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent groupthink when making complex architectural decisions?▼

To prevent groupthink during architectural decisions, use structured adversarial evaluation with independent subagent roles to force disagreement and surface tradeoffs objectively. This prevents cognitive biases like anchoring by isolating context and stress-testing proposed paths through distinct skeptic and critic perspectives.

What is structured adversarial decision-making for ambiguous technical tradeoffs?▼

Structured adversarial decision-making for technical tradeoffs is a process that convenes multiple independent roles—Architect, Skeptic, Pragmatist, and Critic—to analyze complex project dilemmas. It forces independent feedback to surface tradeoffs and prevent bias when choosing between valid paths like monorepo versus polyrepo.

How do I evaluate tradeoffs for migrating to a distributed database architecture?▼

To evaluate tradeoffs for migrating to a distributed database architecture, convene a multi-voice advisory council to facilitate structured disagreement. By assigning independent subagent roles to analyze the decision framing, you ensure objective, adversarial evaluation of the proposed migration path and its inherent tradeoffs.

Can I use independent subagents to stress-test production rollout readiness?▼

Yes, you can use independent subagents to stress-test production rollout readiness by convening an adversarial council. The subagents operate as distinct roles—such as a Skeptic and Pragmatist—to provide fresh, unbiased feedback on complex trade-offs, ensuring objective evaluation of the feature's readiness.

Does this approach require clear decision framing to evaluate strategic paths?▼

Yes, this adversarial evaluation approach requires clear decision framing and context isolation to function correctly. Establishing strict boundaries around the strategic decision ensures that the independent subagent roles can objectively analyze the tradeoffs without anchoring bias interfering with the evaluation.

When should I not use adversarial consensus building for project dilemmas?▼

You should not use adversarial consensus building for project dilemmas when the technical decision lacks ambiguity or valid alternative paths. If there is only one clear solution without complex tradeoffs to surface, the structured disagreement and independent subagent evaluation process provides unnecessary overhead.