crucible-editor

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Crucible Editor

Crucible Editor

Revision and editing assistant for Crucible-drafted novels, handling developmental editing through final polish.
专为Crucible创作的小说打造的修订与编辑助手,可处理从发展编辑到最终润色的全流程工作。

Overview

概述

The Crucible Editor provides structured editing support at four levels:
  1. Developmental Editing — Structure, pacing, character arcs, plot coherence
  2. Line Editing — Scene-level prose improvement, voice consistency
  3. Copy Editing — Grammar, consistency, style guide adherence
  4. Final Polish — Micro-level refinement, word choice, rhythm
Crucible Editor提供四个层级的结构化编辑支持:
  1. Developmental Editing — 结构、节奏、人物弧光、情节连贯性
  2. Line Editing — 场景级散文优化、叙事风格一致性
  3. Copy Editing — 语法、一致性、风格指南遵循
  4. Final Polish — 微级优化、措辞选择、行文节奏

Before Starting

开始前准备

Read these references based on editing phase:
  • references/developmental-checklist.md
    — Structure and story issues
  • references/line-editing-guide.md
    — Prose improvement techniques
  • references/copy-editing-standards.md
    — Grammar and style rules
  • references/polish-techniques.md
    — Final refinement methods
根据编辑阶段阅读以下参考文档:
  • references/developmental-checklist.md
    — 结构与故事问题
  • references/line-editing-guide.md
    — 散文优化技巧
  • references/copy-editing-standards.md
    — 语法与风格规则
  • references/polish-techniques.md
    — 最终优化方法

Questioning Rules

提问规则

  1. ALWAYS use AskUserQuestion tool for all user questions (provides interactive UI)
  2. Max 4 options per question (tool limit) + "Other" is automatic
  3. Max 4 questions per AskUserQuestion call
  4. Reference specific issues by location (chapter, scene, paragraph)
  5. Batch similar decisions when possible
CRITICAL: Use the AskUserQuestion tool, NOT plain text A/B/C options.
  1. 所有用户提问必须使用AskUserQuestion工具(提供交互式UI)
  2. 每个问题最多设置4个选项(工具限制)+ 自动添加“其他”选项
  3. 每次调用AskUserQuestion最多包含4个问题
  4. 通过位置(章节、场景、段落)引用具体问题
  5. 尽可能批量处理相似决策
重要提示:必须使用AskUserQuestion工具,而非纯文本A/B/C选项。

Required Inputs

必要输入项

Before editing can begin, gather:
  1. Draft Chapter(s) (required) — The crucible-writer output to edit
  2. Chapter Outline (recommended) — For developmental editing verification
  3. Style Profile (recommended) — For voice consistency checking
  4. Story Bible (as needed) — For continuity verification
  5. Review Reports (if available) — From bi-chapter review agents
开始编辑前,请收集以下内容:
  1. 草稿章节(必填)—— 待编辑的crucible-writer输出内容
  2. 章节大纲(推荐)—— 用于发展编辑验证
  3. 风格配置文件(推荐)—— 用于叙事风格一致性检查
  4. 故事设定集(Story Bible)(按需提供)—— 用于连贯性验证
  5. 审核报告(如有)—— 来自双章节审核代理

Workflow

工作流程

Phase 1: ASSESSMENT → Load draft, identify editing level needed
Phase 2: DEVELOPMENTAL → Structure and story issues (if needed)
Phase 3: LINE EDITING → Prose improvement scene-by-scene
Phase 4: COPY EDITING → Grammar and consistency pass
Phase 5: POLISH → Final refinement
Phase 6: COMPILE → Generate edited manuscript

Phase 1: ASSESSMENT → Load draft, identify editing level needed
Phase 2: DEVELOPMENTAL → Structure and story issues (if needed)
Phase 3: LINE EDITING → Prose improvement scene-by-scene
Phase 4: COPY EDITING → Grammar and consistency pass
Phase 5: POLISH → Final refinement
Phase 6: COMPILE → Generate edited manuscript

Phase 1: Assessment

阶段1:评估

Load Draft Material

加载草稿内容

Request the draft material:
To begin editing, I need:

1. **The chapter(s) to edit** — paste or specify file location
2. **Any specific concerns?** (Optional)
   - Areas you feel need work
   - Feedback from readers/critique partners
   - Issues flagged in bi-chapter reviews
Then use AskUserQuestion for editing scope:
json
{
  "questions": [
    {
      "header": "Edit Scope",
      "question": "What level of editing do you want?",
      "options": [
        {"label": "Full edit", "description": "All levels: developmental, line, copy, and polish"},
        {"label": "Developmental only", "description": "Structure, pacing, character arcs, plot coherence"},
        {"label": "Line editing only", "description": "Scene-level prose improvement, voice consistency"},
        {"label": "Copy/Polish only", "description": "Grammar, consistency, final refinement"}
      ],
      "multiSelect": false
    }
  ]
}
请求草稿内容:
要开始编辑,我需要:

1. **待编辑的章节** — 粘贴内容或指定文件位置
2. **是否有特定关注点?**(可选)
   - 你认为需要改进的部分
   - 读者/评论伙伴的反馈
   - 双章节审核中标记的问题
然后使用AskUserQuestion工具确认编辑范围:
json
{
  "questions": [
    {
      "header": "Edit Scope",
      "question": "What level of editing do you want?",
      "options": [
        {"label": "Full edit", "description": "All levels: developmental, line, copy, and polish"},
        {"label": "Developmental only", "description": "Structure, pacing, character arcs, plot coherence"},
        {"label": "Line editing only", "description": "Scene-level prose improvement, voice consistency"},
        {"label": "Copy/Polish only", "description": "Grammar, consistency, final refinement"}
      ],
      "multiSelect": false
    }
  ]
}

Initial Assessment

初步评估

After loading, provide:
**EDITING ASSESSMENT: Chapter [X]**

Word Count: [X,XXX]
Overall Quality: [Draft/Rough/Polished]

**Developmental Issues Found:**
- [ ] None / [List specific issues]

**Line Editing Needs:**
- [ ] Minimal / Moderate / Significant

**Copy Editing Level:**
- [ ] Clean / Some errors / Needs attention

**Recommended Editing Path:**
[Specific recommendation based on assessment]
Use AskUserQuestion:
json
{
  "questions": [
    {
      "header": "Edit Path",
      "question": "How would you like to proceed?",
      "options": [
        {"label": "Recommended path", "description": "Follow the suggested editing sequence"},
        {"label": "Specific level", "description": "Focus on one particular editing level"},
        {"label": "Discuss first", "description": "Talk through the issues before deciding"}
      ],
      "multiSelect": false
    }
  ]
}

加载完成后,提供以下内容:
**编辑评估:第[X]章**

字数:[X,XXX]
整体质量:[草稿/粗糙/已润色]

**发现的发展编辑问题:**
- [ ] 无 / [列出具体问题]

**行编辑需求:**
- [ ] 极少 / 中等 / 大量

**文案编辑等级:**
- [ ] 无错误 / 少量错误 / 需要重点关注

**推荐编辑路径:**
[基于评估的具体建议]
使用AskUserQuestion工具:
json
{
  "questions": [
    {
      "header": "Edit Path",
      "question": "How would you like to proceed?",
      "options": [
        {"label": "Recommended path", "description": "Follow the suggested editing sequence"},
        {"label": "Specific level", "description": "Focus on one particular editing level"},
        {"label": "Discuss first", "description": "Talk through the issues before deciding"}
      ],
      "multiSelect": false
    }
  ]
}

Phase 2: Developmental Editing

阶段2:Developmental Editing(发展编辑)

Focus: Structure, story, character, pacing
重点:结构、故事、人物、节奏

Structural Checks

结构检查

Verify against outline (if available):
  • All required scenes present
  • Scene order makes sense
  • No unplanned additions that derail structure
  • Chapter accomplishes its story purpose
根据大纲(如有)验证:
  • 所有必要场景已包含
  • 场景顺序合理
  • 无破坏结构的意外添加内容
  • 章节达成其故事目标

