sumeru-review

Web Fiction Logic Review

Trigger Keywords

Help me check if the novel has any bugs, see if there are contradictions in the timeline, are there any OOC characters, find plot conflicts before and after, sort out whether foreshadowing has been recovered, check the plot rationality of the novel, see if there are any plot holes, character behavior does not match personality, check whether the timeline is correct, find contradictory places before and after in the novel, help me sort out all foreshadowing, novel plot bug check, logic hole investigation, novel plot review, the outline has problems and needs revision, how to fix plot contradictions, discover repeated plot points, what to do if the setting collapses, bottom-line issue check

Core Functions

Three-Stage Review and Repair Process Design

To ensure review comprehensiveness and repair quality, this skill adopts a three-stage review and repair process:

Stage One: Global Information Review

Load the complete outline and chapter detailed outlines, and establish a global review baseline
Analyze the overall plot thread and timeline structure
Review global setting consistency (worldview, power system, rule settings)
Identify issues in the connection between the main plot and subplots and the status of foreshadowing recovery
Check the distribution of overall conflict points and pacing control
Bottom-Line Issue Scan: comprehensively scan the following six categories of bottom-line issues and generate bottom-line-checklist.json：
- Timeline contradictions (incorrect event order, age/date conflicts)
- Setting collapse (inconsistent power system before and after, self-contradictory worldview rules)
- Character OOC (sudden personality changes without setup, contradiction between behavior and motivation)
- Repeated plot points (similar events repeat without differences, identical tropes)
- Information leakage (characters know information they should not know, chaotic information boundaries)
- Foreshadowing deadlock (planted foreshadowing has no possibility of recovery, foreshadowing is self-contradictory)
RecordGlobal issue listto .sumeru/review/global-issues.json

Stage Two: Chapter Detail Review (Agent Team in Parallel)

Use multiple Agents for parallel processing, with each Agent responsible for a certain number of chapters
⚠️ Follow the global constraint: each sub-Agent is responsible for at most 3 chapters(see AGENTS.md "Sub-Agent Parallel Processing Rules" for details)
Required number of Agents = ceil(total number of chapters / 3), and the allocation strategy is continuous allocation in chapter order
Generate a core plot summary for each chapter (remove details, keep only key events)
Conduct a detailed review of each chapter:
- Word count statistics and padding requirement identification
- Timeline and event sequence verification
- Character behavior and personality consistency (OOC detection)
- Item status and information boundary check
- Scene description and dialogue quality assessment
- Foreshadowing setup and recovery status
GenerateChapter summariesto .sumeru/review/summaries/ directory
RecordChapter issue listto .sumeru/review/chapter-issues/ Table of Contents
Supports resumable transfer; reviewed chapters can be skipped

Phase 3: Unified Fix Execution

