@mc1global/opencode-jarvis 0.13.1 → 0.14.0

package/scripts/setup/setup-wsl.sh

@@ -0,0 +1,189 @@
+#!/usr/bin/env bash
+# ──────────────────────────────────────────────────────────────────────────────
+# JARVIS Plugin — Windows (WSL) Prerequisites Setup
+#
+# This script runs INSIDE a WSL (Windows Subsystem for Linux) environment.
+# It installs non-npm dependencies required by @mc1global/opencode-jarvis.
+#
+# Prerequisites:
+#   - WSL 2 with Ubuntu 22.04+ (recommended)
+#   - Run this script from your WSL terminal, NOT from PowerShell/cmd
+#
+# What it installs:
+#   - OpenCode CLI          — The host runtime for JARVIS
+#   - Bun (required)        — SQLite runtime for the plugin
+#   - Ollama (required)     — Local embedding generation for RAG semantic search
+#   - embeddinggemma model  — Default embedding model (768 dimensions)
+#   - Azure CLI (optional)  — Azure DevOps board sync
+#   - Dagger CLI (optional) — Container-based CI/CD gate execution
+#
+# Usage (from WSL terminal):
+#   curl -fsSL <repo-raw-url>/scripts/setup/setup-wsl.sh | bash
+#   # or
+#   chmod +x setup-wsl.sh && ./setup-wsl.sh
+#
+# For more on WSL + OpenCode, see: https://opencode.ai/docs/windows-wsl
+# ──────────────────────────────────────────────────────────────────────────────
+set -euo pipefail
+
+BOLD="\033[1m"
+GREEN="\033[0;32m"
+YELLOW="\033[0;33m"
+RED="\033[0;31m"
+RESET="\033[0m"
+
+info()  { echo -e "${BOLD}[INFO]${RESET}  $1"; }
+ok()    { echo -e "${GREEN}[OK]${RESET}    $1"; }
+warn()  { echo -e "${YELLOW}[WARN]${RESET}  $1"; }
+fail()  { echo -e "${RED}[FAIL]${RESET}  $1"; }
+
+# ── Verify WSL ───────────────────────────────────────────────────────────────
+
+if [ ! -f /proc/version ] || ! grep -qi "microsoft\|wsl" /proc/version 2>/dev/null; then
+  warn "This does not appear to be a WSL environment."
+  warn "This script is designed for Windows Subsystem for Linux."
+  read -rp "Continue anyway? (y/N): " CONTINUE
+  if [[ ! "${CONTINUE:-N}" =~ ^[Yy]$ ]]; then
+    echo "Aborted. Use setup-linux.sh for native Linux or setup-macos.sh for macOS."
+    exit 1
+  fi
+fi
+
+info "WSL environment detected"
+
+# ── OpenCode CLI ─────────────────────────────────────────────────────────────
+
+if ! command -v opencode &>/dev/null; then
+  info "Installing OpenCode CLI..."
+  curl -fsSL https://opencode.ai/install | bash
+  # Source profile to make opencode available
+  # shellcheck disable=SC1090
+  [ -f "$HOME/.bashrc" ] && source "$HOME/.bashrc" 2>/dev/null || true
+  ok "OpenCode CLI installed"
+else
+  ok "OpenCode CLI already installed"
+fi
+
+# ── Bun (required) ───────────────────────────────────────────────────────────
+
+if ! command -v bun &>/dev/null; then
+  info "Installing Bun..."
+  curl -fsSL https://bun.sh/install | bash
+  export BUN_INSTALL="$HOME/.bun"
+  export PATH="$BUN_INSTALL/bin:$PATH"
+  ok "Bun installed ($(bun --version))"
+else
+  ok "Bun already installed ($(bun --version))"
+fi
+
+# ── Ollama (required) ────────────────────────────────────────────────────────
+
+if ! command -v ollama &>/dev/null; then
+  info "Installing Ollama..."
+  curl -fsSL https://ollama.ai/install.sh | sh
+  ok "Ollama installed"
+else
+  ok "Ollama already installed"
+fi
+
+# Start Ollama if not already running
+if ! curl -sf http://localhost:11434/api/tags &>/dev/null; then
+  info "Starting Ollama server..."
+  ollama serve &>/dev/null &
+  sleep 3
+  if curl -sf http://localhost:11434/api/tags &>/dev/null; then
+    ok "Ollama server started"
+  else
+    warn "Ollama server may not have started. You can start it manually: ollama serve"
+  fi
+else
+  ok "Ollama server already running"
+fi
+
+# ── Embedding Model (required for RAG) ───────────────────────────────────────
+
+if ollama list 2>/dev/null | grep -q "embeddinggemma"; then
+  ok "embeddinggemma model already pulled"
+else
+  info "Pulling embeddinggemma embedding model (this may take a minute)..."
+  ollama pull embeddinggemma
+  ok "embeddinggemma model ready"
+fi
+
+# ── Optional: Azure CLI ──────────────────────────────────────────────────────
+
+echo ""
+read -rp "Install Azure CLI for Azure DevOps sync? (y/N): " INSTALL_AZ
+if [[ "${INSTALL_AZ:-N}" =~ ^[Yy]$ ]]; then
+  if ! command -v az &>/dev/null; then
+    info "Installing Azure CLI..."
+    curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
+    ok "Azure CLI installed — run 'az login' to authenticate"
+  else
+    ok "Azure CLI already installed"
+  fi
+else
+  warn "Skipped Azure CLI (optional — needed only for Azure DevOps sync)"
+fi
+
+# ── Optional: Dagger CLI ─────────────────────────────────────────────────────
+
+read -rp "Install Dagger CLI for CI/CD pipelines? (y/N): " INSTALL_DAGGER
+if [[ "${INSTALL_DAGGER:-N}" =~ ^[Yy]$ ]]; then
+  if ! command -v dagger &>/dev/null; then
+    info "Installing Dagger CLI..."
+    curl -fsSL https://dl.dagger.io/dagger/install.sh | sh
+    sudo mv ./bin/dagger /usr/local/bin/dagger 2>/dev/null || true
+    ok "Dagger CLI installed"
+  else
+    ok "Dagger CLI already installed"
+  fi
+else
+  warn "Skipped Dagger CLI (optional — needed only for CI/CD pipeline gates)"
+fi
+
+# ── Summary ──────────────────────────────────────────────────────────────────
+
+echo ""
+echo -e "${BOLD}──────────────────────────────────────────────────────────────${RESET}"
+echo -e "${GREEN}${BOLD}JARVIS prerequisites installed in WSL!${RESET}"
+echo ""
+echo "Next steps:"
+echo ""
+echo "  1. Clone the JARVIS plugin repo INSIDE WSL:"
+echo ""
+echo "     git clone <repo-url> ~/code/jarvis-opencode"
+echo ""
+echo "  Option A — Install from npm (production):"
+echo ""
+echo "     In your project's opencode.json:"
+echo '     { "plugin": ["@mc1global/opencode-jarvis"] }'
+echo ""
+echo "  Option B — Local development (before npm publish):"
+echo ""
+echo "     cd ~/code/jarvis-opencode"
+echo "     npm install"
+echo "     npm run link:local    # builds + creates symlink in ~/.config/opencode/plugins/"
+echo ""
+echo "     The plugin loads globally in ALL projects without any opencode.json change."
+echo "     After each code change: npm run build  (symlink stays valid)"
+echo "     To remove the link:    npm run unlink:local"
+echo ""
+echo "  2. Navigate to your project INSIDE WSL:"
+echo ""
+echo "     # Recommended: WSL-native path (best performance)"
+echo "     cd ~/code/my-project"
+echo ""
+echo "     # Alternative: Windows files via /mnt/"
+echo "     cd /mnt/c/Users/YourName/Documents/my-project"
+echo ""
+echo "  3. Launch OpenCode from WSL:"
+echo ""
+echo "     opencode"
+echo ""
+echo "  4. JARVIS will auto-bootstrap on first launch."
+echo ""
+echo -e "  ${YELLOW}TIP:${RESET} Keep project files in the WSL filesystem (~/code/) for best performance."
+echo ""
+echo -e "  See: ${BOLD}https://opencode.ai/docs/windows-wsl${RESET}"
+echo -e "${BOLD}──────────────────────────────────────────────────────────────${RESET}"

package/templates/agents-md.template.md

@@ -0,0 +1,130 @@
+# AGENTS.md
+
+## DESIGN PRINCIPLES
+
+- SOLID: all 5 principles, every class/module
+- DDD: domain layer zero external deps; repo interfaces in domain, impls in infra
+- Max 500 lines/file — split by SRP when approaching limit
+- No direct cross-context imports — use ports/adapters at composition root
+- No fallback/mock to mask errors — throw with proper context
+- Immutable value objects; entities mutate only via domain methods
+
+## KANBAN LIFECYCLE (mandatory for all work >15 min)
+
+Pipeline: `backlog→grooming→ready→doing→review→tested→done`  
+Never commit to `main`. Never skip steps.
+
+### Before coding
+1. `kanban-card-create` → assign epic + sprint
+2. Groom (all 4 required):
+   - `vault-create-document path="12-Scope-Docs/CD-XXX-title.md"`
+   - `kanban-card-scope-doc card_id="CD-XXX" path="12-Scope-Docs/CD-XXX-title.md"`
+   - `kanban-card-criteria` (min 2 AC)
+   - `kanban-card-estimate` (Fibonacci: 1,2,3,5,8,13,21)
+3. `kanban-grooming-validate` → fix errors → move to `ready`
+4. `kanban-card-assign` + `kanban-card-assign-sprint` → move to `doing`
+5. `context-session-start purpose="CD-XXX: <title>"`
+
+Grooming = problem + value + boundaries. No class names, method signatures, or code.
+
+### After coding
+6. Build + test suite — zero errors/warnings
+7. Commit: `Add X (CD-XXX)` | `Fix Y (CD-XXX)` (imperative, card ref)
+8. Meet all AC + gate tasks → `doing→review→tested→done`
+9. `vault-manage` — update dashboard + any affected docs
+
+## GUARDRAILS
+
+NEVER:
+- fallback/mock to mask errors — errors must throw with proper handling
+- "simpler approach" to bypass the real solution
+- read `.csv` directly → `data-csv-query`
+- read `.yaml/.yml` directly → `data-yaml-get`
+- read `.env/.pem/.key` — blocked by governance
+- `git push --force` on main/master
+- create `TODO.md`, `PLAN.md`, `ROADMAP.md` — use kanban tools
+- bypass kanban for trackable work
+- push to git without explicit user approval
+- start the app from agent session — ask user for separate terminal
+- skip grooming requirements or gate tasks
+
+ALWAYS:
+- `rag-search`/`rag-snippet` before creating or modifying files
+- use specialized tools over raw file/shell ops
+- get full codebase context before changes — ask if unclear
+- `context-session-start` before any card work
+- meet all gate tasks before `review→tested→done`
+
+## GOVERNANCE (runtime enforced)
+
+Hook fires on every tool call — `error` severity blocks execution.
+- file-access: block direct CSV/YAML/env reads
+- shell-safety: block force-push, warn destructive ops
+- security: block env dump, credential file reads
+- kanban: require gate tasks before transitions
+
+`governance-validate` — pre-check before risky ops  
+`governance-policies` — list active policies
+
+## CODE QUALITY GATES
+
+Before moving `doing→review`:
+- Build passes with zero errors
+- All existing tests pass
+- New behaviour covered by tests
+- No secrets or credentials in code
+- No debug/console output left in production paths
+
+Before moving `review→tested`:
+- AC verified against running code (not just reading)
+- Edge cases and error paths tested
+
+Before `tested→done`:
+- Vault docs updated
+- Commit references card ID
+
+## GIT
+
+- feature branches only — never commit to `main`
+- commit: `Add X (CD-XXX)` | `Fix Y (CD-XXX)`
+- no amend on pushed commits
+- no push without explicit user approval
+
+## VAULT
+
+Path: `obsidian-vault/`
+- `09-Dashboards/` — metrics and status
+- `11-Domain-Reference/` — per-context architecture decisions
+- `12-Scope-Docs/CD-XXX-*.md` — grooming scope documents
+
+Tool: `vault-manage` (inspect/read/write/create/search)  
+Use structured lists, not markdown tables.
+
+## TOOLS — KEY WORKFLOWS
+
+| Need | Tool |
+|---|---|
+| Start work on a card | `/start-card CD-XXX` |
+| Check environment health | `/healthcheck` |
+| Explore codebase semantically | `rag-search` / `rag-snippet` |
+| Look up JARVIS workflow docs | `rag-oracle-search query="..."` |
+| Track a decision or finding | `context-note-add` |
+| Plan multi-step work | `context-todo-add` |
+| View board state | `kanban-board-view` |
+| Check governance rules | `governance-policies` |
+| Sync with Azure DevOps | `/sync-azure` |
+
+## WORKFLOW DOCS
+
+Unknown workflow → search ORACLE first:
+- kanban: `rag-oracle-search query="..." domain="workflows"`
+- governance: `rag-oracle-search query="..." domain="governance"`
+- patterns: `rag-oracle-search query="..." domain="patterns"`
+- setup: `rag-oracle-search query="..." domain="quick_reference"`
+
+## SLASH COMMANDS
+
+- `/start-card CD-XXX` — full card lifecycle start
+- `/healthcheck` — diagnostics + fix guidance
+- `/sync-azure` — Azure DevOps sync workflow
+- `/jarvis-agents-md-file` — regenerate this file