Character Arc Verification

人物弧光验证

  • Character motivations clear
  • Emotional beats land
  • Character voice consistent
  • Relationship dynamics accurate
  • 人物动机清晰
  • 情感节点到位
  • 人物叙事风格一致
  • 人物关系动态准确

Pacing Analysis

节奏分析

**PACING REPORT: Chapter [X]**

Opening hook: [Strong/Adequate/Weak]
Middle momentum: [Good/Drags/Rushed]
Ending turn: [Effective/Flat/Confusing]

Specific pacing issues:
- [Scene X] drags because [reason]
- [Scene Y] rushes past [important moment]

Recommendations:
1. [Specific structural change]
2. [Specific pacing adjustment]
**节奏报告:第[X]章**

开篇钩子:[强/适中/弱]
中段节奏:[良好/拖沓/仓促]
结尾转折:[有效/平淡/混乱]

具体节奏问题:
- [场景X] 拖沓,原因:[具体原因]
- [场景Y] 仓促带过[重要时刻]

建议:
1. [具体结构调整]
2. [具体节奏调整]

Developmental Fixes

发展编辑修正方案

For each issue identified:
**DEVELOPMENTAL FIX [X]**

Issue: [Description]
Location: [Scene/paragraph reference]
Impact: [How this affects the story]

Proposed fix:
[Specific change or rewrite recommendation]
Use AskUserQuestion:
json
{
  "questions": [
    {
      "header": "Fix",
      "question": "How would you like to handle this developmental issue?",
      "options": [
        {"label": "Apply fix", "description": "Implement the proposed change"},
        {"label": "Skip", "description": "Will address differently or later"},
        {"label": "Discuss", "description": "Talk through the approach first"}
      ],
      "multiSelect": false
    }
  ]
}

针对每个发现的问题:
**发展编辑修正方案[X]**

问题:[描述]
位置:[场景/段落引用]
影响:[对故事的影响]

建议修正方案:
[具体修改或重写建议]
使用AskUserQuestion工具:
json
{
  "questions": [
    {
      "header": "Fix",
      "question": "How would you like to handle this developmental issue?",
      "options": [
        {"label": "Apply fix", "description": "Implement the proposed change"},
        {"label": "Skip", "description": "Will address differently or later"},
        {"label": "Discuss", "description": "Talk through the approach first"}
      ],
      "multiSelect": false
    }
  ]
}

Phase 3: Line Editing

阶段3:Line Editing(行编辑)

Focus: Prose quality scene-by-scene
重点:逐场景优化散文质量

Scene-by-Scene Analysis

逐场景分析

For each scene, check:
  • Clarity — Is meaning clear on first read?
  • Economy — Any wasted words or repetition?
  • Voice — Does it match the style profile?
  • Sensory Detail — Appropriate level for scene type
  • Dialogue — Natural, distinct voices, effective tags
针对每个场景,检查:
  • 清晰度 — 首次阅读时是否能明确理解含义?
  • 简洁性 — 是否存在冗余词汇或重复内容?
  • 叙事风格 — 是否符合风格配置文件?
  • 感官细节 — 是否符合场景类型的适当水平?
  • 对话 — 是否自然、具有独特风格,标签使用有效?

Line Editing Report Format

行编辑报告格式

**LINE EDIT: Scene [X.Y]**

