agentleFS
Sign inStart free
bs779517bs779517/story-skills/skills/chapter-writing/SKILL.md

chapter-writing

Skill8 starsChanged 9 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. danjdewhurst/story-skills★ 399same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write story chapters using an outline-first workflow.

    line 10
  2. Distinctive:

    Read these files to understand the current story state:

    line 23
  3. Distinctive:

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

    line 30
  4. Distinctive:

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

    line 41
  5. Distinctive:

    Create a beat-by-beat outline listing:

    line 45
  6. Very specific:

    Follow the POV and tense from story.md

    line 59
  7. Distinctive:

    Use the POV character's voice and speech patterns from their profile

    line 60
  8. Very specific:

    Use the chapter template from references/chapter-template.md

    line 63
  9. Distinctive:

    After the chapter is written:

    line 70
  10. Very specific:

    Update chapters/_index.md: - add chapter to registry, update total word count

    line 72
  11. Very specific:

    Update plot/timeline.md: - add events from this chapter in chronological order

    line 73
  12. Distinctive:

    Note character changes: - if a character's status changed (injury, revelation, relationship shift), flag for the user to update the …

    line 76
  13. Distinctive:

    When asked to revise a chapter:

    line 86
  14. Distinctive:

    Read the existing chapter

    line 87
  15. Distinctive:

    Update word count in frontmatter

    line 90
  16. Distinctive:

    Update chapter status (draft -> revised)

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

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

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

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 prose craft guidance
  • Use the chapter template from references/chapter-template.md
  • Include the approved outline in the file above the prose (for reference)

Save to chapters/chapter-{NN}.md with appropriate frontmatter.

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 foreshadowing - mark any items as planted or paid-off with chapter reference
  5. Note character changes - if a character's status changed (injury, revelation, relationship shift), flag for the user to update the character file

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 Workflow

When asked to revise a chapter:

  1. Read the existing chapter
  2. Understand what needs to change
  3. Make targeted edits rather than rewriting from scratch
  4. Update word count in frontmatter
  5. Update chapter status (draft -> revised)

Reference Files

  • references/chapter-template.md - Frontmatter and structure template for chapter files
  • references/writing-guidelines.md - Prose craft guidance: show-don't-tell, POV, dialogue, pacing, scene structure, continuity

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free