scriveno 2.0.5

package/commands/scr/add-note.md

@@ -0,0 +1,51 @@
+---
+description: Add a quick note or reminder to the project notes file.
+argument-hint: "<note text>"
+---
+
+# Add Note
+
+You are adding a quick note to the project's notes file.
+
+## What to do
+
+1. Take the note text from the argument
+2. Open `.manuscript/NOTES.md` (create it if it doesn't exist)
+3. If creating: add header `# Project Notes\n\n`
+4. Append the note with a timestamp:
+   ```
+   - [2026-04-07 14:30] Note text here
+   ```
+5. Save the file
+6. Confirm: "Note added."
+
+## Format
+
+Each note is a bullet point with an ISO-style timestamp (date + time, no seconds). Notes are appended in chronological order -- newest at the bottom.
+
+## 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
+
+Minimal. Just confirm. The writer is jotting something down quickly and wants to get back to work.

package/commands/scr/add-unit.md

@@ -0,0 +1,101 @@
+---
+description: Add a new unit to the end of the outline.
+argument-hint: "[title]"
+---
+
+# /scr:add-unit -- Add New Unit
+
+Add a new structural unit to the end of the outline.
+
+## Usage
+```
+/scr:add-unit [title]
+```
+
+## Instruction
+
+You are a structure management assistant. Load:
+- `.manuscript/config.json` (to get `work_type`)
+- Scriveno's installed/shared `CONSTRAINTS.json` (global `~/.scriveno/data/CONSTRAINTS.json` or project `.scriveno/data/CONSTRAINTS.json`) (to find `work_types[work_type].hierarchy` and determine unit terminology)
+- `.manuscript/OUTLINE.md` (current structural outline)
+- `.manuscript/STATE.md` (progress tracking)
+
+**Work-type adaptation:** Determine the correct unit name from CONSTRAINTS.json hierarchy:
+- Novel: "chapter" (hierarchy.mid)
+- Screenplay: "scene" (hierarchy.atomic) or "act" (hierarchy.top)
+- Short story: "section" (hierarchy.mid)
+- Scripture (Biblical): "chapter" (hierarchy.mid)
+- Use `command_unit` from CONSTRAINTS.json as the default unit level
+
+Use the adapted unit terminology throughout all output and prompts.
+
+---
+
+### ADD UNIT FLOW
+
+<add_unit>
+1. **Resolve unit type** from CONSTRAINTS.json `work_types[work_type].hierarchy`
+   - Use `command_unit` to determine which level of the hierarchy this command operates on
+   - Display the resolved unit type to the writer: "Adding a new [chapter/scene/section/etc.]"
+
+2. **Prompt for details** (if not provided via argument):
+   - Title (required)
+   - Brief summary (1-2 sentences describing the unit's purpose)
+   - Placement in arc (if `.manuscript/PLOT-GRAPH.md` or adapted equivalent exists):
+     ask which arc position this unit occupies (e.g., "rising action", "climax approach")
+
+3. **Check for draft safety** (D-07):
+   - Scan `.manuscript/drafts/body/` for existing draft files
+   - Adding to the end should not affect existing drafts, but verify numbering continuity
+   - If the new unit number conflicts with any existing file naming, warn the writer
+
+4. **Update OUTLINE.md:**
+   - Append the new unit to the end of the unit list section
+   - Assign the next sequential number
+   - Include the title and summary
+   - Update the "High-level structure" section if the unit count changes structural boundaries
+
+5. **Update related files:**
+   - Update `.manuscript/STATE.md` to reflect the new unit (status: pending)
+   - If PLOT-GRAPH.md (or adapted equivalent) exists, suggest adding the new unit to an arc position
+
+6. **Confirm to writer:**
+   - Show the updated outline structure with the new unit highlighted
+   - Display the new unit's number, title, and position
+</add_unit>
+
+Commit: `structure: add {unit_type} "{title}"`
+
+## Edge Cases
+
+- **No OUTLINE.md:** Prompt the writer to run `/scr:plan` first or `/scr:new-work` to initialize the project.
+- **Empty outline:** Add as the first unit (number 1).
+- **Work type with no mid hierarchy:** Use the atomic level instead (e.g., flash_fiction uses "beat").
+- **Title not provided:** Ask the writer for a title before proceeding.
+
+## 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
+
+Efficient and supportive. Adding a unit is a positive creative moment -- acknowledge it briefly without being effusive.

package/commands/scr/art-direction.md

@@ -0,0 +1,225 @@
+---
+description: Generate or refine the visual style bible for illustrations and cover art.
+argument-hint: "[--refine]"
+---
+
+# /scr:art-direction -- Visual Style Bible
+
+Generate or refine ART-DIRECTION.md, the visual style bible that governs all illustration and cover art for the project.
+
+## Usage
+```
+/scr:art-direction [--refine]
+```
+
+## Instruction
+
+You are creating the project's visual style bible. Load:
+- `.manuscript/config.json` (to get `work_type`, `genre`)
+- Scriveno's installed/shared `CONSTRAINTS.json` (global `~/.scriveno/data/CONSTRAINTS.json` or project `.scriveno/data/CONSTRAINTS.json`) (to check `commands.art-direction.available` and `commands.art-direction.hidden`)
+- `.manuscript/WORK.md` (genre, premise, tone, setting context)
+- `.manuscript/CHARACTERS.md` or `.manuscript/FIGURES.md` (per `file_adaptations` for sacred work types) for character physical descriptions
+- `.manuscript/WORLD.md` or `.manuscript/COSMOLOGY.md` (per `file_adaptations`) if it exists, for setting descriptions
+- `.manuscript/illustrations/ART-DIRECTION.md` if it exists (for refine mode)
+
+**Check availability:**
+
+Look up the current work type's group in CONSTRAINTS.json. If the group is in `commands.art-direction.hidden`, inform the writer:
+
+> Art direction is not available for [work_type] projects.
+
+Then **stop**.
+
+---
+
+### INITIAL MODE (no existing ART-DIRECTION.md)
+
+<art_direction_initial>
+  No visual style bible exists yet. Ask 3-4 seed questions to establish the visual identity:
+
+  1. **Art style:** "What visual style do you envision? (realistic, stylized, watercolor, ink, digital painting, minimalist, comic/graphic, mixed media, or describe your own)"
+
+  2. **Mood and tone:** "What's the visual mood? (warm and inviting, dark and atmospheric, bright and energetic, muted and contemplative, high-contrast dramatic, dreamy and ethereal)"
+
+  3. **Color preferences:** "Do you have any color preferences or palette direction? (warm earth tones, cool blues/grays, vibrant saturated colors, monochromatic, specific colors that represent the story)"
+
+  4. **Reference art or artists:** "Are there any artists, art styles, book covers, or visual references that capture the feel you want? (e.g., 'Moebius-style linework', 'Studio Ghibli palette', 'Edward Hopper lighting', or 'no specific reference')"
+
+  Wait for answers. Do not proceed until the writer responds.
+
+  After receiving answers, generate `.manuscript/illustrations/ART-DIRECTION.md` with the following sections:
+
+  ```markdown
+  # ART-DIRECTION
+
+  Visual style bible for [title from config.json].
+
+  ## Visual Style
+
+  [Art style direction based on seed answers. Describe the overall aesthetic: realistic, stylized, watercolor, ink, digital, etc. Include rendering approach, level of detail, and artistic intent.]
+
+  ## Color Palette
+
+  [Mood-based, season-based, or character-coded palettes with hex values.]
+
+  | Role | Color | Hex | Usage |
+  |------|-------|-----|-------|
+  | Primary | [color] | #XXXXXX | [main scenes, dominant mood] |
+  | Secondary | [color] | #XXXXXX | [supporting elements] |
+  | Accent | [color] | #XXXXXX | [highlights, focal points] |
+  | Shadow | [color] | #XXXXXX | [dark areas, contrast] |
+  | Highlight | [color] | #XXXXXX | [light sources, emphasis] |
+
+  ### Mood-Based Palette Variations
+  - **Tension/Conflict:** [palette shift]
+  - **Peace/Resolution:** [palette shift]
+  - **Mystery/Unknown:** [palette shift]
+
+  ## Composition Preferences
+
+  [Composition approach: dynamic, static, symmetrical, rule-of-thirds, golden ratio, diagonal, etc. Include framing preferences, depth of field approach, and perspective choices.]
+
+  - **Default framing:** [e.g., rule-of-thirds with subject off-center]
+  - **Action scenes:** [e.g., dynamic diagonals, motion blur]
+  - **Quiet moments:** [e.g., centered, symmetrical, breathing room]
+  - **Perspective:** [e.g., eye-level for intimacy, bird's-eye for scope]
+
+  ## Reference Artists / Styles
+
+  [Suggested reference artists matching the genre/mood from the writer's input and the work's tone.]
+
+  | Artist / Style | What to Reference | What to Avoid |
+  |----------------|-------------------|---------------|
+  | [artist/style] | [specific quality] | [specific quality] |
+
+  ## Per-Character Visual Specs
+
+  [Pulled from CHARACTERS.md / FIGURES.md. For each major character:]
+
+  ### [Character Name]
+  - **Appearance:** [physical description from character file]
+  - **Clothing/Style:** [wardrobe, accessories, signature items]
+  - **Expressions:** [default expression, emotional range to depict]
+  - **Color association:** [character-specific color from palette]
+  - **Visual motifs:** [recurring visual elements tied to this character]
+
+  ## Per-Setting Visual Specs
+
+  [Pulled from WORLD.md / COSMOLOGY.md if available. For each key setting:]
+
+  ### [Setting Name]
+  - **Lighting:** [natural, artificial, time of day, quality of light]
+  - **Atmosphere:** [clear, hazy, foggy, dust-filled, rain-soaked]
+  - **Key details:** [architectural style, vegetation, textures, materials]
+  - **Color temperature:** [warm, cool, neutral, mixed]
+  - **Mood:** [how this place should feel visually]
+
+  ## Consistency Rules
+
+  - **Object proportions:** [scale relationships, character heights relative to environment]
+  - **Recurring visual motifs:** [symbols, patterns, objects that appear across illustrations]
+  - **Typography style:** [if text appears in illustrations -- font family, weight, style]
+  - **Border/frame treatment:** [if illustrations use borders, vignettes, or full-bleed]
+  - **Negative space:** [approach to empty space in compositions]
+  ```
+
+  Populate each section using:
+  - Seed question answers for style, mood, color, and references
+  - CHARACTERS.md / FIGURES.md for per-character visual specs (physical descriptions, clothing, mannerisms)
+  - WORLD.md / COSMOLOGY.md for per-setting visual specs (locations, atmosphere, lighting)
+  - WORK.md genre and tone for overall aesthetic direction
+  - config.json work_type for genre-appropriate defaults
+
+  If CHARACTERS.md/FIGURES.md is empty or missing, include the Per-Character section with a note:
+  > No characters defined yet. Run `/scr:new-character` to add characters, then re-run `/scr:art-direction --refine` to update visual specs.
+
+  If WORLD.md/COSMOLOGY.md does not exist, include the Per-Setting section with a note:
+  > No world document found. Run `/scr:build-world` to create one, then re-run `/scr:art-direction --refine` to update setting specs.
+
+  Create the output directory if needed:
+  ```bash
+  mkdir -p .manuscript/illustrations
+  ```
+
+  Save to `.manuscript/illustrations/ART-DIRECTION.md`.
+
+  Commit: `art-direction: create visual style bible`
+
+  After saving, tell the writer:
+  > Your visual style bible is ready at `.manuscript/illustrations/ART-DIRECTION.md`. Other illustration commands (`/scr:cover-art`, `/scr:illustrate-scene`, `/scr:character-ref`) will reference this for visual consistency.
+  >
+  > To update any section: `/scr:art-direction --refine`
+</art_direction_initial>
+
+---
+
+### REFINE MODE (--refine or ART-DIRECTION.md exists)
+
+<art_direction_refine>
+  Load the existing `.manuscript/illustrations/ART-DIRECTION.md`.
+
+  Present a summary of current settings:
+  - Visual style
+  - Color palette (primary colors)
+  - Composition approach
+  - Number of characters with visual specs
+  - Number of settings with visual specs
+
+  Ask: "What would you like to update? (visual style, color palette, composition, references, character specs, setting specs, consistency rules, or describe what you want to change)"
+
+  After the writer responds:
+  1. Update the specified section(s) in ART-DIRECTION.md
+  2. Preserve all unchanged sections exactly as they are
+  3. If updating character specs, re-read CHARACTERS.md/FIGURES.md for latest data
+  4. If updating setting specs, re-read WORLD.md/COSMOLOGY.md for latest data
+  5. Save the updated file
+
+  Commit: `art-direction: refine [section updated]`
+</art_direction_refine>
+
+---
+
+### Prompt Output Format (D-01)
+
+All visual prompts generated or referenced by this style bible follow the structured format:
+
+- **Subject:** What is depicted (characters, objects, scene)
+- **Composition:** Framing, perspective, focal point, negative space
+- **Style:** Art style, rendering technique, level of detail
+- **Color Palette:** Dominant colors, mood colors, hex references from ART-DIRECTION.md
+- **Mood:** Emotional tone, atmosphere, time of day
+- **Technical Specs:** Dimensions, DPI, format requirements (when applicable)
+
+This format ensures prompts are copy-pasteable to any AI image generation tool (GPT Image, Stable Diffusion, Midjourney, etc.).
+
+---
+
+### Edge Cases
+
+- **Sacred work type:** Use FIGURES.md instead of CHARACTERS.md; use COSMOLOGY.md instead of WORLD.md. Adapt visual language for sacred art traditions (iconographic style, liturgical colors, sacred geometry)
+- **Work type hidden:** If work type group is in `commands.art-direction.hidden` (script, academic, poetry, speech_song), explain unavailability and stop
+- **No genre in config.json:** Ask the writer about visual mood directly rather than inferring from genre
+- **Existing ART-DIRECTION.md without --refine flag:** Detect existing file and enter refine mode automatically (no need to force --refine)
+
+## 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.

package/commands/scr/autopilot-publish.md

@@ -0,0 +1,210 @@
+---
+description: "Run full publishing pipeline unattended with quality gate (voice-check + continuity-check)."
+argument-hint: "--preset <preset> [--front-level <minimum|balanced|maximum|skip>] [--back-level <minimum|balanced|maximum|skip>]"
+---
+
+# /scr:autopilot-publish -- Unattended Publishing Pipeline
+
+You are running the full publishing pipeline autonomously. Your job is to run quality checks, auto-generate any missing prerequisites, execute the preset pipeline, and report results -- all without asking the writer questions.
+
+## Usage
+
+```
+/scr:autopilot-publish --preset <preset>
+```
+
+The `--preset` argument is **required**. There is no interactive mode in autopilot -- the writer must specify their destination upfront. Valid presets: `kdp-paperback`, `kdp-ebook`, `query-submission`, `ebook-wide`, `ingram-paperback`, `academic-submission`, `thesis-defense`, `screenplay-query`, `share-pdf`, `share-docx`, `share-epub`, `share-bundle`, `all-formats`, `submission-package`.
+
+`--front-level` and `--back-level` control how much front/back matter is generated when the preset includes those steps. Both default to **balanced** for retail and academic presets, **minimum** for share-* and all-formats, and **skip** for query-submission, screenplay-query, and submission-package (the package itself does not need book front/back matter). Pass `skip` to suppress the corresponding generation step entirely. The default is applied silently per the table below; the writer only needs to pass these flags to override.
+
+---
+
+## Instruction
+
+### STEP 0: BOOTSTRAP (context-cost protocol)
+
+Read `.manuscript/CONTEXT.md` first if it exists. If its `Updated` timestamp is newer than `.manuscript/STATE.md` and newer than the newest file in `.manuscript/drafts/body/`, use it as your orientation source for project title, work type, phase, current unit, recent activity, and open items. In STEP 1, skip the raw-file loads of `config.json`, `STATE.md`, and `OUTLINE.md` for those fields -- still load `CONSTRAINTS.json` (CONTEXT.md does not surface adaptation rules) and any specific files later steps need.
+
+If CONTEXT.md is missing, stale, or contradicts STATE.md, fall back to the original loads in STEP 1 unchanged. See `docs/context-protocol.md` for the contract.
+
+---
+
+### STEP 1: LOAD CONTEXT AND VALIDATE
+
+Load these project files:
+
+- `.manuscript/config.json` -- to get `work_type`, title, author
+- Scriveno's installed/shared `CONSTRAINTS.json` (global `~/.scriveno/data/CONSTRAINTS.json` or project `.scriveno/data/CONSTRAINTS.json`) -- to check `publishing_prerequisites` and export availability
+- `.manuscript/OUTLINE.md` -- to verify draft completeness
+
+**Validate preset:** Check that the `--preset` value matches a known preset name. If invalid:
+> Unknown preset "[value]". Available presets: kdp-paperback, kdp-ebook, query-submission, ebook-wide, ingram-paperback, academic-submission, thesis-defense, screenplay-query.
+
+Then **stop**.
+
+**Check draft completeness:** Verify all units in OUTLINE.md have corresponding draft files. If the draft is incomplete:
+> **Warning:** Manuscript is incomplete. Missing units: [list]. Proceeding with available content -- exported files will have gaps.
+
+Continue anyway (autopilot does not stop for incomplete drafts -- it warns and proceeds).
+
+---
+
+### STEP 2: QUALITY GATE (per D-09)
+
+Run quality checks before the export pipeline. The quality gate **warns but does not block** -- issues are logged for the writer to review after export completes.
+
+#### 2a. Voice Check
+
+Check if `.manuscript/STYLE-GUIDE.md` exists:
+
+- **If STYLE-GUIDE.md exists:** Run `/scr:voice-check` on the full manuscript. Capture the voice fidelity score and any issues found.
+- **If STYLE-GUIDE.md does not exist:** Skip voice check with a note:
+  > Voice check skipped -- no STYLE-GUIDE.md found. Run `/scr:profile-writer` to enable voice checking.
+
+#### 2b. Continuity Check
+
+Run `/scr:continuity-check` on the full manuscript. Capture any contradictions or inconsistencies found.
+
+#### 2c. Quality Gate Summary
+
+Show the quality gate results before proceeding:
+
+```
+Quality Gate
+============
+Voice check:      3 warnings (score: 82/100 PASS)
+Continuity check: 1 warning
+
+Proceeding with export. Review full reports after completion.
+```
+
+**Quality gate policy (D-09):** Always proceed to the export pipeline regardless of quality gate results. The quality gate is advisory -- it gives the writer information, not a veto. Even if voice check scores FAIL (below 60) or continuity check finds major contradictions, log the warnings and continue.
+
+---
+
+### STEP 3: GENERATE PREREQUISITES
+
+Auto-generate any missing prerequisites required by the chosen preset. Do not ask -- just generate them.
+
+**Prerequisites by preset:**
+
+| Preset | Needs |
+|--------|-------|
+| kdp-paperback | front-matter, back-matter |
+| kdp-ebook | front-matter, back-matter |
+| query-submission | blurb, synopsis, query-letter |
+| ebook-wide | front-matter, back-matter |
+| ingram-paperback | front-matter, back-matter |
+| academic-submission | (none) |
+| thesis-defense | front-matter, back-matter |
+| screenplay-query | blurb, synopsis, query-letter |
+| share-pdf | (none) |
+| share-docx | (none) |
+| share-epub | (none) |
+| share-bundle | (none) |
+| all-formats | (none) |
+| submission-package | synopsis, query-letter, back-matter |
+
+For each prerequisite the preset needs:
+
+| Prerequisite | Check | Generate Command |
+|-------------|-------|-----------------|
+| front-matter | `.manuscript/front-matter/` has files | `/scr:front-matter --level <resolved-front-level>` (resolve by `--front-level` or the per-preset default; if `skip`, do not run) |
+| back-matter | `.manuscript/back-matter/` has files | `/scr:back-matter --level <resolved-back-level>` (resolve by `--back-level` or the per-preset default; if `skip`, do not run) |
+| blurb | `.manuscript/output/blurb.md` exists | `/scr:blurb` |
+| synopsis | Any `.manuscript/marketing/SYNOPSIS-*.md` file exists | `/scr:synopsis` |
+| query-letter | `.manuscript/marketing/QUERY-LETTER.md` exists | `/scr:query-letter` |
+
+Show progress as each prerequisite is generated:
+
+```
+Generating Prerequisites
+========================
+Step 1/3: Generating front matter... done (7 elements)
+Step 2/3: Generating back matter... done (5 elements)
+Step 3/3: Cover art... already exists, skipping
+```
+
+---
+
+### STEP 4: RUN PRESET PIPELINE
+
+Execute the preset pipeline from `/scr:publish` (same pipeline definitions). Show progress for each step:
+
+```
+Export Pipeline: kdp-paperback
+===============================
+Step 1/2: Exporting print-ready PDF... done (manuscript-print.pdf, 312 pages)
+Step 2/2: Building KDP package... done (kdp-package/)
+```
+
+Run each export command in the preset's pipeline. If an export step fails (e.g., Pandoc not installed, Typst not found), log the error and continue to the next step if possible. Report all failures in the final summary.
+
+---
+
+### STEP 5: FINAL REPORT
+
+Show a complete summary of everything that happened:
+
+```
+Autopilot Publish Complete
+==========================
+Preset: kdp-paperback
+Duration: ~3 minutes
+
+Quality Gate:
+  Voice check:      3 warnings (score: 82/100 PASS)
+  Continuity check: 1 warning
+
+Generated Prerequisites:
+  - Front matter (7 elements)
+  - Back matter (5 elements)
+
+Exported:
+  - manuscript-print.pdf (interior, 6x9, ~312 pages)
+  - kdp-package/ (cover specs, metadata, upload checklist)
+
+Quality Reports:
+  - Voice check: .manuscript/full-VOICE-CHECK-REPORT.md
+  - Continuity check: .manuscript/FULL-CONTINUITY-REPORT.md
+
+Errors:
+  (none)
+
+Next Steps:
+  1. Review quality warnings in the reports above
+  2. Review the interior PDF at .manuscript/output/manuscript-print.pdf
+  3. Review `.manuscript/output/kdp-package/cover-specs.md` and place the finished print cover at `.manuscript/build/paperback-cover.pdf`
+  4. Upload to https://kdp.amazon.com
+```
+
+If any steps failed, show them in the "Errors" section with actionable fix instructions (e.g., "Pandoc not installed -- run `brew install pandoc` and re-run").
+
+---
+
+## 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
+
+Autopilot is the "set it and forget it" mode. Be concise in progress updates -- one line per step. Save the detail for the final report. The writer chose autopilot because they trust the pipeline and want results, not conversation.