iron-edge 1.0.0

package/squads/squad-storytelling/tasks/identify-archetypes.md

@@ -0,0 +1,76 @@
+---
+task: "identify-archetypes"
+responsavel: "joseph-campbell"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Narrative, brand, or situation to analyze"
+Saida:
+  - "Archetype analysis with character/force mapping"
+Checklist:
+  - "[ ] All characters/forces mapped to archetypes"
+  - "[ ] Shadow and Trickster identified (often overlooked)"
+  - "[ ] Recommendations for strengthening archetypal resonance"
+---
+
+# Task: Identify Archetypes
+
+**Task ID:** NARR-004
+**Version:** 1.0.0
+**Command:** `*identify-archetypes`
+**Agent:** Joseph Campbell (joseph-campbell)
+**Purpose:** Identify and analyze archetypal patterns in any narrative, brand, or situation.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `narrative` | Story, brand description, or situation | YES |
+| `context` | Literary, brand, personal, organizational | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Map Characters to Archetypes
+
+For each character or force, determine which archetype(s) they embody:
+
+| Archetype | Function | Question |
+|-----------|----------|----------|
+| Hero | Undergoes transformation | Who is changed by this story? |
+| Mentor | Provides wisdom/tools | Who guides the hero? |
+| Threshold Guardian | Tests readiness | What barriers test commitment? |
+| Herald | Announces change | What signals the call to adventure? |
+| Shapeshifter | Creates uncertainty | Who cannot be fully trusted? |
+| Shadow | Represents darkness | What is the hero's dark mirror? |
+| Trickster | Breaks rules | Who brings chaos and humor? |
+| Allies | Provide support | Who stands with the hero? |
+
+### Phase 2: Analyze Archetypal Dynamics
+
+1. Is the Shadow a true dark mirror of the Hero?
+2. Does the Mentor withdraw at the right moment?
+3. Are Threshold Guardians testing the right qualities?
+4. Does the Shapeshifter create genuine uncertainty?
+5. Is the Trickster serving the story or just providing comic relief?
+
+### Phase 3: Assess Gaps and Recommendations
+
+1. Which archetypes are missing or underserved?
+2. Where could archetypal resonance be strengthened?
+3. What mythological parallels illuminate the story?
+
+## Veto Conditions
+
+- **NEVER** force an archetype where none exists — not every story uses all 8
+- **NEVER** reduce characters to single archetypes — real characters blend multiple
+- **NEVER** ignore cultural context when assigning archetypal meaning
+
+## Completion Criteria
+
+- [ ] All characters/forces mapped to archetypes with reasoning
+- [ ] Shadow and Trickster identified (or noted as absent)
+- [ ] Archetypal dynamics analyzed for effectiveness
+- [ ] Gaps identified with recommendations for strengthening

package/squads/squad-storytelling/tasks/improvised-content-creation.md

