Steelman the opposing view
Builds the strongest version of the view opposed to the user's, finds the real cruxes, and lists the evidence that would change each side's mind. Use before a debate, decision or hard conversation.
The user holds a view and wants to test it against the best case on the other side, not the weakest. A steelman is the version of the opposing position that its smartest, best-informed proponents would read and say "yes, that is exactly why we believe it". The aim is better thinking, not winning: after reading, the user should know where the disagreement really lies and what evidence would settle it.
Only if [TOPIC] is given:
- Restate the user's view in one or two neutral sentences. If it is too vague to oppose (for example "I'm right about this"), ask what the view is and stop.
- Identify the strongest opposing position. Prefer the most defensible one over the most common one. If there are several serious camps, steelman the strongest and name the others in one line each.
- Build that position from the inside: its core claim, the values and premises it starts from, its best three to five arguments, and what it explains well that the user's view struggles with.
- Check it against the proponent test: would a thoughtful advocate sign it without edits? Remove anything that is a caricature, a motive attack or an argument they would not make.
- Find the cruxes: the few specific points where, if one side changed its mind, the whole disagreement would shift. Label each as a question of fact, prediction, values or definitions.
- For each side, list concrete, observable evidence or outcomes that should change its mind. Values cruxes cannot be settled by evidence; say what kind of argument or experience could move them instead.
- Name the two or three weakest points in the user's own view that the steelman exposes.
- Argue the opposing case at full strength. Do not water it down with "but of course" asides, and do not slip in a rebuttal.
- Do not declare a winner unless the user asks. Where one side is clearly better supported by evidence, say so plainly instead of inventing balance.
- If the opposing view contradicts well-established facts (for example, that vaccines cause autism), say that the evidence is settled, then steelman the strongest nearby position that reasonable people do hold, or explain why people find the claim persuasive.
- Do not invent studies, statistics, quotes or names. Describe the kind of evidence ("randomised trials of four-day weeks", "historical rent-control cases") and mark specific figures as "check this" unless you are confident they are accurate.
- Be fair to people: describe what proponents believe and why, never what they are "really" after.
- Separate what you verified from what you inferred. Mark inferences as such.
- When you do not know, say "I don't know" once and state what would settle it.
Your view as I read it
One or two sentences.
The strongest opposing view
The position in one bold sentence, then a short paragraph on the premises and values it rests on. Other camps, one line each, if any.
Its best arguments
Numbered, strongest first. Each: the argument, then the best support for it.
Where you really disagree
Table: Crux | Type (fact, prediction, values, definition) | Your side says | Their side says.
What would change minds
Two lists: "Evidence that should move you" and "Evidence that should move them". Concrete and observable.
Pressure points in your view
Two or three bullets.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Productivity and personal life
- category
- Decision-making
- level
- Intermediate
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install steelman-opposing-view --target claude-codenpx skills add hermes-hq/hodios-dist --skill steelman-opposing-view -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-productivity@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Decision-makingThinking partner
Thinking partner who asks sharp clarifying questions, surfaces hidden assumptions and trade-offs, and disagrees openly when reasoning is weak. Use to pressure-test decisions, plans and ideas.
thinking-partnerRun six thinking hats
Explores a problem through the six thinking hats in a disciplined order - facts, feelings, risks, benefits, alternatives and process - and ends with a balanced view and next steps.
run-six-thinking-hatsCompare options with a decision matrix
Builds a weighted decision matrix for your options and criteria, with must-have filters and anchored scores, then tests how sensitive the winner is to the weights before recommending.
compare-options-matrixCompare products before buying
Compares products before a purchase against your needs and budget - must-haves, trade-offs, total cost of ownership and the facts to verify before paying. Use when choosing between products.
compare-purchase-optionsFind logical fallacies in an argument
Finds logical fallacies and weak reasoning in an argument, quoting each passage, naming the flaw, explaining why it fails in context and showing how to repair it, while crediting what is sound.
find-logical-fallaciesMake a group decision
Picks a fitting group decision method - consent, consensus, advice process, dot voting, majority or a leader deciding with input - and writes the facilitation script to reach and record it.
make-group-decision