sinapse-ai 1.0.0

package/squad-storytelling/tasks/partnership-pitch-narrative.md

@@ -0,0 +1,130 @@
+---
+task: "partnership-pitch-narrative"
+responsavel: "oren-klaff"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Partnership opportunity details"
+  - "Both parties' profiles and motivations"
+Saida:
+  - "Partnership pitch narrative with status alignment and mutual frame design"
+Checklist:
+  - "[ ] Status dynamics mapped for both parties"
+  - "[ ] Mutual prize framing established (both sides gain)"
+  - "[ ] STRONG method adapted for collaborative rather than transactional pitch"
+---
+
+# Task: Partnership Pitch Narrative
+
+**Task ID:** NARR-029
+**Version:** 1.0.0
+**Command:** `*partnership-pitch-narrative`
+**Agent:** Oren Klaff (oren-klaff)
+**Purpose:** Craft partnership proposals using Pitch Anything's frame control and status alignment, adapted for collaborative dynamics where both parties must see themselves as gaining.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `your_organization` | Company, strengths, assets, goals | YES |
+| `target_partner` | Partner company, strengths, needs, goals | YES |
+| `partnership_type` | Co-marketing, technology, distribution, strategic alliance | YES |
+| `mutual_benefit` | What each party gains from the partnership | YES |
+| `context` | How the opportunity arose | PREFERRED |
+| `decision_makers` | Who approves on each side | NO |
+
+## Execution Phases
+
+### Phase 1: Map Status Dynamics
+
+1. Assess relative status — who needs whom more? (be honest)
+2. Identify power asymmetries (brand size, market position, resource disparity)
+3. Map each party's "prize" — what unique value does each bring that the other cannot get elsewhere?
+4. Identify potential frame conflicts: who will try to set the terms?
+5. Design status equilibrium — partnerships require peer-level framing, not dominance
+
+### Phase 2: Design Mutual Prize Frame
+
+1. Unlike sales, partnership pitches require BOTH parties to feel like the prize
+2. Articulate your unique prize: "What we bring that nobody else can"
+3. Acknowledge their unique prize: "What you bring that we value specifically"
+4. Design the "together" frame: "What becomes possible only through this combination"
+5. Create the "exclusivity" angle — why this partnership, why now, why these two
+6. Avoid the "we need you" trap — express desire without neediness
+
+### Phase 3: Apply STRONG for Partnerships
+
+1. **Set the Frame** — Open with a market observation that makes the partnership obvious
+2. **Tell the Story** — Narrative of what both organizations have been building toward
+3. **Reveal the Intrigue** — The specific opportunity that exists ONLY if both parties act together
+4. **Offer the Prize** — Your unique assets, results, and capabilities as contribution
+5. **Nail the Hookpoint** — The vision moment: what this partnership looks like at full potential
+6. **Get the Deal** — Propose a specific, low-risk first step (pilot, co-project, trial)
+
+### Phase 4: Design Collaboration Narrative
+
+1. Create a "shared enemy" — the market problem neither can solve alone
+2. Design the origin story of the partnership: "How we came to see this opportunity"
+3. Build the "future state" narrative: what the partnership achieves in 6, 12, 24 months
+4. Identify and address the "what could go wrong" openly — transparency builds trust
+5. Design mutual accountability language — partner, not vendor-client
+
+### Phase 5: Structure the Proposal
+
+1. Executive summary using partnership ABT (And we each have X, But the market needs Y, Therefore together we Z)
+2. Mutual value map — clear visual of what each party contributes and receives
+3. Proposed structure — governance, decision-making, IP, revenue split
+4. Pilot program design — low-risk first engagement that proves the concept
+5. Success metrics — how both parties will measure whether it is working
+6. Clear next steps — specific actions, owners, timeline
+
+## Output Format
+
+```yaml
+partnership_pitch:
+  your_org: "{name}"
+  target_partner: "{name}"
+  partnership_type: "{type}"
+  status_dynamics:
+    relative_status: "{assessment}"
+    your_prize: "{unique value you bring}"
+    their_prize: "{unique value they bring}"
+    combined_prize: "{what only this partnership creates}"
+  frame_strategy:
+    mutual_prize: "{how both sides feel valued}"
+    exclusivity: "{why this combination is special}"
+    shared_enemy: "{market problem neither can solve alone}"
+  strong_narrative:
+    set_frame: "{market observation}"
+    tell_story: "{convergence narrative}"
+    intrigue: "{unique opportunity}"
+    prize: "{your contribution}"
+    hookpoint: "{full potential vision}"
+    get_deal: "{proposed first step}"
+  proposal_structure:
+    executive_summary: "{partnership ABT}"
+    mutual_value_map: "{contributions and benefits}"
+    governance: "{decision-making framework}"
+    pilot: "{low-risk first engagement}"
+    success_metrics: ["{how to measure success}"]
+    next_steps: ["{specific actions and owners}"]
+```
+
+## Veto Conditions
+
+- **NEVER** pitch a partnership as if pitching a sale — the dynamic is peer, not buyer-seller
+- **NEVER** downplay your own value to seem accommodating — both parties must feel the prize
+- **NEVER** propose big commitments first — start with a pilot that proves the concept
+- **NEVER** ignore status asymmetry — address it directly or it undermines the partnership
+
+## Completion Criteria
+
+- [ ] Status dynamics honestly assessed and equilibrium designed
+- [ ] Mutual prize frame established (both sides see unique value)
+- [ ] STRONG method adapted for collaborative framing
+- [ ] Proposal includes pilot program with low-risk first step
+- [ ] Success metrics defined for both parties
+- [ ] Clear next steps with specific actions and owners

