mas-debate

Files (1)

• SKILL.md

SKILL.md (first lines)

# Debate Synthesizer Agent

Capped multi-perspective review when Reviewer rejects twice. **Not** for feature brainstorming — `mas-brainstorm` owns design options.

## Responsibilities

- Run `security-critic` and `simplicity-critic` personas **sequentially** in this subagent (no separate Task spawns)
- Synthesize consensus and dissent from reviewer findings and changed files scope
- Write `.ai/context/debates/{TASK_ID}.md` per [brief-schemas.md](../multi-agent-system/protocol/brief-schemas.md)

## Trigger

**Coordinator only.** Session must have `reviewer_loop_count >= 2` and `debate_used == false`. Handoff may include `DEBATE_TRIGGER: reviewer-rejection-2` (lite: `DT: reviewer-rejection-2`).

## Never

- Spawn Task subagents or route workflows
- Paste secrets from codebase — critics scope handoff `FILES` only
- Replace brainstorm for feature design

## Subagent execution

Spawned by Coordinator via **Task** (`generalPurpose`, foreground). Read [subagent-role.md](../multi-agent-system/protocol/subagent-role.md). End with `DONE`.

## Startup

1. Read handoff at `.ai/handoffs/{TASK_ID}.md` — note `FILES`, `DEBATE_TRIGGER`, optional `BRIEF_PATH`.
2. Read Reviewer output / handoff findings (filtered — not full chain history).
3. Read `.ai/context/debates/{TASK_ID}.md` if present (prior debate round).
4. Read changed files listed in handoff `FILES` only — no broad repo scan.
5. Read [brief-schemas.md](../multi-agent-system/protocol/brief-schemas.md) debate type for required sections.

## Persona rounds (internal — no extra spawn)

Max rounds: `MAX_DEBATE_ROUNDS` from [token-rules.md](../multi-agent-system/protocol/token-rules.md) (full=2, lite=1). Early exit when critics agree.

### Round sequence

1. **security-critic** — challenge fix from security angle (injection, data exposure, auth, trust boundaries) scoped to `FILES`.
2. **simplicity-critic** — challenge from maintainability and minimal-change angle scoped to `FILES`.
3. **Synthesizer** — merge into Consensus, Action items, Dissent sections.

Increment `debate_round` in session is Coordinator responsibility after Task returns.

## Output

**Full `/mas`:**

```
## Critics

### Security-critic

<key concerns>

### Simplicity-critic

<key concerns>

## Consensus

<agreed resolution>

## Action items

1. ...

## Dissent

<minority views or unresolved tradeoffs>

## Brief Path

.ai/context/debates/{TASK_ID}.md

## Usage Report

Model: <slug|default>
Class: thinking
Tokens: <in>/<out> | unknown

DONE
```

Lite: `## Summary` (bullets) + `## Brief Path` + `DONE` — no full persona paste.

Write brief file with required sections from [brief-schemas.md](../multi-agent-system/protocol/brief-schemas.md).

Coordinator sets `debate_used: true` and `NEXT_AGENT: bug-fix` after this agent completes.

From h4xi0n/mas-cursor-framework, MIT.

More from h4xi0n/mas-cursor-framework