gooseworks-ai/goose-skills / skills/video/video-production-harness
video-production-harness
VerifiedFull 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.
references/specialist-handoff.md
View on GitHub# Human version
Keep the approved brief intact when a specialist makes a scene: fetch the real package, prove its tools work, pass exact sources and timings, check what comes back, and reuse valid work after an interruption.
---
# Agent version
## Select and bind before execution
Read the fetched package, its dependencies, version/hash and the real tool schemas; save its identity in the capability plan. Presence is not readiness: run free checks from its documented cwd (media probe, CLI dry run, fonts, a real browser launch when selected). A missing dependency blocks that route before any paid call. A helper that cannot carry project billing cannot do paid work.
Fetch current slugs; these are starting points.
| Family | Package to inspect | What comes back and what to check |
| --- | --- | --- |
| Realistic generated talking actor | [Talking-actor method](talking-actor.md), and talking-actor specialist when available. Check managed transport and the exact voice-reference interface before paid work. | Three new actor choices only when needed, actual script auditions, a selected pair, native performance compared with its voice reference, and exact-byte clip review. |
| Exact-script UGC creator | `creator-h3@1.8.0` on the kit path; the `create-creator-takes-h3` skill 2.9.0 (superseded; agent-built path; its make_character.py pairs the voice, `--no-voice-pair` for native speech, pair_voice.py `--library-searches`, `--designed` and `--accept-nearest`, with `nearest` across heritage when none shares it; take reviews may be measured). Inspect its first_take, remaining_takes and assemble schemas; `run_takes` defaults to dry run. | The first take stays pending until hash-bound acceptance; assembly needs reviewed sources and real word timing. |
| Product demo from owned media | The `footage-cutlist` skill: survey, preview and cut take sources and beats with source/in/out/fit/why. | Right variant, visible action during the claim, crop, source time mapping, real duration. A diagram or claim card is not feature proof. |
| Branded graphics and motion | The `goose-graphics` skill gives HTML/static composition, not a video renderer. Add a motion capability or the FFmpeg motion path for approved stills. | A rendered motion clip and timeline, exact text/logo, font, safe space, reading time. A PNG export is not a video. |
For creator plus product footage, the `compose-creator-layer` skill may combine checked tracks. No fixed face share or cut count; motion-only scenes skip voice and creator dependencies.
When the video shows work made by a product, use actual outputs from that product/workflow. For static ads, discover the host's static-template/remix capability, ground it in the real brand/product and quote each operation. Generic mock cards or frames borrowed from this video's own footage cannot prove that the product made ads. Inspect full-size text, logos and product fidelity; save the actual outputs as customer assets. An illustrative mockup is allowed only when that distinction fits the approved brief.
## Handoff checklist
Record before each specialist runs:
- Brief revision, product/variant, supported claims and locked copy. The same brief reaches writer, planner and renderer.
- Approved script revision, exact lines and on-screen words, scene IDs with start/end; planned versus measured timings.
- Asset/take IDs, checksums and excerpt ranges, apart from style references.
- Voice or native-dialogue strategy; never a second narrator over native speech.
- References, crop, ratio, text space and neighbour requirements.
- Package slug/version/hash, tool and model, approval revision, budget.
- Expected outputs: media, editable sources, measured timings, job provenance.
Review the output against the creative contract and these inputs, not the specialist's success status. Probe the bytes; check duration, copy, proof, action, product, scale and identity; listen to each spoken output when your tools can, otherwise record `measured`. Save pass, needs_revision or incomplete per duty, graded by [check severity](check-severity.md). A stale source or unconfirmed provider URL (broken data) blocks assembly; a missing word or wrong variant is `must_fix`; a wrong beat is `ask`.
## Resume and repair
Load saved state and match fingerprints, approvals and completed jobs. Run only missing or invalid work; some helpers skip any existing filename, even bad bytes, so validate first. Never regenerate every scene because a process restarted. Poll unresolved jobs before a retry. A changed direction, provider, input or cost goes back through the affected approval. A missing motion dependency gets a compatible plan (a still plus a local pan); never spend hoping it works.
## Acceptance boundary
A dry run or local artifact never proves paid generation, approval or a served end-to-end run.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |