mcpField
M
manage-submission

manage-submission

github.com/vincenzoimpProductivity463 installsUpdated 14w ago
Repository

About manage-submission

A workflow guide for managing paper submissions, review responses, revisions, and camera-ready archives. It is intended for researchers handling venue submissions and requires submitted versions and review records to be preserved in designated directories.

Key features

  1. 01Manage the paper lifecycle by submission event
  2. 02Freeze submitted manuscripts and artifacts in archives
  3. 03Preserve decision letters and reviews verbatim
  4. 04Draft and track responses and revisions by concern
  5. 05Apply camera-ready requirements and archive the result

Use cases

  1. 01Record a submission and preserve its exact manuscript version
  2. 02Organize a decision and prepare point-by-point responses
  3. 03Track manuscript changes against reviewer concerns
  4. 04Prepare and freeze a camera-ready version for a venue

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vincenzoimp/academic-research-skills --skill manage-submission

After installing, type/manage-submissionin Claude Code to confirm it loaded.

Bundled filesreferences/concern-map.md

Details

From the project README

Manage Submission

Operate the lifecycle of papers/<slug>/ around its venue events. The current version always lives in manuscript/; every submitted version is frozen forever in archive/.

Read First

  • papers/README.md — the lifecycle contract
  • papers/<slug>/correspondence/ — current review state
  • references/concern-map.md

Events

Submit. Verify make paper P=<slug> and make check pass and the artifacts bundle is current. Freeze: copy manuscript/ (with its PDF) and artifacts/ into archive/r<N>/ exactly as submitted. Archives are immutable from that moment.

Decision received. Save the decision letter and the reviews verbatim in correspondence/. Summarize the outcome for the user.

Rebuttal. Build the concern map per references/concern-map.md. Draft the response in correspondence/: per concern — direct answer, evidence, and the exact manuscript change it commits to. Get user approval before anything is sent.

Revision. Apply the promised changes to manuscript/, tracking which concern each change answers (concern ids in a change log in correspondence/). New scientific work requested by reviewers goes through develop-contribution first, never directly into prose. Rebuild, re-check, then Submit again as the next round.

Camera-ready. Apply final venue requirements (de-anonymization, format, DOI links), then freeze archive/camera-ready/.

Rules

  • Never edit anything inside archive/.
  • A response letter only promises changes that can actually land in the revision before the deadline.
  • Reviews are private input: they stay inside correspondence/ and are never quoted in public artifacts.

Done When

  • The event is fully recorded — archive frozen and/or correspondence updated — the manuscript state is consistent, and make check passes

Comments

Markdown supported