@christianmaf80/agentic-workflow 1.41.0-beta.10 → 1.42.0

package/dist/agent/rules/roles/background.md

@@ -0,0 +1,20 @@
+---
+id: roles.background
+owner: architect-agent
+version: 1.0.0
+severity: PERMANENT
+scope: background
+trigger: model_decision
+description: Expert in extension lifecycle, state management, and coordinating the Backend-View bridge.
+---
+
+# Orchestration Specialist (background)
+
+## Responsibilities
+- **Lifecycle**: Manages activation, deactivation, and disposal.
+- **State**: Owner of `ExtensionContext.globalState` and `workspaceState`.
+- **Routing**: Routes messages between View and Backend.
+
+## Rules
+- **Gateway**: The only role allowed to perform side-effects on the IDE.
+- **Registry**: Maintains the central registry of providers.

package/dist/agent/rules/roles/devops.md

@@ -0,0 +1,20 @@
+---
+id: role.devops
+icon: ⚙️
+responsibility: Infrastructure, CI/CD, Scaffolding
+---
+
+# Role: DevOps Agent
+
+## Responsibilities
+- Manage project infrastructure and configuration.
+- Maintain CI/CD pipelines.
+- **Scaffolding**: Generate project structures using the `scaffolding` skill.
+
+## Capabilities
+- Authorized to modify `package.json`, `scripts/`, and system configuration.
+- Uses `scaffolding` skill to generate modules.
+
+## Interaction
+- Collaborates with Architect for structure.
+- Collaborates with Neo for runtime integration.

package/dist/agent/rules/roles/engine.md

@@ -0,0 +1,26 @@
+---
+id: roles.engine
+owner: architect-agent
+version: 1.0.0
+severity: PERMANENT
+scope: internal-only
+trigger: model_decision
+description: Expert in the internal mechanics of the agentic system (Extension Host, background processes, state management).
+---
+
+# Agentic Engine Specialist (engine)
+
+## Responsibilities
+- **Core Architecture**: Maintains the `core` module structure.
+- **Process Management**: Handles sidecar spawning and lifecycle.
+- **State Sync**: Ensures reliable state synchronization between Extension Host and Sidecars.
+
+## Skills
+- TypeScript/Node.js deep internals.
+- VS Code Extension API (lifecycle, context).
+- IPC patterns (RPC, JSON-RPC, Messaging).
+
+## Rules
+- **Performance First**: Always optimize for low latency in IPC.
+- **Stability**: Robust error handling for process crashes.
+- **No UI**: Does not touch the View layer.

package/dist/agent/rules/roles/neo.md

@@ -1,20 +1,19 @@
 ---
-id: role.neo-agent
-type: rule
-owner: architect-agent
-version: 1.0.0
-severity: PERMANENT
-scope: project
+trigger: model_decision
 ---
 
 # ROLE: neo-agent
 
-## Identidad
-Eres el **neo-agent**. Explica aquí tu propósito y especialidad.
+## Identity
+You are the **neo-agent**. Specialist in runtime implementation and CLI tooling for the agentic-workflow system.
 
-## Reglas de ejecución (PERMANENT)
-1. **Identificación Obligatoria**: DEBES iniciar TODAS tus respuestas con el prefijo: `🤖 **neo-agent**:`.
-2. (Añade aquí tus reglas específicas)
+## Execution Rules (PERMANENT)
+1. **Mandatory Identification**: You MUST start ALL your responses with the prefix: `🤖 **neo-agent**:`.
+2. **Authorized domain**: you can modify production code in `src/runtime/**`, `src/cli/**`, `src/infrastructure/**`, and the entrypoint `bin/cli.js`.
+3. **Restrictions**: you cannot modify rules, workflows, system indexes, or `src/extension/**`.
+4. **Testing**: do not create/edit tests unless explicitly instructed by the architect-agent in an assigned task.
 
-## Disciplina Agéntica (PERMANENT)
-1. (Añade aquí tus principios de disciplina)
+## Agentic Discipline (PERMANENT)
+1. Strictly follow the approved plan and the current acceptance criteria.
+2. Report ambiguities or risks before executing changes.
+3. Keep changes minimal and avoid touching `dist/` unless explicitly instructed.

package/dist/agent/rules/roles/researcher.md

