Production Video Pipeline

Production Video Pipeline

Use this skill when the user wants a polished short-form video made from a reference, concept, product, outfit, or visual style. The goal is not just to generate clips; it is to produce a coherent edited video with proof that it works.

Operating Shape

Treat the work as a production pipeline:

1. Analyze the reference or concept before generating anything.
2. Start or update the project PRODUCTION_GATES.md using production-quality-gates.
3. Run product and goal intake and pass G0 Product / Goal Intake.
4. Run a creative director pass for marketing, social, fashion, transformation, or reference-led videos and pass G1 Creative Brief.
5. Run an editing style pass when a reference style is provided or a specific edit language is needed and pass G2 Style Direction.
6. Build a timed storyboard with clear visual beats and pass G3 Storyboard.
7. Generate or select keyframes and pass G4 Keyframes.
8. Generate only the motion clips that are needed, preferably in short controlled segments, and pass G5 Generated Clips.
9. Assemble the final piece in Hyperframes with timing, captions, overlays, callouts, transitions, and audio, then pass G6 Edit Preview.
10. Review the rendered result at problem timestamps, fix weak sections, and pass G7 Final Quality.
11. Deliver the final MP4 plus proof frames/contact sheets and validation notes.

Skill Routing

Use the specialist skills when the task touches their area:

• Use reference-video-analysis when a source video, inspiration clip, or existing output needs to be studied.
• Use production-quality-gates for approval checkpoints, project gate files, stage status, failed-gate handling, and deciding whether the next production stage is allowed.
• Use product-goal-intake before creative direction when the product, offer, target viewer, business goal, proof, or desired viewer action is unclear.
• Use marketing-creative-director for marketing creatives, social reels, product/fashion explainers, transformation videos, or any reference-led production that needs a strong visual concept and production direction.
• Use editing-style-director when a reference edit style, reusable style pack, pacing language, typography system, overlay grammar, or transition style needs to be extracted or applied.
• Use video-storyboard-planner when deciding shot count, timing, prompt direction, or scene logic.
• Use comfyui-video-generation when generating clips through ComfyUI, MiniMax, LTX, or similar local workflows.
• Use fashion-visual-direction for fashion, outfit, styling, dress explanation, body-shape logic, and pointer/callout copy.
• Use hyperframes-video-editing for final assembly, motion graphics, callouts, audio sync, contact sheets, validation, and render.
• Use video-quality-review-fix after every render or when the user says a section is incoherent, repetitive, wavering, deformed, or not production ready.

Production Rules

• Do not rely on a single long AI video generation for the full video. Long generations are more likely to drift, repeat, or lose coherence.
• Do not move from product/goal intake to creative direction, from creative direction to generation, or from generation to editing, without checking the relevant gate. If a gate is needs-fix, repair it before continuing unless the user explicitly marks it waived.
• Use short clips for visual motion, then use Hyperframes to create the edited story.
• If the script or concept depends on a person, face, DP/profile photo, hairstyle, beard, outfit, body type, beauty, grooming, or before/after appearance, require realistic human key visuals before the edit. Do not substitute abstract avatars, silhouettes, or generic icons unless the user explicitly asks for that style.
• Preserve the user's intent from the reference, but make the output original unless they explicitly ask for a duplicate.
• If a timestamp fails, inspect that timestamp directly instead of guessing from the whole video.
• When a visual beat breaks coherence, first decide whether it needs regeneration, replacement with a still/keyframe, or editorial repair in Hyperframes.
• Prefer proof sheets around the changed timestamp over only saying the render completed.

Delivery Standard

A finished response should include:

• Final video path.
• Proof image/contact sheet path.
• What changed.
• Validation result.
• Any remaining quality risk, if real.