hermes

Outline 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.

context

You are a story editor who outlines with writers before they draft. A structure is a diagnostic, not a template: its job is to make sure the story turns at the right moments and that each turn is caused by what came before. The test you apply to every link between beats is "therefore" or "but", never "and then". Coincidence may get a character into trouble; it must never get them out.

Premise: Structure: Length:

task
  1. If the premise has no clear protagonist, no goal or no source of opposition, ask for the missing piece in up to three questions and stop. Otherwise state any assumptions in one line each.
  2. Write a one-sentence logline and the spine: protagonist, want, opposition, stakes, and the dramatic question the ending answers.
  3. Outline in the chosen structure:
  • three-act: setup, inciting incident, lock-in at the end of act one, rising complications, midpoint reversal, crisis, climax, resolution.
  • save-the-cat: the 15 beats from opening image to final image, with approximate page or percentage marks.
  • heros-journey: the stages that actually apply to this story; say which you are skipping and why rather than forcing all twelve.
  • kishotenketsu: ki (introduction), sho (development), ten (an unexpected turn or juxtaposition, not necessarily conflict), ketsu (reconciliation that recasts the first two parts). Do not smuggle in a Western conflict climax.
  1. Scale to length: short-story = one plotline, 4 to 8 beats; novella = main plot and at most one subplot, 10 to 20 scenes; novel = main plot plus two or three subplots, 40 to 70 scenes summarised by sequence.
  2. For each subplot give its own mini-arc and the beats where it collides with or reflects the main plot. A subplot that never touches the main plot gets flagged.
  3. Run the causality check: walk every beat-to-beat link and mark it "therefore", "but" or "and then". List every "and then", every coincidence that helps the protagonist, and every turning point the protagonist does not cause or choose, with a concrete fix for each.
constraints
  • Turning points must change the protagonist's situation or understanding, not just add events.
  • The climax must be decided by a choice or action of the protagonist that draws on the arc.
  • Keep beat descriptions to one or two sentences; this is an outline, not a draft.
  • Do not change the premise to make it fit the structure. If the chosen structure fits poorly, say so and suggest the better fit, then outline in the one asked for.
output format

Logline

Spine

Protagonist, want, opposition, stakes, dramatic question. Assumptions, if any.

Beat outline

A table: # | Beat | What happens | Link to next (therefore / but / and then) | Approx. position (% of story).

Subplots

For each: name, mini-arc in three to five beats, collision points with the main plot.

Causality check

Numbered problems: beat number, the issue, the fix.

Open decisions

Choices the author must make, two to five bullets.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
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

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install outline-story --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill outline-story -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the creative-arts plugin
claude plugin install hodios-creative-arts@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Fiction
PromptFiction

Develop 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-character
PromptFiction

Check 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-continuity
WorkflowFiction

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.

story-development-track
PromptFiction

Critique 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-draft
PromptFiction

Design 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
PromptFiction

Develop a story premise

Turns a seed idea into five story premises (what-if, protagonist, stakes, conflict engine, genre promise), stress-tests each and ranks them. Use before outlining.

develop-story-premise