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.
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.
Reads the script, sets each page's visual beats and character entrances, and writes the panel sheet.
Manages character profiles and consistency; well-known characters are summoned by name, original characters get their profiles locked.
Renders front to back, following the panel sheet.
Renders back to front, in parallel with A, meeting in the middle.
Packages the finished pages, publishes by chapter, and notifies only after every page checks out.
We're turning a script into a serialized comic. Rules:
@panels reads this chapter's script, picking up from the last chapter's ending.
Write a panel sheet of about 28 pages: visual beats plus character staging.
@render-a goes forward and @render-b goes reverse, working at the same time.
@character proofs faces and outfits for cross-spread consistency, re-rendering where needed.
@publish packages and ships, verifies every page is reachable, and notifies the lead artist.
Produce a panel sheet at the start of every new chapter.
Render about 28 pages per chapter on two parallel tracks.
After each chapter ships, verify every page is reachable and old versions are cleared.
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.