Ideation and Volume Outline Planning
Responsible for creative and volume-level planning above the single-chapter level in a web-novel project: converge vague ideas into book positioning, a first draft of external copy, the Golden Three Chapters (first three chapters, which determine reader retention), a whole-book outline and volume-level plan (chapter planning table, rhythm waveform, hook grades, daily update groupings with region cycle notes), and then hand the volume plan downstream for chapter writing or review.
When to Use / Not Use
When to use this skill:
- You have only fuzzy ideas and want to converge on genre positioning, core selling points, the protagonist's advantage (golden finger) with its costs and reader expectations.
- You need to draft or rewrite
publish/blurb.md(title, blurb, tags, tagline). - You need to design or restructure the opening Golden Three Chapters, validating "why the reader should keep reading."
- You need to draft or adjust the whole-book outline, volume intervals, overt/covert line rhythm, major reversals, and volume-level big hook chains.
- You need to start a new volume, reorder volumes, edit the
## Chapter Plantable inbible/volumes/{vol}.md, or allocate pop/emotion waves and S/A/B/C hooks according to daily/burst update schedules. - You need to design a stable "region cycle" structure for travel, multi-location, instance, or episodic detective-style volumes.
When to hand over to sibling skills (only hand over, never silently do their work):
- To set up the book skeleton, import existing drafts, or update the public freeze list (
frozen.rangesandlint.mjs --freeze): hand over tofiction-init. If not installed, deliver the produced discussion notes/template list, to-do steps (create directories or updatefrozen.rangesand runlint.mjs --freeze), and unchecked items. - To write single-chapter
outline.md, draft the main text, or do post-chapter updates based on the volume plan: hand over tofiction-chapter. If not installed, deliver that volume'sbible/volumes/{vol}.md(including free-form area with daily grouping and region three notes), a list of chapter outlines to write, and undone text/writeback checks. - To resolve canon conflicts, register new foreshadows/subplots, or do routine maintenance: hand over to
fiction-continuity. If not installed, deliver the list of foreshadows/subplots to register and conflict points, explicitly marking incomplete registration and consistency review for manual backfill by the author. - For automated checks, desensitization review, and editorial review of
publish/blurb.mdand the main text: hand over tofiction-review. If not installed, deliverpublish/blurb.md, a manual review checklist (corresponding tolint.desensitize.*,lint.banned_terms,lint.internal_terms), and note "Automated checks not run." - To submit title, blurb, and chapters to the publishing platform: hand over to
fiction-publish. If not installed, deliverpublish/blurb.mdand a reminder to verifybook.title, for the author to publish manually. - For scene writing, dialogue, atmosphere, or genre details: consult
fiction-craft(especiallyreferences/genres/<id>.md). If not installed, confirm genre conventions and reader expectations with the author. - To adapt the web novel into a vertical short drama: hand over to
fiction-short-drama. If not installed, deliver the finalizedbible/plot-outline.md,bible/volumes/{vol}.md, and a list of drama-side files to create (series.md,adaptation-map.md), noting that adaptation checks have not been run.
Before You Start
Before creating or modifying any machine-readable file, open the corresponding format reference file (references/formats/*.md) and follow its format strictly. Do not rely on memory.
Before planning, read the three categories of project files in order:
- Project
AGENTS.md(focus on## Book Scope): Confirm the protagonist's scope, perspective discipline, book-specific rules, and genre taboos. Project rules take precedence over this skill's defaults (SB §3). .fiction/config.json(fields and defaults in SB §8): Readbook.title,book.genres,rhythm.beat_every(default[3,5]),rhythm.external_event_max_gap(default2),daily.*(default regular2chapters/day, last chapter minimumA; burst3-5chapters/day, last chapter minimumS),hook.discouraged(default["C"]),frozen.ranges,foreshadow.*,subplot.*,lint.desensitize.*,lint.banned_terms,lint.internal_terms, andlint.extra_files.bible/sources.md(SB §5): Confirm the single main writing entry to avoid modifying derivative files by mistake.
Read the minimum required set by task (SB §4.1; do not full-scan bible/ out of fear of missing something):
- For discussing whole-book direction or reordering volumes:
bible/canon.md→bible/timeline.md→chapters/{vol}/vol-info.md→bible/volumes/{vol}.md→bible/plot-outline.md→bible/storylines.md→bible/subplots.md; readbible/foreshadows.mdif needed. - If
fiction-craftis installed andbook.genresis non-empty, first consult the corresponding genre packagereferences/genres/<id>.mdto align with pop preferences and minefields. - If the replanning touches chapters in
frozen.rangesthat are published publicly frozen (SB §7.1), the frozen chapter text is read-only; only adjust unfrozen chapters. For canon conflicts involving frozen chapters, hand over tofiction-continuity; if you need to extend the public freeze range, hand over tofiction-init.
Missing file handling: If the author is starting from scratch with no project files yet, suggest the author can run fiction-init to initialize the skeleton at any time; for now, plan using SB §8 defaults and note at the beginning of the output "Currently using default parameters."
Process
The author may go through the full process from Step 1, or jump directly to the current phase (e.g., starting a new volume or replanning, start directly from Step 5). Whenever core positioning, dual-line thresholds, volume reordering, or overwriting existing plans are involved, first present the proposal for the author to approve; only after confirmation should authoritative files be written.
Step 1: Creative Positioning and Selling Point Convergence
- Collect initial ideas (genre, protagonist's predicament, scenes the author wants to write, estimated length, and target platform). If
fiction-craftis installed and a genre is selected, first consult the corresponding genre package (references/genres/<id>.md) for selling point preferences and minefields. - Following references/ideation-and-blurb.md, produce
2-3premise variants. For each variant, clearly state: core selling point, protagonist's advantage/golden finger (the protagonist's unique problem-solving ability or information asymmetry, if required by the genre) along with its cost, limitations, and growth potential, target reader profile, and a one-line pitch. - Competitor comparison: Ask the author for
2-3reference works; only deconstruct their structure, tone, and selling point differences. Never fabricate sales, subscriptions, clicks, or chart data. - Perform the "Why Keep Reading" five-question validation, and draft a positioning overview (one-line positioning, atmosphere reference, dual-line structure, core character draft).
- Pause and ask the author to approve: After the premise variant and boundaries are selected, continue; leave undecided drafts in
bible/drafts/. According tofiction-continuity's conflict priority (SB §3), only write intobible/canon.mdthe setting judgments that the author unequivocally confirmed in this process and that have no conflicts. Unconfirmed or conflicting items go tofiction-continuity.
Step 2: Drafting External Packaging Copy (publish/blurb.md)
- Based on the approved positioning, referencing references/ideation-and-blurb.md and the template assets/blurb-template.md, draft: title candidates (at least 3 sets with different styles), a four-paragraph blurb, core tags, and a one-line tagline.
- According to SB §1.6 and SB §8, verify copy constraints:
- Desensitization: Do not include exact Gregorian years or words that can be mapped to reality (
lint.desensitize.*); - Banned terms: Avoid
lint.banned_terms; - Internal terms: Do not leak
lint.internal_terms(e.g., "foreshadow," "hook," "pop beat," "subplot," "outline").
- Desensitization: Do not include exact Gregorian years or words that can be mapped to reality (
- Pause and ask the author to choose, then write the selected version to
publish/blurb.md. If the title is selected or changed, also remind to verifybook.titlein.fiction/config.json(for use byfiction-init/fiction-publish). - Handoff closure: This skill is only responsible for drafting; hand over
publish/blurb.mdtofiction-reviewfor automated checks and re-review per main-text standards (lint.extra_filesincludes this file by default), and tofiction-publishwhen ready for platform submission.
Step 3: Golden Three Chapters Design
- Following references/ideation-and-blurb.md, plan the hard tasks for chapters 1–3: Chapter 1 establishes situation + desire + first anomaly/conflict; Chapter 2 active probing + first small validation/small pop beat with its boundaries; Chapter 3 raises stakes + pushes the door open wider + strong cliffhanger hook.
- Check against opening anti-patterns (no infodump-style setup, no generic weather opening, no zero-incremental filler in the first 3 chapters, keep character count manageable).
- Pause and ask the author to confirm the direction of the first three chapters; after confirmation, in Step 6, these will be written into the
## Chapter Planfirst three rows of Volume 1.
Step 4: Whole-Book Outline and Overt/Covert Dual-Line Planning
- Following references/outline-and-dual-line.md and the template assets/plot-outline-template.md, design the whole-book skeleton: phase divisions, volume intervals, volume-level big hook chains (plant the next volume's seed around
50%), overt/covert dual-line four-stage intervention thresholds (thresholds approved by the author based on total length, maintained only inbible/plot-outline.md; if the projectAGENTS.mdneeds to mention, only reference, not copy), key reversal sequences (separating what the reader knows from the author's truth), and endgame direction. - Pause and ask the author to approve the phase divisions, dual-line thresholds, and endgame direction.
- Write-back timing (strictly follow SB §4.2 order) :
- If this session only does whole-book macro-planning without touching existing volumes or detailed volume planning, after author confirmation, write directly to
bible/plot-outline.md; - If this session simultaneously creates or replans specific volumes, first keep the confirmed draft in the conversation or
bible/drafts/, and after Step 6's volume plan is confirmed, write back in order:bible/volumes/{vol}.md→bible/plot-outline.md→chapters/{vol}/vol-info.md.
- If this session only does whole-book macro-planning without touching existing volumes or detailed volume planning, after author confirmation, write directly to
Step 5: Foreshadow and Subplot Scheduling Scan (Mandatory for existing projects starting a new volume or replanning)
- First scan without filtering diagnosis categories (do not add
--only, to avoid maskinginvalidandwriteback), using the latest finalized chapter number as the argument (parameters and default--fail-onbehavior details inforeshadow-scan.mjs --help):node <this skill directory>/scripts/foreshadow-scan.mjs --at <latest finalized chapter number>- Exit code
2(couldn't find book root, configuration, or usage error): First troubleshoot the command and environment; do not treat as no issues and continue; - Exit code
1(default existsoverdueorinvalid) orwritebackgaps appear: First hand overinvalid/writebacktofiction-continuity(or the author manually) to fix the bible, then plan the new volume.
- Exit code
- Cover the entire volume interval to prevent omissions: A single
--atonly reflects a snapshot up to that chapter. After clearing existing debts, for the planned volume interval[vol_start, vol_end], manually check thePlant ChapterandPlanned Recovery Chaptercolumns inbible/foreshadows.md(and can run--at <vol_end> --only plant_due,due,overdue,dormant,subplot_alertsto preview all items due within the volume), aggregate all to-be-planted, due, overdue, dormant foreshadows and stalled subplots within this volume interval into the scheduling pool. - Pure new book handling: If
bible/foreshadows.mdorbible/subplots.mddoes not exist yet, skip the script, but separately list the new foreshadows and subplots planned for this volume for registration before handoff. - Scheduling and approval:
overdue/dueitems are prioritized for recovery in the early-to-middle part of the volume; for those that cannot be recovered on time, list options to reschedule or abandon and ask the author to approve;dormantitems schedule for light touch or recovery;subplot_alerts(stalled/span/remind_gap) arrange advancement nodes according tosubplot.*configuration.
Step 6: Volume-Level Planning, Rhythm Waveform, and Daily Update Scheduling
- Following references/rhythm-and-cadence.md and the template assets/volume-plan-template.md, draft the volume plan:
- Segmentation and emotion waveform: tense → relax → tenser; no two consecutive chapters both climax or both lull; lull chapters carry subplots, ripples, character depth, or seeds for the next volume.
- Pop beat cadence: According to
rhythm.beat_everyin.fiction/config.json(default every3-5chapters), land clear pop beats and rotate types; use micro/medium/macro "build-up then release" to amplify contrast. - External events and mini-arcs: Consecutive chapters without external events should not exceed
rhythm.external_event_max_gap(default2chapters); arrange an external event in the following chapter. Complete a mini-arc every ~3chapters. - Subplots and ripples: Each chapter should touch at least
1active subplot and arrange at least1interacting character; schedule the six-step nodes according tosubplot.remind_gapandsubplot.max_span, and reserve end-of-chapter connection points; after major events, disperse direct/indirect/distant three-layer ripples over several subsequent chapters; recover no more than1-2foreshadows per chapter. - Hook grading and daily/burst update grouping: In the
## Chapter Planningtable'sHookcolumn, indicate the planned grade (S/A/B/C, definitions in SB §7.2). Group updates for regular publishing according todaily.chapters_per_day(default2chapters), with the last chapter each day not belowdaily.last_hook_min(default minimumA); for burst periods, group according todaily.burst.chapters_per_day(default3-5chapters) in a "pop → breather → bigger pop" wave, with the last chapter not belowdaily.burst.last_hook_min(default minimumS). In writing, gradeCis only for breather chapters after big climaxes; hittinghook.discouraged(default["C"]) in automated checks triggers a prompt. Write the chapter number groupings by publish day into the volume outline's free-form area## Daily / Burst Update Grouping Notes, forfiction-chapterto fill into each chapter'soutline.md## Daily Update Position(SB §7.3).
- If this volume belongs to travel, multi-location, instance, or unit structure: Load references/region-cycle.md, establish the local main story line and at least
1attached subplot for the current station, decompose into region cycle eight steps, advancing1-2steps per chapter. Write the three items (current region cycle step, this chapter's new region understanding, this chapter's settled gains) by chapter number into the volume outline's free-form area## Region Cycle Per-Chapter Notes, without modifying the contract's eight-column table header; subsequently,fiction-chapterwill write these into each chapter'soutline.md## This Chapter's Responsibilities. - ID verification before handoff: Verify that all F-IDs and subplot IDs referenced in the
## Chapter Plantable are already registered inbible/foreshadows.md(SB §6.2) andbible/subplots.md(SB §6.3); list new unregistered items as a to-be-registered list. - First pause and ask the author to confirm the complete plan (chapter planning table, rhythm waveform, daily groupings, region three items, list of IDs to register), then strictly follow SB §4.2 order to write back:
- First write or modify
bible/volumes/{vol}.md(- Chapter Range+ free-form area + SB §7.5 eight-column table:Chapter | Core Event | Pop Beat | Hook | Subplot | Foreshadow | Character | Weight); the{start_chapter}-{end_chapter}placeholders in the template must be replaced with actual chapter numbers, otherwise scripts will not parse them; - Then synchronize
bible/plot-outline.md(align the volume's range, core storyline, and big hooks); - Finally update
chapters/{vol}/vol-info.md(SB §7.4 summary fields, do not replicate the planning table).
- First write or modify
Step 7: Handoff to Downstream
Hand over to the corresponding skill according to responsibilities; if the target skill is not installed, deliver the produced files, a clear to-do list, and unchecked items, without silently doing its work:
- Write single-chapter
outline.mdand main text based on the volume plan, and complete post-chapter writeback →fiction-chapter; - List of new foreshadows/subplots to register, reschedule/abandon writeback, or setting conflicts →
fiction-continuity; - Automated check and polish review of
publish/blurb.md→fiction-review; - Submit title, blurb, and chapters externally (synchronously verify
book.title) →fiction-publish; - Set up the book skeleton or update the public freeze list →
fiction-init; - Pipeline continues toward vertical short drama adaptation →
fiction-short-drama.
Checklist
Before delivering any planning artifact, check each item and report truthfully:
- For existing projects, a full
foreshadow-scan.mjshas been run with the current chapter number (no--onlymasking diagnosis categories, exit code not2), and allinvalid,writeback,overdue,due,plant_due,dormant, andsubplot_alertshave been fully listed[Script] - The entire volume interval
[vol_start, vol_end]has been checked against the planned recovery column inbible/foreshadows.md, and due/dormant items and stalled subplots have been scheduled into the volume outline; all F-IDs and subplot IDs referenced in the planning table are registered, or a separate to-be-registered list has been prepared for downstream[Model] -
bible/volumes/{vol}.md(SB §7.5) andchapters/{vol}/vol-info.md(SB §7.4) are format-compliant, and after author confirmation, have been written back in the ordervolumes/{vol}.md→plot-outline.md→vol-info.md[Model] - If
publish/blurb.mdwas drafted, it has been initially checked againstlint.desensitize.*,lint.banned_terms,lint.internal_terms(SB §8), and it has been noted that it must go tofiction-reviewfor automated checks; if the title changed, a reminder to verifybook.titlehas been given[Model] - Pop beat density satisfies
rhythm.beat_every, consecutive chapters without external events do not exceedrhythm.external_event_max_gap, no two consecutive chapters are both climax or both lull; daily/burst update groupings have been written into the volume outline's free-form area, each day's last chapter hook is not below the configured minimum (regulardaily.last_hook_min/ burstdaily.burst.last_hook_min), and grade C andhook.discouragedare handled appropriately[Model] - Each volume has an active big hook and a seed for the next volume planted around
50%; A/B grade subplots are attached to the main plot and scheduled according tosubplot.remind_gap/subplot.max_span; if this is a region-cycle volume, each station has a local main plot and attached subplot, eight steps are complete, three items are written by chapter into the volume outline's free-form area, and no warning-level anti-patterns exist[Model] - Competitor comparison does not fabricate sales/chart data; core selling points, golden finger cost, dual-line thresholds, title/blurb, overdue foreshadow rescheduling/abandonment, and the volume plan have all been approved by the author
[Author]
Outputs
Depending on the current step, create or update the following files:
publish/blurb.md(draft title, blurb, tags, tagline)bible/plot-outline.md(whole-book phases, dual-line thresholds, per-volume big hook chains, reversal sequences, endgame direction)bible/volumes/{vol}.md(detailed volume plan, free-form area daily groupings and region three notes,## Chapter Planeight-column table)chapters/{vol}/vol-info.md(volume summary)bible/drafts/*.md(creative variants or outline drafts not yet approved, read-only reference)
Report format for the author:
- List of newly created/updated files (note whether they were synchronized in the order
volumes→plot-outline→vol-infoafter confirmation). foreshadow-scan.mjsscan results and full-volume foreshadow/subplot scheduling summary (including exit code explanation, list of IDs to register; for pure new books, note script skipped).- Rhythm and daily update health check summary (pop beat spacing, longest consecutive chapter string without external events, emotion peaks, daily last chapter hook compliance, big hook and next-volume seed positions).
- Decision items pending author approval, downstream handoff targets (if downstream skill not installed, list delivered files, to-do list, and unchecked items).
Reference Documents
| When encountering this scenario | Read this file |
|---|---|
View directory structure, conflict resolution, minimum required reading set, writeback order by event, and sources.md (SB §1–§5) | references/formats/project.md |
View foreshadow table, subplot six-step table, character and timeline anchors, and other bible/ machine-readable formats (SB §6) | references/formats/bible.md |
View volume detailed plan eight-column table, vol-info.md, outline.md, and hook grading specification (SB §6.1, §7) | references/formats/chapter.md |
View all .fiction/config.json fields and defaults (SB §8) | references/formats/config.md |
Converge selling points from fuzzy ideas, design golden finger boundaries, draft publish/blurb.md, or polish the Golden Three Chapters | references/ideation-and-blurb.md |
| Arrange whole-book outline, overt/covert dual-line intervention rhythm, three-layer information, big hook chains, A/B/C subplot scheduling, and three-layer ripples | references/outline-and-dual-line.md |
| Arrange pop beat cadence, build-up then release, conflict escalation ladder, emotion waveform, hook grading, and daily/burst update groupings | references/rhythm-and-cadence.md |
| Plan travel, multi-location, instance, and episodic detective-style volumes with the eight-step "region cycle" and warning list | references/region-cycle.md |
Copy the empty external copy template to create publish/blurb.md | assets/blurb-template.md |
Copy the empty whole-book outline template to create bible/plot-outline.md | assets/plot-outline-template.md |
Copy the empty volume-level planning template to create bible/volumes/{vol}.md | assets/volume-plan-template.md |