What problem does it solve? Long-form fiction projects accumulate quality issues—pacing gaps, broken causal chains, AI-sounding prose—that are hard to diagnose chapter by chapter without accidentally rewriting the original text. This Skill runs the novel-studio pipeline's review stage to produce structured editorial feedback while leaving chapters untouched. ## Core Features & Use Cases - Chapter-by-chapter Editor review: Runs novel-studio --pipeline --stages review over an existing project, writing review opinions to the project's reviews/ directory without modifying chapters/*.md. - Craft-grounded diagnostics: The Editor checks against built-in human-feel craft criteria (scene anomalies, object/trace callbacks, subjective misjudgments, dialogue beats, verifiable causal chains) and writing-technique criteria (goals, obstacles, hooks, event aftermath, transitions), so feedback cites concrete fixes rather than vague style complaints. - Scoped and budgeted runs: Review a chapter range with --from/--to and cap per-chapter Editor time with --budget (default 90s). - Use Case: After generating 30 chapters of a web novel, run the review stage on chapters 3–8 to get a list of structural and continuity issues, then hand the accepted findings to a rewrite pass. ## Quick Start Enter my novel project directory and run the novel-studio pipeline review stage on all chapters, then show me the review opinions written to the reviews folder.
