Skip to content
Skills Library
Other · Writing

plot-foreshadowing-twists

/plot-foreshadowing-twists

Use when beta readers guessed the twist, nobody saw it coming, a reveal feels unearned, or you are adding foreshadowing in revision. Gives a target for how many readers should guess, fixes for both extremes, and ways to hide a clue in plain sight.

Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

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 beta readers guessed the twist, nobody saw it coming, a reveal feels unearned, or you are adding foreshadowing in revision. Gives a target for how many readers should guess, fixes for both extremes, and ways to hide a clue in plain sight.

Original author description

Use when beta readers guessed the twist, nobody saw it coming, a reveal feels unearned, or you are adding foreshadowing in revision. Gives a target for how many readers should guess, fixes for both extremes, and ways to hide a clue in plain sight.

How it works

  1. The target
  2. Steps
  3. Fixing the extremes
  4. Ways to hide a clue
  5. Checks
  6. Cautions and exceptions
Original SKILL.md headings · 44 lines, 542 words
SKILL.md preview
---
name: plot-foreshadowing-twists
metadata:
  type: framework
description: >
  Use when beta readers guessed the twist, nobody saw it coming, a reveal feels unearned, or you are adding foreshadowing in revision. Gives a target for how many readers should guess, fixes for both extremes, and ways to hide a clue in plain sight.
---

# Foreshadowing and Twists

Foreshadowing is the setup that makes a payoff or twist feel earned. It is easy to adjust in revision, so a draft with a surprise at the end can be fixed later, including by writers who discover the story as they go.

## The target

Aim for most readers to guess the twist only a page or a paragraph before the reveal. Some will guess early, which cannot be avoided. A twist that no reader could possibly have guessed is a complication, not a twist, because nothing was signposted.

## Steps

1. List every reveal or payoff that must feel earned.
2. For each, mark where the reader first gets a clue and how many clues there are.
3. Add or cut scenes and lines to move the guess point toward the target.
4. Give early readers the draft and ask them to say when they first guessed and what gave it away.

## Fixing the extremes

- **Nobody saw it.** Add clues. Turning foreshadowing up is easy.
- **Everyone guessed in the first act.** Dial the clues back, but note that turning foreshadowing down is harder, and a red herring is harder still to insert. Alternatively, convert the twist into suspense: let the reader know the secret and watch the characters walk into it. Make sure the characters do not look foolish for missing what the reader sees.

## Ways to hide a clue

- Use genre and narrative expectations. Readers follow tropes and look where stories usually look.
- Mention it three times before it matters, so the third time reads as familiar.
- Follow the characters' attention. Readers look where the viewpoint looks, so a clue the viewpoint ignores slips by.
- Have a character remark on an oddity. A character who notices the strange detail and shrugs it off lets the reader shrug too.
- Show a character's quality through other people's eyes, which lets you build a reputation without the character boasting.
- Highlight an object that seems significant to use as a red herring for a different payoff.

## Checks

- `plot.foreshadow.01` For each reveal that must feel earned, where does the reader get the first clue, and how many clues are there?
- `plot.foreshadow.02` Is the likely guess point a page or a paragraph before the reveal, and not "never" or "the first act"?
- `plot.foreshadow.03` If readers guess too early, would turning the twist into suspense serve better than hiding it harder?
- `plot.foreshadow.04` Does a shocking event serve theme, character, and plot, or only shock?

## Cautions and exceptions

- Shock for its own sake needs no skill. Shocking deaths can work when the theme supports them, but the value is in how characters respond. Treat them as complications unless they serve theme, character, and plot.
- A well-foreshadowed twist that readers spot and still enjoy makes a durable book. Do not rewrite a sequel to dodge what early readers guessed, as that tends to hurt the series.
- If the story will change kind midway, such as from classic quest to deconstruction, signal the direction in the promises at the start. Without that, you risk losing both audiences.
- Pair with `plot-twists-promise-and-wish` and `plot-payoff-deniability-forgotten-promise`. Core model is `plot-promise-progress-payoff`.

Versions

The database has no other skills named plot-foreshadowing-twists.

Database snapshot: 13.11.2026 · package version 2d26118eb342 (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

  • 90plot-twists-promise-and-wish
    Use when you want a twist that lands, a reveal feels random or cheap, or you are unsure whether the story needs a twist at all. Gives the promise-and-wish method (promise one thing, make the reader wish for another, deliver that) and the alternatives of escalation and over-delivery.
  • 100novel-twist-architect
    Use when engineering shocking, airtight plot twists, red herrings, misdirection, and climactic reveals — applies the Fair-Play Clue Protocol, Recontextualization Mechanics, and Aristotelian Peripeteia & Anagnorisis.
  • 90plot
    Use for plot, structure, pacing, weak openings, dragging middles, unsatisfying payoffs, or outline methods. Routes to frameworks for promises, progress, conflict, twists, and climaxes.
  • 90foreshadowing-suspense
    Use when designing foreshadowing, clues, suspense, reveals, mystery payoff, hidden identity, or information-release rhythm.
  • 100foreshadowing-system
    Use when user wants to manage foreshadowing (伏笔), track story hooks, or check pending reveals. Triggers include "伏笔", "埋伏笔", "待回收", "伏笔状态".
  • 100foreshadowing-system
    Use when user wants to manage foreshadowing (伏笔), track story hooks, or check pending reveals. Triggers include "伏笔", "埋伏笔", "待回收", "伏笔状态".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.