Skill guide: /write — claim–evidence mapping to manuscript

paper-writing writes manuscript sections from the validated state of the project: the collected sources, the analysis and statistics reports, the design document, the figures. It binds every claim to a session citation [n] or to a session result and discloses what it cannot support.

How to call it

text

/write Write the Methods and Results sections of a manuscript from the literature, design, and analyses in this session, with every claim cited or tied to a session result.

What happens

Reads the session's artifacts — you can watch it load the design report, the statistical report and the literature review before writing.
Writes the sections with a claim–evidence map; numbers come from the structured results, not retyped.
Rebuilds the reference list from the stored sources so it matches the citations exactly, and runs a manuscript check.

The writing turn loads the reports first; the Results section quotes the session's statistics.

What you get

The manuscript (Markdown, editable in the panel), the claim–evidence map, the rebuilt reference list and the manuscript check (unsupported claims, missing citations, mismatched numbers).

The manuscript beside the summary of what was bound to what.

The reference list rebuilt from the session's sources.

Tips

Ask for sections one at a time (Methods and Results first, Discussion next) — each pass reads the latest artifacts.
Deep effort adds a repair loop: the draft is reviewed and revised before it is delivered.
Run /review on the result before submission.