paper-writing-suitelisted

# Paper Writing Suite ## Core Mandate Treat paper writing as a **claim-evidence-engineering workflow**, not prose generation. Every major claim must be backed by code, results, notes, or verified citations. If evidence is missing, weaken the claim or mark the gap explicitly. Never invent citations. Fetch BibTeX from arXiv, DOI/Crossref, Semantic Scholar, publisher pages, or official software/documentation sources. If a citation cannot be verified, use an explicit placeholder and tell the user. When the user asks for a full paper, do not stop at an outline. Produce concrete paper artifacts, then iterate. For full-paper work, do not stop at plans for figures or citations. Generate or fetch the concrete assets whenever tools and access allow: image files for non-numeric diagrams, deterministic plot/table files for results, `references.bib` entries for citations, and local paper copies or metadata records for the literature corpus. ## Operating Modes Choose the smallest mode that satisfies the user request. | Mode | Use when | Load first | |---|---|---| | Full-paper mode | Turn a repo, notes, results, and template into a draft or submission package | `references/README.md`, `references/workflow.md`, `references/artifacts.md` | | Story mode | Clarify thesis, gap, contributions, and claims to make or avoid | `references/paper-story.md` | | Section mode | Write or revise Abstract, Introduction, Related Work, Method, Experiments, Limitations, or Conclusion | `references/READ