Argumentative Document
Input: $ARGUMENTS
Overview
Build a rigorous argumentative document. Starts from a thesis, constructs supporting arguments with evidence, addresses counterarguments honestly, and produces a document where every claim is supported and every objection is handled.
Steps
Step 1: Define the Thesis
- State as a single, clear, falsifiable claim
- Distinguish from: topic (too broad), question (not a position), opinion (not argued)
- Test: can someone disagree? If not, it’s not a thesis.
- Originality test: is this the most popular/predictable conclusion on this topic? Would someone who had never read commentary reach the same position from the evidence alone? If the thesis is pre-baked — the take everyone already has — find what the evidence actually shows that hasn’t been said.
- Scope: what does this cover and NOT cover?
- Stakes: why does this matter?
Step 2: Identify the Audience
- Who is this for?
- What do they currently believe?
- What would convince them?
- What are their likely objections?
- What shared premises can you build on?
Step 3: Map the Argument Structure
- What are the 3-5 main supporting arguments?
- For each: state as claim, identify evidence, link to thesis
- Order: strongest first? Build gradually? Address objections inline?
- Identify dependencies between arguments
Step 4: Gather and Assess Evidence
For each argument:
- What evidence exists? (data, studies, examples, logic)
- How strong is each piece?
- Sufficient to support the claim?
- Could it be interpreted differently?
- Are you cherry-picking? What evidence goes against you?
Step 5: Address Counterarguments
- List every serious counterargument
- Construct the STRONGEST version of each (steelman)
- For each: refute, concede, or integrate
- Refute: show why it fails with evidence
- Concede: acknowledge, show it doesn’t defeat thesis
- Integrate: show it supports a modified thesis
- If a counterargument defeats your thesis, update the thesis.
- Performed humility check: after writing counterargument sections, delete each “to be sure” / “admittedly” / “of course” paragraph. Is the piece the same or better? If yes, the concession was performance — it existed to look balanced, not to engage honestly. Real concessions change the shape of the argument. Fake ones are padding.
Step 6: Write the Document
- Introduction: context, thesis, roadmap
- Background: shared premises, definitions, scope
- Arguments: each with evidence
- Counterarguments: honest engagement
- Synthesis: how arguments combine
- Conclusion: restate thesis, implications
Standards: every claim has evidence, uncertainty acknowledged, no rhetorical tricks.
Step 7: Verify
- Thesis stated in one sentence and consistent throughout?
- Every argument supports the thesis (not a related claim)?
- Every counterargument addressed?
- Evidence cited accurately?
- Would an opponent feel fairly represented?
- Cached takes check: for each supporting argument, ask — has this exact point appeared in 10,000 other pieces? If yes, either find a fresher argument or acknowledge you’re restating consensus (and explain why it still matters here).
- Relativistic hedging check: does the piece say “some argue X, others Y, the truth is in between” anywhere? If yes, state exactly WHERE in between and WHY. A position paper that doesn’t take a position is not an argument.
When to Use
- Writing persuasive essays, proposals, position papers
- Building a case for a decision
- Preparing debate arguments
Verification
- Thesis clear, falsifiable, consistent throughout
- 3+ supporting arguments with evidence
- Counterarguments steelmanned and addressed
- No unsupported claims
- Honest about uncertainty
- Thesis is not the most predictable take on this topic (pre-baked thesis check)
- Concession paragraphs do real work — deleting any “to be sure” section doesn’t improve the piece
- No cached takes masquerading as original arguments