@@ -0,0 +1,137 @@
+---
+task: "improvised-content-creation"
+responsavel: "keith-johnstone"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Content topic or brand context"
+  - "Platform and audience"
+Saida:
+  - "Content pieces created using improv techniques for authenticity and spontaneity"
+Checklist:
+  - "[ ] Yes-And technique applied to build on ideas generatively"
+  - "[ ] Status transactions used for engaging content dynamics"
+  - "[ ] Content feels spontaneous and authentic, not scripted"
+---
+
+# Task: Improvised Content Creation
+
+**Task ID:** NARR-042
+**Version:** 1.0.0
+**Command:** `*improvised-content-creation`
+**Agent:** Keith Johnstone (keith-johnstone)
+**Purpose:** Apply improv theatre techniques to content creation, producing authentic, spontaneous-feeling content that breaks through the sameness of polished marketing.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `topic` | Content subject or brand context | YES |
+| `platform` | Where the content will live | YES |
+| `audience` | Who will consume it | YES |
+| `tone` | Desired energy level (playful, serious, vulnerable, bold) | PREFERRED |
+| `constraints` | Brand guidelines, topics to avoid | NO |
+
+## Execution Phases
+
+### Phase 1: Apply "Yes, And" to Idea Generation
+
+1. Start with the core topic and "Yes, And" through 10 iterations:
+   - Topic: "Our product saves time"
+   - Yes, And: "...and time is what people waste most on meaningless admin"
+   - Yes, And: "...and meaningless admin makes smart people feel stupid"
+   - Continue until you find the REAL story buried beneath the surface topic
+2. Use "Yes, And" to combine unexpected ideas:
+   - Your product + an unlikely metaphor
+   - Your audience's problem + an absurd comparison
+   - Your value prop + a personal confession
+3. Select the 3 most surprising "Yes, And" pathways for content development
+
+### Phase 2: Use Status Transactions for Engagement
+
+1. Identify the status dynamic in the content:
+   - **High-status content**: Authoritative, definitive, "here's how it's done"
+   - **Low-status content**: Vulnerable, questioning, "here's what I got wrong"
+   - **Status flip**: Start one way, switch mid-content (the surprise)
+2. Design status-play content formats:
+   - "Confession" posts: Brand/founder lowers status intentionally (builds trust)
+   - "Expert drop" posts: Brand raises status with a bold claim (builds authority)
+   - "Status flip" posts: Start humble, end authoritative (or vice versa)
+3. Map audience status: Are they feeling high-status (confident) or low-status (struggling)?
+4. Content that acknowledges audience's true status creates immediate connection
+
+### Phase 3: Create "Spontaneous" Content Formats
+
+1. **The Unscripted Take** — A seemingly off-the-cuff thought about the topic
+   - Actually structured: Hook → Observation → Insight → Callback
+   - Feels spontaneous because the language is conversational, not polished
+2. **The Failed Experiment** — Share something that went wrong, in real-time
+   - Improv principle: mistakes are gifts; they create the best content
+3. **The Unexpected Connection** — Link two unrelated things to create insight
+   - Improv principle: "obvious" connections bore; surprising connections delight
+4. **The Live Reaction** — Respond to something in your industry in the moment
+   - Improv principle: the best scenes happen when you react authentically
+5. **The Callback** — Reference something from previous content in a new context
+   - Improv principle: callbacks reward loyal audience and create inside-joke energy
+
+### Phase 4: Apply Theatresports Techniques
+
+1. **Word-at-a-time storytelling** — Build content by adding one idea at a time, letting each idea inform the next (prevents overthinking)
+2. **Emotional rollercoaster** — Alternate between emotional states within one piece
+3. **Offer and accept** — Each section of content makes an offer; the next section accepts and builds
+4. **Break routine** — After establishing a pattern in content, deliberately break it
+5. **The tilt** — Shift perspective unexpectedly mid-content (first person → second person, serious → playful)
+
+### Phase 5: Produce and Refine
+
+1. Create 5 content pieces using the techniques above
+2. For each piece, rate:
+   - Spontaneity score (1-5): Does it feel unscripted?
+   - Surprise score (1-5): Does it contain something unexpected?
+   - Connection score (1-5): Does it create intimacy with the audience?
+3. Edit for clarity without editing out the spontaneity
+4. Add structural elements (headlines, CTAs) without killing the energy
+5. Create a "content improv" practice for the team — weekly exercises that generate content ideas
+
+## Output Format
+
+```yaml
+improvised_content:
+  topic: "{subject}"
+  platform: "{channel}"
+  yes_and_pathways:
+    - pathway: "{unexpected direction}"
+      content_potential: "{what it could become}"
+  content_pieces:
+    - title: "{piece title}"
+      technique: "{yes-and/status-play/spontaneous/callback}"
+      status_dynamic: "{high/low/flip}"
+      content: "{the actual content piece}"
+      spontaneity_score: "{1-5}"
+      surprise_score: "{1-5}"
+      connection_score: "{1-5}"
+  team_exercises:
+    - exercise: "{name}"
+      description: "{how to run it}"
+      content_output: "{what it generates}"
+      frequency: "{how often}"
+```
+
+## Veto Conditions
+
+- **NEVER** over-polish improv content — the rough edges ARE the appeal
+- **NEVER** use improv techniques to be random — spontaneity serves the message
+- **NEVER** ignore status dynamics — every piece of content has status, whether you design it or not
+- **NEVER** skip the "Yes, And" process — jumping to the obvious idea misses the gold
+
+## Completion Criteria
+
+- [ ] Yes-And technique applied to generate unexpected content angles
+- [ ] Status transactions designed for engagement dynamics
+- [ ] 5 content pieces created using distinct improv techniques
+- [ ] Each piece scored for spontaneity, surprise, and connection
+- [ ] Team improv exercises designed for ongoing content generation
+- [ ] Content feels authentic and spontaneous while serving the brand message

