thinking-steel-manning
Agent skill fromtjboudreaux/cc-thinking-skills
Before rejecting a proposal or reflexively agreeing, build the strongest faithful opposing case, state agreement conditions, then update or reaffirm.
How to install thinking-steel-manning
install thinking-steel-manning
# install the cc-thinking-skills pack with the skills CLI
npx skills add tjboudreaux/cc-thinking-skills# or add only this skill to Claude Code: copy the folder
skills/thinking-steel-manning/
# into
~/.claude/skills/thinking-steel-manning/ (all projects)
.claude/skills/thinking-steel-manning/ (one project)
1# Steel-Manning23**Core rule:** Engage the best form of the opposing case, not a weak one. If your position survives that, reaffirm; if not, update.45## When to Use67- About to reject a proposal, design, or alternative approach.8- Inclined to agree with the user/plan and risk sycophancy — construct the best case *against* first.9- Design review, architecture debate, or conflict where trade-offs are real.10- Validating your own preferred decision before locking it (strongest-countercase check).1112## When NOT to Use1314- Settled fact, security anti-pattern, or violated hard requirement — correct it; do not invent a defense of what is wrong.15- You already agree for stated, weighed reasons — do not perform a fake debate.16- Trivial or fully reversible choices where deliberation cost exceeds downside.17- Live emergency — act first; steel-man in the post-incident review.18- Need definition/assumption cleanup, not opposition — use socratic.19- Need failure scenarios for a plan — use pre-mortem; need attacker paths — use red-team.2021## Procedure22231. **State the target claim or decision** you are about to accept or reject, in one sentence. Name the real alternative if one exists.242. **Extract the core insight** behind the opposing position (or against your preferred path): the legitimate concern even if the proposed solution is wrong.25…
Excerpt shown under the repository's MIT license.
