narrative-design

What this skill does

# Narrative Design

**Purpose:** Tools for designing narrative as a functioning game system — quests, branching stories, dialogue, and environmental storytelling that interact with mechanics rather than sitting alongside them. Narrative is how mechanics acquire meaning. This skill treats it with the same structural rigor as combat or economy.

**Position in workflow:** Narrative design interacts with nearly every other system. Use **game-vision** to establish core fantasy and pillars first. Then use this skill to design quests, story structure, and dialogue that serve those pillars. Fan out to **encounter-design** for spatial narrative, **economy-design** for reward flow, and **motivation-design** for retention psychology.

---

## When to Activate

Use this skill when:
- Designing quest systems, quest chains, or quest types
- Structuring branching dialogue or story paths
- Narrative feels disconnected from gameplay — players skip cutscenes or ignore lore
- Story contradicts mechanics (ludonarrative dissonance)
- Quests feel like checklists rather than journeys
- Designing environmental storytelling for levels or world areas
- Players can't explain what they're doing or why in fiction terms
- NPC dialogue feels flat, repetitive, or inconsequential
- Planning how narrative should interact with economy, progression, or combat systems
- Evaluating narrative pacing relative to gameplay intensity

---

## Core Principle: Narrative as System

Narrative is not a layer on top of mechanics. It is a system that interacts with other systems.

### System Interactions

Quests and story interact with every major game system:

| System | Interaction | Example |
|--------|------------|---------|
| **Economy** | Quest rewards flow through currency/item systems | Quest reward is crafting materials, not a unique item that bypasses the economy |
| **Progression** | Quests grant XP, unlock abilities, gate content | Story progression unlocks gameplay progression (new area = new abilities) |
| **Encounter design** | Quests create encounter context | "Defend the village" reframes the same combat encounter with stakes |
| **Social systems** | Quests build NPC relationships, faction standing | Choosing a faction in a quest closes doors with the opposing faction |
| **Exploration** | Quests motivate traversal, reward discovery | Investigation quests turn exploration from wandering into purpose |

### The Context Principle

Story creates CONTEXT that makes mechanical actions meaningful.

- Collecting 10 herbs is a checklist.
- Collecting 10 herbs because the village is dying of plague gives the same mechanic emotional weight.
- The mechanic is identical. The experience is transformed.

Context is the cheapest way to increase perceived value of existing mechanics. Before adding new systems, ask: can narrative context make what we already have feel more meaningful?

### The Dissonance Test

If the story says one thing and the mechanics reward another, players follow the mechanics and resent the story. This is non-negotiable.

| Story Says | Mechanics Reward | Result |
|-----------|-----------------|--------|
| "Peace is the answer" | Combat XP is the fastest progression | Players kill everything and mock the pacifist theme |
| "Time is running out" | No actual time pressure | Players explore leisurely and lose immersion |
| "This choice matters" | Both paths lead to identical outcomes | Players feel deceived and disengage from future choices |
| "You are a lone wanderer" | Optimal play requires a full party | Fantasy is broken by mechanical requirement |

**Rule:** When story and mechanics conflict, either change the story or change the mechanics. Never leave the conflict and hope players won't notice. They will.

Narrative is the bridge between Fiction and Mechanics in the Experience Triangle (see **experience-design**). When that bridge is broken, the triangle collapses.

---

## Quest Structure Patterns

Common quest types, their strengths, and how to subvert their weaknesses:

| Type | Structure | Strength | Weakness | Subversion Technique |
|------|-----------|----------|----------|---------------------|
| **Fetch/Gather** | Go to X, collect Y, return | Simple, teaches exploration | Repetitive, no decisions | Destination is dangerous, or the item has a moral cost |
| **Escort** | Protect NPC from A to B | Creates tension, attachment | Frustrating AI, pacing loss | Give the NPC agency — they help you, not just follow |
| **Investigation** | Gather clues, reach conclusion | Engages reasoning, rewards attention | Can stall if clues are missed | Multiple valid conclusions from the same evidence |
| **Combat Challenge** | Defeat X enemies/boss | Tests core combat skills | Can feel arbitrary | Combat with constraints — protect something, time limit, limited resources |
| **Puzzle** | Solve environmental/logical challenge | Mental engagement, "aha" moments | Can block progress permanently | Escalating hint system, multiple solution paths |
| **Social/Dialogue** | Navigate conversation, build relationships | Character depth, emotional engagement | Can feel passive | Dialogue as mechanic — what you say has gameplay consequences |

### The Combination Principle

The best quests combine 2-3 types. A pure fetch quest is boring. A fetch quest that requires investigation to find the item and combat to retrieve it is a journey.

**Design rule:** When a quest uses only one type, it is a task. When it layers types, it becomes a story. Aim for at least two types per non-trivial quest.

### Quest Pacing Within a Chain

A quest chain should vary its types across entries:

```
Quest 1: Investigation (low intensity, learn the stakes)
Quest 2: Fetch + Combat (rising action, resource gathering under pressure)
Quest 3: Social/Dialogue (emotional beat, key NPC relationship)
Quest 4: Escort + Combat (climax, protect what you've built)
Quest 5: Choice (resolution, player decides outcome)
```

Repeating the same type across a chain is the fastest way to make players lose interest.

---

## Quest as System Interaction

Quests should stress multiple game systems to create depth and meaningful decisions.

### The System Touch Test

For every quest, ask: which systems does this quest touch?

| Systems Touched | Assessment | Example |
|-----------------|------------|---------|
| 1 system | Shallow — task, not quest | "Kill 10 wolves" (combat only) |
| 2 systems | Adequate — functional quest | "Kill wolves threatening the farm, choose reward" (combat + economy) |
| 3+ systems | Rich — memorable quest | "Track wolves to their den (exploration), fight the alpha (combat), discover they were fleeing something worse (narrative hook), choose whether to report to the farmer or the ranger (faction + economy)" |

### Reward Flow

Quest rewards should flow THROUGH the economy system, not bypass it.

- **Good:** Quest rewards currency, materials, or items that participate in crafting/trading
- **Bad:** Quest rewards a unique sword that is simply better than anything available — this creates inflation and undermines the economy's role
- **Exception:** Milestone rewards (end of major quest chains) can be unique, but should be rare enough that they don't devalue the economy loop

**Principle:** If quest rewards are the best way to get everything, the economy system is dead. Rewards should supplement the economy, not replace it.

### Quest Design Checklist

- [ ] Which systems does this quest touch? (Target: 2+)
- [ ] Do rewards flow through the economy system?
- [ ] Does the quest use more than one quest type?
- [ ] Is there at least one meaningful decision?
- [ ] Does the narrative context make the mechanical task feel purposeful?
- [ ] Does the quest teach the player something about a game system?

---

## Branching Narrative Architecture

How to structure player choice in story at a sustainable scale.

| Architecture | Structure | Complexity | Replayability | Best For |
|-------------|-----------|-----------|--------