/seedance-sequence

name: seedance-sequence
description: "This skill should be used when a Seedance 2.0 request is a long story, connected set of clips, multi-generation scene, campaign sequence, dense storyboard, continuation-ready plan, or any idea that must be divided into stateful clips."
license: MIT
user-invocable: true
tags:
  - sequence
  - continuity
  - prompt-compiler
  - seedance-20
metadata:
  version: "6.7.0"
  updated: "2026-08-01"
  parent: "seedance-20"
  author: "Iamemily2050 (@iamemily2050)"
  repository: "https://github.com/Emily2040/seedance-2.0"
  openclaw:
    emoji: "🎬"
    homepage: "https://github.com/Emily2040/seedance-2.0"

seedance-sequence

Before producing prompt text, a prompt-ready block, a rewrite, an example, or a compiled clip, load the [Director's Read](../../references/directors-read.md), classify the brief, and complete its canonical narrative or non-narrative record. Translate that record into visible or audible carriers and keep its internal labels out of final generation prose.

Use this when the user's idea is larger than one reliable generation, when connected clips are requested, or when the user says continue, extend, next part, part two, next scene, or make it longer. Plan globally, generate locally: the skill plans the whole story, but compiles only the next unresolved clip.

Load the [Director's Read](../../references/directors-read.md), [sequence-project-state](../../references/sequence-project-state.md), [continuation-handoff](../../references/continuation-handoff.md), [prompt-compiler](../../references/prompt-compiler.md), [surface-prompt-profiles](../../references/surface-prompt-profiles.md), [event-density](../../references/event-density.md), and [continuity-qc](../../references/continuity-qc.md). Load [reference-transfer-contract](../../references/reference-transfer-contract.md) when references are present and [dense-storyboard-mode](../../references/dense-storyboard-mode.md) when the request contains many shots or animation panels. Load [directing-engine](../../references/directing-engine.md) to set one directorial voice for the whole story and plan the long-form spine so the look is authored by one hand across every clip. For a user's first multi-clip project, [sequence-worked-trace](../../references/sequence-worked-trace.md) walks the whole loop once - plan, deviation, reconciliation, chain cap, re-anchor, resume.

Intent

The user is trying to make a film, not a pile of prompts. This skill protects the thread of action across generations: what already happened, what is happening now, what must not happen yet, and what the accepted footage actually shows. The plan is global; the prompt is local.

Sequence Classifier

Classify as `sequence_project` when the story exceeds the verified active-surface duration, asks for multiple connected clips, contains several narrative beats, is a film scene, ad, campaign, music sequence, action scene, dialogue scene, or uses continue/extend/next-part language. Otherwise classify as `standalone_clip` and return to the concise prompt path.

For every request also classify:

• generation input mode: T2V, I2V, V2V, R2V, FLF2V, edit, native extend when verified for the active surface, or troubleshoot;
• sequence relation: standalone, sequence_first_clip, seamless_continuation, intentional_next_shot, bridge_between_known_states, repair_tail, or reanchor_after_drift;
• shot structure: compact_single_take, phased_single_take, dense_multishot, first_last_frame_transition, or video_edit_contract;
• medium grammar: live_action, 3d_animation, 2d_animation, product_or_object, or another supported medium;
• surface profile: exact reference-tag convention, verified duration range, prompt budget, supported reference roles, timeline syntax, edit/extension availability, audio behavior, and constraints.

If the surface is unknown, use a conservative generic profile. Do not invent a duration, prompt limit, reference count, or tag syntax.

Scene Architecture

Plan scenes before clips. A scene is the re-anchor unit: one location and time envelope whose clips may chain from each other's accepted footage.

• Seamless continuation is legal only inside a scene. A scene boundary is an intentional cut that opens from canonical references and resets `extension_depth` to 0.
• Cap consecutive output-sourced generations at the scene's `max_chain_depth` (default 2, hard ceiling 3). Schedule re-anchors in the plan; identity decays with chained generations, so a scheduled reset is routine and a drift repair is expensive.
• Map the arc to scenes: each scene carries one `arc_position` and its clips inherit it.
• Cuts are the cheapest continuity tool. The audience expects frame continuity only inside a chained shot, not across an editorial cut. A five-minute story usually resolves to several scenes of two to five clips, not one long extension chain.
• Audio: clips carry ambience, sync SFX, and on-camera dialogue; unify music and score in post because audio is not continuous across separate generations.

Build Process

1. Establish the story promise and final outcome before Clip 01. 2. Classify every clip with the [Director's Read](../../references/directors-read.md) and record its explicit `directors_read_lane` as `narrative` or `non_narrative`; never infer psychology from `story.medium`. This per-clip lane lets utility inserts coexist with performed beats in one sequence. Before a clip classified in the narrative lane is compiled, complete its ten-field internal record, including one non-transferable detail and one stock-solution refusal. For observation/performance without a dramatic story turn or for utility, use the non_narrative lane and record the two-line intent and refusal; do not invent drama or suppress the requested expression. Then use [directing-engine](../../references/directing-engine.md) to set one directorial voice for the whole project when the sequence needs it and plan the long-form spine - how shot scale, camer