sinapse-ai 1.0.0

package/squad-storytelling/tasks/case-study-beat-structure.md

@@ -0,0 +1,143 @@
+---
+task: "case-study-beat-structure"
+responsavel: "blake-snyder"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Client/customer success story details"
+  - "Key metrics and outcomes"
+Saida:
+  - "Case study structured with Save the Cat beats for maximum engagement"
+Checklist:
+  - "[ ] Case study follows dramatic structure, not just chronology"
+  - "[ ] Key beats (Catalyst, Midpoint, Finale) create emotional engagement"
+  - "[ ] Results presented as climactic payoff, not dry data"
+---
+
+# Task: Structure Case Study with Beat Sheet
+
+**Task ID:** NARR-025
+**Version:** 1.0.0
+**Command:** `*case-study-beat-structure`
+**Agent:** Blake Snyder (blake-snyder)
+**Purpose:** Transform standard case studies from boring chronologies into compelling narratives using Save the Cat beat structure.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `client_info` | Client name, industry, size | YES |
+| `challenge` | The problem they faced | YES |
+| `solution` | What was implemented | YES |
+| `results` | Metrics, outcomes, testimonials | YES |
+| `timeline` | How long the engagement lasted | PREFERRED |
+| `format` | Long-form, one-pager, video, slide deck | NO (default: long-form) |
+
+## Execution Phases
+
+### Phase 1: Identify the Story Genre
+
+1. Classify the case study using Snyder's 10 genres:
+   - Monster in the House (fighting a threat)
+   - Golden Fleece (quest for a goal)
+   - Out of the Bottle (unexpected transformation)
+   - Dude with a Problem (ordinary person, extraordinary situation)
+   - Rites of Passage (life transition)
+   - Buddy Love (partnership story)
+   - Whydunit (mystery/investigation)
+   - Fool Triumphant (underdog victory)
+   - Institutionalized (group vs system)
+   - Superhero (extraordinary person, ordinary world)
+2. Select the genre that best fits the client's story
+3. This genre determines tone, pacing, and emphasis
+
+### Phase 2: Map Client Story to 15 Beats
+
+1. **Opening Image** — Client's world before the problem peaked (the "normal" that wasn't working)
+2. **Theme Stated** — The core insight the case study will prove
+3. **Set-Up** — Client background, industry context, stakes involved
+4. **Catalyst** — The moment the problem became urgent (what triggered action?)
+5. **Debate** — The client's hesitation, alternatives considered, internal debate
+6. **Break into Two** — The decision to engage your solution
+7. **B Story** — The human element: the champion inside the client org, the relationship
+8. **Fun and Games** — Implementation highlights, the "promise" of the solution in action
+9. **Midpoint** — Early wins OR unexpected complication (raises stakes either way)
+10. **Bad Guys Close In** — Obstacles during implementation, things that almost derailed it
+11. **All Is Lost** — The lowest point or biggest risk moment
+12. **Dark Night** — The moment of doubt before breakthrough
+13. **Break into Three** — The insight or pivot that made everything work
+14. **Finale** — Results delivered, transformation complete
+15. **Final Image** — Client's world now — contrasted with Opening Image
+
+### Phase 3: Enhance Emotional Beats
+
+1. Add a specific human quote or moment to Catalyst, Midpoint, and Finale
+2. Design the "All Is Lost" moment for maximum tension (even if brief in reality)
+3. Ensure the Finale SHOWS results, not just tells (data + human impact)
+4. Create the contrast between Opening Image and Final Image as a single visual
+5. Add the B Story human element — the person behind the numbers
+
+### Phase 4: Write the Case Study
+
+1. Open with the Opening Image — drop the reader into the client's world
+2. Build through beats naturally — never reveal the ending early
+3. Make the Debate real — show why choosing your solution was not obvious
+4. Let Fun and Games deliver the core value proposition through story
+5. End with the Final Image — the transformed reality, backed by data
+
+### Phase 5: Create Format Variations
+
+1. **Long-form** (1500-2500 words) — Full beat sheet with all 15 beats
+2. **One-pager** (300-500 words) — Catalyst, Fun and Games, Finale only
+3. **Slide deck** (8-12 slides) — One beat per slide, visual-first
+4. **Social proof snippet** (50-100 words) — Opening Image → Final Image contrast
+5. **Video script** (if applicable) — Beats timed to runtime
+
+## Output Format
+
+```yaml
+case_study:
+  client: "{name/anonymized}"
+  genre: "{snyder genre}"
+  theme_stated: "{core insight}"
+  beat_sheet:
+    opening_image: "{before state}"
+    catalyst: "{trigger moment}"
+    debate: "{hesitation and alternatives}"
+    break_into_two: "{decision to engage}"
+    b_story: "{human champion}"
+    fun_and_games: "{solution in action}"
+    midpoint: "{early win or complication}"
+    bad_guys: "{implementation obstacles}"
+    all_is_lost: "{lowest moment}"
+    break_into_three: "{breakthrough insight}"
+    finale: "{results and transformation}"
+    final_image: "{after state}"
+  results_highlight:
+    metrics: ["{key numbers}"]
+    testimonial: "{client quote}"
+    before_after: "{contrast summary}"
+  format_versions:
+    long_form: "{word count and outline}"
+    one_pager: "{condensed version}"
+    social_snippet: "{50-100 word version}"
+```
+
+## Veto Conditions
+
+- **NEVER** lead with results — the payoff must be earned through story
+- **NEVER** skip the Debate — showing alternatives considered adds credibility
+- **NEVER** omit the obstacles — case studies without struggle are unbelievable
+- **NEVER** write a chronological timeline and call it a case study — it must be a STORY
+
+## Completion Criteria
+
+- [ ] Case study genre identified and applied
+- [ ] All applicable beats mapped to client story
+- [ ] Emotional beats enhanced with human quotes and moments
+- [ ] Opening Image/Final Image contrast is vivid and compelling
+- [ ] Multiple format variations created
+- [ ] Results presented as narrative payoff, not data dump

