sinapse-ai 1.0.0

package/sinapse/tasks/compose-multi-squad-plan.md

@@ -0,0 +1,175 @@
+---
+task: compose-multi-squad-plan
+responsavel: "@sinapse-master"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: initiative
+    tipo: string
+    origem: "user input ou strategic-brief"
+    obrigatorio: true
+
+Saida:
+  - campo: execution_plan
+    tipo: document
+    destino: "coordinate-cross-squad task"
+
+Checklist:
+  - "[ ] Objetivo decomposto em work packages"
+  - "[ ] Squads atribuidas a cada package"
+  - "[ ] Sequencia definida (paralelo/serial)"
+  - "[ ] Handoffs entre fases especificados"
+  - "[ ] Lead squad designada"
+---
+
+# Task: Compose Multi-Squad Execution Plan
+
+## Metadata
+- **Squad:** squad-sinapse
+- **Agent:** Imperator (sinapse-master)
+- **Complexity:** Advanced
+
+## Objetivo
+Desenhar um plano de execucao detalhado para iniciativas que exigem 2+ squads trabalhando coordenadamente. O plano define work packages, atribuicoes, sequencia, handoffs e metricas de sucesso.
+
+## Entrada
+- Initiative description (o que o usuario quer alcançar)
+- Strategic brief (se ja existe, do task `strategic-brief`)
+- Constraints (timeline, budget, prioridades)
+- Current assets (o que ja existe)
+
+## Passos
+
+### 1. Initiative Decomposition
+
+Quebrar a iniciativa em work packages independentes:
+
+```
+INITIATIVE DECOMPOSITION
+========================
+Initiative: {nome}
+Objective: {objetivo final}
+
+WORK PACKAGES:
+WP-1: {nome}
+  Domain: {dominio}
+  Squad: squad-{x}
+  Orchestrator: {name} ({codename})
+  Invocation: /{prefix}:agents:{orchestrator-id}
+  Deliverables: {lista}
+  Estimated Effort: {Small/Medium/Large}
+
+WP-2: {nome}
+  Domain: {dominio}
+  Squad: squad-{y}
+  Orchestrator: {name} ({codename})
+  Invocation: /{prefix}:agents:{orchestrator-id}
+  Deliverables: {lista}
+  Estimated Effort: {Small/Medium/Large}
+  Depends On: WP-1
+
+WP-N: ...
+```
+
+### 2. Dependency Graph
+
+Mapear dependencias entre work packages:
+
+```
+DEPENDENCY GRAPH:
+
+WP-1 (brand-system) ──→ WP-3 (digital-experience)
+         │                        │
+         └──→ WP-2 (copywriting) ─┘──→ WP-5 (growth-analytics)
+                                       │
+WP-4 (content) ──────────────────────→─┘
+
+Legend: ──→ = "must complete before"
+Parallel: WP-1 and WP-4 can run simultaneously
+Serial: WP-3 waits for WP-1 + WP-2
+```
+
+### 3. Phase Design
+
+Agrupar WPs em fases executaveis:
+
+```
+EXECUTION PHASES:
+
+PHASE 1 — FOUNDATION
+  Timeline: {estimado}
+  Parallel Execution:
+    - WP-1: squad-brand / Meridian
+      → /brand:agents:brand-orchestrator
+    - WP-4: squad-content / content-orchestrator
+      → /content:agents:content-orchestrator
+  Gate: Both WPs complete → proceed to Phase 2
+
+PHASE 2 — BUILD
+  Timeline: {estimado}
+  Parallel Execution:
+    - WP-2: squad-copy / Quill
+      → /copywriting:agents:copy-strategist
+      Inputs from: WP-1 (brand voice, tone)
+    - WP-3: squad-design / Nexus
+      → /digital-experience:agents:dx-orchestrator
+      Inputs from: WP-1 (design tokens, visual identity)
+  Gate: Both WPs complete → proceed to Phase 3
+
+PHASE 3 — LAUNCH
+  Timeline: {estimado}
+  Sequential:
+    - WP-5: squad-growth / Catalyst
+      → /growth:agents:ga-orchestrator
+      Inputs from: WP-2 (content), WP-3 (pages), WP-4 (editorial)
+  Gate: Launch metrics defined → GO
+
+LEAD SQUAD FOR SYNTHESIS: squad-{x} / {orchestrator}
+```
+
+### 4. Handoff Specifications
+
+Para cada transicao entre fases:
+
+| From WP | To WP | Handoff Content | Format |
+|---------|-------|----------------|--------|
+| WP-1 | WP-2 | Brand voice, tone of voice, DO/DON'Ts | Markdown doc |
+| WP-1 | WP-3 | Design tokens, color palette, typography | JSON tokens + guidelines |
+| WP-2 | WP-5 | Web copy, meta descriptions, CTAs | Markdown docs |
+| WP-3 | WP-5 | Page templates, sitemap, technical specs | Figma + HTML |
+
+### 5. Risk & Contingency
+
+| Risk | Impact | Contingency |
+|------|--------|------------|
+| WP-1 delays → all downstream blocks | High | Start WP-4 early (independent) |
+| Quality rejection at gate | Medium | 1 revision cycle built into timeline |
+| Squad unavailable | Low | Imperator handles directly or substitutes |
+
+### 6. Success Criteria
+
+| Phase | Success Criteria | Measured By |
+|-------|-----------------|-------------|
+| Phase 1 | Brand foundation approved | brand-system quality gate |
+| Phase 2 | Copy + Design aligned with brand | cross-review between squads |
+| Phase 3 | Launch metrics on track | growth-analytics dashboard |
+| Overall | {business KPI} | {measurement method} |
+
+## Saida
+- Multi-squad execution plan document
+- Dependency graph
+- Phase-by-phase breakdown with invocation commands
+- Handoff specifications
+- Risk contingency table
+- Success criteria
+
+## Validacao
+- [ ] Todos os work packages tem squad e orchestrator atribuidos
+- [ ] Dependencias entre WPs estao mapeadas
+- [ ] Fases respeitam dependencias (nada executa antes do que depende)
+- [ ] Handoffs entre fases tem conteudo e formato especificados
+- [ ] Lead squad para sintese final designada
+- [ ] Invocation commands corretos para cada squad
+- [ ] Riscos identificados com contingencias

