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/genres/hypermotion.md
View on GitHub# Hypermotion
Fast product hero motion cut from one product clip, with spec cards between the shots. Routing rows are named as in the shot-routing guide.
## Shot list skeleton
1. 0-1.5 s intro card, one or two words.
2. 1.5-4 s crash zoom from wide to the product.
3. 4-5.5 s hero spec: the strongest brand-stated number.
4. 5.5-20.5 s five clip windows (orbit, slow-motion air effect, pull-back, stillness) between four 1.5 s spec cards.
5. 20.5-22 s CTA card.
6. 22-25 s the real logo lands and keeps moving.
## Routing rows
Hypermotion product · Kinetic type / motion card · Music · End card.
## Pacing
- 25 s and about 14 hard cuts; windows shrink from 2.5 s to 1.5 s.
- Every window is cut from one 15 s product clip. Music from the first second, about 120 BPM, drop near 20 s.
- Several products: about 6 s wide plus 4 s close each, 25-30 s for three.
## Nearest template
`product-hypermotion`
## Top 5 failures and fixes
- The product morphs mid-clip → one camera move per beat; end the prompt with locks: shape, label, one product, no hands.
- Shake on the product warps it → put the physics in the air around it (dust, shimmer, spray).
- Every clip turns macro → open the prompt with "product small, setting dominant".
- A studio end frame snaps the scene to blank → match the end frame to the setting, or trim before it.
- The end card freezes → keep held text moving slightly (about 1% scale, a few pixels of drift).
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 |