d-laub Scientific Writing (orchestrator)
Overview
A three-stage pipeline from a code+results repo to a manuscript draft. Each stage owns a skill and a durable artifact under docs/writing/<story-slug>/ in the consuming repo. This skill routes to the right stage and resumes from whatever artifacts already exist.
Method backbone — the fifteen steps
The pipeline operationalizes Drake & Han's "How to write a scientific paper in fifteen steps" (PLOS Comput Biol, 2025). Its core discipline: finish the thinking before the phrasing, and write only after the research is done. Full detail — every step, with the caption/CARS/connector-test specifics each stage calls on — is in scientific-writing/fifteen-steps.md. Each stage owns a contiguous block:
| Steps | Stage | Delivers |
|---|---|---|
| 1–2 | Story | main point + two-part narrative arc |
| 3–12 | Outline | method/result/finding lists → CARS intro, findings + problem/response discussion, closing thesis, per-paragraph purpose statements, figures |
| 13–15 | Draft | topic / supporting / concluding sentences |
Cross-cutting, and true of this agent too: generative AI is a Steps-13–15 tool (phrasing), not a Steps-1–12 tool (thinking). Do the intellectual work of shaping each stage's artifact before smoothing prose; never let fluency stand in for a claim you haven't backed.
Stages
| Stage | Skill | Reads | Writes |
|---|---|---|---|
| 1. Story | scientific-writing-story |
the repo | story.md |
| 2. Outline | scientific-writing-outline |
story.md |
outline.md, references.md |
| 3. Draft | scientific-writing-draft |
outline.md, references.md, story.md, style guide |
draft.md |
Routing
- Look in
docs/writing/*/for existing artifacts. - Resume at the first incomplete stage:
- no
story.md→ invokescientific-writing-story. story.mdbut nooutline.md→ invokescientific-writing-outline.outline.mdbut nodraft.md→ invokescientific-writing-draft.draft.mdalready exists → all stages complete; ask the user whether to revisedraft.md(re-enterscientific-writing-draft) or stop.
- no
- If the user names a stage explicitly, honor that.
- Confirm the target story dir with the user when more than one exists.
Approval is the user's verbal confirmation in the conversation, not an on-disk marker. Artifact existence drives which stage you resume at; approval gates advancing from one stage to the next (each stage skill ends with "once the user approves, invoke the next stage").
Always announce which stage you're entering and why before invoking it.