package/squad-storytelling/tasks/product-launch-narrative.md

@@ -0,0 +1,140 @@
+---
+task: "product-launch-narrative"
+responsavel: "dan-harmon"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Product details and value proposition"
+  - "Target market and launch timeline"
+Saida:
+  - "Complete product launch narrative using Story Circle 8 steps"
+Checklist:
+  - "[ ] Launch narrative follows complete Story Circle arc"
+  - "[ ] Pre-launch, launch, and post-launch phases mapped to circle steps"
+  - "[ ] Audience emotional journey designed for each phase"
+---
+
+# Task: Product Launch Narrative
+
+**Task ID:** NARR-022
+**Version:** 1.0.0
+**Command:** `*product-launch-narrative`
+**Agent:** Dan Harmon (dan-harmon)
+**Purpose:** Structure a product launch as a Story Circle narrative, creating emotional momentum from teaser through post-launch.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `product` | Product name, features, value proposition | YES |
+| `target_market` | Audience profile, needs, current alternatives | YES |
+| `launch_timeline` | Key dates and milestones | YES |
+| `brand_context` | Brand story, voice, positioning | PREFERRED |
+| `competitive_landscape` | Alternatives and differentiators | NO |
+
+## Execution Phases
+
+### Phase 1: Map Launch to Story Circle
+
+1. **YOU (Status Quo)** — The market as it exists today; the audience's current reality and habits
+2. **NEED (Desire)** — The unmet need, frustration, or aspiration the product addresses
+3. **GO (Departure)** — The teaser phase; inviting the audience into something new
+4. **SEARCH (Exploration)** — Revealing features, benefits, use cases progressively
+5. **FIND (Discovery)** — The "aha" moment — the core insight that makes the product click
+6. **TAKE (Acquisition)** — Launch day; making the product available; the call to action
+7. **RETURN (Integration)** — Post-launch; customers using the product in their real lives
+8. **CHANGE (Transformation)** — The new normal; how life/work is different with the product
+
+### Phase 2: Design Pre-Launch (Steps 1-3)
+
+1. Craft the "status quo acknowledgment" — show you understand their world (YOU)
+2. Agitate the gap — make the NEED visceral and urgent without revealing the solution
+3. Design teaser content that creates curiosity without over-promising (GO)
+4. Plan the "threshold moment" — when early adopters commit to learning more
+5. Build anticipation mechanics: waitlists, countdown, behind-the-scenes
+6. Identify the "herald" — who announces the coming change? (influencer, event, ad)
+
+### Phase 3: Design Launch (Steps 4-6)
+
+1. Structure the reveal sequence — progressive disclosure of features/benefits (SEARCH)
+2. Design the "eureka moment" — when the audience truly gets it (FIND)
+3. Create the launch event/content as a climactic narrative moment
+4. Structure the offer as the natural resolution to the story's tension (TAKE)
+5. Remove friction — the TAKE must feel inevitable, not forced
+6. Design social proof moments that validate the decision
+
+### Phase 4: Design Post-Launch (Steps 7-8)
+
+1. Plan onboarding as the RETURN journey — integrating the product into daily life
+2. Design "quick win" moments that reinforce the purchase decision
+3. Create transformation stories from early adopters (CHANGE evidence)
+4. Build community narrative — shared identity among users
+5. Plan the "new status quo" content — life WITH the product as the new normal
+
+### Phase 5: Create Narrative Timeline
+
+1. Map each Story Circle step to specific calendar dates
+2. Assign content types to each phase (email, social, video, PR, event)
+3. Design emotional intensity curve across the timeline
+4. Identify the 3 highest-energy moments (announce, reveal, launch day)
+5. Plan the "quiet after" — post-launch narrative that sustains engagement
+
+## Output Format
+
+```yaml
+product_launch_narrative:
+  product: "{name}"
+  story_circle:
+    you: "{market status quo}"
+    need: "{unmet need}"
+    go: "{teaser/departure}"
+    search: "{progressive reveal}"
+    find: "{aha moment}"
+    take: "{launch/acquisition}"
+    return: "{integration}"
+    change: "{new normal}"
+  pre_launch:
+    duration: "{weeks}"
+    content_plan: ["{teaser content pieces}"]
+    anticipation_mechanics: ["{waitlist, countdown, etc}"]
+    emotional_arc: "{curiosity → desire → impatience}"
+  launch:
+    date: ""
+    reveal_sequence: ["{progressive disclosure steps}"]
+    eureka_content: "{the piece that makes it click}"
+    offer_structure: "{how the TAKE is presented}"
+    social_proof: ["{validation moments}"]
+  post_launch:
+    onboarding_narrative: "{return journey design}"
+    quick_wins: ["{early success moments}"]
+    transformation_stories: "{early adopter narratives}"
+    community_building: "{shared identity design}"
+  timeline:
+    - date: ""
+      circle_step: ""
+      content: ""
+      emotional_intensity: "[1-10]"
+  peak_moments:
+    - moment: "{description}"
+      date: ""
+      content_type: ""
+```
+
+## Veto Conditions
+
+- **NEVER** launch without establishing the NEED — features without context are noise
+- **NEVER** reveal everything at once — the SEARCH phase requires progressive disclosure
+- **NEVER** treat launch day as the end — RETURN and CHANGE are essential
+- **NEVER** skip the emotional design — a launch without feeling is just an announcement
+
+## Completion Criteria
+
+- [ ] Complete Story Circle mapped to launch phases
+- [ ] Pre-launch builds genuine anticipation (not just hype)
+- [ ] Launch moment designed as narrative climax
+- [ ] Post-launch narrative sustains engagement and builds community
+- [ ] Timeline created with emotional intensity mapped
+- [ ] Content types assigned to each phase