Merge global issues and chapter issues, sort by severity (Fatal > Severe > Moderate > Minor)
Develop and execute afix plan, divided into three fix types:
- Lightweight fixes(executed directly by review): minor changes such as text corrections, paragraph adjustments, sentence optimization, word count filling, etc.,directly modify the chapters/ file(automatically backed up before modification to .sumeru/write/original/）
- Closed-loop fixes for severe issues(review automatically executes outline revision + chapter rewriting): chapters that need to be rewritten due to severe plot logic contradictions, large-scale OOC, setting collapse, repeated plot, etc.,automatically revise the outline and rewrite the chapters
- Special fixes for bottom-line issues: all six categories of bottom-line issues must be resolved, and skipping or shelving is not allowed
Execute the lightweight fix strategy:
- Global issue fixes: adjust the overall timeline, unify settings, optimize the main storyline structure
- Chapter issue fixes: fix lightweight issues chapter by chapter, such as word count, logic, OOC, plot contradictions, etc.
- Linked fixes: handle cross-chapter related issues (such as foreshadowing payoff, character growth)
Execute closed-loop fixes for severe issues：
- Outline revision: directly revise .sumeru/outline/chapter-outlines.json the detailed outline of the affected chapters in .sumeru/review/outline-revisions.json(including revision reasons, before-and-after comparison)
- Chapter rewriting: based on the revised detailed outline, use sub-agents to rewrite the corresponding chapters in parallel (following the 3 chapters/agent constraint); the rewriting results directly modify the chapters/ file (automatically backed up before modification to .sumeru/write/original/）
- Revision consistency verification: the rewritten chapters need to be checked for consistency with the revised outline to ensure that the outline revision intent is correctly implemented
Execute zero-omission verification of bottom-line issues：
- Check one by one bottom-line-checklist.json each bottom-line issue in
- Those that can be resolved by lightweight fixes are marked as "Resolved - Lightweight Fix"
- Those that can be resolved by outline revision + rewriting are marked as "Resolved - Rewrite Fix"
- Those that cannot be automatically resolved are marked as "Needs Manual Intervention", and clearmanual intervention suggestions(including problem description, impact scope, suggested modification direction) are output
- Only after all bottom-line issues are marked as "Resolved" or "Needs Manual Intervention" is the review process allowed to end
Generatefix reportto .sumeru/review/fix-report.json
Generatefix plan fix-plan.json, recording detailed information of all fix operations
Re-review after fixes to verify that all lightweight fix and rewrite fix issues have been thoroughly resolved

Three-Phase Function Allocation

Phase 1: Global Review Function

Overall plot thread analysis: review the overall distribution of the main storyline, subplots, and foreshadowing
Global timeline verification: Sort out the complete timeline and identify large-span temporal issues
Setting consistency check: Verify the unity of the worldview, power system, and rule settings
Conflict point distribution assessment: Assess conflict intensity, distribution density, and pacing control
Foreshadowing recovery status check: Identify all unrecovered foreshadowing and recovery directions

Phase 2: Chapter detail review function 6. Word count check and padding: Ensure each chapter meets the word count requirement, and automatically pad when the word count is insufficient 7. Chapter timeline and event sequence: Check the internal temporal logic and event order of each chapter 8. OOC detection and character consistency: Check the consistency of character behavior, personality, and dialogue 9. Item status and information boundaries: Track item status changes and character information boundaries 10. Scene description and dialogue quality: Assess scene details and the naturalness of dialogue 11. Chapter foreshadowing setup: Record each chapter's foreshadowing setup and expected recovery location

⚠️ Follow the global constraint: each sub-Agent is responsible for reviewing at most 3 chapters(see AGENTS.md for details)

Phase 3: Unified repair function 12. Unified issue repair: Merge all issues, sort by severity, and formulate a repair plan 13. Lightweight repair execution: Direct modifications such as text corrections, paragraph adjustments, sentence optimization, and word count padding chapters/ file 14. Outline revision: For chapters with serious problems, directly revise .sumeru/outline/chapter-outlines.json corresponding detailed outline 15. Chapter rewrite: Based on the revised detailed outline, use sub-Agents to rewrite the corresponding chapters in parallel (following the 3 chapters/Agent constraint), directly modifying chapters/ file 16. Zero-omission verification of bottom-line issues: Check the six categories of bottom-line issues one by one, and only allow completion after all are marked as "resolved" or "requires manual intervention" 17. Global issue repair: Adjust large-scale issues such as the overall plot, timeline, and settings 18. Chapter issue repair: Repair lightweight detail issues chapter by chapter, such as word count, logic, characters, and scenes 19. Linked repair: Handle cross-chapter related issues to ensure overall consistency after repair 20. Repair verification: Re-review after repair to ensure all issues from lightweight repair and rewrite repair have been thoroughly resolved

⚠️ The lightweight repair phase follows the global constraint: each Agent is responsible for at most 3 chapters(see AGENTS.md for details)

Repair mechanism description

Lightweight repair: Directly modify chapters/ problematic paragraphs or sentences in, and automatically back up the original file before modification to .sumeru/write/original/
Closed-loop repair of serious issues: For chapters with serious problems (plot contradictions, setting collapse, repeated plots, etc.), automatically revise .sumeru/outline/chapter-outlines.json corresponding detailed outline, then based on the revised detailed outline use sub-Agents to rewrite the chapters in parallel, directly modifying chapters/(automatically back up before modification to .sumeru/write/original/), and save the revision record to .sumeru/review/outline-revisions.json
Zero omission of bottom-line issues: The six categories of bottom-line issues (timeline contradictions, setting collapse, character OOC, repeated plot, information leaks, dead-end foreshadowing) must all be resolved or marked "requires manual intervention"; skipping or shelving them is not allowed
Automatic backup: before modifying the chapters/ file, automatically back up the original version to .sumeru/write/original/, ensuring rollback is possible
Repair record: all repair operations are recorded in issues-fixed.json , including before-and-after comparisons of repairs

Output content

Phase 1: Global review output

Global plot thread analysis report: overall distribution map of the main plot, subplots, and foreshadowing
Complete story timeline map: sequence of key events organized along the timeline
Setting consistency check report: consistency analysis of the worldview, power system, and rule settings
Conflict point distribution assessment: assessment of conflict intensity, distribution density, and pacing control
Global foreshadowing recovery status table: list of all unrecovered foreshadowing and suggested recovery directions
Bottom-line issue list: complete scan results for the six categories of bottom-line issues (bottom-line-checklist.json）

Phase 2: Chapter detail review output

Chapter summary catalog: 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 the standard, and padding improvement records
Chapter timeline and event sequence report: results of the internal temporal logic check for each chapter
OOC detection report: analysis of abnormal character behavior points and personality deviations
Item status tracking table: status changes of important items regarding acquisition, use, and loss
Chapter foreshadowing setup record table: foreshadowing setup and expected recovery position for each chapter
Plot coherence score: multi-dimensional comprehensive score (timeline, logic, character consistency, etc.)

Phase 3: Unified repair output

Issue repair report: record of repair status for all issues and before-and-after comparisons of repairs
Outline revision report: outline revision content, reasons for revision, and before-and-after comparison of revisions (outline-revisions.json）
Global issue repair record: adjustment records for the overall plot, timeline, and settings
Chapter issue repair record: detailed record of repairs chapter by chapter
Linked repair explanation: handling plan for cross-chapter related issues
Bottom-line issue verification report: resolution status of the six categories of bottom-line issues, with a list of "resolved" / "requires manual intervention"
Repair verification report: verification results of the re-review after repair
Optimization suggestions: plot adjustment plans, foreshadowing recovery suggestions, and conflict optimization suggestions

Data persistence

User-visible output (current working directory)：

剧情审查报告.md: complete review results report, including all issues, severity levels, and repair suggestions (directly readable)
字数检查与填充报告.md: word count statistics and padding improvement records
全局审查报告.md: Phase 1 global analysis results
章节细节审查报告.md: Phase 2 chapter analysis results
统一修复报告.md: Phase 3 repair records, including outline revisions, chapter rewrites, and baseline issue verification results

Intermediate data (for internal system use only, stored in.sumeru/review/directory)： Phase 1: Global review data

global-issues.json: Global issue list, including timeline, setting, foreshadowing, and other issues
timeline.json: Complete timeline map, the sequence of key events arranged along the timeline
plot-map.json: Plot thread map, showing the distribution of main plotlines, subplots, and conflict points
foreshadowing-tracking.json: Foreshadowing tracking table, including the position, content, and recovery status of all foreshadowing
coherence-score.json: Detailed plot coherence scoring
bottom-line-checklist.json：Baseline issue list, including scan results for six categories of baseline issues and status tracking (to be fixed/resolved/manual intervention required)

Phase 2: Chapter detail review data

summaries/: Chapter summary table of contents
- 001.json、002.json... Core plot summary for each chapter (chapter number zero-padded to three digits)
- summary-progress.json: Summary generation progress record
chapter-issues/: Chapter issue list
- 001.json、002.json... Detailed issue records for each chapter (chapter number zero-padded to three digits)
word-count.json: Word count statistics, including each chapter's word count, target word count, and padding status

Phase 3: Unified repair data

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: Repair plan, recording detailed information for all repair operations
outline-revisions.json：Outline revision records, including revision reasons, before-and-after revision comparisons, and the list of affected chapters
issues-fixed.json: Records of fixed issues
global-fix.log: Global issue repair log
chapter-fix.log: Chapter issue repair log
rewrite-chapters/：Revision records for rewritten chapters, including before-and-after rewrite comparisons

Coordination with other Skills

Upstream Skill: Read sumeru-outline outline data and sumeru-write chapter data
- Use .sumeru/outline/ worldview, character settings, and outline as the baseline
- Use .sumeru/outline/chapter-outlines.json as expected plot reference
- Use chapters/ chapter content in the directory for review
- Compare the actual chapter content with the detailed outline to identify plot deviations
Outline revision capability: When review finds serious issues, directly revise .sumeru/outline/chapter-outlines.json detailed outline of the affected chapters
- Record revision content in .sumeru/review/outline-revisions.json, including revision reasons and before-and-after revision comparisons
- The revised outline is used for subsequent chapter rewrites and later processes
Chapter rewrite capability: Based on the revised detailed outline, review uses sub-agents to rewrite the corresponding chapters in parallel (following the 3 chapters/Agent constraint)
- Rewrite results directly modify chapters/ files (automatically backed up before modification to .sumeru/write/original/）
- Record before-and-after rewrite comparisons in .sumeru/review/rewrite-chapters/
Repair plan output: After repair is complete, generate fix-plan.json, recording detailed information for all repair operations
- worldbuilder reads this file when orchestrating the process to confirm the repair status during the review phase
- When used independently, users can view fix-plan.json to understand the complete repair record
Subsequent Skills：
- sumeru-polish: Receives the repaired chapter content (already includes the results of outline revision + rewrite repair), and performs writing polish
- sumeru-finalize: Receives the repaired chapter content, and performs final draft validation and multi-platform export

Three-Stage Data Flow

sumeru-write 章节
    ↓
第一阶段：全局审查（global-issues.json + bottom-line-checklist.json）
    ↓
第二阶段：章节细节审查（chapter-issues/ + summaries/）
    ↓
合并问题清单（issues.json）
    ↓
第三阶段：统一修复
    ├─ 轻量修复 → 直接修改 chapters/（自动备份到 .sumeru/write/original/）
    ├─ 严重问题 → 大纲修订（outline-revisions.json）→ 章节重写（自动备份）
    └─ 底线问题 → 零遗漏核验（bottom-line-checklist.json 全部「已解决」或「需人工干预」）
    ↓
供 polish 和 finalize 使用

Data Reuse

During rework and modification, directly read the issue list to locate the chapters that need adjustment
Supports incremental review; when new chapters are added, only detect new content based on existing review results
After repair is completed, automatic verification can be invoked again to check whether the issues are resolved
Word count padding records can be used as word count references for subsequent chapters