ai-video-prompt-generator

AI Video Prompt Generator

This skill no longer writes final prompts directly inside the Codex chat context. It consumes a clean prompt_spec.json, validates it, calls an isolated LLM prompt generator, and lints the output.

Required Reading

Read only what the task needs:

• references/v2-core-protocol.md for the generic v2 prompt contract.
• references/prompt_spec.schema.json before creating or changing specs.
• references/output-contract.md before consuming generator output.
• references/seedance-provider-prompting.md when the target provider is Dreamina, Seedance, Jimeng, or another Seedance-like multimodal video surface.
• references/director-dense-seedance-protocol.md when the requested clip is a continuous take, timed multi-beat sequence, dialogue scene, transformation, occlusion transition, action tableau, cross-video continuation, representation-layer change, or other director-dense prompt.
• references/asset-duty-handoff.md when the prompt uses character, environment, prop, palette, storyboard, staging, frame, source-video, voice, or cadence assets.
• director_profiles/*.md only for the selected director profile.

Do not load old project examples, deprecated compatibility rules, or chat history into the generator. Project-specific examples belong in the movie root, not inside this generic skill.

Workflow

1. Build or receive a prompt_spec.json from project truth. Choose validation_policy.stage before adding detail: exploration for creative discovery, proof_shot for a runnable experiment, batch for repeatable production, or release for final delivery. Missing creative contracts are warnings in the first two stages and blockers in the last two. Legacy specs without this field remain batch for compatibility. Choose prompt_density_policy.mode deliberately: compact_motion for one controllable event, or director_dense for a complete timed execution contract. Long output is valid in director-dense mode; completeness, not brevity, is the gate. Also choose prompt_density_policy.control_source: prompt_owned, asset_delegated, existing_video_delta, or dialogue_audio. A compact prompt may carry several inherited beats only when approved assets or a source clip own those beats and the spec names the inherited and text-owned controls. Do not expand a one-delta edit or voice cue into a scene rewrite. Treat director contracts as modules, not a form to fill. Use only the modules that reduce a real ambiguity or known failure risk for this shot. Consume approved asset duties; do not paste upstream character/scene/prop generation briefs into the video motion prompt. Canonical asset creation remains with ai-film-production-system; this skill binds those assets to the shot and protects them from cross-duty contamination. If existing_video_delta or dialogue_audio already has an authoritative source picture, skip still/storyboard generation. An empty storyboard_prompt is then correct control allocation, not missing work.
2. Run: