mcpField
S
scientific-writing

scientific-writing

github.com/d-laubDocuments037 installsUpdated 2w ago
Repository

About scientific-writing

An orchestrator skill that guides a repository-based scientific manuscript through story, outline, and draft stages. It resumes from existing artifacts and requires user approval before advancing between stages.

Key features

  1. 01三阶段论文写作流程
  2. 02按现有产物恢复写作
  3. 03各阶段对应专用技能
  4. 04阶段审批后再继续
  5. 05遵循十五步写作方法

Use cases

  1. 01从代码和结果整理科学论文故事
  2. 02将研究内容组织为论文提纲
  3. 03根据提纲生成论文初稿

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/d-laub/dlaub-togo --skill scientific-writing

After installing, type/scientific-writingin Claude Code to confirm it loaded.

Bundled filesfifteen-steps.md

Details

From the project README

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:

StepsStageDelivers
1–2Storymain point + two-part narrative arc
3–12Outlinemethod/result/finding lists → CARS intro, findings + problem/response discussion, closing thesis, per-paragraph purpose statements, figures
13–15Drafttopic / 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

StageSkillReadsWrites
1. Storyscientific-writing-storythe repostory.md
2. Outlinescientific-writing-outlinestory.mdoutline.md, references.md
3. Draftscientific-writing-draftoutline.md, references.md, story.md, style guidedraft.md

Routing

  1. Look in docs/writing/*/ for existing artifacts.
  2. Resume at the first incomplete stage:
    • no story.md → invoke scientific-writing-story.
    • story.md but no outline.md → invoke scientific-writing-outline.
    • outline.md but no draft.md → invoke scientific-writing-draft.
    • draft.md already exists → all stages complete; ask the user whether to revise draft.md (re-enter scientific-writing-draft) or stop.
  3. If the user names a stage explicitly, honor that.
  4. 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.

Comments

Markdown supported