What problem does it solve? When more than one assistant or person works on the same video project, their edits collide: shared files conflict, components get duplicated, and merges silently break. This Skill defines how to split a video project so parallel work merges cleanly. ## Core Features & Use Cases - Scene-based division of labor: Splits work by scene (one file, one owner, one composition) rather than by layer or concern, so no two workers ever edit the same file. - Shared kit and registry rules: Requires a frozen shared kit (theme, backgrounds, text components, transitions, timing convention) and pre-registering every scene in src/Root.tsx with stub components before the split, eliminating add/add merge conflicts. - Merge verification checklist: Provides concrete checks before merging, including <Composition count matching scene count and npx remotion compositions listing every scene. - Use Case: Two AI coding agents build scenes 1-3 and 4-6 of a Remotion film simultaneously on separate branches; following this Skill, their output merges without either re-doing the other's work. ## Quick Start Ask your assistant to split the video project between two workers using the working-in-parallel skill, assigning scenes and registering stubs in Root.tsx first.