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

brainstorm.md

View on GitHub
---
name: video-production-harness/brainstorm
description: Refine a fuzzy ad concept into a structured idea brief. Acts as a sharp creative thought partner — challenges generic openings, pushes for specificity, and produces idea_brief.
---

# brainstorm

Follow the [orchestrator](orchestrator.md)'s host contract and [creative contract and review](references/creative-contract-and-review.md).

## Purpose

Turn a rough pitch into a tight idea_brief that later steps can execute. No assets are generated here.

## Inputs

- The user's rough concept (a paragraph to a page).
- Brand assets and evidence, when available.
- Any reference video or competitor ad mentioned.

## Workflow

1. **Study the reference**, picture and sound, per the creative contract. Log timestamped beats and map them to the adaptation's words, action, proof and sound. Frames and transcripts do not prove listening or motion. With no reference, use inspected brand or category examples or a sourced original concept. A template demo is an option, not an automatic substitute.
2. Note what works in the concept: a relatable protagonist, a before/after, a payoff, quotable lines.
3. Push back on:
   - generic openings ("sad person at desk", "scrolling phone at night");
   - names that pattern-match existing IP (rename or commit fully);
   - beats that *tell* instead of *show*;
   - forgettable end-card CTAs (propose 2–3 alternatives);
   - characters or scenes that add no information.
4. Name the concept's real mechanism and feasible proof. Elapsed-time structure is optional and only when the story supports it; it never overrides the reference or invents results.
5. When the concept is open, offer 2–3 alternatives (reference, opening, product explanation, proof, sound, asset gaps) inside the script review. Keep a concept the owner already chose.
6. Ask one clarifying question if a key axis (audience, brand voice) is unresolved.
7. Write `<output_folder>/idea_brief`, creating the folder if needed:
   - **Concept type**: transformation, demo, testimonial, manifesto or comparison (picks the arc template in State 2.5).
   - A scene table: visual, on-screen text, speech.
   - Hero asset references and the reference beat log.
   - Tone and length targets.
   - **Climax beat**: which line is THE line.
   - Open questions.

## Output and write order

1. Save the idea_brief and every concept candidate through the binding.
2. Each candidate keeps a stable ID, title, format, hook, logline, evidence, risks, status and full prose.
3. Keep an existing owner selection; otherwise carry open options into the script review. Save edited concept copy before that review.
4. Validate the binding's concept fields and show the result on its review surface. A side file the host cannot display is unfinished work.

## Quality checks

- Every scene has a clear visual, on-screen text (or "—"), speech and sound intent, and its action or proof. No-speech scenes have no invented VO.
- Scene 1's hook is specific. The payoff line is quotable. A brand-anchor moment exists.
- Open decisions are listed, not silently locked.

## Failure modes

- A feature list instead of a story arc; scenes with no single dominant action.
- "Ask the user" decisions smuggled in as resolved.
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