Claude Skill

chapter-writing

This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write prose for a story project.

LLM Mart · 0 points · 0 views 22 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download danjdewhurst-story-skills-skills_chapter-writing-8350f77.zip · 5 KB
danjdewhurst/story-skills 233 33 forks MIT Updated 4d ago
Part of danjdewhurst/story-skills — 11 skills

Install

skills CLI npx skills add https://github.com/danjdewhurst/story-skills/tree/main/skills/chapter-writing
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install danjdewhurst-story-skills@llmmart
Git git clone https://github.com/danjdewhurst/story-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole danjdewhurst/story-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Chapter Writing

Overview

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

Prerequisites

A story project must already exist with at least:

  • story.md (story bible)
  • At least one character in characters/
  • A plot structure in plot/_index.md (recommended but not required for first chapters)

Recommended Companion Skill

Before drafting or revising chapter prose, check whether the better-writing skill is available in the active agent environment. Detect it by looking for its skill directory in the configured skills paths:

ls -d ~/.claude/skills/better-writing .claude/skills/better-writing skills/better-writing 2>/dev/null
  • If a better-writing directory exists (containing SKILL.md), use it for prose quality, voice calibration, anti-generic writing checks, and the final pre-flight pass before saving the chapter.
  • If better-writing is not installed, point the user at forjd/better-writing and ask whether they want to install it; do not run any installer without explicit approval. Then continue with this skill's built-in writing guidelines (references/writing-guidelines.md) if the user does not install it.

Outline-First Workflow

1. Gather Context

Read these files to understand the current story state:

  • story.md - genre, themes, POV, tense
  • chapters/_index.md - what's been written, current word count
  • plot/_index.md - arc status, what needs to happen next
  • plot/timeline.md - chronological position
  • scenes/_index.md - scene state already recorded
  • continuity/state.md - character, object, and knowledge state
  • continuity/questions/_index.md and continuity/promises/_index.md - unresolved mysteries and setup/payoff commitments

If this isn't the first chapter, also read:

  • The previous chapter file - for continuity (ending state, cliffhangers, emotional tone)
  • Active arc files in plot/arcs/ - for upcoming plot beats

2. Determine Chapter Scope

Ask the user:

  • What should this chapter cover? (or suggest based on plot arcs)
  • Whose POV?
  • Which location(s)?

If plot arcs exist, suggest the next logical beats to advance.

3. Build the Outline

Create a beat-by-beat outline listing:

  • Each scene/beat and what it accomplishes
  • POV character and location for each beat
  • Which arc plot points are advanced
  • Any foreshadowing to plant or pay off
  • Any machine-readable state changes the scene should record

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.

4. Write the Chapter

With the approved outline, write the full prose:

  • Follow the POV and tense from story.md
  • Use the POV character's voice and speech patterns from their profile
  • Ground scenes in location details from worldbuilding files
  • Consult references/writing-guidelines.md for quick prose craft guidance. For the deep reference — the Scene/Sequel unit, dialogue subtext and voice-differentiation, deep POV and psychic distance — use the scene-craft skill.
  • When available, apply the better-writing skill before finalizing prose
  • Use the chapter template from references/chapter-template.md
  • Include the approved outline in the file above ## Chapter Text (for reference). CLI word counts start at that heading, so an outline kept above it never inflates word-count: run story wordcount . --write after writing to record counts.

Save 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 title, chapter, scene, pov, location, characters, mentions, 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.

5. Post-Write Updates

After the chapter is written:

  1. Update chapters/_index.md - add chapter to registry, update total word count
  2. Update plot/timeline.md - add events from this chapter in chronological order
  3. Update arc files - mark advanced plot points with chapter reference
  4. Update scene records - make sure every scene has a corresponding scenes/ file
  5. Update continuity - carry forward character state, object ownership, knowledge, open questions, and promises/payoffs. When story.md links other books through follows or precedes, give reveals the series depends on a stable fact id in knowledge-state (see series-continuity)
  6. Update foreshadowing - mark any items as planted or paid-off with chapter reference
  7. Note character changes - if a character's status changed (injury, revelation, relationship shift), flag for the user to update the character file
  8. Run CLI maintenance when available:
story wordcount . --write
story reindex .
story links .
story validate .
story next .

Present a summary of all updates made.

Scene Breaks

Within a chapter, separate scenes with ---. Each scene should have a clear POV character (even if the same as the previous scene) and location.

Revision Handoff

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.

CLI Maintenance

Use the Story CLI when it is available. If story is not installed, use bun run story -- from the Story Skills repository checkout or the bundled fallback 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.

Reference Files

  • references/chapter-template.md - Frontmatter and structure template for chapter files
  • references/scene-template.md - Machine-readable continuity template for scenes
  • references/writing-guidelines.md - Quick-reference prose craft: show-don't-tell, POV, dialogue, pacing, scene structure, continuity. For the deep reference — the Scene/Sequel unit, dialogue subtext and voice-differentiation, deep POV and psychic distance — use the scene-craft skill.
Files (story-skills)
  • references
    • chapter-template.md 1016 B 
      # Chapter Template

Use this template when creating a new chapter file at `chapters/chapter-{NN}.md`.

```yaml
---
title: "{Chapter Title}"
number: {N}
pov: {character-kebab}
locations:
  - {location-kebab}
characters:
  - {character-kebab}
mentions:
  - {referenced-character-kebab}
arcs-advanced:
  - {arc-kebab}
status: {outline|draft|revised|final|complete}
word-count: {N}
---
```

`characters` lists characters present in the chapter's scenes. `mentions` is optional and lists characters who are only referenced, remembered, recorded, or seen in flashback - including deceased characters, so `story continuity` does not flag them as posthumous appearances.

## Outline

*Beat-by-beat outline approved before writing:*

1. {Beat 1 - what happens, what it accomplishes}
2. {Beat 2}
3. {Beat 3}
...

**Arc beats advanced:** {Which plot points this chapter hits}
**Foreshadowing planted:** {Any setups placed}
**Foreshadowing paid off:** {Any earlier setups resolved}

---

## Chapter Text

{Full prose goes here}
    • scene-template.md 1.3 KB 
      # Scene Template

Use this template when creating a machine-readable scene file at `scenes/chapter-{NN}-scene-{NN}.md`.

```yaml
---
title: "{Scene Title}"
chapter: chapter-{NN}
scene: {N}
pov: {character-kebab}
location: {location-kebab}
characters:
  - {character-kebab}
arcs-advanced:
  - {arc-kebab}
status: {outline|draft|revised|final|complete}
sequel: {true|false}
dilemma: "{The choice the POV character must make in the sequel}"
state-changes:
  - target: {character-or-artifact-kebab}
    change: "{What changed and must carry forward}"
---
```

`sequel` and `dilemma` are optional. Set `sequel: true` when the scene is the reaction half of the scene/sequel unit; leave them out for ordinary action scenes.

## Purpose

What this scene changes for plot, character, theme, or reader knowledge.

## Sequel

For `sequel: true` scenes — the reaction → dilemma → decision half that follows a scene ending in a setback:

- **Reaction:** How the POV character processes the setback emotionally
- **Dilemma:** The impossible choice they face between the options available
- **Decision:** What they decide to do next — the goal that launches the following scene

## Continuity Notes

Track character state, object state, knowledge, timing, and location facts that later chapters must preserve.
    • writing-guidelines.md 2.6 KB 
      # Writing Guidelines

Guidelines for writing chapter prose. Adapt to the story's genre, tone, and POV as defined in `story.md`.

## Show, Don't Tell

- Convey emotion through action, dialogue, and sensory detail rather than stating feelings
- BAD: "She was angry."
- GOOD: "Her fingers whitened around the hilt. She spoke through her teeth."

## POV Consistency

- **First person:** Everything filtered through narrator's voice, knowledge, and bias
- **Third-person limited:** Stay in one character's head per scene. Only describe what they perceive, think, and feel
- **Third-person omniscient:** Can reveal any character's thoughts, but maintain a consistent narrative voice

Do NOT shift POV mid-scene. If a POV shift is needed, use a scene break (marked with `---`).

## Dialogue

- Dialogue should reveal character, advance plot, or both
- Each character should have a distinct voice (reference their Voice & Speech Patterns)
- Use dialogue tags sparingly - "said" is invisible, fancy tags distract
- Break up long speeches with action beats
- Avoid exposition dumps disguised as conversation

## Pacing

- Short sentences and paragraphs = fast pace, tension, action
- Longer sentences and paragraphs = slower pace, reflection, atmosphere
- Vary sentence length for rhythm
- Scene length should match importance - don't over-write minor moments

## Scene Structure

Each scene should have:
- **Goal:** What the POV character wants in this scene
- **Conflict:** What opposes them
- **Outcome:** What happens (often a setback that drives the next scene)

Not every scene needs explosive conflict - quiet character moments matter too. But every scene should change something.

## Sensory Detail

Ground scenes in the physical world:
- Sight, sound, smell, touch, taste
- Choose 2-3 senses per scene, not all five
- Use details specific to the location (reference the location file)
- Sensory details should reflect the POV character's state of mind

## Chapter Openings

- Orient the reader quickly: who, where, when
- Hook with tension, mystery, or voice
- Avoid opening with weather or waking up (unless deliberately subverting the cliche)

## Chapter Endings

- End on a moment of change, revelation, or tension
- Cliffhangers work for action chapters
- Quiet resonance works for character chapters
- The last line should make the reader want to continue

## Continuity

Before writing, check:
- Previous chapter's ending (pick up threads, don't contradict)
- Character states (injuries, emotional state, knowledge)
- Timeline consistency (time of day, travel times, seasons)
- Plot arc progress (what beats need to land)
  • SKILL.md 7 KB 
    ---
name: chapter-writing
description: This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write prose for a story project.
---

# Chapter Writing

## Overview

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

## Prerequisites

A story project must already exist with at least:
- `story.md` (story bible)
- At least one character in `characters/`
- A plot structure in `plot/_index.md` (recommended but not required for first chapters)

## Recommended Companion Skill

Before drafting or revising chapter prose, check whether the `better-writing` skill is available in the active agent environment. Detect it by looking for its skill directory in the configured skills paths:

```shell
ls -d ~/.claude/skills/better-writing .claude/skills/better-writing skills/better-writing 2>/dev/null
```

- If a `better-writing` directory exists (containing `SKILL.md`), use it for prose quality, voice calibration, anti-generic writing checks, and the final pre-flight pass before saving the chapter.
- If `better-writing` is not installed, point the user at [forjd/better-writing](https://github.com/forjd/better-writing) and ask whether they want to install it; do not run any installer without explicit approval. Then continue with this skill's built-in writing guidelines (`references/writing-guidelines.md`) if the user does not install it.

## Outline-First Workflow

### 1. Gather Context

Read these files to understand the current story state:

- `story.md` - genre, themes, POV, tense
- `chapters/_index.md` - what's been written, current word count
- `plot/_index.md` - arc status, what needs to happen next
- `plot/timeline.md` - chronological position
- `scenes/_index.md` - scene state already recorded
- `continuity/state.md` - character, object, and knowledge state
- `continuity/questions/_index.md` and `continuity/promises/_index.md` - unresolved mysteries and setup/payoff commitments

If this isn't the first chapter, also read:
- The previous chapter file - for continuity (ending state, cliffhangers, emotional tone)
- Active arc files in `plot/arcs/` - for upcoming plot beats

### 2. Determine Chapter Scope

Ask the user:
- What should this chapter cover? (or suggest based on plot arcs)
- Whose POV?
- Which location(s)?

If plot arcs exist, suggest the next logical beats to advance.

### 3. Build the Outline

Create a beat-by-beat outline listing:
- Each scene/beat and what it accomplishes
- POV character and location for each beat
- Which arc plot points are advanced
- Any foreshadowing to plant or pay off
- Any machine-readable state changes the scene should record

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.

### 4. Write the Chapter

With the approved outline, write the full prose:

- Follow the POV and tense from `story.md`
- Use the POV character's voice and speech patterns from their profile
- Ground scenes in location details from worldbuilding files
- Consult `references/writing-guidelines.md` for quick prose craft guidance. For the deep reference — the Scene/Sequel unit, dialogue subtext and voice-differentiation, deep POV and psychic distance — use the `scene-craft` skill.
- When available, apply the `better-writing` skill before finalizing prose
- Use the chapter template from `references/chapter-template.md`
- Include the approved outline in the file above `## Chapter Text` (for reference). CLI word counts start at that heading, so an outline kept above it never inflates `word-count`: run `story wordcount . --write` after writing to record counts.

Save 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 `title`, `chapter`, `scene`, `pov`, `location`, `characters`, `mentions`, `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.

### 5. Post-Write Updates

After the chapter is written:

1. **Update `chapters/_index.md`** - add chapter to registry, update total word count
2. **Update `plot/timeline.md`** - add events from this chapter in chronological order
3. **Update arc files** - mark advanced plot points with chapter reference
4. **Update scene records** - make sure every scene has a corresponding `scenes/` file
5. **Update continuity** - carry forward character state, object ownership, knowledge, open questions, and promises/payoffs. When `story.md` links other books through `follows` or `precedes`, give reveals the series depends on a stable `fact` id in `knowledge-state` (see `series-continuity`)
6. **Update foreshadowing** - mark any items as `planted` or `paid-off` with chapter reference
7. **Note character changes** - if a character's status changed (injury, revelation, relationship shift), flag for the user to update the character file
8. **Run CLI maintenance when available:**

```shell
story wordcount . --write
story reindex .
story links .
story validate .
story next .
```

Present a summary of all updates made.

## Scene Breaks

Within a chapter, separate scenes with `---`. Each scene should have a clear POV character (even if the same as the previous scene) and location.

## Revision Handoff

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.

## CLI Maintenance

Use the Story CLI when it is available. If `story` is not installed, use `bun run story --` from the Story Skills repository checkout or the bundled fallback `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.

## Reference Files

- **`references/chapter-template.md`** - Frontmatter and structure template for chapter files
- **`references/scene-template.md`** - Machine-readable continuity template for scenes
- **`references/writing-guidelines.md`** - Quick-reference prose craft: show-don't-tell, POV, dialogue, pacing, scene structure, continuity. For the deep reference — the Scene/Sequel unit, dialogue subtext and voice-differentiation, deep POV and psychic distance — use the `scene-craft` skill.

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related

Claude Prompt
Tighten-my-prose editing prompt
Claude Skill
Adversarial code-review skill for Claude
Claude Workflow
Deep-research workflow (fan-out + verify)
Claude Skill
Conventional-commit writer for Claude