What problem does it solve? Writing and revising serialized fiction often fails in predictable ways: episodes that change nothing, characters whose voices blur together, villains who lose menace the moment the protagonist wins, foreshadowing that is never paid off, and reader comments treated as direct commands. This Skill provides a structured contract for planning, drafting, adapting, and diagnosing serial novels and webnovels so each episode delivers value while protecting canon and continuity. ## Core Features & Use Cases - Canon and continuity management: Separates approved canon decisions from legacy drafts using staged migration classes (STRICT_NOW, BOUNDED_LEGACY_RECONCILIATION_DEBT) with fail-closed invariants, so adaptations never silently rewrite protected story facts. - Episode and arc quality gates: Audits Reader Promise, Episode Value, Local Payoff, Open Loops, information legibility, pattern variation, consequence memory, and setup-payoff debt with named failure states. - Character and opponent integrity: Ensures major characters have distinct observation filters, voices, and problem-solving methods, and that important opponents prove their threat on-screen before the protagonist wins through skill, tactics, rules, or relationships. - Reader feedback as evidence: Converts raw comments into symptom clusters and minimal revision hypotheses instead of promoting single comments to canon. - Use Case: When revising a 200-episode webnovel adaptation of a TRPG log, use this Skill to verify that a canon change is migrated without blind rewrites, that a supposedly strong rival demonstrates threat on-screen, and that each revised episode changes at least one story state. ## Quick Start Use the developing-and-revising-serial-fiction skill to diagnose the attached episode draft for episode value, local payoff, and opponent threat integrity before I revise it.
