scriveno 2.0.5

package/commands/scr/character-arc.md

@@ -0,0 +1,108 @@
+---
+description: Visualize a character's emotional and growth arc across the story.
+argument-hint: "[name]"
+---
+
+# /scr:character-arc -- Character Arc Visualization
+
+Visualize a character's emotional and growth arc aligned with story structure beats.
+
+## Usage
+```
+/scr:character-arc <name>
+```
+
+## Instruction
+
+You are visualizing a character's arc. 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 check `file_adaptations` and `commands.character-arc.adapted`)
+- The adapted characters file (CHARACTERS.md / FIGURES.md / CONCEPTS.md per `file_adaptations`)
+- `PLOT-GRAPH.md` (story arc structure -- cross-reference per D-03)
+- `OUTLINE.md` (scene/chapter mapping)
+
+Determine adapted terminology from CONSTRAINTS.json:
+- Default: "character arc"
+- Sacred: "figure arc" (renamed via CONSTRAINTS.json)
+
+---
+
+### ARC VISUALIZATION
+
+<character_arc_display>
+  Find the character by name (case-insensitive match).
+
+  Read the character's arc data:
+  - Starting state (emotional/spiritual beginning)
+  - Arc type (Change, Growth, Fall, Steadfast, Flat/Catalytic)
+  - Turning points
+  - Ending state
+
+  **Cross-reference with PLOT-GRAPH.md (D-03):**
+  Map the character's transformation moments to story structure beats:
+
+  ```
+  STORY BEAT              | CHARACTER STATE        | EMOTIONAL LEVEL
+  ========================|========================|================
+  Status Quo              | {starting state}       | -----*---------
+  Inciting Incident       | {reaction/response}    | --------*------
+  First Plot Point        | {commitment/refusal}   | ----------*----
+  Rising Action           | {struggle/growth}      | -----------*---
+  Midpoint                | {mirror moment}        | ------*--------
+  All Is Lost             | {lowest point}         | --*------------
+  Climax                  | {transformation}       | -------------*-
+  Resolution              | {ending state}         | ----------*----
+  ```
+
+  For each story beat from PLOT-GRAPH.md:
+  1. Show the beat name and its position in the arc
+  2. Describe the character's emotional/psychological state at that point
+  3. Note if this beat corresponds to a character turning point
+  4. Show emotional trajectory direction (ascending, descending, steady, shift)
+
+  **Arc Summary:**
+  - Arc type: {type}
+  - Total turning points: {N}
+  - Key transformation moment: {which beat triggers the main change}
+  - Theme connection: {which thematic thread this arc serves}
+
+  If PLOT-GRAPH.md is missing or empty:
+  - Show the character's arc data standalone (start -> turning points -> end)
+  - Note: "Run `/scr:plot-graph` to create the story arc, then re-run this command to see how {name}'s arc aligns with story beats."
+
+  If the character has no arc data:
+  - "No arc defined for {name}. Run `/scr:character-sheet {name} --edit` to add arc information."
+</character_arc_display>
+
+---
+
+### Edge Cases
+
+- **Character not found:** Show partial matches or direct to cast-list
+- **PLOT-GRAPH.md missing:** Show character arc standalone with note to create plot graph
+- **Character has Flat/Catalytic arc:** Show how they affect other characters' arcs instead of personal transformation
+- **Multiple POV characters:** Show only the requested character; suggest running for each POV
+- **Sacred work type:** Align with theological arc positions instead of standard story beats
+
+## 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/character-ref.md

@@ -0,0 +1,160 @@
+---
+description: Generate a character visual reference sheet prompt for illustration consistency.
+argument-hint: "<name> [--style <style>]"
+---
+
+# /scr:character-ref -- Character Visual Reference Sheet
+
+Generate a structured visual reference sheet prompt for a character, suitable for AI image generation or illustrator briefs.
+
+## Usage
+```
+/scr:character-ref <name> [--style <style>]
+```
+
+## Instruction
+
+You are generating a character visual reference sheet prompt. 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 check `commands.character-ref`, `file_adaptations`, and `adapted`)
+- `ART-DIRECTION.md` from `.manuscript/` if it exists (for style consistency)
+
+### Work Type Adaptation
+
+Check CONSTRAINTS.json for work type availability:
+- **Available:** prose, script, visual, interactive
+- **Sacred:** Adapted to `figure-ref` (rename via `commands.character-ref.adapted.sacred.rename`)
+- **Hidden:** academic, poetry, speech_song
+
+If the current work type is hidden, respond:
+*"The `character-ref` command is designed for illustrated works. Your {work_type} project uses different visual tools."*
+
+If sacred work type, use "figure-ref" terminology throughout and adapt language accordingly (e.g., "figure reference sheet" not "character reference sheet").
+
+### Load Character Data
+
+Determine the correct characters file from `file_adaptations`:
+- Default: `.manuscript/CHARACTERS.md`
+- Sacred: `.manuscript/FIGURES.md`
+- Academic: `.manuscript/CONCEPTS.md` (though academic is hidden, handle gracefully)
+
+Load the adapted characters file.
+
+Find the character by name (case-insensitive match, same pattern as character-sheet.md):
+- If no exact match: check for partial matches and list them
+- If no matches at all: "No character named '{name}' found. Run `/scr:cast-list` to see all characters."
+- If characters file is empty or missing: "No characters found. Run `/scr:new-character <name>` to create your first character."
+
+### Extract Visual Details
+
+From the character's profile, extract:
+- **Physical appearance:** Height, build, skin tone, hair color/style, eye color, age appearance
+- **Distinguishing features:** Scars, tattoos, birthmarks, unusual traits, physical quirks
+- **Clothing:** Default outfit, armor, uniform, accessories -- whatever is described
+- **Props/Items:** Weapons, tools, jewelry, personal items associated with this character
+- **Emotional range:** Key emotional states mentioned in the character's psychology section (want, need, fear, arc)
+- **Body language:** Physical mannerisms tied to personality (posture, gait, gestures)
+
+### Generate Structured Prompt
+
+Output a structured illustration prompt following the D-01 format:
+
+```markdown
+# Character Visual Reference Sheet: {Character Name}
+
+## Subject
+{Full physical description in illustrator-ready language. Height, build, coloring, age appearance, distinguishing features. Be specific: "tall and lean, approximately 6'2", with deep brown skin, close-cropped silver hair, and a jagged scar running from left temple to jaw" -- not "a tall man with a scar."}
+
+## Poses
+- **Front view:** Full body, neutral standing pose, arms relaxed at sides
+- **3/4 view:** Slight turn showing depth and dimension of features
+- **Profile view:** Left or right profile highlighting facial structure
+- **Action pose:** {Character-appropriate action -- swordfighter in guard stance, scholar leaning over desk, etc.}
+
+## Expressions
+{Key emotional states derived from the character's arc and psychology}
+- {Expression 1}: {Description of facial expression and body language}
+- {Expression 2}: {Description}
+- {Expression 3}: {Description}
+{Typically 3-5 expressions: the character's default state, their emotional extreme, and states relevant to their arc}
+
+## Clothing & Attire
+- **Default outfit:** {Primary clothing described in detail -- fabrics, colors, fit, condition}
+- **Alternate outfit:** {If the character has described alternate clothing for different contexts}
+- **Accessories:** {Jewelry, belts, pouches, headwear, etc.}
+
+## Props & Items
+{Items associated with this character}
+- {Item 1}: {Visual description -- material, size, condition, how they carry/hold it}
+- {Item 2}: {Description}
+
+## Style
+{If ART-DIRECTION.md exists, reference its established visual style. Otherwise, derive from genre:}
+- Fantasy: detailed linework, rich color palette, painterly or concept art style
+- Literary fiction: realistic, muted palette, photographic reference quality
+- Sci-fi: clean lines, high contrast, concept art style
+- Children's: warm, rounded forms, bright palette, storybook illustration style
+- Sacred: reverent, iconographic traditions appropriate to the tradition
+{If --style flag provided, use that style instead}
+
+## Color Palette
+- **Skin:** {specific tone}
+- **Hair:** {specific color}
+- **Eyes:** {specific color}
+- **Primary clothing color:** {color}
+- **Accent colors:** {secondary colors from outfit/accessories}
+
+## Technical Specs
+- **Dimensions:** 2400 x 3200 px (character sheet format)
+- **Resolution:** 300 DPI (print-ready)
+- **Background:** Neutral gray (#808080) or transparent for compositing
+- **Format:** Reference sheet layout with multiple views on single page
+```
+
+### Save Output
+
+Save the generated prompt to:
+`.manuscript/illustrations/character-refs/{character-name}-ref.md`
+
+Where `{character-name}` is the lowercase, hyphenated version of the character's name (e.g., "Elena Vasquez" becomes "elena-vasquez").
+
+Create the directory path if it does not exist.
+
+Commit: `illustration: generate {character-name} visual reference sheet`
+
+After saving, suggest:
+- "Reference sheet prompt saved. Use this with any AI image tool or share with your illustrator."
+- "For style consistency across all illustrations, run `/scr:art-direction` first."
+
+---
+
+### Edge Cases
+
+- **Character has minimal physical description:** Generate the prompt with what exists, mark gaps with `{NEEDS DETAIL: describe height/build/etc.}` placeholders, and suggest the writer flesh out the character's appearance in their profile
+- **Multiple characters with similar names:** List matches and ask the writer to specify
+- **Sacred work type:** Use "figure-ref" command name and terminology; reference sheet language should be respectful and tradition-appropriate (avoid casual phrasing)
+- **ART-DIRECTION.md exists:** Style section MUST reference it for consistency; override genre defaults with art direction choices
+- **--style flag provided:** Use the specified style, note if it conflicts with ART-DIRECTION.md
+
+## 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/character-sheet.md

