sumeru-review

Web Novel Logic Review

Trigger Keywords

Core Features

Three-Stage Review and Repair Process Design

• Load complete outline and chapter detailed outlines to establish a global review benchmark
• Analyze the overall plot context and timeline structure
• Review consistency of global settings (worldview, power system, rule settings)
• Identify issues with main and subplot correlations and foreshadowing resolution status
• Review overall conflict distribution and rhythm control
• Record global issue list to

  .sumeru/review/global-issues.json

• Use multiple Agents for parallel processing, with each Agent responsible for a certain number of chapters
• ⚠️ Follow global constraint: each sub-Agent is responsible for a maximum of 3 chapters (see AGENTS.md "Sub-Agent Parallel Processing Rules")
• Required number of Agents = ceil(total chapters / 3), allocation strategy is sequential continuous assignment by chapter order
• Generate a core plot summary for each chapter (remove details, retain only key events)
• Conduct detailed review for each chapter:
  • Word count statistics and filling demand identification
  • Timeline and event sequence verification
  • Consistency of character behavior and personality (OOC detection)
  • Item status and information boundary check
  • Scene description and dialogue quality evaluation
  • Foreshadowing setting and resolution status
• Generate chapter summaries to

  .sumeru/review/summaries/

  directory
• Record chapter issue list to

  .sumeru/review/chapter-issues/

  directory
• Support resumable review, skip already reviewed chapters

• Merge global issues and chapter issues, sort by severity (Fatal > Severe > Medium > Minor)
• Develop and execute repair plan, divided into two repair types:
  • Lightweight Repair (executed directly by review): minor modifications such as text correction, paragraph adjustment, sentence optimization, word count filling, directly modify files in chapters/ directory (automatically back up original files to

    .sumeru/write/original/

    before modification)
  • Rewrite Repair (marked as pending): chapters with severe plot logic contradictions, large-scale OOC, setting collapse that require rewriting are recorded in the repair plan
• Execute lightweight repair strategy:
  • Global issue repair: adjust overall timeline, unify settings, optimize main plot structure
  • Chapter issue repair: fix lightweight issues such as word count, logic, OOC, plot contradictions chapter by chapter
  • Linked repair: handle cross-chapter related issues (such as foreshadowing resolution, character growth)
• Generate repair report to

  .sumeru/review/fix-report.json

• Generate repair plan

  fix-plan.json

  , mark chapters that need rewriting and specific repair suggestions
• Conduct re-review after repair to verify that all lightweight repair issues are completely resolved

Three-Stage Function Allocation

1. Overall plot context analysis: review the overall distribution of main plot, subplots, and foreshadowings
2. Global timeline verification: sort out the complete timeline, identify large-span sequence issues
3. Setting consistency check: verify the unity of worldview, power system, and rule settings
4. Conflict distribution evaluation: evaluate conflict intensity, distribution density, and rhythm control
5. Foreshadowing resolution status check: identify all unresolved foreshadowings and resolution direction suggestions

• ⚠️ Follow global constraint: each sub-Agent is responsible for a maximum of 3 chapters for review (see AGENTS.md)

fix-plan.json

• ⚠️ Follow global constraint: each Agent is responsible for a maximum of 3 chapters during lightweight repair phase (see AGENTS.md)

Repair Mechanism Description

• Lightweight Repair: directly modify problematic paragraphs or sentences in chapters/ directory, automatically back up original files to

  .sumeru/write/original/

  before modification
• Rewrite Repair: for severely problematic chapters, record to

  fix-plan.json

  , suggest using

  sumeru-write

  to regenerate
• Automatic Backup: automatically back up the original version to

  .sumeru/write/original/

  before modifying files in chapters/ directory to ensure rollback capability
• Repair Records: all repair operations are recorded in

  issues-fixed.json

  , including before-and-after repair comparisons

Output Content

• Overall Plot Context Analysis Report: overall distribution map of main plot, subplots, and foreshadowings
• Complete Story Timeline Map: sequence of key events organized by timeline
• Setting Consistency Check Report: unity analysis of worldview, power system, and rule settings
• Conflict Distribution Evaluation: evaluation of conflict intensity, distribution density, and rhythm control
• Global Foreshadowing Resolution Status Table: list of all unresolved foreshadowings and resolution direction suggestions

• Chapter Summary Directory: core plot summary for each chapter (

  .sumeru/review/summaries/

  )
