Plan a novel, novella, or nonfiction narrative book as a durable chapter architecture with POV rules, part structure, chapter jobs, arcs, reveals, continuity state, and target length.
Installs into .claude/skills of the current project.
Are you the author of Book Plan?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-book-plan)
---
name: book-plan
description: Plan a novel, novella, or nonfiction narrative book as a durable chapter architecture with POV rules, part structure, chapter jobs, arcs, reveals, continuity state, and target length.
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---
# Book Plan
## Workflow
1. Read core contract, style rules, story craft, brief, story bible, characters, and world.
2. Decide the book's POV system, tense, approximate target length, and chapter scale only from known requirements or a small reversible assumption.
3. Write `01_story/book_plan.md` with part or sequence architecture when useful.
4. Assign stable `CH-###` chapter IDs. For each chapter record POV, location and time, characters, chapter goal, conflict, turn, outcome, reveal or withheld information, continuity changes, and the causal handoff to the next chapter.
5. Track subplot movement separately so a subplot cannot disappear for accidental stretches.
6. Do not force every chapter to the same word count.
## Done
The plan covers the complete ending, every major arc changes across the book, and a future session can draft any chapter from saved project state without needing chat memory.