package/squad-storytelling/tasks/review-narrative-output.md

@@ -0,0 +1,108 @@
+---
+task: "review-narrative-output"
+responsavel: "narrative-orchestrator"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Specialist agent output (narrative deliverable)"
+  - "Original user request"
+Saida:
+  - "Review report with verdict (APPROVE/REVISE/REJECT)"
+Checklist:
+  - "[ ] All quality items evaluated and scored"
+  - "[ ] Verdict rendered (APPROVE/REVISE/REJECT)"
+  - "[ ] Specific feedback provided for any failures"
+---
+
+# Task: Review Narrative Output
+
+**Task ID:** NARR-002
+**Version:** 1.0.0
+**Command:** `*review-narrative-output`
+**Agent:** Arc (narrative-orchestrator)
+**Purpose:** Review specialist output against quality criteria, score, and approve or request revision.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `specialist_output` | Specialist agent | YES |
+| `original_request` | User prompt | YES |
+| `specialist_id` | Routing | YES |
+
+## Execution Phases
+
+### Phase 1: Understand Context
+
+1. Re-read the original user request
+2. Identify what was asked vs what was delivered
+3. Note the specialist who produced the output
+4. Identify the narrative purpose: brand story, pitch, content, origin story, presentation, manifesto
+5. Determine the target audience and emotional destination
+
+### Phase 2: Apply Quality Criteria
+
+Evaluate each dimension (1-5 scale):
+
+| Dimension | Weight | Criteria |
+|-----------|--------|----------|
+| Structure | HIGH | Clear beginning/middle/end, beats present, framework followed |
+| Emotional Arc | HIGH | Feelings progression, tension/release, transformation earned |
+| Opening Hook | HIGH | First 30 seconds capture attention, establish stakes |
+| Audience Alignment | MEDIUM | Resonates with intended audience, appropriate tone |
+| Theme Integration | MEDIUM | Central message woven throughout, not just stated |
+| Specificity | MEDIUM | Concrete details, not vague generalizations |
+| Call to Action | MEDIUM | Clear next step (if applicable) |
+| Framework Fidelity | LOW | Follows the specialist's methodology correctly |
+
+### Phase 3: Score and Decide
+
+| Score | Verdict | Action |
+|-------|---------|--------|
+| All HIGH dimensions >= 4, average >= 3.5 | APPROVE | Deliver to user |
+| All HIGH dimensions >= 3, average >= 3.0 | REVISE | Return to specialist with specific feedback |
+| Any HIGH dimension < 3 | REJECT | Return to specialist, block delivery |
+
+### Phase 4: Output
+
+```markdown
+## Review Report
+
+**Specialist:** {name} ({id})
+**Verdict:** {APPROVE | REVISE | REJECT}
+**Score:** {average}/5.0
+
+### Strengths
+- {items that scored well}
+
+### Issues Found
+- [{CRITICAL|WARN}] {description} — {recommendation}
+
+### Narrative-Specific Notes
+- Emotional arc strength: {assessment}
+- Opening hook effectiveness: {assessment}
+- Resolution satisfaction: {assessment}
+
+### Recommendation
+{Next step: deliver / revise specific items / redo}
+```
+
+## Veto Conditions
+
+- **NEVER** approve output with any HIGH dimension below 3
+- **NEVER** reject without providing specific, actionable feedback
+- **NEVER** modify the specialist's output — only review and provide feedback
+- **NEVER** approve narratives without a clear structure (beginning, middle, end)
+- **NEVER** approve stories that lack emotional engagement or feel flat
+
+## Completion Criteria
+
+- [ ] Original request re-read and understood
+- [ ] Narrative purpose and audience identified
+- [ ] All quality dimensions evaluated and scored
+- [ ] Verdict rendered (APPROVE/REVISE/REJECT)
+- [ ] Specific feedback provided for any failures
+- [ ] Emotional arc, structure, and hook individually assessed

