---
name: writers-room-story-engine
description: Writers Room Story Engine mega-skill. Creates, structures, drafts, and revises compelling standalone stories from zero using premise generation, audience engagement, thematic design, character arcs, Story Spine structure, causal beats, worldbuilding in service of story, scene construction, and revision diagnostics. Use when developing short stories, standalone fiction, scripts, or narrative concepts from scratch or when improving weak drafts.
---

# Writers Room Story Engine – Mega Skill

Use this skill to create strong standalone stories from nothing or to repair stories that are weak.

This skill is designed for:
- short stories
- standalone fiction
- world-accompanying stories
- scripts or narrative concepts
- stories starting from zero with no premise, no world, and no characters
- improving flat, episodic, confusing, or emotionally weak drafts

This is a complete story system, not just an outline template.

A compelling story needs:
- a reason for the audience to care
- a meaningful story core
- a protagonist under pressure
- clear stakes
- a causal chain of events
- scenes that change the situation
- a climax that tests the core truth
- an ending that feels earned

This skill should think like a story architect first and a prose writer second.

When starting from zero, do not jump directly into prose. First build:
1. the seed
2. the story core
3. the protagonist engine
4. the Story Spine
5. the major beats
6. the story-supportive world details
7. the scenes
8. the draft
9. the revision pass

## Core operating model

This skill works through 7 engines:

### 1. Audience engine
Always ask:
- why should the audience care?
- what promise is being made?
- what curiosity, dread, wonder, desire, or tension keeps them leaning forward?

### 2. Story core
Find:
- the essence of the story
- the thematic tension
- the ending
- why this story matters

### 3. Character engine
Build:
- want
- need
- lie
- ghost
- spine
- comfort zone
- opposite pressure
- stakes

### 4. Plot engine
Use:
- Story Spine
- therefore/but causality
- escalation through consequence
- simplification and focus

### 5. Scene engine
Each scene should:
- involve desire
- meet resistance
- create change
- reveal character through action
- lead to the next scene via therefore or but

### 6. World engine
Worldbuilding should:
- create friction
- shape choices
- create taboo, law, class, danger, obligation, scarcity, or value conflict
- support the protagonist’s struggle

### 7. Rewrite engine
After drafting:
- discover the real theme
- reject obvious choices
- repair passivity
- sharpen causality
- cut detours
- strengthen climax and ending

## Non-negotiable principles

- Make the audience care.
- Know the ending before building the middle.
- Theme often becomes fully visible in rewrite.
- Prefer therefore/but over and then.
- Let the audience infer.
- Simplify aggressively.
- Coincidence may create trouble but should not solve the story.
- Pressure reveals character.
- Worldbuilding exists to create conflict and consequence.
- If a scene does not turn, it is weak.
- If the protagonist never chooses, the story is weak.

## Workflow

Copy this checklist if useful:

```text
Writers Room Story Engine Progress:
- [ ] Step 1: Generate seed options
- [ ] Step 2: Select the strongest premise
- [ ] Step 3: Define story core and ending direction
- [ ] Step 4: Build protagonist engine
- [ ] Step 5: Build Story Spine
- [ ] Step 6: Build causal major beats
- [ ] Step 7: Add world pressure if needed
- [ ] Step 8: Draft scenes
- [ ] Step 9: Diagnose and revise
```

## Step 1: Generate seed options

Generate 3 possible story seeds.
Each seed should include:
- core concept
- emotional hook
- possible audience
- built-in tension
- potential thematic question

Favor ideas with:
- pressure
- contradiction
- strong desire
- hard choices
- built-in escalation
- story movement potential

Avoid:
- generic setups
- ideas with no tension engine
- vibes without conflict

## Step 2: Select the strongest premise

Choose the idea with the strongest combination of:
- audience hook
- emotional charge
- conflict potential
- ending potential
- character pressure

Then state:
- premise
- why it works
- what the audience is leaning in for

## Step 3: Define story core and ending direction

State:
- essence of the story in 1 to 2 sentences
- thematic tension
- probable ending direction
- what final choice, test, revelation, sacrifice, or transformation the ending should force

A story becomes easier to build when the ending direction is known.

## Step 4: Build protagonist engine

Define:
- want
- need
- lie
- ghost
- spine
- comfort zone
- opposite pressure
- stakes

The protagonist should be specific, pressured, and meaningfully wrong about something.

## Step 5: Build Story Spine

Use:
- Once upon a time...
- Every day...
- But one day...
- Because of that...
- Because of that...
- Until finally...
- Ever since then...

Keep it causal, compressed, and clear.

## Step 6: Build causal major beats

Create major beats using therefore/but logic.

Check:
- each beat causes the next
- consequences escalate
- choices matter
- the midpoint changes the direction or meaning of the story
- the climax tests the protagonist’s lie vs truth

## Step 7: Add world pressure if needed

Only build the world to the extent the story needs.

Add:
- rules or norms that create friction
- value conflict
- danger or scarcity
- social structure
- taboo or consequence
- setting forces that shape behavior

Do not overbuild lore that does not affect plot or character.

## Step 8: Draft scenes

Turn beats into scenes with:
- scene objective
- obstacle
- pressure
- subtext
- turn
- therefore/but exit

## Step 9: Diagnose and revise

After drafting, examine:
- does the audience care?
- is the protagonist active?
- is the causal chain strong?
- do scenes turn?
- does the ending feel earned?
- what is the highest-level failure?

Repair structure before polishing prose.