invos 1.0.0

package/kit/.agents/squads/hormozi-squad/tasks/generate-leads.md

@@ -0,0 +1,187 @@
+---
+task: generateLeads()
+responsavel: "@hormozi-leads"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: business
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+  - campo: audience
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+
+Saida:
+  - campo: leadGenerationSystem
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] All 4 lead sources audited and scored"
+  - "[ ] Lead magnet designed with clear bridge to core offer"
+  - "[ ] 30-Day launch plan created"
+---
+
+# Task: Generate Leads
+
+**Task ID:** HORMOZI-002
+**Version:** 1.0.0
+**Command:** `*generate-leads`
+**Agent:** Hormozi Leads (hormozi-leads)
+**Purpose:** Design a lead generation system using the $100M Leads framework.
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| business | string | User prompt | Yes | Business type, product/service, and current stage |
+| audience | string | User prompt | Yes | Dream customer avatar with demographics |
+| budget | string | User prompt | No | Monthly marketing budget range |
+| current_channels | list | User prompt | No | Existing lead sources |
+| lead_goal | number | User prompt | No | Target leads per month |
+| business_model | string | User prompt | No | B2B, B2C, local, e-commerce, SaaS, service |
+
+---
+
+## Preconditions
+
+- Business type and offer defined
+- Target audience identified with enough specificity to find them
+
+---
+
+## Execution Phases
+
+### Phase 1: Lead Source Audit
+1. Evaluate the 4 core lead sources (Hormozi framework):
+   - Warm Outreach: Existing contacts, past customers, referrals
+   - Cold Outreach: Direct outreach to strangers (email, DM, phone)
+   - Content (Free): Organic content that attracts leads over time
+   - Paid Ads: Paid media that buys leads immediately
+2. Score each source on current effectiveness (1-10)
+3. Identify the biggest gap — which source is underused?
+4. Map each source to the business model and budget
+
+### Phase 2: Lead Magnet Design
+1. Create a lead magnet using the Hormozi criteria:
+   - Solves a specific, narrow problem completely
+   - Delivers value in under 5 minutes of consumption
+   - Naturally leads to the core offer as the next step
+   - Has a compelling, specific name
+2. Choose the lead magnet type:
+   - Free trial / sample
+   - Checklist / cheat sheet
+   - Free tool / calculator
+   - Free training / workshop
+   - Assessment / quiz
+   - Template / swipe file
+3. Name the lead magnet with a result-oriented title
+4. Define the delivery mechanism
+
+### Phase 3: Channel Strategy
+1. For each active or recommended channel, define:
+   - Target volume (leads per week)
+   - Cost per lead estimate
+   - Message/content type
+   - Frequency and cadence
+2. Warm Outreach plan:
+   - List building strategy (who to contact first)
+   - Message templates (ACA framework: Acknowledge, Compliment, Ask)
+   - Follow-up sequence
+3. Cold Outreach plan:
+   - List sourcing method
+   - Offer framing for cold contacts
+   - Personalization approach
+   - Volume targets and conversion expectations
+4. Content plan:
+   - Platform selection (where the audience already is)
+   - Content pillars tied to the core offer
+   - Posting cadence and content types
+   - Call-to-action strategy
+5. Paid Ads plan:
+   - Platform recommendation
+   - Budget allocation
+   - Creative direction
+   - Lead capture mechanism
+
+### Phase 4: System Assembly
+1. Map the complete lead flow: Source → Lead Magnet → Nurture → Offer
+2. Define the follow-up system for each source
+3. Set KPIs for each channel
+4. Create a 30-day launch plan with weekly milestones
+5. Define the scaling triggers (when to increase spend/effort)
+
+---
+
+## Output Format
+
+```markdown
+## Lead Generation System: {Business Name}
+
+**Business Model:** {model}
+**Lead Goal:** {X}/month
+**Budget:** ${range}/month
+**Primary Channel:** {recommended}
+
+---
+
+### Lead Source Scorecard
+
+| Source | Current Score | Opportunity | Priority |
+|--------|-------------|-------------|----------|
+| Warm Outreach | X/10 | {gap} | {1-4} |
+| Cold Outreach | X/10 | {gap} | {1-4} |
+| Content (Free) | X/10 | {gap} | {1-4} |
+| Paid Ads | X/10 | {gap} | {1-4} |
+
+### Lead Magnet
+**Name:** {name}
+**Type:** {type}
+**Problem Solved:** {specific problem}
+**Delivery:** {method}
+**Bridge to Offer:** {how it leads to the paid product}
+
+### Channel Plans
+{Detailed plan per channel}
+
+### Lead Flow Map
+{Source} → {Lead Magnet} → {Nurture} → {Offer}
+
+### 30-Day Launch Plan
+
+| Week | Actions | Target Leads | KPI |
+|------|---------|-------------|-----|
+
+### Scaling Triggers
+| Metric | Threshold | Action |
+|--------|-----------|--------|
+```
+
+---
+
+## Veto Conditions
+
+- NEVER recommend paid ads as the only channel for a business with no budget
+- NEVER skip the lead magnet — direct-to-offer works only for most-aware audiences
+- NEVER recommend channels where the audience does not exist
+- NEVER set lead goals without defining cost per lead expectations
+- NEVER build a system without a follow-up mechanism
+
+---
+
+## Completion Criteria
+
+- [ ] All 4 lead sources audited and scored
+- [ ] Lead magnet designed with clear bridge to core offer
+- [ ] Channel plans defined with volume targets
+- [ ] Lead flow mapped end-to-end
+- [ ] 30-Day launch plan created
+- [ ] Scaling triggers defined
+- [ ] KPIs set for each channel

