Files
nexus/wiki/concepts/ChapterBlueprint.md

49 lines
1.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: "Chapter Blueprint"
type: concept
tags: ["writing", "structure", "planning", "workflow"]
sources: ["marketing-book-co-author"]
last_updated: 2026-04-30
---
## Definition
章节蓝图Chapter Blueprint是 Book Co-Author Agent 在起草正文之前先定义章节承诺Chapter Promise、读者收益和战略功能的结构化规划工具。它是叙事架构[[Narrative Architecture]])在章节层面的具体化。
## Blueprint Structure
```markdown
## Chapter Promise
- What this chapter proves本章证明什么
- Why the reader should care读者为什么在乎
- Strategic role in the book本章在全书的战略角色
## Section Logic
1. Opening scene or tension开场场景或张力
2. Core argument核心论点
3. Supporting example or lesson支撑案例或教训
4. Shift in perspective视角转换
5. Closing takeaway结尾要点
```
## Why Blueprint Before Drafting
1. **防止主题漂移**:没有蓝图,章节容易同时承载过多论点("tries to do three jobs"
2. **对齐全书定位**:每个章节都服务于作者的品类定位,而非泛化的"好建议"
3. **编辑前置**:蓝图阶段的决策比草稿阶段的修改成本更低
4. **委托方对齐**:蓝图是与委托方确认章节方向的机会,避免方向性返工
## Blueprints vs Traditional Outlines
| 维度 | 章节蓝图 | 传统大纲 |
|------|---------|---------|
| 核心问题 | "本章要证明什么?" | "本章要包含哪些内容?" |
| 视角 | 读者收益导向 | 内容清单导向 |
| 关注点 | 战略功能 | 覆盖范围 |
| 与品类定位关系 | 显式关联 | 隐含关联 |
## Related Concepts
- [[Narrative Architecture]] — 章节蓝图是叙事架构在单章层面的工具
- [[Thought Leadership Book]] — 章节蓝图为思想领导力书籍服务
- [[Ghostwriting]] — 章节蓝图是代笔写作流程的重要组成部分