Video Project Setup

Mission

Create the small amount of project context that prevents repeated video work from losing the brief, source roles, continuity rules, rights state, or delivery constraints. This is a planning and workspace skill; it does not submit paid media jobs.

Use this skill when

• a series, campaign, product launch, channel, or recurring show needs a reusable context file;
• several people or agents will contribute clips to one project;
• source assets need stable roles and provenance; or
• a previous receipt exists but its assumptions need to be made explicit.

Collect

Ask for or extract:

• project and series name, owner, audience, language, and intended channels;
• creative objective, tone, format, target duration, aspect ratio, resolution, frame rate, audio, caption, and export requirements;
• product, character, presenter, location, or brand facts that must not drift;
• script, beat sheet, shot list, reference media, and source-video roles;
• rights, consent, music/license, claims, accessibility, and retention state;
• budget, model preference, variant count, review owner, and deadline; and
• definition of done and the next approval gate.

Do not convert an unverified statement into a fact. Keep unknown, user-supplied, provider-observed, and approved distinct.

Asset inventory

For each asset, record a stable local ID, type, role, source, parent if any, rights/consent state, intended use, and whether it may be uploaded. Useful roles include subject_reference, product_reference, first_frame, last_frame, driving_video, source_video, audio, logo, script, and approved_parent.

Do not infer that a file is safe to upload because it is present locally. Ask for permission when an asset contains a real person, private information, licensed material, or an externally owned brand.

Write the context

When workspace writes are allowed, create or update .video/project.md using the structure in reports and receipts. Preserve prior approved facts and append a dated change note when a later brief supersedes them. Do not overwrite a receipt or approved parent merely to make the folder look tidy.

At minimum, the context should include:

1. objective and audience;
2. delivery matrix;
3. continuity and preservation rules;
4. asset manifest link;
5. rights, claims, and consent status;
6. cost and approval boundary; and
7. open decisions and definition of done.

If a project context already exists, summarize the differences and ask before changing an approved invariant. If writing is not authorized, return the proposed context in the response without claiming it was saved.

Handoff

Return the project context path or draft, asset-role table, unresolved decisions, rights/consent gaps, and the recommended next skill. Typical next steps are video-generation, storyboard-to-video, character-continuity, or short-form-repurposing.