Back to Details

non-fiction-revision

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Non-Fiction Revision Diagnostic

非虚构类书籍修订诊断

Purpose

目的

Diagnose and guide revisions in non-fiction books (business, self-help, academic, popular science, memoir). Non-fiction operates across multiple levels simultaneously—thesis, structure, evidence, pedagogy. Changes at one level cascade to others. This skill identifies which level needs attention and prevents revision damage.
为非虚构类书籍（商业、自助、学术、科普、回忆录）提供诊断与修订指导。非虚构类书籍同时在多个层面运作——主题、结构、论据、教学法。一个层面的改动会引发其他层面的连锁反应。本技能可识别需要关注的层面，避免修订过程中造成破坏。

Quick Reference

快速参考

StateSignalCore Issue
NR1Thesis feels unclear or weakConceptual level problem
NR2Arguments don't build logicallyStructural problem
NR3Claims lack adequate supportEvidence problem
NR4Readers report confusionPedagogical problem
NR5Sources outdated or weakCredibility problem
NR6Changes causing new problemsCascade failure
状态信号核心问题
NR1主题模糊或薄弱概念层面问题
NR2论点逻辑衔接不畅结构层面问题
NR3主张缺乏足够支撑论据层面问题
NR4读者反馈困惑教学法层面问题
NR5资料过时或质量差可信度层面问题
NR6改动引发新问题连锁失效问题

The Multi-Level Structure

多层结构

Every non-fiction book operates simultaneously across:
每本非虚构类书籍同时在以下多个层面运作：

Level 1: Conceptual/Thesis

层面1：概念/主题

  • Core thesis and main arguments
  • Foundational assumptions and frameworks
  • Philosophical or theoretical positions
  • Overall purpose and intended impact
  • 核心主题与主要论点
  • 基础假设与框架
  • 哲学或理论立场
  • 整体目标与预期影响

Level 2: Structural/Argument

层面2：结构/论点

  • Logical argument sequence and flow
  • Chapter organization and dependencies
  • Evidence distribution and support patterns
  • Reader journey and persuasion architecture
  • 论点的逻辑顺序与流程
  • 章节组织与依赖关系
  • 论据分布与支撑模式
  • 读者阅读路径与说服架构

Level 3: Content/Evidence

层面3：内容/论据

  • Specific evidence, examples, and data
  • Explanations and clarifications
  • Voice, tone, and accessibility
  • Citations, sources, and credibility markers
  • 具体论据、案例与数据
  • 解释与说明
  • 语气、语调与易读性
  • 引用、资料与可信度标识

Level 4: Pedagogical/Reader

层面4：教学/读者

  • Learning progression and scaffolding
  • Cognitive load management
  • Engagement and retention strategies
  • Practical application guidance
  • 学习进阶与支架式教学
  • 认知负荷管理
  • 参与度与记忆策略
  • 实践应用指导

Critical Principle

核心原则

Any change at one level potentially affects argument validity and reader comprehension at all other levels.
Changes propagate:
  • Upward: New evidence might undermine existing arguments
  • Downward: Thesis changes require complete restructuring
  • Lateral: Chapter reordering affects argument development flow
任何一个层面的改动都可能影响其他所有层面的论点有效性与读者理解度。
改动的传播方式：
  • 向上传播：新论据可能削弱现有论点
  • 向下传播：主题改动需要彻底重构
  • 横向传播：章节重排会影响论点展开的流程

Diagnostic States

诊断状态

NR1: Thesis/Core Argument Problem

NR1：主题/核心论点问题

Symptoms:
  • Thesis feels unclear or unstated
  • Main arguments seem weak or unconvincing
  • Central claims are frequently disputed
  • Book's purpose is hard to articulate
  • Conclusion doesn't deliver on promise
Diagnostic Questions:
  1. Can you state the thesis in one sentence?
  2. What are the 3-5 main arguments supporting it?
  3. What evidence backs each main argument?
  4. Does the conclusion match the opening promise?
  5. What changes if the thesis is wrong?
Interventions:
  1. Map all current evidence supporting the thesis
  2. Identify which chapters depend on current thesis formulation
  3. Evaluate what new evidence a revised thesis would require
  4. Check how thesis change affects the reader promise
  5. Assess impact on conclusion and call-to-action
Cascade Warning: Thesis changes are the most dangerous—they can invalidate entire chapters. Before changing thesis, map all dependencies.
症状：
  • 主题模糊或未明确提出
  • 主要论点看似薄弱或缺乏说服力
  • 核心主张频繁受到质疑
  • 书籍的目的难以清晰表述
  • 结论未兑现引言的承诺
诊断问题：
  1. 你能用一句话概括主题吗？
  2. 支撑主题的3-5个主要论点是什么？
  3. 每个主要论点有哪些论据支撑？
  4. 结论是否与引言的承诺一致？
  5. 如果主题有误，会带来哪些变化？
干预措施：
  1. 梳理当前支撑主题的所有论据
  2. 识别哪些章节依赖于当前的主题设定
  3. 评估修订主题后需要补充哪些新论据
  4. 检查主题改动会如何影响对读者的承诺
  5. 评估对结论与行动号召的影响
连锁警告： 主题改动是最具风险的——可能导致整个章节失效。在改动主题前，务必梳理所有依赖关系。

NR2: Structural/Organization Problem

NR2：结构/组织问题

Symptoms:
  • Argument flow feels illogical
  • Chapters seem disconnected
  • Prerequisite knowledge isn't established before use
  • Reader must jump back to understand
  • Same points repeated without building
Diagnostic Questions:
  1. What logical prerequisites exist for each chapter?
  2. Does knowledge accumulate or repeat?
  3. Are there arguments that depend on later chapters?
  4. Could chapters be reordered without breaking logic?
  5. Do transitions explain the logical connection?
Interventions:
  1. Create dependency map of chapter relationships
  2. Identify logical prerequisites for each major argument
  3. Map reader knowledge accumulation through structure
  4. Test alternative sequences against comprehension requirements
  5. Ensure examples remain contextually appropriate
Cascade Warning: Reordering chapters affects every cross-reference and forward/backward reference. Track all internal citations.
症状：
  • 论点逻辑流程混乱
  • 章节之间看似脱节
  • 在使用相关知识前未建立前置认知
  • 读者需要反复回溯才能理解内容
  • 相同观点重复出现，未逐步深化
诊断问题：
  1. 每个章节存在哪些逻辑前置条件？
  2. 知识是逐步积累还是重复出现？
  3. 是否存在依赖后续章节内容的论点？
  4. 调整章节顺序是否会破坏逻辑？
  5. 过渡内容是否解释了逻辑关联？
干预措施：
  1. 创建章节关系依赖图
  2. 识别每个主要论点的逻辑前置条件
  3. 梳理读者通过结构积累知识的路径
  4. 测试不同章节顺序对理解度的影响
  5. 确保案例仍贴合上下文场景
连锁警告： 调整章节顺序会影响所有交叉引用与前后文关联。务必跟踪所有内部引用。

NR3: Evidence/Support Problem

NR3：论据/支撑问题

Symptoms:
  • Claims feel unsupported or handwavy
  • "Trust me" rather than "here's proof"
  • Evidence exists but doesn't connect to claims
  • Support for different claims inconsistent in quality
  • Key arguments rest on weak foundations
Diagnostic Questions:
  1. What type of evidence supports each main claim?
  2. Are evidence standards consistent throughout?
  3. Which claims have the weakest support?
  4. Does evidence actually prove what's claimed?
  5. Are there counter-arguments addressed?
Interventions:
  1. Audit evidence quality for each major claim
  2. Identify claims needing stronger or different support
  3. Evaluate how new evidence affects existing arguments
  4. Check consistency in citation style and source quality
  5. Assess whether adding evidence changes argument strength
Cascade Warning: Adding strong evidence for one claim can accidentally weaken others by raising the evidence standard readers expect.
症状：
  • 主张看似缺乏支撑或表述模糊
  • 用“相信我”而非“这是证据”
  • 存在论据但与主张无关
  • 不同主张的支撑质量不一致
  • 关键论点建立在薄弱的基础上
诊断问题：
  1. 每个主要主张由何种类型的论据支撑？
  2. 全书的论据标准是否一致？
  3. 哪些主张的支撑最薄弱？
  4. 论据是否真正能证明主张？
  5. 是否回应了反论点？
干预措施：
  1. 审核每个主要主张的论据质量
  2. 识别需要更强或不同类型支撑的主张
  3. 评估新论据对现有论点的影响
  4. 检查引用格式与资料质量的一致性
  5. 评估添加论据是否会提升论点的说服力
连锁警告： 为某个主张添加强有力的论据，可能会意外提高读者对论据标准的预期，从而削弱其他主张的说服力。

NR4: Pedagogical/Comprehension Problem

NR4：教学/理解问题

Symptoms:
  • Readers report confusion
  • Complex concepts introduced too fast
  • Examples don't illuminate—they confuse
  • Practical application unclear
  • Target audience can't follow
Diagnostic Questions:
  1. Where do readers typically get lost?
  2. Are technical terms defined before use?
  3. Do examples match reader experience?
  4. Is cognitive load distributed or front-loaded?
  5. Can readers apply what they learn?
Interventions:
  1. Map cognitive load distribution across chapters
  2. Identify concepts needing better scaffolding
  3. Evaluate example effectiveness and relevance
  4. Check that practical guidance is actionable
  5. Assess whether complexity progression is appropriate
Cascade Warning: Simplifying can accidentally remove nuance that supports arguments. Balance accessibility with accuracy.
症状：
  • 读者反馈内容难以理解
  • 复杂概念引入过快
  • 案例未起到解释作用，反而加剧困惑
  • 实践应用方法不明确
  • 目标受众无法跟上内容节奏
诊断问题：
  1. 读者通常在哪些地方陷入困惑？
  2. 专业术语是否在使用前定义？
  3. 案例是否贴合读者的实际经验？
  4. 认知负荷是分散分布还是集中在前期？
  5. 读者能否将所学内容应用到实践中？
干预措施：
  1. 梳理各章节的认知负荷分布
  2. 识别需要更好支架式教学的概念
  3. 评估案例的有效性与相关性
  4. 确保实践指导具备可操作性
  5. 评估内容复杂度的递进是否合理
连锁警告： 简化内容可能会意外移除支撑论点的细节，需在易读性与准确性之间取得平衡。

NR5: Credibility/Source Problem

NR5：可信度/资料问题

Symptoms:
  • Sources feel outdated
  • Citation patterns inconsistent
  • Author authority questioned
  • Examples from wrong era
  • "According to experts" without naming them
Diagnostic Questions:
  1. How old are the oldest sources?
  2. Are sources appropriate to the field?
  3. Is citation style consistent throughout?
  4. Do you name experts or speak generally?
  5. Are there sources readers would expect that are missing?
Interventions:
  1. Audit source currency and quality
  2. Identify claims needing more recent support
  3. Standardize citation style and depth
  4. Replace generic expert references with specific citations
  5. Add expected canonical sources for the field
Cascade Warning: Updating sources can accidentally change what the evidence actually says. Verify new sources support the same conclusions.
症状：
  • 资料看似过时
  • 引用格式不一致
  • 作者权威性受到质疑
  • 案例来自不恰当的时代
  • 仅提及“据专家称”却未指明具体来源
诊断问题：
  1. 最古老的资料距今有多久？
  2. 资料是否符合该领域的要求？
  3. 全书的引用格式是否一致？
  4. 你是明确提及专家还是泛泛而谈？
  5. 是否缺少读者预期会看到的核心资料？
干预措施：
  1. 审核资料的时效性与质量
  2. 识别需要更新支撑资料的主张
  3. 统一引用格式与深度
  4. 将泛泛的专家引用替换为具体的资料来源
  5. 添加该领域读者预期的经典资料
连锁警告： 更新资料可能会意外改变论据的实际含义。需验证新资料是否仍支持相同的结论。

NR6: Cascade Failure

NR6：连锁失效

Symptoms:
  • Fixes create new problems
  • Changes in one chapter break another
  • Evidence update invalidates argument
  • Structural change creates new confusion
  • Progress feels impossible
Diagnostic Questions:
  1. What was the original change that started the cascade?
  2. What dependencies weren't mapped?
  3. Is there a stable rollback point?
  4. What's the minimum viable change that tests the idea?
  5. Are the problems localized or systemic?
