---
description: Write a scene, passage, or chapter outside the full planning workflow.
argument-hint: "[--discuss] [--research] [--full]"
---

# /scr:quick-write -- Ad-Hoc Writing Without Full Planning

Write a scene, passage, or chapter outside the full planning workflow.

## Usage
```
/scr:quick-write [--discuss] [--research] [--full]
```

**Flags:**
- `--discuss` -- Brief discussion to capture creative direction first
- `--research` -- Research craft techniques before drafting
- `--full` -- Discussion + research + consistency check

## Instruction

Quick write is the fast path. It loads STYLE-GUIDE.md, drafts in the current conversation context (not a fresh per-unit context), and commits atomically. It runs continuity and voice checks only when you pass `--full`. For voice-critical work, prefer `/scr:draft`, which drafts each unit in a fresh context and always runs a voice-check.

### STEP 1: GATHER INTENT

Ask: "What do you want to write?"

Accept any of:
- A specific scene ("The bar fight in chapter 12")
- A character moment ("Marcus confronting his father")
- An exploratory passage ("What it feels like when the magic fails")
- A dialogue exchange ("The negotiation between Eva and the detective")
- A transitional passage ("Getting from the apartment to the airport")

### STEP 2: QUICK CONTEXT

Load relevant files based on characters/settings mentioned:
- `STYLE-GUIDE.md` (always)
- `CHARACTERS.md` (relevant entries)
- `WORLD.md` (relevant sections)
- Previous relevant drafts (for continuity)

If `--discuss`: Ask 3-5 targeted questions about tone, pacing, and purpose for this passage.

If `--research`: Spawn a focused researcher for technique guidance.

If the host runtime cannot spawn a focused researcher, run the research pass in an isolated fresh context and report `prompt-run fallback used` in the status block.

### STEP 3: DRAFT

Write the passage following all established style guide constraints. Target whatever length feels natural unless the writer specified a target.

Quick-write drafts in the current conversation context rather than spawning the drafter in a fresh per-unit context; this trades some voice isolation for speed. When fresh-context voice fidelity matters, use `/scr:draft` instead.

### STEP 4: VERIFY (if --full)

Run continuity and voice checks against existing manuscript.

### OUTPUT

Save to `.manuscript/quick/{NNN}-{slug}/DRAFT.md`
Save plan (if generated) to `.manuscript/quick/{NNN}-{slug}/PLAN.md`

Commit: `quick: {slug}`

## Agent and Automation Status

Every response must include a short status block that makes invocation visible:

```text
Agent status:
Trigger: /scr:quick-write {flags}
Spawned agents:
- researcher: yes/no
Local operations:
- context files loaded: {count}
- draft file written: yes/no
- plan file written: yes/no
Auto-invoked:
- /scr:continuity-check: yes/no
- /scr:voice-check: yes/no
Why: --full runs verification after drafting; --research spawns a focused technique pass
```

In default mode, report `researcher: none` and both auto-invoked checks as `no`.

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