← ClaudeAtlas

dialecticlisted

Decide between options - argue each side to win (independent + grounded), cross-examine, then synthesize a recommendation with the condition that flips it. For real design/architecture decisions.
sgtlaugh/skills · ★ 2 · Code & Development · score 76
Install: claude install-skill sgtlaugh/skills
# /dialectic - argue both sides, then decide Thesis vs antithesis → synthesis. For a real decision between **two or more options**. dialectic argues each option **to win** (not to be fair), grounds each in real code/cost, **cross-examines** them against each other, then an **independent judge** synthesizes. The output is **not "X wins"** - it's the real axis of disagreement, a recommendation, and **the condition that flips it.** **Honest ceiling - trust the map, not the verdict.** A decision *aid*, not an oracle. The **reliable** outputs are the **axis**, the **frame-dependency**, and the **deciding question** - those are structural and hold up. The **recommendation is a tentative lean, a hypothesis to pressure-test** - it inherits the one-pass ceiling: a single advocate round won't reach a deep counter that iterative human probing would (proven - a run can crown the side whose pivot claim its own evidence refutes). So a confident-looking verdict is a **starting point, never the decision**. If it's a call you'll engage deeply anyway, your own iterative reasoning may beat dialectic; reach for it to *map the trade-off fast + name the deciding question*, not to be told the answer. **Why the structure (not just "compare these").** Asking one context to compare options yields lazy both-sides-ism: a hedgy paragraph each, the obvious pick, no teeth. dialectic fixes that with **structural separation** - independent advocates who must win, a rebuttal round that collapses weak claim