MCPInstall

cw-debate

Run a multi-round deliberation between reviewers. Unlike /cw-panel (which synthesizes), /cw-debate has reviewers respond to each other's arguments across rounds until tensions resolve or reach acknowledged stalemate.

Installs
208
Last 24h
+8
Trending rank
#9734
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/everyinc/compound-writing --skill cw-debate
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads cw-debate automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Debate Review

Orchestrate a structured deliberation between reviewer agents. Reviewers don't just give feedback in parallel—they engage with each other's perspectives, challenge each other's recommendations, and work toward resolution (or acknowledged stalemate).

When to Use /cw-debate vs /cw-panel

UseWhen
/cw-panelYou want multiple perspectives synthesized. Fast. Tensions surfaced for you to decide.
/cw-debateYou want reviewers to actually argue it out. More thorough. Tensions may resolve through deliberation.

Choose /cw-debate when:

  • The piece is high-stakes and worth the extra rounds
  • You want to see how perspectives hold up under challenge
  • You suspect some tensions might resolve if reviewers engaged each other
  • You want proposals and compromises, not just "you decide"

Choose /cw-panel when:

  • You want comprehensive feedback quickly
  • You're comfortable resolving tensions yourself
  • Time/tokens are a concern

The Deliberation Flow

Round 1: Initial Positions

Same as /cw-panel—all reviewers analyze the draft independently.

Round 2: Challenges

The moderator identifies tensions and sends challenges to involved reviewers:

## Challenge: The fishing gear paragraph

**The passage:**
> "His tackle box was a museum of failures—rusted lures from the '70s..."

**hemingway said:**
> "47 words that could be 15. Cut it."

**sedaris said:**
> "This is the most alive moment in the piece. Keep every word."

---

**hemingway:** sedaris argues the specificity earns its place. How do you respond?

**sedaris:** hemingway argues this slows momentum. How do you respond?

Round 3: Responses

Reviewers respond in character. They may:

  • Concede — "On reflection, the detail does earn its place. I withdraw."
  • Hold — "The momentum problem remains. Even good details hurt here."
  • Propose — "Keep the first image, cut the extended list. Satisfies both."

Round 4: Resolution

For each tension:

  • Resolved — Reviewers agree (via concession or proposal)
  • Stalemate — Reviewers hold, fundamental value difference
  • Proposal on table — Compromise offered, writer decides

The moderator may run additional rounds if proposals generate new discussion, but caps at 4 rounds.

The Flow in Practice

1. Load Context

Read ../../references/context-contract.md, the draft, and any available brief, outline, project instructions, feedback, or status metadata. Establish:

  • piece_type
  • audience
  • stage
  • goals

Infer missing context from the draft and request. Do not require .status.yaml.

2. Propose Panel

Same as /cw-panel—propose 4-6 reviewers based on context.

## Proposed Panel for Debate

**Draft:** [title]
**Context:** [piece_type] for [audience], [stage]

| Reviewer | Why |
|----------|-----|
| **[name]** | [Rationale] |
| **[name]** | [Rationale] |

**Note:** Debate works best with reviewers who have natural tensions.
Consider including pairs like:
- hemingway + sedaris (economy vs. specificity)
- reader + hitchcock (orientation vs. mystery)
- sorkin + vonnegut (speed vs. depth)

Proceed with this panel, or adjust?

Wait for user confirmation.

3. Round 1: Run Reviewers

Run all reviewers in parallel when the active platform supports isolated workers and the user's explicit debate request authorizes them. On Claude, use the matching reviewer agents when available; on Codex or another runtime, use the reviewer skills or isolated workers with those lenses. Collect independent outputs.

4. Round 2: Identify Tensions and Generate Challenges

Analyze outputs for conflicts. For each significant tension:

  • Quote the passage
  • Present both positions
  • Generate challenge prompts

Spawn challenged reviewers with the challenge context.

5. Round 3: Collect Responses

Each reviewer responds to their challenge:

  • Concede, Hold, or Propose
  • With reasoning

6. Round 4: Resolution and Additional Rounds

Determine resolution status. If proposals warrant further discussion, run another round (max 4 total).

7. Final Synthesis