package/squad-storytelling/tasks/close-story-gap.md

@@ -0,0 +1,71 @@
+---
+task: "close-story-gap"
+responsavel: "kindra-hall"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Current business communication or marketing"
+Saida:
+  - "Story Gap diagnosis with bridge stories"
+Checklist:
+  - "[ ] Current story identified (what is being told)"
+  - "[ ] Desired story identified (what should be told)"
+  - "[ ] Gap measured and bridge story crafted"
+---
+
+# Task: Close the Story Gap
+
+**Task ID:** NARR-014
+**Version:** 1.0.0
+**Command:** `*close-story-gap`
+**Agent:** Kindra Hall (kindra-hall)
+**Purpose:** Diagnose the Story Gap in business communication and craft bridge stories to close it.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `current_communication` | Website copy, sales scripts, presentations | YES |
+| `target_audience` | Who you're trying to reach | YES |
+| `business_goals` | What outcomes you want | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Diagnose Current Story
+
+1. What story are customers telling themselves about you RIGHT NOW?
+2. What story is your marketing/sales currently telling?
+3. Where are you relying on data/features instead of narrative?
+
+### Phase 2: Define Desired Story
+
+1. What story do you WANT customers to tell?
+2. What emotional response do you want to create?
+3. What action should the story drive?
+
+### Phase 3: Measure the Gap
+
+1. How far apart are the current and desired stories?
+2. What is the gap costing? (lost sales, low engagement, weak culture)
+3. Which of the 4 story types would best bridge this gap?
+
+### Phase 4: Craft Bridge Stories
+
+Create 1-3 stories specifically designed to close the gap, using Normal-Explosion-New Normal.
+
+## Veto Conditions
+
+- **NEVER** assume the business doesn't have a Story Gap
+- **NEVER** close the gap with more data — stories bridge emotional gaps
+- **NEVER** create bridge stories without specificity
+
+## Completion Criteria
+
+- [ ] Current story clearly identified
+- [ ] Desired story articulated
+- [ ] Gap measured with cost assessment
+- [ ] 1-3 bridge stories crafted with structure
+- [ ] Implementation recommendations provided

package/squad-storytelling/tasks/community-narrative-design.md

@@ -0,0 +1,138 @@
+---
+task: "community-narrative-design"
+responsavel: "dan-harmon"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Community context (brand, movement, or group)"
+  - "Community goals and values"
+Saida:
+  - "Complete community narrative framework with shared story and rituals"
+Checklist:
+  - "[ ] Community origin story crafted with Story Circle structure"
+  - "[ ] Shared narrative elements defined (language, rituals, milestones)"
+  - "[ ] Member journey mapped as recurring Story Circle"
+---
+
+# Task: Build Community Narrative
+
+**Task ID:** NARR-023
+**Version:** 1.0.0
+**Command:** `*community-narrative-design`
+**Agent:** Dan Harmon (dan-harmon)
+**Purpose:** Design the narrative architecture of a community using Story Circle, creating shared stories, rituals, and identity that bind members together.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `community_context` | Brand, movement, cause, or interest group | YES |
+| `community_values` | Core beliefs and shared principles | YES |
+| `member_profile` | Who the community members are | YES |
+| `community_goals` | What the community aims to achieve together | PREFERRED |
+| `existing_narrative` | Current community story or messaging | NO |
+
+## Execution Phases
+
+### Phase 1: Design the Community Origin Story
+
+1. Apply Story Circle to the community's founding moment:
+   - YOU: The world before this community existed
+   - NEED: What was missing? What gap or injustice sparked creation?
+   - GO: The founding act — who decided to build something different?
+   - SEARCH: Early struggles, finding members, defining identity
+   - FIND: The moment the community discovered what it truly was
+   - TAKE: The core value or insight the community now carries
+   - RETURN: How the community began changing the world around it
+   - CHANGE: What is different because this community exists?
+2. Identify the "founding myth" — the story members retell to each other
+3. Define the community's "enemy" or "antagonist" (a problem, not a person)
+
+### Phase 2: Design Shared Narrative Elements
+
+1. **Sacred language** — Terms, phrases, inside jokes that only members understand
+2. **Origin rituals** — How new members are welcomed (initiation story)
+3. **Milestone celebrations** — How achievements are narratively framed
+4. **Conflict resolution narrative** — How disagreements are understood within the story
+5. **Shared symbols** — Visual or verbal shortcuts that invoke the community story
+6. Define the community's "we believe" statement — the narrative manifesto
+
+### Phase 3: Map the Member Journey
+
+1. Design the individual member's Story Circle within the community:
+   - YOU: Life before joining
+   - NEED: What drew them to seek this community
+   - GO: First interaction, lurking, tentative engagement
+   - SEARCH: Deepening involvement, finding their place
+   - FIND: The "belonging moment" — when they feel truly part of it
+   - TAKE: What they contribute and receive
+   - RETURN: How membership changes their life outside the community
+   - CHANGE: Their identity shift — "I am a [community member]"
+2. Identify the key transition points where members might disengage
+3. Design narrative interventions for each potential drop-off point
+
+### Phase 4: Create Narrative Rituals
+
+1. **Weekly/recurring rituals** — Content, events, or practices that reinforce the story
+2. **Seasonal arcs** — Larger narrative cycles (quarterly themes, annual events)
+3. **Member spotlight format** — How individual stories are shared and celebrated
+4. **Challenge narratives** — How the community frames and overcomes obstacles together
+5. **Legacy stories** — How departing members are honored and remembered
+
+### Phase 5: Design Narrative Governance
+
+1. Define who can tell the community's story and how (brand, leaders, any member)
+2. Create story guidelines — what is on-brand and what is not
+3. Design the "story collection" process — how member stories are gathered
+4. Plan narrative evolution — how the community story grows without losing its core
+5. Define the "North Star narrative" — the story that will still be told in 10 years
+
+## Output Format
+
+```yaml
+community_narrative:
+  community: "{name}"
+  origin_story:
+    story_circle: {you, need, go, search, find, take, return, change}
+    founding_myth: "{retellable origin story}"
+    antagonist: "{the problem the community fights}"
+  shared_elements:
+    sacred_language: ["{terms and phrases}"]
+    we_believe: "{manifesto statement}"
+    symbols: ["{visual and verbal markers}"]
+  member_journey:
+    story_circle: {you, need, go, search, find, take, return, change}
+    belonging_moment: "{when they feel 'in'}"
+    identity_shift: "{who they become}"
+    drop_off_points: ["{risk moments and narrative interventions}"]
+  rituals:
+    recurring: ["{weekly/monthly practices}"]
+    seasonal_arcs: ["{quarterly/annual narrative themes}"]
+    member_spotlight: "{format for sharing individual stories}"
+    challenges: "{how obstacles are framed}"
+    legacy: "{how departures are honored}"
+  governance:
+    storytellers: "{who can tell the story}"
+    guidelines: "{what is on-brand}"
+    collection_process: "{how stories are gathered}"
+    north_star: "{the enduring story}"
+```
+
+## Veto Conditions
+
+- **NEVER** design community narrative without member input or empathy — top-down stories ring hollow
+- **NEVER** create an "us vs them" narrative that targets people — target problems
+- **NEVER** make the brand the center — the community and its members are the heroes
+- **NEVER** design static narratives — communities evolve and the story must breathe
+
+## Completion Criteria
+
+- [ ] Community origin story crafted with complete Story Circle
+- [ ] Shared narrative elements defined (language, symbols, manifesto)
+- [ ] Member journey mapped as individual Story Circle
+- [ ] Drop-off points identified with narrative interventions
+- [ ] Rituals designed for recurring engagement
+- [ ] Narrative governance established

