From story-skills
Writes story chapters using an outline-first workflow. Activates on requests like 'write a chapter' or 'draft chapter' to maintain consistency with existing story elements.
How this skill is triggered — by the user, by Claude, or both
Slash command
/story-skills:chapter-writingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write story chapters using an outline-first workflow. Gathers context from all other story elements (characters, world, plot) to maintain consistency, builds a beat-by-beat outline for approval, then writes full prose. After writing, updates all cross-references (chapter index, timeline, foreshadowing).
Write story chapters using an outline-first workflow. Gathers context from all other story elements (characters, world, plot) to maintain consistency, builds a beat-by-beat outline for approval, then writes full prose. After writing, updates all cross-references (chapter index, timeline, foreshadowing).
A story project must already exist with at least:
story.md (story bible)characters/plot/_index.md (recommended but not required for first chapters)Before drafting or revising chapter prose, check whether the better-writing skill is available in the active agent environment.
better-writing is available, use it for prose quality, voice calibration, anti-generic writing checks, and the final pre-flight pass before saving the chapter.better-writing is not available, recommend installing forjd/better-writing with npx skills add forjd/better-writing or bunx skills add forjd/better-writing, then continue with this skill's built-in writing guidelines if the user does not install it.Read these files to understand the current story state:
story.md - genre, themes, POV, tensechapters/_index.md - what's been written, current word countplot/_index.md - arc status, what needs to happen nextplot/timeline.md - chronological positionscenes/_index.md - scene state already recordedcontinuity/state.md - character, object, and knowledge statecontinuity/questions/_index.md and continuity/promises/_index.md - unresolved mysteries and setup/payoff commitmentsIf this isn't the first chapter, also read:
plot/arcs/ - for upcoming plot beatsAsk the user:
If plot arcs exist, suggest the next logical beats to advance.
Create a beat-by-beat outline listing:
Load the POV character's file for voice reference. Load relevant location files for setting details.
Present the outline to the user for approval. Revise until approved.
With the approved outline, write the full prose:
story.mdreferences/writing-guidelines.md for prose craft guidancebetter-writing skill before finalizing prosereferences/chapter-template.mdSave to chapters/chapter-{NN}.md with appropriate frontmatter.
Create or update a matching scene file in scenes/chapter-{NN}-scene-{NN}.md for each scene. Scene frontmatter should include chapter, scene, pov, location, characters, arcs-advanced, status, and state-changes so continuity survives beyond prose.
Write chapter prose directly into the chapter markdown file. Do not stage prose in project-local build scripts, generator scripts, or bulk writer scripts (for example build-*.js) to emit chapters. If a temporary helper is truly unavoidable for mechanical file operations, keep it outside the story project and remove it before finishing.
After the chapter is written:
chapters/_index.md - add chapter to registry, update total word countplot/timeline.md - add events from this chapter in chronological orderscenes/ fileplanted or paid-off with chapter referencestory wordcount . --write
story reindex .
story links .
story validate .
story next .
Present a summary of all updates made.
Within a chapter, separate scenes with ---. Each scene should have a clear POV character (even if the same as the previous scene) and location.
When asked to revise, line edit, polish, or continuity-check an existing chapter, use the revision-continuity skill. This skill owns new drafting and chapter creation; revision-continuity owns targeted edits, continuity audits, and post-draft cleanup.
Use the Story CLI when it is available. If story is not installed but the story-maintenance skill is present, use node ../story-maintenance/scripts/story.js with the same arguments, resolving the path relative to this skill folder. If no CLI is available, perform the registry, backlink, and word-count checks manually.
references/chapter-template.md - Frontmatter and structure template for chapter filesreferences/scene-template.md - Machine-readable continuity template for scenesreferences/writing-guidelines.md - Prose craft guidance: show-don't-tell, POV, dialogue, pacing, scene structure, continuitynpx claudepluginhub danjdewhurst/story-skills --plugin story-skillsGenerates first-draft novel prose from Crucible outlines via scene-by-scene drafting, style matching, continuity tracking, and hallucination prevention. Use after planning/outlining on write/draft requests.
创作期续写工具,基于场景规划逐章生成小说正文。当用户说"续写"、"写章节"、"生成章节"、"写下一章"、"批量生成"、"继续写"、"写正文"时自动激活。
Initializes a new fiction writing project with structured markdown folders, character/worldbuilding/plot registries, continuity tracking, glossary, and chapter tracker.