package/kit/.agents/squads/hormozi-squad/tasks/plan-launch.md

@@ -0,0 +1,179 @@
+---
+task: planLaunch()
+responsavel: "@hormozi-launch"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: product
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+  - campo: offer
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+
+Saida:
+  - campo: launchPlan
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] Launch model selected with rationale"
+  - "[ ] Timeline mapped with all phases"
+  - "[ ] Revenue model calculated with scenarios"
+---
+
+# Task: Plan Launch
+
+**Task ID:** HORMOZI-006
+**Version:** 1.0.0
+**Command:** `*plan-launch`
+**Agent:** Hormozi Launch (hormozi-launch)
+**Purpose:** Design a product launch strategy that maximizes revenue in a compressed timeframe.
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| product | string | User prompt | Yes | Product being launched |
+| offer | object | User prompt | Yes | Complete offer (price, bonuses, guarantee) |
+| audience_size | number | User prompt | Yes | Total reachable audience (email list, followers, etc.) |
+| launch_type | enum | User prompt | No | seed, internal, partnership, paid — defaults to internal |
+| timeline | string | User prompt | No | Desired launch date or window |
+| budget | number | User prompt | No | Available launch budget |
+
+---
+
+## Preconditions
+
+- Offer fully designed (ideally via create-offer.md)
+- Audience exists to launch to (list, following, community, or ad budget)
+- Product ready or will be ready by launch date
+
+---
+
+## Execution Phases
+
+### Phase 1: Launch Architecture
+1. Select the launch model:
+   - Seed Launch: Small audience, test offer, collect testimonials
+   - Internal Launch: Email list and existing audience
+   - Partnership Launch: Affiliates and JV partners
+   - Paid Launch: Ad-driven with retargeting sequences
+2. Define the launch timeline:
+   - Pre-launch: 7-14 days of warming and anticipation
+   - Launch: 3-7 day cart-open window
+   - Post-launch: 3-5 days of follow-up and onboarding
+3. Set the revenue target based on audience size and expected conversion
+4. Calculate required traffic and conversion rates backward from revenue target
+
+### Phase 2: Pre-Launch Sequence
+1. Design the pre-launch content (value-first, builds anticipation):
+   - Day 1-3: Problem awareness content
+   - Day 4-7: Solution education content
+   - Day 8-10: Proof and social proof content
+   - Day 11-14: Anticipation and waitlist building
+2. Create the pre-launch email sequence
+3. Design the social media content calendar
+4. Build the waitlist or early-bird mechanism
+5. Create the "launch story" narrative arc
+
+### Phase 3: Launch Execution Plan
+1. Cart Open day plan:
+   - Email sequence (open announcement + 2 follow-ups)
+   - Social media posts (announcement + behind-the-scenes)
+   - Sales page live checklist
+2. Mid-cart plan:
+   - Case study or testimonial email
+   - FAQ addressing top objections
+   - Bonus reminder
+3. Cart Close plan:
+   - 48-hour warning email
+   - 24-hour warning email
+   - Final hours email (3-hour, 1-hour, closing)
+   - Urgency escalation on social
+4. Define the scarcity mechanism (quantity, time, bonus expiry)
+
+### Phase 4: Post-Launch
+1. Thank you and onboarding plan for buyers
+2. "Door closed" messaging for non-buyers
+3. Results collection strategy (for future launches)
+4. Debrief metrics: revenue, conversion rate, email performance
+5. Evergreen transition plan (if applicable)
+
+---
+
+## Output Format
+
+```markdown
+## Launch Plan: {Product Name}
+
+**Launch Type:** {type}
+**Timeline:** {dates}
+**Revenue Target:** ${X}
+**Audience Size:** {N}
+**Required Conversion Rate:** {X}%
+
+---
+
+### Launch Calendar
+
+| Phase | Days | Key Actions |
+|-------|------|-------------|
+| Pre-Launch | Day 1-14 | {summary} |
+| Cart Open | Day 15-17 | {summary} |
+| Mid-Cart | Day 18-19 | {summary} |
+| Cart Close | Day 20-21 | {summary} |
+| Post-Launch | Day 22-26 | {summary} |
+
+### Pre-Launch Content Plan
+| Day | Content | Channel | Goal |
+|-----|---------|---------|------|
+
+### Email Sequence
+| Day | Email | Subject Line | Purpose |
+|-----|-------|-------------|---------|
+
+### Cart Open Checklist
+- [ ] {item}
+
+### Revenue Model
+
+| Metric | Target | Conservative | Aggressive |
+|--------|--------|-------------|------------|
+| Traffic | {N} | {N} | {N} |
+| Conversion | {X}% | {X}% | {X}% |
+| Revenue | ${X} | ${X} | ${X} |
+
+### Post-Launch Plan
+{Onboarding, follow-up, and evergreen transition}
+```
+
+---
+
+## Veto Conditions
+
+- NEVER launch without a pre-launch sequence — cold launches underperform
+- NEVER run an open-ended launch — cart must close to create urgency
+- NEVER launch without a follow-up plan for non-buyers
+- NEVER skip the revenue model — launching without targets is guessing
+- NEVER promise results you cannot demonstrate with proof
+
+---
+
+## Completion Criteria
+
+- [ ] Launch model selected with rationale
+- [ ] Timeline mapped with all phases
+- [ ] Pre-launch content plan created
+- [ ] Email sequence outlined for all phases
+- [ ] Cart open/mid/close execution plans defined
+- [ ] Revenue model calculated with scenarios
+- [ ] Post-launch plan included
+- [ ] Scarcity mechanism defined

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

