manuscript-cyclelisted

# Manuscript Cycle ## Core Rule Run the Question → Evidence → Draft → Verify → Cite lifecycle end-to-end, and **halt at the first gate that fails** — never draft past an unresolved citation, an unsupported claim, or a failed compile. This skill orchestrates the kit's existing skills and agents; it does not bypass any of their rules. A clean cycle means: every `\cite` resolves, every claim is sourced and calibrated, the log compiles, and a simulated reviewer would sign off. ## When to Use Invoke with `/manuscript-cycle [section]` when: - Taking a section from outline to review-ready in one pass - You want the full discipline loop run for you, with the gates enforced - Running headless (`/manuscript-cycle mode:headless`) over a spec for an unattended draft pass Scope it: `/manuscript-cycle introduction` works one section; `/manuscript-cycle` reads the next not-started section from `MANUSCRIPT_MAP.md → Structure`. ## Process ### Phase 0 — Load & scope 1. Read `MANUSCRIPT_MAP.md` (thesis, contribution, venue, the Structure table) and `CLAUDE.project.md` / `STYLE.md` if present. 2. Pick the target section (argument) and restate it as **a claim a reader could dispute** (the section's Question). 3. Confirm the scope with the author **unless** `mode:headless` (then proceed and report). ### Phase 1 — Outline (argument architecture) 4. If the section's claim/evidence plan is missing from the map, run **`/outline`** for it (or dispatch the `outline-planner` agent). Each section