Web Novel Chapter Writing
Turn a confirmed plot direction into a full chapter, then after validation record what actually changed back into the story bible.
When to Use / Not Use
- Write a new chapter, continue a half-finished draft, rewrite, or restructure an unfrozen chapter: use this skill.
- Change the overall story direction, restructure volume outlines, decide on payoff rhythm, hook levels, or daily update combinations: hand over to
fiction-planner.fiction-initonly builds the skeleton,fiction-plannersets the volume-level plan; this skill writes a single chapter outline based on that plan and is responsible for post-chapter writeback. Without a planning skill, only execute the existing volume outline; if the plan must change, present the current state and pending items, wait for the author to confirm, and sync volume planning before touching the main text. - Editorial review only, deep check for cross-chapter contradictions, narrative and style consistency, or authorized local fixes, polishing, and removing AI-like prose in an existing chapter: hand over to
fiction-review. If only a deep review is requested but not installed, provide the existing draft, to-do items, and checks not yet performed; do not substitute a light review for a full edit. - Drafting
publish/blurb.md: hand over tofiction-planner. Review/edit:fiction-review. External submission:fiction-publish. When a new book title is confirmed, remind the author to update the configuredbook.title(SB §8).
When downstream skills are missing, deliver the existing files, next to-do items, and checks not performed; do not perform their duties on their behalf or report them as passing.
Before You Start
Open the following files in the author's book root: AGENTS.md (especially the "Book Ground Truth" section), .fiction/config.json, bible/sources.md. Writing conventions follow the "Book Ground Truth" first, then bible/style-guide.md, and finally the defaults in this skill. bible/sources.md registers the single source-of-truth file for each category of information (the main writeback entry point, see SB §5); only write back to that entry point, so the same fact is never maintained in two independent copies.
Before writing or modifying any machine-readable file, first open the corresponding format reference from the reference table at the end of this document, and write according to the original format; do not rely on memory.
If the project skeleton is missing, prompt the user to first use fiction-init. If it's not installed, ask the author to provide or complete the necessary files; do not guess and write assumptions as established facts. If only the configuration is missing, scripts may use contractual defaults; inform the author. If you cannot confirm whether the target chapter has already been published, do not modify any existing draft. All following paths are relative to the book root; run scripts from the book root, replace placeholders in commands with actual values, and quote paths containing spaces.
If the author only wants a trial passage or to stop after a certain step, do so and explain which steps have not been completed. Do not treat a trial passage as a full chapter writeback.
The Six-Step Process
1. Check Context: First Determine if Writing is Possible
Confirm the chapter number and its volume (SB §2, SB §7.5). Chapter numbers are unique across the book, no zero-padding. Existing chapters are in chapters/{vol}/{ch}/; for a new chapter, first check the range in bible/volumes/{vol}.md, then cross-reference with chapters/{vol}/vol-info.md. If the volume assignment is ambiguous, stop and ask the author. If the chapter number falls within frozen.ranges, do not touch that chapter's files: no rewriting, no sentence additions, no reformatting, no new manuscript (SB §7.1). Report the issue and suggest either explaining in a subsequent unfrozen chapter or handing over to fiction-continuity to arbitrate the canon; do not retroactively edit text already seen by readers.
When the author confirms a new chapter has been published, hand over the chapter number and the corresponding adopted draft path to fiction-init's "update freeze list" mode; do not freeze it within the chapter writing process. If fiction-init is not installed, ask the author to handle it in two steps: first, append the confirmed published chapter to frozen.ranges in .fiction/config.json (SB §8), then run node <this skill directory>/scripts/lint.mjs --freeze from the book root (SB §4.2). Do not manually edit hashes or force overwrite the existing freeze list.
Read the volume summary chapters/{vol}/vol-info.md, the detailed volume plan bible/volumes/{vol}.md, bible/canon.md, then run:
node <this skill directory>/scripts/brief.mjs <ch>
For a new chapter that doesn't yet have a directory, and the volume range does not yet cover the target chapter, use node <this skill directory>/scripts/brief.mjs <ch> --vol <vol> only after the author has confirmed the volume number. This only specifies which volume the brief should read from; it does not replace completing the volume plan. If the chapter's responsibilities are not yet determined, first hand over to fiction-planner or wait for author confirmation.
The brief is an index, not the full text of the materials. Look at the chapter plan, foreshadowing that should be planted/triggered/resolved, overdue reminders, active subplots, characters, and time anchors. Success may still include reminders: missing files, parsing errors, or unregistered characters. If a core character has been absent for a long time, first assess whether it relates to this chapter's responsibilities; do not force them in. If the chapter outline conflicts with the established volume plan, do not make a decision based on the brief's merged results. First check the volume plan; if the direction is changing, the author decides.
Open the end of the previous chapter's final draft (cross-volume, using the global chapter number). Confirm the location of the last scene, who was present, any unfinished actions or cliffhangers. The brief only captures the tail; if the connection is unclear, read more sections. If it is indeed the opening chapter, note "No previous chapter." If a previous chapter should exist but has no draft, do not fabricate the connection. For continuation, also open the existing resources.md, outline.md, and the designated draft for this chapter; locate where the draft stopped.
Open the main writing files and anchor points listed in the brief. Read the relevant original text rather than scanning the entire bible/ directory. For stable character traits, check bible/characters.md. For current relationships and states, check bible/character-dynamics.md. Whenever time moves (time skip, recovery, season change, deadline approaching, or event reordering), first check bible/timeline.md. Forward-propagate from the previous chapter's time or backward-propagate from the deadline; verify required durations, event order, and windows. Use precise internal anchors; use relative time in the main text. If factual conflicts or insufficient material will change the plot, stop and ask the author to decide. Do not write any files during this step.
2. Extract to resources.md: Keep Only Materials for This Chapter
Copy the materials verified in Step 1 into chapters/{vol}/{ch}/resources.md. Follow SB §7.4: one entry per line, each ending with the source (Source: relative path#heading). The first entry is the end of the previous chapter (or note "No previous chapter" and point to the volume plan). The second entry is this chapter's responsibility and writing boundaries. Then extract only the rules, current character relationships, item status, reader-knowledge state, and time calibration that this chapter will actually use. Do not copy entire pages; do not treat discussion drafts as established facts. If while writing you read necessary additional material, add its source back here. No extra scripts; if key materials cannot be found, return to Step 1.
3. Write outline.md First: What This Chapter Changes
Starting from resources.md, the volume plan, and the final drafts/outlines of adjacent chapters, write chapters/{vol}/{ch}/outline.md. First open the complete example in SB §7.3: the first line is # Chapter {ch} outline, with H2 headings following the table. Machine-readable line examples (from the same section): - B2 Cascade: The Debtor's cigarette case appears in the lock room, - Plant F004: New cigarette case, - Present: Tang Qi, - Level: A. Only borrow the format; replace with the actual chapter content and registered IDs.
State the chapter's responsibility in one sentence: what it advances and what changes by the end. For each scene, specify the location anchor, sense of time, what the character wants, and what changed when they left. Distinguish between "planned to appear" and "only mentioned." For foreshadowing, specify: Plant/Trigger/Resolve/Drop. For subplots, if only touched on, do not force-fill a lifecycle step. When the volume plan uses zone cycling, read bible/volumes/{vol}.md for the sequence of handoffs in the free zone by chapter number, new zone understanding, visible benefits; apply the corresponding content for this chapter into the existing ## Chapter Responsibility or ## Scenes sections; do not add machine-readable fields.
- External Event: Look back at what actually happened in previous chapters. If it has been
rhythm.external_event_max_gapchapters since the last external event, arrange an interruption in this chapter that comes from outside the character's current plan, forcing a change in action, choice, or cost; not just a noise. [Model] - Subplots & Interaction: Touch at least one active subplot, and include at least one actual character interaction; do not write an entire chapter of monologue. Touching can be brief, like a letter causing a character to change an appointment; it does not need to be a formal step forward every time. Do not start a new subplot just to meet the requirement. If there are no active subplots, ask the author to decide. [Model]
- Mini Arc: Default approximately three chapters for a complete setup → development → climax/turnaround. Check which beat this chapter takes, and whether the volume's core suspense is advanced, reminded, or explicitly left for later chapters. Do not write consecutive chapters at the same intensity. [Model]
- Daily Updates & Hooks: According to the volume plan's free zone handoff by chapter number for daily update grouping, in
## Daily Update Position, fill in whether this is the Nth chapter of the day and whether it is the last. Carry over the hook level from the plan table, and in## Hook, write this chapter's specific landing point. For the last chapter, check against the configureddaily.last_hook_minordaily.burst.last_hook_min(SB §8). If no arrangement exists, ask the author to confirm; do not self-group or change levels. [Model]
No extra scripts for this step. If the author is collaborating in real time, first send the outline for confirmation before writing the main text. If not working in real time and the direction is set, you may continue based on the outline. If you need to deviate from the volume plan, change established settings, or overwrite the author's existing text, first obtain consent.
4. Write v{n}.md: Let the Change Happen in Scenes
Read the chapter outline, materials, and bible/style-guide.md. Write into chapters/{vol}/{ch}/v{n}.md following the complete example in SB §7.2. The example's first line is # Chapter 12: The Lock Room Light, using a full-width colon, with the chapter number matching the table of contents. Use the following paragraph budget to organize the main text; do not use these names as headings in the text:
Opening Hook (200–400 characters) → Scene One (Main Event) → Scene Two (Deepen Conflict or Weave Subplot) → Optional Scene Three → Ending (300–600 characters) → Optional Next Chapter Teaser → Hook Marker.
The two main scenes can be estimated at 800–1200 characters each, adjusted for the chapter's responsibility and the book's word count goals. The opening and ending can be part of the first and last scenes; scene breaks, optional next chapter teaser, and final hook marker follow the examples in SB §7.2. Write the hook marker based on the actual landing point; if the landing point does not meet the planned level, first rewrite the ending or ask the author to confirm the deviation.
Start the first sentence with a specific object, action, or dialogue, providing new information or creating tension. Do not open with weather if it does not affect the plot. Action sections: "Goal → Obstacle → Surprise or Cost." Reaction sections: "Reaction → Dilemma → Decision." The decision leads to the next scene's goal. Dialogue: by default, insert a meaningful action or expression every 2–3 sentences. Say information only once; if dialogue has already made it clear, narration should only supply unstated meaning or consequences. Delete authorial summaries that judge for the reader. Compress smooth processes that add no information, emotion, or risk increments. When technical terms first appear, explain in plain language what they are and what they do at that moment.
For techniques on scene, dialogue, and preparation chapters, action chapters, payoff reviews, transactions, or using in-world materials to set up lore, consult fiction-craft. If not installed, follow the book's style guide and the minimal references below; do not start another scene just to use a template. If a new rule will determine the plot, ask the author to decide first. If a change to established settings is involved, update the authoritative entry first, then write the dependant plot, and verify again during writeback.
Revision: New chapters use v1.md. For permitted minor edits and continuation, directly modify the current draft; do not overwrite unauthorized text. For major changes (scene order, key causality, chapter-end landing point, etc.), increment from the highest existing draft number to create v{n+1}.md, keep old drafts, and update outline.md's ## Final Draft to point to the draft version for review. When a final draft already exists, switching to another draft also requires author consent. The draft pointer is not proof of passing editorial review. No extra scripts for this step.
5. First Pass Machine Checks, Then Review & Edit
Confirm the chapter outline points to the current draft version. When run with a chapter number, the script checks the specified final draft; if none specified, it uses the highest draft number. Run in sequence:
node <this skill directory>/scripts/length.mjs <ch>
node <this skill directory>/scripts/lint.mjs <ch>
length reads the main text and length.* settings. SHORT must be fixed by adding real scenes: increase obstacles for the goal, let interactions change decisions, and land consequences in actions. Do not add recaps or summaries. LONG is not a failure; if significantly above the soft limit, check if the chapter is handling two chapters' worth of responsibility, first compress repetition and idle sections; if a split is needed, ask the author to confirm. Script counts are not equal to platform counts, and cannot detect padding.
lint reads the main text, configuration, author word list/patterns, and the freeze list. Fix each BLOCK entry one by one; for SUGGEST entries, judge the context. If an overall freeze anomaly is encountered, report it and stop; do not modify frozen text or redo hashes to conceal the problem. Exit code 2 indicates usage, configuration, or read errors; not a passing result.
After the machine checks pass, hand over the current main text, chapter outline, style guide, machine check results, and the scope of authorized revisions to fiction-review, following the process "Raise Issues → Revise → Recheck." Clearly state whether it is a "First draft, pending writeback" or "Under revision, pending sync." Do not treat missing writeback as a review failure at this stage. Only accept review as passed after the final draft or revised draft is written back. Allow fiction-review to directly edit drafts only with author authorization, confirmation that the chapter is not frozen, and clear publication status. Structural rewrites should be returned to this skill.
If fiction-review is not installed, do a self-check using the Light Review & Writing Notes within the chapter. Deliver the draft, deep review to-do items, and checks not yet performed. Report: "Light review completed; editorial review not performed." If the review changes appearances, subplots, foreshadowing, or the ending, cross-check the chapter outline and materials. Do not circumvent established plot commitments by deleting outline entries. If the main text was modified, rerun both machine checks. Leave direction or setting disputes to the author; do not proceed to post-chapter settling with unresolved blocking issues.
6. Post-Chapter Settlement: Write Back Based on Final Draft, Then Verify
Read the final draft, chapter outline, and bible/sources.md. First compare the main text against the chapter outline's actual actions, then write back following SB §4.2. For the master writeback table format, see SB §6. If something planned in the outline was not written into the main text, do not mark it as completed. If new actions occurred in the main text not planned in the outline, first reflect them accurately in the outline; if that deviates from an approved plan, first ask the author to confirm.
| Master Writeback File | What to Write Back |
|---|---|
bible/appearances.md | One line per chapter, distinguishing between present and mentioned based on the main text. For revisions, update the existing line; do not add a new one. |
bible/foreshadows.md, bible/subplots.md | Compare actual actions and steps in the chapter outline; write chapter number and status. Touching does not equal advancing a step. Foreshadowing: separate reader-known from author-truth. For unresolved ones, write how they will return in the future. Do not delay registering a new plant until the next chapter. |
bible/storylines.md, bible/character-dynamics.md, bible/inventory.md | Sync only changes: actual progress on overt/covert storylines, character relationships/arcs, item consumption, damage, borrowing, or exchange. Do not copy a summary of plot events. |
bible/timeline.md | Record new hard anchors, windows, deadlines, or confirmed sequence changes. |
bible/canon.md | Following fiction-continuity's conflict priority rules (SB §3), write only decisions the author has explicitly confirmed in this workflow and that have no conflicts. For unconfirmed or conflicted items, hand over to fiction-continuity. |
bible/characters.md, bible/world-rules.md | New characters: add static profiles. Rule changes: update corresponding details. |
Place the connection points left by this chapter in the post-chapter report's "What was written" section. When writing the next chapter, extract them into the next chapter's resources.md following SB §7.4. Do not add H3 headings with non-subplot IDs in bible/subplots.md (SB §6.3), and do not write possible connections as already happened. If a revision conflicts with a later final draft, first ask the author to decide. If this happens to finish a volume, hand over to fiction-continuity to write chapters/{vol}/summary.md and sync the chapter status in chapters/{vol}/vol-info.md (SB §7.4). Retrospective reflection should not reverse planning. For confirmed writing conventions, hand over to fiction-craft to update bible/style-guide.md. Markdown is authoritative; projects using fiction-story-db can update the index after writeback; if not installed, skip the index.
After confirming the target chapter has a readable final draft and outline, run directly from this skill:
node <this skill directory>/scripts/foreshadow-scan.mjs --at <ch> --only writeback,invalid --fail-on writeback,invalid
--at is the cutoff chapter, not checking just one chapter. Reading writeback by chapter number, invalid by file and line number. This chapter must have no writeback entries, and this chapter's outline and related master writeback records must have no invalid entries. If a parsing error in the master writeback table makes it impossible to determine whether this chapter is correctly verified, that also counts as not passing. Exit code 1 means findings exist within the scan range, not necessarily belonging to this chapter. Findings that only involve older chapters or unrelated records should be reported separately; do not unilaterally modify older chapters. Exit code 2, or failure to run, or missing draft/outline, also counts as not passing. After fixing the main text, outline, or related master writeback records, rescan; do not use old results as verification.
Also perform a manual writeback check: scanning will not detect actions in the main text that were missed in the chapter outline, nor verify appearances, time, items, or other writeback targets. When scripts are missing or give errors, you may use the manual checklist to locate omissions, but can only report "Machine check pending" or "Machine check failure"; do not declare completion.
Delivery Checklist
- Target chapter, volume, freeze range, and connections have been verified. If time progressed, timeline was checked. [Model]
- Chapter outline was written first, then the text; scenes have transitions; subplot touches, interactions, and external events meet rhythm conditions; actual hooks match the outline. [Model]
- Where author decision, protection of existing drafts, or real-time outline confirmation was needed, consent was obtained. [Author]
- Current final draft meets the minimum word count;
linthas no blocking issues. [Script] - Editorial review or light review has been completed; no recaps, summaries, or idle padding were used to fill length. [Model]
- Master writeback records (appearances, foreshadowing, subplots, etc.) have been updated based on the final draft for actual changes; planned events were not treated as facts. [Model]
- The final draft, corresponding outline, and related master writeback records required for the scan are all present. [Model]
- In the latest scan, this chapter has no
writebackentries, and this chapter's outline and related master writeback records have noinvalidentries. [Script]
Output & Report
Deliver resources.md, outline.md, the current v{n}.md, and any modified master writeback files. Report to the author in four lines:
- What was written: Volume / Chapter / Draft version and path; what this chapter delivered, and what action, item, or relationship the next chapter can pick up from.
- Checks: Effective character count, word count status,
lintblocking count and non-adopted suggestions, review or light review conclusion, any checks not yet performed. - Writeback: Which master files were modified; whether this chapter's scan passed, failed (missing items / invalid records), not covered, or not run; unrelated old issues listed separately. If this chapter did not pass, report as incomplete.
- Pending: Issues that need the author's decision and possible options; write "None" if none.
Reference Documents
| When you encounter… | Read this |
|---|---|
| Check project paths, main writeback entry points, conflict arbitration, or writeback responsibilities | SB §1–5: Project Structure & Read/Write Rules |
| Update foreshadowing, subplots, characters, timeline, and other master bible records | SB §6: Bible Machine-Readable Format |
| Read volume plan, write chapter outline, main text, resources, or volume-end retrospective | SB §6.1, §7: Chapter Files |
| Check freeze range, word count, rhythm, daily update, or title key | SB §8: Project Configuration |
| Unsure how to cut scenes, plant clues, or perform light review & manual writeback check | Light Review & Writing Notes |