agentleFS
FiredMosquito831FiredMosquito831/my-writing-companion/skills/story-planning/SKILL.md

story-planning

Skill2 starsChanged 26 days agoApache-2.0View on GitHub

Planning work before prose: creative direction, story-planning, outlining, and story architecture. Load when deciding what should happen or how a story should be structured.

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this for pre-page decisions: what the story wants, what options exist, and how chosen direction becomes outline structure.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Story Planning

Use this for pre-page decisions: what the story wants, what options exist, and how chosen direction becomes outline structure. Do not use it for production prose or critique.

Load only the resource needed:

  • resources/creative-direction.md — author-facing direction and option synthesis.
  • resources/brainstorming.md — exploratory capture and source tagging.
  • resources/story-architecture.md — arc, chapter, scene, and beat structure.
  • resources/structure-beats.md — K.M. Weiland 10 landmark beats (Hook through Resolution) + James Scott Bell 14 signposts with percentage positions; each beat annotated with the word-quota convention.
  • resources/scene-cards.md — 9-field scene card (Characters, Place, Time, Event, Conflict, Story value, Value charge, Mood, Outcome) plus a template block.
  • resources/try-fail.md — the arc-level failure ladder: 2–3 attempts before the arc goal succeeds, each costing more; yes-but/no-and as plotting outcomes. Load when outlining an arc or diagnosing a saggy middle.

When the book is linked to a series library, plan with the do-not-re-explain register and the series state card in context: facts established before this book are listed as "Established before this book — do not re-explain." New characters, props, and world facts that enter series scope get a series-id: join key on their kb entity frontmatter (opt-in; absent = invisible to the layer). See /series for the command surface and /series-bible for the bible schema and field conventions.

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.