adversarial-critique

What problem does it solve?

Use when an implementer is blocked mid-work by a design flaw, contradiction, or unforeseen fork with 2-3 ways to resolve it - produces a defended pick that unblocks the work and leaves an audit trail so the decision can be revisited if it later proves wrong

Core Features & Use Cases

Stress-test a mid-implementation design fork by dispatching sub-agents that argue opposing options across three structured rounds. Produces a defended pick with invariants and acceptance criteria — not a "both approaches work" summary. The artifact left on disk is an audit trail: if the decision proves wrong later, future readers can see exactly why it was made and what was considered.

Quick Start

Run three parallel agent evaluations to generate a complete debate transcript and save it to dev-docs/brainstorms/YYYY-MM-DD-adversarial-critique-debate.md