菜单
Run the planning stage — write the style guide, design the structure, and produce one brief per chapter. Use after the spec is settled and before any drafting.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/danielrosehill/Claude-Book-Writing-Plugin --skill book-planning命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Run the definition stage of a book project — record the brief verbatim, interview for the gaps, and settle the spec. Use at the start of a book, before any planning or outlining.
Dispatch chapter-writing subagents in parallel batches to draft the book, and handle research where a chapter's sources are not yet gathered. Use once briefs exist. Enforces the batching rule that keeps parallel writers from colliding.
Produce the book's figures — establish the graphics style guide, spec each figure, and generate them. Use after chapters are drafted, in parallel with review.
正在显示 SKILL.md
| name | book-planning |
| description | Run the planning stage — write the style guide, design the structure, and produce one brief per chapter. Use after the spec is settled and before any drafting. |
The stage that makes parallel drafting possible. Everything the writing team does well or badly is decided here.
voice-designer → outline-architect
style guide outline + briefs + manifest
Style guide first: prose conventions affect chapter sizing, and an outline built before the voice is settled gets re-cut.
Three artefacts, and the third carries the load:
guides/style-guide.mdoutline/outline.md — arc, chapter map, boundaries, drafting orderoutline/briefs/<id>-<slug>.md — one contract per chapterPlus the chapter entries in book.toml, which is structure of record.
A chapter writer reads its brief, the style guide, its research notes and the continuity ledger. It reads no other chapter. So everything that would otherwise come from reading adjacent chapters has to be in the brief — including the neighbour summaries and, above all, must not cover.
If briefs are thin, writers compensate by reading, and the architecture collapses back into one large context without anything visibly failing.
Judge a brief by asking: could someone who has never seen this book write this chapter from it, and would the result sit correctly beside its neighbours?
For every pair of chapters that could plausibly both cover something, decide the owner and write it into both briefs — "must cover" in one, "must not cover" in the other. Undecided boundaries are where duplication comes from, and neither writer will notice it.
Populate establishes and requires in book.toml. A chapter may only require
what an earlier chapter establishes.
python3 scripts/book.py scaffold # stub anything the manifest declares
python3 scripts/book.py lint # ordering, duplicates, missing files
Set status = "outline" when done.