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/hook-compatibility.md
View on GitHub# Human version
A new opening must lead into the body's real proof and payoff. A compatible hook test stays local to the opening; a new promise needs a script and body proposal. Compare complete videos before choosing.
Use the `render-hook-replacement` skill when it is actually available; this guide adds the editorial decisions, not a second renderer.
---
# Agent version
## Check availability and meaning before spending
Fetch the current hook package and read its scripts and config; record its version and hash. A not-found answer blocks that route (a local checkout is not proof it is served): keep the proposal and offer an ordinary recut only as an explicit changed plan.
Freeze the exact original (version, checksum) and study its whole body, speech, captions and ending. Save its promise, buyer, mechanism, proof and payoff. Each opening idea names its hypothesis, what changes and how it links into the kept body.
| Classification | Decision |
| --- | --- |
| Same promise and proof, new opening treatment | Test the opening alone and keep the exact body. Measure a safe hook boundary; use the replacement package's preflight. |
| New promise, buyer, mechanism or outcome | Name the body beats that no longer support it and propose script or coverage changes first; return to the script and design steps and label the result a broader recut. Never splice in an incompatible hook. |
| Same words, changed picture, action or audio | Review the new opening's meaning anyway; a restyle can imply a different benefit with an identical transcript. |
Example: "Know where to spend the next dollar" needs budget-guidance proof; a body showing only a report export does not support it.
## Shortlist, render and compare
1. Sketch up to three cheap options inside the approved direction, each with hypothesis, body fit and added cost. Keep explicit user copy.
2. Run the package's free preflight on the exact source, cut points and captions before paying. Keep the original; label candidates uniquely.
3. Read the renderer's preservation evidence: body frame order, audio, captions and ending kept; measured duration change; speech and caption boundaries.
4. Listen to and watch every complete candidate across opening, join, body and ending when your tools can, and record `listened`/`watched` only when it happened; otherwise record `measured`. Record the received message, the join, truthful proof, readable text and the checksum.
5. Compare complete variants with the baseline and explain tradeoffs. Save lineage, evidence, perception and the decision in version history. No overwrite, no automatic selection.
Missing evidence or unresolved compatibility leaves the review incomplete; concept changes return to script or production. Audience performance stays unknown until real attributed results exist.
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 |