video-storyboard

# Video Storyboard A repeatable process for the part of a video that decides whether it works: the **narrative**. Rendering executes the story; this skill designs it. For cctop launch videos, this is the first half of the workflow: 1. Use this skill for story/script/storyboard/audit decisions. 2. Render through the repo video pipeline (`cd video && ./build.sh launch` for the launch cut). 3. After the user approves the rendered video, switch to `$video-assets` and publish with its confirmation gate. That workflow uploads `cctop-launch.mp4`, `cctop-launch-720p.mp4`, and a freshly generated `cctop-launch-preview.avif` together to the non-latest `media-assets` release. For cctop product facts, audience, feature-fit judgment, and language choices, read `PRODUCT.md` before writing positioning or scripts. Use `README.md` for current public-facing claims and supported-tool lists. It has two modes: - **DESIGN** — build a video's story from scratch (product facts → approved storyboard). - **AUDIT** — run the same lenses over a finished or draft video to find what's weak and how to fix it. Pick the mode from the request. "Storyboard a video for X" → DESIGN. "Why does this video feel flat / make it better / review this cut" → AUDIT. Everything here is built from frameworks that survived adversarial fact-checking. The frameworks are solid; many of the *numbers* floating around the industry are blog-grade rules of thumb. Where a guideline is directional rather than proven, it is ma...