# Micro-Drama Studio in Kolbo Chat

Use this guide for planning, writing and revising a vertical drama series in a chat without production tools. Kobi Act and MCP agents use `references/workflows/micro-drama.md` and load its stage files as they work. These are two surfaces of the same workflow.

## Start with the series

Carry forward decisions already made. Ask only for missing premise/genre, episode count and length, aspect ratio, language, visual style and budget. Suggested starting shape: six episodes of 45–90 seconds in 9:16. Never turn defaults into user requirements.

Build a series bible with logline, dramatic engine, world, cast, relationships, locations, visual style, wardrobe/prop continuity, season outline and house rules. Each episode needs an immediate hook, a character goal, an obstacle, a reversal and a consequence that pulls viewers into the next episode. Establish concrete actions and readable stakes rather than explanatory monologues. Preserve the user's creative direction and approved script lines through revisions.

## Write and prepare

Write each episode as playable beats and dialogue before shot prompts. Track each character's look and emotional state by episode; changes of wardrobe, damage, time or location must be explicit. Keep recurring identities distinct from those states. Reuse approved project cast and Visual DNA names exactly, including non-English names.

Lock cast sheets, locations and voice samples before production. Main characters need enough face, wardrobe and expression coverage for close-ups. Use Kolbo's existing sheet presets and Visual DNA workflow when tools are available; do not claim a sheet, voice, DNA or project was created in a text-only chat.

Compile each part into self-contained shots with timing, visible action, blocking, framing, dialogue and sound. Match each line to its speaker. Keep screen direction, eyelines, props, lighting and acting continuous between shots. Shots must fit the selected model's live duration and prompt limits; never quote remembered identifiers or prices as current. Use the model's own prompt contract when writing a runnable generation prompt.

## Produce with approvals

The production route blocks episodes in Seedance 2.5 Draft, reviews the first part before the remaining parts, then finalizes only approved keepers. Confirm current language, model, resolution and Draft support before generation. Explain any speech limitation and agree on native speech or an audio/lip-sync route before spending.

Approve the concept/season, each new character and voice, the credit cap, and each tight episode cut. A cap does not authorize finalization: quote each finalization from the live tool and obtain explicit approval for that amount. Preserve approval state on follow-ups. A content-policy refusal is not a technical failure to retry. Never claim render completion, QA, credits spent or saved files without tool receipts.

## Edit and deliver

Review identity, physical action, dialogue, lip sync, continuity and pacing. Fix the smallest failed piece, with at most two retries before reporting the unresolved issue. Keep every approved line once and in order. Cut on shot boundaries, avoid flash frames and same-angle jumps, preserve meaningful reaction pauses, and smooth room-tone seams. Music is optional and must not obscure dialogue. Preserve source frame rate unless the user asks to change it.

Deliver the approved episode, then its trailer, social cuts and key art as requested. Put episode numbering and promotional calls to action in post captions. Record user corrections in the bible's house rules. In text-only Chat, deliver the bible, scripts, shot prompts and edit instructions; offer Kobi Act for execution. Publishing remains the user's decision.