Interventions:
  1. Stop implementing and assess damage scope
  2. Identify last stable state
  3. Map actual dependencies (not assumed ones)
  4. Consider whether original change is worth the cascade cost
  5. If proceeding, create checkpoint system for controlled changes
Rollback Criteria:
  • Fundamental logical structure breaks down
  • Evidence requirements become impossible to meet
  • Changes create more credibility problems than they solve
  • Reader comprehension significantly compromised
症状：
  • 修复措施引发新问题
  • 一个章节的改动破坏了另一个章节
  • 论据更新导致论点失效
  • 结构改动引发新的困惑
  • 修订进度陷入停滞
诊断问题：
  1. 引发连锁反应的初始改动是什么？
  2. 哪些依赖关系未被梳理？
  3. 是否存在稳定的回退点？
  4. 测试该想法的最小可行改动是什么？
  5. 问题是局部的还是系统性的？
干预措施：
  1. 停止实施改动，评估破坏范围
  2. 确定最后一个稳定状态
  3. 梳理实际的依赖关系（而非假设的）
  4. 考虑初始改动是否值得承担连锁反应的成本
  5. 若继续推进，需创建受控改动的检查点系统
回退标准：
  • 基础逻辑结构崩溃
  • 论据要求变得无法满足
  • 改动引发的可信度问题多于解决的问题
  • 读者理解度大幅下降

Pre-Change Protocol

改动前流程

Before implementing ANY revision:
在实施任何修订之前：

1. Identify Change Level

1. 确定改动层面

  • Conceptual (thesis, main arguments, frameworks)
  • Structural (chapter sequence, argument flow, organization)
  • Content (evidence, examples, explanations)
  • Pedagogical (presentation, scaffolding, application)
  • 概念层面（主题、主要论点、框架）
  • 结构层面（章节顺序、论点流程、组织架构）
  • 内容层面（论据、案例、解释）
  • 教学层面（呈现方式、支架式教学、应用指导）

2. Map Dependencies

2. 梳理依赖关系

For each change, document:
  • Prerequisites: What must remain intact for this change to work?
  • Dependents: What later claims rely on this element?
  • Evidence: What support becomes necessary or obsolete?
  • Comprehension: How does this affect the learning journey?
针对每一项改动，记录：
  • 前置条件：为使改动生效，哪些内容必须保持不变？
  • 依赖项：哪些后续主张依赖于该元素？
  • 论据：哪些支撑内容会变得必要或过时？
  • 理解度：这会如何影响读者的学习路径？

3. Assess Cascade Risk

3. 评估连锁风险

  • Low: Change is isolated, no dependencies
  • Medium: 2-3 other elements need updating
  • High: Affects multiple chapters or core arguments
  • Critical: Threatens book's foundational structure
  • 低风险：改动独立，无依赖关系
  • 中风险：需要更新2-3个其他元素
  • 高风险：影响多个章节或核心论点
  • 极高风险：威胁书籍的基础结构

4. Define Success Criteria

4. 定义成功标准

Before changing, know how you'll evaluate:
  • Logical coherence: Does the argument still flow?
  • Evidence adequacy: Are claims still supported?
  • Reader comprehension: Can they still follow?
  • Credibility: Does authority remain intact?
在改动前，明确如何评估以下内容：
  • 逻辑连贯性：论点是否仍流畅？
  • 论据充分性：主张是否仍有支撑？
  • 读者理解度：读者是否仍能跟上？
  • 可信度：权威性是否仍保持？

Change Record Template

改动记录模板

markdown
undefined
markdown
undefined

Revision: [Brief Description]

修订：[简要描述]

Change Type

改动类型

  • Conceptual - [ ] Structural - [ ] Content - [ ] Pedagogical
  • 概念层面 - [ ] 结构层面 - [ ] 内容层面 - [ ] 教学层面

Rationale

理由

[Why this change improves the book]
[该改动如何提升书籍质量]

Dependency Analysis

依赖关系分析

  • Prerequisites affected:
  • Dependent elements:
  • Evidence changes needed:
  • Comprehension impacts:
  • 受影响的前置条件：
  • 依赖元素：
  • 需要调整的论据：
  • 对理解度的影响：

