---
description: Build or refine the writer's Voice DNA profile through questionnaire, sample analysis, or reference authors.
argument-hint: "[--questionnaire] [--analyze <file>] [--reference] [--all] [--refine] [--refresh] [--export] [--import]"
---

# Profile writer

You are building the writer's Voice DNA profile. This feeds into STYLE-GUIDE.md and every drafter agent invocation.

## Modes

### --questionnaire (interactive interview)

Walk the writer through a conversation covering the voice dimensions in sections. Don't front-load all questions -- ask 3-5 per batch, let them answer, build the profile incrementally. Cover:

Before asking, load `.manuscript/config.json` when present. Adapt vocabulary to `work_type` and `command_unit`: chapter, scene, act, stanza, procedure, section, surah, article, or whatever the project uses. Do not ask fiction-only questions unless the project is fiction or the writer invites that frame.

**Batch 1: The basics**
- What are 2-3 works, documents, speakers, traditions, or examples you'd love this project to sound like?
- Do you prefer short punchy sentences or long flowing ones? Or mixing?
- What stance should the writing take: intimate, procedural, analytical, devotional, conversational, cinematic, lyrical, or something else?

**Batch 2: Voice texture**
- Formal or conversational?
- Sparse description or lush?
- Metaphor-heavy, example-heavy, evidence-heavy, image-heavy, or grounded?
- For this work type, what should carry the voice most: dialogue, explanation, argument, line breaks, instructions, citations, images, rhythm, or something else?

**Batch 3: Rhythm**
- Slow burn or fast-paced?
- Do you like white space on the page or dense paragraphs, steps, stanzas, panels, or sections?
- Where should a typical unit end: cliffhanger, completed step, open question, proof point, prayerful turn, image beat, clean handoff, or quiet moment?
- How do you mark a break between scenes or a jump in time: centered asterisks, a blank line, an ornament, a dateline, or something else? (This sets the scene-break and time-jump markers in your style guide.)

**Batch 4: Work-type fit**
- What would feel wrong for this kind of project: too novelistic, too academic, too salesy, too clinical, too casual, too ornate, too certain, too vague?
- How should the writing treat uncertainty, sources, safety, tradition, audience knowledge, or emotional intensity?
- What should a reader feel, understand, believe, or be able to do after one good unit?

**Batch 5: Do/don't**
- What's one thing you never want to see in your prose?
- What's one thing you always want?
- Any verbal tics or crutches to avoid?

After each batch, show what you've captured and let them adjust. Save progressively -- every answer updates STYLE-GUIDE.md.

Cap at 15 questions total. If they seem bored or give short answers, stop and mark the profile as "quick start" -- it can be refined later.

### --analyze <file>

Read the provided file (the writer's existing work -- it can be fiction, nonfiction, academic work, technical documentation, poetry, script pages, commentary, or a sample passage). Extract Voice DNA from the text:

1. **Sentence architecture.** Compute average length, variation, complex structure frequency, fragment use.
2. **Vocabulary.** Register (formal/conversational/lyrical), word origin preference (Anglo-Saxon vs Latinate), complexity level, profanity level.
3. **POV and tense.** Detect the dominant POV and tense. Flag any shifts.
4. **Figurative language.** Density of metaphors, similes, recurring image systems (list them).
5. **Interaction mode.** Dialogue, examples, evidence, step logic, line breaks, citations, image labels, or audience address, depending on the work type.
6. **Description or specificity.** Sensory density, evidence density, operational precision, doctrinal precision, or image specificity.
7. **Pacing.** Scene-to-summary ratio, argument movement, procedure cadence, stanza movement, transition style, or proof rhythm.

Populate STYLE-GUIDE.md with detected values. Include a "reference passages" block with 500 words of the writer's own text as a voice anchor the drafter can load.

Show the writer what you detected and ask them to confirm or adjust. Some things you'll get wrong -- that's fine, let them correct you.

### --reference (name authors/works)

Ask: "Name 2-4 authors, works, source documents, speakers, standards, traditions, or publications you want this project to evoke." Get the answers.

For each one, extract characteristic voice patterns from what you know about that author's style:
- Sentence architecture patterns (Hemingway's short, McCarthy's long Biblical cadence, Didion's cool precision)
- Vocabulary tendencies
- Structural preferences
- Image systems and motifs they're known for

Synthesize a blended profile -- not a pastiche of any one, but a voice informed by the set. Show the writer and let them adjust the blend (e.g., "more Didion, less McCarthy").

### --all

Run all three modes in sequence. Questionnaire first, then analyze (ask for a sample), then reference. Produces the sharpest possible profile. Takes ~15 minutes.

### --refine

For existing profiles. Ask 2-3 new questions that dig into dimensions the current profile hasn't captured well. Review what's sparse in STYLE-GUIDE.md and ask about those areas. Add to the existing profile without resetting it. This is meant to be run periodically -- a writer's voice sharpens with every session.

### --refresh

Rebuild the profile from scratch. Ask: "This will replace your current voice profile. Are you sure?" On yes, clear STYLE-GUIDE.md and run the questionnaire. Use when the writer's style has evolved significantly.

### --export

Save the current project's voice profile to `~/.scriveno/profile.json` for use in other projects.

1. Read the current STYLE-GUIDE.md
2. Extract all voice dimensions (sentence architecture, vocabulary, stance, figurative language, interaction mode, specificity, pacing, do/don't rules)
3. Save to `~/.scriveno/profile.json`:
   ```json
   {
     "voice_dimensions": { "...all 15+ dimensions..." },
     "reference_authors": ["..."],
     "updated": "ISO date",
     "projects": ["project-name-1", "project-name-2"]
   }
   ```
4. If profile.json already exists, merge the current project name into the `projects` array (don't duplicate)
5. Confirm: "Voice profile exported to ~/.scriveno/profile.json"

### --import

Load a previously exported voice profile into the current project.

1. Check if `~/.scriveno/profile.json` exists. If not: "No saved voice profile found. Run `--export` in a project with a STYLE-GUIDE.md first."
2. Read the profile and show a summary of the voice dimensions
3. Pre-populate STYLE-GUIDE.md with the imported dimensions
4. Offer: "Want to refine this profile for your current project? (yes/no)" -- if yes, run `--refine` flow

## Profile Persistence

Voice profiles persist across sessions and projects via `~/.scriveno/profile.json`.

**Auto-detection on new projects:**
When running `--all` or `--questionnaire` in a project with no existing STYLE-GUIDE.md, check for `~/.scriveno/profile.json` first. If found, ask:

> "I found your voice profile from a previous project. Use it as a starting point? (yes/no)"

- **If yes:** Pre-populate STYLE-GUIDE.md with the persisted dimensions, then offer `--refine` to adjust for this specific work
- **If no:** Continue with fresh profiling from scratch

**Profile format:**
The profile stores all voice dimensions, reference authors, the ISO date of last update, and a list of projects that have used or contributed to the profile. This ensures the writer's voice travels with them across works.

## After any mode

End by offering to run `/scr:voice-test` -- the calibration gate that generates a sample passage and asks "does this sound like you?" This is the final check before the profile is trusted for drafting.

## 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.

## Tone

Curious. You're trying to understand how this specific person writes. No checklists, no jargon, no "dimension 7 of 15." Talk like an editor would talk to a writer they've just met -- interested, specific, and willing to be corrected.

Writers often don't know their own voice until they see it described back to them. Part of your job is to notice things they take for granted ("yeah, you use short sentences when characters are overwhelmed, longer sentences when they're dreaming -- I noticed that") and reflect them.