--- description: Auto-detect what to do next in your workflow and run it. The one command a writer can always use. --- # Next You are routing the writer to the right next step in their workflow. This command is the universal interface -- a writer who only ever types `/scr:next` should be able to complete an entire novel. ## What to do 1. **Check for `.manuscript/` directory.** If none, the writer has no project. Run `/scr:new-work` to start one (or tell them to). 2. **Read `.manuscript/CONTEXT.md` first if it exists.** This is the auto-regenerated bootstrap file written by `/scr:save`, `/scr:pause-work`, and `/scr:resume-work`. It already contains the suggested next step. If CONTEXT.md is present and its `Updated` timestamp is newer than STATE.md, you can route directly off its `Suggested next step` field without re-deriving from raw files. If CONTEXT.md is missing or stale (older than STATE.md, or older than the newest file in `.manuscript/drafts/body/`), continue with step 3 -- treat STATE.md as authoritative and silently note that CONTEXT.md should be regenerated on the next `/scr:save`. If CONTEXT.md and STATE.md disagree, trust STATE.md and warn the writer in one sentence so they can decide whether to run `/scr:scan`. 3. **Read `.manuscript/STATE.md`** to figure out the current workflow position. STATE.md tracks: current unit, current stage (discuss/plan/draft/review/submit), last command run, pending revisions, unresolved notes. 4. **Read `.manuscript/RECORD.md` when present.** Use it to notice open threads, unresolved promises, continuity obligations, and next-unit obligations that may make more than one next path valid. If RECORD.md is missing in an older project, continue and suggest `/scr:scan --fix` only when the missing store would affect the next step. 5. **Read `.manuscript/config.json`** to get the work type and command_unit (chapter, act, section, surah, etc.). 6. **Explain what you're about to do in ONE plain-language sentence**, then run it. Examples: - "You just finished drafting Chapter 3 -- running editor review now." - "Chapter 4 has a plan but no draft yet -- drafting it." - "You haven't discussed the next chapter -- shaping Chapter 5." ## Routing logic Use the core writing lifecycle as the default map: `seed -> voice -> outline -> discuss -> plan -> draft -> review -> revise -> publish -> translate` Walk the core chain in order and run the first incomplete step: 1. **No OUTLINE.md** -> `/scr:discuss` (high-level discussion about the whole project) 2. **No CHARACTERS.md / FIGURES.md and work type supports them** -> `/scr:new-character` loop 3. **No STYLE-GUIDE.md calibration done** -> `/scr:voice-test` 4. **No {unit} discussed** -> `/scr:discuss N` (next pending unit) 5. **No {unit} planned** -> `/scr:plan N` 6. **No {unit} drafted** -> `/scr:draft N` 7. **No editor review** -> `/scr:editor-review N` 8. **Not submitted** -> `/scr:submit N` 9. **All units submitted** -> `/scr:complete-draft` or start next unit 10. **Draft complete, no revisions** -> suggest revision, beta reader, or publishing path 11. **Revisions pending** -> run the next revision step 12. **Everything done** -> suggest publishing: "Your draft is complete. You could start revisions, run a beta reader pass, or begin the publishing pipeline." ## Edge cases - **Multiple valid next steps** -- Present choices: "Chapter 3 is ready to draft, but you also have editor notes on Chapter 2. Which first?" - **Record-driven branch** -- If RECORD.md shows an open thread, promise, continuity obligation, or next-unit obligation that competes with the linear workflow, offer it as a separate path instead of forcing the next lifecycle step. - **Stuck state** -- If a command failed recently (logged in STATE.md), offer `/scr:troubleshoot` instead of retrying blindly. - **Blocking craft question** -- If a context or plan file contains `QUESTION: Blocking`, route to `/scr:discuss N` before drafting. - **Non-blocking craft question or watchpoint** -- If only `QUESTION: Non-blocking`, `HUNCH`, or `WATCHPOINT` items remain, allow the next draft or review step and mention the watchpoint in one sentence. - **Autopilot mode** -- If config has `autopilot.enabled: true`, run multiple steps in sequence without asking, pausing only per the profile's rules (guided, supervised, full-auto). ## Adaptive naming Use canonical runnable commands, and adapt the terminology in prompts/output for the current work type. If `command_unit` is `surah`, run `/scr:draft` and frame the work as drafting a surah; keep the command id stable and treat unit labels as presentation only. ## Response Contract Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do. Use this format: ```markdown Next commands: - `/scr:...`: One short sentence explaining what this path will do. - `/scr:...`: One short sentence explaining what this alternate path will do. ``` If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice. If the writer seems unsure or no specific next command is obvious, include this default option: ```markdown Next commands: - `/scr:next`: Inspect the project state and choose the right next step. ``` If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing. ## Tone Brief. Decisive. Don't explain the routing logic to the user -- just tell them what you're doing and do it. They're trusting you to know.