fiction-workshop

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Fiction Workshop

虚构作品工作坊

Editorial workflow for collaborative fiction writing in three stages: Story Bible Building, Chapter Development, and Reader Testing.

协作式虚构写作的编辑工作流分为三个阶段：Story Bible构建、章节开发和读者测试。

When to Use

适用场景

This skill is for:

✅ Long-form fiction (novels, novellas, short story collections)
✅ Multi-chapter manuscripts requiring character/plot consistency
✅ Fiction projects needing developmental or line editing
✅ Stories with complex worldbuilding or multiple POV characters

本技能适用于：

✅ 长篇虚构作品（小说、中篇小说、短篇故事集）
✅ 需要保持角色/情节一致性的多章节手稿
✅ 需要进行发展性或逐行编辑的虚构项目
✅ 拥有复杂世界观或多视角角色的故事

When NOT to Use

不适用场景

This skill is NOT for:

❌ Flash fiction or single scenes (< 2000 words) - too lightweight for the workflow
❌ Poetry or experimental prose - needs different editorial approach
❌ Screenplays or stage plays - different format conventions
❌ Technical writing, documentation, or academic papers
❌ Business writing or marketing copy

For narrative nonfiction (memoir, self-help with story elements), use the

narrative-nonfiction

skill instead.

本技能不适用于：

❌ 闪小说或单一场景（少于2000字）——工作流过于繁重
❌ 诗歌或实验性散文——需要不同的编辑方法
❌ 剧本或舞台剧——格式规则不同
❌ 技术写作、文档或学术论文
❌ 商务写作或营销文案

对于叙事性非虚构作品（回忆录、含故事元素的自助书籍），请使用

narrative-nonfiction

技能。

Editorial Personas

编辑角色

Switch between these roles during Chapter Development by requesting a specific lens:

Role	Invocation	Focus
Developmental Editor	"As developmental editor..."	Plot, pacing, structure, stakes, theme
Line Editor	"As line editor..."	Prose rhythm, word choice, "show don't tell"
Character Consultant	"As character consultant..."	Voice consistency, motivation, arc, relationships
Continuity Tracker	"As continuity tracker..."	Timeline, world facts, internal consistency
Brainstorm Partner	"Brainstorm mode..."	"What if" exploration, problem-solving, unsticking

See

references/

for detailed guidance on each role.

在章节开发阶段，可通过请求特定视角切换以下角色：

角色	调用指令	关注重点
发展性编辑	"以发展性编辑的身份..."	情节、节奏、结构、冲突、主题
逐行编辑	"以逐行编辑的身份..."	行文节奏、措辞、“展示而非告知”原则
角色顾问	"以角色顾问的身份..."	语气一致性、动机、成长弧光、人物关系
连续性追踪员	"以连续性追踪员的身份..."	时间线、世界观设定、内部一致性
头脑风暴伙伴	"进入头脑风暴模式..."	“如果...会怎样”的可能性探索、问题解决、突破瓶颈

详见

references/

目录下各角色的详细指南。

Stage 1: Story Bible Building

阶段1：Story Bible构建

Goal: Establish shared story foundation before drafting or editing.

目标： 在起草或编辑前建立统一的故事基础。

Initial Questions

初始问题

Genre and target reader?
Core premise/logline?
Protagonist: who they are, what they want?
Central conflict?
Reader's intended emotional journey?
How much written vs. planned?

体裁与目标读者？
核心设定/一句话梗概？
主角：身份、诉求？
核心冲突？
读者预期的情感体验？
已完成内容与待规划内容的比例？

Story Bible Components

Story Bible组成部分

Plot: Premise, three-act structure/beat sheet, major turns, ending (even if rough)

Characters: Protagonist (want/need/wound/arc), antagonist (motivation/threat), supporting cast (function/relationships), POV voice notes

World: Setting (time/place/rules), tech/magic systems, social structures, sensory palette

Theme: Central question, moral argument, recurring motifs

