Stress-test the user's OWN argument by generating objections at all 4 severity levels and coaching responses. Use when someone says 'stress-test my argument', 'what are the weaknesses in my reasoning', 'play devil's advocate', 'find holes in this', 'what objections would I face', 'how would someone attack this position', 'is my argument solid', or 'help me strengthen my case.' Generates objections using counterfactual thinking, perspective-taking, historical patterns, and the internal skeptic, then coaches response strategies.
Stress-test any argument by generating objections at four severity levels and coaching the user through response strategies — drawn from Chapter 3 of Zakery Kline's How to Think.
Kline's core insight: "The strength of an argument lies not only in its logical construction but in its resilience against potential objections." An untested argument is not a strong argument — it is an argument waiting to be dismantled by someone who bothered to look for the cracks.
The user has an argument, thesis, proposal, or position they believe in and want to harden before presenting it to others. They might say:
This is NOT for when the user wants help constructing an argument from scratch (that is a different skill). The user must already have a position. This skill attacks it.
Ask: "Present the argument you want stress-tested. Give me the claim, the key premises, and the evidence you're relying on. Who is the intended audience — academics, a boss, the public, a friend?"
Listen for:
If the argument is vague, push back: "I can't stress-test a vague position. Can you state your argument in one or two sentences as precisely as possible?" Precision is the prerequisite.
Run the argument through all four objection-generation techniques. Each technique produces different kinds of vulnerabilities.
"What if this premise were false?"
Take each premise in the user's argument and invert it. Ask:
This technique finds load-bearing assumptions — the premises the argument cannot survive without. If a premise is load-bearing AND contested, the argument has a structural weakness.
How would this look from different philosophical, cultural, or disciplinary viewpoints?
Generate objections from at least three distinct vantage points:
The goal is not relativism. The goal is to surface blind spots that come from arguing within a single frame. As Kline puts it: "Developing what we might call an 'internal skeptic' — a questioning voice within your own thinking — is essential for rigorous reasoning."
How have similar arguments been criticized in the past?
Search for analogues:
Historical patterns reveal that arguments which feel original to their maker are often variants of well-worn positions with well-known failure modes.
Where are the weakest links? What would YOU attack if you had to defeat this argument?
This is the most uncomfortable technique. Ask:
The internal skeptic is the objection the user already suspects but has been avoiding.
Organize every objection into four severity levels. This classification is critical — it tells the user where to spend their energy.
Challenges the foundations. If this objection holds, the argument collapses entirely. Must be addressed head-on or the argument should be abandoned or fundamentally restructured.
Signs of a Level 1 objection:
Raises significant questions that demand a careful response. The argument can survive this objection, but only if the user has a real answer — not a hand-wave.
Signs of a Level 2 objection:
Indicates that the argument is confusing or ambiguous at a specific point. Addressable through better explanation, more precise language, or an additional qualifier. The argument is not wrong — it is unclear.
Signs of a Level 3 objection:
Minor issues that do not affect the core claim. Worth noting, not worth restructuring the argument to address. A common trap is spending too much energy defending against Level 4 objections while ignoring Level 1 and 2.
For each Level 1 and Level 2 objection, walk the user through the response strategy that fits best. Present the options and help them choose.
The objection is valid. Accept it and modify the argument accordingly. This is the strongest possible response — it shows intellectual honesty and makes the argument harder to attack because the user has already conceded the point.
When to use: The objection reveals a genuine weakness that cannot be explained away.
The objection appears to conflict with the argument but actually does not. Show that both the argument and the objection can be true simultaneously — they operate at different levels, in different contexts, or address different aspects.
When to use: The objection is based on a real observation but misidentifies it as a contradiction.
The objection itself rests on an unstated premise that, once exposed, weakens the objection. Turn the analysis back on the critic: "Your objection assumes X — but why should we accept X?"
When to use: The objection feels powerful but depends on a premise the objector has not defended.
Take the objection seriously and follow its logic to its conclusion. If the objection's principle, applied consistently, leads to absurd or unacceptable consequences, the objection defeats itself.
When to use: The objection relies on a principle that the objector would not apply universally.
The objection conflates two things that are superficially similar but importantly different. Drawing a precise distinction dissolves the apparent force of the objection.
When to use: The objection works by blurring a boundary that matters.
Help the user build the strongest objections directly into the argument — preemptively.
The principle: an argument that acknowledges and addresses its best objections is vastly more persuasive than one that ignores them. The audience thinks, "If they already considered that and have an answer, the argument must be solid."
For each Level 1 and Level 2 objection:
Deliver the Objection Stress Test Report in this structure:
ARGUMENT UNDER TEST
[Restate the user's argument in 2-3 sentences]
OBJECTION REPORT
Level 1 — Fatal (must address)
1. [Objection] — Source technique: [which of the 4 techniques generated it]
Recommended response: [Strategy A/B/C/D/E + brief explanation]
2. [If any additional Level 1 objections]
Level 2 — Substantial (should address)
1. [Objection] — Source technique: [technique]
Recommended response: [Strategy + explanation]
[Continue for all Level 2]
Level 3 — Clarification (clean up language)
- [Brief list of points where the argument needs clearer phrasing]
Level 4 — Peripheral (note and move on)
- [Brief list of minor issues]
REVISED ARGUMENT
[The user's argument rewritten to preemptively handle Level 1 and Level 2 objections, with responses integrated into the body]
After delivering the report, ask: "Do you want to go deeper on any specific objection, or should we run the revised argument through a second pass?"
A second pass often catches new vulnerabilities introduced by the revisions themselves — the strongest arguments survive multiple rounds.