line-editing

# Line Editing ## Overview Own the prose-quality passes that come after structure is settled: the line edit (sentence clarity, rhythm, precision, voice), character-voice differentiation, the copyedit against `style-sheet.md`, a read-aloud pass, and a proof pass on a built copy. Every change is proposed with a before/after and a one-line rationale so the author can accept or reject it. The author's voice is the standard, not the agent's taste. The `better-writing` skill, when installed, is an optional complement for anti-generic checks; this skill does not depend on it. ## Prerequisites A story project with `story.md` and drafted chapters (status `draft` or later). Read `style-sheet.md` if present; if it is missing or thin, build it first with the `voice-style` skill, because the copyedit checks against it. ## When to Use - A chapter's structure is settled and the prose needs polish - Dialogue sounds the same from every speaker - Preparing a manuscript for beta readers, an editor, or submission - The `line`, `copyedit`, or `proof` revision pass is next in `story passes` - NOT for structural, plot, or continuity revision (use `revision-continuity`; line-edit only after those passes, or the polish is wasted) - NOT for setting house style or the voice description (use `voice-style`; this skill applies it) - NOT for scene-level craft such as deep POV, subtext, or exposition strategy (use `scene-craft`) - NOT for acting on external reader notes (use `feedback-triage`) ## Wor...