Steel-Manning
Core rule: Engage the best form of the opposing case, not a weak one. If your position survives that, reaffirm; if not, update.
When to Use
- About to reject a proposal, design, or alternative approach.
- Inclined to agree with the user/plan and risk sycophancy — construct the best case against first.
- Design review, architecture debate, or conflict where trade-offs are real.
- Validating your own preferred decision before locking it (strongest-countercase check).
When NOT to Use
- Settled fact, security anti-pattern, or violated hard requirement — correct it; do not invent a defense of what is wrong.
- You already agree for stated, weighed reasons — do not perform a fake debate.
- Trivial or fully reversible choices where deliberation cost exceeds downside.
- Live emergency — act first; steel-man in the post-incident review.
- Need definition/assumption cleanup, not opposition — use socratic.
- Need failure scenarios for a plan — use pre-mortem; need attacker paths — use red-team.
Procedure
- State the target claim or decision you are about to accept or reject, in one sentence. Name the real alternative if one exists.
- Extract the core insight behind the opposing position (or against your preferred path): the legitimate concern even if the proposed solution is wrong.
- Construct the strongest faithful case an informed advocate would make: best evidence, incentives, and failure modes — no mockery, no cherry-picked weak version, no motive attacks. Include base rates or concrete alternatives that could overturn the preferred path when relevant.
- State agreement / overturn conditions. Write one observation or result that would make you accept the opposing case (or abandon your preferred path), and whether you have looked for it.
- Engage that strong version, then decide. Respond to the steel-manned case on the merits. Output one of: accept opposing path, revise synthesis, or reaffirm original with explicit residual risks. Naming the countercase without accept/revise/reaffirm is incomplete. Stop once the decision updates or is reaffirmed with conditions.
Output
claim: <decision or proposal under test>
core_insight: <legitimate concern behind the opposition>
steel_man: <strongest faithful opposing argument>
overturn_if: <concrete observation that would change your mind>
looked_for_overturn: yes | no | partial
response_to_steel_man: <engagement on the merits>
decision: accept_opposing | revise | reaffirm
update: <what changed in belief or plan, or why reaffirm stands>
residual_risks: <what remains even after reaffirm/revise>
Verification
- Falsify / stop: If the "steel man" is weaker than the original or attacks a caricature, rebuild it. If no overturn condition is stated, the check is incomplete. If evidence meets the overturn condition, you must update — reaffirmation is then false.
- Over-application guard: Do not steel-man factual errors or hard constraints. Do not run a full adversarial brief for near-zero-cost reversible choices. Do not use this skill to delay an emergency response.
1---
2name: thinking-steel-manning
3description: Before rejecting a proposal or reflexively agreeing, build the strongest faithful opposing case, state agreement conditions, then update or reaffirm.
4disable-model-invocation: true
5metadata:
6 source: https://skillmd.com/skills/gabrielmoreira/thinking-steel-manning
7---
8
9# Steel-Manning
10
11**Core rule:** Engage the best form of the opposing case, not a weak one. If your position survives that, reaffirm; if not, update.
12
13## When to Use
14
15- About to reject a proposal, design, or alternative approach.
16- Inclined to agree with the user/plan and risk sycophancy — construct the best case *against* first.
17- Design review, architecture debate, or conflict where trade-offs are real.
18- Validating your own preferred decision before locking it (strongest-countercase check).
19
20## When NOT to Use
21
22- Settled fact, security anti-pattern, or violated hard requirement — correct it; do not invent a defense of what is wrong.
23- You already agree for stated, weighed reasons — do not perform a fake debate.
24- Trivial or fully reversible choices where deliberation cost exceeds downside.
25- Live emergency — act first; steel-man in the post-incident review.
26- Need definition/assumption cleanup, not opposition — use socratic.
27- Need failure scenarios for a plan — use pre-mortem; need attacker paths — use red-team.
28
29## Procedure
30
311. **State the target claim or decision** you are about to accept or reject, in one sentence. Name the real alternative if one exists.
322. **Extract the core insight** behind the opposing position (or against your preferred path): the legitimate concern even if the proposed solution is wrong.
333. **Construct the strongest faithful case** an informed advocate would make: best evidence, incentives, and failure modes — no mockery, no cherry-picked weak version, no motive attacks. Include base rates or concrete alternatives that could overturn the preferred path when relevant.
344. **State agreement / overturn conditions.** Write one observation or result that would make you accept the opposing case (or abandon your preferred path), and whether you have looked for it.
355. **Engage that strong version, then decide.** Respond to the steel-manned case on the merits. Output one of: accept opposing path, revise synthesis, or reaffirm original with explicit residual risks. Naming the countercase without accept/revise/reaffirm is incomplete. Stop once the decision updates or is reaffirmed with conditions.
36
37## Output
38
39```text
40claim: <decision or proposal under test>
41core_insight: <legitimate concern behind the opposition>
42steel_man: <strongest faithful opposing argument>
43overturn_if: <concrete observation that would change your mind>
44looked_for_overturn: yes | no | partial
45response_to_steel_man: <engagement on the merits>
46decision: accept_opposing | revise | reaffirm
47update: <what changed in belief or plan, or why reaffirm stands>
48residual_risks: <what remains even after reaffirm/revise>
49```
50
51## Verification
52
53- **Falsify / stop:** If the "steel man" is weaker than the original or attacks a caricature, rebuild it. If no overturn condition is stated, the check is incomplete. If evidence meets the overturn condition, you must update — reaffirmation is then false.
54- **Over-application guard:** Do not steel-man factual errors or hard constraints. Do not run a full adversarial brief for near-zero-cost reversible choices. Do not use this skill to delay an emergency response.