---
name: ugc_creator_briefs
description: Writes complete, ready-to-send briefs for UGC creators from brand and product inputs. Covers hook lines, shot lists, do and don't reels, compliance claims, deliverables, revision policy, and usage-rights buyout terms. Use when booking creators, turning a campaign idea into shootable direction, or reviewing a draft brief for gaps.
metadata: { "includeInPrompt": true }
---

# UGC Creator Briefs

## Purpose
Turn a campaign idea into a single written brief a creator can shoot from with no back-and-forth. The brief gives structure (hook, beats, shot list, do/don'ts, rights window) and leaves the performance to the creator. Never a vibe doc, never a line-by-line script.

## Workflow
1. Collect inputs. Required before drafting: brand, product, campaign goal, platform(s), 1-3 concept angles, and the approved claims list. If any are missing, ask for them or mark the brief DRAFT and list what is missing.
2. Write one concept block per angle: angle name, one-sentence big idea, 3 hook variants (exact words, said or on-screen in the first 2 seconds), a shot list with times/visuals/beats, one CTA. Talking points, not scripts.
3. Write the do list and the don't list. Put banned claims and banned behaviors here, each with a reason. No filler lines.
4. Write the usage-rights window as one explicit sentence: where it runs, from whose account, in what form, which geos, for how long, and what is excluded (Spark, whitelisting, dark posts are separate deals and never implied). See `references/rights-buyout-guide.md` for the tier ladder and window language.
5. State revision policy in writing: rounds included (1-2 is standard), what a revision covers (brief compliance only, not new concepts), how requests arrive (specific, consolidated, in writing), and the approval window. State payment terms, deliverables spec (format, naming, raws included), and the FTC disclosure line the creator must use.
6. Render it. Either fill `references/brief-template.md` by hand or run the renderer:
   ```
   python3 bin/render_brief.py --input brief_inputs.json --out brief.md
   ```
   The renderer validates required fields and errors out on gaps instead of guessing.
7. Self-check: would a creator be able to shoot this tomorrow with zero clarification questions? If not, fill the gap.

## Output Contract
The skill outputs one Markdown brief file plus a one-line coverage report. The report confirms: number of concepts, hooks per concept, usage-rights window sentence present, revision rounds stated, disclosure line present. Anything missing is named, not papered over.

## Operating Rules
1. Every factual claim in the brief comes from the brand's approved claims list or a verified source. Never invent numbers, dates, prices, or performance stats. Unverifiable claims get cut or are labeled as opinion.
2. Hooks are the exact words. If the words are regulated, the hook is the approved sentence or there is no hook.
3. Brief structure, not scripts. Over-directing produces content that reads as an ad and kills the native feel that makes UGC perform.
4. Name the music source (supplied track or licensed commercial library). Never brief "trending audio", it kills paid usability on copyrighted tracks.
5. The rights window in the brief and the rights window in the contract must say the same thing. If they disagree, stop and resolve it before the brief ships.
6. Rejected directions go in the don't list with a reason, so a second creator does not revive a killed idea.
7. One brief per batch of named hooks. "Deliver three videos" with no named openings gets three unrelated videos; three named hook lines with the same SKU get a testable set.