Anti-Defensive Writing — скилл

---
name: anti-defensive-writing-en
description: >
  Stops defensive writing across the entire paper lifecycle — writing, revising,
  cutting, and organizing experiments. Treats the paper as a press conference,
  not a project summary, lab log, or self-audit: identify the single most
  publishable strength of the work and build the most favorable, complete, and
  persuasive narrative around it. Never present everything evenly, never volunteer
  weakness, never write an experiment diary, never attack the paper on the
  reviewer's behalf.
  Triggers: polish my paper, revise manuscript, write abstract, write introduction,
  write conclusion, shorten paper, rebuttal, respond to reviewers, organize
  experiments, defensive writing, AI-flavored academic writing.
---

# The Press-Release Principle (Paper as Press Conference)

## One-line principle

A paper is a press conference, not a project summary, a lab log, or a self-audit.
Your job is not to present every aspect of the work evenly, but to identify its
most publishable value and build the most favorable, complete, and persuasive
narrative around it.

## 1. Narrative rules

1. **Organize the paper around strengths only.** Look for what is genuinely ahead,
   unique, or irreplaceable: a new capability, a new problem, a new mechanism, a new
   perspective, broader applicability, lower cost, higher efficiency, better
   scalability, or a more meaningful trade-off. Content that forms no advantage
   does not enter the main storyline.
2. **Do not write a work report.** No "we first did X, then tried Y, and Z failed"
   chronology. Keep only the final standing logic: why the problem matters → why
   existing methods fall short → what this paper provides → how the evidence
   supports it.
3. **Never set a contest you cannot win.** If a metric is not your strength, do not
   build the narrative on it. Re-choose the task definition, evaluation dimension,
   application scenario, constraint, or comparison frame that best reflects your
   value. Name the game this paper actually wins.
4. **State the advantage explicitly.** Do not expect reviewers to discover the
   contribution from a table. Explain: under which condition the method performs
   best, why the advantage emerges, what practical problem it solves, and why it
   deserves attention.
5. **Limit the comparison scope.** Do not chase "wins on every dataset and metric."
   Make only claims your evidence firmly supports. Persuasion comes from tight