storyboard-storytelling-pipeline

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: storyboard-storytelling-pipeline
description: Build, repair, or continue a complete storyboard workflow from script to clean-board guidance. Use when the user wants story-first boarding grounded in FloobyNooby-style planning, clarity, staging, shot progression, motivated cuts, continuity, rough thumbnails, animatic review, structural revision, key panels, full rough board, and clean-pass rules rather than an analysis-heavy shot list.
---

# Storyboard Storytelling Pipeline

Use this skill when the user wants a storyboard that truly tells the story, not just a pile of shots.

This skill treats storyboarding as a full pipeline:

`script read -> sequence map -> camera strategy -> scene shot flow -> rough thumbnails -> animatic review -> structure revision -> shot-language refinement -> key panels -> rough board -> clean pass -> final delivery`

## Read These References

Read in this order before substantial work:

1. `references/floobynooby-core.md`
2. `references/workflow.md`
3. `references/templates.md`

Read `references/night-nuo-case-study.md` when you need a full worked example, a trailer calibration, or a sanity check for object-driven stakes, delayed climax, and story-first lens language.

The full bundled case pack now lives under:

- `references/night-nuo-case/index.md`

## Primary Stance

- Planning comes first. Do not jump straight to a detailed shot list.
- Clarity beats cleverness.
- Story point decides shot progression, not habit.
- Close-ups are budgeted impact tools, not default coverage.
- Cuts need motivation.
- Continuity protects comprehension.
- Rough passes come before clean passes.
- The audience should be able to feel the story by reading the shots in order.
- If a board only works because notes explain it, the board is not solved yet.

## When To Use This Skill

Use it for any of these:

- A full script that needs a complete storyboard workflow
- A scene or sequence that needs stronger shot progression
- A broken storyboard that needs structural repair
- A trailer or short-drama board that feels readable on paper but not visual in the head
- A project that needs sequence maps, rough-thumbnail tasks, animatic checks, or clean-pass rules
- A request to continue an already-started storyboard package from a later stage

Do not use this skill when the user only needs:

- pure image-generation prompts
- a simple shot glossary
- a review of one existing board without continuing the workflow

## Stage Detection

Before producing output, identify what stage already exists.

Common cases:

- Fresh script only: start at Step 1
- Script plus scene notes: usually start at Step 2 or Step 3
- Existing storyboard draft: audit it against the workflow, find the highest stable step, continue from the next step
- Existing rough boards: move to animatic review, structural revision, or clean-pass rules instead of restarting everything

When resuming, preserve any completed stage that is still sound. Replace weak stages, not the whole package by reflex.

## Default Workflow

Follow the full 15-step pipeline unless the user explicitly asks for a narrower slice.

1. Read the whole script for dramatic structure, not shots.
2. Build a `sequence` map.
3. Assign each sequence a camera / lens-language strategy.
4. Build each scene's dramatic spine and `shot flow`.
5. Create rough-thumbnail tasks for the full piece.
6. Review it with animatic thinking.
7. Correct big structure before polishing shots.
8. Refine single-scene shot language.
9. Re-run a second rough pass with corrected shot logic.
10. Lock key panels for the most valuable beats.
11. Build a coarse animatic review plan.
12. Write scene-level shot-by-shot boards for the key scenes.
13. Assemble a full rough-board package.
14. Write clean-pass execution rules and final checks.
15. Deliver a final storyboard master document and a short delivery note.

See `references/workflow.md` for the detailed purpose, output, and failure mode of each step.

## Output Rules

- Def