Academic Research Writing
Overview
Comprehensive toolkit for writing and reviewing computer science research papers. Combines paper writing workflows, manuscript review processes, clarity principles, and formatting standards.
When to Use
Writing Mode:
- Writing new research papers (conference, journal, thesis)
- Creating survey/review papers
- Structuring technical contributions
Review Mode:
- Reviewing/editing existing manuscripts
- Pre-submission polish
- Addressing reviewer comments
- Collaborative editing
Both Modes:
- Improving academic writing clarity
- Preparing IEEE/ACM submissions
- Learning academic writing conventions
Mode Selection
User request received
|
v
Is this about WRITING new content or REVIEWING existing content?
|
+---> Writing new paper -----> Use Writing Workflow
| (references/writing-workflow.md)
|
+---> Reviewing/editing -----> Use Review Workflow
| existing manuscript (references/review-workflow.md)
|
+---> Both/unclear ----------> Start with Review Workflow
to assess, then write
Quick Reference
Writing a Paper
- Clarify scope - topic, venue, format (IEEE/ACM)
- Create outline - section-by-section plan
- Draft core sections - methodology first, then results
- Write supporting sections - intro, related work, discussion
- Add citations - 15-20+ references
- Review & polish - use checklists
See: references/writing-workflow.md
Reviewing a Manuscript
- Extract core message - one sentence summary
- Structural pass - overall organization
- Section reviews - intro, results, discussion
- Scientific clarity - claims, evidence, hedging
- Language polish - terminology, voice
- Formatting check - journal compliance
See: references/review-workflow.md
Core Resources
| Resource |
Purpose |
references/writing-workflow.md |
6-step paper writing process |
references/review-workflow.md |
8-step manuscript review process |
references/narrative-framework.md |
Section-by-section narrative structure (Problem->Solution->Evidence) |
references/clarity-principles.md |
Gopen & Swan sentence-level clarity |
references/academic-phrasebank.md |
Common academic phrases by section |
references/cs-conventions.md |
CS-specific writing conventions |
references/section-checklists.md |
Combined quality checklists |
references/ieee-formatting.md |
IEEE formatting specifications |
references/acm-formatting.md |
ACM formatting specifications |
Templates
| Template |
Purpose |
templates/paper-structure.md |
Introduction arc, results paragraph, discussion templates |
templates/methodology.md |
Core message extraction, structural assessment, language guidelines |
Evaluation
Use evaluators/rubric.json for quality scoring:
- Structure and Organization (weight: 1.0)
- Scientific Rigor (weight: 1.2)
- Language and Clarity (weight: 1.0)
- Section-Specific Quality (weight: 1.0)
- Formatting Compliance (weight: 0.8)
- Citation Quality (weight: 0.8)
Minimum threshold: Average score >= 3.5
Seven Core Principles
- Clarity over cleverness - Scientific clarity beats stylistic elegance
- Narrative shapes comprehension - Structure determines understanding
- Audience dictates tone - Expert vs. general requires different framing
- Format signals credibility - Professional formatting reflects rigor
- Claims require evidence - Strong assertions need strong data
- Each section has a job - Intro sells, Results show, Discussion interprets
- Constraints shape structure - Word limits determine emphasis
Guardrails
Critical requirements:
- Preserve author voice - edit for clarity, don't rewrite
- Claims match data - flag overclaiming immediately
- Quantitative rigor - statistics for all comparisons
- Logical flow - clear transitions between sections
- Appropriate hedging - match evidence strength
- Consistent terminology - same term for same concept
Common pitfalls to avoid:
- Overclaiming ("proves" when data only suggests)
- Missing context (results without interpretation)
- Buried lede (important findings hidden)
- Inconsistent terms (alternating synonyms)
- Vague descriptions ("some increase" vs "3-fold increase")
External Guides
| Guide |
Purpose |
external-guides/how-to-write-a-paper.md |
Practical conference paper structuring guidelines (Introduction paragraphs, experiments, tables/figures) |
PDF Templates
assets/full_paper_template.pdf - IEEE template
assets/interim-layout.pdf - ACM template
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: academic-research-writing3description: Use when writing CS research papers (conference, journal, thesis), reviewing scientific manuscripts, improving academic writing clarity, or preparing IEEE/ACM submissions. Invoke when user mentions paper, manuscript, research writing, journal submission, or needs help with academic structure, formatting, or revision.4---56# Academic Research Writing78## Overview910Comprehensive toolkit for writing and reviewing computer science research papers. Combines paper writing workflows, manuscript review processes, clarity principles, and formatting standards.1112## When to Use1314**Writing Mode:**15- Writing new research papers (conference, journal, thesis)16- Creating survey/review papers17- Structuring technical contributions1819**Review Mode:**20- Reviewing/editing existing manuscripts21- Pre-submission polish22- Addressing reviewer comments23- Collaborative editing2425**Both Modes:**26- Improving academic writing clarity27- Preparing IEEE/ACM submissions28- Learning academic writing conventions2930## Mode Selection3132```33User request received34 |35 v36Is this about WRITING new content or REVIEWING existing content?37 |38 +---> Writing new paper -----> Use Writing Workflow39 | (references/writing-workflow.md)40 |41 +---> Reviewing/editing -----> Use Review Workflow42 | existing manuscript (references/review-workflow.md)43 |44 +---> Both/unclear ----------> Start with Review Workflow45 to assess, then write46```4748## Quick Reference4950### Writing a Paper51521. **Clarify scope** - topic, venue, format (IEEE/ACM)532. **Create outline** - section-by-section plan543. **Draft core sections** - methodology first, then results554. **Write supporting sections** - intro, related work, discussion565. **Add citations** - 15-20+ references576. **Review & polish** - use checklists5859See: `references/writing-workflow.md`6061### Reviewing a Manuscript62631. **Extract core message** - one sentence summary642. **Structural pass** - overall organization653. **Section reviews** - intro, results, discussion664. **Scientific clarity** - claims, evidence, hedging675. **Language polish** - terminology, voice686. **Formatting check** - journal compliance6970See: `references/review-workflow.md`7172## Core Resources7374| Resource | Purpose |75|----------|---------|76| `references/writing-workflow.md` | 6-step paper writing process |77| `references/review-workflow.md` | 8-step manuscript review process |78| `references/narrative-framework.md` | Section-by-section narrative structure (Problem->Solution->Evidence) |79| `references/clarity-principles.md` | Gopen & Swan sentence-level clarity |80| `references/academic-phrasebank.md` | Common academic phrases by section |81| `references/cs-conventions.md` | CS-specific writing conventions |82| `references/section-checklists.md` | Combined quality checklists |83| `references/ieee-formatting.md` | IEEE formatting specifications |84| `references/acm-formatting.md` | ACM formatting specifications |8586## Templates8788| Template | Purpose |89|----------|---------|90| `templates/paper-structure.md` | Introduction arc, results paragraph, discussion templates |91| `templates/methodology.md` | Core message extraction, structural assessment, language guidelines |9293## Evaluation9495Use `evaluators/rubric.json` for quality scoring:96- Structure and Organization (weight: 1.0)97- Scientific Rigor (weight: 1.2)98- Language and Clarity (weight: 1.0)99- Section-Specific Quality (weight: 1.0)100- Formatting Compliance (weight: 0.8)101- Citation Quality (weight: 0.8)102103**Minimum threshold:** Average score >= 3.5104105## Seven Core Principles1061071. **Clarity over cleverness** - Scientific clarity beats stylistic elegance1082. **Narrative shapes comprehension** - Structure determines understanding1093. **Audience dictates tone** - Expert vs. general requires different framing1104. **Format signals credibility** - Professional formatting reflects rigor1115. **Claims require evidence** - Strong assertions need strong data1126. **Each section has a job** - Intro sells, Results show, Discussion interprets1137. **Constraints shape structure** - Word limits determine emphasis114115## Guardrails116117**Critical requirements:**1181. Preserve author voice - edit for clarity, don't rewrite1192. Claims match data - flag overclaiming immediately1203. Quantitative rigor - statistics for all comparisons1214. Logical flow - clear transitions between sections1225. Appropriate hedging - match evidence strength1236. Consistent terminology - same term for same concept124125**Common pitfalls to avoid:**126- Overclaiming ("proves" when data only suggests)127- Missing context (results without interpretation)128- Buried lede (important findings hidden)129- Inconsistent terms (alternating synonyms)130- Vague descriptions ("some increase" vs "3-fold increase")131132## External Guides133134| Guide | Purpose |135|-------|---------|136| `external-guides/how-to-write-a-paper.md` | Practical conference paper structuring guidelines (Introduction paragraphs, experiments, tables/figures) |137138## PDF Templates139140- `assets/full_paper_template.pdf` - IEEE template141- `assets/interim-layout.pdf` - ACM template142143---144> Converted and distributed by [TomeVault](https://tomevault.io/claim/terrytong-git) — claim your Tome and manage your conversions.145<!-- tomevault:4.0:skill_md:2026-04-13 -->