• Must run inside a project containing

  .webnovel/state.json

  .
• If missing, ask for the project path and

  cd

  into it.

• L0: No references before scope/volume is confirmed.
• L1: Minimum set for current generation step.
• L2: Conditional references only if constraints/genre details are needed.

• Before Step 3 (volume skeleton):

  • references/strand-weave-pattern.md

  • .claude/references/genre-profiles.md

• Before Step 3, load only if the cool point structure needs refinement:

  • references/cool-points-guide.md

• Before Step 4, load only if hook/rhythm subdivision is needed:

  • .claude/references/reading-power-taxonomy.md

• Before Step 3/4, load only if the genre is esports/live stream fiction/Cthulhu:

  • references/outlining/genre-volume-pacing.md

1. Load project data.
2. Select volume and confirm scope.
3. Generate volume skeleton.
4. Generate chapter outlines in batches.
5. Validate + save + update state.

cat "$PROJECT_ROOT/.webnovel/state.json"
cat "$PROJECT_ROOT/大纲/总纲.md"

• 设定集/主角组.md

• 设定集/女主卡.md

• 设定集/反派设计.md

• .webnovel/idea_bank.json

  (inherit constraints)

• Offer choices from the master outline (volume name + chapter range).
• Confirm any special requirements (tone, POV emphasis, romance, etc.). If the master outline is missing volume names/chapter ranges/core conflicts/volume-ending climaxes, first ask the user to supplement and update the master outline before proceeding.

cat ".claude/references/genre-profiles.md"

• Strand ratio (Quest/Fire/Constellation)
• Cool point density standards (minimum/recommended per chapter)
• Preferred hook types

• Quest Strand (Mainline Progression): 55-65% of chapters
  • Clear goals, visible progress, phased achievements
  • Examples: Breaking through realms, completing tasks, obtaining treasures
• Fire Strand (Emotion/Relationships): 20-30% of chapters
  • Changes in character relationships, emotional conflicts, team dynamics
  • Examples: Interactions with the female lead, mentor-apprentice conflicts, brotherly betrayal
• Constellation Strand (World/Mystery): 10-20% of chapters
  • Worldview reveals, foreshadowing, mystery progression
  • Examples: Discovering ancient secrets, revealing villainous conspiracies, world truths

• Switch dominant Strand every 3-5 chapters
• Climax chapters can interweave multiple Strands
• Concentrate Quest Strand in the last 3-5 chapters of the volume

cat "${CLAUDE_PLUGIN_ROOT}/skills/webnovel-plan/references/outlining/genre-volume-pacing.md"

• Regular chapters: 1-2 small cool points (intensity 2-3)
• Key chapters: 2-3 cool points, at least 1 medium cool point (intensity 4-5)
• Climax chapters: 3-4 cool points, at least 1 major cool point (intensity 6-7)

• At least 1 key chapter every 5-8 chapters
• At least 1 climax chapter per volume (usually at the end of the volume)

cat ".webnovel/idea_bank.json"

• Anti-cliché rules: Trigger once every N chapters
  • N = max(5, total chapters / 10)
  • Example: 50-chapter volume → trigger every 5 chapters
  • Example: 100-chapter volume → trigger every 10 chapters
• Hard constraints: Applied throughout the entire volume, reflected in chapter goals/cool point design
• Protagonist flaws: Become a source of conflict at least 2 times per volume
• Villain mirroring: Must reflect mirror comparison in chapters where villains appear

undefined

Chapter Range: Chapters {start} - {end} Core Conflict: {conflict} Volume-Ending Climax: {climax}

• Main Characters Introduced:
• Villain Hierarchy:

• Anti-cliché Rules: Trigger once every N chapters
• Hard Constraints: Applied throughout the volume

undefined

• ≤20 chapters: 1 batch
• 21–40 chapters: 2 batches
• 41–60 chapters: 3 batches

• 60 chapters: 4+ batches

• Quest: Mainline task progression, goal achievement, ability improvement
• Fire: Character relationships, emotional conflicts, team dynamics
• Constellation: Worldview reveals, foreshadowing, mystery progression

