| name | paper-publication-orchestrator |
| description | Use when running the complete paper publication pipeline from topic intake to literature search, claim-evidence audit, experiment planning, figure contract, language cleanup, five-reviewer panel, revision, re-review, and submission gate. Coordinates the repository's machine-readable pipeline and stage-specific paper skills. |
Paper Publication Orchestrator
Use this skill as the top-level controller for the full paper workflow. It does
not replace the stage skills; it decides which stage is active, which artifact
is required, and which downstream skill should be invoked next.
The user should not need to name stage skills. Route from intent first, then
load the needed stage skill.
Required Files
- Pipeline definition:
../../pipeline/paper-publication-pipeline.json
- Example intake:
../../examples/mini-paper-intake.json
- Example run record:
../../examples/pipeline-run-record.json
Workflow
- Load
../../pipeline/paper-publication-pipeline.json.
- Identify the user's current entry point: new topic, existing draft, reviewer
comments, or final submission check.
- Create or update a run record with current stage, completed stages, blockers,
and next required gates.
- For each stage, call the listed skill and produce the required artifacts.
- Stop at any non-skippable gate if evidence, citations, figures, data, or
author decisions are missing.
- Before submission, require five-reviewer panel, revision map, and re-review
verification.
- End with a final package checklist and a list of human-review items.
Routing
| Situation | Next Skill |
|---|
| Need current tools or papers | paper-frontier-radar |
| Need claim or citation support | paper-citation-audit |
| Need figure planning | paper-figure-contract |
| Need language, logic, or AI-voice cleanup | paper-language-polishing |
| Need data/code availability | paper-data-availability |
| Draft is complete and needs pressure testing | paper-five-reviewer-panel |
| Reviewer comments need responses | paper-review-response |
| Ready for final package check | paper-submission-gate |
Intent Matching
| User Says | Route |
|---|
| "找方向", "最新论文", "相关仓库", "前沿" | paper-frontier-radar |
| "引用", "参考文献", "claim", "DOI", "BibTeX", "支撑" | paper-citation-audit |
| "画图", "Figure", "配色", "caption", "机械图", "算法对比图" | paper-figure-contract |
| "润色", "翻译", "去 AI", "英文表达", "章节逻辑" | paper-language-polishing |
| "数据声明", "代码开放", "availability", "复现材料" | paper-data-availability |
| "审稿", "5 个审稿人", "reviewer", "投稿前评审" | paper-five-reviewer-panel |
| "回复审稿人", "rebuttal", "response letter", "逐条修改" | paper-review-response |
| "投稿前", "最终检查", "LaTeX", "DOCX", "PDF", "supplement" | paper-submission-gate |
Completion Rules
- Do not mark a stage complete without an artifact or explicit blocker.
- Do not proceed to submission if high-risk review comments remain unresolved.
- Do not hide missing author input; record it in the run record.
- Treat the pipeline JSON as the source of truth for stage order and required
gates.
