skills/dialectical-mapping-steelmanning/SKILL.md
Applies thesis-antithesis-synthesis reasoning to escape false binary choices by steelmanning opposing positions, mapping their underlying principles and tradeoffs, and synthesizing principled third-way resolutions. Use when debates are trapped in false dichotomies, polarized positions need charitable interpretation, tradeoffs are obscured by binary framing, synthesis beyond "pick one side" is needed, or when users mention steelman arguments, Hegelian dialectic, or resolving seemingly opposed principles.
npx skillsauth add lyndonkl/claude dialectical-mapping-steelmanningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Copy this checklist and track your progress:
Dialectical Mapping Progress:
- [ ] Step 1: Frame the debate
- [ ] Step 2: Steelman Position A (Thesis)
- [ ] Step 3: Steelman Position B (Antithesis)
- [ ] Step 4: Map principles and tradeoffs
- [ ] Step 5: Synthesize third way
- [ ] Step 6: Validate synthesis quality
Step 1: Frame the debate
Identify the topic, the two polarized positions (Thesis vs Antithesis), and the apparent tension. Clarify why this feels like a binary choice. See Common Patterns for typical debate structures.
Step 2: Steelman Position A (Thesis)
Present Position A in its strongest form: underlying principle (what it values), best arguments (strongest case for this position), supporting evidence, and legitimate tradeoffs it accepts. Use resources/template.md for structure. Avoid strawmanning—present version that adherents would recognize as fair.
Step 3: Steelman Position B (Antithesis)
Present Position B in its strongest form with same rigor as Position A. Ensure symmetry—both positions get charitable treatment. See resources/template.md.
Step 4: Map principles and tradeoffs
Create tradeoff matrix showing what each position optimizes for (values) and what it sacrifices (costs). Identify underlying principles (speed, quality, freedom, safety, etc.) and how each position weighs them. For complex cases with multiple principles, see resources/methodology.md for multi-dimensional tradeoff analysis.
Step 5: Synthesize third way
Find higher-order principle or hybrid approach that transcends the binary. The synthesis should honor core values of both positions, create new value (not just compromise), and make new tradeoffs explicit. Use resources/template.md for structure. For advanced synthesis techniques (temporal synthesis, conditional synthesis, dimensional separation), see resources/methodology.md.
Step 6: Validate synthesis quality
Self-assess using resources/evaluators/rubric_dialectical_mapping_steelmanning.json. Check: steelmans are charitable and accurate, principles identified, tradeoffs explicit, synthesis transcends binary (not just compromise), new tradeoffs acknowledged. Minimum standard: Average score ≥ 3.5.
Pattern 1: Temporal Synthesis (Both, Sequenced)
Pattern 2: Conditional Synthesis (Both, Contextual)
Pattern 3: Dimensional Separation (Both, Different Axes)
Pattern 4: Higher-Order Principle (Transcend via Meta-Goal)
Pattern 5: Compensating Controls (Accept A's Risk, Mitigate with B's Safeguard)
Key requirements:
Steelman, not strawman: Present each position as its adherents would recognize. Ask: "Would someone who holds this view agree this is a fair representation?" If not, strengthen it further.
Identify principles, not just preferences: Go deeper than "Side A wants X, Side B wants Y." Find the underlying values each side optimizes for: freedom, safety, speed, equity, efficiency, etc.
Synthesis should transcend, not just compromise: Splitting the difference (50% A, 50% B) is usually weak. Good synthesis finds a new option C that honors both principles at a higher level -- "both-and" thinking rather than "either-or" averaging.
Make tradeoffs explicit: Every synthesis has costs. State what you gain and what you sacrifice vs pure positions. Avoid presenting synthesis as "best of both with no downsides."
Avoid false equivalence: Steelmanning does not require treating both sides as equally correct. One position may have stronger arguments or evidence. Synthesis should reflect this (lean toward the stronger position, add safeguards from the weaker).
Check for false dichotomy: Some "debates" are manufactured. Both A and B may be bad options. Ask: "Is this actually a binary choice, or are we missing option C/D/E?"
Test synthesis with adversarial roles: Before finalizing, inhabit each original position and critique the synthesis. Would a partisan of A or B accept it, or see it as capitulation? If the synthesis cannot survive friendly fire, strengthen it.
Common pitfalls:
Key resources:
Typical workflow time:
When to escalate:
Inputs required:
Outputs produced:
dialectical-mapping-steelmanning.md: Complete analysis with steelmanned positions, tradeoff matrix, synthesis, and recommendationsdevelopment
--- name: zettel-note description: The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-
development
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priority. Emits a `transfer-plan` signal. Use when called by wc-squad-architect (whose transfer work this skill is the engine for) and by the strategists in the populate stage when their candidate is transfer-adjacent rather than a full rebuild.
testing
Reads and updates the FIFA World Cup Fantasy tournament state machine (footballfantasy/context/tournament-state.md) — the temporal backbone tracking phase (pre-tournament → group MD1-3 → R32 → R16 → QF → SF → final), budget ($100m group / $105m knockouts), nation cap (3 group, loosening in knockouts), chips remaining, surviving nations, each owned player's elimination-risk horizon, and deadlines. Validates state on load (count/feasibility checks), applies phase transitions, and appends to the append-only state log (never silent overwrite). Use to load state at the start of a run and to commit state changes after the manager makes a move.
development
Validates and persists FIFA World Cup Fantasy signal files to signals/YYYY-MM-DD-<type>.md. Checks the required frontmatter (type, round, date, emitted_by, confidence, source_urls), range-checks declared numeric signals, confirms every factual claim carries a source URL or "manager-provided", rejects unknown signal types, and refuses to persist a signal that fails validation (logging the failure instead). Keeps the inter-agent signal layer auditable so downstream agents can trust what they read and never re-derive it. Use whenever an agent or skill writes a signal.