nature-writinglisted

# Nature-Style Scientific Writing — Router This skill is split into two layers: - A **static layer** under `static/` that holds versioned, reusable content fragments (core stance + workflow, paper-type playbooks, per-section drafting guidance, initial-submission guidance, language-specific rules, per-journal style). - A **dynamic layer** (this file plus `manifest.yaml`) that detects the request's axes and loads only the fragments needed for the current job. Do not try to apply the drafting logic from memory or from this router. Always load fragments from disk as described below. ## Completion intent and scope A manuscript file plus “完成写作 / 帮我写完 / 根据这个文件写”, a project plus “根据项目内容写作”, or a request to fill manuscript placeholders invokes **complete-draft behavior** without a special command. Infer scope from the request, active conversation and document headings; a named section stays that section. A multi-section draft may be completed within its existing scope; a project-only request for a paper supports a full manuscript where evidence permits. Do not infer permission to rewrite from a file attachment alone or a question about its contents. Explicit outline-only, routing-test, review-only, translation, language, and staged-approval requests keep their narrower scope. Read `static/core/evidence-completion.md` through `always_load`. It defines project discovery, evidence retrieval and first-pass completion for all journals. For manuscript work it governs missing-input han