discussion

Orchestrates a three-round debate among multiple LLMs to converge on one conclusion.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/Cohey0727/CodingAgentTools --skill discussion-cohey0727
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discussion
Source: https://github.com/Cohey0727/CodingAgentTools/tree/main/skills/discussion
Command: npx skills add https://github.com/Cohey0727/CodingAgentTools --skill discussion-cohey0727

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a design decision or policy question has no obvious answer, a single model's opinion is unreliable. This Skill runs a structured multi-LLM discussion where independent models state positions, respond to disagreements, and attack a draft conclusion, while the current session's LLM moderates and adjudicates a final answer. ## Core Features & Use Cases - Three-round structured debate: Round 1 collects independent opinions, Round 2 confronts each participant with conflicting anonymous positions and moderator questions, Round 3 stress-tests the aggregated draft for logical holes. - Moderator adjudication: The session LLM builds a topic map, drafts an aggregated proposal, and rules on each criticism by evidence strength rather than majority vote, with one extra round allowed for fatal objections. - Configurable participants via llms.json: Enable or disable discussants by editing entries with name, command, and timeout; all participants run through OpenCode in read-only plan mode. - Use Case: Ask whether to adopt a new architecture for a repository. The Skill checks out a worktree, gathers independent opinions from three models, maps their disagreements, forces responses to conflicts, and delivers a single adjudicated conclusion with remaining uncertainties. ## Quick Start Ask the assistant to run a discussion on whether the team should adopt approach A or B for the current design problem.

Frequently Asked Questions about discussion

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

FAQPage Schema
How do I run a multi-LLM discussion on a design decision?▼

Invoke the discussion skill with a single question as the topic. It reads enabled models from llms.json, collects independent opinions in round one, confronts participants with disagreements in round two, and stress-tests the aggregated draft in round three before producing a final conclusion.

How do I add or remove models from the discussion participants?▼

Edit the llms.json file in the skill directory and set the enabled field to true or false for each entry. New participants are added as entries with a name, a stdin schema, and an opencode run command using the plan agent for read-only access.

What is the difference between discussion and fusion-review?▼

Fusion-review sends the same request to multiple models once in parallel and merges the answers. Discussion adds rebuttal rounds: participants respond to conflicting positions and attack a draft conclusion, while a moderator adjudicates which position survives.

Can the discussion skill modify my repository files?▼

No. All external participants run through opencode with the plan agent flag, which enforces read-only behavior. The skill may create a temporary git worktree so participants can read the code, and it removes that worktree afterward.

What happens if a participant model times out or fails?▼

Failed, timed-out, or empty responses are skipped without retry, and the error is logged to an err file. If a round produces zero responses the skill reports the logs and stops; otherwise it proceeds with the remaining participants.

Why does the final conclusion not mention which models participated?▼

The skill deliberately strips all meta-information such as participant names, headcounts, and agreement status from the final output to prevent authority bias. It greps the conclusion against every name and label in llms.json and rewrites it if any match appears.