Return the debate-moderator's synthesis:

  • Resolved tensions (with how they resolved)
  • Stalemates (with final positions and stakes)
  • Proposals (compromise options)
  • Consensus findings (non-debated)
  • The hard question

Panel Selection for Debate

Debate is most valuable when the panel includes natural tensions:

PairingTension TypeGood For
hemingway + sedarisEconomy vs. SpecificityDeciding what earns its length
reader + hitchcockOrientation vs. MysteryDistinguishing strategic withholding from accidental confusion
reader + hemingwayContext vs. BrevityDeciding what setup a first-time reader needs
reader + sorkinOrientation vs. MomentumGiving readers footing without slowing the piece
mom + hemingwayAccessibility vs. BrevityDeciding what a non-expert audience needs explained
sorkin + sedarisMomentum vs. ObservationPacing of descriptive passages
sorkin + vonnegutSpeed vs. DepthWhen to slow for character
nemesis + sedarisRigor vs. VoiceTone of argument pieces

Recommendation: Include at least one natural tension pair in your panel.

Example Session

User: /cw-debate

Agent: I'll run a deliberation on your draft. Let me read it and propose a panel.

[Reads draft]
[Loads the brief and project context: personal essay, general audience, revision stage]

## Proposed Panel for Debate

**Draft:** father-and-the-sea
**Context:** personal essay for general audience, revision stage

| Reviewer | Why |
|----------|-----|
| **hemingway** | Check economy—personal essays can get overwritten |
| **sedaris** | Find the specific, human, funny moments |
| **sorkin** | Verify pacing through emotional beats |
| **reader** | Trace the first-time reading experience |

**Natural tensions:** hemingway/sedaris (economy vs. specificity),
sorkin/sedaris (momentum vs. observation)

Proceed with this panel, or adjust?

User: yes

Agent: Running Round 1—each reviewer analyzing independently.

[Spawns 4 reviewers in parallel]
[Collects outputs]

Round 1 complete. Analyzing for tensions.

## Tensions Identified

### Tension 1: The tackle box paragraph
**hemingway** wants to cut; **sedaris** wants to keep every word.

### Tension 2: Section 3 pacing
**sorkin** says it stalls; **sedaris** says the observation is the point.

### Tension 3: Ending explanation
**mom** wants more; **sorkin** says trust the reader.

Proceeding to Round 2 with 3 challenges.

[Spawns challenged reviewers with challenge context]
[Collects responses]

## Round 2 Responses

**Tension 1:**
- hemingway: HOLD — "Momentum matters more than any single detail."
- sedaris: PROPOSE — "Keep 'museum of failures' and the pug. Cut the Reagan line."

**Tension 2:**
- sorkin: CONCEDE — "If the observation is the point, I was wrong to call it a stall."
- sedaris: (no concession needed)

**Tension 3:**
- mom: HOLD — "I still don't know what he learned. That's a real gap."
- sorkin: PROPOSE — "One specific image of the lesson. Not explanation—scene."

Proceeding to final synthesis.

## Debate Synthesis

**Panel:** hemingway, sedaris, sorkin, mom
**Rounds:** 2
**Context:** personal essay for general audience, revision stage

---

### Resolved Tensions

**Section 3 pacing**

> [The observation passage]

**Resolution:** Sorkin conceded. The slow pace is intentional and earns its place.
**Recommendation:** Keep as-is. The observation is the point.

---

### Stalemates

*None—all tensions reached resolution or proposal.*

---

### Proposals

**The tackle box paragraph**

> "His tackle box was a museum of failures—rusted lures from the '70s,
> a reel that hadn't worked since Reagan, hooks that had never caught
> anything but his own thumb."

**Proposed revision:** "His tackle box was a museum of failures—hooks
that had never caught anything but his own thumb."

**Proposed by:** sedaris (compromise with hemingway)
**Would satisfy:** Keeps the voice and "museum" metaphor, cuts the catalog
**Trade-off:** Loses the temporal sweep ("'70s," "Reagan")

---

**The ending**

**Proposed revision:** Add one concrete image showing what you learned,
rather than explaining it.

**Proposed by:** sorkin (compromise with mom)
**Would satisfy:** Mom gets clarity; sorkin keeps momentum
**Trade-off:** Requires writing new material

