Skip to content

gooseworks-ai/goose-skills / skills/video/video-production-harness

video-production-harness

Verified

Full video production sequence with script review, actual ingredient choices, controlled generation, editing, evidence-based quality review, polish, captions and delivery. A host binding supplies project storage, authentic approvals, provider access and billing.

FileKindSize
SKILL.mdskill md6.0 KB
auto-fix-from-review-notes.mdmarkdown6.5 KB
auto-refine.mdmarkdown5.3 KB
brainstorm.mdmarkdown3.2 KB
capabilities.mdmarkdown13.6 KB
create-clips.mdmarkdown15.0 KB
create-design-brief.mdmarkdown13.4 KB
create-storyboard.mdmarkdown8.8 KB
edit-clip.mdmarkdown6.4 KB
edit-video.mdmarkdown12.8 KB
lock-character.mdmarkdown12.2 KB
lock-script.mdmarkdown8.7 KB
orchestrator.mdmarkdown10.9 KB
polish.mdmarkdown9.2 KB
preflight-audit.mdmarkdown6.2 KB
promote.mdmarkdown3.2 KB
references/check-severity.mdmarkdown9.7 KB
references/creative-contract-and-review.mdmarkdown11.4 KB
references/creator-grammar.mdmarkdown6.7 KB
references/editorial-review.mdmarkdown6.4 KB
references/genres/ai-creator-ugc.mdmarkdown2.7 KB
references/genres/chat-ui.mdmarkdown2.2 KB
references/genres/hypermotion.mdmarkdown1.4 KB
references/genres/motion-graphics.mdmarkdown1.5 KB
references/genres/narrator-montage.mdmarkdown3.1 KB
references/genres/product-demo.mdmarkdown2.0 KB
references/hook-compatibility.mdmarkdown2.8 KB
references/libraries-look-and-rubric.mdmarkdown6.0 KB
references/product-scale-and-world.mdmarkdown4.2 KB
references/quality-tier.mdmarkdown9.4 KB
references/recipe-format.mdmarkdown7.1 KB
references/review-script-shortform.mdmarkdown11.7 KB
references/shot-routing.mdmarkdown14.9 KB
references/specialist-handoff.mdmarkdown4.7 KB
references/speech-and-route-qualification.mdmarkdown10.1 KB
references/talking-actor.mdmarkdown6.6 KB
release.jsonconfig22.1 KB
review-video.mdmarkdown15.0 KB
scripts/assemble.pyscript11.1 KB
scripts/assemble_sources.pyscript5.7 KB
scripts/assembly_timeline.pyscript11.4 KB
scripts/check_recipe.pyscript9.6 KB
scripts/final_grade.pyscript2.9 KB
scripts/final_measure.pyscript14.1 KB
scripts/final_measure_parts.pyscript14.6 KB
scripts/pack_recipe.pyscript11.3 KB
scripts/qc_evidence.pyscript15.0 KB
scripts/reference_rate.pyscript4.3 KB
scripts/reference_shots.pyscript13.1 KB
scripts/timeline_rules.pyscript10.8 KB
skill.meta.jsonconfig820 B
states/edit-to-delivery.mdmarkdown8.2 KB
states/setup-and-script.mdmarkdown10.8 KB
states/storyboard-and-clips.mdmarkdown8.1 KB
wrap-session.mdmarkdown5.9 KB

states/storyboard-and-clips.md

View on GitHub
---
name: video-production-harness/states/storyboard-and-clips
description: States 3 to 6 of the shared video production sequence — storyboard and ingredient gate, motion strategy, character and world lock, preview, clip creation and clip repair.
---

# Human version

The middle of the run: plan every scene, approve the ingredients, lock the people and the world, try a small preview when a route is risky, then make and repair the clips. The ingredient approval happens here.

---

# Agent version

Part of [the orchestrator](../orchestrator.md). Its non-negotiables, approvals and decision policies apply. Read one file per call; if the output says it was truncated, re-read it in parts before acting.

### State 3 — Storyboard
1. **The storyboard is required, even when the owner pre-approved the script, credits or ingredients.** Pre-approval skips the wait for the owner, never the storyboard or its checks. Reuse a saved storyboard only when it matches the approved script and shot plan.
2. Follow [create-storyboard.md](../create-storyboard.md). It reads VO from `locked_script`, so caption text matches the script.
3. **INGREDIENT OWNER GATE.** In `review_mode: auto`, when the total is still inside the customer's yes, record the approval with their "just make it" words and go on without waiting ([check severity](../references/check-severity.md)). Otherwise show the storyboard on the host review surface with the anchors, world, voice, product photos, routes and cost. Show each speaking character's still together with a short audition of its paired voice saying a real script line, so the owner judges them together. A native-speech character (one H3 take speaking its own line) has no separate voice: show the still and the route now, and accept or reject the generated voice with the first take, before any later take. A separate voice is approved only with its person: while a still is pending or blocked, its voice stays pending too, and a final selected audition whose voice differs from `character.voice_pair` is not shown for approval. Unresolved voice candidates carry their own paired ID/settings; after the customer picks, save that choice as `character.voice_pair` before ingredient approval. Voice-reference native speech retains that pair and audition; the no-pair rule above is for unconditioned speech. Confirm pacing and visual direction before clip credits. A generated preview still needs the approved preview budget. This is the cheapest place to catch a wrong concept. On the kit path, run the kit's make command after this approval.
4. **Coverage and pace.** Use reference-derived targets and the planned cuts and face time from the storyboard step. Every beat needs a viewer purpose and enough time for its action, reading or proof. A long hold is a prompt to check, not a failure; never add arbitrary cuts to meet a quota.
5. **Shot-mix check before any clip spend.** Run the storyboard's pacing and shot-mix diagnostics and `scripts/reference_shots.py compare` against the reference's shot table, and show the counts. Setups or shots more than 30% under the reference with no listed `shots` change are an `ask` finding ([check severity](../references/check-severity.md)): add shots, or list the change and tell the customer; in `review_mode: auto` decide yourself. It never blocks State 5.

