Story Engineer

---
name: story-engineer
description: Use when transforming evidence-rich project histories, case studies, launches, research journeys, or retrospectives into truthful narrative structures. Not for inventing greenfield brand concepts from sparse briefs.
author: J StaR Films / Takomi
coauthored: J StaR Films / Takomi
version: 2.0.0
---

# Story Engineer

Turn real events, artifacts, decisions, and outcomes into a compelling interface narrative without inventing drama or forcing every project through the same arc.

## Applicability

Use this skill when the material contains a meaningful transformation, investigation, trial, construction process, consequence, or sequence of discoveries.

For a sparse request such as “make a website for this business,” use a creative-direction workflow instead. A category name is not a project history.

## 1. Build the Evidence Ledger

Extract:

- Events and their actual order.
- Decisions and known causes.
- Artifacts that can be shown.
- Claims and their support.
- Accurate metrics that materially change understanding.
- Unknowns requiring confirmation.

Keep facts, interpretations, and unknowns distinguishable. Do not invent failures, competitions, milestones, quotations, metrics, or turning points.

### Completion Gate

- [ ] Narrative claims trace to supplied evidence.
- [ ] Missing facts remain visible.

## 2. Identify the Narrative Engine

Choose the real source of motion:

- Transformation
- Investigation
- Trial
- Construction
- Reframing
- Consequence

State it in one sentence. Use a contradiction or driving question only when the evidence earns it.

### Completion Gate

- [ ] The engine describes actual change or discovery.
- [ ] The proposed conclusion can answer it honestly.

## 3. Choose the Shape

Select among chronological, question-and-evidence, problem-attempt-resolution, artifact-first reconstruction, parallel comparison, or thematic chapters.

Protect a reveal only when early disclosure would weaken genuine discovery. Keep products, services, prices, locations, and primary actions available when visitors need them.

### Completion Gate

- [ ] Structure follows evidence rather than a fixed beat sheet.
- [ ] Essential utility is not sacrificed for suspense.

## 4. Construct the Rail

For every beat, specify:

1. Evidence introduced.
2. Question answered.
3. New understanding created.
4. Emotional register earned.
5. Artifact or data carrying the beat.
6. Any withheld information and the reason.

Remove beats that do not advance understanding, emotional context, or visitor action.

### Completion Gate

- [ ] Every beat changes what the visitor knows, feels, or can do.
- [ ] The ending resolves the narrative engine.

## 5. Translate into Interface

Define content, composition, optional visual metaphor, interaction, transition, and persistent utility for each beat. Prefer real artifacts over invented spectacle.

Use cinematic choreography only when time-based progression is essential. Editorial and utility-led narratives are equally valid.

For extended pattern vocabulary, consult [references/narrative-patterns.md](references/narrative-patterns.md). For physicalizing genuinely abstract evidence, consult [references/visual-metaphors.md](references/visual-metaphors.md). Treat [references/examples.md](references/examples.md) as historical examples, not reusable scripts.

### Final Gate

- [ ] Every claim and beat remains evidence-backed.
- [ ] The structure would change if the source material changed.
- [ ] Interaction deepens evidence rather than decorating it.
- [ ] Accessibility and essential visitor utility remain complete.