package/squads/squad-storytelling/tasks/internal-change-presentation.md

@@ -0,0 +1,155 @@
+---
+task: "internal-change-presentation"
+responsavel: "nancy-duarte"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Change initiative details"
+  - "Stakeholder profiles and resistance map"
+Saida:
+  - "Change management presentation with Sparkline and resistance navigation"
+Checklist:
+  - "[ ] What Is / What Could Be contrast addresses real employee concerns"
+  - "[ ] Resistance points anticipated and narratively addressed"
+  - "[ ] Call to action is specific and achievable for each audience segment"
+---
+
+# Task: Internal Change Presentation
+
+**Task ID:** NARR-032
+**Version:** 1.0.0
+**Command:** `*internal-change-presentation`
+**Agent:** Nancy Duarte (nancy-duarte)
+**Purpose:** Design presentations for internal change management using Duarte's Sparkline, helping leaders navigate resistance and inspire adoption through narrative.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `change_initiative` | What is changing (process, tool, structure, strategy) | YES |
+| `why_now` | Trigger for the change | YES |
+| `stakeholders` | Who is affected and how | YES |
+| `expected_resistance` | Anticipated objections and fears | YES |
+| `desired_outcome` | What success looks like post-change | PREFERRED |
+| `timeline` | Implementation timeline | NO |
+
+## Execution Phases
+
+### Phase 1: Map the Emotional Landscape
+
+1. Segment stakeholders by their relationship to the change:
+   - Champions (excited, early adopters)
+   - Fence-sitters (open but cautious)
+   - Resistors (fearful, skeptical, or threatened)
+2. For each segment, identify:
+   - What they stand to gain from the change
+   - What they stand to lose (real or perceived)
+   - Their biggest fear about the change
+   - What would make them advocates
+3. Design narrative paths for each segment
+4. Identify the "loss aversion" triggers — what feels like it is being taken away?
+
+### Phase 2: Design the Change Sparkline
+
+1. **What Is** — Acknowledge the current state HONESTLY (don't minimize what works)
+2. **What Could Be** — Paint the future state with specificity (not vague "better")
+3. **What Is (the cost)** — What happens if nothing changes (external threats, inefficiency)
+4. **What Could Be (the gain)** — Specific benefits for employees, not just the organization
+5. **What Is (the fear)** — Name the resistance openly: "I know some of you are thinking..."
+6. **What Could Be (the support)** — Concrete support: training, timeline, resources
+7. **Call to Adventure** — The specific ask: what each person can do THIS WEEK
+8. **New Bliss** — The organization 6-12 months from now, told through an employee story
+
+### Phase 3: Address Resistance Narratively
+
+1. Name the resistance before the audience does — this disarms it
+2. Use "I know... and..." framing:
+   - "I know this feels like more work. And it will be, for the first 30 days. After that..."
+3. Tell a story of someone who resisted similar change and came to embrace it
+4. Acknowledge what is being lost — grief is real even in organizational change
+5. Provide the "safety net" narrative — what happens if the change is harder than expected
+6. Design the "permission to struggle" moment — normalize difficulty during transition
+
+### Phase 4: Structure the Presentation
+
+1. **Opening** — Start with a shared experience that everyone relates to
+2. **The Burning Platform** — Why change is necessary (external or internal pressure)
+3. **The Vision** — What the changed world looks like (specific, not abstract)
+4. **The Resistance Moment** — "Here's what I'm hearing from many of you..."
+5. **The Bridge** — How we get from here to there (plan, resources, support)
+6. **The First Step** — One specific, achievable action everyone can take immediately
+7. **The New Bliss** — Close with the story of what we will become
+
+### Phase 5: Design Cascade Communications
+
+1. Adapt the core presentation for different audiences:
+   - Executive team: Focus on strategy and metrics
+   - Middle management: Focus on their role as change agents
+   - Front-line employees: Focus on daily impact and support
+2. Create the "manager toolkit" — talking points for team-level conversations
+3. Design the FAQ narrative — answers framed as stories, not corporate speak
+4. Plan the follow-up communications cadence (updates that sustain the narrative)
+5. Design the "quick win" announcement template for early successes
+
+## Output Format
+
+```yaml
+change_presentation:
+  initiative: "{what is changing}"
+  why_now: "{trigger}"
+  sparkline:
+    - moment: "What Is — Current State"
+      content: "{honest acknowledgment}"
+      emotional_tone: "{shared recognition}"
+    - moment: "What Could Be — Vision"
+      content: "{specific future state}"
+      emotional_tone: "{hope, possibility}"
+    - moment: "What Is — Cost of Inaction"
+      content: "{what happens if we don't change}"
+      emotional_tone: "{urgency}"
+    - moment: "What Could Be — Personal Benefit"
+      content: "{what employees gain}"
+      emotional_tone: "{desire}"
+    - moment: "Resistance Acknowledged"
+      content: "{named fears and responses}"
+      emotional_tone: "{empathy, safety}"
+    - moment: "The Bridge"
+      content: "{plan and support}"
+      emotional_tone: "{confidence}"
+    - moment: "First Step"
+      content: "{immediate action}"
+      emotional_tone: "{empowerment}"
+    - moment: "New Bliss"
+      content: "{transformed organization story}"
+      emotional_tone: "{inspiration}"
+  resistance_strategy:
+    - segment: "{stakeholder group}"
+      fear: "{what they worry about}"
+      narrative_response: "{how to address it}"
+  cascade:
+    executive: "{adapted message}"
+    management: "{adapted message}"
+    frontline: "{adapted message}"
+  manager_toolkit: ["{talking points}"]
+  follow_up_cadence: ["{communication schedule}"]
+```
+
+## Veto Conditions
+
+- **NEVER** pretend the change is easy — people see through false optimism
+- **NEVER** ignore resistance — unaddressed fears become underground sabotage
+- **NEVER** make the presentation about the company's needs — frame it as employee benefit
+- **NEVER** skip the first step — people need something concrete they can do NOW
+- **NEVER** use corporate jargon — "synergies" and "alignment" create distance, not buy-in
+
+## Completion Criteria
+
+- [ ] Sparkline designed with honest What Is / aspirational What Could Be
+- [ ] Resistance mapped by stakeholder segment and narratively addressed
+- [ ] Presentation includes specific, achievable first step
+- [ ] Cascade communications adapted for each audience level
+- [ ] Manager toolkit created for team-level conversations
+- [ ] Follow-up communication cadence planned

package/squads/squad-storytelling/tasks/investor-pitch-deck.md

@@ -0,0 +1,137 @@
+---
+task: "investor-pitch-deck"
+responsavel: "oren-klaff"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Company/startup details and financials"
+  - "Funding round and amount sought"
+Saida:
+  - "Complete investor pitch deck narrative using Pitch Anything framework"
+Checklist:
+  - "[ ] STRONG method applied to full deck structure"
+  - "[ ] Frame control strategy designed for investor dynamics"
+  - "[ ] Croc brain optimizations applied to every slide"
+---
+
+# Task: Build Investor Pitch Deck
+
+**Task ID:** NARR-027
+**Version:** 1.0.0
+**Command:** `*investor-pitch-deck`
+**Agent:** Oren Klaff (oren-klaff)
+**Purpose:** Build an investor pitch deck narrative using the Pitch Anything framework, with frame control, STRONG method, and croc brain optimization.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `company` | Name, stage, industry, mission | YES |
+| `problem_solution` | Problem being solved and how | YES |
+| `traction` | Key metrics, revenue, users, growth rate | YES |
+| `funding_ask` | Amount, round type, use of funds | YES |
+| `team` | Founders and key team backgrounds | YES |
+| `market_size` | TAM, SAM, SOM | PREFERRED |
+| `competitive_landscape` | Key competitors and differentiation | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Analyze Investor Psychology
+
+1. Profile the target investor type (angel, VC, PE, strategic)
+2. Identify their decision framework — what pattern do they look for?
+3. Map their default frames: Analyst frame, Power frame, Time frame
+4. Identify beta traps in typical pitch meetings (waiting, interruptions, phone checks)
+5. Determine status dynamics — how to establish peer-level status immediately
+
+### Phase 2: Design Frame Strategy
+
+1. **Prize Frame** — Position the deal as scarce; investors compete for allocation
+2. **Time Frame** — Create urgency without desperation (round timeline, competing interest)
+3. **Authority Frame** — Establish domain expertise that investors cannot match
+4. **Intrigue Frame** — Lead with a mystery or counterintuitive insight about the market
+5. Design frame stacking order for maximum impact
+6. Plan frame collision responses for when investors push back
+
+### Phase 3: Build STRONG Deck Structure
+
+1. **Set the Frame (Slides 1-2)** — Bold opening statement that reframes the market; NOT "Hi, I'm..."
+2. **Tell the Story (Slides 3-5)** — Problem → failed solutions → insight that changes everything
+3. **Reveal the Intrigue (Slide 6)** — The unique insight, technology, or approach nobody else has
+4. **Offer the Prize (Slides 7-9)** — Traction, team, and market as proof the prize is real
+5. **Nail the Hookpoint (Slide 10)** — The moment they lean in; usually a traction or vision slide
+6. **Get the Deal (Slides 11-12)** — Clear ask, use of funds, terms, and immediate next step
+
+### Phase 4: Optimize Each Slide for Croc Brain
+
+For each slide:
+1. One idea per slide — croc brain cannot process complexity
+2. High contrast visuals — before/after, with/without
+3. Novelty element — something they have never seen in a pitch before
+4. Tension maintenance — each slide opens a loop the next slide closes
+5. Remove all jargon — if it requires explanation, simplify it
+6. Design the "look away" test — can someone glance at the slide and get the point?
+
+### Phase 5: Design the Ask and Objection Handling
+
+1. State the ask in one clear sentence (amount, valuation, terms)
+2. Present use of funds as a narrative: "With this capital, we will..."
+3. Prepare responses for top 7 investor objections using frame control
+4. Design the "walk-away" moment — willingness to leave maintains prize frame
+5. Create the post-meeting follow-up narrative (not a thank-you, a momentum piece)
+6. Plan the "information drip" — what to withhold for follow-up meetings
+
+## Output Format
+
+```yaml
+investor_pitch_deck:
+  company: "{name}"
+  round: "{type and amount}"
+  frame_strategy:
+    primary: "{Prize/Time/Authority/Intrigue}"
+    stack_order: ["{frame sequence}"]
+    collision_responses: ["{counter-frame techniques}"]
+  deck_structure:
+    - slide: 1
+      strong_phase: "Set the Frame"
+      headline: "{bold opening}"
+      content: "{key point}"
+      croc_optimization: "{simplicity/novelty/contrast}"
+      tension_loop: "{what question this opens}"
+    # ... all slides
+  the_ask:
+    amount: ""
+    valuation: ""
+    use_of_funds: "{narrative format}"
+    terms: ""
+  objection_handling:
+    - objection: "{concern}"
+      frame: "{which frame to use}"
+      response: "{specific response}"
+  post_meeting:
+    follow_up: "{momentum piece, not thank-you}"
+    information_drip: "{what to reveal in meeting 2}"
+  status_plays:
+    opening: "{how to establish status in first 30 seconds}"
+    beta_trap_avoidance: ["{specific counter-moves}"]
+```
+
+## Veto Conditions
+
+- **NEVER** open with "Hi, I'm X and we do Y" — Set the Frame first
+- **NEVER** present more than one idea per slide
+- **NEVER** chase after the meeting — maintain prize frame in all follow-ups
+- **NEVER** reveal everything — information scarcity maintains intrigue
+- **NEVER** let the investor control the frame — always have a counter-frame ready
+
+## Completion Criteria
+
+- [ ] Frame strategy designed with collision responses
+- [ ] STRONG method applied to complete deck structure
+- [ ] Every slide optimized for croc brain (simplicity, novelty, contrast)
+- [ ] Ask is clear, specific, and narratively framed
+- [ ] Top 7 objections handled with frame control
+- [ ] Post-meeting follow-up strategy designed

package/squads/squad-storytelling/tasks/keynote-presentation-design.md

@@ -0,0 +1,152 @@
+---
+task: "keynote-presentation-design"
+responsavel: "nancy-duarte"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Keynote topic and core message"
+  - "Audience profile and event context"
+Saida:
+  - "Complete keynote presentation designed with Sparkline and STAR moments"
+Checklist:
+  - "[ ] Sparkline structure oscillates between What Is and What Could Be"
+  - "[ ] STAR moment designed for peak memorability"
+  - "[ ] Audience positioned as hero of the transformation"
+---
+
+# Task: Design Keynote Presentation
+
+**Task ID:** NARR-030
+**Version:** 1.0.0
+**Command:** `*keynote-presentation-design`
+**Agent:** Nancy Duarte (nancy-duarte)
+**Purpose:** Design a keynote presentation using Duarte's Sparkline structure, STAR moment methodology, and audience-as-hero philosophy from Resonate.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `topic` | Keynote subject matter | YES |
+| `core_message` | The single idea the audience must remember | YES |
+| `audience` | Who they are, what they know, what they care about | YES |
+| `event_context` | Conference, company meeting, TED-style, workshop | YES |
+| `duration` | Time allotted for the keynote | YES |
+| `speaker_profile` | Speaker's credibility and relationship to topic | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Audience Analysis (The Hero)
+
+1. Profile the audience — demographics, knowledge level, emotional state arriving
+2. Identify their "What Is" — current reality, beliefs, and frustrations
+3. Define their "What Could Be" — the aspirational state the keynote will paint
+4. Map the gap between What Is and What Could Be — this gap IS the keynote
+5. Identify the audience's resistance: What will they push back on? What do they fear?
+6. Determine the "gift" — what does the audience receive by the end?
+
+### Phase 2: Design the Sparkline
+
+1. **Opening: What Is** — Start in the audience's current reality (shared experience)
+2. **First Contrast: What Could Be** — Paint the first glimpse of the better world
+3. **What Is (deepened)** — Why the current state persists; what holds us back
+4. **What Could Be (expanded)** — More evidence, stories, data for the better world
+5. Continue alternating — each cycle deepens the contrast and raises stakes
+6. **Call to Adventure** — The pivot where What Could Be becomes achievable
+7. **New Bliss** — Close with the transformed world; the audience's future if they act
+8. Design 5-7 oscillation points for a 20-minute keynote (adjust by duration)
+
+### Phase 3: Design the STAR Moment
+
+1. The STAR moment (Something They'll Always Remember) is the peak of the keynote
+2. Choose the STAR type:
+   - **Memorable Dramatization** — Live demo, physical prop, unexpected visual
+   - **Repeatable Sound Bite** — A phrase so good the audience will quote it
+   - **Evocative Visual** — A single image that captures the entire message
+   - **Emotive Storytelling** — A personal or human story that creates catharsis
+   - **Shocking Statistic** — A number presented in a way that rewires understanding
+3. Place the STAR moment at approximately 2/3 through the presentation
+4. Design the emotional buildup that makes the STAR moment land
+5. Design the aftermath — what follows must sustain the energy, not deflate it
+
+### Phase 4: Structure the Content
+
+1. Craft the opening — first 30 seconds must establish relevance and credibility
+2. Design 3-5 "movement" sections, each with its own What Is/What Could Be cycle
+3. For each section:
+   - Lead with a story or concrete example
+   - Introduce the concept or insight
+   - Provide evidence (data, case study, research)
+   - Return to the audience: "This means for you..."
+4. Design transitions between sections (callbacks, questions, visual shifts)
+5. Craft the closing — end with the New Bliss and a clear call to action
+
+### Phase 5: Slide Design Principles
+
+1. One idea per slide — if the slide needs a second sentence, split it
+2. Design for glanceability — audience should get the point in 3 seconds
+3. Use full-bleed images for emotional slides, minimal text for data slides
+4. Create visual contrast between What Is (darker/muted) and What Could Be (lighter/vibrant)
+5. The STAR moment slide should break every pattern established so far
+6. Final slide should be the call to action, not "Thank you" or "Questions?"
+
+## Output Format
+
+```yaml
+keynote_presentation:
+  topic: "{subject}"
+  core_message: "{the one thing to remember}"
+  duration: "{minutes}"
+  audience:
+    profile: "{who they are}"
+    what_is: "{current reality}"
+    what_could_be: "{aspirational state}"
+    gap: "{what separates them}"
+    gift: "{what they receive}"
+  sparkline:
+    - moment: "Opening — What Is"
+      content: "{shared current reality}"
+      emotional_tone: "{feeling}"
+      duration: "{minutes}"
+    - moment: "First Contrast — What Could Be"
+      content: "{glimpse of better world}"
+      emotional_tone: "{feeling}"
+      duration: "{minutes}"
+    # ... all oscillation points
+    - moment: "New Bliss"
+      content: "{transformed future}"
+      emotional_tone: "{inspiration}"
+      duration: "{minutes}"
+  star_moment:
+    type: "{dramatization/sound_bite/visual/story/statistic}"
+    content: "{what happens}"
+    placement: "{when in the presentation}"
+    buildup: "{how to prepare the audience}"
+  sections:
+    - title: "{section name}"
+      story: "{opening story}"
+      insight: "{concept}"
+      evidence: "{proof}"
+      audience_relevance: "{why this matters to them}"
+  slide_count: 0
+  call_to_action: "{what the audience should do}"
+```
+
+## Veto Conditions
+
+- **NEVER** make the speaker the hero — the AUDIENCE is always the hero
+- **NEVER** start with "Today I'm going to talk about..." — start in the audience's world
+- **NEVER** create slides with walls of text — one idea per slide
+- **NEVER** end with "Any questions?" — end with the call to action and New Bliss
+- **NEVER** skip the STAR moment — without it, the keynote is forgettable
+
+## Completion Criteria
+
+- [ ] Sparkline designed with clear What Is / What Could Be oscillation
+- [ ] STAR moment designed and placed at optimal point
+- [ ] Audience positioned as hero throughout
+- [ ] Opening hooks audience in first 30 seconds
+- [ ] Closing delivers clear call to action
+- [ ] Slide design principles documented