paper-spine
Write, rewrite, or build a paper or report (journal, conference, report, review, competition) end to end, then output LaTeX/PDF/Word. Contribution-first, reviewer-aware.
WUBING2023 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add WUBING2023/PaperSpine --skill paper-spine技能说明
name: paper-spine description: Write, rewrite, or build a paper or report (journal, conference, report, review, competition) end to end, then output LaTeX/PDF/Word. The main PaperSpine entry point that orchestrates every step.
PaperSpine Orchestrator
Use this skill as the suite entrypoint. PaperSpine exposes one main skill:
paper-spine. Each stage is executed by reading the corresponding playbook
under references/.
Update detection: If the user asks to update, upgrade, or check for updates,
read references/update.md and execute without starting the full writing
workflow.
Command Routing
| Trigger | Read |
|---|---|
| Default / full workflow | This file (Non-Negotiable Route below) |
resume / continue / "continue from" | references/resume.md |
update / "check for updates" | references/update.md |
submission / "submission materials" | references/submission.md |
audit | references/audit.md |
translate | references/translate.md |
humanize | references/humanize.md |
respond / response letter / reviewer comments | references/respond.md |
For fine-grained stage execution, the orchestrator reads the playbook for each
stage from references/ rather than requiring a separate skill invocation:
| Stage | Playbook |
|---|---|
| Intake / config | references/intake.md |
| Resume / checkpoint | references/resume.md |
| Research | references/research.md |
| Citation | references/citation.md |
| Rewrite | references/rewrite.md |
| Build | references/build.md |
| Humanize | references/humanize.md |
| LaTeX | references/latex.md |
| Translate | references/translate.md |
| Respond | references/respond.md |
| Audit | references/audit.md |
Historical worker skill names (paper-spine-research, etc.) are legacy only
and are not user entry points.
Operating Principle
PaperSpine is a research-writing workflow, not a prose patcher. Its job is to learn the target scene and strong examples first, force a user-confirmed motivation, design the paper row by row, and only then write or rebuild the manuscript.
Never fabricate data, metrics, p-values, datasets, citations, figures, or experimental claims. User materials are authoritative for this paper's results. External examples teach structure and rhetoric only.
Contribution-First, Reviewer-Aware Rules (V4)
These three rules sit above the motivation thread. Motivation remains required, but it supports the contribution rather than replacing it.
- Contribution-First. The manuscript's highest-priority organizing unit is
the confirmed contribution. Do not begin substantive writing until
confirmed_contribution.mdexists (what the paper adds, what problem/gap/ challenge makes it necessary, what evidence validates it, what claim boundary to respect, why a reviewer should find it publishable). Template + per-section checklists:references/contribution.md. Gate:contribution_check.py. - Results-as-Validation. Each major Results subsection must validate at least
one contribution promise; metric-only units with no contribution mapping are a
failure. Record this in
results_validation.md. Template:references/results-validation.md. Gate:results_validation_check.py(journal / conference / competition scenes). - Reviewer-Aware. Before claiming submission-ready, create
reviewer_audit.md(reviewer value map + objection register + editorial fit), populating the objection register from the threestructured_reviewreviewer agents. Template:references/reviewer-audit.md. Gate:reviewer_audit_check.py.
The Stage 12 Final Audit hard gate runs all three checks; do not declare the work complete while any of them fails.
User-Facing Language
When the user writes in Chinese, ui_language=zh, output_language=zh, or
translation_package=zh, all user-facing communication must be in Chinese
throughout the whole run, not only in the final completion report. This includes
intermediate progress updates, status bullets, tool-result summaries, blocked
messages, gate re-run notes, final delivery tables, and error explanations.
Do not write English progress sentences such as "Chinese .docx generated", "Now writing the word report", "All stages passed", "Deliverables", or "PaperSpine Workflow Complete" in those Chinese-facing runs. Use Chinese status phrases instead, for example:
中文 Word 文档已生成:final_paper/paper.zh.docx。正在写入 Word 检查报告并重新运行关卡检查。PaperSpine 工作流已完成全部阶段已通过交付文件清单
Tool names, file paths, command names, and required English manuscript text may remain literal, but explanatory prose around them must be Chinese.
Required Configuration
Prefer reading paper_rewriting_output/paper_spine_config.json. If it is
missing, read references/intake.md and collect configuration.
Required fields:
| Field | Allowed Values |
|---|---|
workflow | rewrite_existing, build_from_materials |
scene | journal, conference, report_review, competition |
tier | flash, pro |
output_language | en, zh |
target_name | free text |
materials_dir | path or empty |
draft_path | path or empty |
user_motivation | free text or empty |
official_urls | list |
special_requirements | list |
word_output | none, docx |
translation_package | none, zh |
reference_mode | local_first, specified_paths, web |
reference_paths | list of local reference folders/files; default ["."] |
citation_target_count | integer; default 20 |
humanize_tier | none, light, medium, heavy |
Non-Negotiable Route
Resume-first rule: Before starting any workflow, read
references/resume.md and run progress_check.py against
paper_rewriting_output/. If earlier stages have produced valid artifacts,
start from the first incomplete stage. After executing that stage, run its gate,
run the full progress check again, and continue until fin