package/squad-storytelling/tasks/sales-presentation-frames.md

@@ -0,0 +1,137 @@
+---
+task: "sales-presentation-frames"
+responsavel: "oren-klaff"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Product/service being sold"
+  - "Buyer profile and decision dynamics"
+Saida:
+  - "Sales presentation with frame control strategy and STRONG structure"
+Checklist:
+  - "[ ] Buyer frames identified and counter-frames designed"
+  - "[ ] Prize frame maintained throughout presentation"
+  - "[ ] Hot cognition moments designed for key decision points"
+---
+
+# Task: Sales Presentation with Frame Control
+
+**Task ID:** NARR-028
+**Version:** 1.0.0
+**Command:** `*sales-presentation-frames`
+**Agent:** Oren Klaff (oren-klaff)
+**Purpose:** Build sales presentations that control the frame, maintain prize positioning, and drive decisions through hot cognition rather than rational analysis.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `product_service` | What is being sold | YES |
+| `buyer_profile` | Decision maker(s), their role, authority, motivations | YES |
+| `deal_size` | Approximate value of the deal | YES |
+| `sales_context` | Cold outreach, warm intro, RFP response, renewal | YES |
+| `competition` | Who else is the buyer considering | PREFERRED |
+| `previous_interactions` | Any prior meetings or communications | NO |
+
+## Execution Phases
+
+### Phase 1: Buyer Frame Analysis
+
+1. Identify the buyer's default frames:
+   - **Power Frame** — "I'm the buyer, you need me" (most common)
+   - **Analyst Frame** — "Show me the data, ROI, comparisons"
+   - **Time Frame** — "I'm busy, make it quick"
+   - **Moral Authority Frame** — "We have high standards"
+2. Map the decision-making unit — who influences, who decides, who blocks
+3. Identify beta traps in the sales environment (waiting rooms, junior gatekeepers, "send a proposal")
+4. Determine the buyer's hot buttons — what triggers desire vs analysis
+
+### Phase 2: Design Counter-Frame Strategy
+
+1. **Power Frame → Prize Frame** — "We choose our clients carefully"
+2. **Analyst Frame → Intrigue Frame** — Lead with mystery, not spreadsheets
+3. **Time Frame → Time Constraint** — "I have a hard stop too; let's make this count"
+4. **Moral Authority → Peer Authority** — Establish domain expertise they respect
+5. Design status-leveling techniques for the first 60 seconds
+6. Plan "takeaway" moments — willingness to walk creates desire
+
+### Phase 3: Build STRONG Sales Presentation
+
+1. **Set the Frame** — Open with a bold market observation, NOT a company overview
+2. **Tell the Story** — Client problem narrative: a specific story of someone like them
+3. **Reveal the Intrigue** — The unique angle, approach, or insight that separates you
+4. **Offer the Prize** — Results, case studies, social proof framed as exclusive access
+5. **Nail the Hookpoint** — The moment the buyer shifts from evaluating to wanting
+6. **Get the Deal** — Clear next steps, commitment request, timeline
+
+### Phase 4: Design Hot Cognition Triggers
+
+1. **Novelty** — Something the buyer has never heard from a vendor before
+2. **Tension** — Unresolved question that only your solution answers
+3. **Status alignment** — Showing you understand their world at their level
+4. **Scarcity** — Limited availability, exclusive terms, closing window
+5. **Social proof** — Competitors or peers who already chose you
+6. Time each trigger to land at decision-critical moments in the presentation
+
+### Phase 5: Objection Prevention and Close Design
+
+1. Pre-empt the top 5 objections WITHIN the presentation (don't wait for Q&A)
+2. Design the "push-pull" close — show desire but maintain willingness to walk
+3. Create the "next step cascade" — if they say yes, what happens immediately?
+4. Design the "no is okay" frame — removing pressure paradoxically increases desire
+5. Plan the follow-up sequence maintaining frame control (no desperate check-ins)
+
+## Output Format
+
+```yaml
+sales_presentation:
+  product: "{name}"
+  buyer: "{profile}"
+  deal_size: ""
+  frame_strategy:
+    buyer_default_frames: ["{identified frames}"]
+    counter_frames:
+      - buyer_frame: "{power/analyst/time}"
+        counter: "{prize/intrigue/constraint}"
+        technique: "{specific move}"
+    status_play: "{first 60 seconds strategy}"
+  strong_structure:
+    set_frame: "{bold opening statement}"
+    tell_story: "{client problem narrative}"
+    reveal_intrigue: "{unique insight}"
+    offer_prize: "{exclusive proof}"
+    hookpoint: "{the moment they lean in}"
+    get_deal: "{clear ask and next steps}"
+  hot_cognition_triggers:
+    - trigger: "{type}"
+      content: "{what to say/show}"
+      timing: "{when in the presentation}"
+  objection_prevention:
+    - objection: "{anticipated concern}"
+      preemptive_address: "{how it's handled in the flow}"
+  close_design:
+    primary_ask: "{specific next step}"
+    push_pull: "{desire + willingness to walk}"
+    next_step_cascade: "{if yes, then what}"
+    follow_up_plan: "{frame-controlled sequence}"
+```
+
+## Veto Conditions
+
+- **NEVER** open with a company overview slide — the buyer does not care yet
+- **NEVER** enter the analyst frame willingly — data follows desire, not the other way
+- **NEVER** chase after the meeting — every follow-up must maintain prize frame
+- **NEVER** let a gatekeeper set your status — establish frame before the meeting starts
+- **NEVER** present features without frame — features in an analyst frame become commodities
+
+## Completion Criteria
+
+- [ ] Buyer frames analyzed and counter-frames designed
+- [ ] STRONG method applied to presentation flow
+- [ ] Hot cognition triggers timed to decision moments
+- [ ] Top 5 objections preemptively addressed within presentation
+- [ ] Close designed with push-pull dynamics
+- [ ] Follow-up sequence maintains frame control

package/squad-storytelling/tasks/social-media-story-strategy.md

@@ -0,0 +1,161 @@
+---
+task: "social-media-story-strategy"
+responsavel: "park-howell"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Brand context and social media presence"
+  - "Target audience and platform strategy"
+Saida:
+  - "Social media storytelling strategy with ABT content frameworks per platform"
+Checklist:
+  - "[ ] ABT framework adapted for each platform's format"
+  - "[ ] Content pillars aligned with Story Cycle System"
+  - "[ ] 30-day content plan with story-structured posts"
+---
+
+# Task: Social Media Story Strategy
+
+**Task ID:** NARR-041
+**Version:** 1.0.0
+**Command:** `*social-media-story-strategy`
+**Agent:** Park Howell (park-howell)
+**Purpose:** Create a social media storytelling strategy using ABT framework and Story Cycle System, turning social content from noise into narrative.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `brand_context` | Brand, values, BrandScript | YES |
+| `platforms` | Which social media channels | YES |
+| `audience` | Target audience per platform | YES |
+| `current_content` | Existing social media content | PREFERRED |
+| `goals` | Awareness, engagement, conversion, community | PREFERRED |
+| `frequency` | Posting cadence per platform | NO |
+
+## Execution Phases
+
+### Phase 1: Diagnose Current Social Content
+
+1. Audit existing content for narrative quality:
+   - AAA content: "We launched X and it has Y features and Z benefits" (boring)
+   - ABT content: "You face X, BUT Y makes it hard, THEREFORE here's Z" (engaging)
+2. Calculate the narrative ratio — what percentage tells a story?
+3. Identify which posts got highest engagement — do they share narrative patterns?
+4. Find the "story gap" on social — what stories are missing?
+
+### Phase 2: Define Story-Based Content Pillars
+
+Map content pillars to Story Cycle stages:
+1. **Backstory pillar** — Behind-the-scenes, origins, the "why" behind the brand
+2. **Desire pillar** — Aspirational content showing the transformed state
+3. **Resistance pillar** — Naming the obstacles the audience faces (empathy)
+4. **Adventure pillar** — Educational content, tips, how-tos (the solution journey)
+5. **Trial pillar** — Case studies, results, proof (overcoming challenges)
+6. **Rebirth pillar** — Customer transformations, testimonials, celebrations
+
+### Phase 3: Adapt ABT for Each Platform
+
+1. **LinkedIn ABT:**
+   - And: Professional context or industry observation (2-3 lines)
+   - But: Counterintuitive insight or challenge (1-2 lines)
+   - Therefore: Key lesson or recommendation (1-2 lines)
+   - Format: 150-300 words, text-first, CTA to comment
+2. **Instagram ABT:**
+   - And: Visual showing the situation (image/reel)
+   - But: Caption hook that names the tension (first line)
+   - Therefore: The insight or story resolution (caption body)
+   - Format: Carousel (ABT across slides) or Reel (ABT in 30-60s)
+3. **Twitter/X ABT:**
+   - And: Thread opener establishing context (tweet 1)
+   - But: The twist or problem (tweet 2-3)
+   - Therefore: The lesson or resolution (final tweet)
+   - Format: Thread of 5-7 tweets or single tweet with contrast
+4. **TikTok ABT:**
+   - And: Visual hook in first 1-2 seconds
+   - But: The tension or reveal at 3-5 seconds
+   - Therefore: Resolution/transformation by end
+   - Format: 15-60 second video, text overlay, trending audio
+
+### Phase 4: Create Story Templates
+
+For each pillar, create reusable post templates:
+1. **The Origin Post** — "Here's why we started..." (ABT: We were doing X, But Y happened, Therefore we built Z)
+2. **The Customer Post** — "Meet [name]..." (ABT: They faced X, But struggled with Y, Therefore with our help Z)
+3. **The Lesson Post** — "I used to think X..." (ABT: Everyone says X, But actually Y, Therefore do Z)
+4. **The Behind-the-Scenes Post** — "Here's what you don't see..." (ABT: It looks like X, But really Y, Therefore we do Z)
+5. **The Challenge Post** — "Most people get this wrong..." (ABT: You try X, But Y happens, Therefore try Z instead)
+
+### Phase 5: Build 30-Day Content Plan
+
+1. Map 30 days of content across pillars and platforms
+2. Ensure each week has a narrative arc (mini Story Cycle across 5-7 posts)
+3. Include a "serial story" — a multi-post narrative that builds over the month
+4. Plan engagement triggers (questions, polls, challenges) within the narrative
+5. Design the content creation workflow (batch creation using ABT templates)
+6. Define success metrics per pillar and platform
+
+## Output Format
+
+```yaml
+social_media_story_strategy:
+  brand: "{name}"
+  platforms: ["{channels}"]
+  narrative_audit:
+    current_abt_ratio: "{percentage}"
+    top_performing_pattern: "{what works now}"
+    story_gap: "{what's missing}"
+  content_pillars:
+    - pillar: "{name}"
+      story_cycle_stage: "{which stage}"
+      frequency: "{per week}"
+      platform_adaptation: "{how it changes per platform}"
+  platform_abt:
+    linkedin:
+      format: "{text structure}"
+      ideal_length: "{word count}"
+      example_post: "{ABT example}"
+    instagram:
+      format: "{visual + caption}"
+      ideal_length: "{caption length}"
+      example_post: "{ABT example}"
+    # ... per platform
+  templates:
+    - name: "{template name}"
+      abt_structure: "{And/But/Therefore}"
+      pillar: "{which content pillar}"
+      example: "{complete post example}"
+  thirty_day_plan:
+    - week: 1
+      theme: "{weekly narrative arc}"
+      posts:
+        - day: 1
+          platform: "{channel}"
+          pillar: "{content pillar}"
+          template: "{which template}"
+          topic: "{specific subject}"
+  serial_story: "{multi-post narrative description}"
+  metrics:
+    - pillar: "{name}"
+      kpi: "{what to measure}"
+      target: "{benchmark}"
+```
+
+## Veto Conditions
+
+- **NEVER** post content without ABT structure — random facts are noise, not narrative
+- **NEVER** use the same format across all platforms — each platform has its own ABT
+- **NEVER** create a content plan without a weekly narrative arc — isolated posts don't build
+- **NEVER** make the brand the hero of every post — the customer and their story come first
+
+## Completion Criteria
+
+- [ ] Current content audited for narrative quality
+- [ ] Content pillars mapped to Story Cycle stages
+- [ ] ABT adapted for each platform with format specifications
+- [ ] Reusable story templates created (5+ templates)
+- [ ] 30-day content plan with weekly narrative arcs
+- [ ] Success metrics defined per pillar and platform