package/sinapse/tasks/coordinate-cross-squad.md

@@ -0,0 +1,151 @@
+---
+task: coordinate-cross-squad
+responsavel: "@sinapse-master"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: multi_squad_plan
+    tipo: object
+    origem: "compose-multi-squad-plan ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: coordination_log
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Plano multi-squad definido"
+  - "[ ] Sequencia de execucao clara"
+  - "[ ] Handoffs estruturados entre squads"
+  - "[ ] Progresso monitorado"
+  - "[ ] Resultado final sintetizado"
+---
+
+# Task: Coordinate Cross-Squad Workflow
+
+## Metadata
+- **Squad:** squad-sinapse
+- **Agent:** Imperator (sinapse-master)
+- **Complexity:** Advanced
+
+## Objetivo
+Orquestrar workflows que envolvem 2 ou mais squads trabalhando juntas, garantindo handoffs estruturados, execucao sequencial/paralela correta, e sintese final coerente.
+
+## Entrada
+- Multi-squad execution plan (from `compose-multi-squad-plan`)
+- User's business objective
+- Timeline and constraints
+- Current state of each squad's deliverables (if any)
+
+## Passos
+
+### 1. Execution Plan Review
+
+Validar o plano antes de iniciar:
+
+```
+CROSS-SQUAD EXECUTION PLAN
+===========================
+Initiative: {nome}
+Objective: {objetivo do usuario}
+Squads Involved: {lista}
+Lead Squad: {quem faz a sintese final}
+Timeline: {estimado}
+
+PHASES:
+Phase 1: {nome}
+  Lead: squad-{x} / {orchestrator}
+  Parallel: [squad-{y}, squad-{z}]
+  Dependencies: none
+  Expected Output: {deliverable}
+
+Phase 2: {nome}
+  Lead: squad-{a} / {orchestrator}
+  Dependencies: Phase 1 outputs
+  Handoff Required: {what context passes}
+  Expected Output: {deliverable}
+
+Phase N: {nome} — SYNTHESIS
+  Lead: {lead squad}
+  Inputs: All previous phase outputs
+  Expected Output: {final deliverable}
+```
+
+### 2. Phase Kickoff
+
+Para cada fase:
+- Ativar o(s) squad orchestrator(s) da fase com contexto completo
+- Fornecer invocation commands ao usuario
+- Especificar o que cada squad deve entregar
+- Se paralelo: iniciar todos simultaneamente
+- Se serial: aguardar fase anterior completar
+
+### 3. Handoff Management
+
+Quando uma fase termina e a proxima depende dela:
+
+```
+HANDOFF ARTIFACT
+================
+From: squad-{sender} / {agent}
+To: squad-{receiver} / {agent}
+Phase: {N} → {N+1}
+
+Deliverables Passed:
+- {deliverable 1}: {descricao + localizacao}
+- {deliverable 2}: {descricao + localizacao}
+
+Key Decisions Made:
+- {decisao 1}
+- {decisao 2}
+
+Constraints for Next Phase:
+- {restricao 1}
+- {restricao 2}
+
+Invocation: /{prefix}:agents:{orchestrator-id}
+Context: {resumo do que a squad receptora precisa saber}
+```
+
+### 4. Progress Tracking
+
+Manter status atualizado:
+
+| Phase | Squad | Status | Deliverable | Notes |
+|-------|-------|--------|-------------|-------|
+| 1 | brand-system | Done | Brand guidelines | Approved |
+| 2a | digital-experience | In Progress | Wireframes | 60% |
+| 2b | copywriting-persuasion | In Progress | Web copy | Draft ready |
+| 3 | creative-animations | Waiting | Page animations | Depends on 2a |
+
+### 5. Blocker Resolution
+
+Se uma squad reportar blocker:
+- Identificar se e intra-squad ou inter-squad
+- Se intra: delegar ao squad orchestrator resolver
+- Se inter: mediar entre os squad orchestrators
+- Se nao resolvivel: escalar ou adaptar o plano
+
+### 6. Final Synthesis
+
+Quando todas as fases completam:
+- Coletar outputs de todas as squads
+- Verificar coerencia entre deliverables
+- Gerar resumo executivo para o usuario
+- Destacar pontos de atencao ou gaps
+
+## Saida
+- Coordination log com status de cada fase
+- Handoff artifacts entre fases
+- Final synthesis document
+- Lessons learned (para futuras coordenacoes similares)
+
+## Validacao
+- [ ] Todas as fases executadas na ordem correta
+- [ ] Handoffs entre squads estruturados e completos
+- [ ] Nenhum blocker inter-squad pendente
+- [ ] Deliverables finais coerentes entre si
+- [ ] Usuario recebeu resultado unificado

