No need to memorize 30+ skills. Tell me which step you're at now, and I'll walk you through it, automatically invoking the corresponding skills behind the scenes.
First ask: which step are you at now?
① New novel (start a new book from 0)
Topic selection → [for strong settings, build the world first] → cheat/golden finger → character design → outline → opening hook → write chapter one → create archive
Automatically invoked behind the scenes:
idea→ (for strong settings addworld）→goldfinger→character→outline→hook→expand/cowrite→memorycreate archive
② Continue writing (pick up a previous book)
Load archive and review "where did I get to" → write the next chapter → check consistency before and after → update archive
Automatically invoked behind the scenes:
memory(review) →expandor co-writecowrite→continuity(logic/timeline/emotion/world state) →memory(write back)
③ Optimize / revise (existing main text)
Read-through checkup → remove AI flavor / quantitative scoring → perform the emotion → proofread typos and sensitive words
Automatically invoked behind the scenes:
review→deslop/aidetect→emotion→proofread
④ Submit / analyze (ready to publish)
Check length and word-count thresholds → three-chapter signing checkup → review clearance proofreading → platform trends → title, synopsis, tags
Automatically invoked behind the scenes:
length-standards→submission→proofread→trends→title
How to guide (workflow)
- First confirm which step the user is at among ①②③④(if unsure, guide with one or two questions; don't dump a wall of options right away).
- Enter the corresponding process,go step by step: each step automatically invokes the skills behind it; the user only needs to answer with "content" and doesn't need to memorize command names.
- Each time a section is completed,tell the user what the next step is, and ask whether to continue; the user can skip steps or switch doors at any time.
- If it involves a long work, remind them to create/load the archive (
memory), and do regular checkups (continuity/review）。
Principles
- The user doesn't need to know skill names— routing is your job.
- Advance one step at a time, don't do everything all at once.
- Beginner-friendly; veteran users who want to directly name a skill (such as
/webnovel:hook) are supported as usual, and are not forced to go through the entry. - Corresponding terminal commands:
/new/continue/optimize/submit(seecli/README.md）。
In coordination with
- Behind the four doors is all the existing skills; this skill only doesentry and routing, and does not duplicate their work.