domains / families / science / resubmit-pipeline

resubmit-pipeline

authentic

Workflow 5: orchestrate a text-only resubmit of a polished paper to a different venue under hard constraints (no new experiments, no bib edits, no framework changes, never overwrite prior submissions). Use when user says \"resubmit pipeline\", \"重投流程\", \"port paper to <new venue>\", \"resubmit to <venue>\", \"tighten paper for resubmission\", or has a rejected/withdrawn paper to move to a different top venue under tight time budget.

When to use

• A theory or system paper was rejected at venue A and you want to resubmit to venue B with tight time budget (≤ 1-2 weeks).
• You have **3 inputs ready**: the polished paper directory at venue A's format, the target venue B's format/template/style files, and the prior reviewer reports.
• You explicitly do **not** want to re-derive theorems, run new experiments, or change the bibliography.

When not to use

• The paper still needs experiments — use `/experiment-bridge` → `/auto-review-loop` first.
• The paper still needs structural rewrites or new sections — use `/paper-writing` (Workflow 3).
• You want to write the rebuttal response itself — use `/rebuttal` (Workflow 4).
• The reviewer feedback demands new theorems or new framework — escalate to user before starting; this skill emits `BLOCKED` with `reason_code: out_of_scope_microedit` if it detects this case.

Skill page

Source