Seedance production workflow

Produce a traceable video package, not just a polished prompt. Distinguish planned, assets-ready, submitted, generated, and reviewed states. Never call a prompt or an unrun storyboard a completed video.

This Skill coordinates production and review. For case-backed prompt structure, use the repository's timeline, reference-image identity, or storyboard grid template when it fits. Those cases support the prompt structures; they do not prove that this end-to-end workflow improves final-video quality. Treat that as a test question.

Route the project

1. Collect only missing essentials: story or product, intended viewer, duration, aspect ratio, desired look, must-have actions, audio/dialogue, existing reference assets, target Seedance entry point, and the user's time or generation budget. Use a fictional subject for a pilot when the user has not chosen one and say so.
2. Choose the simplest control structure that fits the brief:
   • One continuous shot: a timed action and camera plan may be enough.
   • Multi-shot with exact order or composition: shot list plus numbered storyboard grid or per-shot keyframes.
   • Identity/product-sensitive: add a master reference and an explicit inherit / do-not-inherit map.
   • Complex choreography: use authorized motion video or spatial/clay reference if the entry point supports it.
   • Longer than one generation: plan a native extension first where available; otherwise plan a segment handoff using the prior video or returned last frame, and verify the join.
3. Check current model and entry-point limits in provider capabilities before fixing duration, media count, resolution, or an API route. A supported model capability does not prove that the user's account exposes it.

Prepare the inputs