sumeru-worldbuilder

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

网文创作世界构建师 (worldbuilder)

Web Novel Creation World Builder (worldbuilder)

触发关键词

Trigger Keywords

我想写小说、写一本网文、从零开始创作小说、帮我写本XX类型的小说、我要写本小说、给我整个小说创作流程、自动写小说、小说创作一站式服务、帮我完成一本小说、我只有创意怎么写小说、从零开始写网文、小说全流程创作

I want to write a novel, Write a web novel, Create a novel from scratch, Help me write a novel of XX genre, I want to write a novel, Give me the entire novel creation process, Auto-write a novel, One-stop novel creation service, Help me finish a novel, How to write a novel with only an idea, Write a web novel from scratch, Full-process novel creation

核心功能

Core Features

worldbuilder 是网文创作的一站式主控技能，负责统筹协调从创意萌芽到作品完稿的完整创作链路，构建完整统一的故事世界。通过智能编排各专项技能的调用顺序与参数传递，实现自动化、流水线式的网文创作体验：

选题策划：调用
```
sumeru-topic
```
进行市场分析、选题定位，生成核心创意与卖点
大纲设计：调用
```
sumeru-outline
```
构建完整世界观、人物设定、分卷大纲与完整章节细纲
内容创作：调用
```
sumeru-write
```
按大纲进行分章节内容撰写，保持风格统一（必须完成所有章节后才进入下一阶段）
逻辑审查：调用
```
sumeru-review
```
对所有已完成章节进行全面审查，校验时间线一致性、人物行为逻辑、前后剧情连贯性
内容润色：调用
```
sumeru-polish
```
对所有已审查章节进行文笔优化、细节丰满、节奏调整
完稿校验：调用
```
sumeru-finalize
```
对所有已润色章节完成错别字检查、标点规范、逻辑漏洞最终排查与作品打包

worldbuilder is a one-stop master skill for web novel creation, responsible for coordinating the complete creation chain from idea germination to final draft, and building a complete and unified story world. Through intelligent orchestration of the calling sequence and parameter transfer of each specialized skill, it achieves an automated, assembly-line web novel creation experience:

Topic Planning: Call
```
sumeru-topic
```
for market analysis, topic positioning, and generate core ideas and selling points
Outline Design: Call
```
sumeru-outline
```
to build a complete worldview, character settings, volume outlines, and detailed chapter outlines
Content Creation: Call
```
sumeru-write
```
to write chapter-by-chapter content according to the outline, maintaining a consistent style (Must complete all chapters before proceeding to the next stage)
Logic Review: Call
```
sumeru-review
```
to conduct a comprehensive review of all completed chapters, verifying timeline consistency, character behavior logic, and plot coherence
Content Polishing: Call
```
sumeru-polish
```
to optimize writing style, enrich details, and adjust pacing for all reviewed chapters
Finalization Check: Call
```
sumeru-finalize
```
to complete typo checking, punctuation standardization, final logical loophole排查, and work packaging for all polished chapters

⚠️ 全局约束：子Agent并行处理规则

⚠️ Global Constraint: Sub-Agent Parallel Processing Rules

worldbuilder 在协调所有涉及章节级操作的子技能时，强制执行 AGENTS.md 中定义的子Agent并行处理规则：

每个子Agent最多负责3个章节（硬性约束，详见 AGENTS.md "子Agent并行处理规则"）

此规则适用于以下所有阶段：

写作阶段（sumeru-write）
审查阶段（sumeru-review）：审查和轻量修复
润色阶段（sumeru-polish）
完稿阶段（sumeru-finalize）
细纲生成（sumeru-outline）

设计原因：详见 AGENTS.md "子Agent并行处理规则"

worldbuilder的调度责任：

worldbuilder在调用各子技能时，必须确保子技能遵循3章/Agent的约束
如果子技能未自动遵守此约束，worldbuilder需要通过参数或指令强制执行
监控子技能的执行过程，确认Agent分配符合约束

When coordinating all sub-skills involving chapter-level operations, worldbuilder enforces the Sub-Agent Parallel Processing Rules defined in AGENTS.md:

Each sub-Agent is responsible for a maximum of 3 chapters (hard constraint, see AGENTS.md "Sub-Agent Parallel Processing Rules")

This rule applies to all the following stages:

Writing Stage (sumeru-write)
Review Stage (sumeru-review): Review and lightweight fixes
Polishing Stage (sumeru-polish)
Finalization Stage (sumeru-finalize)
Detailed Outline Generation (sumeru-outline)

Design Rationale: See AGENTS.md "Sub-Agent Parallel Processing Rules"

worldbuilder's Scheduling Responsibilities:

When calling each sub-skill, worldbuilder must ensure that the sub-skill follows the 3 chapters/Agent constraint
If the sub-skill does not automatically comply with this constraint, worldbuilder needs to enforce it through parameters or instructions
Monitor the execution process of sub-skills to confirm that Agent allocation meets the constraint

Skill 协调流程

Skill Coordination Flow

worldbuilder 负责以下数据流转和协调工作：

用户需求
    ↓
[收集创作需求 → 保存到 .sumeru/session/requirements.json]
    ↓
[sumeru-topic] 选题策划
    → 输出: 选题策划报告.md, .sumeru/topic/options.json
    ↓
[sumeru-outline] 大纲设计（**生成完整章节细纲**）
    → 输入: .sumeru/topic/options.json (可选)
    → 输出: 小说大纲_*.md, .sumeru/outline/*.json（含 chapter-outlines.json）
    ↓
[阶段检查点 1] 检查大纲完整性，确认章节细纲已生成
    ↓
[sumeru-write] 章节撰写（**细纲驱动，并行批量生成，每个Agent最多3章**）
    → 输入: .sumeru/outline/chapter-outlines.json
    → 输出: chapters/*.md, .sumeru/write/*.json
    → ✅ **必须完成所有章节**（检查章节数与细纲一致）
    → ⚠️ **遵循全局3章/Agent约束**
    ↓
[阶段检查点 2] 验证所有章节已完成，记录写入进度
    ↓
[sumeru-review] 逻辑审查（**审查所有章节，每个Agent最多3章**）
    → 输入: .sumeru/outline/*.json, chapters/*.md
    → 输出: 剧情审查报告.md, .sumeru/review/*.json, .sumeru/review/fix-plan.json
    → ✅ **必须完成全本审查**
    → ⚠️ **遵循全局3章/Agent约束**
    ↓
[阶段检查点 3] 验证审查完成，检查 fix-plan.json 是否有重写修复项
    ↓
{fix-plan.json 有重写修复项?}
    →|是| [调用sumeru-write重写指定章节 → 直接修改 chapters/（自动备份到 .sumeru/write/original/）]
    →|否| 继续
    ↓
[review 轻量修复已直接修改 chapters/，无需额外应用步骤]
    ↓
[sumeru-polish] 内容润色（**润色所有章节，每个Agent最多3章**）
    → 输入: chapters/*.md, .sumeru/review/*.json
    → 输出: chapters/*.md（润色后直接修改，自动备份到 .sumeru/write/original/）, .sumeru/polish/*.json
    → ✅ **必须完成全本润色**
    → 📝 **润色结果直接修改 chapters/，修改前自动备份到 .sumeru/write/original/**
    → ⚠️ **遵循全局3章/Agent约束**
    ↓
[阶段检查点 4] 验证润色完成
    ↓
[sumeru-finalize] 完稿校验（**处理所有章节，每个Agent最多3章**）
    → 输入: chapters/*.md（已包含review修复和polish润色后的内容）
    → 输出: publish/*, .sumeru/finalize/*
    → ⚠️ **遵循全局3章/Agent约束**

worldbuilder is responsible for the following data flow and coordination work:

User Requirements
    ↓
[Collect Creation Requirements → Save to .sumeru/session/requirements.json]
    ↓
[sumeru-topic] Topic Planning
    → Output: Topic Planning Report.md, .sumeru/topic/options.json
    ↓
[sumeru-outline] Outline Design (**Generate complete detailed chapter outlines**)
    → Input: .sumeru/topic/options.json (optional)
    → Output: Novel Outline_*.md, .sumeru/outline/*.json (including chapter-outlines.json)
    ↓
[Stage Checkpoint 1] Check outline completeness, confirm detailed chapter outlines are generated
    ↓
[sumeru-write] Chapter Writing (**Outline-driven, parallel batch generation, max 3 chapters per Agent**)
    → Input: .sumeru/outline/chapter-outlines.json
    → Output: chapters/*.md, .sumeru/write/*.json
    → ✅ **Must complete all chapters** (Check that the number of chapters matches the outline)
    → ⚠️ **Follow global 3 chapters/Agent constraint**
    ↓
[Stage Checkpoint 2] Verify all chapters are completed, record writing progress
    ↓
[sumeru-review] Logic Review (**Review all chapters, max 3 chapters per Agent**)
    → Input: .sumeru/outline/*.json, chapters/*.md
    → Output: Plot Review Report.md, .sumeru/review/*.json, .sumeru/review/fix-plan.json
    → ✅ **Must complete full-book review**
    → ⚠️ **Follow global 3 chapters/Agent constraint**
    ↓
[Stage Checkpoint 3] Verify review completion, check if fix-plan.json has rewrite repair items
    ↓
{Does fix-plan.json have rewrite repair items?}
    →|Yes| [Call sumeru-write to rewrite specified chapters → Directly modify chapters/ (auto-backup to .sumeru/write/original/)]
    →|No| Continue
    ↓
[Review lightweight fixes have directly modified chapters/, no additional application steps required]
    ↓
[sumeru-polish] Content Polishing (**Polish all chapters, max 3 chapters per Agent**)
    → Input: chapters/*.md, .sumeru/review/*.json
    → Output: chapters/*.md (directly modified after polishing, auto-backup to .sumeru/write/original/), .sumeru/polish/*.json
    → ✅ **Must complete full-book polishing**
    → 📝 **Polishing results directly modify chapters/, auto-backup to .sumeru/write/original/ before modification**
    → ⚠️ **Follow global 3 chapters/Agent constraint**
    ↓
[Stage Checkpoint 4] Verify polishing completion
    ↓
[sumeru-finalize] Finalization Check (**Process all chapters, max 3 chapters per Agent**)
    → Input: chapters/*.md (already includes review fixes and polished content)
    → Output: publish/*, .sumeru/finalize/*
    → ⚠️ **Follow global 3 chapters/Agent constraint**

关键阶段检查点说明

Key Stage Checkpoint Instructions

每个阶段完成后都会自动更新

WORKBUILDER_PROGRESS.json

，任务重启时从上次未完成的阶段继续：

大纲阶段：确认
```
chapter-outlines.json
```
生成且包含完整章节列表
创作阶段：检查
```
chapters/
```
目录下已生成章节数与细纲一致
审查阶段：确认
```
剧情审查报告.md
```
生成且包含全本审查结果，确认
```
fix-plan.json
```
已生成。review 的轻量修复已直接修改
```
chapters/
```
，修改前已自动备份到
```
.sumeru/write/original/
```
润色阶段：确认润色已直接修改
```
chapters/
```
中的文件。润色修改前已自动备份到
```
.sumeru/write/original/
```
完稿阶段：确认
```
publish/
```
目录下各平台格式导出完成

After each stage is completed,

WORKBUILDER_PROGRESS.json

is automatically updated. When the task restarts, it continues from the last unfinished stage:

Outline Stage: Confirm
```
chapter-outlines.json
```
is generated and contains a complete chapter list
Creation Stage: Check that the number of generated chapters in the
```
chapters/
```
directory matches the outline
Review Stage: Confirm
```
Plot Review Report.md
```
is generated and contains full-book review results, and confirm
```
fix-plan.json
```
is generated. Review lightweight fixes have directly modified
```
chapters/
```
, with auto-backup to
```
.sumeru/write/original/
```
before modification
Polishing Stage: Confirm polishing has directly modified files in
```
chapters/
```
. Auto-backup to
```
.sumeru/write/original/
```
before polishing modification
Finalization Stage: Confirm export of various platform formats in the
```
publish/
```
directory is completed

数据共享机制

Data Sharing Mechanism

所有 skill 通过

.sumeru/

目录共享数据：

```
session/
```
- 全局会话配置、用户需求、进度状态
```
topic/
```
- 选题数据 → 供 outline 使用
```
outline/
```
- 大纲数据 → 供 write、review 使用
- chapter-outlines.json
  - 完整章节细纲 → 供 write 进行并行批量生成
```
write/
```
- 创作进度 → 供 review 使用
```
review/
```
- 审查问题 → 供 write、polish 使用
```
polish/
```
- 润色结果 → 供 finalize 使用
```
finalize/
```
- 完稿数据

All skills share data through the

.sumeru/

directory:

```
session/
```
- Global session configuration, user requirements, progress status
```
topic/
```
- Topic data → Used by outline
```
outline/
```
- Outline data → Used by write, review
- chapter-outlines.json
  - Complete detailed chapter outlines → Used by write for parallel batch generation
```
write/
```
- Creation progress → Used by review
```
review/
```
- Review issues → Used by write, polish
```
polish/
```
- Polishing results → Used by finalize
```
finalize/
```
- Finalized work data

执行流程

Execution Flow

mermaid

flowchart LR
    A[接收创作需求] --> B[参数校验与初始化]
    B --> C[调用 topic 选题策划]
    C --> D[调用 outline 大纲设计]
    D --> E[调用 write 完整章节撰写]
    E -->|✅ 全部章节完成| F[调用 review 全本逻辑审查]
    F --> G{fix-plan.json 有重写项?}
    G -->|是| H[调用 write 重写指定章节]
    H --> I[直接修改 chapters/，自动备份到 .sumeru/write/original/]
    I --> J[调用 polish 全本内容润色]
    G -->|否| J
    J --> K{润色确认?}
    K -->|否| L[针对性调整润色]
    L --> J
    K -->|是| M[调用 finalize 完稿校验]
    M --> N[生成创作报告与作品文件]
    
    subgraph 进度保存
        O[WORKBUILDER_PROGRESS.json]
        E -->|保存进度| O
        F -->|保存进度| O
        J -->|保存进度| O
        M -->|保存进度| O
    end

详细流程说明：

初始化阶段：验证输入参数有效性，创建工作目录，初始化创作状态，创建
```
WORKBUILDER_PROGRESS.json
```
进度文件
需求收集阶段：智能判断用户提供的信息是否充足，如信息不足则自动触发交互式提问引导用户补充需求，确认所有需求后进入下一阶段
选题阶段：基于收集到的完整需求生成3-5个精准匹配的选题方案供选择，确定后进入大纲设计，完成后更新进度文件
大纲阶段：先输出世界观与人设，确认后生成完整大纲和所有章节细纲，完成后更新进度文件
创作阶段：按细纲驱动批量创作所有章节，支持并行生成，必须完成所有章节后才进入下一阶段（遵循全局3章/Agent约束），完成后更新进度文件
审查阶段：调用
```
sumeru-review
```
执行三阶段审查修复流程（遵循全局3章/Agent约束）：
- 第一阶段：全局审查：分析整体剧情脉络、时间线、设定一致性、冲突点分布、伏笔回收状态
- 第二阶段：章节细节审查：逐章检查字数、时间线、人物OOC、物品状态、场景质量、伏笔设置
- 第三阶段：统一修复：
  - 合并全局和章节问题，按严重程度制定修复计划
  - 执行轻量修复（文字修正、段落调整、字数填充等），直接修改
```
chapters/
```
    文件（自动备份到
```
.sumeru/write/original/
```
    ）
  - 对需要重写修复的章节，生成
```
fix-plan.json
```
    ，记录问题与修复建议
- 字数检查与填充：在第二阶段逐章统计字数，对不足的章节自动填充内容（强化场景描写、丰富对话、补充心理活动等）
- 自动修复所有问题：不只是提出问题，而是自动修复所有轻量级问题
- worldbuilder 读取
```
fix-plan.json
```
  ，如有重写项则调用
```
sumeru-write
```
  重写指定章节，直接修改
```
chapters/
```
- 修复完成后重新验证，确保所有问题已解决
- 完成后更新进度文件
润色阶段：调用
```
sumeru-polish
```
进行全本内容润色（遵循全局3章/Agent约束），提供多种润色风格选项（精简/详写/抒情/热血等）
- 润色完成后，直接修改
```
chapters/
```
  中的文件（修改前自动备份到
```
.sumeru/write/original/
```
  ）
- 润色过程和结果记录到
```
.sumeru/polish/
```
  目录
- 完成后更新进度文件
完稿阶段：调用
```
sumeru-finalize
```
对所有润色后的章节进行完稿校验（遵循全局3章/Agent约束），从
```
chapters/
```
目录读取最终内容（已包含review修复和polish润色后的结果），输出多种格式（Markdown/HTML/EPUB）到
```
publish/
```
目录，生成创作总结报告，完成后更新进度文件为最终完成状态

mermaid

flowchart LR
    A[Receive Creation Requirements] --> B[Parameter Validation & Initialization]
    B --> C[Call topic for Topic Planning]
    C --> D[Call outline for Outline Design]
    D --> E[Call write for Complete Chapter Writing]
    E -->|✅ All Chapters Completed| F[Call review for Full-Book Logic Review]
    F --> G{Does fix-plan.json have rewrite items?}
    G -->|Yes| H[Call write to rewrite specified chapters]
    H --> I[Directly modify chapters/, auto-backup to .sumeru/write/original/]
    I --> J[Call polish for Full-Book Content Polishing]
    G -->|No| J
    J --> K{Polishing Confirmation?}
    K -->|No| L[Targeted Adjustment Polishing]
    L --> J
    K -->|Yes| M[Call finalize for Finalization Check]
    M --> N[Generate Creation Report & Work Files]
    
    subgraph Progress Saving
        O[WORKBUILDER_PROGRESS.json]
        E -->|Save Progress| O
        F -->|Save Progress| O
        J -->|Save Progress| O
        M -->|Save Progress| O
    end

Detailed Flow Explanation:

Initialization Phase: Validate input parameter validity, create working directories, initialize creation status, and create the
```
WORKBUILDER_PROGRESS.json
```
progress file
Requirements Collection Phase: Intelligently judge whether the information provided by the user is sufficient. If information is insufficient, automatically trigger interactive questions to guide the user to supplement requirements, then proceed to the next stage after confirming all requirements
Topic Phase: Generate 3-5 precise topic options based on the collected complete requirements for selection. After confirmation, proceed to outline design, and update the progress file upon completion
Outline Phase: First output worldview and character settings, then generate a complete outline and all detailed chapter outlines after confirmation. Update the progress file upon completion
Creation Phase: Batch create all chapters driven by the outline, supporting parallel generation. Must complete all chapters before proceeding to the next stage (follow global 3 chapters/Agent constraint). Update the progress file upon completion
Review Phase: Call
```
sumeru-review
```
to execute the three-stage review and repair process (follow global 3 chapters/Agent constraint):
- Phase 1: Global Review: Analyze overall plot脉络, timeline, setting consistency, conflict distribution, and foreshadowing resolution status
- Phase 2: Chapter Detail Review: Check word count, timeline, character OOC, item status, scene quality, and foreshadowing setup chapter by chapter
- Phase 3: Unified Repair:
  - Merge global and chapter issues, develop a repair plan based on severity
  - Execute lightweight fixes (text correction, paragraph adjustment, word count filling, etc.), directly modifying
```
chapters/
```
    files (auto-backup to
```
.sumeru/write/original/
```
    )
  - For chapters requiring rewrite repair, generate
```
fix-plan.json
```
    to record issues and repair suggestions
- Word Count Check & Filling: In Phase 2, count word count chapter by chapter, automatically fill content for chapters with insufficient word count (enhance scene descriptions, enrich dialogues, supplement psychological activities, etc.)
- Auto-Fix All Issues: Not just raise issues, but automatically fix all lightweight issues
- worldbuilder reads
```
fix-plan.json
```
  , and if there are rewrite items, calls
```
sumeru-write
```
  to rewrite specified chapters, directly modifying
```
chapters/
```
- Re-verify after repair to ensure all issues are resolved
- Update the progress file upon completion
Polishing Phase: Call
```
sumeru-polish
```
for full-book content polishing (follow global 3 chapters/Agent constraint), providing multiple polishing style options (concise/detailed/lyrical/passionate, etc.)
- After polishing, directly modify files in
```
chapters/
```
  (auto-backup to
```
.sumeru/write/original/
```
  before modification)
- Record polishing process and results in the
```
.sumeru/polish/
```
  directory
- Update the progress file upon completion
Finalization Phase: Call
```
sumeru-finalize
```
to conduct finalization checks on all polished chapters (follow global 3 chapters/Agent constraint), read the final content from the
```
chapters/
```
directory (already includes review fixes and polished results), output multiple formats (Markdown/HTML/EPUB) to the
```
publish/
```
directory, generate a creation summary report, and update the progress file to the final completed status upon completion

交互式需求引导

Interactive Requirements Guidance

当用户提供的信息过于简略时（仅输入题材和少量关键词），系统会自动触发交互式提问，一步步引导用户明确创作需求，确保生成内容完全符合预期。

When the information provided by the user is too brief (only input genre and a few keywords), the system will automatically trigger interactive questions, guiding the user to clarify creation requirements step by step to ensure the generated content fully meets expectations.

提问维度（按优先级）

Question Dimensions (by Priority)

基础信息确认（必问）

Basic Information Confirmation (Mandatory)

🎯 题材确认：确认具体题材细分类型，如"玄幻" → "高武玄幻/修仙玄幻/异世玄幻/系统玄幻"
📏 篇幅预期：确认目标字数/章节数，是短篇/中篇/长篇/超长篇
🎯 核心爽点：用户最看重的爽点类型，如"打脸/升级/搞钱/恋爱/权谋"
👥 受众定位：目标读者群体，男频/女频/全年龄，偏向什么年龄层

🎯 Genre Confirmation: Confirm specific sub-genre, e.g., "Xuanhuan" → "High Martial Xuanhuan/Cultivation Xuanhuan/Other World Xuanhuan/System Xuanhuan"
📏 Expected Length: Confirm target word count/chapter count, whether it's short/medium/long/extra-long
🎯 Core Hook Points: The type of core excitement the user values most, e.g., "face-slapping/level-up/making money/romance/political intrigue"
👥 Audience Positioning: Target reader group, male-oriented/female-oriented/all-age, preferred age group

核心设定引导（可选，根据需求深度）

Core Setting Guidance (Optional, based on requirement depth)

🦸 主角设定偏好：主角性格（隐忍/张扬/腹黑/逗比）、身份（废柴/天才/穿越者/重生者）、金手指类型偏好
🎭 反派设定偏好：反派类型（家族敌人/宗门对手/异族/天道）、反派强度
🌍 世界观偏好：偏向什么世界观设定，是否有特别喜欢/讨厌的设定
📖 参考作品：是否有类似风格的参考作品，可以更精准匹配风格

🦸 Protagonist Setting Preferences: Protagonist personality (forbearing/arrogant/scheming/funny), identity (underdog/prodigy/reincarnator/reborn), preferred "golden finger" type
🎭 Antagonist Setting Preferences: Antagonist type (family enemy/sect rival/foreign race/heavenly way), antagonist strength
🌍 Worldview Preferences: Preferred worldview setting, whether there are specific liked/disliked settings
📖 Reference Works: Whether there are reference works with similar styles for more precise style matching

风格偏好设置（可选）

Style Preference Settings (Optional)

✍️ 写作风格：偏好快节奏爽文/细腻精品文/幽默搞笑文/暗黑压抑文
📱 发布平台：计划发布到哪个平台，适配对应平台的节奏和字数要求
⚠️ 禁忌内容：明确不想要的情节、设定、人物类型

✍️ Writing Style: Preference for fast-paced爽文/detailed quality work/humorous work/dark depressing work
📱 Publishing Platform: Planned publishing platform, adapting to the platform's pacing and word count requirements
⚠️ Forbidden Content: Clear unwanted plots, settings, character types

交互模式

Interaction Modes

详细引导模式：强制开启全量交互式提问，即使用户提供了充足信息也会完整走一遍需求确认流程
快速模式：仅提问最核心的3个问题（题材确认、篇幅、核心爽点），其他使用默认值
静默模式：关闭交互式提问，直接基于已有信息生成，适合明确知道自己需求的用户

Detailed Guidance Mode: Forcefully enable full interactive questioning, going through the complete requirement confirmation process even if the user provides sufficient information
Quick Mode: Only ask the 3 most core questions (genre confirmation, length, core hook points), use default values for others
Silent Mode: Turn off interactive questioning, generate directly based on existing information, suitable for users who clearly know their requirements

需求确认机制

Requirements Confirmation Mechanism

所有用户回答自动保存到
```
.sumeru/session/user-requirements.json
```
，全流程各阶段共享使用
提问完成后生成需求确认摘要，用户确认无误后才开始正式创作
支持中途修改，用户可以随时调整之前的回答

All user answers are automatically saved to
```
.sumeru/session/user-requirements.json
```
, shared across all stages of the full process
After questioning is completed, generate a requirements confirmation summary, and start formal creation only after the user confirms it is correct
Support mid-process modification, users can adjust previous answers at any time

引导示例

Guidance Example

> /worldbuilder 玄幻 "废柴逆袭"
🤖 我来帮您完善创作需求，只需要回答几个简单问题：
1️⃣ 请问您想要的玄幻细分类型是？[高武玄幻/修仙玄幻/异世玄幻/系统玄幻/其他]
> 系统玄幻
2️⃣ 预期总篇幅大概多少字？[20万内/20-50万/50-100万/100万以上]
> 100万以上
3️⃣ 您最看重的核心爽点是？[打脸/升级/扮猪吃虎/收小弟/开后宫/其他]
> 打脸+扮猪吃虎
4️⃣ 主角性格偏好？[隐忍腹黑/张扬霸道/逗比搞笑/温柔沉稳/其他]
> 隐忍腹黑
5️⃣ 有没有特别喜欢的参考作品？比如类似《XX》的风格
> 类似《大王饶命》的搞笑风格
...

✅ 需求收集完成，给您确认一下：
类型：系统玄幻
篇幅：100万字以上
核心爽点：打脸+扮猪吃虎
主角性格：隐忍腹黑
风格参考：《大王饶命》搞笑风
是否确认？[Y/n]
> Y
🚀 开始创作！

> /worldbuilder Xuanhuan "Underdog Counterattack"
🤖 Let me help you refine your creation requirements, just answer a few simple questions:
1️⃣ What specific sub-genre of Xuanhuan do you want? [High Martial Xuanhuan/Cultivation Xuanhuan/Other World Xuanhuan/System Xuanhuan/Other]
> System Xuanhuan
2️⃣ What's the expected total word count? [Under 200k/200k-500k/500k-1M/Over 1M]
> Over 1M
3️⃣ What core hook points do you value most? [Face-slapping/Level-up/Hiding Strength/Recruiting Subordinates/Harem/Other]
> Face-slapping + Hiding Strength
4️⃣ Preferred protagonist personality? [Forbearing & Scheming/Arrogant & Domineering/Funny & Humorous/Gentle & Steady/Other]
> Forbearing & Scheming
5️⃣ Are there any favorite reference works? For example, a style similar to "XX"
> Similar to the funny style of "King of Slaughter"
...

✅ Requirements collection completed, let's confirm:
Genre: System Xuanhuan
Length: Over 1 million words
Core Hook Points: Face-slapping + Hiding Strength
Protagonist Personality: Forbearing & Scheming
Style Reference: Funny style of "King of Slaughter"
Confirm? [Y/n]
> Y
🚀 Start creation!

参数说明

Parameter Description

创建时需要提供以下信息：

作品类型（必填）：如玄幻、都市、仙侠、科幻、言情、悬疑等
核心创意关键词（必填）：核心创意关键词，支持多个关键词用"+"连接，如"废柴逆袭+系统流+赘婿"

可选信息（不提供则使用默认值或自动生成）：

作品标题：如不提供则自动生成
预期篇幅：短篇（20万字内）/中篇（20-50万字）/长篇（50-100万字）/超长篇（100万字以上），默认中篇
写作风格：快节奏/均衡/详写/文艺，默认均衡
整体调性：幽默/严肃/励志/暗黑，默认中立
输出目录：作品输出目录路径，默认 ./output
中断恢复：传入上次的创作会话ID，可从断点恢复
跳过阶段：跳过指定阶段（topic/outline/write/review/polish/final），适用于续创或团队分工

The following information is required for creation:

Work Genre (Required): e.g., Xuanhuan, Urban, Xianxia, Sci-Fi, Romance, Mystery, etc.
Core Idea Keywords (Required): Core idea keywords, support multiple keywords connected with "+", e.g., "Underdog Counterattack+System Flow+Son-in-law"

Optional Information (use default values or auto-generate if not provided):

Work Title: Auto-generate if not provided
Expected Length: Short (under 200k words)/Medium (200k-500k words)/Long (500k-1M words)/Extra-long (over 1M words), default is Medium
Writing Style: Fast-paced/Balanced/Detailed/Literary, default is Balanced
Overall Tone: Humorous/Serious/Inspirational/Dark, default is Neutral
Output Directory: Output directory path for the work, default is ./output
Resume Creation: Pass the session ID of the last creation session to resume from the breakpoint
Skip Stages: Skip specified stages (topic/outline/write/review/polish/final), suitable for continuation or team division of labor

使用示例

Usage Examples

基础使用

Basic Usage

undefined

undefined

最简单的调用方式，只指定类型和关键词

Simplest call method, only specify genre and keywords

/worldbuilder 玄幻 "废柴逆袭+系统流"

/worldbuilder Xuanhuan "Underdog Counterattack+System Flow"

都市言情作品，指定标题

Urban romance work, specify title

/worldbuilder 言情 "霸道总裁+契约恋爱" 标题"总裁的契约新娘"

/worldbuilder Romance "Domineering CEO+Contract Relationship" title"The CEO's Contract Bride"

科幻悬疑，长篇幅，快节奏风格

Sci-fi mystery, long length, fast-paced style

/worldbuilder 科幻 "时间循环+密室解谜" 长篇快节奏

undefined

/worldbuilder Sci-Fi "Time Loop+Locked Room Puzzle" long fast-paced

undefined

进阶使用

Advanced Usage

undefined

undefined

指定详细参数的完整调用

Complete call with detailed parameters

/worldbuilder 仙侠 "重生+无敌流+宗门" 标题"重生之太上掌门" 长篇详写风格励志调性

/worldbuilder Xianxia "Rebirth+Invincible Flow+Sect" title"Rebirth of the Supreme Sect Leader" long detailed-style inspirational-tone

从中断点恢复创作

Resume creation from breakpoint

/worldbuilder 玄幻 "废柴逆袭+系统流" 恢复上次创作

/worldbuilder Xuanhuan "Underdog Counterattack+System Flow" resume-last-session

跳过选题阶段，直接从已有大纲继续创作

Skip topic stage, continue creation directly from existing outline

/worldbuilder 都市 "职场+重生" 跳过选题阶段

undefined

/worldbuilder Urban "Workplace+Rebirth" skip-topic-stage

undefined

多风格组合

Multi-Style Combination

undefined

undefined

幽默风都市修仙

Humorous urban cultivation

/worldbuilder 都市 "修仙+打工+搞笑" 均衡风格幽默调性

/worldbuilder Urban "Cultivation+Part-time Job+Funny" balanced-style humorous-tone

暗黑系悬疑推理

Dark mystery推理

/worldbuilder 悬疑 "连环杀人+心理侧写+反转" 详写风格暗黑调性

/worldbuilder Mystery "Serial Murder+Psychological Profiling+Twist" detailed-style dark-tone

热血励志竞技

Passionate inspirational sports

/worldbuilder 竞技 "篮球+天赋+逆袭" 快节奏励志调性

undefined

/worldbuilder Sports "Basketball+Talent+Counterattack" fast-paced inspirational-tone

undefined

错误处理说明

Error Handling Instructions

常见错误类型与解决方案

Common Error Types and Solutions

错误代码	错误信息	原因分析	解决方案
`INVALID_GENRE`	不支持的作品类型	传入的 genre 参数不在支持列表中	检查类型拼写，支持的类型：玄幻、都市、仙侠、科幻、言情、悬疑、历史、游戏、竞技、军事、武侠、轻小说
`KEYWORDS_TOO_LONG`	关键词过长	keywords 参数超过100字符限制	精简关键词，保留最核心的3-5个
`DEPENDENCY_MISSING`	缺少依赖技能	未安装所需的子技能（topic等）	运行 `/find-skills` 查找并安装所有依赖技能
`OUTPUT_DIR_PERMISSION`	输出目录无权限	指定的 output-dir 无写入权限	更换有权限的目录，或使用默认目录
`INVALID_SESSION_ID`	无效的会话ID	resume 参数传入的会话ID不存在	检查会话ID是否正确，或重新开始创作
`STAGE_SKIP_CONFLICT`	阶段跳过冲突	跳过的阶段与后续阶段有依赖关系	移除对前置阶段的跳过，或提供必要的前置文件
`CONTENT_GENERATION_FAILED`	内容生成失败	创作过程中遇到内容审核或模型限制	调整关键词或风格参数，或分阶段手动确认

Error Code	Error Message	Cause Analysis	Solution
`INVALID_GENRE`	Unsupported work genre	The passed genre parameter is not in the supported list	Check genre spelling. Supported genres: Xuanhuan, Urban, Xianxia, Sci-Fi, Romance, Mystery, History, Game, Sports, Military, Wuxia, Light Novel
`KEYWORDS_TOO_LONG`	Keywords too long	The keywords parameter exceeds the 100-character limit	Simplify keywords, keep the core 3-5 keywords
`DEPENDENCY_MISSING`	Missing dependent skills	Required sub-skills (such as topic) are not installed	Run `/find-skills` to find and install all dependent skills
`OUTPUT_DIR_PERMISSION`	No permission for output directory	The specified output-dir has no write permission	Change to a directory with permission, or use the default directory
`INVALID_SESSION_ID`	Invalid session ID	The session ID passed in the resume parameter does not exist	Check if the session ID is correct, or start creation again
`STAGE_SKIP_CONFLICT`	Stage skip conflict	The skipped stage has dependencies with subsequent stages	Remove the skip of the prerequisite stage, or provide necessary prerequisite files
`CONTENT_GENERATION_FAILED`	Content generation failed	Content review or model restrictions encountered during creation	Adjust keywords or style parameters, or confirm manually stage by stage

错误恢复机制

Error Recovery Mechanism

自动重试：对于临时性网络错误，自动重试3次，间隔5秒
断点保存：每完成一个阶段自动保存状态，支持从中断点恢复
回滚选项：对不满意的阶段可选择回滚到上一节点重新开始
错误报告：生成详细的错误日志文件，位于
```
{output-dir}/error.log
```

Auto-Retry: Automatically retry 3 times with 5-second intervals for temporary network errors
Breakpoint Saving: Automatically save status after completing each stage, supporting resume from breakpoint
Rollback Option: Roll back to the previous node to restart for unsatisfactory stages
Error Report: Generate a detailed error log file located at
```
{output-dir}/error.log
```

进阶使用场景

Advanced Usage Scenarios

场景1：团队协作创作

Scenario 1: Team Collaborative Creation

undefined

undefined

策划完成选题和大纲后，交由写手继续

After planning completes topic and outline, hand over to writer

/worldbuilder 玄幻 "废柴逆袭+系统流" 跳过写作、审查、润色、完稿阶段

/worldbuilder Xuanhuan "Underdog Counterattack+System Flow" skip-writing, skip-review, skip-polish, skip-finalize stages

写手接手，从创作阶段继续

Writer takes over, continues from creation stage

/worldbuilder 玄幻 "废柴逆袭+系统流" 跳过选题、大纲阶段恢复上次创作

undefined

/worldbuilder Xuanhuan "Underdog Counterattack+System Flow" skip-topic, skip-outline stages resume-last-session

undefined

场景2：多版本对比创作

Scenario 2: Multi-Version Comparison Creation

undefined

undefined

生成多个版本进行对比

Generate multiple versions for comparison

/worldbuilder 言情 "穿越+宫斗" 标题"清宫·甄嬛传" 文艺风格 /worldbuilder 言情 "穿越+宫斗" 标题"清宫·步步惊心" 快节奏

undefined

/worldbuilder Romance "Time Travel+Palace Intrigue" title"Qing Palace·Legend of Zhen Huan" literary-style /worldbuilder Romance "Time Travel+Palace Intrigue" title"Qing Palace·Startling by Each Step" fast-paced

undefined

场景3：定制化系列作品

Scenario 3: Customized Series Works

undefined

undefined

第一部

First installment

/worldbuilder 玄幻 "系统+升级" 标题"武帝降临" 中篇

/worldbuilder Xuanhuan "System+Level-up" title"The Martial Emperor Arrives" medium

第二部（沿用世界观）

Second installment (reuse worldview)

/worldbuilder 玄幻 "系统+升级" 跳过选题、大纲阶段恢复上次创作标题"武帝降临2"

undefined

/worldbuilder Xuanhuan "System+Level-up" skip-topic, skip-outline stages resume-last-session title"The Martial Emperor Arrives 2"

undefined

场景4：A/B测试优化

Scenario 4: A/B Testing Optimization

undefined

undefined

测试不同开篇风格

Test different opening styles

/worldbuilder 都市 "重生+商战" 跳过写作、审查、润色、完稿阶段

/worldbuilder Urban "Rebirth+Business War" skip-writing, skip-review, skip-polish, skip-finalize stages

手动修改大纲中的开篇设定后继续

Manually modify opening settings in the outline, then continue

/worldbuilder 都市 "重生+商战" 跳过选题阶段恢复上次创作

undefined

/worldbuilder Urban "Rebirth+Business War" skip-topic-stage resume-last-session

undefined

场景5：批量生成素材库

Scenario 5: Batch Generate Material Library

undefined

undefined

生成多个选题方案用于后续选择

Generate multiple topic options for later selection

/worldbuilder 玄幻 "废柴" 跳过大纲、写作、审查、润色、完稿阶段 /worldbuilder 玄幻 "系统" 跳过大纲、写作、审查、润色、完稿阶段 /worldbuilder 玄幻 "重生" 跳过大纲、写作、审查、润色、完稿阶段

undefined

/worldbuilder Xuanhuan "Underdog" skip-outline, skip-writing, skip-review, skip-polish, skip-finalize stages /worldbuilder Xuanhuan "System" skip-outline, skip-writing, skip-review, skip-polish, skip-finalize stages /worldbuilder Xuanhuan "Rebirth" skip-outline, skip-writing, skip-review, skip-polish, skip-finalize stages

undefined

数据持久化规范

Data Persistence Specification

所有中间状态数据统一存储在当前工作目录的

.sumeru/

目录下，避免上下文压缩或清理导致数据丢失：

All intermediate state data is uniformly stored in the

.sumeru/

directory of the current working directory to avoid data loss caused by context compression or cleanup:

全局存储结构

Global Storage Structure

.sumeru/
├── session/          # 会话全局数据
│   ├── config.json   # 创作配置参数
│   ├── status.json   # 当前进度状态
│   └── history.log   # 操作历史记录
├── topic/            # 选题阶段输出
│   ├── report.md     # 完整选题策划报告
│   └── options.json  # 多选题方案原始数据
├── outline/          # 大纲阶段输出
│   ├── world.md      # 世界观设定
│   ├── characters.json # 人物设定卡
│   ├── plot.md       # 剧情大纲
│   ├── plot-outline.json # 剧情大纲结构化数据
│   └── chapter-outlines.json # **完整章节细纲（核心输出）**
├── write/            # 创作阶段输出
│   ├── draft/        # 章节草稿
│   ├── original/     # 原始章节备份（review/polish修改前自动备份）
│   └── progress.json # 创作进度跟踪
├── review/           # 审查阶段输出
│   ├── timeline.json # 时间线数据
│   ├── issues.json   # 问题清单
│   ├── fix-plan.json # 重写修复计划
│   └── plot-map.json # 剧情脉络图
├── polish/           # 润色阶段输出
│   └── diff.json     # 修改对比记录
└── finalize/         # 完稿阶段输出
    ├── clean/        # 纯净版全文
    ├── platforms/    # 各平台导出版本
    └── report.md     # 完稿校验报告

.sumeru/
├── session/          # Global session data
│   ├── config.json   # Creation configuration parameters
│   ├── status.json   # Current progress status
│   └── history.log   # Operation history record
├── topic/            # Topic stage output
│   ├── report.md     # Complete topic planning report
│   └── options.json  # Raw data of multiple topic options
├── outline/          # Outline stage output
│   ├── world.md      # Worldview settings
│   ├── characters.json # Character setting cards
│   ├── plot.md       # Plot outline
│   ├── plot-outline.json # Structured plot outline data
│   └── chapter-outlines.json # **Complete detailed chapter outlines (core output)**
├── write/            # Creation stage output
│   ├── draft/        # Chapter drafts
│   ├── original/     # Original chapter backups (auto-backup before review/polish modification)
│   └── progress.json # Creation progress tracking
├── review/           # Review stage output
│   ├── timeline.json # Timeline data
│   ├── issues.json   # Issue list
│   ├── fix-plan.json # Rewrite repair plan
│   └── plot-map.json # Plot脉络图
├── polish/           # Polishing stage output
│   └── diff.json     # Modification comparison record
└── finalize/         # Finalization stage output
    ├── clean/        # Clean full text
    ├── platforms/    # Platform-specific export versions
    └── report.md     # Finalization check report

进度保存机制（WORKBUILDER_PROGRESS.json）

Progress Saving Mechanism (WORKBUILDER_PROGRESS.json)

json

{
  "session_id": "session-20240315-abc123",
  "created_at": "2024-03-15T10:00:00",
  "updated_at": "2024-03-15T14:30:00",
  "current_stage": "review",
  "stages": {
    "topic": {
      "status": "completed",
      "completed_at": "2024-03-15T10:15:00",
      "output_files": [
        "选题策划报告.md",
        ".sumeru/topic/options.json"
      ]
    },
    "outline": {
      "status": "completed", 
      "completed_at": "2024-03-15T11:20:00",
      "output_files": [
        "小说大纲_玄幻系统流.md",
        ".sumeru/outline/chapter-outlines.json"
      ]
    },
    "write": {
      "status": "completed",
      "completed_at": "2024-03-15T13:45:00",
      "output_files": [
        "chapters/001-废物觉醒系统.md",
        "chapters/002-系统签到奖励.md",
        ".sumeru/write/progress.json"
      ],
      "statistics": {
        "total_chapters": 100,
        "completed_chapters": 100,
        "total_words": 520000
      }
    },
    "review": {
      "status": "completed",
      "completed_at": "2024-03-15T14:45:00",
      "output_files": [
        "剧情审查报告.md",
        ".sumeru/review/issues.json",
        ".sumeru/review/fix-plan.json"
      ],
      "statistics": {
        "total_issues_found": 8,
        "critical_issues": 2,
        "issues_fixed": 6,
        "issues_rewritten": 2
      },
      "fix_plan_generated": true
    },
    "polish": {
      "status": "in_progress",
      "started_at": "2024-03-15T15:00:00",
      "progress": "60%",
      "polish_level": "moderate",
      "style": "小白爽文"
    },
    "finalize": {
      "status": "pending"
    }
  }
}

json

{
  "session_id": "session-20240315-abc123",
  "created_at": "2024-03-15T10:00:00",
  "updated_at": "2024-03-15T14:30:00",
  "current_stage": "review",
  "stages": {
    "topic": {
      "status": "completed",
      "completed_at": "2024-03-15T10:15:00",
      "output_files": [
        "Topic Planning Report.md",
        ".sumeru/topic/options.json"
      ]
    },
    "outline": {
      "status": "completed", 
      "completed_at": "2024-03-15T11:20:00",
      "output_files": [
        "Novel Outline_Xuanhuan System Flow.md",
        ".sumeru/outline/chapter-outlines.json"
      ]
    },
    "write": {
      "status": "completed",
      "completed_at": "2024-03-15T13:45:00",
      "output_files": [
        "chapters/001-Underdog Awakens System.md",
        "chapters/002-System Sign-in Reward.md",
        ".sumeru/write/progress.json"
      ],
      "statistics": {
        "total_chapters": 100,
        "completed_chapters": 100,
        "total_words": 520000
      }
    },
    "review": {
      "status": "completed",
      "completed_at": "2024-03-15T14:45:00",
      "output_files": [
        "Plot Review Report.md",
        ".sumeru/review/issues.json",
        ".sumeru/review/fix-plan.json"
      ],
      "statistics": {
        "total_issues_found": 8,
        "critical_issues": 2,
        "issues_fixed": 6,
        "issues_rewritten": 2
      },
      "fix_plan_generated": true
    },
    "polish": {
      "status": "in_progress",
      "started_at": "2024-03-15T15:00:00",
      "progress": "60%",
      "polish_level": "moderate",
      "style": "Light爽文"
    },
    "finalize": {
      "status": "pending"
    }
  }
}

数据生命周期管理

Data Lifecycle Management

自动保存：每完成一个阶段自动将数据写入对应目录，支持幂等写入
进度追踪：每个阶段完成后自动更新
```
WORKBUILDER_PROGRESS.json
```
，记录阶段状态与完成时间
版本控制：关键节点自动生成版本快照，命名格式
```
{stage}-{timestamp}.json
```
断点恢复：恢复创作时自动从
```
.sumeru/
```
目录读取对应阶段数据
清理规则：支持清理所有中间数据，默认保留最近3个版本
数据复用：可直接引用其他项目的
```
.sumeru/
```
目录数据，实现世界观/人设复用

Auto-Save: Automatically write data to the corresponding directory after completing each stage, supporting idempotent writing
Progress Tracking: Automatically update
```
WORKBUILDER_PROGRESS.json
```
after each stage is completed, recording stage status and completion time
Version Control: Automatically generate version snapshots at key nodes, named in the format
```
{stage}-{timestamp}.json
```
Breakpoint Resume: Automatically read corresponding stage data from the
```
.sumeru/
```
directory when resuming creation
Cleanup Rules: Support cleaning all intermediate data, default to keep the latest 3 versions
Data Reuse: Directly reference
```
.sumeru/
```
directory data from other projects to achieve worldview/character setting reuse

高级配置：自定义阶段钩子

Advanced Configuration: Custom Stage Hooks

通过配置文件

{output-dir}/hooks.json

可以在各阶段前后插入自定义处理：

json

{
  "before_topic": "my-preprocess-script.sh",
  "after_outline": "validate-outline.js",
  "before_write": "setup-write-env.py",
  "after_final": "deploy-to-platform.sh"
}

Custom processing can be inserted before and after each stage through the configuration file

{output-dir}/hooks.json

json

{
  "before_topic": "my-preprocess-script.sh",
  "after_outline": "validate-outline.js",
  "before_write": "setup-write-env.py",
  "after_final": "deploy-to-platform.sh"
}