Viral Web Novel Creation Workflow

The Problem

Web novel projects often fail not because of prose quality, but because the pipeline from trend selection to naming, worldbuilding, characters, plot, and chapter pacing is missing. If a model starts writing immediately, the output can drift into the wrong genre, lose character consistency, forget planted foreshadowing, fall short on chapter length, or read like generic AI text. This skill replaces that ad hoc flow with a staged, confirmation-driven workflow.

How It Works

• Trend analysis: uses WebSearch and WebFetch to compare current genres, platform trends, and hit formulas, then presents S/A/B-tier options for the writer to choose from.
• Design gates: moves through title → worldbuilding → characters → plot → ten-chapter plan, requiring user confirmation before the next step.
• Writing constraints: targets at least 3000 Chinese characters per chapter, with short sentences, fast pacing, chapter-end hooks, and restrictions on common AI-sounding phrases.
• Periodic QA: every ten chapters checks character behavior, foreshadowing payoffs, timeline continuity, word count, and pacing.
• Project files: stores design docs and chapters under novel-project/ paths, making ongoing serialization easier to manage.

Limits

It is best for long-form web novel drafts and serial writing where the author needs a structured outline and continuous chapter production. It is less suitable for short stories, editorial copy, screenwriting, or publication-ready prose without additional review. Search, automation, and file writes depend on the runtime providing those tools; unconfirmed design notes should not be treated as final canon.