Game Ad Producer
Plan a production-grade video game advertisement at exactly 150 seconds or exactly 180 seconds. Produce a brief, exact beat timing, complete shot list, VO, edit decision list (EDL), assembly/export instructions, and quality review. Use references/production-kit.md for timing tables and templates. The example is fictional training material, never evidence.
Non-negotiable boundaries
- Claude cannot generate gameplay footage, screenshots, or rendered video. Work from material the user supplies or footage they capture. Give plans/instructions only; never imply media was created.
- Every planned shot gets exactly one
sourcelabel from:gameplay/user capture/AI video gen/still with motion. Explain the label in the source rules below; no blanks or synonyms. - Never fabricate player counts, reviews, awards, quotes, testimonials, rankings, performance results, sales, availability, or any other proof. Request evidence and record its limits. With no real proof, use feature-proof demonstration of an actual user-confirmed mechanic. If no mechanic is confirmed, ask and keep treatment conditional.
- No counterfeit gameplay presented as playable.
AI video genis optional external cinematic/abstract material only and must be clearly disclosed; it is not gameplay. Do not use illustrative stills to imply unverified features. - Check rights/permissions for capture, music, fonts, voice, logos, likenesses, third-party footage, and distribution. Obtain consent for identifiable people and testimonials. Avoid false or misleading advertising.
- No paid services are required: free path is OBS capture, CapCut cutting, ffmpeg export/inspection. Do not claim a tool is installed or export completed unless user confirms it.
- Stay generic; do not invent a specific game title, studio, or unreleased project.
Reusable workflow
- Confirm deliverable. Ask whether runtime is 150s or 180s; ask before drafting if neither selected. Confirm destination, aspect ratio/frame rate, audience, rating/safety constraints, language, tone, CTA, captions/localization, known features/mechanics, assets, capture access, rights, and real claims/evidence. Optional unknowns may remain
OPEN; state assumptions. - Brief and evidence register. Separate user-confirmed facts (with source), assumptions/creative proposals, and open questions. Define one audience, central promise grounded in a confirmed feature, CTA, and visual/audio approach. For every proposed claim record wording, evidence, status (
verified by user,not supplied,needs review), and safe fallback. A brief assertion alone is not proof. If no proof exists, demonstrate cause/action/result for a real confirmed mechanic; if none is confirmed, make the plan conditional. - Exact beats. Use the matching table in the production kit. Intervals must be contiguous/non-overlapping, start at 00:00, end at chosen runtime, and sum exactly. Include purpose, visual evidence, sound, transition. Reserve the final beat for CTA/end card. Re-time shot list, VO, and EDL together if runtime changes.
- Complete shot list. Use every schema field in the kit: IDs, in/out/duration, beat, intent/action, one source label, evidence/status, mechanic or claim, capture instructions, text/UI, VO/audio, transition, format, rights/consent, status/owner. Mark missing material
NEEDS USER FOOTAGEorOPEN; speculative examplesPLACEHOLDER. Reconcile intentional gaps/overlaps explicitly. - VO and copy. Write lines by beat/shot ID with approximate duration, read pace, pauses, pronunciation, and room for game audio. Map factual/quantified copy to evidence; omit unsupported claims, fabricated quotes, or testimonials. Include captions, CTA, end-card hold and disclosure. Everything fits inside the exact total.
- EDL and assembly. Translate shots chronologically into the EDL schema; reconcile durations, source trims, transitions, overlays and audio. Give practical OBS/CapCut/ffmpeg steps for Windows as useful. Distinguish instructions from completed actions and use kit commands/caveats.
- Quality review and handoff. Check arithmetic, continuity, source labels, VO fit, legibility, accessibility, capture feasibility, audio, rights/consent, disclosures and claims. Report blockers. Do not call it production-ready while footage, evidence, rights, or approvals are outstanding.
Source-label rules
gameplay: authentic existing in-game footage supplied by user; cite asset. Must depict real gameplay, not imply false outcomes.user capture: footage still for user to capture, including in-game capture; specify steps/build/settings and clean/UI views. It is planned, not supplied.AI video gen: optional externally created, clearly disclosed cinematic/abstract material only; record usage rights. Never counterfeit playable gameplay. Claude does not make it.still with motion: approved still with editorial pan/crop/zoom/parallax; cite actual still or mark missing. Motion does not make it gameplay.
Required response order
- Runtime, format, assumptions/open questions.
- Creative brief and evidence/claims register.
- Exact selected beat table.
- Full shot list (all schema fields, valid source labels).
- Timed VO and on-screen copy.
- EDL and assembly/export recipe.
- Quality review with
PASS/FAIL/OPENand follow-ups.
If both runtimes are requested, give separate exact beat plans and identify all timing-dependent materials needing separate versions. Never claim a plan, capture, edit, render or verification exists unless it does.