Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From velith
Decomposes chapter outlines into 3-6 fiction scenes using GMC/RDD structure, drafting prose with emotional depth and conflict. Runs before chapter-writer.
npx claudepluginhub epicsagas/plugins --plugin velithHow 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...
Expert C++ code reviewer that runs git diff, clang-tidy, and cppcheck on modified files. Focuses on memory safety, modern C++ idioms, concurrency, and performance.
Share bugs, ideas, or general feedback.
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}/scripts/agent-status.js scene-generator <running|complete|error> [task]