write-paper
Draft an academic paper from analysis outputs and project materials.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Draft an academic paper from analysis outputs and project materials.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
End-to-end empirical data analysis workflow for R or Python projects.
Find and assess datasets for a research question.
Repository-wide consistency audit for skills, hooks, rules, and docs.
Systematic literature review workflow using parallel librarian agents.
Structured interview and project-spec workflow for new research ideas.
Proofreading workflow for academic manuscripts and papers.
| name | write-paper |
| description | Draft an academic paper from analysis outputs and project materials. |
Draft an academic manuscript from existing analysis outputs. Follows propose-first — the outline is always shown for approval before writing begins.
Input: $ARGUMENTS — a paper title, research question, or from spec to read from quality_reports/specs/.
Read project context:
PROJECT_CONTEXT.md — project name, author, institutionreferences/domain-profile.md — field conventions and target venuesquality_reports/specs/ — research question and identification strategyquality_reports/lit_review_*.md — related literature (if it exists)quality_reports/research_ideation_*.md — hypotheses (if it exists)If no spec exists, ask the user for the core research question before proceeding.
Use references/domain-profile.md to calibrate writing style and section emphasis. A political science paper should not read like an econometrics note; mirror the conventions of the project's field rather than forcing a single voice.
Glob for available outputs:
output/tables/**/*.tex — regression tablesoutput/tables/**/*.html — HTML table versionsoutput/figures/**/*.pdf, output/figures/**/*.png — figuresoutput/**/*.rds, output/**/*.pkl, output/**/*.parquet — saved objectsList what exists. Note any gaps (for example, "no summary statistics table found").
Draft a paper outline using this standard structure:
1. Abstract
2. Introduction
3. Background
4. Data & Methods
5. Results
6. Discussion
7. Appendix
References
The structure is flexible. Default to the outline above unless:
references/domain-profile.md has strong conventions that warrant a different organization.If you deviate from the default, explain why before drafting.
Present the outline with a one-sentence description of each section's content, linking specific output files to each section (for example, "Table 2 -> Section 5, Results"). Do NOT start writing until the user approves the outline or requests changes.
Write in this order (minimizes backtracking):
\input{} or \includegraphics{}. Do NOT copy table content inline.Save to manuscripts/[project-name]-draft.tex (or .qmd if the user prefers Quarto).
Create manuscripts/ directory if it does not exist.
If output format is not already clear from the repo or the user's request, use request_user_input in Plan mode for a single-choice prompt if available; otherwise ask conversationally:
.qmd authoring"Use \input{} for tables and \includegraphics{} for figures — reference the actual files in output/, do not embed content directly.
Before handing off to proofread, review-paper, or revise-paper, run a quick structural check on the saved draft. This is not a substance review — it is a drafting-artifact check.
Read the draft and verify:
\input{...} command in the draft, confirm the referenced file exists in output/.\includegraphics{...} command, confirm the referenced file exists in output/figures/.TODO, FIXME, XXX, [placeholder], [TK], ???, and square-bracketed all-caps tokens such as [PLACEHOLDER].Present the results as a short checklist:
## Structural Smoke Test Results
[OK] Table references: 8/8 resolve
[FAIL] Figure references: 3/4 resolve — missing output/figures/heterogeneity.pdf
[OK] No placeholders found
[OK] Required sections present
[WARN] 4 numeric claims in prose may lack nearby output references — see notes
If the smoke test flags issues, offer to fix them before the next review step.
Inform the user:
proofread — for grammar, typos, layout, and consistencyreview-paper — for a multi-perspective top-journal-style reviewrevise-paper — to apply an approved review report systematicallyvalidate-bib — to check all citations are in the bibliographyquality-gate — to verify every claim in the paper is backed by an output fileoutput/; the paper references them by path.output/, flag it rather than guessing.review-paper.