Skip to content
Back to skills

Write Book

ASecurity

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.

  • 2 stars
  • 0 votes
  • 3 copies
  • 31 views
  • Added September 9, 2026
ai-agents

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add badgids/Story-Film-Skills --skill write-book --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Write Book?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Write Book
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/badgids-write-book/badge)](https://www.skillsdirectory.com/skills/badgids-write-book)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.