メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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.
| 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.