argumentationlisted

# Construct Arguments Build rigorous arguments from hypothesis through reasoning to concrete evidence. Every persuasive technical claim follows the same triad: a clear hypothesis states *what* you believe, an argument explains *why* it holds, and examples prove *that* it holds. This skill teaches you to apply that structure to code reviews, design decisions, research writing, and any context where claims need justification. ## When to Use - Writing or reviewing a PR description that proposes a technical change - Justifying a design decision in an ADR (Architecture Decision Record) - Constructing feedback in a code review that goes beyond "I don't like this" - Writing a research argument or technical proposal - Challenging or defending an approach in a technical discussion ## Inputs - **Required**: A claim or position that needs justification - **Required**: Context (code review, design decision, research, documentation) - **Optional**: Audience (peer developers, reviewers, stakeholders, researchers) - **Optional**: Counterarguments or alternative positions to address - **Optional**: Evidence or data available to support the claim ## Procedure ### Step 1: Formulate the Hypothesis State your claim as a clear, falsifiable hypothesis. A hypothesis is not an opinion or a preference -- it is a specific assertion that can be tested against evidence. 1. Write the claim in one sentence 2. Apply the falsifiability test: can someone prove this wrong with evidence? 3. Scope it n