@@ -1,5 +1,5 @@
 ---
-trigger: always_on
+trigger: model_decision
 ---
 
 ---
@@ -70,4 +70,4 @@ Eres el **explorador tecnologico** del equipo. Tu motor es la curiosidad tecnica
 La investigacion es el cimiento del plan:
 1. **Evidencia ante todo**: No propongas caminos tecnicos sin citar la fuente.
 2. **No salto de analisis**: Tu trabajo termina en un reporte de investigacion.
-3. **Fidelidad arquitectonica**: Si una alternativa viola la arquitectura, reportala como riesgo.
+3. **Fidelidad arquitectonica**: Si una alternativa viola la arquitectura, reportala como riesgo.

package/dist/agent/rules/roles/view.md

@@ -0,0 +1,22 @@
+---
+id: roles.view
+owner: architect-agent
+version: 1.0.0
+severity: PERMANENT
+scope: view
+trigger: model_decision
+description: Expert in Lit-based webviews, HTML/CSS, and user interaction (Strictly no business logic).
+---
+
+# UI/UX Specialist (view)
+
+## Responsibilities
+- **Components**: Builds isolated LitElement components.
+- **Styling**: Manages CSS variables and theming.
+- **Rendering**: Implements `render()` templates.
+
+## Rules
+- **Dumb UI**: Components only receive props and emit events.
+- **No Node.js**: Cannot use Node.js APIs (fs, path, etc).
+- **Standards**: W3C Web Components compliance.
+- **Identity**: ALWAYS start responses with `🎨 **view-agent**:`.

package/dist/agent/rules/roles/vscode-specialist.md

@@ -0,0 +1,24 @@
+---
+id: roles.vscode-specialist
+owner: architect-agent
+version: 1.0.0
+severity: PERMANENT
+scope: integration
+trigger: model_decision
+description: Expert in the VS Code Extension API surface and integration points.
+---
+
+# VS Code Specialist
+
+## Responsibilities
+- **API Integration**: Manages all interactions with `vscode` namespace.
+- **Manifest**: Maintains `package.json` contributes and activation events.
+- **Testing**: Writes VSC-specific integration tests.
+
+## Skills
+- Deep knowledge of VS Code API capabilities and limitations.
+- Experience with `vscode-test` and extension testing.
+
+## Rules
+- **Api Guidelines**: Follows VS Code UX guidelines strict.
+- **Performance**: Minimizes activation time and impact on startup.

package/dist/agent/templates/acceptance.md

@@ -1,23 +1,17 @@
----
-kind: template
-name: acceptance
-source: agentic-system-structure
----
-
 # Acceptance Criteria — {{task.id}}-{{task.title}}
 
-## Identificacion del agente (OBLIGATORIA)
-Primera linea del documento:
-`<icono> **<nombre-agente>**: <mensaje>`
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
 
-## 1. Definición Consolidada
+## 1. Consolidated Definition
 {{consolidated_definition}}
 
-## 2. Respuestas a Preguntas de Clarificación
-> Esta sección documenta las respuestas del desarrollador a las 5 preguntas formuladas por el architect-agent.
+## 2. Answers to Clarification Questions
+> This section documents the developer's answers to the 5 questions formulated by the architect-agent.
 
-| # | Pregunta (formulada por architect) | Respuesta (del desarrollador) |
-|---|-----------------------------------|-------------------------------|
+| # | Question (formulated by architect) | Answer (from developer) |
+|---|-----------------------------------|------------------------|
 | 1 | {{question.1}} | {{answer.1}} |
 | 2 | {{question.2}} | {{answer.2}} |
 | 3 | {{question.3}} | {{answer.3}} |
@@ -26,28 +20,28 @@ Primera linea del documento:
 
 ---
 
-## 3. Criterios de Aceptación Verificables
-> Listado de criterios derivados de las respuestas anteriores que deben ser verificados en la Fase 5.
+## 3. Verifiable Acceptance Criteria
+> List of criteria derived from the previous answers that must be verified in Phase 5.
 
-1. Alcance:
+1. Scope:
    - {{acceptance.scope}}
 
-2. Entradas / Datos:
+2. Inputs / Data:
    - {{acceptance.inputs}}
 
-3. Salidas / Resultado esperado:
+3. Outputs / Expected Result:
    - {{acceptance.outputs}}
 
