decision-board

Orchestrate structured multi-agent debates to generate Architecture Decision Records.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/dnhess/spectra --skill decision-board
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-board
Source: https://github.com/dnhess/spectra/tree/main/decision-board
Command: npx skills add https://github.com/dnhess/spectra --skill decision-board

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a team of expert agents who conduct a structured, multi-perspective debate on an architectural or technical decision using a blackboard architecture. Agents write structured JSON files to a shared session directory; the moderator polls for file existence, reads results, and writes all events to the JSONL log. Debates unfold with stances, challenges, concessions, and a final Architecture Decision Record (ADR).

Core Features & Use Cases

  • Structured, multi-agent debate with a moderator-driven flow
  • Automated logging via JSONL and generation of ADRs
  • Context-budget checks and tiered debate modes (Quick, Standard, Deep)
  • Role-based personas (Architect, Pragmatist, Economist, etc.) guiding diverse perspectives
  • Synthesis briefs and debate logs for post-session review

Quick Start

Initiate a session by providing a decision question and optional options, then let the moderator orchestrate the debate.

Frequently Asked Questions about decision-board

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

FAQPage Schema
How do I automate a structured architectural decision debate to generate an ADR?

To automate an architectural decision debate and generate an ADR, initiate a session with your decision question and optional constraints. A moderator agent orchestrates a multi-perspective debate, logging JSONL events and outputting a final Architecture Decision Record.

What is a multi-agent blackboard architecture for technical decision making?

A blackboard architecture for technical decisions uses a shared session directory where expert agents write structured JSON files. A moderator polls for these files, reads results, and writes events to a JSONL log to orchestrate a reproducible multi-perspective debate.

How do I conduct a multi-perspective evaluation of migration plans and technology choices?

You can evaluate migration plans and technology choices by running a structured debate with role-based personas like Architect, Pragmatist, and Economist. Agents exchange stances, challenges, and concessions to deliver a well-supported recommendation.

Does the structured debate format support quick evaluations for fast technical decisions?

Yes, the structured debate supports quick evaluations for fast technical decisions through tiered modes. You can select Quick, Standard, or Deep debate modes to match your context budget constraints and desired depth of analysis.

Do I need any specific dependencies to run a session-based architectural decision debate?

No specific dependencies are required to run a session-based architectural decision debate. The process relies on a fixed blackboard-like session protocol, writing structured JSON files to a shared directory and logging all events to JSONL.

When should I not use an automated multi-agent debate for technical decisions?

You should not use an automated multi-agent debate when context budget is severely limited or the decision requires immediate resolution. The protocol involves multiple agents writing JSON files and logging JSONL events, which demands processing overhead.