# Getting Started with Scriven

Go from zero to a drafted scene in under 10 minutes. This guide walks you through installation, project setup, and your first draft.

Want evidence first? Start with [Proof Artifacts](proof-artifacts.md). The watchmaker sample flow and the Voice DNA before/after bundle give you the fastest way to inspect what Scriven actually proves today.

## Prerequisites

- **An AI coding agent** -- Claude Code, Cursor, Gemini CLI, or another current Scriven installer target
- **Node.js >=20.0.0** -- needed for the installer only. For new installs, use a currently supported LTS such as Node.js 24.
- That's it. No other dependencies for the core writing workflow.

Before choosing a runtime, check [Runtime Support](runtime-support.md) for the current installer targets, install types, support levels, and verification status.

## Step 1: Install Scriven

Run the installer in your terminal:

```
npx scriven-cli@latest
```

This installs Scriven into the runtime you choose. Command-directory and skills targets place files where the runtime expects them. Guided targets like Perplexity Desktop instead write setup assets and show the exact connector steps you need. Takes about 30 seconds.

Once installed, Claude Code uses flat `/scr-*` commands such as `/scr-help` and `/scr-new-work`. Other command-directory runtimes currently keep `/scr:*`. Codex uses generated `$scr-*` skills such as `$scr-help` and `$scr-new-work`. Guided targets explain their supported setup path directly in the generated setup files.

## Step 2: Explore the Demo (Optional)

Not sure what Scriven does? Try the demo before starting your own project:

Claude Code:

```
/scr-demo
```

Codex:

```
$scr-demo
```

This creates a pre-built short story project -- a retired watchmaker who receives a letter from a daughter he never knew. The demo includes:

- 4 fully drafted scenes with distinct voice and style
- A complete voice profile (STYLE-GUIDE.md)
- Character files, plot graph, and thematic threads
- Editor notes on one scene so you can see the revision workflow
- 1 planned-but-undrafted scene so you can watch the drafter work

Explore at your own pace. When you're ready to start your own work, run `/scr-demo --clear` to clean up.

If you want a curated reading path instead of jumping straight into the demo files, open [Proof Artifacts](proof-artifacts.md) first. It maps the watchmaker sample to the exact files worth inspecting.

## Step 3: Start Your Project

Create a new writing project:

Claude Code:

```
/scr-new-work
```

Codex:

```
$scr-new-work
```

Scriven asks just 3 questions -- what you're writing, your premise, and whether you have existing material. That's it. No long setup forms, no configuration wizards.

From your answers, Scriven generates your project structure:

```
.manuscript/
  WORK.md          -- your project's identity
  OUTLINE.md       -- structure and unit breakdown
  RECORD.md        -- what the work has established
  STYLE-GUIDE.md   -- your Voice DNA profile
  CHARACTERS.md    -- cast and voice anchors
  THEMES.md        -- thematic threads
  PLOT-GRAPH.md    -- story arc and beats
  STATE.md         -- workflow position tracker
  config.json      -- project settings
```

Every file adapts to your work type. Writing a screenplay? You get acts and scenes. A research paper? Sections and argument maps. A runbook? Procedures and system maps. A Quran commentary? Surahs and doctrinal frameworks. Scriven supports 50 work types with tradition-native vocabulary.

## Step 4: Calibrate Your Voice

Before you draft anything substantial, turn the STYLE-GUIDE template into a real voice profile:

Claude Code:

```
/scr-profile-writer
```

Codex:

```
$scr-profile-writer
```

This interview builds your Voice DNA from your preferences, reference works, or a writing sample. When it finishes, run:

Claude Code:

```
/scr-voice-test
```

Codex:

```
$scr-voice-test
```

That calibration pass writes a short sample and lets you say what sounds right or wrong before Scriven starts drafting real units.

## Step 5: Develop Your Story

Before drafting, shape your ideas:

Claude Code:

```
/scr-discuss
```

Codex:

```
$scr-discuss
```

This opens a collaborative conversation where you and the AI work through the creative decisions for your next unit -- pacing, voice, character dynamics, what to include, what to avoid. Scriven picks the 3-4 most relevant questions for your specific scene rather than running through a checklist.

Your decisions get saved to a context file that the drafter will use. Think of this as giving the drafter its marching orders.

If you already refined your voice profile, you can also skip this step and draft with the defaults you've approved.

## Step 6: Write Your First Draft

Draft your first unit:

Claude Code:

```
/scr-draft
```

Codex:

```
$scr-draft
```

The drafter loads your Voice DNA (STYLE-GUIDE.md) and writes in your voice, not generic AI prose. Each atomic unit (scene, beat, passage) is drafted in a fresh context to prevent voice drift and keep quality consistent across the entire work.

After drafting, Scriven runs a voice-check pass to flag anything that drifted from your established style. You'll see a summary like: "Drafted Chapter 1: 2,400 words across 3 scenes. Voice consistency: 94%."

Your draft files appear in `.manuscript/` ready for you to read and revise.

## What's Next

Not sure what to do? There's one command that always knows:

Claude Code:

```
/scr-next
```

Codex:

```
$scr-next
```

`/scr-next` reads your project state and runs the right next step automatically. A writer who only ever types `/scr-next` in Claude Code can complete an entire manuscript from start to finish.

Beyond the core workflow, Scriven offers:

- **Revision** -- `/scr-editor-review`, `/scr-line-edit`, `/scr-continuity-check`
- **Publishing** -- `/scr-publish`, `/scr-export`, `/scr-cover-art`, `/scr-blurb`
- **Collaboration** -- `/scr-track` for revision tracks (`create`, `compare`, `merge`, `propose`)
- **Versions** -- `/scr-save`, `/scr-history`, `/scr-versions`, `/scr-compare`
- **Navigation** -- `/scr-help`, `/scr-next`, `/scr-pause-work`

For the full command list, see [Command Reference](command-reference.md).

If you want the trust surfaces around installation and shipping details, continue with:

- [Runtime Support](runtime-support.md) -- installer targets, support levels, and verification status
- [Shipped Assets](shipped-assets.md) -- what the npm package actually includes on the trust-critical surface
- [Release Notes](release-notes.md) -- what changed in the latest package release