invos 1.0.0

package/kit/.agents/squads/hormozi-squad/tasks/create-hooks.md

@@ -0,0 +1,159 @@
+---
+task: createHooks()
+responsavel: "@hormozi-hooks"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: topic
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+  - campo: platform
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+
+Saida:
+  - campo: hookPackage
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] Hooks written across at least 4 categories"
+  - "[ ] Platform constraints respected"
+  - "[ ] All hooks scored on 3 dimensions"
+---
+
+# Task: Create Hooks
+
+**Task ID:** HORMOZI-005
+**Version:** 1.0.0
+**Command:** `*create-hooks`
+**Agent:** Hormozi Hooks (hormozi-hooks)
+**Purpose:** Create attention-grabbing hooks for content, ads, and sales material.
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| topic | string | User prompt | Yes | Subject matter for the hooks |
+| platform | enum | User prompt | Yes | youtube, tiktok, instagram, facebook, linkedin, email, ad |
+| audience | string | User prompt | Yes | Who the hooks must stop |
+| content_goal | enum | User prompt | Yes | educate, sell, entertain, build-authority, generate-leads |
+| quantity | number | User prompt | No | Defaults to 20 hooks |
+
+---
+
+## Preconditions
+
+- Platform selected with understanding of format constraints
+- Audience defined with enough specificity to write for them
+
+---
+
+## Execution Phases
+
+### Phase 1: Hook Category Mapping
+1. Select from the 7 hook categories (Hormozi framework):
+   - **Contrarian:** Challenge a commonly held belief
+   - **Curiosity Gap:** Create an information gap they must close
+   - **Result/Proof:** Lead with a specific, impressive result
+   - **Story:** Open with a dramatic moment from a real story
+   - **Question:** Ask a question that forces self-reflection
+   - **Bold Claim:** Make a specific, provocative statement
+   - **Pattern Interrupt:** Break the expected scroll pattern with something unexpected
+2. Allocate hooks across categories (at least 3 from each used category)
+3. Match category to platform norms:
+   - YouTube: Curiosity Gap and Result hooks dominate
+   - TikTok: Pattern Interrupt and Contrarian perform best
+   - LinkedIn: Bold Claim and Result hooks drive engagement
+   - Email subjects: Curiosity Gap and Question hooks win opens
+   - Ads: Result and Bold Claim hooks stop the scroll
+
+### Phase 2: Hook Writing
+1. Write each hook following platform constraints:
+   - YouTube: Under 10 words for thumbnail, under 15 seconds spoken
+   - TikTok/Reels: Under 3 seconds (8-12 words max)
+   - LinkedIn: First line before "see more" (under 150 chars)
+   - Email: Under 50 characters for subject line
+   - Ads: Under 125 characters for primary text hook
+2. Apply the specificity rule: replace vague words with numbers, names, or details
+3. Apply the "would I stop scrolling?" test to each hook
+4. Create 2-3 variations per core hook idea (reframed angles)
+
+### Phase 3: Scoring and Packaging
+1. Score each hook on 3 dimensions (1-5):
+   - Stop Power: Would someone stop scrolling?
+   - Relevance: Is it relevant to the target audience?
+   - Payoff Potential: Can the content deliver on this hook's promise?
+2. Rank by total score
+3. Group into "ready to use" and "needs content built around it"
+4. Suggest content ideas for the top 5 hooks
+5. Provide A/B testing pairs
+
+---
+
+## Output Format
+
+```markdown
+## Hook Package: {Topic}
+
+**Platform:** {platform}
+**Audience:** {audience}
+**Total Hooks:** {count}
+
+---
+
+### Top 10 Hooks (Ranked)
+
+| Rank | Hook | Category | Stop | Relevance | Payoff | Total |
+|------|------|----------|------|-----------|--------|-------|
+
+### All Hooks by Category
+
+#### Contrarian
+1. {hook}
+2. {hook}
+
+#### Curiosity Gap
+1. {hook}
+2. {hook}
+
+#### Result/Proof
+...
+
+### Content Ideas for Top 5
+| Hook | Content Idea | Format |
+|------|-------------|--------|
+
+### A/B Testing Pairs
+| Pair | Hook A | Hook B | What We're Testing |
+|------|--------|--------|-------------------|
+```
+
+---
+
+## Veto Conditions
+
+- NEVER write hooks that the content cannot deliver on — clickbait destroys trust
+- NEVER write vague hooks ("This changed everything") — specificity is mandatory
+- NEVER ignore platform constraints — a YouTube hook differs from a TikTok hook
+- NEVER submit hooks without scoring — unranked hooks are unusable
+- NEVER use the same formula for more than 3 consecutive hooks
+
+---
+
+## Completion Criteria
+
+- [ ] Hooks written across at least 4 categories
+- [ ] Platform constraints respected
+- [ ] All hooks scored on 3 dimensions
+- [ ] Top 10 ranked with rationale
+- [ ] Content ideas provided for top 5
+- [ ] A/B testing pairs suggested
+- [ ] Specificity rule applied to every hook

