From velith
Decomposes chapter outlines and character bibles into GMC/RDD scene sequences for fiction writing. Runs before chapter-writer to produce per-scene prose drafts.
How this agent operates — its isolation, permissions, and tool access model
Agent reference
velith:agents/scene-generatorThe summary Claude sees when deciding whether to delegate to this agent
Chapter outline → scene list → per-scene drafts. Fiction only. **Input**: outline.md chapter spec + STYLE.md + character bible + prev chapter scenes. 1. Analyze 15-beat position, A/B Story advancement needed, chapter-ending hook type 2. Decompose into 3-6 scenes (alternate GMC ↔ RDD). Per scene: type, POV, goal/reaction, conflict/dilemma, disaster/decision, setting, beat contribution 3. Draft e...
Chapter outline → scene list → per-scene drafts. Fiction only.
Input: outline.md chapter spec + STYLE.md + character bible + prev chapter scenes.
Scene design: alternate Scene↔Sequel, every scene from character motivation, conflict required in every scene.
Output: drafts/ch{NN}-scenes.md. chapter-writer reads this for integration; falls back to outline→chapter if absent.
Status: node {PLUGIN_ROOT}/velith.mjs agents scene-generator <running|complete|error> [task]
npx claudepluginhub epicsagas/plugins --plugin velithDesigns compelling story structures, plot arcs, pacing, and scene sequences using three-act structure, hero's journey, Save the Cat beats, and conflict escalation. Delegate for planning novels, screenplays, or narratives from concept to beat sheets.
Writes immersive web novel episodes integrating episode blueprints and continuity reports. Ensures character depth via embodiment principles, strong hooks, timeline/numerical consistency, plausibility, and cliffhanger endings. Use for episode body writing.
Generates a single book or document chapter from an outline spec, style guide, and source excerpts, with built-in self-QA for length, structure, and style compliance.