• Word Count Check Report: word count statistics for each chapter, list of chapters that do not meet standards, filling improvement records
• Chapter Timeline and Event Sequence Report: results of time logic check within each chapter
• OOC Detection Report: abnormal character behavior points, personality deviation analysis
• Item Status Tracking Table: status changes of important items (obtained, used, lost)
• Chapter Foreshadowing Setting Record Table: foreshadowing settings and expected resolution positions in each chapter
• Plot Coherence Score: multi-dimensional comprehensive score (timeline, logic, character consistency, etc.)

• Issue Repair Report: repair status records of all issues, before-and-after repair comparisons
• Global Issue Repair Record: adjustment records of overall plot, timeline, and settings
• Chapter Issue Repair Record: detailed repair records chapter by chapter
• Linked Repair Description: solutions for cross-chapter related issues
• Repair Verification Report: verification results of re-review after repair
• Optimization Suggestions: plot adjustment plans, foreshadowing resolution suggestions, conflict optimization suggestions

Data Persistence

• 剧情审查报告.md

  : complete review result report, including all issues, severity levels, and repair suggestions (directly readable)

• 字数检查与填充报告.md

  : word count statistics, filling improvement records

• 全局审查报告.md

  : global analysis results of Phase 1

• 章节细节审查报告.md

  : chapter analysis results of Phase 2

• 统一修复报告.md

  : repair records of Phase 3

.sumeru/review/

• global-issues.json

  : global issue list, including timeline, setting, foreshadowing, and other issues

• timeline.json

  : complete timeline map, sequence of key events arranged by timeline

• plot-map.json

  : plot context map, showing distribution of main plot, subplots, and conflict points

• foreshadowing-tracking.json

  : foreshadowing tracking table, including position, content, and resolution status of all foreshadowings

• coherence-score.json

  : plot coherence score details

• summaries/

  : chapter summary directory

  • 001.json

    ,

    002.json

    ... core plot summary for each chapter (chapter number padded with three zeros)

  • summary-progress.json

    : summary generation progress record

• chapter-issues/

  : chapter issue list

  • 001.json

    ,

    002.json

    ... detailed issue records for each chapter (chapter number padded with three zeros)

• word-count.json

  : word count data, including word count per chapter, target word count, and filling status

• issues.json

  : merged complete issue list, classified by severity and type

• fix-report.json

  : issue repair report, including before-and-after repair comparisons

• fix-plan.json

  : rewrite repair plan, mark chapters that need rewriting and specific repair suggestions

• issues-fixed.json

  : resolved issue records

• global-fix.log

  : global issue repair log

• chapter-fix.log

  : chapter issue repair log

Cooperation with Other Skills

• Predecessor Skills: Read outline data from

  sumeru-outline

  and chapter data from

  sumeru-write

  • Use worldview, character settings, and outline from

    .sumeru/outline/

    as benchmarks
  • Use

    .sumeru/outline/chapter-outlines.json

    as expected plot reference
  • Use chapter content in chapters/ directory for review
  • Compare actual chapter content with detailed outlines to identify plot deviations
• Repair Plan Output: Generate

  fix-plan.json

  after repair completion, which marks chapters that need rewriting and specific repair suggestions
  • worldbuilder reads this file when orchestrating processes to decide whether to call

    sumeru-write

    for rewriting
  • When used independently, users can view

    fix-plan.json

    and manually call

    sumeru-write

    to rewrite specified chapters
• Successor Skills:
  • sumeru-write: Read

    fix-plan.json

    to execute rewrite repair (orchestrated by worldbuilder or manually called by users)
  • sumeru-polish: Receive repaired chapter content for stylistic polishing
  • sumeru-finalize: Receive repaired chapter content for final draft verification and multi-platform export

Three-Stage Data Flow

sumeru-write chapters
    ↓
Phase 1: Global Review (global-issues.json)
    ↓
Phase 2: Chapter Detail Review (chapter-issues/ + summaries/)
    ↓
Merge Issue List (issues.json)
    ↓
Phase 3: Unified Repair
    ├─ Lightweight Repair → Directly modify chapters/ (auto-backup to .sumeru/write/original/)
    └─ Rewrite Repair → Generate fix-plan.json
    ↓
Used by polish and finalize

Data Reuse

• Directly read issue list to locate chapters that need adjustment during rework
• Support incremental review, only detect new content based on existing review results when adding new chapters
• Can be called again after repair to automatically verify if issues are resolved
• Word count filling records can be used as word count reference for subsequent chapters