council

Resolve ambiguous decisions by surfacing structured tradeoffs from four independent advisory perspectives.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/himanshu231204/AI_Research_agent --skill council-himanshu231204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: council
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/council
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill council-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of making high-stakes ambiguous decisions where multiple valid paths exist, eliminating the risk of unexamined bias, conversational anchoring, and missed tradeoffs that lead to suboptimal outcomes.

Core Features & Use Cases

  • Four-Voice Advisory Council: Convenes an in-context Architect voice plus three independent subagent roles (Skeptic, Pragmatist, Critic) to surface diverse perspectives and structured dissent.
  • Anti-Anchoring Protocol: Launches external subagents with only the decision question and relevant context, preventing bias from ongoing conversation history.
  • Structured Synthesis: Enforces bias guardrails during verdict generation, ensuring all dissenting views are visible and weighed before a final recommendation is made. Common use cases include go/no-go launch calls, choosing between competing technical architectures (e.g., monorepo vs polyrepo), deciding between shipping now vs holding for polish, and evaluating feature flag vs full rollout strategies.

Quick Start

Use the council skill to evaluate whether we should ship the new customer onboarding flow as a public beta or wait until all edge case error handling is complete.

Frequently Asked Questions about council

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

FAQPage Schema
How do I resolve ambiguous strategic decisions without anchoring bias?

To resolve ambiguous strategic decisions without anchoring bias, you can use a structured multi-voice review that isolates independent advisory perspectives to surface dissent and tradeoffs before synthesizing a final recommendation.

What is the best way to evaluate go/no-go launch calls between competing options?

Evaluating go/no-go launch calls is best achieved through adversarial review, where multiple independent perspectives analyze risks and structured dissent before generating a synthesized verdict to mitigate unexamined bias.

How does multi-perspective tradeoff analysis work for technical architecture choices?

Multi-perspective tradeoff analysis works by launching isolated subagents for each advisory role, requiring them to output explicit positions, reasoning, and risks before a final synthesis weighs all dissenting views.

When do I need a structured decision-making process for high-stakes choices?

You need a structured decision-making process for high-stakes choices when multiple credible paths exist and unexamined bias or conversational anchoring risks leading to suboptimal outcomes.

Can I use adversarial review to decide between shipping a feature now or waiting for polish?

Yes, you can use adversarial review to decide between shipping now or waiting for polish by convening independent advisory roles to surface diverse perspectives and structured dissent.

What are the limitations of using multi-voice advisory councils for decision-making?

The limitations of using multi-voice advisory councils include the overhead of launching isolated subagents for each role, making it less suitable for low-stakes choices where the cost of structured dissent outweighs the benefit.