Technical SDK Screencast Script Brief

Role: Principal Developer Advocate and Technical Instructional Designer for developer infrastructure tooling.

Context

• Target tech stack: {{tech_stack}}
• Developer experience tier: {{developer_tier}}
• Primary command-line tool or SDK: {{terminal_tool}}
• Real-world technical bottleneck: {{friction_scenario}}
• Live implementation path: {{live_demo_workflow}}
• Public repository link: {{repo_url}}

Task

Author a comprehensive screencast script brief that empowers developer advocates to record an authentic, fluff-free technical demonstration solving {{friction_scenario}} using {{terminal_tool}}.

Method

1. Define the prerequisites, terminal environments, and package versions required for {{tech_stack}}.
2. Establish the architectural challenge and failure state caused by {{friction_scenario}}.
3. Script the step-by-step CLI execution and code snippets matching {{live_demo_workflow}}.
4. Design side-by-side terminal capture and code editor callouts with precise zoom coordinates.
5. Write technical audio narration that explains the "why" behind syntax rather than reading code verbatim.
6. Include troubleshooting callouts for common edge-case errors during installation or compilation.
7. Anchor the closing segment to practical self-service exploration via {{repo_url}}.

Constraints

• Narration MUST NOT read code syntax line-by-line; focus audio on runtime behavior and mental models.
• Terminal commands MUST reflect runnable, production-valid syntax for {{tech_stack}}.
• MUST include explicit instructions for IDE themes, font sizes (min 16pt), and terminal prompt sanitization.
• Do not include marketing fluff, corporate slogans, or unprompted feature teasers.

Output format

Provide a technical brief with the following sections:

1. Video Spec & Sandbox Setup (environment, packages, font/terminal configuration)
2. Code & Capture Sequence (Step, Screen State, Terminal/IDE Input, Audio Narrative, Callout Box)
3. Git Commit Milestones & Links (mapping script milestones to {{repo_url}})

Self-review

• Are all terminal commands in {{live_demo_workflow}} executable in order without missing dependencies?
• Is the tone appropriate for {{developer_tier}} engineers without condescension?
• Does the screencast resolve {{friction_scenario}} within the first 60% of the duration?