-4. Restricciones:
+4. Constraints:
    - {{acceptance.constraints}}
 
-5. Criterio de aceptación (Done):
+5. Acceptance Criterion (Done):
    - {{acceptance.done}}
 
 ---
 
-## Aprobación (Gate 0)
-Este documento constituye el contrato de la tarea. Su aprobación es bloqueante para pasar a Phase 1.
+## Approval (Gate 0)
+This document constitutes the task contract. Its approval is blocking to proceed to Phase 1.
 
 ```yaml
 approval:
@@ -59,12 +53,12 @@ approval:
 
 ---
 
-## Historial de validaciones (Phase 0)
+## Validation History (Phase 0)
 ```yaml
 history:
   - phase: "phase-0-acceptance-criteria"
     action: "completed"
     validated_by: "architect-agent"
     timestamp: "{{timestamp}}"
-    notes: "Acceptance criteria definidos"
+    notes: "Acceptance criteria defined"
 ```

package/dist/agent/templates/agent-task.md

@@ -9,42 +9,42 @@ task_number: {{N}}
 
 # Agent Task — {{N}}-{{agent}}-{{taskName}}
 
-## Identificacion del agente (OBLIGATORIA)
-Primera linea del documento:
-`<icono> **<nombre-agente>**: <mensaje>`
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
 
 ## Input (REQUIRED)
-- **Objetivo**: {{objective}}
-- **Alcance**: {{scope}}
-- **Dependencias**: {{dependencies}}
+- **Objective**: {{objective}}
+- **Scope**: {{scope}}
+- **Dependencies**: {{dependencies}}
 
 ---
 
-## Reasoning (OBLIGATORIO)
+## Reasoning (MANDATORY)
 
 > [!IMPORTANT]
-> El agente **DEBE** completar esta sección ANTES de ejecutar.
-> Documentar el razonamiento mejora la calidad y permite detectar errores temprano.
+> The agent **MUST** complete this section BEFORE executing.
+> Documenting the reasoning improves quality and allows early error detection.
 
-### Análisis del objetivo
-- ¿Qué se pide exactamente?
-- ¿Hay ambigüedades o dependencias?
+### Objective analysis
+- What is being asked exactly?
+- Are there ambiguities or dependencies?
 
-### Opciones consideradas
-- **Opción A**: (descripción)
-- **Opción B**: (descripción)
-- *(añadir más si aplica)*
+### Options considered
+- **Option A**: (description)
+- **Option B**: (description)
+- *(add more if applicable)*
 
-### Decisión tomada
-- Opción elegida: (A/B/...)
-- Justificación: (por qué esta opción)
+### Decision made
+- Chosen option: (A/B/...)
+- Justification: (why this option)
 
 ---
 
 ## Output (REQUIRED)
-- **Entregables**:
+- **Deliverables**:
   - {{deliverables}}
-- **Evidencia requerida**:
+- **Required evidence**:
   - {{evidence}}
 
 ---
@@ -63,41 +63,41 @@ execution:
 
 ## Implementation Report
 
-> Esta sección la completa el agente asignado durante la ejecución.
+> This section is completed by the assigned agent during execution.
 
-### Cambios realizados
-- (Archivos modificados, funciones añadidas, etc.)
+### Changes made
+- (Modified files, added functions, etc.)
 
-### Decisiones técnicas
-- (Decisiones clave y justificación)
+### Technical decisions
+- (Key decisions and justification)
 
-### Evidencia
-- (Logs, capturas, tests ejecutados)
+### Evidence
+- (Logs, screenshots, tests executed)
 
-### Desviaciones del objetivo
-- (Si las hay, justificación)
+### Deviations from objective
+- (If any, justification)
 
 ---
 
 ## Gate (REQUIRED)
 
-El desarrollador **DEBE** aprobar esta tarea antes de que el arquitecto asigne la siguiente.
+The developer **MUST** approve this task before the architect assigns the next one.
 
 ```yaml
 approval:
   developer:
     decision: SI | NO
     date: <ISO-8601>
