nature-responselisted

# Nature Reviewer Response — Router This skill is split into two layers: - A **static layer** under `static/` that holds versioned, reusable content fragments (the default stance and red lines, and the response workflow with output format). - A **dynamic layer** (this file plus `manifest.yaml`) that loads the core every time and reaches for the deeper response references only when a step needs them. Do not try to apply the response logic from memory or from this router. Always load fragments from disk as described below. ## Routing protocol Follow these four steps every time the skill is invoked. ### 1. Load the manifest and the core layer Read [manifest.yaml](manifest.yaml). Then read every file listed under `always_load`: - `static/core/stance.md` — the editor-facing purpose, the default stance, the red lines, and the source hierarchy that apply to every response job. - `static/core/workflow.md` — accepted inputs, the ten-step workflow, and the output package format. ### 2. No content axis — identify mode and language inline Unlike nature-writing or nature-figure, nature-response has no fragment axis. Its variation is identified at runtime, not by loading different content bodies: - **task mode** — `draft` / `audit` / `revise` / `triage-only` / `appeal-like`. - **decision type** — minor revision, major revision, revise-and-resubmit, transfer after review, or unclear. - **user language** — if the user writes Chinese, also produce the 中文核对 block. Use `references/i