If a Story Bible document exists, review it. If not, offer to create one using

assets/story-bible-template.md

Example Story Bible entry (character):

ALEX CHEN - Protagonist
Want: Expose the conspiracy and clear her name
Need: Learn to trust her instincts over institutional authority
Wound: Mentor betrayed her at previous agency, causing career setback
Arc: Lone wolf → realizes she needs allies → builds trust with team
Voice notes: Analytical, dry humor when stressed, avoids emotional language
Key relationship: Tension with Handler (wants to trust, can't fully)

Exit condition: Confident grasp of story fundamentals. Can discuss character motivations, predict plot implications, and identify thematic threads without asking basic questions.

情节： 核心设定、三幕结构/节拍表、关键转折点、结局（即使是粗略版本）

角色： 主角（诉求/需求/创伤/成长弧光）、反派（动机/威胁）、配角（作用/关系）、视角语气说明

世界观： 设定（时间/地点/规则）、科技/魔法体系、社会结构、感官细节

主题： 核心问题、道德立场、反复出现的意象

如果已有Story Bible文档，请进行审核。如果没有，可使用

assets/story-bible-template.md

创建。

Story Bible示例条目（角色）：

ALEX CHEN - Protagonist
Want: Expose the conspiracy and clear her name
Need: Learn to trust her instincts over institutional authority
Wound: Mentor betrayed her at previous agency, causing career setback
Arc: Lone wolf → realizes she needs allies → builds trust with team
Voice notes: Analytical, dry humor when stressed, avoids emotional language
Key relationship: Tension with Handler (wants to trust, can't fully)

退出条件： 充分掌握故事基础内容。无需询问基础问题即可讨论角色动机、预测情节影响、识别主题脉络。

Stage 2: Chapter Development

阶段2：章节开发

Goal: Draft or refine chapters through brainstorm → curate → draft → refine cycles.

Drafting new? → Creation workflow | Editing existing? → Editing workflow

目标： 通过头脑风暴→筛选→起草→优化的循环来起草或完善章节。

起草新内容？ → 创建工作流 | 编辑现有内容？ → 编辑工作流

Creation Workflow

创建工作流

Scene Planning
- What must happen (plot)? Whose POV?
- Chapter's emotional arc?
- What reader learns/feels by end?
Brainstorm Beats (5-15 options): Opening hooks, key moments, dialogue, sensory details, closing

Example (thriller scene): Same car outside coffee shop three days running | Phone buzzing at 3am with blocked caller | Surveillance photo under door | Colleague mentions detail only surveillance would know | Camera lens reflection in window | Dead drop cleaned out | Safe house key doesn't fit | Contact misses first check-in

Then curate: "Which create immediate tension? Combine any?"
Curate: Ask which to keep, combine, or discard. Reasons help calibrate.
Draft: Write chapter. Use
```
str_replace
```
for revisions, never reprint.
Refine: Iterate on feedback. After 3 passes with minimal changes, ask: "What could be cut?"

场景规划
- 必须发生的情节？谁的视角？
- 章节的情感弧光？
- 读者在章节结束时的收获/感受？
头脑风暴情节节点（5-15个选项）：开场钩子、关键场景、对话、感官细节、结尾

示例（惊悚场景）： 咖啡店外连续三天停着同一辆车 | 凌晨3点陌生号码来电 | 门下塞着监控照片 | 同事提及只有监控才能获知的细节 | 窗户反射出镜头光晕 | 秘密交接点已被清空 | 安全屋钥匙无法插入 | 联系人未按时报到

然后筛选：“哪些选项能立即制造紧张感？是否可以组合？”
筛选： 讨论保留、组合或删除哪些选项，理由有助于校准方向。
起草： 撰写章节。使用
```
str_replace
```
进行修订，请勿重印全文。
优化： 根据反馈迭代。经过3次修改且变化微小时，询问：“哪些内容可以删减？”

Editing Workflow

编辑工作流

Read and Diagnose: What chapter tries to do, where it succeeds, where it loses energy/clarity
Invoke Persona: Structure/pacing → Developmental | Prose → Line | Voice → Character | Facts → Continuity
Propose Changes: Specific, surgical edits with brief "why"
Implement: Use
```
str_replace
```
. Link to file after changes.
Iterate: Until chapter achieves purpose

阅读与诊断： 分析章节的目标、成功之处、缺乏活力/清晰度的地方
调用角色： 结构/节奏 → 发展性编辑 | 行文 → 逐行编辑 | 语气 → 角色顾问 | 设定 → 连续性追踪员
提出修改建议： 具体、精准的修改，并简要说明“原因”
实施： 使用
```
str_replace
```
。修改后链接至文件。
迭代： 直到章节达成目标

Role-Specific Guidance

角色专属指南

When a specific editorial persona is invoked, load the corresponding reference file:

Developmental editing →
```
references/developmental-editing.md
```
Line editing →
```
references/line-editing.md
```
Character work →
```
references/character-work.md
```
Continuity →
```
references/continuity-tracking.md
```
Brainstorming →
```
references/brainstorming.md
```
Thriller-specific craft →
```
references/thriller-craft.md
```
Sci-fi worldbuilding →
```
references/scifi-worldbuilding.md
```

当调用特定编辑角色时，加载对应的参考文件：

发展性编辑 →
```
references/developmental-editing.md
```
逐行编辑 →
```
references/line-editing.md
```
角色工作 →
```
references/character-work.md
```
连续性追踪 →
```
references/continuity-tracking.md
```
头脑风暴 →
```
references/brainstorming.md
```
惊悚体裁技巧 →
```
references/thriller-craft.md
```
科幻世界观构建 →
```
references/scifi-worldbuilding.md
```

Stage 3: Reader Testing

阶段3：读者测试

Goal: Verify manuscript works without author context.

Using fresh sub-agent (no story bible):

Comprehension: Can they summarize plot, understand motivations, identify stakes?
Engagement: Where did they lose interest, have questions, feel confused?
Emotional: Did key moments land? Ending satisfying? Theme clear?

Common issues: Unclear motivation | Pacing lags | Unearned moments | Confusion

If struggles: Identify gap → Return to Stage 2 → Re-test

Exit condition: Reader understands and engages without author explanations.

目标： 在无作者背景信息的情况下验证手稿的可读性。

使用全新子Agent（无Story Bible权限）：

理解度： 能否总结情节、理解动机、识别冲突？
参与度： 在哪里失去兴趣、产生疑问或感到困惑？
情感共鸣： 关键场景是否达到预期效果？结局是否令人满意？主题是否清晰？

常见问题： 动机模糊 | 节奏拖沓 | 情节突兀 | 内容困惑

若存在问题： 识别漏洞 → 返回阶段2 → 重新测试

退出条件： 读者无需作者解释即可理解并投入故事。

Self-Check: Is This Working?

自我检查：工作流是否有效？

Use these checkpoints to verify you're following the workflow correctly.

After Story Bible building:

Can you describe the protagonist's want vs. need without re-reading notes?
Can you predict how the antagonist would react to a new scenario?
Do you understand the thematic question the book explores?
Could you summarize the three-act structure in 2-3 sentences?

After invoking a persona:

Did you explicitly say "As [persona name]..." in your request?
Is the feedback focused on that persona's domain (developmental = structure, line = prose)?
Did you avoid mixing feedback from multiple personas in one pass?

After making edits:

Did you use
```
str_replace
```
for surgical changes, not reprinting entire sections?
Can you articulate what changed and why it's better?
Is the change consistent with the Story Bible (character voice, plot logic, world rules)?

After brainstorming:

Did you generate 5+ options before selecting one?
Did you curate collaboratively rather than taking the first suggestion?
Can you explain why the selected option is stronger than alternatives?

Before claiming "done":

Has a fresh sub-agent (without Story Bible context) read the manuscript?
Did the fresh reader understand plot, character motivations, and stakes?
Were any gaps or confusion points identified and addressed?

If you answered "no" to any checkpoint, return to that stage before proceeding.

使用以下检查点验证是否正确遵循工作流。

完成Story Bible构建后：

无需重读笔记即可描述主角的“诉求”与“需求”？
能否预测反派对新场景的反应？
是否理解作品探讨的核心主题？
能否用2-3句话总结三幕结构？

调用角色后：

是否在请求中明确说明“以[角色名称]的身份...”？
反馈是否聚焦于该角色的职责范围（发展性编辑=结构，逐行编辑=行文）？
是否避免在单次反馈中混合多个角色的意见？

完成修改后：

是否使用
```
str_replace
```
进行精准修改，而非重印整个章节？
能否说明修改内容及改进原因？
修改是否符合Story Bible（角色语气、情节逻辑、世界观规则）？

完成头脑风暴后：

是否生成5个以上选项后再做选择？
是否通过协作筛选而非直接采纳第一个建议？
能否解释所选选项优于其他选项的原因？

声称“完成”前：

是否让未接触过Story Bible的全新子Agent阅读手稿？
全新读者是否理解情节、角色动机与冲突？
是否识别并解决了所有漏洞或困惑点？

若任何检查点答案为“否”，请返回对应阶段后再继续。

Common Mistakes

常见错误

Mistake	Why It Happens	Fix
Skipping Story Bible	"I know my story well enough"	Story Bible isn't for you—it's for Claude. Without shared context, feedback will miss key story elements. Build it.
Generic feedback without persona	Rushing, forgetting to invoke specific role	Explicitly say "As developmental editor..." or "As line editor..." in your prompt. Different lenses catch different issues.
Reprinting entire chapters	Habit from other editing contexts	Use `str_replace` for surgical edits only. Reprinting burns context and makes changes hard to track. Link to file after edits.
Jumping to line edits before structure	Wanting to "fix" prose immediately	If plot/pacing/character issues exist, line edits are wasted effort. Always developmental pass first. See example below.
Skipping Reader Testing	"I've read it so many times already"	You have author context. Reader Testing uses fresh sub-agent without story bible to catch gaps readers will hit.
Too many personas at once	Trying to fix everything in one pass	Invoke one persona per pass. Developmental → Character → Line → Continuity. Focused feedback is actionable feedback.
Brainstorming without curation	Taking first idea that sounds good	Generate 5-15 options, then curate. First idea is rarely best idea. Quantity enables quality.

错误	原因	解决方法
跳过Story Bible构建	“我对自己的故事足够了解”	Story Bible并非为你准备——而是为Claude准备的。没有统一的背景信息，反馈会遗漏关键故事元素。请务必构建Story Bible。
未调用角色的通用反馈	仓促行事，忘记调用特定角色	在请求中明确说明“以发展性编辑的身份...”或“以逐行编辑的身份...”。不同视角能发现不同问题。
重印整个章节	受其他编辑习惯影响	仅使用 `str_replace` 进行精准修改。重印会丢失上下文，且难以追踪变化。修改后链接至文件。
先进行逐行编辑再调整结构	急于“修正”行文	若存在情节/节奏/角色问题，逐行编辑只是无用功。务必先进行发展性编辑。见下方示例。
跳过读者测试	“我已经读了很多遍了”	你拥有作者背景信息。读者测试使用未接触过Story Bible的全新子Agent，能发现普通读者会遇到的漏洞。
同时调用多个角色	试图一次性解决所有问题	每次仅调用一个角色。顺序为：发展性编辑→角色顾问→逐行编辑→连续性追踪员。聚焦的反馈更具可操作性。
头脑风暴后直接采纳第一个建议	满足于初步想法	生成5-15个选项后再筛选。第一个想法很少是最佳选择。数量决定质量。

Example: Developmental vs. Line Editing

示例：发展性编辑 vs 逐行编辑

Same passage, different lenses:

Sarah walked into the office. Her boss looked angry. "We need to talk," he said. She sat down nervously.

Line Editor feedback (prose-level):

"Walked" is weak—try "strode" or "slipped"
"Looked angry" tells rather than shows—describe furrowed brow, tight jaw
"Nervously" is an adverb crutch—show the nervousness through action

Developmental Editor feedback (structure/stakes):

What does Sarah want in this scene? What does her boss want?
If this is the confrontation, we need setup—what's the conflict history?
Stakes feel low—why does this conversation matter to the story?
Pacing: Is this the right chapter for this confrontation, or should tension build longer?

The difference: Line edits polish sentences. Developmental edits ensure the scene earns its place in the story. Always developmental first.

同一段落，不同视角：

Sarah walked into the office. Her boss looked angry. "We need to talk," he said. She sat down nervously.

逐行编辑反馈（行文层面）：

“Walked”过于平淡——尝试“strode”或“slipped”
“Looked angry”属于“告知而非展示”——描述皱眉、紧咬的牙关
“Nervously”是副词滥用——通过动作展现紧张情绪

发展性编辑反馈（结构/冲突层面）：

Sarah在这个场景中的诉求是什么？她的老板的诉求是什么？
若这是冲突爆发点，需要铺垫——冲突的历史背景是什么？
冲突感不足——这场对话对故事的重要性体现在哪里？
节奏：这场对峙放在当前章节是否合适，还是应该先积累更多紧张感？

区别： 逐行编辑润色句子。发展性编辑确保场景在故事中具备存在的意义。务必先进行发展性编辑。

Quick Reference Commands

快速参考指令

Need	Command
Start new project	"Let's build a story bible for [project]"
Developmental pass	"As developmental editor, analyze [chapter/section]"
Line edit	"As line editor, polish [scene/passage]"
Character check	"As character consultant, is [character]'s [action] in character?"
Continuity audit	"As continuity tracker, check [chapters X-Y] for inconsistencies"
Get unstuck	"Brainstorm mode—I need to [solve problem]"
Test readability	"Run a fresh read on [chapter/section]"

需求	指令
启动新项目	“为[项目名称]构建Story Bible”
发展性审核	“以发展性编辑的身份，分析[章节/段落]”
逐行编辑	“以逐行编辑的身份，润色[场景/段落]”
角色一致性检查	“以角色顾问的身份，[角色名称]的[行为]是否符合人设？”
连续性审核	“以连续性追踪员的身份，检查[章节X-Y]的一致性”
突破瓶颈	“进入头脑风暴模式——我需要解决[问题]”
可读性测试	“对[章节/段落]进行全新阅读测试”

Files

文件列表

```
references/developmental-editing.md
```
- Plot, structure, pacing analysis
```
references/line-editing.md
```
- Prose-level refinement
```
references/character-work.md
```
- Voice, motivation, arc tracking
```
references/continuity-tracking.md
```
- Timeline and fact consistency
```
references/brainstorming.md
```
- Idea generation techniques
```
references/thriller-craft.md
```
- Genre-specific guidance for suspense
```
references/scifi-worldbuilding.md
```
- Technical accuracy, speculation rules
```
assets/story-bible-template.md
```
- Blank story bible structure
```
assets/scene-worksheet.md
```
- Scene-level analysis template

```
references/developmental-editing.md
```
- 情节、结构、节奏分析
```
references/line-editing.md
```
- 行文层面优化
```
references/character-work.md
```
- 语气、动机、成长弧光追踪
```
references/continuity-tracking.md
```
- 时间线与设定一致性
```
references/brainstorming.md
```
- 创意生成技巧
```
references/thriller-craft.md
```
- 悬疑体裁专属指南
```
references/scifi-worldbuilding.md
```
- 技术准确性、设定规则
```
assets/story-bible-template.md
```
- 空白Story Bible模板
```
assets/scene-worksheet.md
```
- 场景层面分析模板