In WorkBuddy, the short video production pipeline is split into two specialized AI Expert Teams: one responsible for generating videos, and one responsible for reverse-engineering viral videos.
| Team | Scope | Target Tasks |
|---|---|---|
| Video Generation Team | Handles topic aggregation, selection filtering, scripting, storyboarding, voice-overs, rendering, subtitles, and publishing based on a theme. | AI newsletters, product updates, educational videos, industry analysis, product reviews. |
| Viral Video Analyzer Team | Downloads video links, extracts audio, transcribes voice-overs, analyzes camera language, and outputs teardown reports and copying advice. | Learning viral hooks, reviewing competitor videos, compiling shooting manuals, providing references for the generation team. |
These two teams do not replace each other. The generation team answers "how to produce a video today," while the analyzer team answers "why someone else's video went viral and what we can learn." One is responsible for production, the other for learning; combining them allows for continuous iteration.
How to Summon: Start with One Sentence, but Do Not Stop There
Summon the Video Generation Team to produce a 46-second AI Weekly Newsletter short video.First Team: Video Generation Team
The Video Generation Team consists of four core roles: Ling Dao (Director / Team Leader), Ling Yue (Information Scraper), Ling Shu (Content Planner), and Ling Ying (Video Editor). They form an upstream-to-downstream pipeline, not just four chat windows with different names.
| Role | Position | Deliverables |
|---|---|---|
| Ling Dao | Director / Leader | Decomposes tasks, arranges parallel/serial flows, aggregates deliverables, and manages checkpoints. |
| Ling Yue | Information Scraper | Hot topic pools, source logs, deduplicated summaries, and topic candidates. |
| Ling Shu | Content Planner | Topic selections, script drafts, storyboards, voice-overs, transitions, asset lists, BGM, and subtitle pacing. |
| Ling Ying | Video Editor | HTML video projects, voice-over generation, subtitle alignment, transition animations, rendering. |
This is the key to multi-agent architectures: each role has distinct inputs and outputs. The scraper does not write scripts, the planner does not invent news, the editor does not rewrite facts, and the leader ensures the workflow never stalls.
Underlying Engine: HyperFrames
This pipeline is built on HyperFrames. Its core concept is rendering videos via HTML, which is naturally suited for Agents to compile structured templates and output MP4 files via rendering utilities. It includes a CLI toolchain, TTS voice-over, Whisper subtitles alignment, background removal, and video component templates.
Step 1: Information Scraper Establishes Topic Feeds
The most time-consuming part of video production is deciding what to shoot, not editing. Thus, the pipeline starts with Ling Yue scanning RSS feeds, news portals, and social boards to gather AI news and output deduplicated digests. The deliverables must contain: title, source, publish time, event time, primary URL, heat index, and why it is worth noting. Heat indexes only help rank priorities; they do not replace fact checking.
Step 2: Content Planner Transforms Themes into Storyboards
Once a topic is selected, Ling Shu writes scripts, designs storyboards, plans narration, and suggests transitions, BGM pacing, and subtitle pauses. We recommend a manual checkpoint here: check if the first 3 seconds contain a hook, if the script is overloaded for a 46-second video, and if the visual cues support the claims. Do not proceed to voice-over and rendering if the script fails validation.
Step 3: Video Editor Turns Storyboards into Video Clips
Ling Ying converts the approved script into HTML and invokes HyperFrames to render the MP4. The system automatically processes Azure TTS voice-overs, Whisper subtitle alignments, transition animations, asset merging, and video rendering. Do not verify the output merely by checking if it plays. Verify if the voice-over aligns with subtitles, if shot durations are appropriate, if text blocks obscure subjects, if BGMs are royalty-free, and if layouts fit the safe zones of target platforms.
Step 4: Distribution is Automated, but Requires Confirmation
The distribution Agent automatically writes titles, adds hashtags, uploads cover cards, and posts to Douyin, WeChat Channels, and Bilibili via cloud emulator frameworks. This represents strong automation capability; however, we recommend requiring manual confirmation for accounts, titles, and compliance boundaries before publishing.
Second Team: Viral Video Analyzer Team
Generation is only half of the loop. Content creators must comprehend why other videos go viral, reverse-engineering them into actionable guidelines: download video, transcribe audio, analyze camera frames, and compile imitation playbooks.
| Role | Responsibility | Tools / Tech |
|---|---|---|
| Ah Bao | Leader / Controller | Task scheduling, pipeline orchestration, result aggregation. |
| Xiao Kai | Audio & Transcription | ffmpeg, ASR to convert video audio into full text scripts. |
| Xiao Miao | Video Analysis | Video understanding APIs, ffmpeg to analyze shots and cut clips. |
Step 1: Video Downloading and Fallbacks
The first step is downloading the target video. A three-tier fallback pipeline is designed: Official APIs -> Playwright -> yt-dlp. As long as one tier succeeds, the pipeline continues. Boundary check: Video downloads and analyses must respect platform terms of service, copyright licenses, and fair use limits. The goal of analysis is learning structures, not ripping original assets.
Step 2: Audio Extraction and Transcription
Once downloaded, Xiao Kai extracts the audio from video.mp4 into audio.mp3 using ffmpeg, and calls speech-to-text APIs to compile transcriptions. The manual task of listening and typing is fully automated.
Step 3: Video Understanding and Shot Analysis
Xiao Miao analyzes shot sizes, camera movements, cuts, paces, colors, and shot durations. Behind "good-looking" viral videos are stable camera laws that the Agent structures.
Closing the Loop between Both Teams
The two teams cooperate. First, the analyzer team decodes camera patterns and paces, then the generation team produces new clips. Once published, metrics are analyzed to refine the next generation run.
flowchart LR
A[Viral Video Link] --> B[Analyzer Team: Transcript, Shots, Pace, Imitation Guide]
B --> C[Compile Production Guide & Visual Patterns]
C --> D[Generation Team: Topics, Scripts, Storyboards, Rendering]
D --> E[Human Review & Publication]
E --> F[Performance Analysis]
F --> BThis is the value of Expert Teams over single tools: it does not just produce a video, it builds an executing system of "learn, produce, publish, and review."
References
Part of this series
WorkBuddy In Action
View all guides in this series →