---
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 `dependencies.feature_prerequisites`)
- `docs/surface-resolution-protocol.md` for adapted cast surface resolution
- `STYLE-GUIDE.md` (writer's voice dimensions -- the sample must feel like this writer's prose)

Determine the adapted cast surface for canonical `CHARACTERS.md` from `file_adaptations`:
- Default: `CHARACTERS.md`
- Academic work types: `CONCEPTS.md`
- Technical work types: `AUDIENCE.md`
- Sacred work types: `FIGURES.md`

Load the adapted cast surface from `.manuscript/`.

**Prerequisites check** (from CONSTRAINTS.json `dependencies.feature_prerequisites`):
- The adapted cast surface must exist with at least one 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 adapted cast surface
  - **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.

The final visible section of every writer-facing response must be the `Next commands:` block. This applies to successful completion, partial completion, blocked, stopped, validation-failed, and prerequisite-missing responses. Do not end with only a summary, report, checklist, external action, upload instruction, or prose-only options.

Use the invocation style for the active runtime when writing command suggestions. Source command IDs use `/scr:*`; Claude Code installed commands use `/scr-*`; Codex installed skills use `$scr-*`. Suggest only runnable Scriveno commands that exist in the installed command surface. Do not invent adjacent workflow names.

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.