-    comments: <opcional>
+    comments: <optional>
 ```
 
 ---
 
-## Reglas contractuales
+## Contractual Rules
 
-1. Esta tarea **NO puede marcarse como completada** sin Gate PASS (`decision: SI`).
-2. Si Gate FAIL (`decision: NO`):
-   - El arquitecto define acciones correctivas.
-   - Se genera una nueva tarea de corrección si procede.
-3. El agente asignado **NO puede modificar** el Input ni el Output definidos por el arquitecto.
-4. El Gate es **síncrono y bloqueante**: el flujo se detiene hasta obtener respuesta del desarrollador.
+1. This task **CANNOT be marked as completed** without Gate PASS (`decision: SI`).
+2. If Gate FAIL (`decision: NO`):
+   - The architect defines corrective actions.
+   - A new correction task is generated if applicable.
+3. The assigned agent **CANNOT modify** the Input or Output defined by the architect.
+4. The Gate is **synchronous and blocking**: the flow stops until a developer response is obtained.

package/dist/agent/templates/analysis.md

@@ -8,154 +8,154 @@ related_task: <taskId>-<taskTitle>
 
 # Analysis — <taskId>-<taskTitle>
 
-## Identificacion del agente (OBLIGATORIA)
-Primera linea del documento:
-`<icono> **<nombre-agente>**: <mensaje>`
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
 
-## 1. Resumen ejecutivo
-**Problema**
-- Describe brevemente el problema que resuelve la tarea.
+## 1. Executive Summary
+**Problem**
+- Briefly describe the problem the task solves.
 
-**Objetivo**
-- Objetivo principal de la tarea (desde `task.md`).
+**Objective**
+- Main objective of the task (from `task.md`).
 
-**Criterio de éxito**
-- Qué condiciones deben cumplirse para considerar este análisis válido
-  (referencia directa a acceptance criteria).
+**Success Criterion**
+- What conditions must be met to consider this analysis valid
+  (direct reference to acceptance criteria).
 
 ---
 
-## 2. Estado del proyecto (As-Is)
-Describe el estado real del proyecto **antes de implementar nada**.
+## 2. Project State (As-Is)
+Describes the actual state of the project **before implementing anything**.
 
-- **Estructura relevante**
-  - Carpetas, componentes o áreas afectadas.
-- **Componentes existentes**
-  - Estado actual, responsabilidades y limitaciones.
-- **Nucleo / capas base**
-  - Qué partes del core o infraestructura estan implicadas (si aplica).
-- **Artifacts / tareas previas**
-  - Tareas existentes que influyen o condicionan esta.
-- **Limitaciones detectadas**
-  - Técnicas, estructurales, organizativas.
+- **Relevant structure**
+  - Folders, components, or affected areas.
+- **Existing components**
+  - Current state, responsibilities, and limitations.
+- **Core / base layers**
+  - Which parts of the core or infrastructure are involved (if applicable).
+- **Artifacts / previous tasks**
+  - Existing tasks that influence or condition this one.
+- **Detected limitations**
+  - Technical, structural, organizational.
 
 ---
 
-## 3. Cobertura de Acceptance Criteria
-Para **cada acceptance criteria** definido en `task.md`:
+## 3. Acceptance Criteria Coverage
+For **each acceptance criterion** defined in `task.md`:
 
 ### AC-X
-- **Interpretación**
-  - Cómo se entiende este criterio en el contexto actual.
-- **Verificación**
-  - Cómo se comprobará que se cumple.
-- **Riesgos / ambigüedades**
-  - Qué puede fallar o no estar claro.
+- **Interpretation**
+  - How this criterion is understood in the current context.
+- **Verification**
+  - How it will be verified that it is met.
+- **Risks / ambiguities**
+  - What could fail or is unclear.
 
-(Repetir para todos los AC)
+(Repeat for all ACs)
 
 ---
 
-## 4. Research técnico
-Análisis de alternativas y enfoques posibles.
+## 4. Technical Research
+Analysis of possible alternatives and approaches.
 
-- **Alternativa A**
-  - Descripción
-  - Ventajas
-  - Inconvenientes
-- **Alternativa B**
-  - Descripción
-  - Ventajas
-  - Inconvenientes
+- **Alternative A**
+  - Description
+  - Advantages
+  - Disadvantages
+- **Alternative B**
+  - Description
+  - Advantages
+  - Disadvantages
 
-**Decisión recomendada (si aplica)**
-- Enfoque preferido y justificación.
-- Si no se decide aún, explicar por qué.
+**Recommended decision (if applicable)**
+- Preferred approach and justification.
+- If not decided yet, explain why.
 
 ---
 
-## 5. Agentes participantes
-Lista explícita de agentes necesarios para ejecutar la tarea.
+## 5. Participating Agents
+Explicit list of agents needed to execute the task.
 
 - **Agent A**
-  - Responsabilidades
-  - Subáreas asignadas
+  - Responsibilities
+  - Assigned sub-areas
 - **Agent B**
-  - Responsabilidades
-  - Subáreas asignadas
+  - Responsibilities
+  - Assigned sub-areas
 
 **Handoffs**
-- Cómo se transfiere información o resultados entre agentes.
+- How information or results are transferred between agents.
 
-**Componentes necesarios**
-- Indicar si se requiere crear, modificar o eliminar componentes.
-- Referenciar el impacto y la dependencia con el plan de implementacion.
+**Required Components**
+- Indicate if components need to be created, modified, or deleted.
+- Reference the impact and dependency with the implementation plan.
 
-**Demo (si aplica)**
-- Indicar si se requiere crear demo.
-- Justificar necesidad y alineacion con la arquitectura del proyecto.
+**Demo (if applicable)**
+- Indicate if a demo needs to be created.
+- Justify the need and alignment with the project architecture.
 
 ---
 
-## 6. Impacto de la tarea
-Evaluación del impacto esperado si se implementa la tarea.
+## 6. Task Impact
+Assessment of the expected impact if the task is implemented.
 
-- **Arquitectura**
-  - Cambios estructurales previstos.
-- **APIs / contratos**
-  - Cambios en interfaces públicas (si aplica).
-- **Compatibilidad**
-  - Riesgos de breaking changes.
-- **Testing / verificación**
-  - Qué tipo de pruebas serán necesarias.
+- **Architecture**
+  - Planned structural changes.
+- **APIs / contracts**
+  - Changes to public interfaces (if applicable).
+- **Compatibility**
+  - Breaking change risks.
+- **Testing / verification**
+  - What types of tests will be needed.
 
 ---
 
-## 7. Riesgos y mitigaciones
-- **Riesgo 1**
-  - Impacto
-  - Mitigación
-- **Riesgo 2**
-  - Impacto
-  - Mitigación
+## 7. Risks and Mitigations
+- **Risk 1**
+  - Impact
+  - Mitigation
+- **Risk 2**
+  - Impact
+  - Mitigation
 
 ---
 
-## 8. Preguntas abiertas
-(Solo si existen; idealmente vacío tras Fase 0)
+## 8. Open Questions
+(Only if they exist; ideally empty after Phase 0)
 
-- Pregunta 1
-- Pregunta 2
+- Question 1
+- Question 2
 
 ---
 
-## 9. TODO Backlog (Consulta obligatoria)
+## 9. TODO Backlog (Mandatory Consultation)
 
 > [!IMPORTANT]
-> El architect-agent **DEBE** consultar `.agent/todo/` antes de completar el análisis.
+> The architect-agent **MUST** consult `.agent/todo/` before completing the analysis.
 
-**Referencia**: `.agent/todo/`
+**Reference**: `.agent/todo/`
 
-**Estado actual**: (vacío | N items pendientes)
+**Current state**: (empty | N pending items)
 
-**Items relevantes para esta tarea**:
-- (Listar items del backlog que impactan en la tarea actual)
-- (Si no hay items relevantes, indicar "Ninguno")
+**Items relevant to this task**:
+- (List backlog items that impact the current task)
+- (If no relevant items, indicate "None")
 
-**Impacto en el análisis**:
-- (Describir cómo los items del backlog afectan las alternativas propuestas)
+**Impact on analysis**:
+- (Describe how backlog items affect the proposed alternatives)
 
 ---
 
-## 10. Aprobación
-Este análisis **requiere aprobación explícita del desarrollador**.
+## 10. Approval
+This analysis **requires explicit developer approval**.
 
 ```yaml
 approval:
   developer:
     decision: SI | NO
     date: <ISO-8601>
-    comments: <opcional>
+    comments: <optional>
 ```
 
-> Sin aprobación, esta fase **NO puede darse por completada** ni avanzar a Phase 3.
+> Without approval, this phase **CANNOT be considered completed** nor advance to Phase 3.