deliberation

Synthesize conflicting viewpoints into conditional verdicts with adversarial challenge workflows.

7|Updated May 26, 2026
One-click install
npx skills add https://github.com/chrono-meta/forge-harness --skill deliberation-chrono-meta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliberation
Source: https://github.com/chrono-meta/forge-harness/tree/main/plugins/fh-commons/skills/deliberation
Command: npx skills add https://github.com/chrono-meta/forge-harness --skill deliberation-chrono-meta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of biased, single-perspective decision making by providing a structured workflow to clash, challenge, and synthesize conflicting viewpoints for design, architectural, and proposal evaluations, ensuring no salvageable insights are discarded.

Core Features & Use Cases

  • 3-Layer Core Workflow: Innovator proposes options, Devil-Advocate challenges assumptions with required acknowledgment of valid points, and an isolated Mediator synthesizes a conditional verdict instead of picking a binary winner.
  • Optional 5-Layer Jury: Add domain-specific personas (UX, technical, business) to fill blind spots for high-stakes decisions.
  • Use Cases: Ideal for design tradeoffs, architectural choices, skill proposal reviews, and any scenario where you need to weigh pros and cons without unproductive conflict.

Quick Start

Use the deliberation skill to weigh the pros and cons of adopting a microservices architecture for our new e-commerce backend and get a conditional verdict with required safeguards.

Frequently Asked Questions about deliberation

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

FAQPage Schema
How do I evaluate architectural tradeoffs without picking a binary winner?

To evaluate architectural tradeoffs without a binary winner, use a structured multi-perspective synthesis workflow. It clashes conflicting viewpoints, applies adversarial reasoning, and outputs a conditional verdict that retains all salvageable insights. This prevents unproductive conflict during design decisions.

What is adversarial reasoning for design decisions and how does it work?

Adversarial reasoning for design decisions works through a 3-layer workflow where an innovator proposes options and a devil's advocate challenges assumptions. The devil's advocate must acknowledge valid points before an isolated mediator synthesizes an unbiased, conditional verdict.

Can I use domain-specific personas for high-stakes proposal evaluations?

Yes, you can use an optional 5-layer jury to add domain-specific personas like UX, technical, and business experts for high-stakes proposal evaluations. These personas fill analytical blind spots and enrich the multi-perspective synthesis process.

What's the best way to analyze pros and cons for conflicting viewpoints?

The best way to analyze pros and cons for conflicting viewpoints is using a structured synthesis workflow with confirmation bias guardrails. It ensures valid points are acknowledged during adversarial challenges, preventing biased judgment and ensuring no salvageable insights are discarded.

When should I not use multi-perspective synthesis for decision making?

You should avoid multi-perspective synthesis when the system detects unsynthesizable inputs, triggering an automatic warning. If your proposal evaluation lacks conflicting viewpoints or clear architectural tradeoffs, the conditional verdict process may not yield actionable results.