AI Comic Drama Script Studio
Transform ideas, novels, or existing scripts into producible 16:9 landscape AI comic drama scripts. Scripts serve continuous episode viewing and subsequent storyboarding, not character display or model demo. A complete single episode runs 90-180 seconds; partial trial writing must explicitly be marked as not a full episode.
Launch
- Confirm whether the task is original creation, novel adaptation, existing script review, partial rewrite, continuous episode continuation, or pre-storyboarding arrangement. Read existing scripts, finalized settings, character/scene/prop states, and the previous episode's ending.
- Determine primary and secondary genres, target audience, episode duration, story language, episode position, existing materials, and unchangeable facts. For missing information that does not affect the current output, use minimal design to fill in gaps and label it as authorial completion.
- For complete episodes, establish a unique fact ledger and manage characters, relationships, props, world rules, character knowledge, foreshadowing, scene states, and unresolved issues according to
references/project-contract.md. Author truth, character knowledge, and audience knowledge must be kept separate. - Only read the reference files needed for this task. Review and rewrite are two separate states; do not overwrite the original draft without user request.
Task Routing
| Task | Required Resources | Deliverable |
|---|---|---|
| Original project initiation, genres, character relationships, episode commitment | references/series-development.md | Project seed, audience promise, character goals, relationship engine, episode state changes |
| Novel or outline adaptation | references/adaptation.md, references/project-contract.md | Original text fact table, adaptation boundaries, shootable scenes and basis for cuts |
| Single or multiple episode scripts | references/episode-writing.md, references/dialogue-and-performance.md | Frozen script, scene cards, dialogue table, episode-end interface |
| Cold reading, logic review | references/script-review.md | P0/P1/P2 issues, evidence, and minimal repair proposals |
| Rewriting, quality improvement, cost reduction, or shot preparation | references/script-review.md, references/episode-writing.md | Original draft preserved, rewritten draft, ledger increments, and re-review |
| Pre-storyboarding arrangement | references/shot-handoff.md | Shootable beats, appearance order, states, and audio-visual interface |
Core Constraints
- Each scene must advance at least one of: goal, information, relationship, obstacle, or situation. Do not fill runtime with scenery display, character posing, causeless camera movement, or repetitive reactions.
- Each scene must have: goal, obstacle, visible action, feedback, strategy or relationship change, result, and the initial state of the next scene. Psychological judgment must be grounded in gaze, pause, action, dialogue, breath, choice, or consequence.
- Dialogue must preserve character intent, original line, speaker, on-screen or off-screen category, listener, trigger, and result. Characters must not suddenly gain unknown information, change stance, or exceed established abilities/rules because the plot demands it.
- Scene partner interactions proceed by: observation target, noticing or choice, readable reaction, verbal or action response, stable final state. Focus transfer must be triggered by visible events or dialogue.
- Action, magic battles, chases, and complex interactions are written as a continuous chain: preparation/center of gravity, path, contact or evasion, force feedback, ending posture. Ability and prop activation, effect, cost, residue, and next-step interface are entered into the ledger.
- Each episode must have: an opening hook, escalating conflict, visible state change, and an episode-end interface. The episode ending grows from events that have already occurred in the episode; do not replace it with abrupt sound effects or characters appearing without source.
- Formal scripts do not contain model prompts, camera parameters, asset prompts, inspection terminology, or creative notes. Storyboarding requirements are output separately in handoff documents.
- User-locked characters, props, world rules, and facts must not be silently rewritten. When altering finalized facts, list the affected scenes and provide forward-foreshadowing or backward-consistent repair options.
Standard Process
P0 Project Initiation
Establish core conflict, primary and secondary genres, audience emotional promise, protagonist's episode goal, obstacles, choice cost, relationship dynamics, and the ending state of this episode. Each genre only adds necessary rules; do not use genre names in place of causality.
P1 Facts and Ledger
When importing a work, first preserve the original text. Build ledgers for: facts, character knowledge, reader information, props, abilities, locations, timeline, and foreshadowing. During adaptation, distinguish between: original text facts, confirmed adaptations, candidate completions, and unknowns.
P2 Episode Script
First write the episode's state change, then the scenes. Each scene uses the check: purpose, obstacle, action, feedback, change, result. Estimate runtime with trial reading, actions, and reactions; a complete single episode accumulates 90-180 seconds.
P3 Review and Revision
Before freezing, check: causality, characters, information, relationships, time/space, props/abilities, shootability, rhythm, and serial interface. For each issue, write: scene, evidence, audience impact, severity, and minimal repair. When the user requests a rewrite, preserve the original draft and only re-review affected scenes and adjacent seams.
P4 Storyboarding Handoff
After the script passes review, output: scene cards, shootable beats, appearance order, character positions and sight lines, prop and environment states, dialogue delivery, sound events, and entry/exit states. This is input for the director and video pipeline, not a video prompt.
Completion Criteria
Report: actual deliverable path or scope, accumulated single-episode runtime, pending facts, and identified risks. When no assets, storyboards, video, or audio have been generated, only deliver the corresponding pre-production text.