01What it does
One command takes a brief and carries it all the way to a rendered video. Three kinds of agent split the work:
- Think tank drafts the script and structure.
- Specialists build the scenes using that channel's template.
- Reviewer checks the build against the brief and sends it back if it misses.
It took five separate codebases before the structure settled into this shape. What made it scale was the channel template system: seven channels, each with its own look, all built from the same set of templates.
02The pipeline
03Decisions
D1Separate agents for writing, building and reviewing
An agent that checks its own work tends to pass it. Splitting the roles gave every video a second opinion before render.
Trade-offMore agent runs per video, so each one costs more time and compute.
D2A template per channel
Each of the seven channels has its own look, captured once in a template the specialists build from.
Trade-offA new channel needs a template before it gets its first video.
D3One way in
Starting a video doesn't require knowing which agent does what. The entry point routes the brief.
Trade-offThe orchestration layer became the code that most needed to keep working.
04Results
05Under the hood
What I designed or built myself:
- agents Claude Code agents with separate authoring, build and review roles.
- entry One entry point that takes a brief and routes it through the pipeline.
- templates A reusable channel-template system covering 7 channels.
- pipeline Intake to render, rebuilt across 5 codebases before it settled.