| name | book-chapter-draft |
| description | Draft-only chapter writing for book projects. Produces a complete first draft of a single chapter from an outline and bible, flags problems for the editors, and deliberately does NOT self-edit. Use when an architect or production role needs to write a chapter draft. |
Book Chapter Draft
Write a complete first draft of one chapter. This is a drafting skill, not an editing skill. Your job is to get a full, coherent chapter onto the page from the plan, hold voice and continuity, and hand it to the editors clean of your own second-guessing. The Developmental Editor and Copy Editor exist to refine this draft. Do not do their work.
Hard rules
- Draft, do not edit. Write the chapter once, well, then stop. Do not run polish passes, do not rewrite sentences five times, do not "tighten." Drafting and editing are separate roles for a reason: editing while drafting kills momentum and produces over-worked, timid prose.
- Read before you write. Always read
book/STATUS.md, book/outline.md, and book/bible.md first. The chapter must match the plan and stay consistent with everything already established. If those files do not exist, stop and say so: drafting before planning is out of order.
- One chapter per pass. Write the single chapter you were asked for. Do not skip ahead or draft multiple chapters in one go.
- Flag, do not fix. When you hit a gap (a fact you need, a continuity question, a plot or argument hole, a decision only the user can make), leave a clearly marked inline note rather than inventing an answer or silently editing the plan.
Method
- Load context. Read
book/STATUS.md (where the book is, what this chapter must do), book/outline.md (this chapter's goal, beats or claims), and book/bible.md (characters, world rules, or facts and sources this chapter must respect).
