en un clic
paper-spine-build
// Builds a paper or report from materials using the shared PaperSpine research, motivation, and rationale workflow.
// Builds a paper or report from materials using the shared PaperSpine research, motivation, and rationale workflow.
| name | paper-spine-build |
| description | Builds a paper or report from materials using the shared PaperSpine research, motivation, and rationale workflow. |
Use this skill when the user does not have a real manuscript draft yet and instead provides a materials folder with experiment settings, results, figures, notes, PDFs, Word files, TXT/Markdown reports, or partial drafts.
This workflow shares the same research, motivation confirmation, evidence bank,
section blueprint, and writing rationale matrix logic as paper-spine-rewrite.
It is not a separate shortcut.
paper_rewriting_output/paper_spine_config.jsonmaterials_dirpaper_rewriting_output/reference_materials/source_index.mdpaper_rewriting_output/research_dossier.mdpaper_rewriting_output/exemplar_learning_dossier.mdpaper_rewriting_output/style_profile.mdpaper_rewriting_output/sota_gap_map.mdpaper_rewriting_output/confirmed_motivation.md with user confirmationIf research or confirmed motivation is missing, do not draft. Return to
paper-spine-research and ask the user to confirm the motivation after seeing
research-grounded options.
Run or emulate:
python scripts/material_inventory.py <materials_dir> --output-dir paper_rewriting_output
Create source_inventory.md before making claims.
paper_rewriting_output/source_inventory.mdpaper_rewriting_output/evidence_bank.mdpaper_rewriting_output/figure_asset_map.mdpaper_rewriting_output/claim_register.mdpaper_rewriting_output/section_blueprints.mdpaper_rewriting_output/writing_rationale_matrix.mdpaper_rewriting_output/final_paper/main.texpaper_rewriting_output/final_paper/paper.pdf when a TeX engine is availablepaper_rewriting_output/latex_report.mdpaper_rewriting_output/final_artifact_manifest.mdBefore final prose, create writing_rationale_matrix.md and read
references/writing-rationale-matrix.md. The matrix is the build plan. It must
be ordered by the target document's actual writing units, not by a fixed paper
template.
Use this table:
| Row ID | Manuscript Unit | Planned Function | Motivation Link | Reference/SOTA Pattern Learned | Target Scene or Venue Norm | User Evidence or Citation Anchor | Planned Text Move | Final Text Check |
|---|
The first data row must deeply justify the whole-work framework or throughline: why this controlling structure is chosen, how SOTA/target examples informed it, how it follows the confirmed motivation, which user evidence anchors it, and how the final manuscript/report will be checked against it. After that, split the work into the smallest useful units for the selected scene: abstract/summary moves, problem restatement, assumptions, model design, methods choices, result/claim units, review synthesis blocks, validation blocks, recommendations, headings, captions, or other argument-bearing fragments.
No row may be generic. Each row must state why that unit exists and how it is connected to the confirmed motivation, learned examples, target-scene norms, or user evidence. If a paragraph or figure claim needs a separate writing decision, it needs its own row.
figures/
folder and reference them with labels and captions.output_language: en or zh.paper-spine-latex. A Markdown draft is not
a final deliverable for this workflow.paper_rewriting_output/final_paper/.word_output is docx, generate final_paper/paper.docx and run
scripts/word_guard.py, saving paper_rewriting_output/word_report.md.output_language is en and translation_package is zh, create a full
paper_rewriting_output/translation_zh/ package. This includes complete
row-by-row translation of large intermediate files such as
writing_rationale_matrix.md; partial translation or summary translation is
a failure.Read references/build-from-materials.md and
references/writing-rationale-matrix.md before building the manuscript.
Audits PaperSpine outputs for missing artifacts, shallow revisions, logic transfer, unsupported claims, and translation coverage.
Collects PaperSpine workflow options and writes config for flash/pro, scene, language, and inputs.
Handles LaTeX project assembly, figure placement, citations, labels, and compile-safe cleanup.
Researches target requirements, downloads reference materials, learns strong examples, and prepares motivation options.
Rewrites an existing manuscript from confirmed motivation, research, paragraph-level rationale, and evidence.
Orchestrates the PaperSpine suite for motivation-driven paper/report rewriting or building from materials.