Scene Sequencing

Structure scenes and control pacing using scene-sequel rhythm. Use when individual scenes work but don't accumulate, when pacing feels off (too rushed or too slow), when transitions feel mechanical, or when readers can follow but aren't compelled forward. Based on Dwight Swain's Goal-Conflict-Disaster and Reaction-Dilemma-Decision structure.

191 stars 24 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jwynia/agent-skills --skill scene-sequencing
Manual install
git clone --depth 1 https://github.com/jwynia/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/creative/fiction/structure/scene-sequencing ~/.claude/skills/scene-sequencing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Scene Sequencing: Pacing Skill

You help writers structure scenes and control narrative pacing using the scene-sequel rhythm.

## Core Principle

**The fundamental unit of pacing is not the scene alone, but the scene-sequel pair.** Scenes create tension; sequels process it. The alternation creates peaks and valleys that make stories readable.

## Scene Structure: Goal → Conflict → Disaster

### Goal
What does the POV character want in this scene?
- Specific and concrete
- Achievable within the scene
- Connected to larger story goals
- Clear to reader within first beats

### Conflict
Opposition to the goal that **escalates** within the scene.
- Another character with different agenda
- Environmental obstacle or time pressure
- Internal resistance (fear, doubt, values)

Static conflict is boring. Each beat should make the goal harder.

### Disaster
Scene ends with one of these outcomes (in order of narrative power):
1. **Yes, but...** — Goal achieved, new problem created (strongest)
2. **No, and furthermore...** — Goal failed, situation worse
3. **No** — Goal failed, must try again
4. **Yes** — Goal achieved cleanly (use sparingly—kills tension)

## Sequel Structure: Reaction → Dilemma → Decision

### Reaction
Emotional response to disaster. Lets reader:
- Process what happened
- Connect with character's emotional state
- Breathe between high-tension scenes

Can be brief (a sentence) or extended (pages).

### Dilemma
Read the full skill on GitHub

Details

Skill name
scene-sequencing
Path
skills/creative/fiction/structure/scene-sequencing/SKILL.md
Repo updated
24 February 2026

FAQ

What does the Scene Sequencing skill do?

Structure scenes and control pacing using scene-sequel rhythm. Use when individual scenes work but don't accumulate, when pacing feels off (too rushed or too slow), when transitions feel mechanical, or when readers can follow but aren't compelled forward. Based on Dwight Swain's Goal-Conflict-Disaster and Reaction-Dilemma-Decision structure.

How do I install the Scene Sequencing skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jwynia/agent-skills --skill scene-sequencing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Scene Sequencing popular?

It lives in jwynia/agent-skills, which has 191 GitHub stars and 24 forks.

Related skills

Abstract Strategy

191

jwynia/agent-skills

Design abstract strategy games with perfect information, no randomness, and strategic depth. Use when designing a board game, exploring abstract strategy games, brainstorming game mechanics, or evaluating game balance. Keywords: board game, game design, strategy, mechanics, balance.

Other24

Adaptation Synthesis

191

jwynia/agent-skills

Synthesize new works from extracted functional DNA documents. Use when adapting a source work to a new context, when combining multiple source extractions, or when generating variations that preserve function while changing form.

Other24

Agent Bootstrap

191

jwynia/agent-skills

Bootstrap agentic development environment from agent.toml manifest

AI, LLMs & Agents24

Schedule Design

201

swyxio/skills

Design patterns and lessons for building conference schedule pages with React. Covers theme systems, 2D grid overviews, filter UX, sticky layouts, modals, favorites, and data normalization. Use when building or modifying schedule views, grid tables, filter panels, or conference UI components.

Frontend & Design12

Resilient Computer Use

201

swyxio/skills

Operate desktop applications and browsers reliably through Computer Use, with proactive state tracking and recovery from common automation failures. Use for any multi-step or consequential UI workflow, especially when app focus moves, multiple monitors or windows are present, accessibility state is empty or stale, element indices change, screenshots and accessibility disagree, dialogs or file pickers appear, a browser upload chooser or native picker fails, a local artifact is prepared but not attached, buttons remain disabled, typing submits unexpectedly, a user interrupts or concurrently uses

Frontend & Design12

Second Order Thinking

150

guia-matthieu/clawfu-skills

Think beyond immediate consequences to understand the chain reactions of decisions. Master Howard Marks' investment framework for seeing what others miss. Use when: **Strategic decisions** where long-term consequences matter; **Policy/rule changes** that will trigger behavioral responses; **Competitive moves** to anticipate market reactions; **Product decisions** where user behavior may shift; **Investment analysis** to see past obvious conclusions

Frontend & DesignIn 1 list32

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.