What problem does it solve?
Long-running webnovel projects accumulate many files, databases, and configs across phases; when something breaks it is hard to know which directory, JSON file, SQLite table, RAG setting, Python dependency, or Dashboard build artifact is missing. This Skill performs a read-only health check so you can see exactly what is incomplete without risking any changes to your book project.
Core Features & Use Cases
- Phase-aware diagnosis: Reads the project's current phase via project-status, then checks only what that stage should have, so a freshly initialized project is not judged by the standards of a 200-chapter one.
- Full-stack integrity check: Verifies directories, files, JSON state, SQLite databases, RAG configuration, Python dependencies, and Dashboard build output in one pass.
- Actionable reporting: Reports the current phase and target chapter, blockers, missing or abnormal file paths, and the impact plus suggested fix for each issue.
- Use Case: After moving your novel project to a new machine, run a deep check with --deep to confirm the SQLite state, RAG index config, and Dashboard build artifacts all survived the migration before writing the next chapter.
Quick Start
Ask the assistant to run a read-only health check on the current webnovel project and report any missing files, configuration, or dependencies.