package/kit/.agents/squads/hormozi-squad/tasks/create-offer.md

@@ -0,0 +1,178 @@
+---
+task: createOffer()
+responsavel: "@hormozi-offers"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: product
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+  - campo: audience
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+
+Saida:
+  - campo: grandSlamOffer
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] Value Equation scored across all 4 quadrants"
+  - "[ ] Problems mapped to solution vehicles with proprietary names"
+  - "[ ] Offer stack assembled with core + bonuses"
+---
+
+# Task: Create Grand Slam Offer
+
+**Task ID:** HORMOZI-001
+**Version:** 1.0.0
+**Command:** `*create-offer`
+**Agent:** Hormozi Offers (hormozi-offers)
+**Purpose:** Build a Grand Slam Offer using the Value Equation from $100M Offers.
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| product | string | User prompt | Yes | Core product or service |
+| audience | string | User prompt | Yes | Dream customer avatar |
+| current_price | number | User prompt | No | Existing price if applicable |
+| delivery_method | string | User prompt | No | How the product is delivered |
+| market | string | User prompt | No | Industry or niche |
+| competitors | list | User prompt | No | Known competing offers |
+
+---
+
+## Preconditions
+
+- Core product or service identified
+- Target audience defined with clear pain points and dream outcomes
+
+---
+
+## Execution Phases
+
+### Phase 1: Dream Outcome Mapping
+1. Define the dream outcome in the customer's words (not yours)
+2. Identify the gap between where they are and where they want to be
+3. List every problem that stands between the customer and the dream outcome
+4. For each problem, list the sub-problems and adjacent problems
+5. Rate each problem by severity (how much pain it causes 1-10)
+6. Identify which problems they have tried and failed to solve before
+
+### Phase 2: Value Equation Construction
+1. Apply the Hormozi Value Equation: Value = (Dream Outcome x Perceived Likelihood) / (Time Delay x Effort & Sacrifice)
+2. Maximize the numerator:
+   - Dream Outcome: Make the outcome as specific and vivid as possible
+   - Perceived Likelihood: Stack proof, guarantees, and track record
+3. Minimize the denominator:
+   - Time Delay: Compress time to first result
+   - Effort & Sacrifice: Remove friction, do it for them where possible
+4. Score each quadrant (1-10) for the current offer
+5. Identify which quadrant has the most room for improvement
+
+### Phase 3: Offer Architecture
+1. Transform each problem into a solution vehicle (course, tool, template, service, community, etc.)
+2. Name each solution vehicle with a proprietary name
+3. Assign delivery method and format to each vehicle
+4. Stack the vehicles into a cohesive offer:
+   - Core offer: The main transformation vehicle
+   - Speed bonuses: Things that compress time to result
+   - Effort bonuses: Things that reduce work required
+   - Proof bonuses: Things that increase confidence
+5. Design the guarantee using the Hormozi guarantee stack:
+   - Unconditional (full refund, no questions)
+   - Conditional (refund if you do X and don't get Y)
+   - Anti-guarantee (this is NOT for you if...)
+   - Performance (we'll work for free until you hit X)
+6. Set the price based on value delivered, not cost or competitors
+
+### Phase 4: Offer Naming and Positioning
+1. Create a compelling offer name that implies the transformation
+2. Write the one-line value proposition
+3. Define the "this is NOT for you" qualifier to increase perceived exclusivity
+4. Create the scarcity/urgency mechanism
+5. Write the stack slide (visual summary of everything included)
+
+---
+
+## Output Format
+
+```markdown
+## Grand Slam Offer: {Offer Name}
+
+**Dream Outcome:** {specific outcome}
+**Avatar:** {dream customer}
+**Price:** ${price}
+**Value Equation Score:** {X}/10
+
+---
+
+### Value Equation Breakdown
+
+| Quadrant | Score | Strategy |
+|----------|-------|----------|
+| Dream Outcome | X/10 | {how we maximize} |
+| Perceived Likelihood | X/10 | {how we maximize} |
+| Time Delay | X/10 | {how we minimize} |
+| Effort & Sacrifice | X/10 | {how we minimize} |
+
+### Problems → Solutions Map
+
+| Problem | Solution Vehicle | Proprietary Name | Delivery |
+|---------|-----------------|-------------------|----------|
+
+### Offer Stack
+
+| Component | What It Does | Value |
+|-----------|-------------|-------|
+| Core Offer | {description} | ${value} |
+| Speed Bonus 1 | {description} | ${value} |
+| Effort Bonus 1 | {description} | ${value} |
+| Proof Bonus 1 | {description} | ${value} |
+
+**Total Value:** ${total}
+**Your Price:** ${price}
+
+### Guarantee
+{Full guarantee statement with type}
+
+### Scarcity/Urgency
+{Mechanism and rationale}
+
+### Qualifier
+"This is NOT for you if..."
+
+### Stack Slide Copy
+{Ready-to-use visual stack summary}
+```
+
+---
+
+## Veto Conditions
+
+- NEVER create an offer without applying the Value Equation
+- NEVER price based on competitor prices — price based on value delivered
+- NEVER skip the problem-solution mapping — every solution must solve a real problem
+- NEVER create a guarantee that the business cannot fulfill
+- NEVER add bonuses that distract from the core transformation
+
+---
+
+## Completion Criteria
+
+- [ ] Dream outcome defined in customer's language
+- [ ] Value Equation scored across all 4 quadrants
+- [ ] Problems mapped to solution vehicles with proprietary names
+- [ ] Offer stack assembled with core + bonuses
+- [ ] Guarantee designed and documented
+- [ ] Price set with value-based justification
+- [ ] Scarcity mechanism defined
+- [ ] Stack slide copy written

package/kit/.agents/squads/hormozi-squad/tasks/design-workshop.md

@@ -0,0 +1,192 @@
+---
+task: designWorkshop()
+responsavel: "@hormozi-workshop"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: topic
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+  - campo: duration
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+
+Saida:
+  - campo: workshopDesign
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] Single transformation promise defined"
+  - "[ ] 3-5 teaching modules designed with frameworks and exercises"
+  - "[ ] Run of show created with timing"
+---
+
+# Task: Design Workshop
+
+**Task ID:** HORMOZI-008
+**Version:** 1.0.0
+**Command:** `*design-workshop`
+**Agent:** Hormozi Workshop (hormozi-workshop)
+**Purpose:** Design a workshop that delivers massive value and converts attendees into buyers.
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| topic | string | User prompt | Yes | Workshop subject and transformation |
+| audience | string | User prompt | Yes | Target attendees |
+| duration | string | User prompt | Yes | 60min, 90min, half-day, full-day, multi-day |
+| format | enum | User prompt | Yes | virtual, in-person, hybrid |
+| backend_offer | object | User prompt | No | What you sell at the end (if conversion workshop) |
+| price | number | User prompt | No | Workshop ticket price (0 for free) |
+| capacity | number | User prompt | No | Max attendees |
+
+---
+
+## Preconditions
+
+- Topic expertise available to deliver the content
+- If conversion workshop: backend offer must be defined
+
+---
+
+## Execution Phases
+
+### Phase 1: Workshop Architecture
+1. Define the single transformation promise ("By the end of this workshop, you will...")
+2. Choose the workshop model:
+   - Pure Value: No pitch, brand building and relationship
+   - Value + Offer: 80% teaching, 20% transition to offer
+   - Implementation: Hands-on where they build something live
+3. Structure the content blocks:
+   - Opening: Hook + promise + agenda (10% of time)
+   - Teaching blocks: 3-5 core modules (70% of time)
+   - Implementation/exercises: Hands-on application (embedded in teaching)
+   - Close: Recap + CTA or offer transition (20% of time)
+4. For each teaching block, define the "aha moment" — what will they realize?
+
+### Phase 2: Content Design
+1. For each teaching block:
+   - Big idea (one concept per block)
+   - Framework or model to teach it
+   - Example or case study to illustrate
+   - Exercise or implementation step
+   - Transition to next block
+2. Design the "framework reveal" — give them a proprietary framework
+3. Create worksheets or templates attendees will use
+4. Build in interaction points every 10-15 minutes:
+   - Questions to the audience
+   - Chat engagement prompts
+   - Quick exercises
+   - Poll or vote moments
+5. Plan the energy arc: start strong, vary pace, end on a peak
+
+### Phase 3: Conversion Design (if applicable)
+1. Plant "seeds" throughout the teaching that point to the offer:
+   - "In my program, we go much deeper on this..."
+   - "My clients get a done-for-you version of this..."
+2. Design the transition from teaching to offer (the "bridge"):
+   - Recap the transformation they experienced
+   - Identify the gap between workshop knowledge and full implementation
+   - Position the offer as the bridge to close that gap
+3. Structure the offer presentation:
+   - Restate the dream outcome
+   - Reveal the offer and what's included
+   - Stack the value
+   - Present the price with anchoring
+   - Handle the top 3 objections
+   - CTA with urgency
+4. Plan the follow-up for non-buyers
+
+### Phase 4: Logistics and Delivery
+1. Create the run-of-show with exact timing
+2. Define tech requirements (platform, tools, slides, chat)
+3. Plan the registration and reminder sequence
+4. Create the post-workshop follow-up plan
+5. Define success metrics (attendance rate, engagement, conversion if applicable)
+
+---
+
+## Output Format
+
+```markdown
+## Workshop Design: {Workshop Name}
+
+**Promise:** "By the end, you will {transformation}"
+**Duration:** {time}
+**Format:** {format}
+**Model:** {pure-value / value+offer / implementation}
+**Capacity:** {N}
+
+---
+
+### Run of Show
+
+| Time | Block | Content | Energy Level |
+|------|-------|---------|-------------|
+| 0:00-{X} | Opening | {hook + promise} | High |
+| {X}-{Y} | Module 1 | {topic} | Medium |
+| ... | ... | ... | ... |
+| {Z}-END | Close/Offer | {recap + CTA} | Peak |
+
+### Module Details
+
+#### Module 1: {Title}
+**Big Idea:** {concept}
+**Framework:** {framework name}
+**Example:** {case study}
+**Exercise:** {what they do}
+**Aha Moment:** {realization}
+
+#### Module 2-N: ...
+
+### Worksheets/Templates
+| Resource | Purpose | When Used |
+|----------|---------|-----------|
+
+### Conversion Plan (if applicable)
+**Seeds planted in:** {modules}
+**Bridge script:** {transition language}
+**Offer presentation:** {structure}
+**Follow-up plan:** {non-buyer sequence}
+
+### Registration and Reminders
+| Timing | Communication | Channel |
+|--------|--------------|---------|
+
+### Success Metrics
+| Metric | Target |
+|--------|--------|
+```
+
+---
+
+## Veto Conditions
+
+- NEVER design a workshop without a single clear transformation promise
+- NEVER teach more than 5 core concepts — depth beats breadth
+- NEVER go more than 15 minutes without audience interaction
+- NEVER pitch before delivering substantial value (minimum 60% pure teaching)
+- NEVER skip the energy arc — monotone workshops lose people
+
+---
+
+## Completion Criteria
+
+- [ ] Single transformation promise defined
+- [ ] Workshop model selected
+- [ ] 3-5 teaching modules designed with frameworks and exercises
+- [ ] Run of show created with timing
+- [ ] Interaction points planned every 10-15 minutes
+- [ ] Conversion plan designed (if applicable)
+- [ ] Worksheets/templates created
+- [ ] Registration and follow-up sequences planned
+- [ ] Success metrics defined

package/kit/.agents/squads/hormozi-squad/tasks/diagnose.md

@@ -0,0 +1,166 @@
+---
+task: diagnoseBusinessChallenge()
+responsavel: "@hormozi-chief"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: request
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+  - campo: revenue_stage
+    tipo: string
+    origem: User Input
+    obrigatorio: false
+
+Saida:
+  - campo: diagnosis
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] Request parsed and keywords extracted"
+  - "[ ] Routing catalog consulted with scored results"
+  - "[ ] Quick answer provided with Hormozi framework reference"
+---
+
+# Task: Diagnose Business Challenge
+
+**Task ID:** HORMOZI-CHIEF-001
+**Version:** 1.0.0
+**Command:** `*diagnose`
+**Orchestrator:** Hormozi Chief (hormozi-chief)
+**Purpose:** Triage business challenges, provide quick answer using Hormozi frameworks, route to specialist.
+
+---
+
+## Overview
+
+```
+User Request → Parse Keywords → Match Routing Catalog → Answer/Route → Output
+     │              │                    │                     │
+     ▼              ▼                    ▼                     ▼
+  Raw input   Extract business     Score domains         Quick answer +
+              challenge type     against 15 domains     specialist route
+              + stage + metric                          (Value Equation lens)
+```
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| request | string | User prompt | Yes | Non-empty business challenge description |
+| context | object | Session state | No | Business stage, revenue, industry, current metrics |
+| revenue_stage | string | User prompt | No | Pre-revenue, <$1M, $1-3M, $3-10M, $10M+ |
+
+---
+
+## Preconditions
+
+- Hormozi Squad is active with Hormozi Chief as entry agent
+- Routing catalog loaded from data/routing-catalog.yaml
+- All 15 specialist agents registered in config.yaml
+- Core formula context: Value = (Dream Outcome x Perceived Likelihood) / (Time Delay x Effort & Sacrifice)
+
+---
+
+## Execution Phases
+
+### Phase 1: Analyze Request
+
+1. Parse the user's business challenge
+2. Extract primary keywords and intent
+3. Identify the business function (offers, leads, pricing, sales, scaling, retention, etc.)
+4. Identify the business stage if mentioned (pre-revenue, startup, growth, scale)
+5. Note which part of the Value Equation is underperforming
+
+### Phase 2: Match Against Routing Catalog
+
+| Domain | Keywords | Route To |
+|--------|----------|----------|
+| Offer Creation | offer, grand slam, value stack, bonuses, guarantee | hormozi-offers / hormozi-pricing |
+| Lead Generation | leads, lead magnet, acquisition, outreach, traffic | hormozi-leads / hormozi-ads |
+| Pricing Strategy | pricing, charge more, premium, margins, price point | hormozi-pricing / hormozi-offers |
+| Sales Copy | sales copy, landing page copy, ad text, write copy | hormozi-copy / hormozi-hooks |
+| Paid Ads | ads, paid ads, advertising, ad spend, media buying | hormozi-ads / hormozi-hooks |
+| Content Strategy | content, social media, organic, YouTube, posting | hormozi-content / hormozi-hooks |
+| Hooks & Headlines | hooks, headlines, attention, scroll stopper, opening | hormozi-hooks / hormozi-copy |
+| Product Launch | launch, go to market, MVP, first customers | hormozi-launch / hormozi-offers |
+| Sales Closing | close, sales call, objections, CLOSER, high ticket | hormozi-closer / hormozi-offers |
+| Workshop Design | workshop, seminar, event, training, masterclass | hormozi-workshop / hormozi-closer |
+| Churn & Retention | churn, retention, cancel, LTV, keep customers | hormozi-retention / hormozi-scale |
+| Business Scaling | scale, grow, $1M, $10M, $100M, expand, hire | hormozi-scale / hormozi-models |
+| Business Model | business model, recurring revenue, subscription, SaaS | hormozi-models / hormozi-scale |
+| Business Audit | audit, evaluate, diagnose, bottleneck, problems | hormozi-audit / hormozi-models |
+| General Strategy | strategy, advice, direction, next step, mentor | hormozi-advisor / hormozi-chief |
+
+**Scoring rules:**
+- Count keyword matches per domain
+- 2+ matches above others --> route to that domain's primary specialist
+- Tie or cross-domain --> Hormozi Chief answers using Value Equation lens
+- No clear match --> ask about business stage and primary bottleneck
+
+### Phase 3a: Cross-Cutting Answer
+
+If request is general or cross-domain:
+- Apply the Value Equation to diagnose the core issue
+- Identify which lever (Dream Outcome, Likelihood, Time Delay, Effort) needs work
+- Reference which specialists could go deeper
+
+### Phase 3b: Domain-Specific Route
+
+If request maps clearly to a domain:
+1. **Quick answer first** (3-5 lines minimum + Hormozi framework reference)
+2. **Route:** Name the specialist, explain their unique value, provide activation command
+   - Example: "Your offer needs the Grand Slam framework. Activate with `@hormozi-squad:hormozi-offers`"
+
+### Phase 4: Confidence Assessment
+
+| Confidence | Criteria | Action |
+|------------|----------|--------|
+| HIGH | 3+ keyword matches in one domain | Route with confidence to primary specialist |
+| MEDIUM | 1-2 matches or split across 2 domains | Answer + suggest 2 specialists |
+| LOW | No clear match or vague request | Answer with Value Equation, ask clarifying question |
+
+---
+
+## Output Format
+
+```markdown
+## Diagnosis
+**Category:** {domain | cross-cutting}
+**Confidence:** {HIGH | MEDIUM | LOW}
+**Specialist:** {Name} ({agent-id}) | Direct Answer
+
+### Quick Answer
+{3-10 line answer using Hormozi frameworks}
+
+### Recommended Next Step
+{Route instruction with activation command, or follow-up question}
+```
+
+---
+
+## Veto Conditions
+
+- NEVER route without providing a quick answer first
+- NEVER route when confidence is LOW — answer using Value Equation and ask clarifying questions
+- NEVER load a specialist agent file during diagnosis
+- NEVER guess the business stage — ask if unclear
+- NEVER give generic advice without referencing a specific Hormozi framework
+
+---
+
+## Completion Criteria
+
+- [ ] Request parsed and keywords extracted
+- [ ] Business challenge type identified
+- [ ] Routing catalog consulted with scored results
+- [ ] Quick answer provided with Hormozi framework reference
+- [ ] Specialist routing provided (if domain-specific)
+- [ ] Confidence level stated