Product Ad Video Script
Use this workflow when the user wants to turn a product, landing page, offer, screenshot, or rough idea into a short ad video plan and script.
Use this workflow to plan the ad first, then execute only the assets and edits the chosen script actually needs.
When to Use
- The user provides a product, product page, app, feature, screenshot, or offer.
- The user asks for ad copy, hooks, UGC script, promo video, product reel, launch video, or short-form marketing video.
- The task needs angles, scene structure, captions, CTA, and visual treatment.
Workflow
- Read the product context: what it is, who it is for, core benefit, proof, offer, limitations, and required claims.
- Extract or infer the customer problem, desired outcome, objections, and strongest differentiator.
- Pick or propose 2-4 ad angles using references/ad-script-framework.md.
- For the chosen angle, write a concise video structure: hook, problem, demo or proof, benefit, objection handling, CTA.
- Map each beat to required visuals using product/page assets or user-provided media. Generate new visuals only when the script needs them.
- Create the timeline or present the script first depending on the user's intent.
- QA claims, readability, pacing, CTA clarity, brand fit, and whether the first seconds explain why the viewer should care.
Rules
- Ground claims in the product page, user notes, or visible assets. Do not invent prices, guarantees, medical claims, revenue claims, or endorsements.
- Prefer clear benefits over feature lists.
- Keep hooks concrete and viewer-facing.
- If required information is missing and affects truthfulness or positioning, ask or label the assumption.
- Match the visual plan to what OpenChatCut can make now; do not prescribe external-only steps unless the user asks.
- Do not add transitions, effects, music, or voiceover unless the selected script calls for them.
Output
For planning, show angle, target viewer, hook, script beats, visual plan, captions, CTA, and assumptions. For execution, also report what was added to the timeline.
1---2name: product-ad-video-script3description: Turn a product into ad angles, hooks, scenes, and CTA.4---5
6# Product Ad Video Script
7
8Use this workflow when the user wants to turn a product, landing page, offer, screenshot, or rough idea into a short ad video plan and script.
9
10Use this workflow to plan the ad first, then execute only the assets and edits the chosen script actually needs.
11
12## When to Use
13
14- The user provides a product, product page, app, feature, screenshot, or offer.
15- The user asks for ad copy, hooks, UGC script, promo video, product reel, launch video, or short-form marketing video.
16- The task needs angles, scene structure, captions, CTA, and visual treatment.
17
18## Workflow
19
201. Read the product context: what it is, who it is for, core benefit, proof, offer, limitations, and required claims.
212. Extract or infer the customer problem, desired outcome, objections, and strongest differentiator.
223. Pick or propose 2-4 ad angles using [references/ad-script-framework.md](references/ad-script-framework.md).
234. For the chosen angle, write a concise video structure: hook, problem, demo or proof, benefit, objection handling, CTA.
245. Map each beat to required visuals using product/page assets or user-provided media. Generate new visuals only when the script needs them.
256. Create the timeline or present the script first depending on the user's intent.
267. QA claims, readability, pacing, CTA clarity, brand fit, and whether the first seconds explain why the viewer should care.
27
28## Rules
29
30- Ground claims in the product page, user notes, or visible assets. Do not invent prices, guarantees, medical claims, revenue claims, or endorsements.
31- Prefer clear benefits over feature lists.
32- Keep hooks concrete and viewer-facing.
33- If required information is missing and affects truthfulness or positioning, ask or label the assumption.
34- Match the visual plan to what OpenChatCut can make now; do not prescribe external-only steps unless the user asks.
35- Do not add transitions, effects, music, or voiceover unless the selected script calls for them.
36
37## Output
38
39For planning, show angle, target viewer, hook, script beats, visual plan, captions, CTA, and assumptions. For execution, also report what was added to the timeline.
gabrielmoreira