package/templates/commands/jarvis-agents-md-file.md

@@ -0,0 +1,7 @@
+---
+description: Generate or update AGENTS.md with the canonical JARVIS operational guide
+---
+
+Run the `jarvis-bootstrap` tool with `force: true` to generate or update the AGENTS.md file in the current project directory.
+
+After completing, report what was created or updated. If AGENTS.md was created or modified, remind the user to commit it to version control.

package/.opencode/agents/_domain-agent-base.md

@@ -1,131 +0,0 @@
-# Domain Agent Base - JARVIS Framework
-
-Base comum para todos os domain agents. **NÃO duplica regras** - orienta a consultar ORACLE.
-
----
-
-## ANTES DE QUALQUER AÇÃO
-
-```bash
-python scripts/rag/oracle_rag_cli.py search "sua dúvida"
-python scripts/rag/oracle_rag_cli.py rules "regras para X"
-python scripts/rag/oracle_rag_cli.py avoid "anti-patterns X"
-```
-
----
-
-## ESPECIFICAÇÕES TÉCNICAS
-
-- **Python**: 3.11.x
-- **Ambiente**: `uv` (NUNCA pip direto)
-- **Ativar**: `source .venv/bin/activate`
-- **Instalar**: `uv pip install <package>`
-
----
-
-## CONSULTAS ORACLE OBRIGATÓRIAS
-
-| Quando | Consultar |
-|--------|-----------|
-| Não sabe qual tool usar | `oracle search "tool para X"` |
-| Vai editar arquivo | `oracle rules "edit file type"` |
-| Vai criar código | `oracle rules "code standards"` |
-| Vai fazer git operation | `oracle search "git operations"` |
-| Precisa de workflow | `oracle search "kanban workflow"` |
-| Vai criar testes | `oracle search "test patterns"` |
-
----
-
-## CICLO DE TRABALHO
-
-### Hierarquia de Organização
-
-```
-Epic (EP-XXX)           # Objetivo maior (feature, initiative)
-  └── Sprint            # Ciclo de trabalho (opcional)
-       └── Card (CD-XXX)    # Tarefa executável
-            └── Session     # Período de trabalho vinculado ao Card
-                 └── TODOs, Notes, Artifacts  # Registros da Session
-```
-
-### Fluxo Completo
-
-**1. Verificar contexto antes de iniciar**
-```bash
-# Há Card em doing para você?
-python scripts/kanban_manager.py card list -w WORKSPACE --status doing
-
-# Há Session ativa?
-python scripts/context_memory_cli.py session current -w WORKSPACE
-```
-
-**2. Se não há Card em doing** → Buscar próximo Card ready
-```bash
-python scripts/kanban_manager.py card list -w WORKSPACE --status ready
-python scripts/kanban_manager.py card start CD-XXX -a AGENT -w WORKSPACE
-```
-
-**3. Se não há Session ativa** → Iniciar Session vinculada ao Card
-```bash
-# Session ID formato: YYYY-MM-DD-HHMM-workspace
-python scripts/context_memory_cli.py session start "CD-XXX: descrição" -w WORKSPACE
-```
-
-**4. Durante o trabalho**
-- Consultar ORACLE para regras da operação
-- Usar manager/skill indicada pelo ORACLE
-- Registrar descobertas como notes
-- Criar testes para código produzido
-
-**5. Registrar artefatos no Context Memory**
-```bash
-# Test plan
-python scripts/context_memory_cli.py note add "Test plan: ..." -w WORKSPACE --tags test-plan,CD-XXX
-
-# Test result
-python scripts/context_memory_cli.py note add "Test result: ..." -w WORKSPACE --tags test-result,CD-XXX
-
-# Decisões técnicas
-python scripts/context_memory_cli.py note add "Decision: ..." -w WORKSPACE --tags decision,CD-XXX
-```
-
-**6. Ao finalizar Card**
-```bash
-# Mover Card pelo pipeline: doing → review → tested → done
-python scripts/kanban_manager.py card move CD-XXX --to=review -w WORKSPACE
-
-# Finalizar Session com resumo
-python scripts/context_memory_cli.py session finish SESSION_ID -w WORKSPACE
-```
-
-### Estados do Card
-
-```
-backlog → grooming → ready → doing → review → tested → done
-                                  ↘ blocked
-```
-
-| Estado | Significado |
-|--------|-------------|
-| backlog | Identificado, não refinado |
-| grooming | Em refinamento/investigação |
-| ready | Refinado, pronto para execução |
-| doing | Em execução (1 por agent) |
-| review | Aguardando revisão |
-| tested | Testado, aguardando merge |
-| done | Concluído |
-| blocked | Impedido (requer ação externa) |
-
----
-
-## REFERÊNCIAS NO ORACLE
-
-- Protocolo completo: `oracle search "agent protocol"`
-- Tools permitidas: `oracle search "tools governance"`
-- Token economy: `oracle search "token optimization"`
-- Kanban workflow: `oracle search "kanban workflow"`
-- Session lifecycle: `oracle search "session lifecycle"`
-
----
-
-**Princípio**: O ORACLE é a fonte de verdade. Este documento apenas orienta COMO consultar.

package/.opencode/agents/agent-integration.md

@@ -1,197 +0,0 @@
----
-description: Reference guide for JARVIS agent integration and Scrum + Kanban workflow orchestration
-mode: subagent
----
-
-# JARVIS Agent Integration - Scrum + Kanban Workflow
-
-## Identidade: Coordenador Principal (Scrum Master + Tech Lead)
-
-O coordenador principal atua simultaneamente como:
-
-| Persona          | Responsabilidades                                                                             |
-| ---------------- | --------------------------------------------------------------------------------------------- |
-| **Scrum Master** | Sessions, Kanban workflow, Sprint coordination, Card management, Velocity tracking            |
-| **Tech Lead**    | Qualidade de código (SOLID, DDD), Arquitetura, Code review, Token economy, Governança técnica |
-
-## Ecossistema de Agents
-
-### 1. Domain Agents (JARVIS Framework)
-
-Para trabalhos no próprio JARVIS, use **domain agents especializados** com níveis de complexidade:
-
-| Domínio             | Simple                             | Medium                             | Complex                             |
-| ------------------- | ---------------------------------- | ---------------------------------- | ----------------------------------- |
-| **Code Management** | code-management-agent-simple       | code-management-agent-medium       | code-management-agent-complex       |
-| **Kanban**          | kanban-domain-agent-simple         | kanban-domain-agent-medium         | kanban-domain-agent-complex         |
-| **RAG**             | rag-domain-agent-simple            | rag-domain-agent-medium            | rag-domain-agent-complex            |
-| **Context Memory**  | context-memory-domain-agent-simple | context-memory-domain-agent-medium | context-memory-domain-agent-complex |
-
-**Localização**: `.opencode/agents/*-domain-agent-{simple,medium,complex}.md`
-
-### 2. MCP Workspace Agents (Projetos Externos)
-
-Para projetos nos workspaces, use **MCP workspace agents**:
-
-| Workspace          | Projeto        | Agents Disponíveis              |
-| ------------------ | -------------- | ------------------------------- |
-| ARVision           | Android/Kotlin | kotlin-expert, android-expert   |
-| web-ui-gensynth    | Web UI         | react-expert, typescript-expert |
-| genSyntheticCroped | Python ML      | python-expert, ml-expert        |
-| neural_quant-bot   | Trading        | trading-expert, python-expert   |
-
-### 3. Specialized Agents (Cross-Domain)
-
-| Agent                | Responsabilidade                    | Quando Usar                             |
-| -------------------- | ----------------------------------- | --------------------------------------- |
-| `product-owner`      | User stories, requirements analysis | Análise de requisitos, backlog creation |
-| `solution-architect` | DDD architecture, bounded contexts  | Design de sistema, arquitetura          |
-| `data-engineer`      | Database schema, migrations         | Modelagem de dados, migrations          |
-| `script-developer`   | Multi-language code development     | Implementação de código                 |
-| `code-reviewer`      | SOLID principles, DDD validation    | Code review, quality assurance          |
-| `scrum-master`       | Multi-agent workflow orchestration  | Sprint planning, workflow coordination  |
-
-## Workflow de Coordenação
-
-### Framework de Decisão por Complexidade
-
-| Nível       | Critérios                                           | Modelo Recomendado                 | Agent Sufixo |
-| ----------- | --------------------------------------------------- | ---------------------------------- | ------------ |
-| **Simple**  | Tarefas básicas, leitura, buscas simples            | ollama/llama3.2:3b                 | -simple      |
-| **Medium**  | Modificações moderadas, CRUD, análise média         | ollama/gpt-oss:20b                 | -medium      |
-| **Complex** | Refatoração avançada, análise profunda, arquitetura | anthropic/claude-sonnet-4-20250514 | -complex     |
-
-### Protocolo de Delegação
-
-```bash
-# 1. Identificar Contexto
-Tarefa no JARVIS? → Domain Agent especializado
-Tarefa em Workspace? → MCP Agent + Skills
-Tarefa cross-workspace? → workspace-domain-agent (orquestração)
-
-# 2. Consultar ORACLE Antes de Agir
-python scripts/rag/oracle_rag_cli.py search "como fazer X"
-python scripts/rag/oracle_rag_cli.py rules "regras para X"
-
-# 3. Delegar ao Agent Correto
-@{domain}-agent-{complexity} "descrição detalhada da tarefa"
-```
-
-## Scrum + Kanban Workflow
-
-### Hierarquia de Organização
-
-```
-Epic (EP-XXX)           # Objetivo maior (feature, initiative)
-  └── Sprint            # Ciclo de trabalho (opcional)
-       └── Card (CD-XXX)    # Tarefa executável
-            └── Session     # Período de trabalho vinculado ao Card
-                 └── TODOs, Notes, Artifacts  # Registros da Session
-```
-
-### Kanban Pipeline
-
-```
-backlog → grooming → ready → doing → review → tested → done
-    ↑         ↑                                    ↓
-    |         └─── artifacts required ────────────┘
-    └─────────────── rework if rejected ──────────┘
-```
-
-### Session Lifecycle (OBRIGATÓRIO)
-
-```bash
-# Iniciar sessão antes de qualquer trabalho
-python scripts/context_memory_cli.py session start "descrição" -w WORKSPACE
-
-# Session ID: YYYY-MM-DD-HHMM-workspace
-# Vincula: TODOs, notes, cards, artifacts
-```
-
-### Kanban Workflow Commands
-
-```bash
-# Card Management
-python scripts/kanban_manager.py card create -w WORKSPACE -t "Task"
-python scripts/kanban_manager.py card start CARD_ID -a AGENT -w WORKSPACE
-python scripts/kanban_manager.py card move CARD_ID --to=STATUS -w WORKSPACE
-
-# Grooming Requirements (antes de mover para READY)
-python scripts/kanban_manager.py card add-artifact CD-XXX -t scope_doc --title "Scope" -c "Content"
-
-# Sprint Management
-python scripts/kanban_manager.py sprint create -w WORKSPACE -n "Sprint Name"
-python scripts/kanban_manager.py sprint start SPRINT_ID -w WORKSPACE
-```
-
-## Agent Coordination Patterns
-
-### Product Owner → Solution Architect
-
-- PO cria user stories com acceptance criteria
-- Solution Architect projeta bounded contexts e domain models
-- **Comando:** `user-story-manager create` → `solution-architect`
-
-### Solution Architect → Data Engineer
-
-- Architect define entidades e agregados
-- Data Engineer projeta schema e migrations
-- **Comando:** `migration-manager generate` → `data-engineer`
-
-### Architect/Engineer → Script Developer
-
-- Specs via artifacts (scope_doc, design_doc)
-- Script Developer implementa seguindo SOLID + DDD
-- **Comando:** `kanban_manager.py card start` → `script-developer`
-
-### Script Developer → Code Reviewer
-
-- Dev marca card como REVIEW
-- Code Reviewer valida SOLID, DDD, token economy
-- **Comando:** `kanban_manager.py card move --to=review` → `code-reviewer`
-
-### Scrum Master Orchestration
-
-- Monitora WIP limits
-- Coordena multi-agent workflow
-- Resolve conflitos e dependências
-- **Comando:** `scrum-master` para planning e standups
-
-## Governança e Permissões
-
-### Operações OBRIGATÓRIAS via Managers
-
-| Operação | Manager Obrigatório     | Benefício         |
-| -------- | ----------------------- | ----------------- |
-| YAML     | `yaml_manager.py`       | 98% token savings |
-| JSON     | `json_manager.py`       | 98% token savings |
-| Markdown | `markdown_manager.py`   | 95% token savings |
-| Código   | `code_block_manager.py` | 90% token savings |
-| CSV      | `csv_manager.py`        | 99% token savings |
-| Git      | `git_repo_manager.py`   | 95% token savings |
-
-### Workflow de Validação Kanban
-
-- **Grooming → Ready**: Requer pelo menos 1 artifact
-- **Ready → Doing**: Auto-aprovado se groomed
-- **Doing → Review**: Requer implementação completa
-- **Review → Tested**: Aprovação do code-reviewer
-- **Tested → Done**: Testes passando
-
-## Token Economy
-
-| Operação      | Alto Custo      | Baixo Custo          | Economia |
-| ------------- | --------------- | -------------------- | -------- |
-| Ler arquivo   | `Read` inteiro  | `code-block-manager` | 90%      |
-| Editar código | `Edit`          | `code-block-manager` | 90%      |
-| Buscar código | `Grep` múltiplo | `rag_cli.py search`  | 80%      |
-| Git ops       | `Bash(git)`     | `git-repo-manager`   | 95%      |
-| JSON/YAML     | `Read` inteiro  | `*-manager get`      | 98%      |
-
-## See Also
-
-- `@_domain-agent-base.md` - Base comum para domain agents
-- `@OPENCODE.md` - Modelo operacional completo
-- `@kanban_cli_reference.md` - Comandos Kanban detalhados
-- `@context_memory_vs_kanban.md` - Sistemas complementares
-- `@agent_protocol.md` - Protocolo obrigatório para agents