@@ -0,0 +1,143 @@
+---
+description: Display or edit a specific character's full profile.
+argument-hint: "[name] [--edit]"
+---
+
+# /scr:character-sheet -- View or Edit Character Profile
+
+Display or edit a specific character's complete profile.
+
+## Usage
+```
+/scr:character-sheet <name> [--edit]
+```
+
+## Instruction
+
+You are presenting a character's profile. 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 check `file_adaptations` and `commands.character-sheet.adapted`)
+- `STYLE-GUIDE.md` (voice dimension context)
+
+Determine the correct characters file from `file_adaptations`:
+- Default: `CHARACTERS.md`
+- Academic work types: `CONCEPTS.md`
+- Sacred work types: `FIGURES.md`
+
+Load the adapted characters file from `.manuscript/`.
+
+Determine adapted terminology from CONSTRAINTS.json:
+- Default: "character", "character sheet"
+- Sacred: "figure", "figure sheet"
+- Academic: "concept", "concept sheet"
+
+---
+
+### DISPLAY MODE (default)
+
+<character_sheet_display>
+  Find the character by name (case-insensitive match).
+
+  If no exact match found:
+  - Check for partial matches and list them: "Did you mean: [match1], [match2]?"
+  - If no partial matches: "No character named '{name}' found. Run `/scr:cast-list` to see all characters."
+
+  If the characters file is empty or missing:
+  - "No characters found. Run `/scr:new-character <name>` to create your first character."
+
+  Present the complete profile with all sections:
+
+  **Identity**
+  - Name, age, role, first impression, background
+
+  **Psychology**
+  - Want (conscious desire)
+  - Need (unconscious need)
+  - Lie (false belief)
+  - Ghost (formative backstory event)
+  - Fear (greatest fear)
+
+  **Arc**
+  - Starting state, turning point, ending state, arc type
+
+  **Voice Anchor (D-01)**
+  Highlight these 5-8 concrete attributes prominently:
+  1. Speech patterns (how they construct sentences)
+  2. Vocabulary register (formal, casual, slang, technical)
+  3. Sentence length tendency (short/punchy, long/flowing, mixed)
+  4. Verbal tics (repeated words, filler phrases, catchphrases)
+  5. Internal monologue style (if POV character)
+  6. Avoidances (words or topics they never use)
+  7. Emotional expression style (direct, deflecting, metaphorical)
+  8. Physical mannerisms tied to speech (gestures, pauses)
+
+  **5-Line Dialogue Sample**
+  - Show the voice anchor sample if it exists
+
+  **Persona Under Pressure**
+  - How the character behaves when afraid, angry, lying, avoiding truth, or vulnerable
+  - Physical tells that reveal pressure before the character admits anything
+
+  **Thematic Function**
+  - Themes embodied, narrative purpose
+
+  **Key Relationships**
+  - Each relationship with dynamic and tension
+
+  **Relationship-Specific Interactions**
+  - How this character changes with each important person: trust posture, conflict pattern, speech shift, hidden agenda or fear
+</character_sheet_display>
+
+---
+
+### EDIT MODE (--edit)
+
+<character_sheet_edit>
+  Find the character by name (same matching logic as display mode).
+
+  Walk through each section interactively:
+  1. Show the current value for each field
+  2. Ask: "Keep, change, or skip?"
+  3. If "change": accept the new value
+  4. Move to the next field
+
+  After all sections reviewed:
+  - Show a summary of changes
+  - Ask for confirmation
+  - Update the characters file
+  - If voice anchor attributes changed, note that drafter agents will use the updated profile
+
+  Commit: `character: update {name} profile`
+</character_sheet_edit>
+
+---
+
+### Edge Cases
+
+- **Character not found:** Show partial matches or direct to cast-list
+- **Multiple partial matches:** List all matches and ask writer to specify
+- **Empty characters file:** Direct to new-character command
+- **No voice anchor data:** Warn that voice consistency may suffer and suggest running `/scr:character-voice-sample` to generate one
+
+## 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/character-touch.md

