Skip to content

gooseworks-ai/goose-skills / skills/video/write-video-ad-script

write-video-ad-script

Verified

Write or revise a short-form ad from a sourced angle and reference. Plan connected words, product proof and sound; expose production gaps before script review.

references/creative-brief.md

View on GitHub
# The creative brief

_Step 2 of write-video-ad-script, in full._

Read current product/variant evidence from the connected Brain/brand tools and the
project's saved history **before drafting**, using their existing scopes and IDs. The
angle bank supplies research; it does not silently override a newer user direction,
offer or variant. Read the actual source behind each material field and retain its
pointer/revision. Reuse answered questions. Surface only unresolved conflicts that
change the promise, execution or spend at the existing review boundary.

Save the concise current-run `creative-brief.json` described in the files reference.
Keep approved product facts separate from customer language and authored direction.
Record the exact variant, buyer situation, supported mechanism, objective, offer,
CTA, constraints, relevant previous decisions, locked words and delivery intent.
An absent offer is explicitly “no offer supplied”; an unknown claim or variant is
a gap, not a default. Retrieve prior rejected wording with its reason and scope;
carry project-specific taste only when it applies to this run. Do not turn it into a
standing brand rule. The existing history file remains the durable record.

Pass this brief to `prepare_angle_context.py --brief …`; it travels inside the
existing angle-context to lint, the critic and production. New custom and template
runs set `requires_creative_brief: true` in their shape. Older saved contexts remain
readable; enrich them before a new production run instead of inventing provenance.
If a fetched preparation rejects `--brief`, stop and refresh the writer through the
existing release flow; do not drop the argument or its strict requirement. The files
reference's `verify_handoff.py` smoke tests the actual saved package before release,
including a missing-brief rejection and legacy compatibility. A source merge alone
does not establish that a connection serves those scripts.

Load [buyer perspective and product explanation](buyer-and-mechanism.md).
Use the current campaign's consumer role and a concrete task or decision. Map what
the buyer supplies or does, what the offering does, what they receive and why it
helps here. That connection must survive in the actual words or feasible actions;
neither a private brief nor a benefit label can explain it for the viewer.

For each eligible angle, write a compact brief:

- One audience in a recognizable situation, and its awareness or buying context.
- One promise that matters, and why this product can credibly deliver it.
- The mechanism or differentiator, supported facts and one feasible proof device.
- The desire, identity, tension or objection the story uses. Pain is optional.
- The offer, CTA, visual opening and payoff, within the selected format.

Establish this message **before selecting the reference or locking a street interaction
subtype**. State what the viewer should understand and why that matters to the objective.
A supported preparation detail is not automatically a reason to choose the product. Do
not reshape the audience or buying concern to fit an available example. If an internally
generated angle has no useful brand message, return to the angle research; if the user
selected it, preserve that choice and flag the concrete weakness rather than silently
changing it.

Buyer language improves relevance and voice. It is not a mandatory plot and does not
substantiate the brand's claims. Competitor complaints suggest a research question; they
do not establish that this product fixes it. Quotes may be attributed as real quotes when
appropriate, never recast as an invented narrator's own purchase or result. Fictional
scenes must not masquerade as genuine interviews, reviews or customer experience.

Reuse collected quotes and history before collecting more. Store verbatim quotes with real
sources and their product/competitor scope. A product-led demo or launch may have no quotes;
verified facts and a strong feasible demonstration are valid foundations.
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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated 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: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall