What problem does it solve? Long-running AI novel-writing pipelines can silently stall, drift from the outline, or lose character continuity, and the evidence is buried in local output artifacts. This Skill statically analyzes a project's output directory and surfaces actionable findings instead of forcing you to inspect pipeline state files by hand. ## Core Features & Use Cases - Four-Dimension Diagnosis: Checks process (rewrite loops, unconsumed steering directives, chapter gaps), quality (review scores, contract fulfillment, rewrite rates), planning (stalled foreshadowing, outdated compass, exhausted outline), and context (disappearing characters, timeline gaps, stale relationship data). - Pipeline Evidence Verification: Read-only inspection of meta/pipeline.json flags completed stages missing evidence, unverified evidence states, or missing artifacts and checkpoints. - Sanitized Issue Export: Writes meta/diag-export.md with story content removed, leaving only a behavioral skeleton suitable for pasting into a GitHub issue. - Use Case: Your serial novel project feels stuck after chapter 40. Run the diagnostic to discover an unconsumed steering directive and a foreshadowing thread that has not advanced in ten chapters, then attach the sanitized report to a bug report. ## Quick Start Run the novel-studio diagnostic on my current project and tell me why the pipeline is stuck.
