plot-causal-bridges
/plot-causal-bridges
Use when events follow one another but do not cause each other, an outline reads as a list of interesting incidents, a turn feels arbitrary, or a character does something because the plot needs it. Tests each major turn for why this person, why now, why this method, and what it changes.
- Author
- saigauthamr ↗
- Repository
- fiction-craft-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when events follow one another but do not cause each other, an outline reads as a list of interesting incidents, a turn feels arbitrary, or a character does something because the plot needs it. Tests each major turn for why this person, why now, why this method, and what it changes.
Original author description
Use when events follow one another but do not cause each other, an outline reads as a list of interesting incidents, a turn feels arbitrary, or a character does something because the plot needs it. Tests each major turn for why this person, why now, why this method, and what it changes.
How it works
- The bridge
- The removal test
- Building the spine
- Checks
- Cautions and exceptions
SKILL.md preview
--- name: plot-causal-bridges metadata: type: framework description: > Use when events follow one another but do not cause each other, an outline reads as a list of interesting incidents, a turn feels arbitrary, or a character does something because the plot needs it. Tests each major turn for why this person, why now, why this method, and what it changes. --- # Causal Bridges Events in order are not automatically a story. A plot holds when each turn is caused by the one before it, through someone's choice. ## The bridge Between any two major turns, the chain should be readable: new pressure or evidence, then a specific actor interprets it, then pursues a goal, then picks a method, then the choice changes someone else's options, then a visible consequence creates the next event. At each turn, ask: **Why this person? Why now? Why this method? What was already true? What did this decision newly cause?** ## The removal test If taking an event out would not change the next decision, either the bridge is missing or the event is not on the story's spine. Keep it only if it earns something else (a promise, a character beat). ## Building the spine - **Cause before system.** Write the causal story first: the starting situation, how it begins through someone acting, the turns, the climax, and the resulting state. Explain the machinery behind it afterward. - **Start through an actor.** The first on-page change is an assignment, an encounter, or a mistake, not a thematic statement like "the hero enters a hidden order." - **Anchor before use.** Establish a place, group, system, or important person before asking it to carry an event. Readers should not meet the followers before the organization exists, or a victim before their situation is known. - **No summary jumps.** "Attention grew, so the villain picked a victim" hides everything. Say what pressure the attention created, what the villain wanted, why this victim served that, and who acted. ## Checks - `plot.bridges.01` For each major turn, can you name the pressure, the actor who interprets it, their goal, and their method? - `plot.bridges.02` Why this person, why now, and why this method? - `plot.bridges.03` If this event were removed, would the next decision change? If not, it is off the spine or a bridge is missing. - `plot.bridges.04` Does any turn rest on a summary jump (A happened, so B) with no one choosing? - `plot.bridges.05` Is every place, group, or person established before it carries an event? ## Cautions and exceptions - Discovery writers can find the bridges in revision. A missing one is a question to answer, not a failure. - A coincidence can start trouble. One that solves it needs setup; see `plot-payoff-deniability-forgotten-promise`. - For generating the next complication, see `plot-yes-but-no-and`. For what the reader is promised along the way, see `plot-promise-progress-payoff`.
Versions
The database has no other skills named plot-causal-bridges.
Database snapshot: 13.11.2026 · package version cc1ed11430ed (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100plot-outline-interwoven-cycles
Use when you need to outline a book with several plotlines, viewpoints, a romance or a mystery thread, you lose track of promises across a long draft, or you are unsure how outlining fits your writing style. Gives a method for listing each plot cycle's progress beats and merging… - 90plot-reveal-boundaries
Use when a story has secrets, a mystery, or a hidden system, you are unsure when readers should learn what, or an outline explains the mechanism before the story makes anyone care. Separates what is true, what each character knows, and when the reader learns it.