Draft a novel, novella, or narrative book chapter by chapter from an approved book plan, maintaining POV, character voice, causality, continuity, and a compact running chapter-state record.
Scanned 9/9/2026
Install to Claude Code
npx -y skills add badgids/Story-Film-Skills --skill write-book --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Write Book?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-write-book-story-film-skills)More formats (shields.io, HTML) on the badges page.
---
name: write-book
description: Draft a novel, novella, or narrative book chapter by chapter from an approved book plan, maintaining POV, character voice, causality, continuity, and a compact running chapter-state record.
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---
# Write Book
## Workflow
1. Read core contract, style rules, book plan, canon, and the immediately relevant prior chapter state.
2. Draft one `CH-###` at a time under `01_story/chapters/CH-###.md`.
3. After the chapter, update `01_story/chapter_state.json` with a compact navigation summary, then run `story-state` for durable changes to location, injuries, possessions, character knowledge, relationships, questions, promises/payoffs, prop state, life state, and chronology.
4. Before the next chapter, re-read its plan entry plus the saved state. Do not reread the entire manuscript unless a revision or continuity problem requires it.
5. Use summaries only for navigation. Treat the actual chapter text and canon as authority when wording or facts matter.
6. Run the style checker on every completed chapter.
## Done
Every planned chapter exists through the ending, chapter state and `story_state.json` match the manuscript, and no chapter depends on unsaved conversational memory.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling