---
name: storytelling-advisor
description: Shape pitches, brand stories, presentations, and creative writing with narrative frameworks such as the Hero's Journey, Story Spine, and Freytag's Pyramid. Use when a user wants to structure, critique, or strengthen a story.
version: 1.0.0
license: MIT
---

# Storytelling Advisor

## What It Does

Transforms raw ideas, experiences, or messages into structured narratives using proven storytelling frameworks. Whether you're writing a brand story, a keynote, a pitch deck, or a social media thread, this skill helps you find the right structure, emotional arc, and narrative tension.

## Fact and Fiction Boundary

- For case studies, pitches, testimonials, biographies, and other factual narratives, use only facts the user supplied or explicitly confirmed.
- Never silently invent names, quotations, dates, durations, metrics, customers, outcomes, motives, or events to make a factual story more compelling.
- Mark missing material as a question, a placeholder such as `[customer outcome needed]`, or an explicitly labeled illustrative option.
- Invent details only when the user requests fiction or explicitly authorizes creative fabrication. Keep fictional additions distinguishable from factual claims.

---

## Frameworks Available

### 1. The Hero's Journey (Monomyth)

**Best for**: Brand origin stories, founder journeys, case studies, transformation narratives

| Stage | Description | Prompting Question |
|-------|-------------|-------------------|
| **Ordinary World** | The hero's normal life before the adventure | What was life like before the problem was solved? |
| **Call to Adventure** | An event disrupts the status quo | What changed? What forced action? |
| **Refusal of the Call** | Doubt, hesitation, fear | What almost stopped you from taking action? |
| **Meeting the Mentor** | A guide provides wisdom or tools | Who or what showed the way? |
| **Crossing the Threshold** | Commitment to the journey | What was the point of no return? |
| **Tests, Allies, Enemies** | Challenges, support, obstacles | What went wrong along the way? Who helped? |
| **Approach to the Inmost Cave** | Preparing for the biggest challenge | What was the hardest obstacle you faced? |
| **Ordeal** | The central crisis | What was make-or-break moment? |
| **Reward** | The prize for surviving the ordeal | What did you gain? |
| **The Road Back** | Returning to normal life with new wisdom | How did things change after? |
| **Resurrection** | Final test — applying the lesson | How did you prove the transformation was real? |
| **Return with Elixir** | Sharing the lesson with the world | What can others learn from this journey? |

### 2. Pixar Storytelling Formula

**Best for**: Short-form narratives, social media stories, email sequences, product launches

> **Structure**: Once upon a time there was **\_\_\_**. Every day, **\_\_\_**. One day **\_\_\_**. Because of that, **\_\_\_**. Because of that, **\_\_\_**. Until finally **\_\_\_**.

| Element | Role | Fictional product-story example |
|---------|------|----------------------|
| **Once upon a time...** | Setup — who, where, when | "Once upon a time, a community organizer struggled to coordinate neighborhood repairs." |
| **Every day...** | Status quo — the routine struggle | "Every day, useful items were discarded because neighbors could not find help." |
| **One day...** | Inciting incident | "One day, the organizer sketched a simple repair-matching service." |
| **Because of that...** | Consequence 1 | "Because of that, volunteers could list the skills they offered." |
| **Because of that...** | Consequence 2 | "Because of that, neighbors could match broken items with local help." |
| **Until finally...** | Resolution | "Until finally, the first fictional repair day could be coordinated in one place." |

### 3. Freytag's Pyramid (Dramatic Structure)

**Best for**: Speeches, presentations, campaign narratives

| Element | Purpose |
|---------|---------|
| **Exposition** | Context — what's the situation? |
| **Rising Action** | Tension builds — what's at stake? |
| **Climax** | The turning point — the big reveal or decision |
| **Falling Action** | Consequences unfold |
| **Denouement** | Resolution and takeaway |

### 4. The Story Spine

**Best for**: Team storytelling, collaborative narrative building

> Once upon a time... And every day... But one day... And because of that... And because of that... And because of that... Until finally... And ever since that day... The moral of the story is...

### 5. The Inverted Pyramid

**Best for**: Newsletters, blog posts, executive summaries

| Layer | Content |
|-------|---------|
| **Lead** | The most critical information (who, what, when, where, why) |
| **Body** | Supporting details, context, evidence |
| **Tail** | Background, nuance, optional reading |

---

## Trigger Phrases

| Phrase | Action |
|--------|--------|
| "Help me tell a story about..." | Guides you through selecting the best framework |
| "Turn this into a narrative..." | Structures raw info into a story arc |
| "Make this more compelling..." | Suggests adding stakes, tension, or emotional beats |
| "Tell my brand story..." | Applies Hero's Journey to brand/founder narrative |
| "Pixar this for me..." | Forces content into the Pixar formula |
| "What framework should I use for..." | Recommends the best framework for your context |
| "Pitch this as a story..." | Converts a pitch into narrative form |

---

## Step-by-Step Instructions

### Step 1: Clarify the Goal
Infer what the audience should **feel**, **think**, and **do** from the request. Ask one focused
question only when the missing goal would materially change the story.

### Step 2: Harvest the Raw Material
Collect:
- Characters (who is the hero? who is the mentor? who is the antagonist?)
- Setting (where and when does this happen?)
- Conflict (what was the problem or challenge?)
- Stakes (what was at risk?)
- Transformation (how did things change?)
- Lesson (what can be learned?)

Separate confirmed facts from assumptions and gaps before drafting. Ask only for gaps that materially affect the story; otherwise retain visible placeholders.

### Step 3: Select the Framework
Match the story type to the right structure:

| If you're telling... | Use... |
|---------------------|--------|
| A founder origin story | Hero's Journey |
| A product value prop | Pixar Formula |
| A keynote or speech | Freytag's Pyramid |
| A social media thread | Story Spine |
| A newsletter or article | Inverted Pyramid |

### Step 4: Map Content to Structure
Fill each framework slot with your raw material. Identify gaps and missing beats.

### Step 5: Add Narrative Devices
- **Emotional hook**: Start with a relatable moment or surprise
- **Specific details**: Prefer concrete details supplied by the user. Never add a detail such as "3 AM in a coffee shop" to a factual account unless it is confirmed.
- **Tension**: What was almost lost? What was uncertain?
- **Pacing**: Short sentences for action, longer ones for reflection

### Step 6: Refine and Cut
- Remove everything that doesn't serve the goal
- Read aloud to test rhythm
- Tighten: Can you say it in half the words?

### Step 7: End with a Punch
The last line should be memorable — a lesson learned, a question posed, an invitation extended.

---

## Examples

### Example 1: Factual Founder Story with Gaps

> **Input**: "I built a project management tool because Trello was too simple and Jira was too complex."
>
> **Output** (outline):
> - **Problem**: Existing tools felt either too simple or too complex for the user's needs.
> - **Action**: The user built a project management tool.
> - **Outcome**: `[What changed for you or your users?]`
> - **Evidence needed**: `[Who first used it?]` `[What measurable result can be verified?]`
>
> Do not add a company size, customer crisis, development timeline, adoption count, or testimonial unless the user supplies it.

### Example 2: Explicitly Fictional Product Launch Exercise

> **Input**: "Create a fictional launch-story example for a new habit tracking app."
>
> **Output**:
> "**Fictional example:** Once upon a time, there was a developer who wanted a kinder way to build habits. Every day, rigid streaks made one missed day feel like failure. One day, the developer tried a tracker that welcomed restarts. Because of that, returning became easier. Until finally, the idea became an app designed around beginning again."

---

## Pro Tips

- **Start in the middle**: The most interesting story doesn't always start at the beginning. Open with the crisis, then flash back.
- **Use contrast**: Before/after, then/now, almost lost/eventually won.
- **Use verified specificity**: Real, sourced numbers are stronger than generic claims. Use placeholders when the number is not known.
- **Include a limitation**: For factual stories, include a supported challenge or trade-off rather
  than making the subject unrealistically one-dimensional.
- **End with a call-to-story**: Invite the audience to see themselves in the narrative.
