---
name: video-producer
description: Produce structured AI-video projects as a production pipeline: world bible, tone package, visual package, continuity rules, character bible, location bible, still-shot planning, and action prompts. Use for corporate video, dorama/serialized drama, cinema scenes, advertisement fragments, character/location reference planning, scene packets, shot lists, still generation, reference-to-video prompts, and VideoProducer work. Triggers on requests like video-producer, сгенерируй шот, сделай видео, анимируй, пересними сцену, библия мира, библия персонажей, библия локаций, раскадровка, action prompt, dorama, corporate, cinema, advertisement, Roman, Kate, Helen, Alexander, Marco.
---

# Video Producer

This workspace is a production system for AI video. Kira is producer. Dmitry is director and editing director.

## Core Principle

Do not start from a single video prompt when the project requires continuity.

Correct sequence:
1. choose project layer
2. build world / tone / visual / continuity rules
3. approve principle characters and principle locations
4. build character bible and location bible with 360 references
5. convert raw material into scene packets
6. produce still-shot plans and still prompts
7. approve stills
8. produce action prompts for video
9. review outputs by failure layer and montage logic

## Project Layers

Always classify the layer first. Different layers have different rules:
- **corporate** — premium business realism, restrained acting, spatial office logic
- **dorama** — serialized emotional drama, strong identity/location continuity
- **cinema** — authorial cinematic scene work, atmosphere, subtext, composition
- **advertisement** — persuasive clarity, product/service legibility, brand discipline

Read `references/layers.md` when starting or reclassifying a project.

## Production Roles

Use these roles as production departments:

- **screenwriter** — rewrites raw material strictly into the project standard: scene objective, beat list, continuity-in/out, risk notes.
- **location-manager** — creates principle locations first; after approval builds location bible and 360 image references.
- **casting-manager** — creates principle characters first; after approval builds character bible and 360 image references.
- **director-of-photography** — creates still-shot plans and still-image prompts from the bibles and references.
- **director** — creates detailed action prompts for video from approved stills and project context.

Read `references/production-roles.md` before delegating or simulating these roles.

## World / Bible Workflow

Before repeatable generation, preserve:
- core world rules
- tone package
- visual package
- tech bible
- continuity rules
- appearance anchors
- behavior anchors
- social roles
- visual and behavioral prohibitions
- location anchors and geography

Read `references/world-building.md` for the schema.
For serialized work, also read `references/serialized-drama-schema.md`.
Read `references/project-setup-rules.md` when defining project-level technical and reference-generation standards.

## Reference Syntax in Prompts

Important references must be explicit inside prompts:

`Character [NAME] (reference image: [URL]) is in location [NAME] (reference image: [URL]).`

If multiple 360 references exist, choose the reference matching the shot angle and location zone.

## Still Generation

Generate stills before video.

Still stage locks:
- composition
- geography
- identity
- wardrobe
- hand safety
- clean start frame for motion

Default still policy:
- **Nano Banana 2** — default for complex staging, multiple characters, reflections, difficult continuity, style consistency
- **Wan 2.7** — only when Dmitry explicitly wants Wan or when the scene is simple/cheap enough

## Video Generation

Use Kling O3 PRO reference-to-video unless a project proves a better route.

One generation should usually express one dominant beat/action.
Always specify:
- motion tempo
- start state
- end state
- character action
- camera behavior
- continuity constraints
- negative constraints

## Evaluation

If a shot fails, classify the failure first:
- identity
- staging/geography
- location readability
- emotional tone
- motion tempo
- camera logic
- hand/prop anatomy
- reflection/mirror logic
- sound/lip sync
- montage continuity

Fix the failed layer instead of rewriting everything blindly.

## Music

Music workflow is intentionally not part of the default production path yet. Use music references only if Dmitry explicitly asks.

## References

- Project layer rules -> `references/layers.md`
- Project setup / tech bible / ref workflow rules -> `references/project-setup-rules.md`
- Production roles -> `references/production-roles.md`
- World and bible schema -> `references/world-building.md`
- Serialized drama schema -> `references/serialized-drama-schema.md`
- Profiles and current project notes -> `references/profiles.md`
- Prompt and motion rules -> `references/prompt-rules.md`
- Editing rules -> `references/editing-rules.md`
- API details -> `references/atlas-api.md`
- Seedance rules -> `references/seedance-prompting.md`

## Storage

- Workspace: `/home/kira/.openclaw/workspace-video-producer`
- Canonical projects root: `/home/kira/Documents/kira-vault/projects`
- Local projects entrypoint (symlink): `/home/kira/.openclaw/workspace-video-producer/projects`
- Template: `/home/kira/Documents/kira-vault/projects/_template`

All project bibles, refs, scene packets, shot logs, and production notes should live under the vault root so they are visible in Obsidian.
- Skill: `/home/kira/.openclaw/workspace-video-producer/skills/video-producer`