package/squad-storytelling/tasks/content-series-story-circle.md

@@ -0,0 +1,142 @@
+---
+task: "content-series-story-circle"
+responsavel: "dan-harmon"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Content series theme or topic"
+  - "Platform and audience context"
+Saida:
+  - "Complete content series plan structured with Story Circle for each episode"
+Checklist:
+  - "[ ] Series arc mapped with overarching Story Circle"
+  - "[ ] Each episode structured with its own 8-step circle"
+  - "[ ] Fractal narrative maintains coherence across episodes"
+---
+
+# Task: Plan Content Series Using Story Circle
+
+**Task ID:** NARR-021
+**Version:** 1.0.0
+**Command:** `*content-series-story-circle`
+**Agent:** Dan Harmon (dan-harmon)
+**Purpose:** Plan a multi-episode content series using Story Circle structure, ensuring each piece works standalone while contributing to a larger narrative arc.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `series_theme` | Overarching topic or message | YES |
+| `episode_count` | Number of content pieces planned | YES |
+| `platform` | Blog, podcast, video, social, newsletter | YES |
+| `audience` | Target audience profile | YES |
+| `brand_voice` | Tone and style guidelines | PREFERRED |
+| `call_to_action` | What the series should ultimately drive | NO |
+
+## Execution Phases
+
+### Phase 1: Design the Macro Story Circle (Series Arc)
+
+1. **YOU** — Where is the audience right now? (their comfort zone, current beliefs)
+2. **NEED** — What gap or desire will the series address?
+3. **GO** — What unfamiliar territory will the series take them into?
+4. **SEARCH** — What will they explore across episodes?
+5. **FIND** — What is the central insight or revelation of the series?
+6. **TAKE** — What do they gain? (skill, perspective, tool)
+7. **RETURN** — How do they come back to their world, changed?
+8. **CHANGE** — What is different about them after consuming the series?
+
+### Phase 2: Design Episode Arcs (Micro Circles)
+
+For each episode, create an individual Story Circle:
+1. Map the episode's own YOU → CHANGE cycle
+2. Ensure each episode delivers a complete satisfying arc
+3. Identify the "hook" (first 10% of content that establishes YOU and NEED)
+4. Identify the "midpoint reversal" (FIND moment — the insight)
+5. Design the "return gift" (TAKE — actionable takeaway)
+6. Create the cliffhanger or bridge to next episode (maintaining series tension)
+
+### Phase 3: Design Fractal Coherence
+
+1. Map how each episode's micro-circle nests within the macro-circle
+2. Identify which macro-stage each episode serves (early episodes = GO/SEARCH, later = FIND/TAKE)
+3. Ensure progressive deepening — each episode builds on previous understanding
+4. Design recurring motifs or callbacks that create series cohesion
+5. Plan the "dark night" episode (the one that challenges everything established so far)
+
+### Phase 4: Create Episode Outlines
+
+For each episode, document:
+1. Title and hook (compelling reason to consume)
+2. Story Circle mapping (all 8 steps)
+3. Key content points and teaching moments
+4. Emotional journey of the episode
+5. Bridge to next episode
+6. Standalone value (what someone gets if they only see this one)
+
+### Phase 5: Design Series Mechanics
+
+1. Plan the release cadence and build anticipation mechanics
+2. Design the "previously on" recaps for continuity
+3. Create engagement prompts that invite audience into the story
+4. Plan the series finale — the ultimate CHANGE moment
+5. Design post-series content (the "encore" — what comes after transformation)
+
+## Output Format
+
+```yaml
+content_series_plan:
+  series_title: "{title}"
+  theme: "{overarching message}"
+  platform: "{where it lives}"
+  episode_count: 0
+  macro_story_circle:
+    you: "{audience starting point}"
+    need: "{gap or desire}"
+    go: "{unfamiliar territory}"
+    search: "{exploration theme}"
+    find: "{central revelation}"
+    take: "{what they gain}"
+    return: "{coming back changed}"
+    change: "{transformed state}"
+  episodes:
+    - number: 1
+      title: "{episode title}"
+      macro_stage: "{which macro step this serves}"
+      micro_circle:
+        you: "{episode starting point}"
+        need: "{episode gap}"
+        go: "{episode exploration}"
+        search: "{episode search}"
+        find: "{episode insight}"
+        take: "{episode takeaway}"
+        return: "{episode return}"
+        change: "{episode change}"
+      hook: "{opening hook}"
+      key_content: ["{main points}"]
+      emotional_journey: "{feeling progression}"
+      bridge_to_next: "{connection to next episode}"
+  fractal_map: "{how episodes nest in macro arc}"
+  recurring_motifs: ["{callbacks and patterns}"]
+  release_cadence: "{schedule}"
+  engagement_prompts: ["{audience participation hooks}"]
+```
+
+## Veto Conditions
+
+- **NEVER** create episodes that only work in sequence — each must deliver standalone value
+- **NEVER** skip the NEED step — without it, content is information, not story
+- **NEVER** front-load all insights — the FIND should land at the right moment
+- **NEVER** forget the CHANGE — every episode must leave the audience slightly different
+
+## Completion Criteria
+
+- [ ] Macro Story Circle designed for complete series arc
+- [ ] Each episode has its own micro Story Circle
+- [ ] Fractal coherence verified (episodes nest within macro arc)
+- [ ] Episode outlines include hooks, bridges, and standalone value
+- [ ] Series mechanics designed (cadence, recaps, engagement)
+- [ ] Finale delivers on the macro CHANGE promise

