
dialectical-mapping-steelmanning
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.
- Installs
- 127
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/lyndonkl/claude --skill dialectical-mapping-steelmanning- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads dialectical-mapping-steelmanning automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Dialectical Mapping & Steelmanning
Table of Contents
Workflow
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.
Common Patterns
Pattern 1: Temporal Synthesis (Both, Sequenced)
- Structure: Do A first, then B. Or B in some phases, A in others.
- Example: "Speed vs Quality" → Synthesis: Iterate fast early (speed), stabilize before launch (quality). Time-box exploration, then shift to refinement.
- When to use: Positions optimize for different lifecycle stages or contexts.
Pattern 2: Conditional Synthesis (Both, Contextual)
- Structure: A in these situations, B in those situations. Define decision criteria.
- Example: "Centralized vs Decentralized" → Synthesis: Centralize strategy/standards/shared resources, decentralize execution/tactics/experiments. Clear escalation criteria for edge cases.
- When to use: Positions are optimal in different scenarios or scopes.
Pattern 3: Dimensional Separation (Both, Different Axes)
- Structure: Optimize A on one dimension, B on another orthogonal dimension.
- Example: "Simple vs Powerful" → Synthesis: Simple by default (80% use cases), powerful for power users (progressive disclosure, advanced mode). Complexity optional, not mandatory.
- When to use: Tradeoff is false—can achieve both on different dimensions simultaneously.
Pattern 4: Higher-Order Principle (Transcend via Meta-Goal)
- Structure: Both A and B are means to same end. Find better means.
- Example: "Build vs Buy" → Synthesis: Neither—rent/SaaS. Or: Build core differentiator, buy commodity. Higher principle: Maximize value creation per dollar/hour.
- When to use: Binary options are tactics, not ends. Reframe around shared ultimate goal.
Pattern 5: Compensating Controls (Accept A's Risk, Mitigate with B's Safeguard)
- Structure: Lean toward A, add B's protections as guardrails.
- Example: "Move Fast vs Prevent Errors" → Synthesis: Move fast with automated testing, staged rollouts, quick rollback. Accept some errors, contain blast radius.
- When to use: One position clearly better for primary goal, other provides risk mitigation.
Guardrails
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:
- ❌ Strawmanning: "Position A naively believes X" (uncharitable). Instead: "Position A prioritizes Y principle because..."
- ❌ False balance: Steelmanning doesn't require treating bad-faith arguments as if made in good faith. If one position is empirically wrong or logically inconsistent, note this after steelmanning.
- ❌ Mushy middle: "Do a little of both" is not synthesis. Synthesis finds NEW approach, not diluted mix.
- ❌ Ignoring power dynamics: Some debates aren't idea conflicts—they're conflicts of interest. Synthesis may not resolve structural problems.
- ❌ Analysis paralysis: Dialectical mapping is a tool for decision-making, not an end. Set time bounds, converge on synthesis, decide.
Quick Reference
Key resources:
- resources/template.md: Steelmanning template, tradeoff matrix template, synthesis structure
- resources/methodology.md: Advanced techniques (multi-party dialectics, principle hierarchies, Toulmin argumentation for steelmanning, synthesis patterns)
- resources/evaluators/rubric_dialectical_mapping_steelmanning.json: Quality criteria for steelmans and synthesis
Typical workflow time:
- Simple binary debate (2 positions, clear principles): 20-30 minutes
- Complex multi-stakeholder debate: 45-60 minutes
- Strategic frameworks (long-term decisions): 60-90 minutes
When to escalate:
- More than 2 positions (multi-party dialectics)
- Nested tradeoffs (position A itself is a synthesis of A1 vs A2)
- Empirical questions disguised as value debates
- Bad faith arguments (not resolvable via steelmanning) → Use resources/methodology.md for these advanced cases
Inputs required:
- Debate topic: The decision or question being debated
- Position A (Thesis): One side of the binary
- Position B (Antithesis): The opposing side
- Context (optional): Constraints, stakeholders, decision criteria
Outputs produced:
dialectical-mapping-steelmanning.md: Complete analysis with steelmanned positions, tradeoff matrix, synthesis, and recommendations
FAQ
What does the dialectical-mapping-steelmanning skill do?
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.
How do I install dialectical-mapping-steelmanning?
Run npx skills add https://github.com/lyndonkl/claude --skill dialectical-mapping-steelmanning in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/dialectical-mapping-steelmanning/ (personal) or .claude/skills/dialectical-mapping-steelmanning/ (project).
Which AI agents can use dialectical-mapping-steelmanning?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is dialectical-mapping-steelmanning safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains dialectical-mapping-steelmanning?
It is published by lyndonkl in lyndonkl/claude. It has 127 recorded installs.
More from lyndonkl/claude
evaluation-rubrics
lyndonkl/claude
Designs structured scoring tools with explicit criteria, performance scales, and descriptors for consistent, transparent quality assessment. Use when need quality criteria and scoring scales to evaluate work consistently, compare alternatives objectively, set acceptance thresholds, reduce subjective bias, or when user mentions rubric, scoring criteria, quality standards, evaluation framework, inter-rater reliability, or grading/assessing work.
strategy-and-competitive-analysis
lyndonkl/claude
Develops business strategies grounded in rigorous competitive and market analysis using proven frameworks (Good Strategy kernel, Porter's 5 Forces, SWOT, Blue Ocean, Playing to Win, Value Chain Analysis, BCG Matrix). Use when developing strategy (market entry, product launch, expansion, M&A, turnaround), conducting competitive analysis, making strategic decisions (build vs buy, pricing, positioning), planning strategic initiatives, or when user mentions strategy, competitive analysis, Porter's 5 Forces, SWOT, market positioning, or strategic frameworks.
scientific-manuscript-review
lyndonkl/claude
Guides systematic multi-pass review and editing of scientific manuscripts (research articles, reviews, perspectives) to improve clarity, structure, scientific rigor, and reader comprehension. Use when reviewing or editing research manuscripts, journal articles, or perspectives, when user mentions manuscript, paper draft, article, research writing, journal submission, reviewer feedback, or needs to improve scientific writing.
memory-retrieval-learning
lyndonkl/claude
Open the skill to read its SKILL.md instructions.
socratic-teaching-scaffolds
lyndonkl/claude
Open the skill to read its SKILL.md instructions.
grant-proposal-assistant
lyndonkl/claude
Open the skill to read its SKILL.md instructions.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.