### State 3.4 — Motion strategy
1. Read the design brief's `visual_style:` (and explicit storyboard notes).
2. Write `motion_strategy` into `project_state`:
   - `generative_video`: photoreal, real performance, products in use. Each shot uses its row in [shot routing](../references/shot-routing.md).
   - `ffmpeg_motion`: editorial illustration, 2D, halftone, paper and ink. FFmpeg zoompan over each approved still with hard cuts. **No generative video**: it invents photoreal middle states.
   - `hybrid_remotion`: kinetic type, motion graphics, data viz, from the browser-rendered rows.
3. No pause when `visual_style` is clear. If the brief lists several styles, ask at the ingredient gate.

### State 3.5 — Character lock
1. Skip when there is no recurring person or a current, complete `character_locks` (anchor, angles and the Phase 2 check) exists. An anchor made in State 2.6 and picked at the ingredient gate continues at Phase 1.
2. Otherwise follow [lock-character.md](../lock-character.md) with `<character_descriptors>` from the design brief.
3. Show anchor choices inside the ingredient review. Record real identity evidence, not invented drift percentages.
4. After lock, `character_locks` is the contract create-clips reads for every scene's references.
5. **Chained references.** `character_locks` records `chain_strategy`: `"anchor-only"` (only the anchor goes to each call) or `"all-locked-frames-as-refs"` (the anchor plus every approved keyframe). Use the second for series where consistency across many frames matters (decline arcs, ping-pong loops, before/after pairs).

### State 3.55 — World lock
1. Run when the content has a continuing world, a recurring person or a scale-critical product, whatever the format label.
2. Read the required set, wardrobe, lighting, grade, recurring props and time of day. Missing constraints block this phase. Preserve the approved world: a phone, studio, cinematic or animated format keeps its own capture, focus, light and texture ([libraries, look and rubric](../references/libraries-look-and-rubric.md)).
3. Reuse suitable existing world and product references. Generate only the missing views needed for scale, placement or detail; there is no fixed quota.
4. Register candidates with stable world ids and provenance; show open choices in the ingredient review. A replaced world invalidates the ingredient approval.
5. Every later character keyframe sends both the identity anchor and the matching world references, with the descriptors verbatim in the prompt.

### State 4.5 — Representative preview (optional)
1. Use it when an unproven creator or action route, or another production risk, needs evidence before the full batch. It is an agent check inside the approved preview scope.
2. Skip it only when accepted evidence already covers the same endpoint, product, action and inputs. A short duration alone does not qualify a speaking or difficult-action route.
3. Pick scenes that test the riskiest parts: the main character and framing, a stylistically different beat such as the climax, and any difficult product action.
4. Use the real intended endpoint. A cheaper tier may test a layout but cannot qualify another route's voice, sync or product handling.
5. Review the preview with sound before batching: framing, wardrobe and identity across cuts, appearance, light, world and product geometry, and music sync at the climax. Grade matching later cannot repair identity, anatomy or action.
6. **Iterate cheaply.** Fix category-level problems inside the preview's small scope; aim for one preview iteration before the full batch. Show open look or voice questions in the existing owner reviews.

### State 5 — Create clips
1. Reuse clips only when scene ids, exact inputs, approvals and job results match the plan and no clip has an open `must_fix` (`ask` and `fine` clips are kept).
2. Re-run [preflight-audit.md](../preflight-audit.md) as a sub-step; new assets may have landed.
3. Check the specialist package handoff and free dependencies, then follow [create-clips.md](../create-clips.md). It reads `character_locks` and sends the locked anchor into every keyframe.
4. Phase 0 of create-clips keeps the style anchor for cartoon scenes; for people the lock-character anchor already covers it.
5. Inspect every clip, its speech and its action before assembly. A clip with an open `must_fix` is redone (paid from the approved total when it fits, otherwise after a new yes), never dropped; `ask` and `fine` clips go in.

### State 6 — Edit clip (loop)
1. Read the latest review notes for `must_fix` (P0) items mapped to scenes, and the `ask` (P1) items the customer, or you in `review_mode: auto`, chose to fix.
2. For each scene that needs a re-roll, follow [edit-clip.md](../edit-clip.md) with the note's `edit_type`.
3. Run sequentially; each edit changes state and may invalidate the next.
4. With no review notes yet, go to State 7; the first edit uses the raw clips.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall