All skills
danjdewhurst avatar

/scene-craft

@0ced653

This skill should be used when the user asks to "plan a scene", "scene structure", "sequel scene", "dialogue subtext", "deep POV", "psychic distance", "try fail", "scene cards", "exposition", "info dump", "flashback", "time skip", "story opening", "first page hook", "introduce a character", "scene outcome", "yes-but no-and", "chapter hook", or wants scene-level craft for drafting or revision. NOT for book-level pacing or act structure (use plot-structure).

Use this Skill: https://skilld.dev/gh/danjdewhurst/story-skills/scene-craft

This session only. Nothing lands on disk.

referencesscene-cards.md

≈702 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Scene Cards

A scene card is the planning unit between a plot beat and a chapter draft: one card per scene, each recording what changes. Use cards when a chapter has multiple POV lines or timelines to braid, or when scenes need reordering before drafting. They are the cheapest place to fix structure — reordering cards costs minutes; reordering drafted scenes costs days.

Card contents

One card per scene, with exactly these fields:

  • Scene id: chapter-{NN}-scene-{NN} (matches the scenes/ record id)
  • POV: who carries the scene
  • Location: where
  • Start state: the situation, the POV character's emotional state, and the open question at the scene's beginning — one line each
  • Change: what shifts by the scene's end (plot fact, relationship, knowledge, or emotional state). If nothing changes, the card has no reason to exist — cut, fold, or combine it.
  • End state: the new situation and the new open question
  • Type: Scene (goal → conflict → outcome) or Sequel (reaction → dilemma → decision); see scene-sequel.md
  • Try/fail position: try-1, try-2, try-3, or setback when part of an escalation chain; see try-fail.md
  • Arcs advanced: which arcs move in this scene (kebab-case ids)

Store the card in the scene's scenes/ file under a ## Scene Card section, or as a block at the top of the chapter outline. Keep the format identical everywhere so a later agent can read them.

Reordering

Lay the cards out and check:

  1. Causality: each card's start state must follow from the previous card's end state. Gaps are plot holes; contradictions are continuity errors.
  2. Escalation: across the chapter, stakes, pressure, or emotional cost rise. A card that lowers tension after the midpoint needs a reason.
  3. Rhythm: alternate scene types. Two pure action scenes back-to-back flatten; a sequel between them deepens both.
  4. Reader knowledge vs character knowledge: mark cards where the reader learns something the POV character doesn't (or vice versa). Unplanned dramatic-irony gaps are continuity bugs; planned ones are logged in continuity/questions/.

Braiding POV lines

When a chapter or sequence alternates POV characters:

  1. Write one card stack per POV line.
  2. Interleave so each line's cliffhanger resolves at least two of its own cards later — never cut away at a resolution, always at an unresolved question.
  3. Record the interleave order in the chapter outline and mirror it in the scenes/ card stack.

When to ask the user

Reordering changes story shape. Present the proposed new order as a card list (start state → change → end state per card) and get approval before rewriting scene files or the chapter outline. Do not reorder silently.

Source: SKILL.md on GitHub

No alerts2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill provides a comprehensive framework for planning and drafting individual scenes within a story project, covering dialogue subtext, psychic distance, and narrative structure. It integrates with a local Story CLI and maintenance scripts to perform project-level tasks like reindexing, continuity validation, and pacing analysis. No security risks were detected in the skill's instructions or workflow.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: LOW · No issues

Signed by skilld at 0ced653. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 4 days ago

README badge

README badge for danjdewhurst/story-skills/scene-craft