Argument Mapping

Argument Mapping

Lay out an argument's claims, premises, warrants, and rebuttals as an explicit structure so its strength can be assessed part by part.

Why

Prose hides argumentative structure — a paragraph can feel compelling while its support graph rests on one weak, buried link. Mapping the argument makes every dependency visible and individually attackable.

Use when / Don't use when

• Use when: evaluating or writing a long-form argument; a disagreement keeps circling and mapping both sides would locate the crux.
• Don't use when: the argument is a single inferential step — a direct validity check is faster.

Inputs → Outputs

• Inputs: an argument in prose, yours or someone else's.
• Outputs: a structured map — main claim, premises, warrants, objections and answers — with the weakest link flagged.

Principles

• Every claim is either supported, a supporter of something else, or flagged unsupported.
• The warrant — why this premise supports that claim — is usually the buried weak part prose conceals.
• An argument is only as strong as its weakest necessary link, though independent parallel lines add real robustness.

Procedure

1. Identify the main claim.
2. Extract each supporting reason, noting whether reasons are independent lines or links in one chain.
3. For each link, articulate the warrant — the rule making this premise relevant to that claim.
4. Add known objections and rebuttals at the point where they attach.
5. Mark each node: established, plausible, contested, or unsupported.
6. Identify the crux — the node whose failure would do the most damage.
7. Report the map and the crux as the residual point of highest leverage.

Common mistakes

• Mapping only the supporting side and never the objections that attach to it.
• Treating chained dependencies as independent corroboration, when one broken link takes down the chain.
• Exhaustively mapping minor claims when only the crux actually matters.

Examples

• Mapping a policy memo's structure before an executive review, to find where it's vulnerable.
• Finding the real crux of a week-long technical design disagreement.
• Structuring a legal argument to see which precedent is truly load-bearing.

Related

• [[deductive-validation]] — tests each individual link in the map for whether it actually holds.
• [[argument-construction]] — the generative direction: building a map like this from scratch rather than extracting one from existing prose.
• [[steelmanning]] — often needed before mapping an opposing argument, to ensure the map represents its strongest form.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: skyf0xx
• Source: skyf0xx/better-thinking
• License: MIT
• Homepage: https://zenbin.org/p/better-thinking

Install and usage instructions live in the source repository linked above.