package/sinapse/tasks/diagnose-and-route.md

@@ -0,0 +1,126 @@
+---
+task: diagnose-and-route
+responsavel: "@sinapse-master"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: user_request
+    tipo: string
+    origem: "user input"
+    obrigatorio: true
+
+Saida:
+  - campo: routing_decision
+    tipo: document
+    destino: "squad orchestrator"
+
+Checklist:
+  - "[ ] Analisar request do usuario"
+  - "[ ] Classificar dominio(s) envolvido(s)"
+  - "[ ] Resolver ambiguidades"
+  - "[ ] Gerar routing decision com invocation command"
+---
+
+# Task: Diagnose and Route
+
+## Metadata
+- **Squad:** squad-sinapse
+- **Agent:** Imperator (sinapse-master)
+- **Complexity:** Standard
+
+## Objetivo
+Analisar qualquer request do usuario, identificar qual(is) squad(s) deve(m) tratar, e rotear com contexto estruturado. Esta e a task mais executada do Imperator — todo pedido passa por aqui primeiro.
+
+## Entrada
+- User request (texto livre)
+- Optional: context about current project or ongoing work
+
+## Passos
+
+### 1. Request Analysis
+Extrair do pedido:
+- **Intent:** O que o usuario quer alcançar?
+- **Domain signals:** Quais palavras-chave indicam o dominio?
+- **Complexity:** Single-squad ou multi-squad?
+- **Urgency:** Implied timeline?
+
+### 2. Domain Classification
+
+Mapear contra a routing table:
+
+| Dominio | Squad | Prefix | Orchestrator | Invocacao |
+|---------|-------|--------|-------------|-----------|
+| Branding/identidade | brand-system | brand | Meridian | `/brand:agents:brand-orchestrator` |
+| Vendas/CRM/pipeline | commercial-systems | commercial | Pipeline | `/commercial:agents:cs-orchestrator` |
+| Conteudo/editorial | content-intelligence | content | content-orchestrator | `/content:agents:content-orchestrator` |
+| Copywriting/persuasao | copywriting-persuasion | copywriting | Quill | `/copywriting:agents:copy-strategist` |
+| Animacoes/Three.js | creative-animations | ca | Kinetic | `/ca:agents:ca-orchestrator` |
+| UX/UI/experiencia | digital-experience | digital-experience | Nexus | `/digital-experience:agents:dx-orchestrator` |
+| Financeiro/pricing | financial-intelligence | finance | Ledger | `/finance:agents:fi-orchestrator` |
+| Growth/SEO/analytics | growth-analytics | growth | Catalyst | `/growth:agents:ga-orchestrator` |
+| Midia paga/ads | paid-media | pm | Apex | `/pm:agents:pm-orchestrator` |
+| Produto/discovery | product-systems | product | Vector | `/product:agents:ps-orchestrator` |
+| Pesquisa/competitivo | research-intelligence | research | Prism | `/research:agents:research-orchestrator` |
+| Claude Code/prompts | claude-mastery | claude | Orion | `/claude:agents:cm-orchestrator` |
+| Estrategia/advisory | strategic-council | council | Zenith | `/council:agents:council-orchestrator` |
+| Narrativa/pitch | narrative-masters | narrative | Arc | `/narrative:agents:narrative-orchestrator` |
+| Seguranca/compliance | cyber-defense | cyber | Fortress | `/cyber:agents:cyber-orchestrator` |
+
+### 3. Ambiguity Resolution
+
+Se o dominio nao e claro, aplicar regras de desambiguacao:
+
+| Sinal Ambiguo | Pergunta Clarificadora |
+|---------------|----------------------|
+| "Copy para ads" | "Voce precisa escrever o texto do anuncio (copywriting) ou gerenciar a campanha de midia paga (paid-media)?" |
+| "Design system" | "E para a marca (brand-system) ou para o produto digital (digital-experience)?" |
+| "Metricas" | "Metricas de growth organico, midia paga, ou financeiras?" |
+| "Pesquisa" | "Pesquisa de mercado/competitiva (research) ou pesquisa com usuarios (product/UX)?" |
+| "Pricing" | "Modelagem de precos/oferta (commercial) ou analise financeira de pricing (finance)?" |
+| "Storytelling" | "Historia da marca (brand), pitch/apresentacao (narrative), ou conteudo (content)?" |
+
+**Regra:** No maximo 1 pergunta clarificadora. Se 2+ dominios sao igualmente provaveis, apresentar ambos e deixar o usuario escolher.
+
+### 4. Routing Decision
+
+Gerar output estruturado:
+
+```
+ROUTING DECISION
+================
+Request: {resumo do pedido}
+Domain: {dominio primario}
+Squad: squad-{name}
+Orchestrator: {name} ({codename})
+Invocation: /{prefix}:agents:{orchestrator-id}
+
+Context for Squad:
+- Objective: {o que o usuario quer}
+- Constraints: {restricoes mencionadas}
+- Expected Output: {tipo de entrega esperada}
+
+Confidence: High / Medium / Low
+Rationale: {por que esta squad}
+```
+
+### 5. Multi-Squad Detection
+
+Se 2+ squads sao necessarias:
+- Listar todas as squads envolvidas
+- Indicar que a task `compose-multi-squad-plan` deve ser executada
+- Nao rotear para squad individual ate o plano estar pronto
+
+## Saida
+- Routing decision document
+- Invocation command para o usuario
+- Context summary para o squad orchestrator
+- Flag se multi-squad plan e necessario
+
+## Validacao
+- [ ] Request analisado com intent claro
+- [ ] Squad identificada com confianca >= Medium
+- [ ] Invocation command fornecido
+- [ ] Context para squad structurado
+- [ ] Ambiguidades resolvidas (ou pergunta feita)

