/research-publish

Role: Principal Investigator (publication) Pipeline position: mid-chain

Formats the paper to the venue template and assembles the submission package — supplementary materials, data / code-availability statement, cover letter, ethics and conflict-of-interest declarations — plus a preprint / archival plan with a DOI and a submission checklist. The operator submits the package; the terminal successor is /research-disseminate, which carries the published work to its audience.

Canonical invocationCopy Anchor Link

/research-publish

With arguments:

/research-publish [--suite-name NAME]

InputsCopy Anchor Link

The paper deliverable and _outputs/review-report.md (the peer-review revisions and its not-judged list).

OutputsCopy Anchor Link

The venue-formatted submission package at a host-natural location (the formatted manuscript + supplementary materials + data / code-availability statement + cover letter + ethics / COI declarations) + _outputs/publication-record.md (including the dated venue-rule register: each rule with its official source page, read date, and submission stage) + a submission checklist.

DownstreamCopy Anchor Link

/research-disseminate (downstream consumer) — the operator performs the submission, then /research-disseminate carries the published work to its audience. When the venue returns revisions, re-run /research-review against the revised paper before rebuilding the package.

Workflow phasesCopy Anchor Link

The command follows the standard /research pipeline workflow:

1. Load context — Read the paper and the review report; pin the venue, cycle, track, and article type, and record each venue rule with its official source page, read date, and submission stage.
2. Verify the Sequence Gate — Confirm _outputs/review-report.md exists and its HIGH-severity revisions are resolved (or the operator has explicitly accepted the residual risk); otherwise halt with Blocked: run /research-review first.
3. Format & package — Carry each venue rule with its source page, read date and submission stage, build on the venue's untouched template, count pages and words the venue's way, and inspect the compiled PDF; then assemble supplementary, data/code availability, cover letter, ethics / COI declarations.
4. Plan the preprint / archival — Record the preprint and DOI plan; build the submission checklist.
5. Update the handoff manifest — Record the submission package and the publication record.
6. Emit the package — the venue-formatted submission package + _outputs/publication-record.md.

Rigor floorCopy Anchor Link

Formatting honors staged disclosure: for a double-blind venue, author, institution, and system identity are stripped to separately-submitted metadata and restored only at the designated camera-ready stage. The archival deposit carries the venue-scaled reproducibility-evidence package (data, code, pinned environment, seeds, hardware log, per-instance results, and figures). For a double-blind venue the supplementary archive and every linked repository or dataset are inspected for identity, not only the manuscript.

Venue rules are sourced and staged. Only the target's own official pages count: a neighboring venue, an earlier cycle, or a sibling track is never a stand-in, and a rebuild for a revision or for camera-ready enforces that stage's limits, not the initial-submission ones. A rule with no official page behind it is asked of the operator and marked not verified against the venue. The venue's template files stay as issued, so a locally written starting file is reported as such. Pages and words are counted the venue's way, with the excluded sections recorded, and each figure and table is checked at the size and format the venue receives.

Failure modesCopy Anchor Link

ExamplesCopy Anchor Link

# Assemble the venue submission package
/research-publish --suite-name <name>

Cross-referencesCopy Anchor Link

• Pipeline overview
• Commands reference