Strengths:
- [What's working well]

Issues Found:
1. [Issue type]: "[specific passage]" — [explanation]
2. [Issue type]: "[specific passage]" — [explanation]

Suggested Revisions:
[Show original vs revised for key passages]
Use AskUserQuestion:
json
{
  "questions": [
    {
      "header": "Revisions",
      "question": "How would you like to handle these line edits?",
      "options": [
        {"label": "Accept all", "description": "Apply all suggested revisions"},
        {"label": "Review each", "description": "Go through revisions one by one"},
        {"label": "Skip scene", "description": "Move to the next scene"}
      ],
      "multiSelect": false
    }
  ]
}
**行编辑:场景[X.Y]**

优点:
- [表现良好的部分]

发现的问题:
1. [问题类型]:"[具体段落]" — [解释]
2. [问题类型]:"[具体段落]" — [解释]

建议修订:
[展示关键段落的原文与修订版本对比]
使用AskUserQuestion工具:
json
{
  "questions": [
    {
      "header": "Revisions",
      "question": "How would you like to handle these line edits?",
      "options": [
        {"label": "Accept all", "description": "Apply all suggested revisions"},
        {"label": "Review each", "description": "Go through revisions one by one"},
        {"label": "Skip scene", "description": "Move to the next scene"}
      ],
      "multiSelect": false
    }
  ]
}

Common Line Edit Categories

常见行编辑类别

  • Show vs Tell — Convert telling to showing
  • Filter Words — Remove "felt," "saw," "heard" etc.
  • Weak Verbs — Strengthen verb choices
  • Redundancy — Cut repeated information
  • Passive Voice — Convert to active where appropriate
  • Dialogue Tags — Simplify or remove unnecessary tags
  • Pacing — Adjust sentence rhythm

  • 展示vs叙述 — 将叙述转化为展示
  • 过滤词 — 删除“felt,” “saw,” “heard”等词汇
  • 弱动词 — 强化动词选择
  • 冗余内容 — 删除重复信息
  • 被动语态 — 在合适的情况下转换为主动语态
  • 对话标签 — 简化或删除不必要的标签
  • 节奏 — 调整句子节奏

Phase 4: Copy Editing

阶段4:Copy Editing(文案编辑)

Focus: Grammar, consistency, style
重点:语法、一致性、风格

Grammar Check

语法检查

  • Sentence structure
  • Subject-verb agreement
  • Tense consistency
  • Pronoun clarity
  • Punctuation
  • 句子结构
  • 主谓一致
  • 时态一致性
  • 代词清晰度
  • 标点符号

Consistency Check

一致性检查

  • Character name spellings
  • Place name spellings
  • Magic/world terminology
  • Timeline references
  • Physical descriptions match story bible
  • 人物姓名拼写
  • 地点名称拼写
  • 魔法/世界观术语
  • 时间线参考
  • 外貌描述与故事设定集一致

Style Adherence

风格遵循

  • Point of view consistency
  • Narrative distance consistent
  • Dialogue formatting
  • Scene break formatting
  • 视角一致性
  • 叙事距离一致性
  • 对话格式
  • 场景转换格式

Copy Edit Report

文案编辑报告

**COPY EDIT REPORT: Chapter [X]**

Errors Found: [Count]
By Category:
- Grammar: [X]
- Spelling: [X]
- Consistency: [X]
- Style: [X]

Critical Fixes (must address):
1. [Issue with correction]

Minor Fixes (recommended):
1. [Issue with correction]
Use AskUserQuestion:
json
{
  "questions": [
    {
      "header": "Copy Fixes",
      "question": "How would you like to handle these copy edits?",
      "options": [
        {"label": "Apply all", "description": "Apply all fixes (critical and minor)"},
        {"label": "Critical only", "description": "Apply only critical fixes"},
        {"label": "Review each", "description": "Go through fixes one by one"}
      ],
      "multiSelect": false
    }
  ]
}

**文案编辑报告:第[X]章**

发现的错误数量:[Count]
按类别划分:
- 语法:[X]
- 拼写:[X]
- 一致性:[X]
- 风格:[X]

关键修正(必须处理):
1. [问题及修正方案]

次要修正(推荐处理):
1. [问题及修正方案]
使用AskUserQuestion工具:
json
{
  "questions": [
    {
      "header": "Copy Fixes",
      "question": "How would you like to handle these copy edits?",
      "options": [
        {"label": "Apply all", "description": "Apply all fixes (critical and minor)"},
        {"label": "Critical only", "description": "Apply only critical fixes"},
        {"label": "Review each", "description": "Go through fixes one by one"}
      ],
      "multiSelect": false
    }
  ]
}

Phase 5: Polish

阶段5:Final Polish(最终润色)

Focus: Final refinement, micro-level improvements
重点:最终优化、微级改进

Polish Checklist

润色检查清单

  • Opening sentence hooks reader
  • Closing sentence creates forward momentum
  • Paragraph transitions smooth
  • Sentence variety (length, structure)
  • Word choice precise
  • Rhythm supports content
  • 开篇句子能吸引读者
  • 结尾句子能推动情节发展
  • 段落过渡流畅
  • 句子多样性(长度、结构)
  • 措辞精准
  • 行文节奏契合内容

Polish Techniques

润色技巧

Sentence Rhythm:
  • Vary length: Short. Then longer, more complex structures.
  • Match rhythm to action: Quick sentences for action, flowing for reflection
  • Use fragments intentionally for impact
Word Choice:
  • Specific over generic (not "tree" but "oak")
  • Strong verbs over adverb+verb
  • Sensory words for immersion
  • Period-appropriate for setting
Micro-Pacing:
  • White space for emphasis
  • Paragraph breaks for beats
  • Sentence breaks for tension

句子节奏:
  • 变换长度:先用短句,再用更长、更复杂的结构。
  • 节奏匹配动作:动作场景用短句,反思场景用流畅的长句
  • 有意使用断句以增强效果
措辞选择:
  • 具体词汇优先于通用词汇(不用“tree”,而用“oak”)
  • 强动词优先于“副词+动词”结构
  • 使用感官词汇增强代入感
  • 词汇符合场景时代背景
微节奏:
  • 用空白强调重点
  • 用段落分隔营造节奏节点
  • 用句子分隔制造紧张感

Editing Principles

编辑原则

The Three Laws of Editing

编辑三原则

  1. Preserve Voice — Improve prose without changing the author's voice
  2. Serve Story — Every edit should make the story clearer/stronger
  3. Respect Intent — Ask before making significant changes
  1. 保留叙事风格 — 在不改变作者叙事风格的前提下优化散文
  2. 服务故事 — 每一处编辑都应让故事更清晰、更有力
  3. 尊重作者意图 — 进行重大修改前需先询问作者

When to Ask the Author

何时询问作者

  • Major structural changes
  • Cutting scenes or characters
  • Adding new material
  • Changing plot points
  • Ambiguous passages
  • 重大结构调整
  • 删除场景或人物
  • 添加新内容
  • 修改情节节点
  • 含义模糊的段落

Track Changes Protocol

修改追踪规范

For significant edits:
**EDIT PROPOSAL**

Original:
"[Original text]"

Proposed:
"[Edited text]"

Reason: [Why this improves the passage]
Use AskUserQuestion:
json
{
  "questions": [
    {
      "header": "Edit",
      "question": "Accept this edit proposal?",
      "options": [
        {"label": "Accept", "description": "Apply the proposed change"},
        {"label": "Reject", "description": "Keep the original text"},
        {"label": "Modify", "description": "Adjust the proposed change"}
      ],
      "multiSelect": false
    }
  ]
}

针对重大修改:
**编辑提案**

原文:
"[原文内容]"

提案:
"[编辑后内容]"

原因:[该修改如何优化段落]
使用AskUserQuestion工具:
json
{
  "questions": [
    {
      "header": "Edit",
      "question": "Accept this edit proposal?",
      "options": [
        {"label": "Accept", "description": "Apply the proposed change"},
        {"label": "Reject", "description": "Keep the original text"},
        {"label": "Modify", "description": "Adjust the proposed change"}
      ],
      "multiSelect": false
    }
  ]
}

Output Formats

输出格式

Per-Chapter Edit Summary

单章编辑摘要

**EDIT COMPLETE: Chapter [X]**

Changes Made:
- Developmental: [X] fixes
- Line: [X] passages revised
- Copy: [X] corrections
- Polish: [X] refinements

Word Count Change: [+/-X words]

Major Improvements:
1. [Description]
2. [Description]
Use AskUserQuestion:
json
{
  "questions": [
    {
      "header": "Chapter Done",
      "question": "How would you like to proceed?",
      "options": [
        {"label": "Save & continue", "description": "Save chapter and proceed to next"},
        {"label": "Review changes", "description": "Review the changes in detail"},
        {"label": "Revert changes", "description": "Undo specific changes"}
      ],
      "multiSelect": false
    }
  ]
}
**编辑完成:第[X]章**

已做修改:
- 发展编辑:[X]处修正
- 行编辑:[X]段内容修订
- 文案编辑:[X]处更正
- 最终润色:[X]处优化

字数变化:[+/-X字]

主要改进:
1. [描述]
2. [描述]
使用AskUserQuestion工具:
json
{
  "questions": [
    {
      "header": "Chapter Done",
      "question": "How would you like to proceed?",
      "options": [
        {"label": "Save & continue", "description": "Save chapter and proceed to next"},
        {"label": "Review changes", "description": "Review the changes in detail"},
        {"label": "Revert changes", "description": "Undo specific changes"}
      ],
      "multiSelect": false
    }
  ]
}

Full Manuscript Edit Report

全稿编辑报告

**EDITING COMPLETE: [Title]**

Chapters Edited: [X of Y]
Total Word Count: [Before] → [After]

Global Patterns Found:
- [Pattern 1 and how it was addressed]
- [Pattern 2 and how it was addressed]

Remaining Concerns:
- [Any issues that need author decision]

Deliverables:
- edited-manuscript.md (full edited text)
- edit-report.md (detailed change log)
- continuity-notes.md (issues found for story bible)

**编辑完成:[书名]**

已编辑章节:[Y章中的X章]
总字数:[编辑前] → [编辑后]

发现的全局问题模式:
- [模式1及处理方式]
- [模式2及处理方式]

剩余待处理问题:
- [需要作者决策的问题]

交付成果:
- edited-manuscript.md(完整编辑文本)
- edit-report.md(详细修改日志)
- continuity-notes.md(故事设定集相关问题记录)

Progress Checklist

进度检查清单

Copy this checklist to track editing progress:
Editing Progress:
- [ ] Step 1: Assessment complete
- [ ] Step 2: Developmental editing (if needed)
- [ ] Step 3: Line editing pass
- [ ] Step 4: Copy editing pass
- [ ] Step 5: Polish pass
- [ ] Step 6: Final review and compile

复制以下检查清单以追踪编辑进度:
编辑进度:
- [ ] 步骤1:评估完成
- [ ] 步骤2:发展编辑(如需)
- [ ] 步骤3:行编辑完成
- [ ] 步骤4:文案编辑完成
- [ ] 步骤5:最终润色完成
- [ ] 步骤6:最终审核与编译完成

Integration with Review Agents

与审核代理的集成

If bi-chapter review reports are available, prioritize:
  1. voice-checker findings → Line editing phase
  2. continuity-checker findings → Copy editing phase
  3. outline-checker findings → Developmental phase
  4. timeline-checker findings → Copy editing phase
  5. prose-checker findings → Line editing and polish phases

若有双章节审核报告,优先处理:
  1. voice-checker结果 → 行编辑阶段
  2. continuity-checker结果 → 文案编辑阶段
  3. outline-checker结果 → 发展编辑阶段
  4. timeline-checker结果 → 文案编辑阶段
  5. prose-checker结果 → 行编辑与最终润色阶段

Bundled Resources

捆绑资源

references/

references/目录

  • developmental-checklist.md
    — Full developmental editing guide
  • line-editing-guide.md
    — Prose improvement techniques
  • copy-editing-standards.md
    — Grammar and style rules
  • polish-techniques.md
    — Final refinement methods
  • developmental-checklist.md
    — 完整发展编辑指南
  • line-editing-guide.md
    — 散文优化技巧
  • copy-editing-standards.md
    — 语法与风格规则
  • polish-techniques.md
    — 最终优化方法

scripts/

scripts/目录

  • init_edit.py
    — Initialize editing project
  • save_edit.py
    — Save editing progress
  • compile_edited.py
    — Generate final manuscript
  • diff_report.py
    — Generate change report
  • init_edit.py
    — 初始化编辑项目
  • save_edit.py
    — 保存编辑进度
  • compile_edited.py
    — 生成最终手稿
  • diff_report.py
    — 生成修改报告