fatihguner/foreman/building-story-stakes
Claude Code and agent skill by fatihguner/foreman
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install fatihguner/foreman/building-story-stakesSKILL.md
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.
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/foreman/skills/building-story-stakes/SKILL.md
Popularity
- Repository stars
- 52
- Repository forks
- 9
- Repository npm downloads, 7 days
- 4
- 7-day trend score
- 30
Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 28 Apr 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/fatihguner/foreman/building-story-stakes)