Paper Writing
A systematic 11-step workflow for writing academic papers, with section-specific templates and battle-tested writing principles.
When to Use This Skill
- User asks to write or draft a paper or paper section
- User needs LaTeX templates for Abstract, Introduction, Method, Experiments, etc.
- User wants to improve academic writing quality
- User mentions "paper writing", "write introduction", "draft method section", etc.
Artifact Sources
If you used upstream EvoSkills, pull these artifacts before writing:
| Source Skill |
Artifact |
Used In |
paper-planning |
Story summary (task → challenge → insight → contribution → advantage) |
Steps 1-2 (Introduction writing plan) |
paper-planning |
Module Motivation Mapping table |
Step 3 (Method subsections) |
paper-planning |
Experiment plan (comparisons + ablations + demos) |
Step 5 (Experiments section) |
paper-planning |
Pipeline figure sketch |
Steps 1, 6 (Method overview figure) |
paper-planning |
Claim-to-experiment mapping |
Steps 2, 5 (Abstract, Introduction, Experiments) |
paper-planning |
Fallback narrative (if planned) |
Steps 7-8 (Introduction / Conclusion pivot) |
experiment-pipeline |
Stage 1-4 results, ablation tables, trajectory logs |
Step 5 (write experiments) |
experiment-craft |
Failure analysis, implementation tricks |
Step 3 (Method section), Step 9 (limitations) |
The 11-Step Writing Process
Follow these steps in order. Each step builds on the previous one.
- Draw a pipeline figure sketch — Sketch the method's pipeline figure to clarify the overall approach. The figure highlights novelty, not just explanation.
- Design the story and plan experiments — Outline the paper's story (core contribution, module motivations). List comparison experiments and ablation studies. Draft an Introduction writing plan.
- Write Method — Organize the Method writing plan, then draft Method. Run experiments in parallel.
- Revise Introduction and Method — Iterate on both sections while experiments continue.
- Write Experiments — Once experiments are mostly done, organize the Experiments writing plan, then draft.
- Polish figures — Finalize the pipeline figure. Create the teaser figure.
- Write Related Work — List related papers, group into topics, write paragraphs.
- Review the paper — Self-review Introduction, Method, and Experiments. Use the
paper-review skill.
- Write Abstract — Organize the Abstract writing plan, then draft.
- Choose the title — List important keywords, then compose an informative title.
- Iterate — Repeatedly review and revise the entire paper.
Counterintuitive Writing Rules
Apply these rules when aiming for higher acceptance probability:
- Underclaim in prose, overdeliver in evidence: Reduce adjective intensity in Abstract/Introduction; let tables and figures carry the strength.
- State one meaningful limitation early: A controlled limitation statement increases credibility and lowers reviewer suspicion.
- Lead with mechanism, not only metric: Explain why the method works before listing numbers; reviewers trust causal logic more than isolated gains.
- Prefer one decisive figure over many average figures: Build one "cannot-ignore" figure that validates the central claim under hard conditions.
- Remove weak but flashy claims: Any claim without direct evidence should be deleted, even if it sounds impressive.
- Declare scope boundaries explicitly: One sentence in Introduction and Conclusion stating what your method targets reduces reviewer fear of hidden assumptions.
- Show one failure case: Include one representative failure with diagnosis — it signals competence, not weakness.
See references/counterintuitive-writing.md for all 7 tactics with before/after examples.
Section Quick Reference
Abstract
Answer these questions before drafting:
- What technical problem do we solve, and why is there no well-established solution?
- What is our technical contribution?
- Why does our method fundamentally work?
- What is our technical advantage / new insight?
Three template versions: challenge-first, insight-bridge, multi-contribution.
See references/abstract-templates.md
Introduction
Thinking process (reverse then forward):
- Reverse: (1) What is the technical problem? (2) What are our contributions? (3) Benefits and new insights? (4) How to lead into the challenge?
- Forward: (1) Task → (2) Previous methods → challenge → (3) Our contributions → (4) Technical advantages and insights
Four ways to introduce the task, three ways to present challenges, four ways to describe the pipeline.
See references/introduction-templates.md
Anti-pattern: Never write "here is a naive solution, then our improvement" — this makes the work appear incremental.
Method
Every pipeline module needs three elements:
- Module design — Data structure, network design, forward process (given X input, step 1..., step 2..., output Y)
- Motivation — Why this module exists (problem-driven: "A remaining challenge is...")
- Technical advantages — Why this module works well
Start with an Overview paragraph (setting + core contribution + section roadmap), then one subsection per module.
See references/method-templates.md
Experiments
Three key questions to answer:
- How to prove our method is better → comparison experiments
- How to prove our modules are effective → ablation studies
- How to showcase the method's upper limit → demos on challenging data
Ablation studies need: one big table (core contributions) + several small tables (design choices, hyperparameters).
See references/experiments-guide.md
Related Work
Three-step process:
- List papers closely related to our method (most important — missing key references can cause rejection)
- Determine topics based on research direction and algorithm techniques
- Organize writing plan based on listed papers
See references/related-work-guide.md
Conclusion
- Must include Limitation section (reviewers frequently cite "no limitation" as a weakness)
- Limitation = task goal / setting limitations (like future work), NOT technical defects
- Rule: "If our method does not fall below current SOTA metrics, it is not a technical defect"
Supplementary Material
For page-limited venues, decide what goes in main paper vs. supplementary:
- Core evidence for claims must stay in the main paper
- Implementation details, extra ablations, full visual galleries go in supplementary
- Reference supplementary at the point of need, not as a blanket statement
See references/supplementary-guide.md
Core Writing Principles
- One message per paragraph — Each paragraph conveys exactly one point
- Topic sentence first — The first sentence tells readers what this paragraph is about
- Plan before writing — Outline the writing plan, refine each part, then write English sentences
- Flow between sentences — Ensure logical continuity between consecutive sentences
- Terminology consistency — Use the same term throughout; do not alternate names
- Reverse-outlining — After writing, extract the outline from paragraphs; check if the flow is smooth
- Iterate relentlessly — Polish repeatedly, asking whether readers can follow
See references/writing-principles.md
Key Insight
Visual polish directly influences review outcomes. See the paper-planning skill's figure-design.md for the full visual quality guide.
Paper Title Guidelines
- The title attracts specific reviewers — choose keywords carefully
- Before writing the title, list important keywords, then compose
- Title must be informative: include the technique, task, or problem solved
- Avoid generic titles; specific phrases are more memorable
LaTeX Assets
- assets/paper-skeleton.tex — Annotated LaTeX skeleton with section structure
- assets/table-style.tex — Booktabs table macros with color highlighting
Handoff to Review
Before invoking paper-review, verify this checklist:
Section Navigation
| Section |
Reference File |
When to Load |
| Abstract |
abstract-templates.md |
Step 9: Writing abstract |
| Introduction |
introduction-templates.md |
Step 2: Story design |
| Method |
method-templates.md |
Step 3: Writing method |
| Experiments |
experiments-guide.md |
Step 5: Writing experiments |
| Related Work |
related-work-guide.md |
Step 7: Writing related work |
| Writing Principles |
writing-principles.md |
Any time during writing |
| Supplementary |
supplementary-guide.md |
Deciding main vs. supplementary content |
| Counterintuitive strategy |
counterintuitive-writing.md |
Improving reviewer trust and novelty perception |
| Writing Practice |
writing-practice.md |
Building writing ability through deliberate practice |
1---
2name: paper-writing
3description: "Guides writing academic papers section by section using an 11-step workflow with LaTeX templates and counterintuitive writing tactics. Covers Abstract, Introduction, Method, Experiments, Related Work, Conclusion, and Supplementary. Use when: user asks to write or draft a paper section, needs LaTeX templates, wants to improve academic writing quality, optimize novelty framing, or mentions 'write introduction', 'draft method', 'paper writing'. Do NOT use for pre-submission review (use paper-review), experiment execution (use experiment-pipeline), or paper planning/story design (use paper-planning)."
4allowed-tools: "write_file edit_file read_file think_tool"
5metadata:
6 source: https://skillmd.com/skills/evoscientist/paper-writing
7 author: EvoScientist
8 version: '1.0.0'
9 tags: [core, research, writing, academic-writing, latex]
10---
11
12# Paper Writing
13
14A systematic 11-step workflow for writing academic papers, with section-specific templates and battle-tested writing principles.
15
16## When to Use This Skill
17
18- User asks to write or draft a paper or paper section
19- User needs LaTeX templates for Abstract, Introduction, Method, Experiments, etc.
20- User wants to improve academic writing quality
21- User mentions "paper writing", "write introduction", "draft method section", etc.
22
23## Artifact Sources
24
25If you used upstream EvoSkills, pull these artifacts before writing:
26
27| Source Skill | Artifact | Used In |
28|-------------|----------|---------|
29| `paper-planning` | Story summary (task → challenge → insight → contribution → advantage) | Steps 1-2 (Introduction writing plan) |
30| `paper-planning` | Module Motivation Mapping table | Step 3 (Method subsections) |
31| `paper-planning` | Experiment plan (comparisons + ablations + demos) | Step 5 (Experiments section) |
32| `paper-planning` | Pipeline figure sketch | Steps 1, 6 (Method overview figure) |
33| `paper-planning` | Claim-to-experiment mapping | Steps 2, 5 (Abstract, Introduction, Experiments) |
34| `paper-planning` | Fallback narrative (if planned) | Steps 7-8 (Introduction / Conclusion pivot) |
35| `experiment-pipeline` | Stage 1-4 results, ablation tables, trajectory logs | Step 5 (write experiments) |
36| `experiment-craft` | Failure analysis, implementation tricks | Step 3 (Method section), Step 9 (limitations) |
37
38## The 11-Step Writing Process
39
40Follow these steps in order. Each step builds on the previous one.
41
421. **Draw a pipeline figure sketch** — Sketch the method's pipeline figure to clarify the overall approach. The figure highlights novelty, not just explanation.
432. **Design the story and plan experiments** — Outline the paper's story (core contribution, module motivations). List comparison experiments and ablation studies. Draft an Introduction writing plan.
443. **Write Method** — Organize the Method writing plan, then draft Method. Run experiments in parallel.
454. **Revise Introduction and Method** — Iterate on both sections while experiments continue.
465. **Write Experiments** — Once experiments are mostly done, organize the Experiments writing plan, then draft.
476. **Polish figures** — Finalize the pipeline figure. Create the teaser figure.
487. **Write Related Work** — List related papers, group into topics, write paragraphs.
498. **Review the paper** — Self-review Introduction, Method, and Experiments. Use the `paper-review` skill.
509. **Write Abstract** — Organize the Abstract writing plan, then draft.
5110. **Choose the title** — List important keywords, then compose an informative title.
5211. **Iterate** — Repeatedly review and revise the entire paper.
53
54## Counterintuitive Writing Rules
55
56Apply these rules when aiming for higher acceptance probability:
57
581. **Underclaim in prose, overdeliver in evidence**: Reduce adjective intensity in Abstract/Introduction; let tables and figures carry the strength.
592. **State one meaningful limitation early**: A controlled limitation statement increases credibility and lowers reviewer suspicion.
603. **Lead with mechanism, not only metric**: Explain why the method works before listing numbers; reviewers trust causal logic more than isolated gains.
614. **Prefer one decisive figure over many average figures**: Build one "cannot-ignore" figure that validates the central claim under hard conditions.
625. **Remove weak but flashy claims**: Any claim without direct evidence should be deleted, even if it sounds impressive.
636. **Declare scope boundaries explicitly**: One sentence in Introduction and Conclusion stating what your method targets reduces reviewer fear of hidden assumptions.
647. **Show one failure case**: Include one representative failure with diagnosis — it signals competence, not weakness.
65
66See [references/counterintuitive-writing.md](references/counterintuitive-writing.md) for all 7 tactics with before/after examples.
67
68## Section Quick Reference
69
70### Abstract
71
72Answer these questions before drafting:
731. What technical problem do we solve, and why is there no well-established solution?
742. What is our technical contribution?
753. Why does our method fundamentally work?
764. What is our technical advantage / new insight?
77
78Three template versions: challenge-first, insight-bridge, multi-contribution.
79See [references/abstract-templates.md](references/abstract-templates.md)
80
81### Introduction
82
83**Thinking process** (reverse then forward):
84- Reverse: (1) What is the technical problem? (2) What are our contributions? (3) Benefits and new insights? (4) How to lead into the challenge?
85- Forward: (1) Task → (2) Previous methods → challenge → (3) Our contributions → (4) Technical advantages and insights
86
87Four ways to introduce the task, three ways to present challenges, four ways to describe the pipeline.
88See [references/introduction-templates.md](references/introduction-templates.md)
89
90**Anti-pattern**: Never write "here is a naive solution, then our improvement" — this makes the work appear incremental.
91
92### Method
93
94Every pipeline module needs three elements:
951. **Module design** — Data structure, network design, forward process (given X input, step 1..., step 2..., output Y)
962. **Motivation** — Why this module exists (problem-driven: "A remaining challenge is...")
973. **Technical advantages** — Why this module works well
98
99Start with an Overview paragraph (setting + core contribution + section roadmap), then one subsection per module.
100See [references/method-templates.md](references/method-templates.md)
101
102### Experiments
103
104Three key questions to answer:
1051. How to prove our method is better → comparison experiments
1062. How to prove our modules are effective → ablation studies
1073. How to showcase the method's upper limit → demos on challenging data
108
109Ablation studies need: one big table (core contributions) + several small tables (design choices, hyperparameters).
110See [references/experiments-guide.md](references/experiments-guide.md)
111
112### Related Work
113
114Three-step process:
1151. List papers closely related to our method (most important — missing key references can cause rejection)
1162. Determine topics based on research direction and algorithm techniques
1173. Organize writing plan based on listed papers
118
119See [references/related-work-guide.md](references/related-work-guide.md)
120
121### Conclusion
122
123- Must include **Limitation** section (reviewers frequently cite "no limitation" as a weakness)
124- Limitation = task goal / setting limitations (like future work), NOT technical defects
125- Rule: "If our method does not fall below current SOTA metrics, it is not a technical defect"
126
127### Supplementary Material
128
129For page-limited venues, decide what goes in main paper vs. supplementary:
130- Core evidence for claims must stay in the main paper
131- Implementation details, extra ablations, full visual galleries go in supplementary
132- Reference supplementary at the point of need, not as a blanket statement
133
134See [references/supplementary-guide.md](references/supplementary-guide.md)
135
136## Core Writing Principles
137
1381. **One message per paragraph** — Each paragraph conveys exactly one point
1392. **Topic sentence first** — The first sentence tells readers what this paragraph is about
1403. **Plan before writing** — Outline the writing plan, refine each part, then write English sentences
1414. **Flow between sentences** — Ensure logical continuity between consecutive sentences
1425. **Terminology consistency** — Use the same term throughout; do not alternate names
1436. **Reverse-outlining** — After writing, extract the outline from paragraphs; check if the flow is smooth
1447. **Iterate relentlessly** — Polish repeatedly, asking whether readers can follow
145
146See [references/writing-principles.md](references/writing-principles.md)
147
148## Key Insight
149
150Visual polish directly influences review outcomes. See the `paper-planning` skill's [figure-design.md](../paper-planning/references/figure-design.md) for the full visual quality guide.
151
152## Paper Title Guidelines
153
154- The title attracts specific reviewers — choose keywords carefully
155- Before writing the title, list important keywords, then compose
156- Title must be **informative**: include the technique, task, or problem solved
157- Avoid generic titles; specific phrases are more memorable
158
159## LaTeX Assets
160
161- [assets/paper-skeleton.tex](assets/paper-skeleton.tex) — Annotated LaTeX skeleton with section structure
162- [assets/table-style.tex](assets/table-style.tex) — Booktabs table macros with color highlighting
163
164## Handoff to Review
165
166Before invoking `paper-review`, verify this checklist:
167
168- [ ] All sections (Abstract, Introduction, Method, Experiments, Related Work, Conclusion) drafted
169- [ ] Every claim in Abstract/Introduction anchored to a table or figure
170- [ ] Limitation section present in Conclusion
171- [ ] Pipeline figure and teaser figure finalized
172- [ ] All `\todo{}` markers resolved or removed
173
174---
175
176## Section Navigation
177
178| Section | Reference File | When to Load |
179|---------|---------------|--------------|
180| Abstract | [abstract-templates.md](references/abstract-templates.md) | Step 9: Writing abstract |
181| Introduction | [introduction-templates.md](references/introduction-templates.md) | Step 2: Story design |
182| Method | [method-templates.md](references/method-templates.md) | Step 3: Writing method |
183| Experiments | [experiments-guide.md](references/experiments-guide.md) | Step 5: Writing experiments |
184| Related Work | [related-work-guide.md](references/related-work-guide.md) | Step 7: Writing related work |
185| Writing Principles | [writing-principles.md](references/writing-principles.md) | Any time during writing |
186| Supplementary | [supplementary-guide.md](references/supplementary-guide.md) | Deciding main vs. supplementary content |
187| Counterintuitive strategy | [counterintuitive-writing.md](references/counterintuitive-writing.md) | Improving reviewer trust and novelty perception |
188| Writing Practice | [writing-practice.md](references/writing-practice.md) | Building writing ability through deliberate practice |