@@ -0,0 +1,133 @@
+---
+task: reviewBusinessScalingOutput()
+responsavel: "@hormozi-chief"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: specialist_output
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+  - campo: original_request
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+
+Saida:
+  - campo: reviewReport
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] All checklist items evaluated"
+  - "[ ] Verdict rendered (APPROVE/REVISE/REJECT)"
+  - "[ ] Value equation and revenue math individually assessed"
+---
+
+# Task: Review Business Scaling Output
+
+**Task ID:** HORMOZI-CHIEF-002
+**Version:** 1.0.0
+**Command:** `*review`
+**Orchestrator:** Hormozi Chief (hormozi-chief)
+**Purpose:** Review specialist output against quality checklist, score, and approve or request revision.
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| specialist_output | string | Specialist agent | Yes | Non-empty deliverable |
+| original_request | string | User prompt | Yes | The original request that triggered the work |
+| specialist_id | string | Routing | Yes | Agent ID that produced the output |
+
+---
+
+## Preconditions
+
+- Specialist has completed their task and produced output
+- Output quality checklist is available at checklists/output-quality.md
+
+---
+
+## 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 business model, revenue stage, and scaling constraint
+5. Determine the Hormozi framework being applied (value equation, offer creation, lead gen, etc.)
+
+### Phase 2: Apply Quality Checklist
+
+1. Load checklists/output-quality.md
+2. Evaluate each item against the specialist output
+3. Mark each item: [x] Pass, [ ] Fail, [N/A] Not Applicable
+4. Count CRITICAL failures and total failures
+5. Pay special attention to: value equation clarity, offer irresistibility, and revenue math
+
+### Phase 3: Score and Decide
+
+| Score | Verdict | Action |
+|-------|---------|--------|
+| All CRITICAL pass, < 2 non-critical fail | APPROVE | Deliver to user |
+| All CRITICAL pass, 2+ non-critical fail | REVISE | Return to specialist with specific feedback |
+| Any CRITICAL fail | REJECT | Return to specialist, block delivery |
+
+### Phase 4: Output
+
+Produce review report with verdict, score, and feedback.
+
+---
+
+## Output Format
+
+```markdown
+## Review Report
+
+**Specialist:** {name} ({id})
+**Verdict:** {APPROVE | REVISE | REJECT}
+**Score:** {X}/{total} items passed
+
+### Passed
+- {items that passed}
+
+### Issues Found
+- [{CRITICAL|WARN}] {description} — {recommendation}
+
+### Scaling-Specific Notes
+- Value equation strength: {assessment}
+- Revenue impact estimate: {assessment}
+- Implementation feasibility: {assessment}
+
+### Recommendation
+{Next step: deliver / revise specific items / redo}
+```
+
+---
+
+## Veto Conditions
+
+- NEVER approve output with CRITICAL failures
+- NEVER reject without providing specific, actionable feedback
+- NEVER modify the specialist's output — only review and provide feedback
+- NEVER approve strategies without clear revenue math or unit economics
+- NEVER approve vague "grow your business" advice without concrete levers
+
+---
+
+## Completion Criteria
+
+- [ ] Original request re-read and understood
+- [ ] Business model and revenue stage identified
+- [ ] All checklist items evaluated
+- [ ] Score calculated
+- [ ] Verdict rendered (APPROVE/REVISE/REJECT)
+- [ ] Specific feedback provided for any failures
+- [ ] Value equation and revenue math individually assessed

