---
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`)
- `docs/surface-resolution-protocol.md` for adapted cast surface resolution
- `STYLE-GUIDE.md` (voice dimension context)

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/`.

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 adapted cast surface is empty or missing:
  - "No cast entries found. Run `/scr:new-character <name>` to create your first entry."

  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 adapted cast surface
  - 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 adapted cast surface:** 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.

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.