seedance-interview-short

name	seedance-interview-short
description	This skill should be used when the user wants a fast Seedance 2.0 creative brief, a short interview, a compressed intake flow, or a quick director-style clarification before prompt writing.
license	MIT
user-invocable	true
tags	["creative-direction","brief","compression","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-interview-short

Before producing prompt text, a prompt-ready block, a rewrite, an example, or a compiled clip, load the Director's Read, 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 speed matters more than exhaustive creative discovery. The goal is to turn a vague idea into a compact director brief with no more than three questions, then route to prompt writing.

Speed does not bypass story judgment. Load the Director's Read before producing the compact brief. Complete its ten-field internal record for every narrative, story, or performance idea; for a utility, product-only, abstract, VFX, or ambient idea with no requested agency or performance, record its two-line non-narrative intent and refusal instead. Never reconstruct the read from remembered craft.

Intent

The user here knows what they want and is asking you to respect their momentum. The soul of this skill is restraint: find the one missing piece that would sink the generation, ask only that, and get out of the way. Speed is the form their trust takes.

Process

Ask at most three questions, and only ask them if the answer materially changes the prompt. Assume no film background: ask in everyday words, give pickable options, and attach a default so "I don't know" never stalls the brief. Prioritize:

1. What happens in the video, and what is different at the end? (not sure? I'll pick one simple action with a visible ending)
2. Is this one complete clip, connected clips, a longer scene to divide, a continuation of accepted footage, or are you unsure? (not sure? I'll plan the whole story but only finalize the first prompt)
3. How must the complete story end, and do you have photos, clips, final frames, or sound that define the look, motion, or sound? (none is fine; if continuing, I need the accepted clip or final frame)

If the user already supplied enough information, do not ask. Produce a brief immediately. If the user speaks production language fluently, drop the plain phrasing and ask in director terms.

Run the interview and brief in the user's language; for localized starting-point menus and invites, load interview-starters. If the user gives explicit shot, lens, camera, blocking, or performance direction, keep it verbatim and compile it into a shot-contract-grade brief - never simplify or override a professional's spec. When the user has no idea at all, offer a starting-point menu to react to instead of asking a question they cannot answer.

Even in fast mode, the brief states one motivated intention, not a generic "cinematic" look. For narrative work, derive it from the completed Director's Read record and translate the turn, visible suppressed behavior, and non-transferable detail into filmable or audible carriers. For non-narrative work, serve the utility intent without inventing want, power, conflict, or subtext. Load directing-engine only when the right setup for the scene is genuinely unclear.

Compact Brief Pattern

Internal lane record from the Director's Read, then: Mode: [T2V/I2V/V2V/R2V]. Subject: [anchor]. Beat: [before -> action -> final state]. Camera: [one move]. Light/style: [physical source and safe descriptor]. Sound: [dialogue/ambience/SFX/music/silence]. Constraints: [identity, IP, safety, product, prompt budget].

Routing Rule

Route to seedance-sequence for connected clips, long scenes, unclear total duration, or continuation-ready planning; seedance-continuation for accepted-footage continuation; seedance-prompt for a full standalone production prompt; seedance-prompt-short for a compact prompt; seedance-copyright for IP/likeness risk; or seedance-troubleshoot when the user starts from a bad result.

Output Contract

Return one compact brief under 150 words, any missing high-impact question, and a recommended skill route. Keep Director's Read labels out of final generation prose; show the internal record only when the user requests the planning rationale or when another agent needs the handoff. If the request is a sequence, include the complete story ending, likely clip count, current clip job, and the fact that future prompts stay provisional until accepted footage is reviewed.