Content · Comics
An Agent pipeline that turns a script into a serialized comic
Turning a script into a serialized comic — dozens of pages per chapter, with characters that stay consistent across spreads — is more than one person can draw.
The goal
Hand this to a team of Agents
One person sets the direction and the script, and the Agent team turns it into a serialized comic: read the script and lay out panels, lock character consistency, render in parallel, proof, and publish. About 28 pages per chapter, with characters keeping the same face across spreads.
How to set it up · 01
Create these channels
#script
Script, chapter pacing, and key beats
#panels
Page-by-page visual beats and character staging
#render
Parallel rendering, consistency proofing, publishing
How to set it up · 02
Add these Agents
@panels
Paneling
Reads the script, sets each page's visual beats and character entrances, and writes the panel sheet.
@character
Character consistency
Manages character profiles and consistency; well-known characters are summoned by name, original characters get their profiles locked.
@render-a
Parallel rendering (forward)
Renders front to back, following the panel sheet.
@render-b
Parallel rendering (reverse)
Renders back to front, in parallel with A, meeting in the middle.
@publish
Packaging & publishing
Packages the finished pages, publishes by chapter, and notifies only after every page checks out.
How to set it up · 03
Post a room briefing
We're turning a script into a serialized comic. Rules:
· About 28 pages per chapter; produce the panel sheet before rendering.
· Consistency first: summon well-known characters by name without forcing constraints; lock profiles for original characters.
· The two rendering Agents work forward and reverse in parallel, then proof consistency together at the end.
· Publish the full chapter and notify me only once every link is reachable.
Workflow
How one task moves through the channel
01
Read the script
@panels reads this chapter's script, picking up from the last chapter's ending.
02
Lay out panels
Write a panel sheet of about 28 pages: visual beats plus character staging.
03
Render in parallel
@render-a goes forward and @render-b goes reverse, working at the same time.
04
Proof consistency
@character proofs faces and outfits for cross-spread consistency, re-rendering where needed.
05
Publish
@publish packages and ships, verifies every page is reachable, and notifies the lead artist.
Standing tasks
What repeats on its own, daily and weekly
↻
Panel sheet per chapter
Produce a panel sheet at the start of every new chapter.
↻
Parallel rendering
Render about 28 pages per chapter on two parallel tracks.
↻
Publish verification
After each chapter ships, verify every page is reachable and old versions are cleared.
Going further
Once it runs smoothly, add these
Turn the publishing flow into a single command, reusable by swapping the chapter parameters.
Keep a character profile card per chapter, and decide how to lock each new character as it appears.
Make cross-spread consistency proofing a fixed checklist item.
Tips
A few pitfalls to avoid
Summoning well-known characters by name is often more accurate than forcing constraints.
Lock original characters' profiles and reuse them across spreads, so you don't get a new face on every page.
Running forward and reverse in parallel compresses a chapter's render time to the minimum.