Menu
Use when turning research notes into a book structure, chapter tree, and writing plan for a technical guide, orange-book, or whitepaper.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when rendering a technical manuscript into a polished HTML and PDF orange-book with a custom cover, table of contents, book-like spacing, and printable A4 layout.
Use when writing a technical orange-book or handbook that should read like a product manual with explicit judgment, dense tables, and stable chapter structure rather than a polished blog post.
Use when a long-form technical draft is factually decent but still feels generic, too smooth, or too AI-written and needs sharper voice, specificity, and pacing.
Use when preparing a technical book, orange-book, or long-form guide and the draft must be grounded in official documentation, release notes, and a saved evidence ledger before writing starts.
Use when a book project has multiple chapters or sections that can be researched, drafted, or revised in parallel by separate agents without sharing a write target.
Use when drafting a technical orange-book, handbook, or long-form guide that must feel like a knowledgeable human wrote it from use and judgment, not like official docs paraphrased into prose.
| name | mj-book-outline |
| description | Use when turning research notes into a book structure, chapter tree, and writing plan for a technical guide, orange-book, or whitepaper. |
把零散调研，压成一本能继续扩写的章节结构。
开篇先写三句边界：
这一步能明显减少后面的 AI 式堆料。
先有 5-8 个 Part，再往下拆章节。
每个 Part 都要能用一句话解释：
一章只回答一个主问题。
建议每章附 4 个字段：
titlereader_questionwhy_nowmust_have_evidence优先挑这三类章节做样本：
如果读者里有中国开发者，不要把中国内容零碎地塞进所有章节。
更好的方式：