package/sinapse/tasks/onboard-user.md

@@ -0,0 +1,145 @@
+---
+task: onboard-user
+responsavel: "@sinapse-master"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: user_context
+    tipo: object
+    origem: "user input"
+    obrigatorio: false
+
+Saida:
+  - campo: onboarding_guide
+    tipo: document
+    destino: "user"
+
+Checklist:
+  - "[ ] Entender o perfil do usuario"
+  - "[ ] Apresentar o ecossistema"
+  - "[ ] Recomendar squads relevantes"
+  - "[ ] Fornecer quick-start commands"
+---
+
+# Task: Onboard User
+
+## Metadata
+- **Squad:** squad-sinapse
+- **Agent:** Imperator (sinapse-master)
+- **Complexity:** Simple
+
+## Objetivo
+Guiar um novo usuario pelo ecossistema Sinapse, ajudando-o a entender o que esta disponivel, qual squad e mais relevante para suas necessidades, e como comecar a usar.
+
+## Entrada
+- User background (opcional): tipo de negocio, industria, goals
+- Focus area (opcional): se o usuario ja sabe o dominio de interesse
+
+## Passos
+
+### 1. Welcome & Discovery
+
+Se o usuario nao forneceu contexto:
+
+```
+BEM-VINDO AO IMORI SQUADS
+==========================
+
+Eu sou o Imperator, o Imori Master. Coordeno 15 squads especializadas com
+127+ agentes de IA e 965+ tasks prontas para usar.
+
+Para te direcionar ao melhor especialista, preciso entender:
+
+1. Qual e o seu negocio/projeto?
+2. Qual e o seu objetivo principal agora?
+3. Em que fase esta? (ideia, construcao, crescimento, otimizacao)
+```
+
+### 2. Profile Classification
+
+Classificar o usuario em um perfil:
+
+| Perfil | Squads Prioritarias | Primeira Acao |
+|--------|-------------------|--------------|
+| Founder pre-launch | strategic-council, product-systems, brand-system | Strategic vision |
+| Founder building | product-systems, digital-experience, brand-system | Product development |
+| Founder growing | growth-analytics, paid-media, commercial-systems | Growth engine |
+| Marketer | content-intelligence, copywriting-persuasion, paid-media | Content strategy |
+| Designer | brand-system, digital-experience, creative-animations | Design system |
+| Developer | claude-mastery, creative-animations, digital-experience | Claude mastery |
+| Sales/Revenue | commercial-systems, financial-intelligence | Revenue architecture |
+| Strategist | strategic-council, research-intelligence | Strategic counsel |
+| Security-focused | cyber-defense | Security audit |
+
+### 3. Personalized Guide
+
+```
+SEU GUIA PERSONALIZADO
+======================
+
+Com base no seu perfil ({perfil}), recomendo comecar por:
+
+TOP 3 SQUADS PARA VOCE:
+
+1. {squad 1} — {por que e relevante}
+   Invoke: /{prefix}:agents:{orchestrator}
+   Start with: {task recomendada}
+
+2. {squad 2} — {por que e relevante}
+   Invoke: /{prefix}:agents:{orchestrator}
+   Start with: {task recomendada}
+
+3. {squad 3} — {por que e relevante}
+   Invoke: /{prefix}:agents:{orchestrator}
+   Start with: {task recomendada}
+
+QUICK START:
+- Para comecar imediatamente: invoke a squad #1 acima
+- Para uma visao estrategica: /council:agents:council-orchestrator
+- Para ver tudo disponivel: *status
+- Para qualquer duvida: fale comigo (Imperator)
+```
+
+### 4. Ecosystem Map (condensed)
+
+```
+O QUE CADA SQUAD FAZ:
+
+ESTRATEGIA          → strategic-council (10 advisors de classe mundial)
+PESQUISA            → research-intelligence (inteligencia competitiva)
+MARCA               → brand-system (identidade visual completa)
+PRODUTO             → product-systems (discovery a delivery)
+UX/UI               → digital-experience (experiencia digital)
+CONTEUDO            → content-intelligence (estrategia editorial)
+COPY                → copywriting-persuasion (textos que convertem)
+ANIMACOES           → creative-animations (Three.js, shaders, motion)
+NARRATIVA           → narrative-masters (storytelling e pitch)
+GROWTH              → growth-analytics (SEO, analytics, organico)
+MIDIA PAGA          → paid-media (Meta, Google, TikTok, LinkedIn)
+COMERCIAL           → commercial-systems (vendas, CRM, pipeline)
+FINANCEIRO          → financial-intelligence (pricing, P&L, budget)
+SEGURANCA           → cyber-defense (compliance, pentest)
+CLAUDE CODE         → claude-mastery (automacao, prompt engineering)
+```
+
+### 5. Follow-up
+
+Oferecer proximos passos:
+- "Quer que eu te direcione para uma squad agora?"
+- "Quer um strategic brief sobre o seu negocio?"
+- "Quer ver todas as tasks disponiveis de uma squad especifica?"
+
+## Saida
+- Personalized onboarding guide
+- Top 3 squad recommendations with invocation commands
+- Ecosystem overview condensado
+- Quick start instructions
+
+## Validacao
+- [ ] Perfil do usuario identificado
+- [ ] Squads recomendadas sao relevantes para o perfil
+- [ ] Invocation commands fornecidos e corretos
+- [ ] Linguagem clara e acolhedora
+- [ ] Proximos passos oferecidos