paper-workflow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Paper Workflow

论文工作流

Overview

概述

Use this skill as the routing map for paper work. It does not replace the specialized skills. It tells you which one to use next.

Default assumption: unless the user explicitly names a conference venue, the manuscript should follow the journal-oriented,

Nature

-style workflow.

When writing follows experiments or analysis performed across multiple sessions, freeze a compact handoff first: current paper story, supported findings, unresolved decisions, and the figure list that actually carries those findings.

将本技能作为论文工作的路线指引，它不会替代专业技能，而是告诉你下一步该使用哪项技能。

默认假设：除非用户明确指定会议场地，否则手稿应遵循面向期刊的

Nature

风格工作流。

当写作基于多轮实验或分析成果时，应先整理一份简洁的交接文档：当前论文的核心故事、已验证的研究发现、尚未确定的决策点，以及承载这些发现的图表清单。

Routing Map

路线指引

Use:

```
paper-bootstrap
```
when a project is new, messy, or missing a source of truth
```
nature-portfolio-playbook
```
when the target is
```
Nature
```
,
```
Nature Methods
```
,
```
Nature Biotechnology
```
, or the venue fit among those journals is still unclear
```
scientific-writing
```
when drafting or rewriting sections in prose
```
manuscript-optimizer
```
when the paper's claim structure, evidence chain, terminology, or prose need revision
```
results-section-revision
```
when the Results section is scientifically stable but the subsection flow, paragraph openings, or argument progression still feel jumpy
```
figure-planner
```
when the main bottleneck is figure logic, panel roles, or legend sync
```
citation-verifier
```
when bibliography hygiene or source verification is the bottleneck
```
data-availability
```
when repository plans, accession numbers, source-data coverage, or Data Availability wording are the bottleneck
```
submission-audit
```
when the paper is near submission or resubmission and needs a preflight pass
```
rebuttal-response
```
when reviewer comments exist and a response letter plus aligned manuscript edits are needed
```
conference-paper-writing
```
only when the user explicitly wants a conference paper for venues such as NeurIPS, ICML, ICLR, ACL, AAAI, or COLM

使用：

```
paper-bootstrap
```
：适用于新项目、杂乱无章的项目，或是缺乏可信基准的项目
```
nature-portfolio-playbook
```
：当目标期刊为
```
Nature
```
、
```
Nature Methods
```
、
```
Nature Biotechnology
```
，或是尚未明确上述期刊中哪一个更合适时
```
scientific-writing
```
：用于撰写或重写散文式章节内容
```
manuscript-optimizer
```
：当论文的论点结构、证据链、术语表述或行文需要修订时
```
results-section-revision
```
：当结果部分的科学内容已稳定，但小节逻辑、段落开头或论证推进仍显跳跃时
```
figure-planner
```
：当主要瓶颈在于图表逻辑、面板作用或图例一致性时
```
citation-verifier
```
：当参考文献规范或来源验证是瓶颈时
```
data-availability
```
：当存储库规划、登录号、源数据覆盖范围或数据可用性表述是瓶颈时
```
submission-audit
```
：当论文接近投稿或重新投稿阶段，需要进行预检时
```
rebuttal-response
```
：当收到评审意见，需要撰写回复信并同步修改手稿时
```
conference-paper-writing
```
：仅当用户明确希望撰写会议论文，目标会议如NeurIPS、ICML、ICLR、ACL、AAAI或COLM时

Default Sequence

默认流程

For most journal manuscripts, prefer this order:

```
paper-bootstrap
```
```
nature-portfolio-playbook
```
when venue fit or article type is uncertain

Refresh

notes/project_truth.md

notes/result_summary.md

, and

notes/paper_handoff.md

after any major experimental or figure update

```
scientific-writing
```
or
```
manuscript-optimizer
```
```
figure-planner
```
```
results-section-revision
```
when Results is substantively right but narratively abrupt
```
citation-verifier
```
```
data-availability
```
```
submission-audit
```
```
rebuttal-response
```
after external review

对于大多数期刊手稿，优先遵循以下顺序：

```
paper-bootstrap
```
若不确定期刊适配性或文章类型，使用
```
nature-portfolio-playbook
```

每次重大实验或图表更新后，更新

notes/project_truth.md

、

notes/result_summary.md

和

notes/paper_handoff.md

```
scientific-writing
```
或
```
manuscript-optimizer
```
```
figure-planner
```
当结果部分内容准确但叙事生硬时，使用
```
results-section-revision
```
```
citation-verifier
```
```
data-availability
```
```
submission-audit
```
收到外部评审意见后，使用
```
rebuttal-response
```

Common Mistakes

常见误区

using conference-style writing skills by default for journal manuscripts
polishing sections before the active manuscript source of truth is clear
rewriting the manuscript from experiment memory instead of a current
```
result_summary.md
```
or
```
paper_handoff.md
```
editing figure legends late without rechecking the Results text
leaving repository choice, accession IDs, or source-data coverage until the submission portal is already open
postponing Nature Portfolio article-type or venue-fit decisions until after the paper is mostly rewritten
treating citation formatting as the same thing as citation verification
writing a response letter before deciding the underlying manuscript edits

默认使用会议风格写作技能处理期刊手稿
在明确手稿的可信基准前就开始润色章节
仅凭实验记忆重写手稿，而非参考最新的
```
result_summary.md
```
或
```
paper_handoff.md
```
很晚才编辑图表图例，却未重新核对结果部分的文本
直到投稿系统已打开才确定存储库选择、登录号或源数据覆盖范围
等到手稿基本完成重写后才确定Nature Portfolio的文章类型或期刊适配性
将引用格式设置与引用验证混为一谈
在确定手稿的修改方案前就撰写回复信