sinapse-ai 1.0.0

package/squad-storytelling/tasks/brand-script-sb7.md

@@ -0,0 +1,165 @@
+---
+task: "brand-script-sb7"
+responsavel: "park-howell"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Brand/business details"
+  - "Customer profile and pain points"
+Saida:
+  - "Complete StoryBrand BrandScript with all 7 elements"
+Checklist:
+  - "[ ] All 7 SB7 elements completed (Character through Success)"
+  - "[ ] Customer positioned as character, brand as guide"
+  - "[ ] One-liner created from BrandScript"
+---
+
+# Task: Complete StoryBrand BrandScript
+
+**Task ID:** NARR-038
+**Version:** 1.0.0
+**Command:** `*brand-script-sb7`
+**Agent:** Park Howell (park-howell)
+**Purpose:** Build a complete StoryBrand BrandScript using the SB7 framework, clarifying brand messaging so customers listen and engage.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `brand` | Company, product, or service | YES |
+| `customer` | Who they serve — detailed profile | YES |
+| `problem` | What the customer struggles with | YES |
+| `solution` | What the brand offers | YES |
+| `current_messaging` | Existing website copy, taglines | PREFERRED |
+| `competitors` | Competitive landscape | NO |
+
+## Execution Phases
+
+### Phase 1: Define the Character (Customer as Hero)
+
+1. Who is the character in your brand's story? (Always the customer, never the brand)
+2. What does the character WANT as it relates to your brand?
+3. Express the want in a single, clear sentence
+4. Ensure the want is specific and measurable (not vague like "success")
+5. Test: If a customer read this, would they immediately nod?
+
+### Phase 2: Define the Problem (Three Levels)
+
+1. **External Problem** — The tangible, surface-level problem (what they're googling)
+2. **Internal Problem** — How the external problem makes them FEEL (frustrated, overwhelmed, embarrassed)
+3. **Philosophical Problem** — Why this situation is just plain WRONG ("Customers shouldn't have to...")
+4. Name the Villain — What is the root cause personified? (not a person, but a force: complexity, inefficiency, misinformation)
+5. Test: Does the internal problem create an emotional response?
+
+### Phase 3: Position the Guide (Brand as Mentor)
+
+1. Express **Empathy** — "We understand what it's like to..."
+2. Express **Authority** — Credentials, results, testimonials that prove competence
+3. Balance empathy and authority — too much empathy = weak; too much authority = arrogant
+4. Write the empathetic statement (1-2 sentences)
+5. List 3 authority proof points (logos, numbers, testimonials)
+
+### Phase 4: Give Them a Plan
+
+1. Create the **Process Plan** — 3 simple steps that remove confusion:
+   - Step 1: "{Easy first action}"
+   - Step 2: "{What happens next}"
+   - Step 3: "{The outcome they receive}"
+2. Create the **Agreement Plan** — Promises that reduce fear of doing business with you
+3. Name each step with action verbs (not nouns)
+4. Test: Do the 3 steps make the purchase feel simple and risk-free?
+
+### Phase 5: Define the Stakes
+
+1. **Failure** — What happens if they DON'T take action? Paint the negative consequences:
+   - What gets worse?
+   - What do they continue to suffer?
+   - What opportunity do they miss?
+2. **Success** — What does life look like AFTER they engage your brand?
+   - How do they feel?
+   - What can they do?
+   - How has their status changed?
+3. Make failure visceral and success aspirational
+4. Ensure success maps directly to the character's want from Phase 1
+
+### Phase 6: Create the Call to Action
+
+1. **Direct CTA** — The primary action (Buy Now, Schedule a Call, Start Free Trial)
+2. **Transitional CTA** — The lower-commitment option (Download Guide, Watch Demo, Take Quiz)
+3. Ensure the Direct CTA is bold, clear, and repeated throughout messaging
+4. Transitional CTA should provide value and advance the relationship
+5. Write button text for both CTAs
+
+### Phase 7: Build the One-Liner and Messaging Guide
+
+1. Create the BrandScript One-Liner:
+   - Problem: "{The problem}"
+   - Solution: "{Your unique solution}"
+   - Result: "{The successful outcome}"
+   - Format: "We help [character] who [problem] by [solution] so they can [result]"
+2. Create the elevator pitch version (30 seconds)
+3. Map BrandScript to website wireframe:
+   - Header: Character want + CTA
+   - Stakes: Problem + failure
+   - Value prop: Guide + plan
+   - Social proof: Authority
+   - Bottom CTA: Success vision + CTA
+
+## Output Format
+
+```yaml
+brandscript:
+  character:
+    who: "{customer}"
+    want: "{specific desire}"
+  problem:
+    villain: "{root cause force}"
+    external: "{tangible problem}"
+    internal: "{how it feels}"
+    philosophical: "{why it's wrong}"
+  guide:
+    empathy: "{empathetic statement}"
+    authority: ["{proof points}"]
+  plan:
+    process:
+      - step: 1
+        action: "{what to do}"
+      - step: 2
+        action: "{what happens}"
+      - step: 3
+        action: "{outcome received}"
+    agreement: ["{promises}"]
+  call_to_action:
+    direct: "{primary CTA}"
+    transitional: "{secondary CTA}"
+  failure: ["{negative consequences}"]
+  success: ["{positive outcomes}"]
+  one_liner: "{problem + solution + result}"
+  elevator_pitch: "{30-second version}"
+  website_wireframe:
+    header: "{want + CTA}"
+    stakes_section: "{problem + failure}"
+    value_section: "{guide + plan}"
+    proof_section: "{authority}"
+    closing_section: "{success + CTA}"
+```
+
+## Veto Conditions
+
+- **NEVER** make the brand the hero — the brand is ALWAYS the guide
+- **NEVER** skip the internal problem — external problems alone don't create urgency
+- **NEVER** create a plan with more than 4 steps — simplicity is the point
+- **NEVER** write a CTA that is vague — "Learn More" is not a call to action
+
+## Completion Criteria
+
+- [ ] All 7 SB7 elements completed with specificity
+- [ ] Three problem levels defined (external, internal, philosophical)
+- [ ] Guide positioned with balanced empathy and authority
+- [ ] Plan reduces complexity to 3 clear steps
+- [ ] Failure and success stakes clearly articulated
+- [ ] One-liner and elevator pitch created
+- [ ] Website wireframe mapped from BrandScript

package/squad-storytelling/tasks/brand-storytelling-strategy.md

@@ -0,0 +1,148 @@
+---
+task: "brand-storytelling-strategy"
+responsavel: "kindra-hall"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Brand context, values, and positioning"
+  - "Target audience profiles"
+Saida:
+  - "Complete brand storytelling strategy with 4 story types and Story Gap analysis"
+Checklist:
+  - "[ ] All 4 story types (Value, Founder, Purpose, Customer) developed"
+  - "[ ] Story Gap identified and bridge narrative designed"
+  - "[ ] Story bank created with 10+ ready-to-deploy stories"
+---
+
+# Task: Brand Storytelling Strategy
+
+**Task ID:** NARR-034
+**Version:** 1.0.0
+**Command:** `*brand-storytelling-strategy`
+**Agent:** Kindra Hall (kindra-hall)
+**Purpose:** Build a complete brand storytelling strategy using Hall's four story types and Story Gap methodology from Stories That Stick.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `brand_context` | Company, products, mission, values | YES |
+| `audience` | Primary and secondary audience profiles | YES |
+| `current_messaging` | Existing marketing copy and narratives | PREFERRED |
+| `business_goals` | What storytelling should achieve (awareness, trust, conversion) | PREFERRED |
+| `competitors` | How competitors tell their stories | NO |
+
+## Execution Phases
+
+### Phase 1: Diagnose the Story Gap
+
+1. Identify the gap between what the brand BELIEVES about itself and what the AUDIENCE perceives
+2. Map the "story gap" — the space where the brand's message is not landing
+3. Assess current messaging: Is it telling stories or just stating facts?
+4. Identify where stories are missing in the customer journey (awareness, consideration, decision, retention)
+5. Determine the emotional connection deficit — what feelings are absent?
+6. Define what "bridging the gap" looks like — the measurable outcome
+
+### Phase 2: Develop the Value Story
+
+1. The Value Story answers: "What's in it for me?" (the customer's question)
+2. Identify the core value the product/service delivers — not features, but transformation
+3. Structure: Normal → Explosion (problem) → New Normal (with your product)
+4. Create 3 Value Stories from different angles:
+   - Functional value (saves time, money, effort)
+   - Emotional value (reduces anxiety, increases confidence)
+   - Social value (improves status, belonging, identity)
+5. Test each story: Does it make the audience say "I want that"?
+
+### Phase 3: Develop the Founder Story
+
+1. The Founder Story answers: "Why should I trust you?"
+2. Find the founder's defining moment — when they became the person who HAD to create this
+3. Structure: Normal (before the insight) → Explosion (the catalytic moment) → New Normal (the company born)
+4. Ensure vulnerability is present — perfection kills trust
+5. Connect the founder's "why" to the customer's "why"
+
+### Phase 4: Develop the Purpose Story
+
+1. The Purpose Story answers: "Why does this company exist beyond profit?"
+2. Identify the bigger mission — what change does the brand want to create in the world?
+3. Structure: Normal (the world's problem) → Explosion (why this matters now) → New Normal (the world with your mission fulfilled)
+4. Connect purpose to daily actions — not just a mission statement but a lived narrative
+5. Find examples of the purpose in action (community impact, team decisions, product choices)
+
+### Phase 5: Develop the Customer Story
+
+1. The Customer Story answers: "Can this work for someone like me?"
+2. Collect and structure real customer narratives using:
+   - Normal: Life before discovering the product
+   - Explosion: The problem that drove them to search
+   - New Normal: Life after using the product
+3. Create 5 Customer Stories spanning different personas and use cases
+4. Ensure diversity of contexts — different industries, sizes, challenges
+5. Make the customer the hero — the brand is the tool, not the protagonist
+
+### Phase 6: Build the Story Bank
+
+1. Compile all stories into a categorized story bank
+2. Tag each story by: type, audience, funnel stage, channel, emotional tone
+3. Create "story starters" — prompts for gathering more stories from team and customers
+4. Design the story collection process — ongoing, not one-time
+5. Create deployment guidelines: which story type works best where
+
+## Output Format
+
+```yaml
+brand_storytelling_strategy:
+  story_gap:
+    brand_belief: "{what the brand thinks about itself}"
+    audience_perception: "{what the audience actually thinks}"
+    gap: "{the disconnect}"
+    bridge: "{how storytelling closes the gap}"
+  value_stories:
+    - angle: "{functional/emotional/social}"
+      normal: "{before state}"
+      explosion: "{problem}"
+      new_normal: "{transformation with product}"
+  founder_story:
+    defining_moment: "{catalytic event}"
+    vulnerability: "{honest struggle}"
+    connection_to_customer: "{shared why}"
+    narrative: "{the story}"
+  purpose_story:
+    mission: "{bigger change}"
+    narrative: "{the story}"
+    purpose_in_action: ["{concrete examples}"]
+  customer_stories:
+    - persona: "{who}"
+      normal: "{before}"
+      explosion: "{problem}"
+      new_normal: "{after}"
+  story_bank:
+    total_stories: 0
+    by_type: {value: 0, founder: 0, purpose: 0, customer: 0}
+    deployment_guide:
+      awareness: ["{which stories}"]
+      consideration: ["{which stories}"]
+      decision: ["{which stories}"]
+      retention: ["{which stories}"]
+  collection_process: "{how to gather ongoing stories}"
+```
+
+## Veto Conditions
+
+- **NEVER** create stories without the Normal → Explosion → New Normal structure
+- **NEVER** skip vulnerability in the Founder Story — polish kills authenticity
+- **NEVER** make the brand the hero in Customer Stories — the customer is always the hero
+- **NEVER** treat the story bank as a one-time project — it must be a living system
+
+## Completion Criteria
+
+- [ ] Story Gap diagnosed with clear bridge narrative
+- [ ] All 4 story types developed with multiple variations
+- [ ] Story bank created with 10+ stories tagged and categorized
+- [ ] Deployment guide maps stories to funnel stages and channels
+- [ ] Story collection process designed for ongoing gathering
+- [ ] Each story tested for emotional resonance and audience relevance

package/squad-storytelling/tasks/build-brand-narrative.md

@@ -0,0 +1,125 @@
+---
+task: "build-brand-narrative"
+responsavel: "park-howell"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Brand/business context"
+  - "Target customer profile"
+Saida:
+  - "Complete brand narrative with ABT and Story Cycle"
+Checklist:
+  - "[ ] Brand ABT defined (And, But, Therefore)"
+  - "[ ] Story Cycle mapped (10 steps with customer as hero)"
+  - "[ ] 5 Primal Elements verified"
+---
+
+# Task: Build Brand Narrative
+
+**Task ID:** NARR-015
+**Version:** 1.0.0
+**Command:** `*build-brand-narrative`
+**Agent:** Park Howell (park-howell)
+**Purpose:** Build a complete brand storytelling strategy using ABT and Story Cycle System.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `brand_context` | Company, product, mission, values | YES |
+| `target_customer` | Customer profile, pain points | YES |
+| `competitors` | Competitive landscape | PREFERRED |
+| `existing_messaging` | Current marketing copy | NO |
+
+## Execution Phases
+
+### Phase 1: Diagnose Current Communication
+
+1. Is current messaging ABT or AAA?
+2. Identify the "BUT" — where is the conflict/tension?
+3. If AAA (And, And, And), note the narrative void
+
+### Phase 2: Craft Brand ABT
+
+**And:** {Context — the world your customer lives in, the status quo}
+**But:** {Conflict — the problem, pain, obstacle, tension}
+**Therefore:** {Resolution — how your brand resolves it, the transformation}
+
+Test: Does this ABT make someone want to hear more?
+
+### Phase 3: Build Story Cycle (10 Steps)
+
+Map the customer's journey through all 10 steps:
+1. Backstory — customer's world and history
+2. Desire — what the customer wants
+3. Resistance — obstacles in their way
+4. Adventure — committing to seek a solution
+5. Allies & Enemies — brand as guide, competitors as antagonist
+6. Trial — the critical decision point
+7. Death — old way of doing things must end
+8. Rebirth — customer emerges transformed
+9. Return — back to their world, but changed
+10. Encore — advocacy, referrals, word of mouth
+
+### Phase 4: Verify 5 Primal Elements
+
+- Hero (customer) identified?
+- Desire (job to be done) clear?
+- Obstacle (conflict) compelling?
+- Mentor (brand as guide) positioned correctly?
+- Moral (transformation) evident?
+
+### Phase 5: Application Map
+
+Map the narrative to: website, pitch deck, social media, email sequences, sales scripts.
+
+## Output Format
+
+```yaml
+brand_narrative:
+  brand_abt:
+    and: "{context/status quo}"
+    but: "{conflict/tension}"
+    therefore: "{resolution/transformation}"
+  story_cycle:
+    backstory: "{customer world}"
+    desire: "{customer want}"
+    resistance: "{obstacles}"
+    adventure: "{commitment}"
+    allies_enemies: "{brand as guide}"
+    trial: "{critical decision}"
+    death: "{old way dies}"
+    rebirth: "{transformation}"
+    return: "{changed world}"
+    encore: "{advocacy}"
+  primal_elements:
+    hero: "{customer}"
+    desire: "{job to be done}"
+    obstacle: "{conflict}"
+    mentor: "{brand}"
+    moral: "{transformation}"
+  application_map:
+    website: "{how to apply}"
+    pitch_deck: "{how to apply}"
+    social_media: "{how to apply}"
+    email: "{how to apply}"
+    sales: "{how to apply}"
+```
+
+## Veto Conditions
+
+- **NEVER** make the brand the hero — the customer is ALWAYS the hero
+- **NEVER** accept AAA communication as final — convert to ABT
+- **NEVER** skip the "BUT" — without conflict there is no story
+- **NEVER** create a Story Cycle without a clear death/rebirth moment
+
+## Completion Criteria
+
+- [ ] Brand ABT defined and tested
+- [ ] Story Cycle completed with all 10 steps
+- [ ] 5 Primal Elements verified
+- [ ] Application map created for key channels
+- [ ] Customer is positioned as hero throughout

package/squad-storytelling/tasks/build-business-stories.md

@@ -0,0 +1,120 @@
+---
+task: "build-business-stories"
+responsavel: "kindra-hall"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Business context (company, product, audience)"
+Saida:
+  - "Complete set of 4 business stories (Value, Founder, Purpose, Customer)"
+Checklist:
+  - "[ ] All 4 story types drafted with specific details"
+  - "[ ] Each story follows Normal-Explosion-New Normal structure"
+  - "[ ] Stories are 60-90 seconds when spoken aloud"
+---
+
+# Task: Build Business Stories
+
+**Task ID:** NARR-013
+**Version:** 1.0.0
+**Command:** `*build-business-stories`
+**Agent:** Kindra Hall (kindra-hall)
+**Purpose:** Build the 4 essential business stories every company needs.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `business_context` | Company, product, mission | YES |
+| `target_audiences` | Sales, marketing, leadership, HR | PREFERRED |
+| `existing_stories` | Any stories currently in use | NO |
+| `founder_background` | Founder's personal history | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Story Audit
+
+1. Identify which of the 4 stories currently exist (even informally)
+2. Assess quality: specific or generic? Structured or rambling?
+3. Identify the biggest Story Gap — which missing story is costing the most?
+
+### Phase 2: Build Each Story
+
+For each story type, apply Normal-Explosion-New Normal:
+
+**Value Story** (for sales):
+- Normal: A real person with a real problem
+- Explosion: The struggle, the pain point intensified
+- New Normal: The solution (your product) transformed their reality
+
+**Founder Story** (for trust):
+- Normal: The founder's world before the insight
+- Explosion: The specific moment of realization
+- New Normal: The commitment born from that moment
+
+**Purpose Story** (for culture):
+- Normal: A customer/user before your company existed in their life
+- Explosion: The moment your company's work made tangible human difference
+- New Normal: The lasting impact, the reason the work matters
+
+**Customer Story** (for social proof):
+- Normal: The customer's world with the problem (before)
+- Explosion: Discovering and choosing the solution (during)
+- New Normal: The transformed reality (after)
+
+### Phase 3: Polish for Stickiness
+
+For each story, verify: specificity, emotion, relatability, simplicity, strategic intent.
+
+### Phase 4: Usage Guide
+
+Map each story to its primary use case: sales calls, website, investor meetings, team all-hands, social media.
+
+## Output Format
+
+```yaml
+business_stories:
+  story_gap_assessment: "{which gap is costing most}"
+  value_story:
+    normal: "{specific before state}"
+    explosion: "{the struggle}"
+    new_normal: "{the transformation}"
+    use_case: "Sales conversations, landing pages"
+    duration: "60-90 seconds"
+  founder_story:
+    normal: "{founder's world before}"
+    explosion: "{the moment of realization}"
+    new_normal: "{the commitment}"
+    use_case: "About page, investor meetings, keynotes"
+    duration: "60-90 seconds"
+  purpose_story:
+    normal: "{before impact}"
+    explosion: "{the moment of impact}"
+    new_normal: "{lasting difference}"
+    use_case: "Team meetings, hiring, culture docs"
+    duration: "60-90 seconds"
+  customer_story:
+    normal: "{customer before}"
+    explosion: "{discovering solution}"
+    new_normal: "{transformed reality}"
+    use_case: "Case studies, testimonials, social proof"
+    duration: "60-90 seconds"
+```
+
+## Veto Conditions
+
+- **NEVER** write generic stories — specificity is everything
+- **NEVER** skip the Normal phase — relatability requires it
+- **NEVER** make the company the hero — the customer is always the hero
+- **NEVER** create stories longer than 90 seconds when spoken
+
+## Completion Criteria
+
+- [ ] All 4 story types drafted with specific, vivid details
+- [ ] Each follows Normal-Explosion-New Normal
+- [ ] Stories are 60-90 seconds when spoken
+- [ ] Strategic intent clear for each story
+- [ ] Usage guide maps stories to business contexts

package/squad-storytelling/tasks/build-story-circle.md

@@ -0,0 +1,98 @@
+---
+task: "build-story-circle"
+responsavel: "dan-harmon"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Story concept or existing narrative"
+Saida:
+  - "Complete Story Circle (8 steps) with content for each step"
+Checklist:
+  - "[ ] All 8 steps populated with specific content"
+  - "[ ] Death and rebirth moment identified at the bottom of the circle"
+  - "[ ] Character transformation clear from Step 1 to Step 8"
+---
+
+# Task: Build Story Circle
+
+**Task ID:** NARR-005
+**Version:** 1.0.0
+**Command:** `*build-story-circle`
+**Agent:** Dan Harmon (dan-harmon)
+**Purpose:** Apply the Story Circle (8 steps) to any narrative, mapping character journey through descent and return.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `story_concept` | User prompt | YES |
+| `format` | TV episode, film, brand, personal | PREFERRED |
+| `character` | Protagonist description | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Identify Character and World
+
+1. Who is the protagonist? What makes them relatable (not admirable — relatable)?
+2. What is their zone of comfort? (Not necessarily pleasant — just familiar)
+3. What is the conscious WANT vs the unconscious NEED?
+
+### Phase 2: Map the 8 Steps
+
+1. **YOU** — Establish the character in their status quo
+2. **NEED** — Something disrupts; a want or lack emerges
+3. **GO** — The character crosses the threshold into the unfamiliar
+4. **SEARCH** — Struggle, adaptation, trial and error in the new world
+5. **FIND** — They get what they wanted (midpoint; the nadir; symbolic death)
+6. **TAKE** — But they pay a heavy price for it
+7. **RETURN** — They cross back to the familiar world
+8. **CHANGE** — They are fundamentally different now
+
+### Phase 3: Verify the Circle
+
+1. Is there clear death and rebirth at steps 4-5-6?
+2. Does Step 8 mirror but differ from Step 1?
+3. Is the WANT resolved differently from the NEED?
+4. Would the audience FEEL something at each step?
+
+### Phase 4: Fractal Check (optional)
+
+Map nested circles if applicable: scene circles within episode circles within season circles.
+
+## Output Format
+
+```yaml
+story_circle:
+  character: "{protagonist}"
+  want: "{conscious desire}"
+  need: "{unconscious need}"
+  steps:
+    you: "{status quo}"
+    need: "{disruption/desire}"
+    go: "{crossing threshold}"
+    search: "{trials and adaptation}"
+    find: "{getting what was wanted — symbolic death}"
+    take: "{paying the price}"
+    return: "{coming back}"
+    change: "{transformed state}"
+  death_rebirth: "{what dies and what is born}"
+  emotional_arc: "{feeling progression}"
+  theme: "{what the circle is really about}"
+```
+
+## Veto Conditions
+
+- **NEVER** skip the death and rebirth — without it there is no transformation
+- **NEVER** make Step 8 identical to Step 1 — the whole point is change
+- **NEVER** confuse WANT and NEED — they must be different
+- **NEVER** let structure override character truth
+
+## Completion Criteria
+
+- [ ] All 8 steps populated with specific content
+- [ ] Death and rebirth clearly identified
+- [ ] Character transformation visible from Step 1 to Step 8
+- [ ] Emotional arc mapped throughout the circle