package/squad-storytelling/tasks/craft-logline.md

@@ -0,0 +1,74 @@
+---
+task: "craft-logline"
+responsavel: "blake-snyder"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Story concept or idea"
+Saida:
+  - "Polished logline with irony, mental picture, and primal test"
+Checklist:
+  - "[ ] Logline is one sentence with built-in irony"
+  - "[ ] Mental picture conjured — a stranger can 'see' the story"
+  - "[ ] Primal test passed"
+---
+
+# Task: Craft Logline
+
+**Task ID:** NARR-008
+**Version:** 1.0.0
+**Command:** `*craft-logline`
+**Agent:** Blake Snyder (blake-snyder)
+**Purpose:** Craft a compelling one-sentence logline that sells the story.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `story_concept` | User description | YES |
+| `genre` | If known | NO |
+| `target_audience` | Who this is for | NO |
+
+## Execution Phases
+
+### Phase 1: Extract Core Elements
+
+1. Who is the hero? (adjective + noun, not a name)
+2. What is the inciting incident? (the catalyst)
+3. What is the goal? (clear, external, visual)
+4. What is the opposition? (stakes, antagonist, obstacle)
+
+### Phase 2: Build Logline
+
+Formula: **On the verge of [status quo], a [flawed hero] must [do something difficult] when [catalyst occurs], or [consequence].**
+
+Check for:
+- **Irony:** Is there a built-in contradiction or twist?
+- **Mental picture:** Can a stranger visualize the whole story?
+- **Audience + genre:** Does it imply who watches and what genre?
+- **Killer title pairing:** Does it work with a great title?
+
+### Phase 3: Primal Test
+
+Does it connect to: survival, hunger, sex, protection of loved ones, or fear of death?
+
+### Phase 4: Iterate
+
+Generate 3-5 variations, test each against the criteria, select the strongest.
+
+## Veto Conditions
+
+- **NEVER** accept a logline that is not one sentence
+- **NEVER** accept a logline without irony
+- **NEVER** accept a logline that fails the primal test
+
+## Completion Criteria
+
+- [ ] Logline is one compelling sentence
+- [ ] Built-in irony creates emotional hook
+- [ ] Mental picture is clear and vivid
+- [ ] Primal test passed
+- [ ] Multiple variations generated and best selected