Cascade Risk Level

连锁风险等级

  • Low - [ ] Medium - [ ] High - [ ] Critical
  • 低 - [ ] 中 - [ ] 高 - [ ] 极高

Success Criteria

成功标准

  • Logical coherence check:
  • Evidence adequacy standard:
  • Reader comprehension benchmark:
  • 逻辑连贯性检查：
  • 论据充分性标准：
  • 读者理解度基准：

Implementation Status

实施状态

  • Initial change complete
  • Dependencies updated
  • Cross-references revised
  • Cascade effects resolved
  • 初始改动完成
  • 依赖项已更新
  • 交叉引用已修订
  • 连锁影响已解决

Outcome

结果

[Complete after implementation]

---
[实施完成后填写]

---

Non-Fiction Type Variations

非虚构类书籍类型差异

Academic/Research

学术/研究类

  • Methodology consistency paramount
  • Literature review must stay current
  • Anticipate peer review critique
  • Contribution clarity essential
  • 方法论一致性至关重要
  • 文献综述需保持时效性
  • 提前预判同行评审意见
  • 必须明确研究贡献

Business/Self-Help

商业/自助类

  • Practical applicability above all
  • Examples must feel current
  • Implementation guidance required
  • ROI/benefit must be clear
  • 实用性优先
  • 案例需贴合当下
  • 需提供实践指导
  • 必须清晰呈现ROI/收益

Popular Science

科普类

  • Accessibility without dumbing down
  • Research currency matters
  • Analogies must actually illuminate
  • Balance education with engagement
  • 兼顾易读性与专业性
  • 研究资料需及时更新
  • 类比需真正起到解释作用
  • 平衡教育性与趣味性

Memoir/Personal Narrative

回忆录/个人叙事类

  • Factual accuracy + compelling narrative
  • Emotional authenticity preserved
  • Privacy boundaries respected
  • Personal connects to universal
  • 兼顾事实准确性与叙事吸引力
  • 保留情感真实性
  • 尊重隐私边界
  • 实现个人经历与普遍意义的联结

Anti-Patterns

反模式

The Endless Revision Spiral

无限修订循环

Fixing one thing breaks another, which breaks another. The book never reaches stable state.
Fix: Define minimum viable change, implement, stabilize before next change.
修复一个问题却引发另一个问题，陷入恶性循环，书籍始终无法达到稳定状态。
解决方法：定义最小可行改动，实施后先稳定，再进行下一项改动。

The Evidence Addiction

论据堆砌

Adding more and more sources without improving argument quality. Quantity masking weakness.
Fix: Better evidence, not more evidence. One strong study beats ten weak ones.
不断添加更多资料，却未提升论点质量，用数量掩盖薄弱之处。
解决方法：选择高质量论据而非堆砌数量。一项有力的研究胜过十项薄弱的研究。

The Clarity Trap

清晰度陷阱

Simplifying until accuracy suffers. Readers can follow but learn the wrong thing.
Fix: Scaffold complexity rather than remove it. Build up to nuance.
过度简化导致准确性受损，读者能跟上却学到错误内容。
解决方法：为复杂内容搭建学习支架，而非直接删减。逐步深入呈现细节。

The Thesis Drift

主题偏移

Small changes accumulate until the book argues something different than intended.
Fix: Regularly check: does the conclusion still match the introduction's promise?
小改动不断累积，最终书籍的论点与最初意图大相径庭。
解决方法：定期检查：结论是否仍与引言的承诺一致？

Integration Points

集成要点

Inbound:
  • From 
    research
    : When gathering new evidence
  • From 
    revision
    : For overall revision strategy
Outbound:
  • To 
    prose-style
    : After structural issues resolved
  • To 
    fact-check
    : For evidence verification
Complementary:
  • research
    : For evidence gathering
  • revision
    : For fiction revision (parallel skill)
输入：
  • 来自
    research
    ：收集新论据时
  • 来自
    revision
    ：制定整体修订策略时
输出：
  • 至
    prose-style
    ：解决结构问题后
  • 至
    fact-check
    ：进行论据验证时
互补技能：
  • research
    ：用于论据收集
  • revision
    ：用于虚构类书籍修订（平行技能）