• Quest Strand → Achievement cool points (humiliation reversal, underdog rise, breakthrough)
• Fire Strand → Emotional cool points (recognition, protection, confession)
• Constellation Strand → Cognitive cool points (truth, prophecy, identity revelation)

• Suspense hook: Raise questions, create crises
• Promise hook: Tease rewards, hint at twists
• Emotional hook: Relationship changes, character crises

• None: Daily chapters, cultivation chapters, relationship chapters
• Minor: Small conflicts, minor villains, local confrontations
• Medium: Medium villains appear, important conflicts, phased confrontations
• Major: Major villains appear, core conflicts, volume-level climaxes

• New characters: Name + one-sentence positioning
• New locations: Name + one-sentence description
• New items: Name + function
• New forces: Name + stance

• Is the anti-cliché rule triggered?
• Are hard constraints reflected?
• Are protagonist flaws demonstrated?
• Is villain mirroring reflected?

undefined

• Goal: {≤20 characters}
• Cool Point: {Type} - {≤30 characters}
• Strand: {Quest|Fire|Constellation}
• Villain Hierarchy: {None/Minor/Medium/Major}
• POV/Protagonist: {Protagonist A/Protagonist B/Female Lead/Ensemble}
• Key Entities: {New or important appearances}
• Hook: {Type} - {≤30 characters}

**Field Explanations**:
- **Hook**: The end-of-chapter hook to be planned for this chapter
  - Example: Suspense Hook - The identity of the mysterious person is about to be revealed
  - Meaning: This chapter's ending should include this suspense hook
  - The next chapter's context-agent will read chapter_meta[N].hook (the actual implemented hook) to generate "pick up from previous chapter" guidance
  - Hook type references: Suspense Hook | Crisis Hook | Promise Hook | Emotional Hook | Choice Hook | Desire Hook

Save after each batch:
```bash
@'
{batch_content}
'@ | Add-Content -Encoding UTF8 "$PROJECT_ROOT/大纲/第{volume_id}卷-详细大纲.md"

• Each chapter has ≥1 small cool point (intensity 2-3)
• At least 1 key chapter every 5-8 chapters (intensity 4-5)
• At least 1 climax chapter per volume (intensity 6-7)

• Quest: Should account for 55-65%
• Fire: Should account for 20-30%
• Constellation: Should account for 10-20%

• Does the volume's core conflict run through the chapters?
• Is the volume-ending climax reflected in the last 3-5 chapters?
• Do key characters appear as planned?

• Number of anti-cliché rule triggers ≥ total chapters / N (N = max(5, total chapters/10))
• Hard constraints are reflected in at least 50% of chapters
• Protagonist flaws become a source of conflict at least 2 times
• Villain mirroring is reflected in chapters where villains appear

• Goal (≤20 characters)
• Cool Point (type + ≤30 character description)
• Strand (Quest/Fire/Constellation)
• Villain Hierarchy (None/Minor/Medium/Major)
• POV/Protagonist
• Key Entities (at least 1)
• Hook (type + ≤30 character description)

python "${CLAUDE_PLUGIN_ROOT}/scripts/update_state.py" \
  --project-root "$PROJECT_ROOT" \
  --volume-planned {volume_id} \
  --chapters-range "{start}-{end}"

• Chapter outline file has been written:

  大纲/第{volume_id}卷-详细大纲.md

• Each chapter includes: Goal/Cool Point/Strand/Villain Hierarchy/POV/Key Entities/Hook
• Consistent with master outline conflict/climax, reasonable constraint trigger frequency (if idea_bank is enabled)

• Chapter outline file does not exist or is empty
• Any chapter is missing: Goal/Cool Point/Strand/Villain Hierarchy/POV/Key Entities/Hook
• Obvious conflict with master outline core conflict or volume-ending climax
• Insufficient constraint trigger frequency (when idea_bank is enabled)

1. Stop and list the failing items.
2. Re-generate only the failed batch (do not overwrite the whole file).
3. If the last batch is invalid, remove that batch and rewrite it.
4. Only update state after Final check passes.

• Continue planning next volume → /webnovel-plan
• Start writing → /webnovel-write