Story development track
Takes a story from premise to characters, an outline, a sample scene and revision notes, stopping for the author's approval between steps. Use when starting a new novel or story.
Develops ""Only if [SEED] is given: (seed: ) the way a good editor works with an author before the first draft: sharpen the premise, build characters the plot can pressure, outline with causality, test the voice and the outline in one sample scene, then plan the revision. Each step produces one document and stops for approval; later steps build on the approved documents instead of re-asking.
Rules for every step: the author owns the story, so offer options and ask for decisions on anything that defines it (genre, ending, point of view, theme) instead of choosing silently; never contradict an approved earlier step without flagging it; keep each document short enough to read in five minutes; and do not draft beyond the single sample scene in step 4. If the author wants to go faster or skip to drafting, explain in one line what each remaining step protects, offer the fast route (shorter documents, one question per step, a sample scene as soon as the outline is approved), and keep every approval gate.
Step 1: Premise
Turn the seed of "" into a premise strong enough to outline.
- Ask, in one message, only what you cannot infer: the seed idea if none was given, genre and readership, target length (short story, novella, novel), what drew the author to this idea, and anything that must stay (a character, an image, an ending).
- Once answered, write three distinct premise options. Each has: a logline (protagonist, inciting incident, goal, opposition, stakes); the central dramatic question the ending answers; the thematic question underneath it; and what makes it fresh in its genre.
- For each option, name the biggest risk (thin opposition, passive protagonist, familiar setup) in one line.
- Recommend one option and say why, or a merge of two.
Write the document with sections Answers, Options, Recommendation.
Stop and wait for the author to choose or adjust the premise.
Step 2: Characters
Build the cast the approved premise needs.
- Protagonist: want (external, concrete), need (internal), flaw and the false belief behind it, the wound that taught it, a contradiction, voice notes with two sample lines, and the arc type (positive, negative, flat).
- Opposition: the antagonist or antagonistic force, with a want that is reasonable from their side and a direct collision with the protagonist's want.
- Two or three supporting characters, each with a job in the story (mirror, mentor, temptation, cost) and their own small want.
- A relationship map: one line per important pair saying what each wants from the other and where it will break.
- Flag any character who has no job in the plot or theme.
Write the document with sections Protagonist, Opposition, Supporting cast, Relationships, Flags. Use names that fit the setting; avoid stock names.
Stop and wait for approval.
Step 3: Outline
Outline the story from the approved premise and characters.
- Propose the structure that fits (three-act, Save the Cat beats, hero's journey stages, kishotenketsu, or a mystery's clue-and-reveal structure) and say why in one line. Use the author's choice if they have one.
- Outline the main plot as beats, scaled to the target length, with an approximate position for each. Every link to the next beat is "therefore" or "but"; mark any "and then".
- Weave in the subplots from the relationship map, noting where each collides with the main plot.
- Mark where the protagonist's arc beats fall: first challenge to the false belief, the low point, the final choice.
- Run a causality check and list every coincidence that helps the protagonist, every turning point they do not cause, and every subplot that never touches the main plot, each with a fix.
- Propose two or three candidate scenes for the sample in step 4: pivotal moments that test the voice and the central conflict.
Write the document with sections Structure, Beat outline (table), Subplots, Arc beats, Causality check, Candidate scenes.
Stop and wait for approval and the choice of sample scene.
Step 4: Sample scene
Write the chosen scene as a test of voice and outline, not as the final draft.
- Confirm point of view and tense; ask once if the author has not decided.
- Write a scene card first: the point-of-view character's goal in the scene, the opposition, the turn (how the situation changes), and the value shift (for example trust to betrayal).
- Write the scene in 800 to 1,500 words. Enter late, leave early, ground it in specific sensory detail, and let the dialogue carry subtext.
- Avoid stock phrasing ("a testament to", "the air was thick with", "a breath she didn't know she was holding").
Write the document with sections Scene card and Scene.
Stop and wait for the author's reaction. Ask what felt right and what did not.
Step 5: Revision notes
Use the sample scene and the author's reaction to improve the plan before drafting begins.
- Note what the scene revealed: did the voice work, did the characters behave as designed, did the scene's turn match the outline, and what surprised you or the author.
- List changes to the earlier documents this implies (premise, characters, outline), each with the reason. Keep it to the changes that matter.
- Give prioritised notes on the scene itself (at most five), without rewriting it.
- End with a drafting plan: where to start, the first five scenes to write, and three questions for the author to keep in mind while drafting.
Write the document with sections What the scene showed, Changes to the plan, Scene notes, Drafting plan.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Workflow: ordered steps with a checkpoint between them
- domain
- Creative arts
- category
- Fiction
- level
- Intermediate
- made for
- Writer / author
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install story-development-track --target claude-codenpx skills add hermes-hq/hodios-dist --skill story-development-track -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-creative-arts@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of FictionDevelop a character
Develops a fictional character with a want, a need, a flaw, a backstory that matters, a distinct voice and an arc that serves the story. Use when a character feels flat or generic.
develop-characterOutline a story
Outlines a story in a chosen structure with beats, subplots and turning points, and flags every link where events follow by coincidence instead of cause. Use before drafting.
outline-storyCritique a fiction draft
Gives developmental feedback on a fiction draft covering point of view, pacing, stakes, character and dialogue, prioritised and without rewriting the author's prose. Use between drafts.
critique-fiction-draftFiction-writing mentor
Fiction-writing mentor who protects the author's voice, asks craft questions before judging, and gives specific, prioritised notes. Use as a long-running writing companion for any project.
fiction-writing-mentorCheck story continuity
Finds continuity errors across chapters (names, timelines, physical details, objects, who knows what, world rules) and lists them by location with quotes. Use before beta readers or submission.
check-story-continuityDesign a plot twist
Designs plot twists that feel surprising yet inevitable, naming the reader's false assumption, the reveal, which clues to plant where and how to hide them. Use for novels and screenplays.
design-plot-twist