video-annotation-review
Video annotation review
Use this skill when Framebrief annotations are the human review surface. Read VIDEO.md at the active workspace root before selecting a renderer. Then read the project, annotations, and attached annotation images through WebMCP.
Before opening a review, ensure the Framebrief CLI is available globally. If framebrief is not on PATH, run npm install -g framebrief. Check the installed version with npm ls -g framebrief --depth=0 and the published version with npm view framebrief version; when the registry has a newer version, upgrade with npm install -g framebrief@latest. Verify framebrief --help before continuing. If the registry cannot be reached, report that the update check was unavailable and use the installed CLI only if it works.
If VIDEO.md is missing or its brief is draft/incomplete, ask only for the missing production decisions: goal, output format/duration, visual direction, source rights, and explicit authorization for any external provider. Create or update VIDEO.md, then synchronize the same complete brief with update_video_project_brief. Never store or echo API keys; record only provider/model, authorization, and whether a key is configured.
New project preview
For a newly created video project, do not render the complete target first. Once the goal, style, format, target duration, and required provider permissions are known, build the production source and render an initial 10-second preview (or the full duration when the requested video is shorter than 10 seconds). The preview should demonstrate the actual opening, visual language, typography, motion, pacing, and representative media treatment intended for the final video. It is a production sample, not a separate throwaway concept.
Validate the preview, register it as the current rendered media in video.review.json, open it in Framebrief through Codex's integrated browser, and use the review gate below. Record the preview path and its status in VIDEO.md; do not list it as the final output.
If the submitted preview review contains annotations, apply them to the editable source, render an updated preview, consume the processed annotations, and reopen Framebrief for another review. When the user completes a review with no remaining adjustments or explicitly says the preview is satisfactory, ask whether they are ready for the complete target-duration render. Start the complete render only after that explicit confirmation. Reuse the approved source and direction so the full version remains consistent with the reviewed preview.