Comic Creator

Comic Creator — Full Comic Production Pipeline

Produce comics from storyboard through dialogue, image generation, and editing via an agent team, all in one pass. Supports 4-panel strips, short-form, and long-form (chapter-based) formats.

Execution Mode

Agent Team — Five agents communicate directly via SendMessage and cross-validate each other's work.

Agent Roster

Workflow

Phase 1: Preparation (Performed Directly by the Orchestrator)

1. Extract from user input:
   • Topic/Story Idea: The story to turn into a comic
   • Format: 4-panel / Short-form (8-16 pages) / Long-form (chapter-based) / Webtoon
   • Genre: Comedy, drama, fantasy, slice-of-life, action, etc.
   • Art Style (optional): Manga, American comics, webtoon style, etc.
   • Existing Files (optional): Scenario, character settings, etc.
2. Create _workspace/ directory and _workspace/panels/ subdirectory
3. Organize input and save to _workspace/00_input.md
4. If existing files are available, copy to _workspace/ and skip corresponding phase
5. Determine execution mode based on request scope

Phase 2: Team Assembly and Execution

Tasks 2a (dialogue) and 2b (images) run in parallel. Both depend only on Task 1 (storyboard).

Inter-agent communication flow:

• storyboarder completes -> delivers per-panel situations and emotions to dialogue-writer; character sheets and compositions to image-generator
• dialogue-writer completes -> delivers SFX style to image-generator; bubble types and reading order to comic-editor
• image-generator completes -> delivers image files and blank area info to comic-editor
• comic-editor completes -> delivers editing spec to quality-reviewer
• quality-reviewer cross-validates all deliverables. On RED Must Fix findings, sends revision requests -> rework -> re-validate (up to 2 cycles)

Phase 3: Integration and Final Deliverables

1. Verify all files in _workspace/
2. Confirm all RED Must Fix items have been addressed
3. Report final summary to user

Execution Modes by Scope

Using Existing Files: If the user provides a scenario, storyboard, etc., copy to _workspace/ and skip that agent's phase.

Data Transfer Protocol

File naming convention: {order_number}_{deliverable}.{extension}

Error Handling

Test Scenarios

Normal Flow

Prompt: "Create a 4-panel comic about a programmer's daily life. Comedy genre." Expected Result:

• Storyboard: 4-panel setup-development-twist-punchline storyboard, character sheet
• Dialogue: Character-specific speech, sound effects, punchline
• Images: 4 panel images generated (consistent art style)
• Editing: Speech bubble placement, reading flow specification
• Review: Full consistency matrix verified

Existing File Flow

Prompt: "Create a webtoon from this scenario" + attached scenario file Expected Result:

• Incorporate existing scenario into _workspace/01_storyboard.md
• Storyboarder adds panel layout design on top of existing scenario
• Deploy dialogue-writer + image-generator + comic-editor + reviewer

Error Flow

Prompt: "Just create a quick storyboard, any topic" Expected Result:

• Switch to storyboard mode (storyboarder + reviewer)
• Topic is unclear, so storyboarder proposes 3 genre-based synopses
• Review report notes "Dialogue/image/editing not generated"

Agent Extension Skills