KyleAMathews / hegelian-dialectic-skill

The Electric Monks — Dialectic Skill *Named after Douglas Adams' machines built to believe things for you* **An agent skill that helps you think better by automating the brutally expensive parts of deep reasoning.** Two AI subagents — the Electric Monks — *believe* fully committed positions on your behalf. A third, the orchestrator, decomposes both arguments into atomic parts, finds cross-domain connections, and synthesizes. The result is a **semi-lattice** — a structure no single linear argument could produce. You operate from a belief-free position above the Monks, analyzing the *structure* of the contradiction rather than being inside either side. This isn't artificial intelligence — it's an **artificial belief system** that frees you to think. **What the output feels like:** Left alone, LLMs produce shallow takes. The dialectic breaks that pattern. As you read through the Monks' committed arguments, connections come to mind — things neither side considered, corrections to their framing, ideas you hadn't articulated yet. You feed these back in. The skill tunes to your thinking more and more with each round, but it also rigorously exposes the contradictions in that thinking — so you get an increasingly full and precise map of your own ideas. Then the skill breaks it apart and reforms it as something richer and more interesting than what you started with. Each synthesis becomes the next round's thesis, and by Round 2–3 the dialectic is operating in territory no single prompt could reach. **Why this works** — thinking well about hard problems has at least three bottlenecks, and they compound: • **Belief.** Once you hold a position, you can't simultaneously entertain its negation at full strength. You hedge, steelman weakly, unconsciously bias the comparison. • **Research breadth.** Surveying a domain's thinkers, history, and adjacent fields takes enormous time. Most people stop too early. • **Structural comparison.** Even with two positions side by side, decomposing them into atomic parts and finding cross-domain connections is cognitively brutal. Most analysis stalls here. LLMs can do all three at a scale and speed humans can't. This skill orchestrates them to do exactly that. When to Use • **You've locked onto a vision and can't genuinely entertain alternatives.** You have a strong thesis — maybe an architecture, a strategy, a life direction — and you want to stress-test it, but you keep steelmanning the other side weakly. • **You're trying to do everything because cutting anything feels like betrayal.** Competing needs all feel equally urgent. You can't triage because every priority has someone counting on it. • **You can argue every side but can't commit to any of them.** You find the question intellectually interesting but "what do *you* actually think?" produces discomfort. You've explored this before without resolution. • **You've optimized a system and suspect you might be optimizing the wrong thing.** Your approach works — you have data to prove it — but the landscape may have shifted and you can't see past your own competence. • **Your own values contradict each other.** You believe multiple things passionately, each feels individually right, but collectively they're impossible. The tension is internal, not external. • **"This is how it's done" has become invisible as an assumption.** You have deep knowledge of how things work, but you suspect it's blinding you to radically different approaches. Works across domains — technical architecture, product strategy, philosophy, personal decisions. Usage The skill works with any coding agent that supports subagent spawning and web search — Claude Code, Cursor, Windsurf, etc. **This is a heavy process by design.** Expect 10–15 minutes per round minimum, and plan for at least 3 rounds. This skill needs the best available model — every phase benefits from maximum reasoning capability. Setup Create a directory to collect your dialectics. Each dialectic gets its own subdirectory — the skill generates several files (context briefing, monk essays, structural analysis, synthesis, dialectic queue). Running a Dialectic • Create a subdirectory for your topic: • Load the skill and give it your question: • Start your coding agent in that directory: The skill will walk you through the elenctic interview, spawn the Monks, and produce the full dialectical trace — all saved as files in the current directory. You can also just run /dialectic to get an introductory help message that walks you through the process. Tips • **You are the co-pilot.** Interrupt, correct, redirect at any point. The Monks will get things wrong. Your corrections are the highest-leverage input in the entire process. • **The first round is calibration.** Don't judge the skill by Round 1. The real insights come in Rounds 2–3, once the process has dug past the obvious framing. • **Say yes to recursion.** When the skill proposes recursive directions after a synthesis, pick one. Each round ratchets up the quality. • **The dialectic queue persists.** The file tracks explored and unexplored contradictions. You can come back to it in a future session and pick up where you left off. How It Works The process has seven phases. Phase 1: Elenctic Interview + Research — surface the real contradiction The orchestrator interviews you Socratically — surfacing hidden assumptions, finding the deepest version of the contradiction, and identifying your belief burden. Then it researches the domain to ground both sides in specifics. The interview surfaces what you're *actually* wrestling with; the research ensures the downstream arguments are grounded in specifics, not generics. Phase 2: Generate Electric Monk Prompts — calibrate the belief assignments The orchestrator crafts two prompts — one per Monk — calibrated to your specific belief burden. Each prompt includes framing corrections that prevent the Monk from falling into the obvious, boring version of the argument, plus ta…