wegho-agentes 7.0.3 → 7.0.6

package/.agent/workflows/preview.md

@@ -0,0 +1,81 @@
+---
+description: Preview server start, stop, and status check. Local development server management.
+---
+
+# /preview - Preview Management
+
+$ARGUMENTS
+
+---
+
+## Task
+
+Manage preview server: start, stop, status check.
+
+### Commands
+
+```
+/preview           - Show current status
+/preview start     - Start server
+/preview stop      - Stop server
+/preview restart   - Restart
+/preview check     - Health check
+```
+
+---
+
+## Usage Examples
+
+### Start Server
+```
+/preview start
+
+Response:
+🚀 Starting preview...
+   Port: 3000
+   Type: Next.js
+
+✅ Preview ready!
+   URL: http://localhost:3000
+```
+
+### Status Check
+```
+/preview
+
+Response:
+=== Preview Status ===
+
+🌐 URL: http://localhost:3000
+📁 Project: C:/projects/my-app
+🏷️ Type: nextjs
+💚 Health: OK
+```
+
+### Port Conflict
+```
+/preview start
+
+Response:
+⚠️ Port 3000 is in use.
+
+Options:
+1. Start on port 3001
+2. Close app on 3000
+3. Specify different port
+
+Which one? (default: 1)
+```
+
+---
+
+## Technical
+
+Auto preview uses `auto_preview.py` script:
+
+```bash
+python .agent/scripts/auto_preview.py start [port]
+python .agent/scripts/auto_preview.py stop
+python .agent/scripts/auto_preview.py status
+```
+

package/.agent/workflows/run-agents-workflow.md

