| name | to-scenes |
| description | Use when a narrated video's beats and draft narration need visual direction, scene concepts, metaphors, worlds, action, camera logic, or visual continuity before storyboarding. |
To scenes
Turn BEATS.md and NARRATION.md into SCENES.md. A scene is a small event in a world, not a container for information.
Process
- Read both inputs, the applicable design truth, and
references/hyperframes-capability-envelope.md. The envelope constrains feasibility without prescribing implementation. Treat narration as revisable evidence, not a locked timeline.
- Find a physical or spatial expression for each abstract beat: give the concept a body, put it in a world, and cause a visible state change.
- Group beats that belong to one continuous event; split a beat when its explanation requires distinct visual events.
- Design the film as a whole: establish a continuity object or motion, vary worlds and shot scales, place visual peaks, and name the rhythm.
- Write
SCENES.md using references/scene-format.md. Read that file before drafting or auditing scenes.
- Flag narration sentences whose order, length, or duplication fights the visual event. Revise
NARRATION.md only after preserving the originating beat's claim and job.
- Classify every scene's feasibility using the capability envelope, naming dependencies and fallbacks where required.
- Run the scene audit in the format reference.
SCENES.md is complete when every beat has a feasible visual event, the film has deliberate variation and continuity, and a storyboard artist can choose shots without inventing the direction.
