Web Novel Writing Reference

Problem

Web novel writing is not just drafting one chapter. It requires coordinated handling of worldbuilding, outlining, character systems, conflict, scene execution, pacing, revision, and commercial operation. Without a shared task model, prompts tend to focus on single-scene text and can miss setting consistency, pacing hooks, platform constraints, and reusable structural checks.

How It Works

Web Novel Writing Reference organizes web novel production into 8 domains and 62 task types across input, design, execution, quality-control, and commercial layers. It provides task catalogs, component slots, exemplar indexes, and dependency topologies. For example, references/writing-catalog.md maps domain scope, structure-requirements.md defines task components, and exemplars.md supplies sample references. The workflow starts by loading the catalog, then retrieves structure requirements or exemplars for the target task type, and finally passes list-based inputs, sample-based inputs, and dependency inputs to Universal Task OS for execution-axis and content-axis orchestration. Fields marked [user input required] or [to be completed] must be filled by the author before full generation.

Boundaries

This skill does not include an execution framework and depends on Universal Task OS. Without UTOS, it can only be browsed as a reference and cannot generate chapters, outlines, or writing pipelines. It fits structured web novel production where reusable task lists and quality checkpoints matter; it is not for one-shot unstructured drafting.