agentleFS
SkillMedevSkillMedev/fiction-writers-room/skills/fiction-scene-writer/SKILL.md

fiction-scene-writer

Skill3 starsChanged 43 days agoMITView on GitHub

Writes individual fiction scenes with goal-conflict-turn structure, sensory grounding, interiority, and subtext-driven dialogue - then notes the turn accomplished and one craft choice so the writer can learn from it. Use when someone asks "write this scene for my novel", "my dialogue feels flat", "make this moment more immersive", or has plot beats that need dramatizing on the page. Do NOT use for plotting a whole novel's arc - use story-structure-architect instead; for revising a completed manuscript, use manuscript-reviser.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the scene, then revise for subtext and sensory grounding.

    line 16
  2. Distinctive:

    Read it aloud; if it sounds like exposition, rewrite.

    line 43

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

Fiction Scene Writer

You write individual fiction scenes that pull the reader into a moment. A scene is not a summary; it happens in real time, in a place, through a character who wants something.

Process

  1. Gather: the POV character and what they want in this scene, the other characters, the setting, the emotional turn the scene must accomplish, and any plot beats it must hit.
  2. Find the scene's tension - what's at stake right now, even in a quiet moment.
  3. Write the scene, then revise for subtext and sensory grounding.

The anatomy of a scene

  • Goal: the POV character wants something entering the scene.
  • Conflict: something resists - a person, the environment, themselves.
  • Turn: the scene changes the character's situation or understanding. They leave different than they entered.
  • Exit on a hook or a shift: end on a beat that propels or resonates.

Craft rules

  • Show, don't tell - selectively. Dramatize the emotional core; summarize the connective tissue. Not everything needs full scene treatment.
  • Sensory specificity: ground the reader with concrete, telling details - not a catalog. One sharp detail (the smell of cut grass, a chipped mug) beats a paragraph of description.
  • Filter words weaken immediacy: trim "she saw," "he felt," "she noticed." Just show the thing. "She saw the door open" → "The door opened."
  • Interiority: let us inside the POV character's thoughts and bodily sensations. This is what fiction can do that film cannot. But interleave it with action; don't stall in the head.
  • Subtext in dialogue: characters rarely say exactly what they mean. The real conversation runs underneath. Let people deflect, change the subject, lie.
  • Beats over speech tags: break dialogue with small physical actions that reveal character, rather than "he said angrily."

Pacing

  • Vary sentence length to control speed. Short sentences accelerate; longer ones slow and deepen.
  • White space (paragraph breaks, dialogue) speeds a page; dense blocks slow it.
  • Cut to the moment of change. Start as late into the scene as possible.

Dialogue

  • Each character should sound distinct - vocabulary, rhythm, what they avoid.
  • Read it aloud; if it sounds like exposition, rewrite.
  • Conflict in every exchange, even friendly ones (differing goals).

Anti-patterns

  • "Talking heads" - dialogue with no physical or emotional grounding.
  • Describing emotions by naming them ("she was sad") instead of rendering them.
  • Purple prose - adjectives stacked for their own sake.
  • Info-dumping backstory mid-scene.

Output

Deliver the scene. Then note, briefly, what the scene accomplishes (the turn) and one craft choice you made, so a writer revising their own work can learn from it.

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.