video-prompt-engineer

Convert approved storyboards and cinematography plans into provider-ready video generation prompts.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill video-prompt-engineer-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: video-prompt-engineer
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/video-prompt-engineer
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill video-prompt-engineer-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating an approved creative brief into a text-to-video or image-to-video prompt often introduces contradictions, lost details, and provider-incompatible parameters. This Skill turns approved production artifacts into structured, model-ready video prompts that preserve creative intent. ## Core Features & Use Cases - Structured prompt ordering: Enforces a ten-part prompt grammar covering subject identity, motion, camera, lighting, timing, and exclusions. - Image-to-video motion rules: Describes motion while locking reference-image details so the model does not replace protected elements. - Provider adaptation: Produces a provider-neutral prompt plus an adapted request accounting for duration, aspect ratio, seed, and negative-prompt support. - Use Case: Given an approved storyboard for a six-second macro dolly-in on a jewelry pendant, generate a prompt package with locked elements, negative constraints, and provider-specific parameters. ## Quick Start Use the video-prompt-engineer skill to turn my approved storyboard and cinematography plan into a prompt package for my target video generation provider.

Frequently Asked Questions about video-prompt-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a prompt for image-to-video generation?▼

Describe the motion you want rather than re-describing the reference image, since re-description can cause the model to replace locked details. Specify allowed motion, camera movement, duration, and list the elements that must remain unchanged.

What should a text-to-video prompt include?▼

A video prompt should cover subject identity, permitted action, environment, shot scale, camera movement, lens and lighting, timing, continuity or loop instructions, exclusions, and output format constraints, in that order unless the provider documents another grammar.

How do I adapt a video prompt for different providers?▼

Check the provider profile for supported durations, aspect ratios, negative-prompt support, reference-image limits, seed support, and parameter names. Keep the provider-neutral prompt separate from the adapted request so creative intent survives provider changes.

Why does my video generation change details from my reference image?▼

This happens when the prompt re-describes the image content instead of only describing motion, causing the model to regenerate rather than preserve details. Lock immutable elements explicitly and instruct the model to preserve the supplied reference exactly.

What negative constraints should I use for video generation?▼

Use observable exclusions relevant to the shot, such as no added objects, no text, no geometry changes, no camera shake, no flicker, and no scene cuts. Avoid large generic negative-prompt lists that do not match the actual risks of the shot.