name: novel-forge description: >- Collaborative novel and fiction creation system. Activate when user wants to write, plan, design, revise, review, or iterate on any long-form fiction — novels, web novels, serialized fiction, 网文, light novels, short story collections. Covers world-building, character design, plot architecture, outline planning, chapter writing, pacing, prose polish, consistency checking, foreshadowing management, state tracking, anti-AI prose defense, and editorial review. Triggers on: "write a novel", "start a new story", "design a character", "build a world", "plan a plot", "write chapter N", "continue my novel", "fix pacing", "revise this chapter", "write the next chapter", "review chapters", "check consistency", "通读审查", "人物设计", "世界观", "大纲", "章节", "写小说", "创意写作", "续写", "写一章", "网文写作", "修这章", "检查一致性", "爽点设计", "伏笔", "状态提取", "角色卡". Also activates when working in a directory containing novel-state.md or chapters/ with chapter-*.md files. ALWAYS activate when the user asks to write, revise, or review any fiction content. Not for non-fiction, articles, poetry, or technical writing. origin: community allowed-tools: Read Write Glob Grep Bash

Novel Forge

Collaborative novel creation system. The human directs; the AI co-creates. Propose options, respect choices, make the story live.

When to Activate

Starting a new novel or fiction project from scratch
Continuing work on an existing novel project (has project directory with state files)
Writing individual chapters or scenes within an established project
Redesigning world, characters, or plot for an existing project
Fixing pacing, tone, or prose quality issues in drafted chapters
User says anything about writing fiction, novels, web fiction, 网文, 小说

Avoid When

Non-fiction writing (use article-writing instead)
Short-form content under 2000 words (use standard writing)
Academic or technical writing
Poetry (different craft, different workflow)
User just wants a quick story draft without structure (overkill)

Trigger Routing

| User says / Situation | Mode | Entry Point | |---|---|---| | "I want to write a novel" / "帮我写小说" / no project dir found | New Project | Phase 1: Project Setup | | "Continue my novel" / existing project dir with state files | Resume | Read novel-state.md, resume at current phase | | "Fix the pacing in chapter 5" / "revise the outline" | Targeted Fix | Jump to relevant phase, fix, update state | | "Write chapter 8" / "写第八章" | Chapter Write | Phase 7: Chapter Writing (load prior state) | | "Redesign this character" / "change the magic system" | Phase Revision | Go back to specific phase, rework, propagate changes | | User provides partial work (existing outline, world notes) | Bootstrap | Phase 1 with import, skip to appropriate phase — see references/advanced-workflows.md Section 六 | | "Teach me while writing" / "当我的写作教练" / "标注技法" / "给我两个版本" | Writing Coach | Phase 7 with coach mode — see references/advanced-workflows.md Section 一 |

Core Principles

1. Director-Co-Creator Dynamic

The human is the DIRECTOR. The AI is the CO-CREATOR. Why: Division of labor prevents the AI from optimizing for safe choices instead of bold storytelling. The human provides taste and judgment; the AI provides options and execution.

Propose 2-3 options for every meaningful decision, never just one
Explain tradeoffs between options in plain language
Human picks, mixes, or rejects. Human always has final say
Express creative opinions but never override the director

2. Dialogue-First, Templates-Second

Conversation drives creation. Templates capture decisions. Why: Premature template-filling locks in choices before the human has thought through implications. Dialogue first ensures templates reflect real decisions.

Start every phase with a dialogue about vision and constraints
Fill templates AFTER discussion, not before
If the user has strong opinions, skip proposal and capture directly
If the user is uncertain, offer more options with reasoning

3. File-as-Memory

All project state lives in human-readable markdown files in the project directory. Why: Markdown files survive tool failures, session resets, and can be read/edited by the human without any specialized software. No database lock-in.

Read files to restore context between sessions
Output updated files after every phase — the human can read and edit directly
No hidden state. No databases. Just markdown.
Detect and respect manual edits to any file

4. Nonlinear Phase Access

Phases are listed in order but are not a rigid pipeline. Why: Stories evolve during writing — a linear pipeline would force early guesses to override later discoveries. Characters grow their own logic; the system must accommodate that.

Jump back to any phase at any time to revise
Changes propagate forward (e.g., new character affects outline)
The state file tracks which phases are complete and which need rework
No phase is ever "locked" -- the story evolves

5. Anti-AI as Narrative Technique

Fight AI-sounding prose at the craft level, not the word level.

Address sentence structure, rhythm, and narrative approach — not just word choice
Use word replacement lists as a last resort, not the primary defense
Target prose that could not have been written by filling in a template
See references/anti-ai-system.md for the full technique library

6. Relentless Validation (HARD RULE — MANDATORY IN ALL COLLABORATIVE PHASES)

After every creative decision in Phases 1–6, apply five mandatory questioning rules: post-selection probing ("why this one?"), contradiction detection (flag conflicts with prior choices immediately), readiness confirmation (one final question before advancing), one-question-at-a-time (never stack), and always recommend (suggest a preferred resolution). The AI must initiate questioning — never wait for the user to prompt it. See references/proposal-system.md for the complete protocol with examples.

Iron Rules (MANDATORY — EVERY WRITING SESSION)

Non-negotiable. Apply to every draft, every revision, every edit. Full definitions in references/iron-rules.md.

Escalation Rule: Same error category in two chapters → fix text AND add/strengthen a rule. AI learns from explicit rules, not text corrections.

| IR | Title | One-Line Summary | |----|-------|-----------------| | IR-1 | POV Lock | Only describe what POV character perceives. Limited info → hedging language, not absolutes. | | IR-2 | Vocabulary Register Audit | 16 modern terms forbidden in non-modern settings. Replace on sight. | | IR-3 | Context Loading Protocol | P0→P1→P2 loading order. 15K char hard cap. Never load full prior chapter. Load milestone direction, not chapter-level outline entries. | | IR-4 | State Extraction = Complete | Chapter not done until state snapshot + timeline + novel-state updated. | | IR-5 | Anti-AI 9-Point Self-Check | Pre-delivery: Show Don't Tell, Rhythm, Subtext, Register, Asymmetry, Punctuation, Meta-Markers, Citation, Voice Swap. Any fail → rewrite. | | IR-6 | Prose Iron Laws (9 Rules) | Narrator never concludes. No analysis-speak. Surprise markers limited. Max 2 same sensation. No planning terms. Hard bans on "不是...而是..." / excessive "——". Questions use "？". No meta-markers. Numbers pass plausibility. | | IR-7 | Cool Point Engineering | Satisfaction = Oppression × Delivery × Surprise. Density: 2-3ch ≥ 1 micro, 5ch ≥ 1 combo, 10-15ch ≥ 1 milestone. Full modes in excitement-engineering.md. | | IR-8 | Psychology 3-Layer + Emotion 4-Level | Use Conscious/Subconscious/Unconscious layers. Match emotion intensity (1-4) to importance. Full techniques in emotion-psychology.md. | | IR-9 | Citation Integrity — Zero Fabrication | Verify ALL factual claims with tool calls before asserting. Never fabricate quotes. Never cite summaries as file content. Mark unverified claims as [未验证]. | | IR-10 | Reader Experience Tracking | Eight-dimension tracking (emotion range/interaction density/promise delivery/cool points/experience goals/genre alignment/world-building delivery/activity diversity). Phase 6 structural prevention + Phase 7 per-chapter detection + Phase 8 audit. WARNING→next chapter responds. MUST/CRITICAL→this chapter responds. |

Phase Overview

Eight phases of novel creation. Phases produce files. Files are memory. Memory persists across sessions.

Phase 1: Project Setup          --> novel-state.md, project-config.md
Phase 2: Core Concept + Title   --> title-synopsis.md (logline + working title)
Phase 3: World-Building         --> world.md
Phase 4: Character Design       --> characters/main/<name>.md + characters/supporting/<name>.md + knowledge-state.md
Phase 5: Plot Architecture      --> plot.md
Phase 6: Outline + Pacing       --> outline.md (volumes + milestones) + timeline.md + foreshadowing-ledger.md
Phase 7: Chapter Writing        --> chapters/chapter-NNN.md (via direction proposals)
Phase 8: State Extraction       --> state/chNNN.md + updates novel-state.md + timeline.md + world.md (if new lore) + foreshadowing-ledger.md + knowledge-state.md

Dependency Map

Phase 1 ──> Phase 2 ──> Phase 3 ──> Phase 4 ──> Phase 5 ──> Phase 6 ──> Phase 7
            (concept)   (world)     (chars)     (plot)      (outline)  (writing)
                 +─── any phase can loop back ────+
                                          Phase 8 (runs after every chapter)

Workflow Steps

⚠️ PHASE LOADING RULE: Before entering ANY phase below, MUST Read the reference files listed in that phase's PRE-LOAD line. Skipping the Read = skipping the rules = producing inferior work. No exceptions.

Phase 1: Project Setup

Establish the project container and initial vision.

⚠️ PRE-LOAD: references/proposal-system.md

Create project directory at user-specified location (default: ~/novels/<title-slug>/)
Dialogue: Ask about genre, tone, target length, audience, and initial spark
Create novel-state.md with phase tracker and project metadata
Create project-config.md with agreed parameters

Output files: novel-state.md, project-config.md Templates: templates/novel-state.md, templates/project-config.md Quality gate: directory exists, both files written, user confirmed vision ⚠️ VALIDATION REQUIRED: Before advancing to Phase 2, confirm readiness — ask the user one question that tests whether the project vision is truly settled.

Phase 2: Core Concept + Title

Distill the story's soul before building anything. A strong concept guides every later decision.

⚠️ PRE-LOAD: references/proposal-system.md

Dialogue: Ask what excites the user most about this story. What's the emotional core? What's the "what if?"
Propose 2-3 logline options — each in one sentence, each capturing a different angle of the core conflict
Propose 2-3 title options with reasoning (genre-appropriate, memorable, not generic)
Capture core concept: logline, central conflict, thematic question, emotional promise to reader
Create title-synopsis.md with working title, logline, and concept notes (full synopsis refined after Phase 5)

Output file: title-synopsis.md (initial version — logline + working title + concept) Template: templates/title-synopsis.md Quality gate: logline is one clear sentence with conflict + stakes, title resonates with genre and tone ⚠️ VALIDATION REQUIRED: After user picks logline and title, ask "why this one?" — surface the real reason. Before advancing to Phase 3, check for contradictions between the core concept and the genre/tone choice.

Phase 3: World-Building

Build the story world through dialogue, not questionnaire.

⚠️ PRE-LOAD: references/world-building-guide.md

Dialogue: Ask what makes this world different from ours. Start with the one thing the user is most excited about.
Propose 2-3 world-building approaches (hard magic system vs. soft; near-future vs. far; geopolitical focus vs. cultural)
Build iteratively: flesh out the areas that matter to the story first
Create world.md organized by what the reader needs to know, not encyclopedia order

Output file: world.md Template: templates/world.md Detailed guide: references/world-building-guide.md Quality gate: rules are internally consistent, key conflicts emerge from world design, no unexplained contradictions ⚠️ VALIDATION REQUIRED: After each world-building choice, check for contradictions with the core concept (Phase 2). Before advancing to Phase 4, ask one question that tests whether the world truly serves the story's emotional promise.

Phase 4: Character Design

Create characters who drive plot through desire and flaw.

⚠️ PRE-LOAD: references/character-design-guide.md（知识状态追踪已整合入 references/consistency-system.md Section 1.4，按需查阅）

Start with the protagonist: what do they want, what stops them, what will they sacrifice
Propose 2-3 character archetypes as starting points, let user pick or blend
Build supporting cast based on story needs (antagonist, mirror, foil, catalyst)
Create character files: main characters get detailed profiles in characters/main/<name>.md; supporting characters get brief profiles in characters/supporting/<name>.md
Create knowledge-state.md for cumulative knowledge tracking across chapters (updated after each chapter in Phase 8)

Output: characters/main/<name>.md (per main character) + characters/supporting/<name>.md (per supporting character) + knowledge-state.md Detailed guide: references/character-design-guide.md Template: templates/character-card.md, templates/knowledge-state.md Quality gate: each character has distinct voice, conflicting desires exist between characters, no character is purely good or evil without reason ⚠️ VALIDATION REQUIRED: After each character is defined, check for contradictions with the world rules (Phase 3) and core concept (Phase 2). Ask "does this character's desire create genuine conflict with other characters?" Before advancing, confirm the cast is complete enough to drive the plot.

Phase 5: Plot Architecture

Design the structural backbone before filling in details.

⚠️ PRE-LOAD: references/plot-architecture.md

Propose 2-3 structural frameworks (three-act, seven-point, hero's journey, web-novel arc structure, etc.) with tradeoffs
Define the central question the story answers
Map major turning points and their emotional targets
Create plot.md with structure, central conflict, key turning points, and thematic throughlines

⚠ 规划深度限制（防止过早锁定）： 只详细规划前两个卷的转折点和角色弧线。第三卷及以后只写方向性描述（"主角失去一切"），不写具体节拍。远期内容在写作推进到时再细化——到那时，角色和情节已经长出了自己的逻辑，规划会更准确。过早细化远期 = 把猜测当承诺。

Output file: plot.md Template: templates/plot.md Detailed guide: references/plot-architecture.md Quality gate: central conflict is clear, stakes escalate, resolution follows from established rules ⚠️ VALIDATION REQUIRED: After the plot structure is chosen, check for contradictions with character desires (Phase 4) and world constraints (Phase 3). Ask "does every turning point require a character to make a painful choice?" Before advancing, confirm the plot structure serves the core concept's emotional promise.

Phase 6: Outline + Pacing

Plan the story's milestone architecture. NOT a per-chapter script — a roadmap with key events and open space for discovery.

⚠️ PRE-LOAD: references/outline-template-guide.md, references/pacing-curve-reference.md

Propose 2-3 volume structures (how many volumes, how many chapters per volume)
Define 3-5 milestones per volume: the MUST-HAPPEN events that drive the story forward
Set volume-level tone and tension direction (rising / peaking / recovering), NOT per-chapter tension numbers
Leave the space between milestones OPEN — these will be filled during Phase 7 through discussion
类型承诺结构审查（MILESTONE-LEVEL GENRE CHECK）: 加载 title-synopsis.md（主题材/副题材/核心卖点），对每个里程碑跨度检查：该跨度内的主导情境是否结构性地支持类型承诺？问："如果主角在这个情境中 N 章，类型承诺能兑现吗？" 连续 ≥5 章的里程碑跨度排除类型活动 → 必须重新设计里程碑（不是等 Phase 7 再修）。根因：Phase 7 的类型检查是章级检测——如果大纲结构性地排除了类型活动，Phase 7 每章都会触发 MUST_ALIGN 但无力回天。预防必须在 Phase 6。
Create outline.md with volume overview + milestones + tension direction
Create timeline.md for scene-level time tracking (updated after each chapter)
Create foreshadowing-ledger.md for foreshadowing tracking (initially empty, populated from Phase 8)

⚠ 规划深度递减原则（防止锚定过死）：

当前卷（即将写的卷）：可以列里程碑 + 章节级条目（如黄金三章等关键章节）
下一卷：只列里程碑 + 方向性描述。不列章节级细节。
更远的卷：只写卷级概述（Central Question + Start/End State）。连里程碑都不细化。
原则：写作推进到某卷时，再回头细化该卷的规划。到那时，前文已写的内容会告诉你角色真正需要什么——而不是靠 Phase 6 时的猜测。

Output: outline.md (volumes + milestones), timeline.md (empty initially), foreshadowing-ledger.md (initially empty) Detailed guide: references/outline-template-guide.md Template: templates/outline-master.md, templates/timeline.md, templates/foreshadowing-ledger.md Quality gate: every milestone has clear narrative purpose, milestones escalate across volumes, breathing room exists between peaks, no milestone span structurally excludes genre promise for ≥5 chapters, 时间节奏结构审查通过（每个里程碑有合理的时间跨度规划，里程碑间有跳转点） ⚠️ VALIDATION REQUIRED: After the outline is complete, check for contradictions with the plot turning points (Phase 5). Ask "does every milestone earn its place?" Then run 类型承诺结构审查（step 5）+ 时间节奏结构审查（outline-template-guide.md Smoke Test §7）— confirm every milestone span supports the genre promise and has planned time pacing. Before advancing to writing, do a final readiness check — confirm the user is satisfied with the story shape, not just "good enough to start."

Phase 7: Chapter Writing

Write chapters through collaborative discussion. One chapter at a time. Each chapter starts with a direction proposal — the AI never writes without the user choosing where to go.

⚠️ PRE-LOAD (TIERED LOADING — load in order):

| Tier | When to Load | File | Content | |------|-------------|------|---------| | 1 (PRE-LOAD) | Before direction proposal | references/chapter-writing-guide.md + references/pre-writing-brief.md | Operational guide (direction proposals, scene structure, quality guardrails) + Pre-writing briefing format (7-segment memo, 5-segment task sheet) | | 2 (PRE-DRAFT) | After user selects direction, before drafting | references/anti-ai-system.md Part 1 | Writing-time defense: 7 structural layers, 8 rewrite algorithms, hard bans | | 3 (SELF-CHECK) | After drafting, before delivery | references/anti-ai-system.md Appendix + references/advanced-detection.md | Post-writing detection: pattern system, clustering, signal stacking, word bank | | 4 (ON-DEMAND) | Only for deep prose diagnosis | references/prose-quality-framework.md | Four reward channels, psychic distance, free indirect discourse — NOT loaded by default |

Never load all tiers simultaneously. Tier 1 is always loaded. Tiers 2-3 are loaded when needed. Tier 4 is reference only.

⚠️ PREFLIGHT (MANDATORY — two phases):

Phase A — BEFORE direction proposal (load context):

NOVEL_FORGE_PREFLIGHT_A: preload=pass|fail ir3_context=pass|fail reader_experience=pass|fail settings_gap=pass|fail foreshadowing_lifecycle=pass|fail

Load references per PRE-LOAD, load project state per IR-3, load novel-state.md 读者体验追踪 + 时间节奏追踪（检查 WARNING/MUST 警报），扫描 world.md + outline.md 识别本章方向需要的场景元素缺口，扫描活跃伏笔摘要检查伏笔生命周期阈值（15/30/50），then propose 2-3 direction options. WARNING/MUST 警报（含时间节奏 + 伏笔生命周期）必须在方向选项中响应。每个方向选项标注设定缺口（如有）。

Phase B — BEFORE drafting (after user selects direction):

NOVEL_FORGE_PREFLIGHT_B: direction_proposed=pass|fail user_selected=pass|fail ir1_pov=pass|fail ir2_register=pass|fail|n/a ir6_prose=pass|fail ir5_check=pass|fail reader_experience=pass|fail

direction_proposed=pass requires 2-3 options actually shown to user. user_selected=pass requires explicit user pick/blending. reader_experience=pass requires Segment 8 (读者体验设计) 已填写（情感目标≠前章，爽点/互动安排已确认）。ALL must be pass before drafting.

Propose 2-3 direction options for this chapter based on: current volume milestones, prior chapter state snapshot (including Reader Knowledge Delta), reader knowledge gaps (from world.md Reader Delivery Tracker + prior snapshot's 读者认知缺口), and where the story wants to go next. NOT based on pre-written chapter-level outline entries. Those entries are Phase 6 guesses — use them as ONE input among many, not as the answer. Each direction option should note: (a) what reader knowledge it delivers or advances, (b) what reader knowledge it requires readers to already have, (c) what settings gaps exist — does this direction require elements not yet in world.md/outline.md/plot.md? If so, classify as major (needs pre-planning) or minor (can emerge during writing). If required knowledge is undelivered, the option must include a delivery mechanism (展示后果/对比/新手视角/回忆/对话 — never "As You Know, Bob").
User selects a direction (or proposes their own, or blends options) — DO NOT draft until user has explicitly chosen
- Optional: if user requests writing guidance, activate coach mode — offer 2-3 opening versions, annotate techniques, provide alternate key-scene versions, and post-writing self-assessment. See references/advanced-workflows.md Section 一.
Load context per IR-3 (P0→P1→P2, 15K char cap, never load full prior chapter)
State PREFLIGHT_B — declare all gates pass before drafting
Draft the chapter following Iron Rules IR-1 (POV lock), IR-2 (register audit), IR-5 (anti-AI check), IR-6 (prose iron laws), IR-7 (cool point), IR-8 (psychology layers)
Self-review: IR-5 9-point check + IR-6 9 iron laws + quality score >= 12/20（评分标准见 pre-writing-brief.md Section 3.1 十大标准20分制）
Write chapter file to chapters/chapter-NNN.md
IMMEDIATELY execute Phase 8 — per IR-4, the chapter is not done until state is extracted (Phase 8 handles timeline update)

Output: chapters/chapter-NNN.md（Phase 8 随后自动执行，产出 state 快照 + 更新 timeline） Quality gate: PREFLIGHT declared + IR-5 checks pass + quality >= 12/20（评分标准见 pre-writing-brief.md Section 3.1）+ state snapshot per IR-4

Phase 8: State Extraction (MANDATORY — runs after EVERY chapter)

After each chapter, create an immutable state snapshot file AND update supporting files. This prevents "amnesia" across chapters — every chapter's aftermath is preserved exactly, not overwritten.

⚠️ PRE-LOAD (CRITICAL): references/consistency-system.md, references/state-extraction-guide.md

Create state/chNNN.md using the state snapshot template (one file per chapter, never overwrite, NNN = zero-padded chapter number). Populate Snapshot Identity: chapter number, title, POV character, story timestamp, real date
Record chapter summary (≤200 chars): what happened, what changed
Record character state changes: for each character who appeared, capture physical, emotional, location, status, items/skills gained/lost, key changes. Include 伤势追踪表 for any injury. Record knowledge state changes (Knows/Believes/Doesn't Know per character)
Record relationship changes: any relationship temperature shifts with cause and direction
Record foreshadowing updates: new plants, advances, resolutions, deferrals — with chapter IDs. 对每个活跃伏笔计算无接触章数，更新生命周期状态（pass/浇水候选/WARNING/MUST_RESOLVE）。HARVEST 操作前必须回读种植章节的 state snapshot 验证一致性。 Update foreshadowing-ledger.md accordingly
Record timeline: story-internal time position, gap since previous chapter
Record new elements: new proper nouns, new locations, new props introduced
Record open questions: questions raised, still open, or answered this chapter
Verify new lore elements against world.md and characters/ — add consistent new elements to canon files
Reader knowledge audit: identify what the READER learned this chapter (separate from character knowledge), assess delivery sufficiency (full / partial / label-only), check world.md Reader Delivery Tracker for unfilled items, update state snapshot's Reader Knowledge Delta. Flag gaps persisting ≥3 chapters as "must deliver next chapter"（详见 state-extraction-guide.md §8） 10b. 读者体验审计: 执行九维审计（情感范围/互动密度/承诺兑现/爽点传递/体验目标验证/类型承诺对齐/活动多样性/世界观交付/思维留白）+ 时间节奏审计 + 角色出场追踪审计（命名检查 + 档案创建/升级检查），更新 state-snapshot.md "读者体验 Delta" + novel-state.md "读者体验追踪" + "时间节奏追踪" + "角色出场追踪"（详见 state-extraction-guide.md §9-10）
Update timeline.md with scene-level entries for this chapter
Update novel-state.md: add chapter summary to 章节摘要 table, update 活跃伏笔摘要（类型/紧迫度从 foreshadowing-ledger.md 同步）, update 角色状态摘要, update 术语一致性表 and 关键数字表, update current_chapter counter
Update knowledge-state.md: merge snapshot knowledge changes into cumulative file
Write Delta Summary: 3-5 bullet points of the most important changes for quick reference by next chapter
Run consistency check: verify state snapshot against chapter text and world rules, flag contradictions

Output: state/chNNN.md (immutable snapshot, including Reader Knowledge Delta + 读者体验 Delta) + updated novel-state.md (including 读者体验追踪) + updated timeline.md + updated foreshadowing-ledger.md + updated knowledge-state.md + updated world.md (if new lore or Reader Delivery Tracker update) + updated outline.md/plot.md/prose_style.md (if emergent settings require) Template: templates/state-snapshot.md Detailed guide: references/state-extraction-guide.md Consistency system: references/consistency-system.md Quality gate: state snapshot written (including Reader Knowledge Delta + 读者体验 Delta), novel-state.md updated (including 读者体验追踪), timeline updated, no contradictions with prior state, 读者体验九维审计完成（含思维留白审计），伏笔生命周期已检查

Phase 8.5: Volume-End Settings Audit (卷末设定审计)

每卷写完后、下一卷开始前执行。AI 自动执行，执行前先让用户确认审计范围。

⚠ PRE-LOAD: references/outline-template-guide.md §8（卷末设定审计流程）

审计本卷所有 state 快照 — 检查"涌现设定捕获"记录，汇总本卷所有新设定
审计所有项目文件 — world.md / outline.md / plot.md / prose_style.md / novel-state.md / timeline.md
生成审计报告 — 包含补漏/调整/展望三部分（详见 outline-template-guide.md §8）
呈现给用户审阅 — 用户确认审计范围和发现无遗漏
用户确认后执行更新 — 更新所有需要变更的文件
更新 novel-state.md 决策记录 — 新增审计条目

Output: 所有项目文件更新 + novel-state.md 决策记录 + 下一卷设定预规划清单 Detailed guide: references/outline-template-guide.md §8

File Structure Reference

<project-dir>/
  novel-state.md          # Phase tracker, chapter summaries, foreshadowing, 术语表, 数字表
  project-config.md       # Genre, tone, length, audience
  world.md                # World rules — minimum viable, grows with content
  characters/main/        # Main character profiles (detailed)
  characters/supporting/  # Supporting characters (brief, created as they appear)
  knowledge-state.md      # Cumulative knowledge tracking per character (Phase 4+)
  relationship-map.md     # Relationship network (created as needed in Phase 4+)
  plot.md                 # Structure, central conflict, turning points
  outline.md              # Volumes + milestones (NOT per-chapter scripts)
  foreshadowing-ledger.md # Foreshadowing tracking (Phase 6+, updated in Phase 8)
  timeline.md             # Scene-level time tracking (updated after each chapter)
  title-synopsis.md       # Title, synopsis, metadata
  chapters/               # chapter-001.md, chapter-002.md, ...
  state/                  # ch001.md, ch002.md, ... (immutable snapshots per IR-4, zero-padded)
  import/                 # (Bootstrap only) Original imported material

Error Handling

Flag problems to the user with specific details and proposed resolutions — never silently patch or ignore. See references/error-handling.md for the full protocol.

Examples

New: User says "I want to write a xianxia novel" → Phase 1, create project, begin dialogue
Resume: User says "继续写我的小说" → Read novel-state.md, identify current phase, resume
Targeted: User says "chapters 15-25 drag" → Jump to Phase 6, re-examine outline, propose fixes

References

Loaded on demand — each phase's PRE-LOAD directive specifies which are mandatory.

Authority declarations: 上下文加载协议 → SKILL.md IR-3 · Anti-AI 防御与检测 → anti-ai-system.md · 一致性追踪（含知识状态、伏笔账本）→ consistency-system.md · 节奏张力 → pacing-curve-reference.md

Phase-Specific References (loaded per PRE-LOAD directive)

Core Craft: anti-ai-system.md (写作防御 Part 1 + 写后检测 Part 2) · advanced-detection.md (写后审计，Tier 3 加载) · chapter-writing-guide.md · prose-quality-framework.md (Tier 4, on-demand only) · writing-styles.md · emotion-psychology.md · combat-scenes.md

Story Architecture: excitement-engineering.md · plot-architecture.md · outline-template-guide.md · pacing-curve-reference.md · narrative-craft.md · subplot-management.md · genre-configs.md · craft-specialization.md

World & Characters: world-building-guide.md · character-design-guide.md

Consistency & State: consistency-system.md (含知识状态追踪 + 伏笔账本系统) · state-extraction-guide.md · pre-writing-brief.md · editorial-roles.md

Process & Advanced: proposal-system.md · memory-management.md · error-handling.md · advanced-workflows.md · revision-workflow.md

Templates: project-config.md · novel-state.md · title-synopsis.md · world.md · character-card.md · plot.md · outline-master.md · timeline.md · chapter-plan.md · chapter-draft.md · state-snapshot.md · foreshadowing-ledger.md · knowledge-state.md · relationship-map.md · editorial-report.md

Forge de Romans

Recommandé pour