Why this exists

Design opinions calcify. The tradeoff that justified a decision in month one gets forgotten by month twelve, but the convention keeps shipping anyway — encoded in folder layouts, repeated in code review, defended on reflex. The codebase ends up enforcing a position nobody on the team could still argue for. The Steel Man Bot is the antidote: it forces the strongest possible counter-argument into the room, on a regular cadence, before the original rationale fully decays.

What you get back

  • A ranked list of the load-bearing opinions in your codebase — extracted from comments, commit messages, design docs, and folder structure.
  • The strongest counter-argument for each one, written as if by an engineer who genuinely disagrees with you and is better at this than you expected.
  • A verdict on which opinions survive the challenge and which ones lose on the merits.
  • A refactored version of the code where the counter-argument won, with a written diff of what changed in your thinking and why.

When to reach for this pattern

Run it as pre-rewrite reflection before you commit a quarter to a new direction. Run it before you double down on a contested architecture that keeps generating friction in code review. Run it when a convention has outlived its rationale — when you catch yourself defending a structure because it is the structure, not because you can still name the tradeoff it was solving. The point is not to flip every position. The point is to make sure the ones that survive are the ones that earned it.