Building Story Stakes logo

Building Story Stakes

Community
fatihguner
building-story-stakes

Teaches five named techniques for creating and sustaining narrative tension in any story. Applies when a founder needs to hold an audience's attention through a pitch, investor update, all-hands talk, or customer case study. Use when a narrative feels flat, when attention wanders mid-presentation, or when the storyteller senses the audience could walk away without consequence.

Overview

Publisherfatihguner
Repositoryforeman
Skill namebuilding-story-stakes
Stars
63
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by fatihguner on GitHub. Read the source before you install it.

Installation

Install the Building Story Stakes AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/building-story-stakes
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/fatihguner/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/plugins/foreman/skills/building-story-stakes .claude/skills/building-story-stakes
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Building Story Stakes in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Building Story Stakes on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Building Story Stakes is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Building Story Stakes

What keeps a listener hooked is not curiosity. It is the elephant you planted at the beginning -- the question they desperately need answered. Stakes are the gears that make stories work; without them, any narrative, however polished, becomes something an audience can take or leave. The framework identifies five discrete techniques for infusing stakes into a story, each learnable and each deployable in settings ranging from a Moth stage to a Series A pitch meeting. The entrepreneur who masters these techniques does not merely tell stories. That entrepreneur controls attention.


The Framework

Stakes answer a deceptively simple question: would the audience want to hear the next sentence? If the answer is no, the story has failed -- not in content, but in architecture. These five strategies address different failure modes of attention, and they work in combination. Some stories need all five. Others, naturally loaded with drama, need only the first. The key is diagnosis: knowing which strategy a given moment demands.

1. The Elephant

Every story must have an Elephant. The Elephant is the large, obvious thing in the room -- a clear statement of the need, the want, the problem, the peril, or the mystery. It tells the audience what to expect, gives them a reason to wonder, and infuses the story with instantaneous stakes.

The Elephant should appear within the first sixty seconds. Thirty seconds is better. Storytellers lack the luxury of trailers; when a speaker begins, the audience has no idea whether they are hearing a comedy, a tragedy, or a waste of their morning. Without an early Elephant, listeners check out.

The distinction matters. Consider two openings for the same company origin story:

  • Version A: "Our co-founder grew up in a small town in Ohio. She studied engineering at State. She worked at three companies before starting ours."
  • Version B: "When our co-founder was twenty-six, she bet her entire savings -- $11,400 -- on a product nobody in her industry believed would work. Our co-founder grew up in a small town in Ohio..."

Version B has an Elephant. The character sketch that follows is identical, but now the audience carries a question: did she lose everything?

Elephants can change colour. A story may begin with one apparent direction and reveal a deeper one. The pitch deck that opens with "How do we reduce churn by 40%?" may end on a far more interesting question about customer identity. The audience believes they are on one path; the storyteller reveals it was always a different, richer one. This is not bait-and-switch. The path was the same all along. Only its depth was hidden.

2. The Backpack

A Backpack loads the audience with the storyteller's hopes, fears, and plans before moving the story forward. Its purpose is twofold: make the audience wonder what will happen next, and -- more ambitiously -- make them feel something close to what the storyteller felt in the moment.

The mechanism is plan articulation. Before a critical scene, the storyteller explains the plan in full. If the plan then fails, the audience experiences something like the same disappointment the storyteller felt. They knew the plan. They wanted it to succeed. Their shoulders slump.

This is why heist films explain the robbery before the heist begins. Danny Ocean's crew lays out every step so that the audience becomes a member of the team. When things go wrong, the frustration is shared.

For entrepreneurs: Before describing a product launch, a fundraising round, or a pivotal customer meeting, lay out the plan. Detail the strategy, the hoped-for outcome, the metrics that would signal success. Then describe what actually happened. The gap between plan and reality is where the audience lives.

Plans that work perfectly make terrible stories. Perfect execution is the province of narcissists and thin-skinned egotists, as the framework bluntly observes. The audience wants struggle before triumph.

3. Breadcrumbs

Breadcrumbs are small hints dropped about a future event -- just enough to keep the audience guessing, never enough to let them guess correctly. The storyteller reveals one intriguing detail and withholds the rest.

The trick is selectivity. Choose Breadcrumbs that create maximum wonder without telegraphing the outcome. They are most effective when something truly unexpected is coming. A single well-placed detail -- "and then I noticed the crumpled uniform in the backseat" -- can keep an audience leaning forward through an otherwise expository passage.

4. The Hourglass

When the audience is hanging on every word, the Hourglass says: let them hang. At the precise moment the story reaches its most anticipated beat, the storyteller slows down. Introduces unnecessary (but evocative) detail. Describes things that do not require description. Grinds the narrative to a halt.

