agentleFS
LeoYeAILeoYeAI/seedance-skills/skills/seedance-continuation/SKILL.md

seedance-continuation

Skill42 starsChanged 4 months agoMITView on GitHub

This skill should be used when a Seedance 2.0 user asks to continue, extend, make the next part, repair the tail, bridge between known frames, re-anchor drift, or create a successor prompt from accepted footage.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this for seamless continuation, intentional next shots, bridge clips, tail repair, and re-anchoring after drift.

    line 24
  2. Distinctive:

    Before writing any continuation prompt, require:

    line 34
  3. Distinctive:

    Do not hide this uncertainty by writing a speculative prompt.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

seedance-continuation

Use this for seamless continuation, intentional next shots, bridge clips, tail repair, and re-anchoring after drift. A continuation prompt must be grounded in accepted footage, not only in the old plan.

Load [ref:continuation-handoff], [ref:sequence-project-state], [ref:prompt-compiler], [ref:reference-transfer-contract], and [ref:continuity-qc]. Load [ref:failure-atlas] when the continuation failed or drift is visible. Load [ref:directing-engine] so the next clip inherits the project's directorial voice and its position on the long-form spine; the look never re-rolls between clips.

Intent

The user already made something they accepted, and now they are trusting the story to continue from exactly where it really landed - not where the plan hoped it would. The soul of this skill is fidelity to what actually happened: honor the accepted footage as the only truth, refuse to invent the bridge, and ask for the real ending rather than guess it. Continuity is a promise that the film the user already has will not be quietly contradicted.

Required Input Gate

Before writing any continuation prompt, require:

  • project_id;
  • current clip_id;
  • valid parent_clip_id;
  • scene_id, and whether the next clip stays inside the scene or crosses a scene boundary;
  • full-story objective;
  • final story outcome;
  • next planned narrative job;
  • next clip felt_intent - what the viewer should feel or notice;
  • accepted previous clip or accepted final frame;
  • observed_end_state;
  • continuity locks;
  • inherited directorial voice and arc position;
  • exact reference registry;
  • active surface or conservative surface profile.

If the source is unavailable, say: "I have the story plan, but I do not have the actual ending of the previous generation. Upload the clip or its final frame - python scripts/extract_last_frame.py <take> pulls the final frame locally - or describe exactly what is visible at the end. I should not invent the continuation state."

Once a frame or clip is attached, run the Observation Fast Path from [ref:continuation-handoff]: the agent fills the observation record from what is visible and asks only about what the attachment cannot show (for a still: open motion, camera movement phase, audio phase). Never hand the sensing work back to the user when the pixels are already in hand.

Do not hide this uncertainty by writing a speculative prompt.

Continuation Types

seamless_continuation: same shot, same geography, same open motion, same or motivated camera continuation, and accepted previous footage as the source.

intentional_next_shot: an editorial cut is appropriate. Story continuity matters, but exact frame continuity is not promised. Do not call it seamless.

bridge_between_known_states: a defined start state and end state must be connected, often with first/last-frame generation when the active surface supports it.

repair_tail: the previous final seconds failed. Repair, edit, or regenerate the tail before continuing because continuing from a failed tail amplifies the error.

reanchor_after_drift: identity, detail, geography, motion, audio, or world continuity degraded. Return to canonical identity, the strongest accepted final frame, a stable source clip, or a new intentional shot using canonical references.

Scene Boundary Rule

Crossing a scene boundary defaults to intentional_next_shot opening from canonical references. Do not promise seamless_continuation across a scene boundary; if the user explicitly asks for one, record the reason and treat the result as high drift risk.

Canon Rule

Accepted observed footage overrides planned state. If the plan says the subject reached the car door but the accepted clip ends two steps away, the next prompt begins two steps away. It does not replay the terminal exit, and it does not assume the subject is inside the car.

Rejected footage never updates canon and never becomes a parent source.

Track extension_depth as consecutive output-sourced generations since the last canonical re-anchor; it resets to 0 when a clip opens from canonical references. At the scene's max_chain_depth (default 2, hard ceiling 3), re-anchor by schedule instead of extending again. Visible drift before the cap is an immediate reanchor_after_drift.

Output Contract

Return:

  1. Continuation type.
  2. Source evidence used.
  3. Observed end state.
  4. Next clip contract.
  5. Intent echo: one line - "this clip exists so the viewer feels X" - confirmed before generation spends money.
  6. Continuity locks and allowed changes.
  7. Completed beats to exclude.
  8. Reserved future beats to exclude.
  9. Final natural-language Seedance prompt for the current clip only.
  10. Updated Project State Capsule or a request for missing source evidence.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.