package/kit/.agents/squads/hormozi-squad/tasks/set-pricing.md

@@ -0,0 +1,167 @@
+---
+task: setPricing()
+responsavel: "@hormozi-pricing"
+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: pricingStrategy
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] Value delivered calculated with financial and emotional dimensions"
+  - "[ ] Pricing model selected with rationale"
+  - "[ ] Testing plan defined"
+---
+
+# Task: Set Pricing Strategy
+
+**Task ID:** HORMOZI-003
+**Version:** 1.0.0
+**Command:** `*set-pricing`
+**Agent:** Hormozi Pricing (hormozi-pricing)
+**Purpose:** Design a value-based pricing strategy that maximizes revenue without competing on price.
+
+---
+
+## Inputs
+
+| Field | Type | Source | Required | Validation |
+|-------|------|--------|----------|------------|
+| product | string | User prompt | Yes | Product or service to price |
+| audience | string | User prompt | Yes | Target customer with willingness-to-pay context |
+| current_price | number | User prompt | No | Existing price if applicable |
+| cost_structure | object | User prompt | No | Cost to deliver (COGS, fulfillment, etc.) |
+| competitor_prices | list | User prompt | No | Market pricing references |
+| business_model | string | User prompt | No | One-time, subscription, tiered, usage-based |
+| revenue_target | number | User prompt | No | Target monthly/annual revenue |
+
+---
+
+## Preconditions
+
+- Product or service defined with clear value delivery
+- Offer structure completed (ideally via create-offer.md first)
+
+---
+
+## Execution Phases
+
+### Phase 1: Value Assessment
+1. Calculate the ROI the customer receives from the product
+2. Apply the 10x Rule: price should be 1/10 of the value delivered minimum
+3. Determine the "cost of inaction" — what does NOT buying cost them?
+4. Identify comparable investments the customer already makes
+5. Assess the emotional value beyond financial ROI
+
+### Phase 2: Pricing Architecture
+1. Choose the pricing model:
+   - Premium (high price, high touch, fewer customers)
+   - Volume (lower price, systems-based, many customers)
+   - Hybrid (tiered with entry and premium levels)
+2. Set the anchor price (the "should be" number based on value)
+3. Set the actual price as a fraction of the anchor
+4. Design payment options:
+   - Pay-in-full with discount incentive
+   - Payment plan with premium for convenience
+   - Subscription with lock-in benefits
+5. Create pricing tiers if applicable:
+   - Good: Core offer only
+   - Better: Core + speed bonuses
+   - Best: Core + all bonuses + premium access
+
+### Phase 3: Price Justification
+1. Build the price-to-value narrative
+2. Calculate the daily/weekly cost breakdown ("less than a coffee per day")
+3. Create the comparison stack (what else costs this much but delivers less)
+4. Define the ROI timeline — when does the investment pay for itself?
+5. Write the pricing section copy for sales materials
+
+### Phase 4: Pricing Optimization
+1. Set the initial test price
+2. Define the price testing methodology:
+   - Test at 2x current price first (most businesses underprice)
+   - Monitor conversion rate AND revenue (not just conversion)
+   - Revenue per lead matters more than conversion rate
+3. Define price increase triggers
+4. Plan the annual price increase strategy
+
+---
+
+## Output Format
+
+```markdown
+## Pricing Strategy: {Product Name}
+
+**Model:** {premium / volume / hybrid}
+**Price:** ${price}
+**Value Delivered:** ${value}
+**Value-to-Price Ratio:** {X}:1
+**Cost of Inaction:** ${cost}/year
+
+---
+
+### Value Assessment
+
+| Dimension | Value | Rationale |
+|-----------|-------|-----------|
+| Financial ROI | ${X} | {calculation} |
+| Time Saved | {hours} | {at $X/hour = $Y} |
+| Emotional Value | {qualitative} | {description} |
+| Cost of Inaction | ${X}/year | {what they lose by not buying} |
+
+### Pricing Tiers
+
+| Tier | Includes | Price | Target Customer |
+|------|----------|-------|----------------|
+
+### Payment Options
+
+| Option | Price | Terms | Incentive |
+|--------|-------|-------|-----------|
+
+### Price Justification Narrative
+{Ready-to-use copy for sales materials}
+
+### Testing Plan
+| Phase | Price | Duration | Success Metric |
+|-------|-------|----------|----------------|
+
+### Price Increase Strategy
+{Annual increase plan with triggers}
+```
+
+---
+
+## Veto Conditions
+
+- NEVER price based solely on competitor pricing — that is a race to the bottom
+- NEVER lower price to increase sales without first testing at higher prices
+- NEVER offer discounts without a strategic reason (urgency, loyalty, volume)
+- NEVER price below 10x of delivery cost — margins must support growth
+- NEVER set price without calculating the value delivered first
+
+---
+
+## Completion Criteria
+
+- [ ] Value delivered calculated with financial and emotional dimensions
+- [ ] 10x Rule applied and validated
+- [ ] Pricing model selected with rationale
+- [ ] Tiers and payment options designed
+- [ ] Price justification narrative written
+- [ ] Testing plan defined
+- [ ] Price increase strategy documented