council

Generate a four-voice adversarial verdict with explicit dissent for ambiguous decisions.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill council-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: council
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/council
Command: npx skills add https://github.com/luongldptit/move-ticket --skill council-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of biased, anchored, or poorly informed decisions when multiple valid paths exist with no obvious winner, ensuring all tradeoffs and dissenting perspectives are surfaced before you commit to a path.

Core Features & Use Cases

  • Four-voice adversarial council: Conveniences an Architect (your initial position), Skeptic, Pragmatist, and Critic to cover correctness, assumption-breaking, execution reality, and downside risk.
  • Anti-anchoring workflow: Runs external voices as fresh subagents with only relevant context to avoid conversational bias from ongoing discussions.
  • Structured scannable verdict: Produces a phone-friendly output that makes disagreement legible, so you can make informed go/no-go calls, tradeoff decisions, or path selections.
  • Use Case: Use it to decide between shipping a feature now vs holding for polish, choosing between monorepo and polyrepo structures, or evaluating feature flag vs full rollout strategies.

Quick Start

Use the council skill to get a structured four-voice verdict on whether to ship the new user onboarding flow now or wait for additional accessibility polish, including all relevant constraints and success criteria.

Frequently Asked Questions about council

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

FAQPage Schema
How do I make tradeoff analysis decisions without biased consensus?

To make tradeoff analysis decisions without biased consensus, use a four-voice adversarial council that surfaces all dissenting perspectives before committing. This structured approach runs external voices as fresh subagents to avoid conversational anchoring and reduce decision risk.

What is an adversarial council for ambiguous decision-making?

An adversarial council for ambiguous decision-making is a structured process that convenes an Architect, Skeptic, Pragmatist, and Critic to cover correctness, assumption-breaking, execution reality, and downside risk. It delivers a synthesized recommendation with explicit dissent for go/no-go calls.

How do I evaluate a go/no-go call when multiple credible paths exist?

Evaluate a go/no-go call with multiple credible paths by running a four-voice analysis that breaks down assumptions and execution realities. This method produces a scannable verdict making disagreement legible so you can commit to a path with reduced decision risk.

When should I use multi-perspective analysis for product decisions?

Use multi-perspective analysis for product decisions when facing ambiguous scenarios with no obvious optimal choice, such as shipping a feature now versus holding for polish. It prevents conversational anchoring by running fresh subagents with only relevant context.

What is the best way to choose between monorepo and polyrepo structures?

The best way to choose between monorepo and polyrepo structures is to apply a structured four-voice adversarial verdict. This method evaluates tradeoffs across correctness, execution reality, and downside risk to produce a synthesized recommendation for your path selection.

Can I use this multi-perspective approach for feature flag vs full rollout strategies?

Yes, you can use this multi-perspective approach for feature flag vs full rollout strategies. The four-voice council evaluates the ambiguous decision by surfacing tradeoffs and explicit dissent from an Architect, Skeptic, Pragmatist, and Critic to ensure informed path selection.