restructure-chapterlisted

# Skill: restructure-chapter **What it does.** Takes a chapter that already exists and has a **structural** problem — not a prose problem — reconstructs its obligations from what is on the page, and proposes a new scene architecture. The counterpart of `outline-chapter` for text that already exists. **Triggers** - "restructure chapter X.Y" - "/restructure-chapter X.Y" - "this chapter's problem isn't the sentences" - "chapter X drags in the middle" / "nothing happens in X" - Routed here by `revise-passage` when a passage's problem is upstream, or by `check-arc` / `review-book` when a finding is scene-level - Equivalent phrasing in the project's output language **Input.** The chapter, plus the diagnosis if one exists (a `check-arc` finding, a `review-book` note, or the author's own complaint). If none is given, the skill diagnoses first. **Output.** `{chapter}_restructure.md` next to the chapter — a plan, presented against the current structure. **Never applied to the manuscript.** Once validated, the author executes it, or hands individual scenes to `draft-scene` and `expand-beat`. > **Write the plan in the project's output language.** --- ## Core principle > **Restructuring is diagnosis plus a plan, not a rewrite. The scenes that work are not touched.** This skill exists to close a gap: `check-arc` and `review-book` find structural faults but cannot act on them; `revise-passage` explicitly refuses them ("if more than ~60% needs replacing, the problem is upstream"); `