AI ScriptCrafter 02 (Bible) v4.0 - Akki

The AI ScriptCrafter 02 (Beat Sheet) v4.0 sits between the bible generator and the screenplay writer in the AkkiNodes pipeline. It takes your story plus the character and world bibles and produces a 15-point beat sheet - a structural blueprint of the story from opening hook to resolution. That beat sheet is what gives the screenplay stage its pacing instead of letting the LLM just wing a three-act shape.

How it works

It's one LLM call with the bibles fed in as extra context - the source literally notes the prompt was enhanced to accept the Narrative Bible for richer context. The point of that is grounding: without the bibles, a beat sheet drifts toward generic story structure; with them, the beats actually reference your characters and your world. It's a simple, low-risk node, which is fine - in this pipeline the beat sheet isn't a creative fireworks display, it's a scaffolding pass.

The passthroughs are the real output

Required inputs: llm_model, story_text, world_bible, character_bible, plus max_tokens (4096) and the sampling knobs (temperature 0.7).

Three outputs:

• beat_sheet - the 15-point blueprint. This feeds ScriptCrafter 03.
• world_bible_passthrough and character_bible_passthrough - the bibles, untouched.

Don't underestimate those passthroughs. ComfyUI is a graph, and this node sits in the middle of the chain - you could re-wire the bibles from the previous node directly to ScriptCrafter 03, but the passthroughs mean the chain flows naturally: story + bibles in, story + bibles + beat sheet out. If you're building the workflow from the example JSON, keep them wired as-is and the next stage just works.

Install and gotchas

Standard pack install: search "AkkiNodes LLM Suite" in ComfyUI Manager, or git clone https://github.com/routhakash/AkkiNodes-LLM-Suite-for-ComfyUI into custom_nodes, run install.bat as admin on Windows, put a GGUF in ComfyUI/models/llms/, restart.

The gotcha here is subtle and annoying: the bibles are passed through, but the beat sheet is generated in one shot, so if your max_tokens is too small the beat sheet truncates mid-point and ScriptCrafter 03 silently writes a screenplay with a missing finale. 4096 default is generally fine, but if your story is long, bump it. And because the beat sheet quality caps the screenplay quality, this is another node where a weak GGUF will make itself known two stages later - the symptom shows up in the screenplay, not here.