mcpField
S
scene-analysis

scene-analysis

github.com/bybren-llcCreative & media7065 installsUpdated 12w ago
Repository

About scene-analysis

scene-analysis is a writing skill for screenplay writers assessing how scenes function and flow. It breaks scenes into beats and examines purpose, conflict, change, and pacing.

Key features

  1. 01Scene purpose and function analysis
  2. 02Hook-to-resolution structure
  3. 03Beat and emotional-shift mapping
  4. 04Pacing and scene-length review
  5. 05Common scene problem checks

Use cases

  1. 01Assess whether a scene advances the story
  2. 02Find pacing issues across scene lengths
  3. 03Map emotional or power shifts in dialogue
  4. 04Revise scenes with unclear conflict or purpose

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bybren-llc/story-systems-template --skill scene-analysis

After installing, type/scene-analysisin Claude Code to confirm it loaded.

Bundled filesREADME.md

Details

From the project README

Scene Analysis Skill

Invocation Triggers

Apply this skill when:

  • Analyzing scene effectiveness
  • Evaluating scene pacing
  • Identifying scene problems
  • Breaking down scene beats

Scene Fundamentals

What Makes a Scene?

A scene is a unit of story with:

  • Single location (or continuous movement)
  • Continuous time (or clearly marked passage)
  • Beginning, middle, end
  • Purpose in the larger story
The Scene Question

Every scene should answer: "What changes?"

If nothing changes, the scene may not be necessary.

Scene Anatomy

Scene Structure
HOOK      → Grabs attention, establishes context
BUILD     → Develops conflict/tension
TURN      → Something changes
RESOLUTION → Scene's immediate outcome
PROPULSION → Sets up what's next
Example Analysis
INT. RESTAURANT - NIGHT

HOOK: Sarah sits waiting. Checks her watch. John arrives, late.

BUILD: Awkward pleasantries. Sarah's cool. John tries to connect.

TURN: Sarah reveals she knows about the affair.

RESOLUTION: John admits it. Offers no excuse.

PROPULSION: Sarah says "I want a divorce" - cut before John responds.

Scene Purpose

Plot Functions
FunctionDescription
SetupEstablish information for later
ConfrontationCharacters in conflict
RevelationNew information emerges
DecisionCharacter makes choice
ActionPhysical events unfold
ConsequenceResults of previous actions
Character Functions
FunctionDescription
IntroductionMeet a character
DevelopmentDeepen understanding
Arc momentCharacter changes
RelationshipDefine/change relationship
Every Scene Must
  1. Serve at least ONE plot function
  2. Serve at least ONE character function
  3. Ideally serve BOTH simultaneously

Pacing Analysis

Scene Length Guidelines
TypePagesPurpose
Short (1/2-1 page)Quick information, transitions
Medium (2-3 pages)Standard dialogue scenes
Long (4-5 pages)Major confrontations, setpieces
Extended (5+ pages)Climactic moments only
Pacing Rhythm

Vary scene lengths for rhythm:

SHORT - MEDIUM - MEDIUM - SHORT - LONG - SHORT

Not:

MEDIUM - MEDIUM - MEDIUM - MEDIUM - MEDIUM
Scene Economy
  • Enter late: Skip arrivals, greetings
  • Leave early: Cut after the point is made
  • Cut the fat: Every line earns its place

Scene Beats

What is a Beat?

A shift in the scene - emotion, power, information.

Identifying Beats

Mark where something changes:

1. Sarah waits (anticipation)
   [BEAT: John arrives late]
2. Awkward greeting (tension)
   [BEAT: Sarah asks direct question]
3. John deflects (avoidance)
   [BEAT: Sarah reveals she knows]
4. John exposed (power shift)
   [BEAT: John admits truth]
5. Resolution (new status quo)
Beat Mapping
| Beat # | What Happens | Emotional Shift |
|--------|--------------|-----------------|
| 1 | Sarah waits | Hope → Doubt |
| 2 | John arrives | Doubt → Tension |
| 3 | Small talk | Tension → Impatience |
| 4 | Sarah confronts | Impatience → Anger |
| 5 | John admits | Anger → Devastation |

Scene Analysis Template

## Scene Analysis: [Scene Description]

### Location & Time
INT./EXT. [LOCATION] - [TIME]
Page [X] - [Y] ([Z] pages)

### Scene Purpose
- **Plot Function:** [setup/confrontation/revelation/etc.]
- **Character Function:** [introduction/development/arc/etc.]
- **What changes:** [state A → state B]

### Structure
- **Hook:** [description]
- **Build:** [description]
- **Turn:** [description]
- **Resolution:** [description]
- **Propulsion:** [description]

### Beat Breakdown
[Beat mapping table]

### Strengths
- [What works]

### Issues
- [What doesn't work]

### Recommendations
1. [Specific improvement]
2. [Specific improvement]

Common Scene Problems

No Conflict

Problem: Characters agree, nothing is at stake. Fix: Give characters opposing goals. Even allies disagree on methods.

No Change

Problem: Scene ends same as it started. Fix: Something must be different. Information, relationship, stakes.

Wrong Length

Problem: Scene overstays welcome or rushes through. Fix: Match length to importance. Trim fat or expand key moments.

Unclear Purpose

Problem: Scene exists but why? Fix: Define the scene's job. If it has none, cut it.

Predictable

Problem: Scene goes exactly as expected. Fix: Add reversals, surprises, complications.

Scene Types Analysis

Exposition Scene
  • Risk: Information dump
  • Goal: Information + conflict
  • Test: Would scene be interesting without info?
Action Scene
  • Risk: All spectacle, no stakes
  • Goal: Character revealed through action
  • Test: What does action tell us about character?
Dialogue Scene
  • Risk: Talking heads
  • Goal: Subtext, conflict, change
  • Test: Is there tension in the conversation?
Transition Scene
  • Risk: Unnecessary
  • Goal: Essential bridge only
  • Test: Can it be cut? Can info be combined elsewhere?

Scene Checklist

Before Writing
  • What is the scene's purpose?
  • What changes by the end?
  • What's the conflict?
  • When does the scene start/end?
After Writing
  • Does the scene have a clear hook?
  • Does tension build?
  • Is there a turn?
  • Does it propel to next scene?
  • Can it be shorter?
  • Is it the right length for its importance?

Comments

Markdown supported