chapter-writing

Installed Root

Resolve the installed reasflow-dev private skills root before running packaged scripts:

REASFLOW_PRIVATE_SKILLS_ROOT="${REASFLOW_PRIVATE_SKILLS_ROOT:-}"
if [ -z "$REASFLOW_PRIVATE_SKILLS_ROOT" ]; then
  if [ -d ./.codex/reasflow-skills ]; then
    REASFLOW_PRIVATE_SKILLS_ROOT="$(pwd)/.codex/reasflow-skills"
  elif [ -d "$HOME/.codex/reasflow-skills" ]; then
    REASFLOW_PRIVATE_SKILLS_ROOT="$HOME/.codex/reasflow-skills"
  else
    echo "reasflow private skills not found in ./.codex/reasflow-skills or $HOME/.codex/reasflow-skills" >&2
    exit 1
  fi
fi

Chapter Writing

Overview

This skill supports paper-subwriter after the assignment contract is already fixed by the prompt. It does not define chapter ownership; it tells the writer how to consume assigned assets correctly.

Installed Paths

Set:

SKILL_ROOT="$REASFLOW_PRIVATE_SKILLS_ROOT/paper/chapter-writing"

Asset Handling Rules

1. .tex: copy the content directly when possible, preserve environments and \label{} tags, and only lightly adapt surrounding connective prose.
2. .bib, .yaml, .yml: keep citation keys stable, merge entries into the chapter-local bibliography flow only when the assignment requests it, and never invent keys.
3. images: wrap in figure environments with \caption{} and \label{fig:...}, then reference them in the text.
4. .md and .txt: convert the substance into academic prose; do not paste markdown syntax into LaTeX.
5. code and experiment reports: describe the algorithm, result, or setting they support; the paper normally cites the artifact outcome, not the source code itself.

Helper Commands

Generate a chapter scaffold with section-level claim placeholders:

python3 "$SKILL_ROOT/scripts/create_chapter_draft.py" \
  --output output/Paper03_SudaMuon/theory.tex \
  --section "Problem Setup::Define setting, notation, and assumptions." \
  --section "Main Result::State theorem and proof roadmap." \
  --section "Proof::Provide complete proof with stable labels."