package/squad-storytelling/tasks/create-beat-sheet.md

@@ -0,0 +1,107 @@
+---
+task: "create-beat-sheet"
+responsavel: "blake-snyder"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Story concept, logline, or existing draft"
+Saida:
+  - "Complete 15-beat sheet with all beats populated"
+Checklist:
+  - "[ ] All 15 beats defined with content and page targets"
+  - "[ ] Genre type identified from the 10 genres"
+  - "[ ] Primal test passed — connects to survival drives"
+---
+
+# Task: Create Beat Sheet
+
+**Task ID:** NARR-007
+**Version:** 1.0.0
+**Command:** `*create-beat-sheet`
+**Agent:** Blake Snyder (blake-snyder)
+**Purpose:** Build a complete 15-beat Save the Cat beat sheet for any narrative.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `story_concept` | User prompt or logline | YES |
+| `genre` | User-specified or to be determined | PREFERRED |
+| `format` | Film, novel, series | NO (default: film) |
+
+## Execution Phases
+
+### Phase 1: Logline and Genre
+
+1. Craft or refine the logline (irony + mental picture + audience)
+2. Classify into one of the 10 genre types
+3. Apply the primal test — does it connect to survival drives?
+
+### Phase 2: Build 15 Beats
+
+For each beat, define: what happens, the emotional state, and how it connects to the theme.
+
+1. **Opening Image** (p.1) — The "before" snapshot
+2. **Theme Stated** (p.5) — The lesson, stated but not yet understood
+3. **Set-Up** (p.1-10) — World, flaws, relationships, stakes planted
+4. **Catalyst** (p.12) — The life-changing inciting incident
+5. **Debate** (p.12-25) — Should I? Can I? Last chance to turn back
+6. **Break into Two** (p.25) — Proactive CHOICE to enter new world
+7. **B Story** (p.30) — Love story / theme carrier
+8. **Fun and Games** (p.30-55) — The promise of the premise
+9. **Midpoint** (p.55) — False victory or false defeat; stakes raise
+10. **Bad Guys Close In** (p.55-75) — External + internal pressure
+11. **All Is Lost** (p.75) — Whiff of death; lowest point
+12. **Dark Night of the Soul** (p.75-85) — Despair before breakthrough
+13. **Break into Three** (p.85) — A + B stories cross; solution found
+14. **Finale** (p.85-110) — Execute, defeat, transform
+15. **Final Image** (p.110) — Opposite of Opening Image; proof of change
+
+### Phase 3: Verify Structure
+
+1. Does the Midpoint mirror/reverse All Is Lost?
+2. Do A and B stories cross at Break into Three?
+3. Is Fun and Games delivering the promise of the premise?
+4. Is there a clear "whiff of death" at All Is Lost?
+5. Does Final Image oppose Opening Image?
+
+## Output Format
+
+```yaml
+beat_sheet:
+  logline: "{one sentence with irony}"
+  genre: "{one of 10 types}"
+  primal_test: "{survival drive connection}"
+  beats:
+    - number: 1
+      name: "Opening Image"
+      page: "1"
+      content: "{what happens}"
+      emotional_state: "{feeling}"
+      theme_connection: "{how it relates}"
+    # ... all 15 beats
+  structural_checks:
+    midpoint_mirror: "{assessment}"
+    ab_crossover: "{assessment}"
+    promise_of_premise: "{assessment}"
+    whiff_of_death: "{assessment}"
+    transformation_proof: "{assessment}"
+```
+
+## Veto Conditions
+
+- **NEVER** skip any of the 15 beats — the system requires completeness
+- **NEVER** proceed without a logline — it is the foundation
+- **NEVER** make Break into Two an accident — it must be a hero's CHOICE
+- **NEVER** forget the whiff of death at All Is Lost
+
+## Completion Criteria
+
+- [ ] Logline crafted with irony and primal resonance
+- [ ] Genre identified from the 10 types
+- [ ] All 15 beats defined with content, emotion, and theme
+- [ ] Structural checks passed
+- [ ] Transformation visible from Opening to Final Image