| name | objection-stress-test |
| description | 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. |
Objection Stress Test
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.
When to Use
The user has an argument, thesis, proposal, or position they believe in and want to harden before presenting it to others. They might say:
- "Stress-test my argument for X"
- "What are the weaknesses in this reasoning?"
- "Play devil's advocate on my proposal"
- "How would a critic attack this position?"
- "Help me prepare for objections to my thesis"
- "Is my argument solid, or am I fooling myself?"
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.
The Consultation
Phase 1: Elicit the Argument
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:
- The central claim (what they're asserting)
- The supporting premises (the logical steps)
- The evidence (data, examples, authorities cited)
- The audience (who needs to be convinced — this shapes which objections matter most)
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.
Phase 2: Generate Objections
Run the argument through all four objection-generation techniques. Each technique produces different kinds of vulnerabilities.
Technique 1: Counterfactual Thinking
"What if this premise were false?"
Take each premise in the user's argument and invert it. Ask:
- If the opposite of Premise A were true, does the conclusion still hold?
- Which premises, if removed, cause the entire argument to collapse?
- Are there plausible scenarios where the key assumptions fail?
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.
Technique 2: Perspective-Taking
How would this look from different philosophical, cultural, or disciplinary viewpoints?
Generate objections from at least three distinct vantage points:
- A different academic discipline (e.g., an economist critiquing a moral argument, a psychologist critiquing an economic one)
- A different cultural or value framework (e.g., collectivist vs. individualist, secular vs. religious, pragmatist vs. deontologist)
- The strongest version of the opposing position (steelman the opposition — not a strawman)
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."
Technique 3: Historical Patterns
How have similar arguments been criticized in the past?
Search for analogues:
- Has this type of argument been made before in a different domain? How was it defeated?
- Are there famous counterexamples that undermine the general principle?
- Does the argument rely on a pattern that has broken before? (e.g., "this has always worked" — until it didn't)
- Is there a known fallacy lurking in the structure? (slippery slope, false dichotomy, appeal to nature, etc.)
Historical patterns reveal that arguments which feel original to their maker are often variants of well-worn positions with well-known failure modes.
Technique 4: The Internal Skeptic
Where are the weakest links? What would YOU attack if you had to defeat this argument?
This is the most uncomfortable technique. Ask:
- Where does the argument rely on the audience not asking a follow-up question?
- Where does the evidence feel thinnest — where is the user most reliant on assertion rather than proof?
- Where does the argument conflate correlation with causation, or anecdote with data?
- What is the strongest single sentence someone could say to make this argument look foolish?
The internal skeptic is the objection the user already suspects but has been avoiding.
Phase 3: Classify by Severity
Organize every objection into four severity levels. This classification is critical — it tells the user where to spend their energy.
Level 1 — Fatal
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:
- It attacks a load-bearing premise with strong evidence
- It reveals a logical contradiction in the argument's structure
- It shows the conclusion does not follow from the premises even if they are true
Level 2 — Substantial
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:
- It identifies a genuine gap in the evidence
- It presents a plausible alternative explanation
- It shows the argument works in some contexts but not others
Level 3 — Clarification
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:
- It misreads the argument because a key term is ambiguous
- It raises a question the argument already answers, just not clearly enough
- It conflates the argument with a weaker version of itself
Level 4 — Peripheral
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.
Phase 4: Coach Response Strategies
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.
Strategy A: Acceptance and Refinement
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.
Strategy B: Demonstrating Compatibility
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.
Strategy C: Revealing Hidden Assumptions in the Objection
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.
Strategy D: Reductio ad Absurdum
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.
Strategy E: Distinction Drawing
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.
Phase 5: Integrate and Revise
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:
- Identify where in the argument it should be addressed (not as a footnote — in the main body)
- Draft the preemptive acknowledgment ("One might object that...")
- Draft the response using the chosen strategy
- Check that the response does not introduce new vulnerabilities
Output
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.
