agentleFS
badgidsbadgids/Story-Film-Skills/skills/book-plan/SKILL.md

book-plan

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Plan a novel, novella, or nonfiction narrative book as a durable chapter architecture with POV rules, part structure, chapter jobs, arcs, reveals, continuity state, and target length.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read core contract, style rules, story craft, brief, story bible, characters, and world.

    line 13
  2. Very specific:

    Write 01_story/book_plan.md with part or sequence architecture when useful.

    line 15
  3. Distinctive:

    Do not force every chapter to the same word count.

    line 18

≈ “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

Book Plan

Workflow

  1. Read core contract, style rules, story craft, brief, story bible, characters, and world.
  2. Decide the book's POV system, tense, approximate target length, and chapter scale only from known requirements or a small reversible assumption.
  3. Write 01_story/book_plan.md with part or sequence architecture when useful.
  4. Assign stable CH-### chapter IDs. For each chapter record POV, location and time, characters, chapter goal, conflict, turn, outcome, reveal or withheld information, continuity changes, and the causal handoff to the next chapter.
  5. Track subplot movement separately so a subplot cannot disappear for accidental stretches.
  6. Do not force every chapter to the same word count.

Done

The plan covers the complete ending, every major arc changes across the book, and a future session can draft any chapter from saved project state without needing chat memory.

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.