submission-checklist

Submission Checklist (Pre-submission / Revision / Camera-ready Checklist)

Objective

Break "submission" into an executable, reusable checklist to avoid the typical situation where "low-level errors lead to desk reject / major revision."

This skill is not about writing the main text of a paper, but rather provides the following for these stagesExecutable checklist + templates：

Pre-submission (self-check before submission)
Submission (submission package and system form filling)
Revision / Rebuttal (revision and responses to reviewer comments)
Camera-ready / Proof (camera-ready, proofing stage)

Template files are in templates/：

pre-submission-checklist.md
rebuttal-response-matrix.md
camera-ready-checklist.md
cover-letter.md

When to use

Trigger keywords:

投稿、submission、cover letter、highlights
返修、revision、rebuttal、回复审稿意见
camera-ready、proof、校样
checklist、自检清单

Input (minimum information)

Venue (journal/conference/publisher)
Stage (pre-submission / submission / revision / camera-ready)
Document format (LaTeX/Word/Quarto)

Core meta-rules (easiest to miss)

1) The checklist must be "bound to artifacts"

Each checklist item is not a "suggestion," but can point to a specific file/location:

"Export Figure 2 as 600dpi TIFF" → figures/fig-02/out/fig-02.tiff
"Write the statistical tests clearly" → manuscript/methods.md#统计 or main.tex corresponding paragraph

2) Revision responses must be "traceable"

Each reviewer comment must correspond to:

What change you made (action)
How you responded (reply)
Where the change is (location: page number/line number/section)

Template:templates/rebuttal-response-matrix.md

Delivery suggestion (implementation)

It is recommended to always output one "submission bundle directory":

submission/cover-letter.md
submission/highlights.md
submission/submission-manifest.yml
revision/rebuttal.md(during revision)

And in submission-manifest.yml record whether each key check item is completed.