This feels counterintuitive. The instinct is to rush toward the payoff. Resist. The Hourglass works because the audience already wants the next sentence more than anything. Every second of delay compounds the tension.

The technique is demonstrated by describing a McDonald's uniform in granular detail at the exact moment the audience needs to know what happens when a door opens. "Blue shirt. Blue pants. Blue tie. Gold name badge." The story has stopped. The audience cannot breathe.

In a pitch context: When you reach the moment of product-market fit revelation, the first major customer win, or the turning point that changed everything -- slow down. Add sensory detail. Set the scene with physical specifics. Make the investor wait five more seconds for the number they need.

5. The Crystal Ball

A Crystal Ball is a false prediction made by the storyteller to cause the audience to wonder whether it will prove true. It exploits the human compulsion to anticipate the future.

"I was sure the investor was going to say no. I could see it in the way he closed his notebook." This prediction -- stated explicitly -- makes the audience hold its breath. Even if the prediction is wrong (especially if it is wrong), the audience needed to find out.

Deploy Crystal Balls when the prediction seems plausible, when the guess is reasonable, and when the predicted outcome presents an intriguing or frightening possibility.

The Supplementary Principle: Make the Big Story Little

Large, dramatic events -- near-death experiences, massive failures, extraordinary successes -- are paradoxically the hardest stories to tell. The big parts are singular, unusual, and difficult to relate to. The secret: find the small, specific, personal moment hidden inside the big event.

A story about nearly going bankrupt is not really about the bank balance. It is about the look on a co-founder's face across a kitchen table at 2 a.m. A story about closing a transformative deal is not about the contract. It is about the three-word text message sent to a spouse from a parking garage.

Big themes land only through small, concrete details. The founder who says "we almost died as a company" connects with no one. The founder who describes eating ramen at a desk at midnight, watching the last $4,000 leave the account, and then receiving an email with a subject line that changed everything -- that founder makes the room hold its breath.


Prompts

Prompt 1 -- Elephant Identification:

I need to present [a pitch / an investor update / a company story] about [topic]. The key transformation or revelation is [describe it]. Help me craft an Elephant -- a clear, compelling statement of need, want, problem, or mystery -- that I can deliver within the first 30 seconds. The Elephant should make the audience desperate to hear what happens next. Also suggest how the Elephant's colour might change by the story's end.

Prompt 2 -- Backpack Construction:

I am telling the story of [a product launch / fundraising round / customer win]. Before the critical moment, I want to load my audience with my plans and hopes so they feel the weight of what follows. Help me articulate the plan, the expected outcome, and the emotional stakes in a way that makes the audience co-invest in the result. Then show me how the gap between plan and reality creates narrative tension.

Prompt 3 -- Full Stakes Audit:

Here is a narrative I plan to deliver: [paste draft or outline]. Audit it for stakes using the five techniques (Elephant, Backpack, Breadcrumbs, Hourglass, Crystal Ball). Identify where attention might wander. Recommend specific insertions of each technique at precise moments. Flag any "big story" moments that need to be made smaller and more personal.

Prompt 4 -- Hourglass Moment Design:

The climax of my story is [describe the key reveal or turning point]. Help me design an Hourglass moment around it: what sensory details can I add, what unnecessary-but-evocative description can I layer in, and how should I slow my pacing to maximise the tension just before the payoff?


Use Cases

Series A Pitch -- SaaS Founder

A founder pitching enterprise software opens with three minutes of product features. Attention drifts. Applying the framework: she opens with an Elephant ("Eighteen months ago, our largest customer called to say they were leaving -- and that call saved the company"). She uses a Backpack before describing the product pivot ("Our plan was simple: rebuild the entire integration layer in six weeks with a team of four"). She drops a Breadcrumb ("I still had the resignation letter in my drafts folder"). She deploys an Hourglass at the moment of product-market fit revelation, slowing down to describe the Slack message from the customer's CTO. The pitch transforms from a feature walkthrough into a story the room cannot leave.

All-Hands Address -- Post-Layoff

A CEO addresses a shaken team after a reduction in force. The big story (layoffs, financial pressure, survival risk) is inherently difficult to connect with at scale. The CEO makes it little: she describes a single conversation with a departing colleague, the specific object on his desk he packed last, and the sentence he said as he left. The Elephant is planted at the outset ("This morning I want to tell you about one conversation that changed how I think about what we owe each other"). The Crystal Ball appears mid-narrative ("I was certain he was going to be angry. I had rehearsed for anger"). The small moment carries the weight that the big narrative cannot.