@@ -0,0 +1,157 @@
+---
+description: Update a character's evolving state (emotional position, knowledge, possessions, relationships) after a unit lands.
+argument-hint: "<name> [--from <unit>]"
+---
+
+# /scr:character-touch -- Update Character State
+
+CHARACTERS.md (and FIGURES.md for sacred works) is a living document. Voice anchors and physical descriptions stay stable; emotional position, knowledge, possessions, and relationships move as the story unfolds. Without periodic touch-ups, the file freezes at character-creation time and the drafter ends up reading a stale "current emotional state" two-thirds of the way through the manuscript.
+
+This command is the touch-up surface. Use it after `/scr:draft` (especially when the drafter emits a CHARACTER STATE NUDGE), or any time you've written prose that visibly shifts a character.
+
+## Usage
+
+```
+/scr:character-touch <name>                  # interactive update
+/scr:character-touch <name> --from <unit>    # base the update on a specific unit's drafted prose
+```
+
+If `<name>` is omitted, list all characters from CHARACTERS.md and ask which to update.
+
+## 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 for orientation (project title, work type, current unit, recent activity). Step 1 still needs the full CHARACTERS.md (you will be editing it). See `docs/context-protocol.md` for the contract.
+
+### STEP 1: LOAD CONTEXT
+
+Load these project files:
+
+- `.manuscript/config.json` -- to determine work type (CHARACTERS.md vs FIGURES.md naming)
+- `.manuscript/CHARACTERS.md` (or `FIGURES.md` for sacred works) -- the file you will update
+- `.manuscript/STATE.md` -- to know which units have been drafted
+- The drafted unit file for the touch-up basis: `.manuscript/drafts/body/{N}-*-DRAFT.md` either for the unit named in `--from` or, if `--from` is omitted, the most recently modified draft file (the unit whose state shift is most likely fresh in the writer's mind)
+
+### STEP 2: RESOLVE THE CHARACTER
+
+If the writer named a character, find their entry in CHARACTERS.md by case-insensitive name match. If no match, suggest the closest names from the file and stop.
+
+If the writer did not name a character, list every character from CHARACTERS.md (one per line, with their voice anchor as a hint) and ask which to update.
+
+### STEP 3: PROPOSE A DELTA
+
+Read the basis draft file (from STEP 1). Identify what about this character has visibly shifted in this unit. Cover four dimensions; skip any that did not change:
+
+1. **Emotional position** -- where they are now vs where the file says they were (e.g. "from grieving to numb-determined")
+2. **Knowledge** -- what they learned this unit that they did not know before (or, less commonly, what they have forgotten or been deceived into believing)
+3. **Possessions** -- objects gained, lost, given, taken (e.g. "now carries the letter; left the coat behind")
+4. **Relationships** -- with whom, how shifted (e.g. "trust with Marcus broken; new alliance with Sarah forming")
+5. **Relationship-specific interaction** -- whether this unit changed how the character behaves with another person (speech shift, trust posture, conflict pattern, hidden agenda or fear)
+
+Present the proposed delta to the writer in this exact format:
+
+```
+Character: <name>
+Basis: <unit name from draft filename>
+
+Proposed updates to <NAME>'s entry in CHARACTERS.md:
+
+  Emotional position
+    was: <current text from CHARACTERS.md>
+    now: <proposed new text>
+
+  Knowledge gained
+    + <new knowledge bullet>
+    + <new knowledge bullet>
+
+  Possessions
+    + <gained>
+    - <lost or given>
+
+  Relationships
+    <other character>: <new state>
+
+  Relationship-specific interaction
+    <other character>: <new trust posture, conflict pattern, speech shift, hidden agenda or fear>
+
+Apply these updates? (yes / no / edit)
+```
+
+If the writer accepts (`yes`), proceed to STEP 4. If `edit`, ask which dimension to revise and re-prompt. If `no`, exit with no changes and no log entry.
+
+### STEP 4: APPLY THE DELTA
+
+Update the character's entry in `.manuscript/CHARACTERS.md` (or `FIGURES.md`):
+
+- **Replace** the existing "Emotional position" / "Current emotional state" line with the new value. If the entry has no such line, add it under the section the writer's character template uses for evolving state (look for "Current state", "Arc state", or just append to the end of the entry).
+- **Append** new knowledge bullets under a "Knowledge" subsection (create the subsection if absent).
+- **Append** possession changes under a "Possessions" subsection (create the subsection if absent), with `+` for gained and `-` for lost.
+- **Update or append** relationship lines under a "Relationships" subsection (create the subsection if absent).
+- **Update or append** pairwise behavior under a "Relationship-specific interactions" subsection (create the subsection if absent).
+
+**Do not touch:**
+- The character's voice anchor (this is identity, not state -- voice changes are a separate craft decision and need a different command)
+- Their physical description (height, eye color, distinguishing features -- those are stable unless the prose explicitly changed them, in which case treat as a Knowledge or Possession entry: "lost left arm in chapter 12")
+- Their name, age-at-introduction, or backstory section
+
+Preserve the file's existing formatting and section order.
+
+### STEP 5: STAMP THE UPDATE
+
+Add a one-line "Last touched" marker under the character's entry:
+
+```
+_Last touched: {ISO timestamp} -- after drafting <unit name>_
+```
+
+If a Last-touched line already exists, replace it.
+
+### STEP 6: HISTORY LOG
+
+Append one line to `.manuscript/HISTORY.log` per `docs/history-protocol.md`:
+
+```
+{ISO timestamp} | scr:character-touch | character=<name> | basis=<unit name> | dimensions=<comma-separated list of changed dimensions> | outcome=ok
+```
+
+If the writer chose `no` and exited with no changes, do not append a line. Touch-ups that go nowhere are not state events.
+
+### STEP 7: SUGGEST NEXT
+
+End with a one-line suggestion:
+
+> Updated <name>. The next `/scr:draft` invocation will read the new state. Consider running `/scr:scan` if multiple characters drifted in this unit.
+
+## 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
+
+Brisk and editorial. The writer just finished a draft; they're in flow. Surface the proposed delta, get a yes / no / edit answer, apply, get out. Do not narrate. Do not ask follow-up questions beyond the delta confirmation.
+
+## What this command is not
+
+- **Not a re-write of the character's profile.** Use `/scr:new-character` to start fresh, `/scr:character-sheet <name>` to view, this command to update evolving state.
+- **Not an arc analysis.** Use `/scr:character-arc <name>` to see the trajectory across units.
+- **Not automatic.** This command exists because automatic state updates risk silently overwriting the writer's intentional choices. The writer is always in the loop on a character's state.

package/commands/scr/character-voice-sample.md

@@ -0,0 +1,111 @@
+---
+description: Generate a dialogue sample to preview a character's voice before drafting.
+argument-hint: "[name]"
+---
+
+# /scr:character-voice-sample -- Preview Character Voice
+
+Generate a dialogue sample to preview how a character sounds before drafting scenes with them.
+
+## Usage
+```
+/scr:character-voice-sample <name>
+```
+
+## Instruction
+
+You are generating a voice sample for a character. 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 check `file_adaptations`, `commands.character-voice-sample.adapted`, and `feature_prerequisites`)
+- `STYLE-GUIDE.md` (writer's voice dimensions -- the sample must feel like this writer's prose)
+
+Determine the correct characters file from `file_adaptations`:
+- Default: `CHARACTERS.md`
+- Academic work types: `CONCEPTS.md`
+- Sacred work types: `FIGURES.md`
+
+Load the adapted characters file from `.manuscript/`.
+
+**Prerequisites check** (from CONSTRAINTS.json `feature_prerequisites`):
+- The characters file must exist with at least one character entry
+- `STYLE-GUIDE.md` must exist
+- If either is missing: "This command requires {missing_file}. Run {generator_command} first."
+
+Determine adapted terminology:
+- Default: "character voice sample"
+- Sacred: "register sample" (renamed via CONSTRAINTS.json)
+- Academic: "concept voice" (adapted tone)
+
+---
+
+### GENERATE VOICE SAMPLE
+
+<voice_sample_generation>
+  Find the character by name (case-insensitive match).
+
+  Read the character's existing profile, focusing on:
+  - Voice anchor attributes (speech patterns, vocabulary register, sentence length, verbal tics, internal monologue style)
+  - Speech patterns section (register, tics, vocabulary, sentence length, avoidances)
+  - Persona under pressure (how fear, anger, lying, or vulnerability change the voice)
+  - Relationship-specific interactions (the character may sound different depending on who they are speaking to)
+  - Psychology (want, need, lie -- these shape HOW they speak)
+  - Key relationships (they may speak differently to different people)
+
+  Generate exactly 5 lines of dialogue that showcase:
+  1. Their vocabulary register and sentence length
+  2. At least one verbal tic or catchphrase
+  3. Their emotional expression style
+  4. A moment of subtext (saying one thing, meaning another)
+  5. Their unique rhythm distinct from other characters
+
+  Include brief stage direction / action beats between lines to ground the dialogue in physical reality:
+  ```
+  "[Dialogue line 1.]" Character does something physical.
+
+  "[Dialogue line 2.]" Brief internal beat or reaction.
+
+  "[Dialogue line 3.]" Action or gesture.
+
+  "[Dialogue line 4.]" Beat.
+
+  "[Dialogue line 5.]"
+  ```
+
+  After presenting the sample, ask:
+  - "Does this sound like {name}? You can:"
+  - **Approve** -- save this as the voice anchor in the characters file
+  - **Adjust** -- tell me what to change (too formal, needs more humor, wrong tic, etc.)
+  - **Regenerate** -- try a completely fresh sample
+</voice_sample_generation>
+
+---
+
+### Edge Cases
+
+- **Character has no voice data yet:** Generate based on psychology and role, then note the sample is speculative and should be refined
+- **Character not found:** Show partial matches or direct to cast-list
+- **STYLE-GUIDE.md missing:** Warn that voice consistency cannot be verified without the style guide
+- **Sacred work type:** Use "register sample" terminology; voice attributes map to sacred registers (prophetic, wisdom, legal, etc.)
+
+## 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.