Use when starting a new manuscript project or cleaning up an existing paper directory under `/data/boom/Papers` and you need a standard structure, active source files, project memory, and venue defaults before deeper writing begins.
Use this skill to make a paper project writable before trying to make it good. The goal is not to generate boilerplate. The goal is to identify the real manuscript source of truth, create only the folders that help the workflow, and lock the project onto the correct venue and contribution framing early.
Default assumption: broad-impact journal work should start from the global Nature-style preference unless the user explicitly overrides the venue.
When the manuscript depends on experiments, figures, or results produced across multiple rounds, initialize lightweight project-state documents early so writing does not depend on memory alone: project_truth.md, decision_log.md, result_summary.md, and paper_handoff.md.
Use the helper script when you need a clean baseline layout quickly:
python ~/.codex/skills/paper-bootstrap/scripts/init_paper_layout.py /data/boom/Papers/<paper>
Use this skill when:
/data/boom/PapersDo not use this skill for:
Nature-style unless the user says otherwisenotes/project_truth.mdnotes/decision_log.mdnotes/result_summary.mdnotes/paper_handoff.mdDo not force this layout mechanically. Use it as the default skeleton when the repository is messy or empty.
input/ for external source material, reviewer comments, and imported filesnotes/ for working notes, claim maps, figure plans, meeting summaries, and lightweight state filesfigures/ for source figures and editable figure assetsoutput/doc/ for active manuscript drafts and exported versionsoutput/review/ for audits, revision memos, and pre-submission checksDefault state files inside notes/ when the project does not already have equivalents:
project_truth.md for the current paper story, active manuscript, central claim, and stable constraintsdecision_log.md for durable framing or scope decisions that future revisions must respectresult_summary.md for experiment-to-manuscript translation of supported findings, weak findings, and figure anchorspaper_handoff.md for the current writing-ready package: what is ready to draft, what still lacks evidence, and which figures or tables carry each pointIf the project already has an established structure, preserve it and map the workflow onto that structure instead of rebuilding everything.
Write project memory only for stable local facts such as:
Do not write project memory for:
result_summary.md and paper_handoff.mdWhen you finish bootstrapping, report: