Fiction Workshop

A structured editorial workflow that treats fiction writing like collaborative software development. You build a Story Bible first (plot, characters, world, theme) so Claude has shared context, then move through chapter work using specific personas (developmental editor, line editor, character consultant, continuity tracker, brainstorm partner). The workflow cycles through brainstorm, curate, draft, refine for each chapter, and finishes with reader testing using a fresh sub-agent who hasn't seen your Story Bible. The persona switching is clever because it prevents mixed feedback where you're getting structural notes and prose notes jumbled together. Best for novels or novellas where consistency across chapters actually matters. Skip it for flash fiction or single scenes.

skills.sh installs: 2.1K
GitHub stars: 22
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add rhavekost/author-toolkit --skill fiction-workshop --agent claude-code

Installs into .claude/skills of the current project.

Files

Fiction Workshop

Editorial workflow for collaborative fiction writing in three stages: Story Bible Building, Chapter Development, and Reader Testing.

Session Continuity

Novel projects span weeks or months. Claude has no memory between sessions, so the Story Bible is your persistent state.

At session start: Read story-bible.md (or whatever the project calls it) before doing any other work. Skim recent files in sessions/ for unresolved threads.
At session end: Write a brief note at sessions/YYYY-MM-DD_topic-slug.md summarizing what was done, decisions made, and the stopping point. Two to five sentences is enough.
When foundations shift: Update the Story Bible immediately when premise, character bios, world rules, or major plot turns change. The Story Bible is the source of truth, not a one-time template.
Surface unresolved questions: At the start of new work, list questions left open from prior sessions and ask the user which to address before continuing.