Retention-Engineered YouTube Long-Form Video Scriptwriter
Script engaging 8-to-15 minute YouTube videos with open loops, visual B-roll cues, and pattern interrupts that sustain watch time.
Compatibility & Specs
Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables4 parameters
Main Prompt Template
181 words • 1305 characters
You are an Elite YouTube Video Director and Retention Scriptwriter who has helped channels scale to millions of subscribers. I need a comprehensive video script engineered to maintain 60%+ average percentage viewed (APV).
Video Title & Core Concept:
[video_title_concept]
Target Audience & Baseline Knowledge:
[target_audience]
Key Teaching Points or Narrative Milestones:
[key_milestones]
Desired Video Length & Pacing:
[video_length_pacing]
Write a production-ready YouTube Script formatted in a two-column director layout:
1. The Irresistible Hook (0:00 - 0:45): Visually arresting opening that delivers on the thumbnail promise immediately, states the stakes, introduces an open curiosity loop, and transitions seamlessly with ZERO 'Hey guys, welcome back to the channel' preamble.
2. Story Progression (Milestones 1 through 3): Script the spoken dialogue with rhythmic sentence variety, including explicit [B-ROLL / ON-SCREEN GRAPHIC / SFX] cues every 20-30 seconds to re-engage wandering attention.
3. The Midpoint Retention Re-hook: A deliberate shift or surprise revelation around the 50% mark that prevents the classic mid-video retention valley.
4. High-Conversion Outro (Final 60s): Smoothly bridging the conclusion into a specific recommendation to click the next related video on screen.
Tip:Variables marked in purple brackets can be tailored below.
Customize Prompt
Fill in the variables below. Your customized prompt updates instantly in the browser — no AI API needed.
Parameters (4)* Indicates required field
[video_title_concept]
The working title and thesis of the video
[target_audience]
Who is watching and their technical level
[key_milestones]
The 3-4 primary lessons or steps to cover
[video_length_pacing]
Target runtime and pacing feel
4 parameters active
Live Customized OutputLive Preview
267 wordsYou are an Elite YouTube Video Director and Retention Scriptwriter who has helped channels scale to millions of subscribers. I need a comprehensive video script engineered to maintain 60%+ average percentage viewed (APV).
Video Title & Core Concept:
Why Next.js App Router Confused Everyone (And How It Actually Works)
Target Audience & Baseline Knowledge:
React developers who upgraded to Next.js 14/15 and felt frustrated by Server Components, caching behaviors, and client-server boundaries.
Key Teaching Points or Narrative Milestones:
1. The fundamental mental model: Server Components are NOT PHP; they run once and stream serialized HTML/JSON. 2. The 4 layers of Next.js caching that tripped everyone up. 3. Practical rule: Data lives on server, interactivity lives in leaves. 4. A clean 3-step checklist to structure any route.
Desired Video Length & Pacing:
10 minutes, high-energy technical teardown with clear code animations and minimal talking head.
Write a production-ready YouTube Script formatted in a two-column director layout:
1. The Irresistible Hook (0:00 - 0:45): Visually arresting opening that delivers on the thumbnail promise immediately, states the stakes, introduces an open curiosity loop, and transitions seamlessly with ZERO 'Hey guys, welcome back to the channel' preamble.
2. Story Progression (Milestones 1 through 3): Script the spoken dialogue with rhythmic sentence variety, including explicit [B-ROLL / ON-SCREEN GRAPHIC / SFX] cues every 20-30 seconds to re-engage wandering attention.
3. The Midpoint Retention Re-hook: A deliberate shift or surprise revelation around the 50% mark that prevents the classic mid-video retention valley.
4. High-Conversion Outro (Final 60s): Smoothly bridging the conclusion into a specific recommendation to click the next related video on screen.
How to Use This Prompt
Follow this 3-step workflow to extract high-signal responses from any compatible AI model.
01
1. Tailor the Parameters
Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.
02
2. Send to AI Model
Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.
03
3. Review and Iterate
Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.
Prompt Variables & Parameters
Reference breakdown of every dynamic variable embedded in this prompt template.
| Placeholder | Parameter Name | Type | Status | Description & Guidance |
|---|---|---|---|---|
| [video_title_concept] | Video Title & Concept | text | Required | The working title and thesis of the videoDefault: Why Next.js App Router Confused Everyone (And How It Actually Works) |
| [target_audience] | Target Audience | text | Required | Who is watching and their technical levelDefault: React developers who upgraded to Next.js 14/15 and felt frustrated by Server Components, caching behaviors, and client-server boundaries. |
| [key_milestones] | Key Milestones / Teaching Points | textarea | Required | The 3-4 primary lessons or steps to coverDefault: 1. The fundamental mental model: Server Components are NOT PHP; they run once and stream serialized HTML/JSON. 2. The 4 layers of Next.js caching that tripped everyone up. 3. Practical rule: Data lives on server, interactivity lives in leaves. 4. A clean 3-step checklist to structure any route. |
| [video_length_pacing] | Video Length & Pacing | text | Required | Target runtime and pacing feelDefault: 10 minutes, high-energy technical teardown with clear code animations and minimal talking head. |
Example Execution & Benchmark Output
Sample input arguments and the verified AI response demonstrating expected quality and formatting.
Sample VariablesInputs
[video_title_concept]
Why Next.js App Router Confused Everyone (And How It Actually Works)
[target_audience]
React developers who upgraded to Next.js 14/15 and felt frustrated by Server Components, caching behaviors, and client-server boundaries.
[key_milestones]
1. The fundamental mental model: Server Components are NOT PHP; they run once and stream serialized HTML/JSON. 2. The 4 layers of Next.js caching that tripped everyone up. 3. Practical rule: Data lives on server, interactivity lives in leaves. 4. A clean 3-step checklist to structure any route.
[video_length_pacing]
10 minutes, high-energy technical teardown with clear code animations and minimal talking head.
Expected AI ResponseVerified Result
### Production Script Excerpt: (0:00 - 1:30)
| Visual / Audio Cues | Spoken Dialogue |
| :--- | :--- |
| **[0:00 - 0:08]**<br>FAST ZOOM into a code editor displaying `'use client'` at the top of 20 different files. Red error badge flashes on screen.<br>*SFX: Subtle error buzz.* | In 2023, the React team gave us Server Components. And for the last two years, half the developer community has spent their Friday nights screaming at their terminal trying to figure out why their state vanished. |
| **[0:08 - 0:22]**<br>CUT TO HOST at desk, holding up an old 2005 PHP book, then throwing it off-screen.<br>*SFX: Book thud.*<br>GRAPHIC: Animated architecture split screen. | A lot of people told you Next.js turned React back into PHP. They were wrong. But the documentation didn't help, and the mental model was completely backwards. |
| **[0:22 - 0:42]**<br>ON-SCREEN DIAGRAM: Color-coded component tree. Server nodes glow blue; Client nodes glow orange.<br>*Text: The Golden Rule.* | Today, I'm going to give you the exact mental model that turns App Router from a caching nightmare into the fastest, cleanest React code you've ever shipped. By minute six, you will never write an unnecessary `'use client'` tag again. |
Best Use Cases
Scenarios and roles where this prompt produces maximum leverage.
Technical creators drafting polished long-form YouTube tutorials
Educators structuring complex topics into entertaining, high-retention video narratives
Video production teams preparing camera-ready scripts with detailed B-roll cue cards
Tips for Best Results
Techniques to elevate response fidelity
- •Provide rich background context rather than one-sentence inputs to receive deep, non-generic responses.
- •Engage in multi-turn conversation: use the initial output as a baseline, then ask the AI to sharpen specific sections.
- •Prompt the model to highlight any hidden assumptions or missing trade-offs in its recommendations.
Common Mistakes to Avoid
Frequent failure modes and anti-patterns
- •Giving minimal context and expecting nuanced, expert-level strategic output.
- •Not validating factual references, citations, or statistical claims with verified primary sources.
- •Skipping the customization step and pasting raw bracketed template variables into the AI chat.
Part of Curated Collections
This prompt is sequenced as part of these goal-oriented workflows
Related AI Prompts
Complementary workflows in YouTube
YouTubeintermediate
High-Search & High-Curiosity YouTube Video Concept Explorer
Brainstorm video concepts that bridge high-volume search intent with high-curiosity packaging to drive algorithmic views.
claudechatgptgemini
#youtube#video-ideas#search-intent
YouTubeintermediate
First 30 Seconds YouTube Hook Diagnostics & Rewriter
Audit your video's opening 30 seconds to eliminate viewer drop-off, front-load stakes, and fulfill the thumbnail promise.
claudechatgptgemini
#youtube-hook#intro-rewriter#retention
YouTubebeginner
YouTube CTR Title & SEO Description Optimizer
Generate 10 high-CTR title variations and an algorithmic, chapter-structured video description with keyword tags.
claudechatgptgemini
#youtube-seo#ctr-optimization#video-titles
Related Engineering Guides
Deep-dive playbooks and system prompt methodologies for YouTube