Anti-Patterns

  • The Missing Elephant. Beginning a story with context, background, or credentials before establishing what is at stake. If the audience does not know why they are listening within the first minute, they have already stopped. Most failed pitches and company narratives suffer from this structural defect.

  • The Perfect Plan. Describing a strategy that executed flawlessly. The Backpack technique only works when the plan encounters friction. Audiences want suffering before triumph. A founder who describes a seamless journey from idea to traction sounds either dishonest or uninteresting.

  • Rushing the Hourglass. Sprinting through the most anticipated moment because the storyteller is eager to deliver the payoff. The payoff gains its power from delay. Rushing it is the narrative equivalent of lighting a firework indoors.

  • Stacking Stakes Without Resolution. Deploying Breadcrumbs, Crystal Balls, and Backpacks in rapid succession without ever paying them off. Each technique creates a promise to the audience. Broken promises erode trust faster than absent stakes erode attention.

  • Confusing Big with Compelling. Assuming that dramatic events automatically make good stories. The founder who says "we nearly went bankrupt" without finding the small, human, relatable moment inside the crisis tells a story nobody can connect to. Grand scale is not a substitute for personal specificity.


By Stage

StageFocusKey Difference
IdeaThe Elephant is existential: does this problem matter?Stakes must be borrowed from the customer's pain, since the company has no history to draw from yet
ValidationBackpacks and Crystal Balls dominate: plans are made, predictions testedThe narrative tension lives in the gap between hypothesis and evidence
Early TractionBreadcrumbs become available as real customer stories accumulateThe storyteller can now hint at outcomes before revealing them, because outcomes exist
GrowthThe Hourglass becomes critical for investor narratives and team alignmentAudiences are sophisticated; they need to be slowed down at key moments, not sped through them
ScaleElephants must change colour: the company's story is no longer what it appearsThe most powerful narratives at scale reveal that the real stakes were always something deeper than revenue

At the idea stage, founders frequently attempt to manufacture stakes through hyperbole ("This is a trillion-dollar market"). Manufactured stakes are transparent and counterproductive. Genuine stakes at this stage come from the founder's personal connection to the problem -- the small story hidden inside the big ambition.


Output Template

markdown
# Narrative Stakes Worksheet

## Story Summary
[One sentence describing the story you intend to tell]

## The Elephant
- **Core question planted for the audience:** [What need / want / problem / mystery?]
- **Appears by second:** [Target: within 30 seconds]
- **Colour change (if any):** [What the story appears to be about vs. what it is really about]

## Backpack Moment(s)
- **Plan articulated before scene [X]:** [Describe the plan and hoped-for outcome]
- **Actual result:** [What happened instead]
- **Emotional gap:** [What the audience should feel]

## Breadcrumbs
- **Hint dropped at [moment]:** [The detail revealed]
- **What it foreshadows:** [What the audience cannot yet guess]

## Hourglass Moment
- **Scene to slow down:** [The most anticipated beat]
- **Details to add:** [Sensory, environmental, physical specifics]
- **Duration of delay:** [How many additional seconds / sentences]

## Crystal Ball
- **False prediction stated at [moment]:** [What the storyteller expected]
- **Actual outcome:** [What happened instead]

## Big-to-Little Check
- **The big event:** [What happened at macro level]
- **The small moment inside it:** [The specific, personal, relatable detail]

Related Skills

  • Storytelling Truth and Vividness -- Stakes lose their power if the audience cannot see the story; vividness techniques ensure the Hourglass and Breadcrumbs land in a cinematic mental image.
  • Emotional Impact in Stories -- Stakes create tension; emotional impact techniques convert that tension into tears, laughter, or action at the moment of release.
  • Story Performance and Delivery -- Written stakes must be performed: pacing, tense shifts, and vocal control determine whether an Hourglass moment actually slows the room.
  • Story Structure and Arc -- The five-second moment provides the target that stakes build toward; without clear structure, even well-crafted stakes dissipate before the payoff.
  • Storytelling for Leaders -- The leadership-application counterpart; focuses on when and why leaders deploy stories, whereas this skill addresses the craft of making them hold attention.
  • Writing for Response -- The Breadcrumbs technique for maintaining audience attention operates on the same cognitive principle as friction reduction in written calls to action: keep the reader moving forward.

Frequently asked questions

What does the Building Story Stakes AI skill do?

Teaches five named techniques for creating and sustaining narrative tension in any story. Applies when a founder needs to hold an audience's attention through a pitch, investor update, all-hands talk, or customer case study. Use when a narrative feels flat, when attention wanders mid-presentation, or when the storyteller senses the audience could walk away without consequence.

Why use Building Story Stakes on TypingMind?

Because you install it once and use it with any model. Building Story Stakes is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Building Story Stakes in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/building-story-stakes. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Building Story Stakes?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Building Story Stakes?

As many as you like. As long as a model supports skills, you can use Building Story Stakes with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Building Story Stakes AI skill free?

Yes. It is published on GitHub by fatihguner under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