---

### Consensus Findings

| Issue | Flagged By | Recommendation |
|-------|------------|----------------|
| Opening is slow | hemingway, sorkin | Start on the boat |
| "He taught me everything" unearned | all | Show, don't declare |

---

### The Deliberation Summary

**Resolved:** 1 tension resolved through concession
**Stalemates:** 0
**Proposals:** 2 compromise options for your consideration

---

### The Hard Question

> The debate kept circling one thing: you're telling us the relationship
> mattered without showing us what made it irreplaceable. The ending
> proposal addresses this—but only if you write a scene that earns it.

Cost And Scope

Debate is materially slower and more context-intensive than panel because reviewers receive follow-up challenges. Use it for consequential tensions, cap the number of rounds, and prefer cw-panel for routine coverage.

Error Handling

If a reviewer fails to spawn:

  • Note the gap
  • Proceed with available reviewers
  • Tensions involving that reviewer won't be debated

If no tensions identified:

  • Skip to synthesis
  • Report as "No significant tensions—reviewers largely aligned"

If a reviewer doesn't respond to challenge:

  • Treat as implicit HOLD
  • Note non-response in synthesis

If debate goes circular:

  • Moderator calls stalemate after positions repeat
  • Cap at 4 rounds regardless

Relationship to /cw-panel

/cw-panel and /cw-debate share infrastructure:

  • Same reviewer agents
  • Same context loading from the active project and artifact
  • Same panel proposal logic

The difference:

  • /cw-panel → synthesizer (one pass, tensions surfaced)
  • /cw-debate → moderator (multiple rounds, tensions engaged)

A natural workflow: run /cw-panel first for quick feedback, then /cw-debate on specific tensions if you want them argued out.

Lessons

[Skill-specific lessons will be added here as they're captured]

FAQ

What does the cw-debate skill do?

Run a multi-round deliberation between reviewers. Unlike /cw-panel (which synthesizes), /cw-debate has reviewers respond to each other's arguments across rounds until tensions resolve or reach acknowledged stalemate.

How do I install cw-debate?

Run npx skills add https://github.com/everyinc/compound-writing --skill cw-debate in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/cw-debate/ (personal) or .claude/skills/cw-debate/ (project).

Which AI agents can use cw-debate?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is cw-debate safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains cw-debate?

It is published by everyinc in everyinc/compound-writing. It has 208 recorded installs.

More from everyinc/compound-writing

View all →

cw-sedaris

everyinc/compound-writing

Open the skill to read its SKILL.md instructions.

Docs & Writing216 installs

cw-dev-edit

everyinc/compound-writing

Review a draft for big-picture issues in argument, structure, stakes, evidence, and payoff. Use when a piece needs developmental editing, a top-level diagnosis, or substantial restructuring before sentence polish.

cw-final-pass

everyinc/compound-writing

Run a publication-readiness check on a nearly complete piece and deliver a clear ready, almost-ready, or needs-work verdict. Use when the user asks for a final pass, quality gate, or pre-publication check.

Docs & Writing212 installs

cw-brainstorm

everyinc/compound-writing

Help users surface raw material for a piece when they don't have a specific idea yet. Invoke with /cw-brainstorm or when user says they want to explore ideas.

cw-hitchcock

everyinc/compound-writing

Open the skill to read its SKILL.md instructions.

Docs & Writing212 installs

cw-scribe

everyinc/compound-writing

Route open-ended writing work through the smallest useful Compound Writing workflow. Use when the user wants to start, continue, finish, or improve a piece and has not named a more specific skill.

Docs & Writing211 installs

Popular docs & writing skills

View category →

grill-with-docs

mattpocock/skills

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Docs & Writing1.2M installs

lark-markdown

open.feishu.cn

飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。

Docs & Writing778.7K installs

writing-beats

mattpocock/skills

Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Docs & Writing490.7K installs

writing-shape

mattpocock/skills

Writing, exploit: shape raw material into an article, paragraph by paragraph.

Docs & Writing490.2K installs

writing-fragments

mattpocock/skills

Writing, explore: mine raw fragments, no structure yet.

Docs & Writing489.6K installs

writing-for-agents

mattpocock/skills

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Docs & Writing479.3K installs