@@ -1,186 +1,15 @@
----
-description: Como executar o sistema de agentes com validação de workflow completa
----
-
-# Workflow: Executar Sistema de Agentes
-
-Este workflow garante que todos os agentes sigam os 6 passos obrigatórios do `AGENT_WORKFLOW.md` e valida a execução completa.
-
-## Pré-requisitos
-
-- Node.js 18+ instalado
-- Projeto `wegho-agentes` configurado
-- Dependências instaladas (`npm install`)
-
-## Passos de Execução
-
-### 1. Verificar estrutura de memória
-
-Certifique-se de que a pasta `.agents/memory` existe:
-
-```powershell
-if (-not (Test-Path ".agents/memory")) {
-    New-Item -ItemType Directory -Path ".agents/memory" -Force
-    Write-Host "✅ Pasta de memória criada"
-} else {
-    Write-Host "✅ Pasta de memória já existe"
-}
-```
-
-### 2. Verificar arquivo de repositórios de referência
-
-```powershell
-if (-not (Test-Path ".agents/memory/reference-repositories.json")) {
-    Write-Host "⚠️  Arquivo reference-repositories.json não encontrado"
-    Write-Host "   Criando arquivo padrão..."
-    # O sistema criará automaticamente na primeira execução
-} else {
-    Write-Host "✅ Arquivo de repositórios encontrado"
-}
-```
-
-### 3. Executar o sistema de agentes
-
-// turbo
-```powershell
-npm run agent:preflight
-npm run agent
-```
-
-**O que acontece:**
-- Orquestrador inicia e exibe banner
-- Fase 1: Análise da tarefa
-- Fase 2: Seleção inteligente de agentes
-- Fase 3: Execução com validação de workflow
-- Fase 4: Decisão final (GO/NO-GO)
-- Fase 5: Coleta de feedback (se habilitado)
-- Fase 6: Salvamento de logs
-
-### 4. Verificar logs de execução
-
-```powershell
-if (Test-Path ".agents/memory/orchestrator-logs.json") {
-    Write-Host "✅ Logs salvos com sucesso"
-    Get-Content ".agents/memory/orchestrator-logs.json" | ConvertFrom-Json | Select-Object -Last 1 | ConvertTo-Json -Depth 10
-} else {
-    Write-Host "❌ Logs não foram salvos"
-}
-```
-
-### 5. Validar workflow compliance
-
-Verifique no console se todos os agentes executaram os 6 passos:
-
-**Esperado:**
-```
-━━━ Validação de Workflow: [nome-do-agente] ━━━
-Status: ✅ COMPLIANT
-Passos Completados: 5/5
-
-✅ Passos Executados:
-   - Consultar Memória
-   - Obter Recomendações
-   - Consultar Repositórios
-   - Aplicar Aprendizados
-   - Registrar Resultado
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-**Se houver problema:**
-```
-━━━ Validação de Workflow: [nome-do-agente] ━━━
-Status: ❌ NON-COMPLIANT
-Passos Completados: 3/5
-
-❌ Passos Faltantes:
-   - Consultar Repositórios
-   - Aplicar Aprendizados
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### 6. Verificar estatísticas dos agentes
-
-```powershell
-Get-ChildItem ".agents/memory" -Directory | ForEach-Object {
-    $agentName = $_.Name
-    $successFile = Join-Path $_.FullName "successes.json"
-    $failureFile = Join-Path $_.FullName "failures.json"
-    
-    if (Test-Path $successFile) {
-        $successes = (Get-Content $successFile | ConvertFrom-Json).Count
-        $failures = if (Test-Path $failureFile) { (Get-Content $failureFile | ConvertFrom-Json).Count } else { 0 }
-        $total = $successes + $failures
-        $rate = if ($total -gt 0) { [math]::Round(($successes / $total) * 100, 1) } else { 0 }
-        
-        Write-Host "📊 $agentName - Taxa de sucesso: $rate% ($successes/$total)"
-    }
-}
-```
-
-## Troubleshooting
-
-### Problema: Agente não segue todos os passos
-
-**Solução:**
-1. Verificar se o agente herda de `BaseAgent`
-2. Verificar se usa `executeWithMemory()` ao invés de `executeTask()` diretamente
-3. Verificar logs em `orchestrator-logs.json` para detalhes
-
-### Problema: Logs não são salvos
-
-**Solução:**
-1. Verificar permissões da pasta `.agents/memory`
-2. Verificar se há espaço em disco
-3. Verificar erros no console
-
-### Problema: Repositórios não são consultados
-
-**Solução:**
-1. Criar arquivo `.agents/memory/reference-repositories.json`
-2. Implementar método `getRelevantRepositories()` no agente específico
-3. Verificar se o arquivo JSON está bem formatado
-
-## Comandos Úteis
-
-### Limpar logs antigos
-```powershell
-if (Test-Path ".agents/memory/orchestrator-logs.json") {
-    Remove-Item ".agents/memory/orchestrator-logs.json"
-    Write-Host "✅ Logs limpos"
-}
-```
-
-### Resetar memória de um agente
-```powershell
-$agentName = "frontend-agent"  # Alterar conforme necessário
-Remove-Item ".agents/memory/$agentName" -Recurse -Force
-Write-Host "✅ Memória do $agentName resetada"
-```
-
-### Ver últimos 5 logs
-```powershell
-$logs = Get-Content ".agents/memory/orchestrator-logs.json" | ConvertFrom-Json
-$logs | Select-Object -Last 5 | ForEach-Object {
-    Write-Host "`n━━━ Task ID: $($_.taskId) ━━━"
-    Write-Host "Timestamp: $($_.timestamp)"
-    Write-Host "Total de logs: $($_.logs.Count)"
-}
-```
-
-## Métricas de Sucesso
-
-✅ **Workflow Completo:**
-- Todos os 5 passos obrigatórios executados
-- Logs salvos em arquivo
-- Validação passou sem warnings
-
-✅ **Performance:**
-- Taxa de sucesso > 90%
-- Tempo de execução < 30s por agente
-- Sem erros críticos
-
-✅ **Qualidade:**
-- Aprendizados aplicados (confidence > 0.7)
-- Repositórios consultados
-- Feedback coletado (se habilitado)
-
+---
+description: Como executar o sistema de agentes com documentação sincronizada e workflow obrigatório
+---
+
+# Workflow: Executar Sistema de Agentes
+
+## Sequência obrigatória
+1. `npm run docs:sync`
+2. `npm run agent:preflight`
+3. `npm run agent:start` ou `npm run agent -- "sua tarefa"`
+
+## Validação mínima
+- Confirmar que os `.md` irmãos foram criados ou atualizados
+- Confirmar que o preflight concluiu sem erro
+- Validar escopo, mudanças mínimas, validações e revisão de diff

package/.agent/workflows/status.md

@@ -0,0 +1,86 @@
+---
+description: Display agent and project status. Progress tracking and status board.
+---
+
+# /status - Show Status
+
+$ARGUMENTS
+
+---
+
+## Task
+
+Show current project and agent status.
+
+### What It Shows
+
+1. **Project Info**
+   - Project name and path
+   - Tech stack
+   - Current features
+
+2. **Agent Status Board**
+   - Which agents are running
+   - Which tasks are completed
+   - Pending work
+
+3. **File Statistics**
+   - Files created count
+   - Files modified count
+
+4. **Preview Status**
+   - Is server running
+   - URL
+   - Health check
+
+---
+
+## Example Output
+
+```
+=== Project Status ===
+
+📁 Project: my-ecommerce
+📂 Path: C:/projects/my-ecommerce
+🏷️ Type: nextjs-ecommerce
+📊 Status: active
+
+🔧 Tech Stack:
+   Framework: next.js
+   Database: postgresql
+   Auth: clerk
+   Payment: stripe
+
+✅ Features (5):
+   • product-listing
+   • cart
+   • checkout
+   • user-auth
+   • order-history
+
+⏳ Pending (2):
+   • admin-panel
+   • email-notifications
+
+📄 Files: 73 created, 12 modified
+
+=== Agent Status ===
+
+✅ database-architect → Completed
+✅ backend-specialist → Completed
+🔄 frontend-specialist → Dashboard components (60%)
+⏳ test-engineer → Waiting
+
+=== Preview ===
+
+🌐 URL: http://localhost:3000
+💚 Health: OK
+```
+
+---
+
+## Technical
+
+Status uses these scripts:
+- `python .agent/scripts/session_manager.py status`
+- `python .agent/scripts/auto_preview.py status`

package/.agent/workflows/test.md

@@ -0,0 +1,144 @@
+---
+description: Test generation and test running command. Creates and executes tests for code.
+---
+
+# /test - Test Generation and Execution
+
+$ARGUMENTS
+
+---
+
+## Purpose
+
+This command generates tests, runs existing tests, or checks test coverage.
+
+---
+
+## Sub-commands
+
+```
+/test                - Run all tests
+/test [file/feature] - Generate tests for specific target
+/test coverage       - Show test coverage report
+/test watch          - Run tests in watch mode
+```
+
+---
+
+## Behavior
+
+### Generate Tests
+
+When asked to test a file or feature:
+
+1. **Analyze the code**
+   - Identify functions and methods
+   - Find edge cases
+   - Detect dependencies to mock
+
+2. **Generate test cases**
+   - Happy path tests
+   - Error cases
+   - Edge cases
+   - Integration tests (if needed)
+
+3. **Write tests**
+   - Use project's test framework (Jest, Vitest, etc.)
+   - Follow existing test patterns
+   - Mock external dependencies
+
+---
+
+## Output Format
+
+### For Test Generation
+
+```markdown
+## 🧪 Tests: [Target]
+
+### Test Plan
+| Test Case | Type | Coverage |
+|-----------|------|----------|
+| Should create user | Unit | Happy path |
+| Should reject invalid email | Unit | Validation |
+| Should handle db error | Unit | Error case |
+
+### Generated Tests
+
+`tests/[file].test.ts`
+
+[Code block with tests]
+
+---
+
+Run with: `npm test`
+```
+
+### For Test Execution
+
+```
+🧪 Running tests...
+
+✅ auth.test.ts (5 passed)
+✅ user.test.ts (8 passed)
+❌ order.test.ts (2 passed, 1 failed)
+
+Failed:
+  ✗ should calculate total with discount
+    Expected: 90
+    Received: 100
+
+Total: 15 tests (14 passed, 1 failed)
+```
+
+---
+
+## Examples
+
+```
+/test src/services/auth.service.ts
+/test user registration flow
+/test coverage
+/test fix failed tests
+```
+
+---
+
+## Test Patterns
+
+### Unit Test Structure
+
+```typescript
+describe('AuthService', () => {
+  describe('login', () => {
+    it('should return token for valid credentials', async () => {
+      // Arrange
+      const credentials = { email: 'test@test.com', password: 'pass123' };
+      
+      // Act
+      const result = await authService.login(credentials);
+      
+      // Assert
+      expect(result.token).toBeDefined();
+    });
+
+    it('should throw for invalid password', async () => {
+      // Arrange
+      const credentials = { email: 'test@test.com', password: 'wrong' };
+      
+      // Act & Assert
+      await expect(authService.login(credentials)).rejects.toThrow('Invalid credentials');
+    });
+  });
+});
+```
+
+---
+
+## Key Principles
+
+- **Test behavior not implementation**
+- **One assertion per test** (when practical)
+- **Descriptive test names**
+- **Arrange-Act-Assert pattern**
+- **Mock external dependencies**