Web novel complete one episodeIt is a skill that does this. It applies genre grammar to write the episode manuscript and designs the cut point so readers pay for the next episode. Platform decisions are story-webnovel-plannerassumed to have already been finished.
1. Overview
Web novels are charged per episode, so **what to include in one episode (density)** and **where to cut it (cut)** are directly tied to revenue. This skill handles both axes: genre grammar and cut intensity.
2. What this skill does not do
- Does not choose a platform — Which platform, payment structure, or exclusivity is
story-webnovel-planneris confirmed. This skill only adjusts length and cuts to match that decision. - Does not create the overall series arc or state ledger — The master plan and episode status table are
story-series-bible's responsibility. On re-invocation, it reads the ledger and restores the flow. - Does not re-list appearances — Character sheets are in
story-character-sheet. Do not list character appearances in the main text (see §3 Visual-Narrative Separation below). - Does not perform AI slop inspection itself — Completed manuscripts are passed to the regular inspection chain (§7 Post).
Visual-Narrative Separation Principle
The episode text is made to read as story . Re-listing appearance every time a character appears, such as "He, with silver hair, a mole under his left eye, and a black coat…", is the slop that most reveals AI-ness. Appearance information is gathered in story-character-sheet's character sheets, and characters are revealed in the text through actions, emotions, and dialogue.
3. Pre-check
${CLAUDE_PLUGIN_ROOT}/skills/story-webnovel-planner/references/webnovel-platforms.md— The confirmed platform's episode length and payment unit (the basis of cut rhythm).references/genre-craft.md— Genre-specific grammar and cliché handling.references/cliffhanger-grades.md— Cut intensity grades and serialization cycle.${CLAUDE_PLUGIN_ROOT}/skills/story-series-bible/references/recall-design.md— The 5 principles of reverse-calculation design on re-invocation (when receiving the ledger again to write a specific episode).
4. Workflow
Step 1 — Episode goal
Decide in one line this episode's event, emotional change, and hook for this episode. If re-invoking, first read story-series-bible the status table, and recall-design.md according to the 5 principles, design this episode not because "it's in the status table" but because "this is needed now in the overall flow."
Step 2 — Apply genre grammar
Apply the confirmed genre's paragraph length, dialogue proportion, and POV conventions. Details are in references/genre-craft.md. Clichés such as regression/possession/reincarnation have conventional grammar that readers expect, so even if subverting them, subvert them knowing that convention.
Step 3 — Writing
- Density: Align with the confirmed platform's episode length conventions (for figures, refer to the planner table; if unconfirmed, keep the flag).
- Hook placement: Plant this episode's hook naturally within the episode. The 4 hook types (emotion, curiosity, character, empathy) are
genre-craft.mdcombined with the cider/angst axis of - Visual-narrative separation(§2) complied with.
Step 4 — Cut design
Place a cut at the end of the episode (or the end of the payment unit) that pulls readers into the next episode. Cut strength is tuned by grade (the strongest cut every episode causes fatigue) — references/cliffhanger-grades.md. For a wait-free platform, align the wait-release point with the cut.
Step 5 — Length tuning
Adjust excess or shortfall against the platform's average length. Follow the planner table for numeric criteria, and if unconfirmed, leave it as "needs confirmation" and only do relative tuning.
5. Output format
# [작품제목] [N]화 — [회차 제목]
> 참조 기획서: [작품제목]_기획서.md
> 이번 회 훅: ___ / 절단 강도: [등급]
## 본문
(회차 원고 — 지문 + 대사, 외형 재나열 없이)
---
## 절단 메모
- 절단 지점: ___
- 다음 회로 넘기는 미끼(떡밥): ___
- (기다무 시) 대기 해제 지점 정렬: ___
6. Cautions
- No re-listing of appearance(§2) — AI slop priority 1.
- No strongest cut every episode — Give rhythm through strength grades (
cliffhanger-grades.md). - Re-calls are back-calculated from the overall flow — Do not write the next episode mechanically by looking at just one line of the status table (
recall-design.md). - Length figures are planner-confirmed values — Do not make them up.
7. Related skills
Before
story-webnovel-planner— Platform and serialization structure confirmationstory-series-bible— Master planning document and episode status table (required for re-calls)story-character-sheet— Character sheet (appearance goes here, not in the body text)
After
story-series-bible— Episode status table updatestory-cover-art— Web novel cover (optional)story-ip-pitch— Webtoonization and drama adaptation (optional)moai-writer:book-concept-planner— Conversion to book form (one-way handoff)
Post (Review — regular chain for text deliverables)
moai-coworker:ai-slop-reviewer— AI slop review (required)moai-writer:korean-humanize— Precise polishing of AI tells (required)
⚠️ Web novel episodes are the genre where readers are most sensitive to AI tells. The regular chain is required.
8. References
| File | Load conditions |
|---|---|
references/genre-craft.md |
When genre-specific grammar, clichés, and the 4 hook types are needed |
references/cliffhanger-grades.md |
When cut strength grades and consecutive-release cycles are needed |
../story-webnovel-planner/references/webnovel-platforms.md |
Confirm confirmed platform episode length and payment unit |
../story-series-bible/references/recall-design.md |
Back-calculation design for re-calls |
9. Sources
- Visual-narrative separation and 4 hook types: aitoon-plot planning system (internal asset transplant).
- Genre grammar and cliché operation: Korean web novel serialization practices (organized in references; figures to be confirmed with the platform).
- Original copywriter: Jo Nam-kyung (https://www.facebook.com/Bmisty)