Novel Craft: Growth Novel Studio

The Problem

The main engineering issue in long-form web novels is not whether chapters can be generated, but whether the story remains consistent. As the plot extends, models can forget character positions, contradict power rules, miss planted setup, and break the timeline. novel-craft（爽文工坊） turns these continuity risks into checkable files and workflows, so each new chapter begins by reading stored story state instead of relying on context memory.

How It Works

The skill routes common intents into six workflows: create, continue, revise, extend settings, review progress, and export.
- Prompt refinement: it first identifies the reader payoff you want, such as high-impact reveal, strategy, growth, emotional healing, or discovery, then checks the protagonist's starting point, ability limits, and early highlights.
- Outline and chapters: it produces output/提示词.md, output/大纲.md, and chapter files, with attention to conflict, suspense, pacing, and progression.
- Memory system: it maintains CHARACTERS.md, LOCATIONS.md, PLOT_POINTS.md, STORY_BIBLE.md, TIMELINE.md, FORESHADOWING.md, and CHAPTER_INDEX.md for characters, locations, plot, canon, time, setup, and chapter index.
- Error tracking: continuity failures, characterization breaks, pacing issues, and forgotten setups are logged in ERRORS.md.

Boundaries

This is useful for chapter-based growth novels that need strong pacing and continuity, not for one-off copy. If the user only provides a one-line idea, prompt and outline confirmation are still required. For long runs, the main risk is stale memory files, not model creativity.