@christianmaf80/agentic-workflow 1.24.0-beta.3 → 1.25.0-beta.3

package/dist/agent/workflows/tasklifecycle-long/phase-7-evaluation.md

@@ -1,6 +1,6 @@
 ---
 id: workflow.tasklifecycle-long.phase-7-evaluation
-description: Fase 7 del ciclo de tarea. Evalua la participacion de los agentes y la ejecucion de la tarea con puntuaciones objetivas.
+description: Phase 7 of the task lifecycle. Evaluates agent participation and task execution with objective scores.
 owner: architect-agent
 version: 1.0.0
 severity: PERMANENT
@@ -12,112 +12,121 @@ blocking: true
 # WORKFLOW: tasklifecycle.phase-7-evaluation
 
 ## Input (REQUIRED)
-- Existe el informe de implementacion por agente (si aplica):
+- The agent implementation report exists (if applicable):
   - `.agent/artifacts/<taskId>-<taskTitle>/<agent>/subtask-implementation.md`
-- Existe el informe de revision del arquitecto:
+- The architect's review report exists:
   - `.agent/artifacts/<taskId>-<taskTitle>/architect/review.md`
-- Existe la current task:
+- The current task exists:
   - `.agent/artifacts/<taskId>-<taskTitle>/task.md`
-- El `task.md` **DEBE** reflejar:
+- The `task.md` **MUST** reflect:
   - `task.phase.current == aliases.tasklifecycle-long.phases.phase_7.id`
 
 > [!IMPORTANT]
-> **Constitución activa (OBLIGATORIO)**:
-> - Cargar `constitution.clean_code` antes de iniciar
-> - Cargar `constitution.agents_behavior` (sección 7: Gates, sección 8: Constitución)
+> **Active constitution (MANDATORY)**:
+> - Load `constitution.clean_code` before starting
+> - Load `constitution.agents_behavior` (section 7: Gates, section 8: Constitution)
 
 ## Output (REQUIRED)
-- Crear metricas de la tarea (por agente y global):
+- Create task metrics (per agent and global):
   - `.agent/artifacts/<taskId>-<taskTitle>/metrics.md`
-- Registrar puntuaciones por agente:
+- Record per-agent scores:
   - `.agent/artifacts/<taskId>-<taskTitle>/agent-scores.md`
-- Actualizacion del estado en:
+- State update in:
   - `.agent/artifacts/<taskId>-<taskTitle>/task.md`
 
-## Objetivo (ONLY)
-- Valorar objetivamente a cada agente participante.
-- Evaluar la adecuacion del rol y la ejecucion de cada agente.
+## Objective (ONLY)
+- Objectively evaluate each participating agent.
+- Assess the role adequacy and execution of each agent.
 
-## Templates (OBLIGATORIOS)
-- Metricas de tarea:
+## Templates (MANDATORY)
+- Task metrics:
   - `templates.task_metrics`
-- Metricas globales:
+- Global metrics:
   - `templates.agent_scores`
 
 ---
 
-## Pasos obligatorios
+## Mandatory Steps
 
-0. Activar `architect-agent` y usar prefijo obligatorio en cada mensaje.
+0. Activate `architect-agent` and use the mandatory prefix in every message.
 
-1. Verificar inputs
-   - Existe `task.md`
+1. Verify inputs
+   - `task.md` exists
    - `task.phase.current == aliases.tasklifecycle-long.phases.phase_7.id`
-   - Existe `architect/review.md`
-   - Si aplica, existen subtasks por agente
-   - Si falla → ir a **Paso 8 (FAIL)**.
-
-2. Cargar templates
-   - Cargar `templates.task_metrics` y `templates.agent_scores`
-   - Si no existen o no se pueden leer → ir a **Paso 8 (FAIL)**.
-
-3. Evaluar agentes
-   - Para cada agente participante:
-     - revisar su subtask e informe de review
-     - asignar puntuacion (0-10)
-     - justificar la puntuacion
-
-4. Calcular puntuacion global de la tarea
-   - Promedio ponderado de agentes
-   - Registrar en `metrics.md`
-
-5. Registrar puntuaciones por agente
-   - Actualizar `agent-scores.md` con el score de la tarea actual
-
-6. Solicitar feedback y puntuación obligatoria del desarrollador (por consola)
-   - Presentar `metrics.md` al usuario.
-   - Solicitar confirmación explícita (SI/NO).
-   - Solicitar puntuación del desarrollador (1-10) para CADA agente participante.
-   - **GATE OBLIGATORIO**: Sin estas puntuaciones, la tarea NO puede cerrarse.
-   - Si respuesta es NO → ir a **Paso 8 (FAIL)**.
+   - `architect/review.md` exists
+   - If applicable, agent subtasks exist
+   - If it fails → go to **Step 8 (FAIL)**.
+
+2. Load templates
+   - Load `templates.task_metrics` and `templates.agent_scores`
+   - If they do not exist or cannot be read → go to **Step 8 (FAIL)**.
+
+3. Evaluate agents
+   - For each participating agent:
+     - review their subtask and review report
+     - assign score (0-10)
+     - justify the score
+
+4. Calculate global task score
+   - Weighted average of agents
+   - Record in `metrics.md`
+
+5. Record per-agent scores
+   - Update `agent-scores.md` with the current task's score
+
+6. Request mandatory developer feedback and scoring (via console)
+   - Present `metrics.md` to the user.
+   - Request explicit confirmation (SI/NO).
+   - Request developer score (1-10) for EACH participating agent.
+   - **MANDATORY GATE**: Without these scores, the task CANNOT be closed.
+   - If response is NO → go to **Step 8 (FAIL)**.
 
 7. PASS
-   - Registrar validación en `metrics.md`.
-   - Actualizar `.agent/artifacts/<taskId>-<taskTitle>/task.md`:
-     - marcar Fase 7 como completada
-     - establecer `task.lifecycle.phases.phase-7-evaluation.validated_at = <ISO-8601>`
-     - actualizar `task.phase.updated_at = <ISO-8601>`
-     - avanzar `task.phase.current = aliases.tasklifecycle-long.phases.phase_8.id`
+   - Report that Phase 7 is correctly completed.
+   - Record validation in `metrics.md`.
+   - The `architect-agent` **MUST explicitly perform** the following actions:
+     - Mark Phase 7 as completed in `task.md`.
+     - Set `task.lifecycle.phases.phase-7-evaluation.completed = true`.
+     - Set `task.lifecycle.phases.phase-7-evaluation.validated_at = <ISO-8601>`.
+     - Update `task.phase.updated_at = <ISO-8601>`.
+     - Update the state:
+       - `task.phase.current = aliases.tasklifecycle-long.phases.phase_8.id`
+   - This update is **NOT automatic** and **CANNOT be inferred**.
+   - Until this change is reflected in `task.md`, **Phase 8 cannot be started**.
+   - Indicate paths:
+     - `metrics.md`
+     - `agent-scores.md`
+     - `task.md` updated
 
 ---
 
-## FAIL (OBLIGATORIO)
+## FAIL (MANDATORY)
 
-8. Declarar Fase 7 como **NO completada**
-   - Casos de FAIL:
-     - fase incorrecta
-     - faltan informes requeridos
-     - no se pudieron crear metricas
-     - desarrollador rechaza la evaluación
-   - Accion minima: corregir inputs y reintentar
-   - Terminar bloqueado: no avanzar de fase.
+8. Declare Phase 7 as **NOT completed**
+   - FAIL cases:
+     - incorrect phase
+     - missing required reports
+     - could not create metrics
+     - developer rejects the evaluation
+   - Minimum action: fix inputs and retry
+   - Terminate blocked: do not advance phase.
 
 ---
 
 ## Gate (REQUIRED)
 
-Requisitos (todos obligatorios):
-1. Existe `.agent/artifacts/<taskId>-<taskTitle>/metrics.md`.
-2. El `metrics.md` inicia con el prefijo del `architect-agent`.
-3. `metrics.md` contiene la validación del desarrollador (`Aprobado: SI`).
-4. `metrics.md` contiene la puntuación del desarrollador (0-5).
-5. Existe `.agent/artifacts/<taskId>-<taskTitle>/agent-scores.md` actualizado.
-6. `task.md` refleja:
-   - Fase 7 completada
+Requirements (all mandatory):
+1. `.agent/artifacts/<taskId>-<taskTitle>/metrics.md` exists.
+2. The `metrics.md` starts with the `architect-agent` prefix.
+3. `metrics.md` contains the developer's validation (`Approved: SI`).
+4. `metrics.md` contains the developer's score (0-5).
+5. `.agent/artifacts/<taskId>-<taskTitle>/agent-scores.md` updated exists.
+6. `task.md` reflects:
+   - Phase 7 completed
    - `task.phase.current == aliases.tasklifecycle-long.phases.phase_8.id`
    - `task.lifecycle.phases.phase-7-evaluation.completed == true`
-   - `task.lifecycle.phases.phase-7-evaluation.validated_at` no nulo
-   - `task.phase.updated_at` no nulo
+   - `task.lifecycle.phases.phase-7-evaluation.validated_at` not null
+   - `task.phase.updated_at` not null
 
-Si Gate FAIL:
-- Ejecutar **Paso 8 (FAIL)**.
+If Gate FAIL:
+- Execute **Step 8 (FAIL)**.

package/dist/agent/workflows/tasklifecycle-long/phase-8-commit-push.md

@@ -1,6 +1,6 @@
 ---
 id: workflow.tasklifecycle-long.phase-8-commit-push
-description: Fase 8 del ciclo de tarea. Consolida y publica los cambios en la rama destino mediante commits normalizados (Conventional Commits), genera changelog y requiere aprobación explícita del desarrollador antes del push final.
+description: Phase 8 of the task lifecycle. Consolidates and publishes changes to the target branch via normalized commits (Conventional Commits), generates changelog, and requires explicit developer approval before final push.
 owner: architect-agent
 version: 1.0.0
 severity: PERMANENT
@@ -12,126 +12,131 @@ blocking: true
 # WORKFLOW: tasklifecycle.phase-8-commit-push
 
 ## Input (REQUIRED)
-- Existe el informe de evaluacion de agentes:
+- The agent evaluation report exists:
   - `.agent/artifacts/<taskId>-<taskTitle>/metrics.md`
-- Existe la current task:
+- The current task exists:
   - `.agent/artifacts/<taskId>-<taskTitle>/task.md`
-- El `task.md` **DEBE** reflejar:
+- The `task.md` **MUST** reflect:
   - `task.phase.current == aliases.tasklifecycle-long.phases.phase_8.id`
 
 > [!IMPORTANT]
-> **Constitución activa (OBLIGATORIO)**:
-> - Cargar `constitution.clean_code` antes de iniciar
-> - Cargar `constitution.agents_behavior` (sección 7: Gates, sección 8: Constitución)
+> **Active constitution (MANDATORY)**:
+> - Load `constitution.clean_code` before starting
+> - Load `constitution.agents_behavior` (section 7: Gates, section 8: Constitution)
 
 ## Output (REQUIRED)
-- Crear changelog:
+- Create changelog:
   - `.agent/artifacts/<taskId>-<taskTitle>/changelog.md`
-- Actualizacion del estado en:
+- State update in:
   - `.agent/artifacts/<taskId>-<taskTitle>/task.md`
 
-## Reglas de commits
-Ejemplos válidos:
+## Commit Rules
+Valid examples:
 - `feat(core): add caching layer`
 - `fix(core): handle cache eviction`
 - `refactor(workflows): normalize tasklifecycle phases`
-- No se permiten:
-- mensajes genéricos (`update`, `changes`, `fix stuff`)
-- commits sin scope
-- commits que mezclen cambios no relacionados
+- Not allowed:
+- generic messages (`update`, `changes`, `fix stuff`)
+- commits without scope
+- commits that mix unrelated changes
 
 ---
 
-## Pasos obligatorios
+## Mandatory Steps
 
-0. Activar `architect-agent` y usar prefijo obligatorio en cada mensaje.
+0. Activate `architect-agent` and use the mandatory prefix in every message.
 
-1. Verificar inputs
- - Existe `metrics.md` y contiene `Aprobado: SI`.
- - Existe `task.md`.
+1. Verify inputs
+ - `metrics.md` exists and contains `Approved: SI`.
+ - `task.md` exists.
  - `task.phase.current == aliases.tasklifecycle-long.phases.phase_8.id`
- - Si falla → ir a **Paso 10 (FAIL)**.
-
-2. Preparar commits
- - Revisar `git status` y `git diff`.
- - Agrupar cambios de forma lógica.
- - Definir número y alcance de commits.
-
-3. Crear commits (OBLIGATORIO)
- - Ejecutar commits siguiendo **Conventional Commits**.
- - Cada commit **DEBE**:
-   - tener propósito claro
-   - mapear a cambios reales
- - Si algún commit no cumple el formato → **FAIL**.
-
-4. Generar changelog (OBLIGATORIO)
- - Crear:
+ - If it fails → go to **Step 10 (FAIL)**.
+
+2. Prepare commits
+ - Review `git status` and `git diff`.
+ - Group changes logically.
+ - Define number and scope of commits.
+
+3. Create commits (MANDATORY)
+ - Execute commits following **Conventional Commits**.
+ - Each commit **MUST**:
+   - have a clear purpose
+   - map to actual changes
+ - If any commit does not follow the format → **FAIL**.
+
+4. Generate changelog (MANDATORY)
+ - Create:
    - `.agent/artifacts/<taskId>-<taskTitle>/changelog.md`
- - El changelog **DEBE** incluir:
-   - lista de commits
-   - mensaje completo de cada commit
-   - resumen funcional del cambio
-
-5. Solicitar aprobación del desarrollador (OBLIGATORIA, por consola)
- - El desarrollador **DEBE** aprobar explícitamente:
-   - el contenido de los commits
-   - el push a la rama destino
- - Decisión binaria:
-   - **SI** → continuar
-   - **NO** → ir a **Paso 10 (FAIL)**
-
-6. Push a la rama destino
- - Ejecutar:
+ - The changelog **MUST** include:
+   - list of commits
+   - full message of each commit
+   - functional summary of the change
+
+5. Request developer approval (MANDATORY, via console)
+ - The developer **MUST** explicitly approve:
+   - the commit contents
+   - the push to the target branch
+ - Binary decision:
+   - **SI** → continue
+   - **NO** → go to **Step 10 (FAIL)**
+
+6. Push to target branch
+ - Execute:
    ```bash
    git push <remote> <branch>
    ```
- - Confirmar que el push fue exitoso.
+ - Confirm that the push was successful.
 
 7. PASS
- - Actualizar `.agent/artifacts/<taskId>-<taskTitle>/task.md`:
-   - marcar Fase 8 como completada
-   - establecer `task.lifecycle.phases.phase-8-commit-push.validated_at = <ISO-8601>`
-   - actualizar `task.phase.updated_at = <ISO-8601>`
-   - marcar la tarea como **técnicamente cerrada**
- - Indicar:
-   - rama destino
-   - referencia de commits
+ - Report that Phase 8 is correctly completed.
+ - The `architect-agent` **MUST explicitly perform** the following actions:
+   - Mark Phase 8 as completed in `task.md`.
+   - Set `task.lifecycle.phases.phase-8-commit-push.completed = true`.
+   - Set `task.lifecycle.phases.phase-8-commit-push.validated_at = <ISO-8601>`.
+   - Update `task.phase.updated_at = <ISO-8601>`.
+   - Mark the task as **technically closed**.
+ - This update is **NOT automatic** and **CANNOT be inferred**.
+ - Indicate:
+   - target branch
+   - commit references
+   - `changelog.md`
+   - `task.md` updated
 
 ---
 
-## FAIL (OBLIGATORIO)
-
-10. Declarar Fase 8 como **NO completada**
-  - Casos de FAIL:
-    - resultados no aprobados
-    - fase incorrecta
-    - commit no cumple Conventional Commits
-    - changelog inexistente o incompleto
-    - desarrollador no aprueba commit/push
-    - fallo en `git push`
-  - Acciones obligatorias:
-    - corregir mensajes de commit
-    - reestructurar commits
-    - actualizar changelog
-    - volver a solicitar aprobación
-  - Terminar bloqueado: no avanzar.
+## FAIL (MANDATORY)
+
+10. Declare Phase 8 as **NOT completed**
+  - FAIL cases:
+    - results not approved
+    - incorrect phase
+    - commit does not follow Conventional Commits
+    - non-existent or incomplete changelog
+    - developer does not approve commit/push
+    - `git push` failure
+  - Mandatory actions:
+    - fix commit messages
+    - restructure commits
+    - update changelog
+    - request approval again
+  - Terminate blocked: do not advance.
 
 ---
 
 ## Gate (REQUIRED)
 
-Requisitos (todos obligatorios):
-1. Todos los commits cumplen **Conventional Commits**.
-2. Existe `.agent/artifacts/<taskId>-<taskTitle>/changelog.md`.
-3. El desarrollador ha aprobado explícitamente commit y push.
-4. Working tree limpio (`git status` sin cambios).
-5. Los cambios están correctamente subidos a la rama destino.
-6. `task.md` refleja:
- - Fase 8 completada
- - Tarea cerrada técnicamente
+Requirements (all mandatory):
+1. All commits follow **Conventional Commits**.
+2. `.agent/artifacts/<taskId>-<taskTitle>/changelog.md` exists.
+3. The developer has explicitly approved commit and push.
+4. Clean working tree (`git status` with no changes).
+5. Changes are correctly pushed to the target branch.
+6. `task.md` reflects:
+ - Phase 8 completed
+ - Task technically closed
  - `task.lifecycle.phases.phase-8-commit-push.completed == true`
- - `task.lifecycle.phases.phase-8-commit-push.validated_at` no nulo
- - `task.phase.updated_at` no nulo
+ - `task.lifecycle.phases.phase-8-commit-push.validated_at` not null
+ - `task.phase.updated_at` not null
 
-Si Gate FAIL:
-- Ejecutar **Paso 10 (FAIL)**.
+If Gate FAIL:
+- Execute **Step 10 (FAIL)**.

package/dist/agent/workflows/tasklifecycle-short/short-phase-1-brief.md

@@ -1,6 +1,6 @@
 ---
 id: workflow.tasklifecycle-short.short-phase-1-brief
-description: Fase 1 del ciclo Short. Fusiona Acceptance + Analysis + Planning. Incluye 5 preguntas obligatorias y detección de complejidad.
+description: Phase 1 of the Short lifecycle. Merges Acceptance + Analysis + Planning. Includes 5 mandatory questions and complexity detection.
 owner: architect-agent
 version: 1.0.0
 severity: PERMANENT
@@ -12,99 +12,106 @@ blocking: true
 # WORKFLOW: tasklifecycle-short.short-phase-1-brief
 
 ## Input (REQUIRED)
-- Existe task candidate con `task.strategy: short`.
-- El desarrollador ha proporcionado título y objetivo.
+- Task candidate exists with `task.strategy: short`.
+- The developer has provided a title and objective.
 
 > [!IMPORTANT]
-> **Constitución activa (OBLIGATORIO)**:
-> - Cargar `constitution.clean_code` antes de iniciar
-> - Cargar `constitution.agents_behavior` (sección 7: Gates, sección 8: Constitución)
-> - **Activar `skill.runtime-governance`** (Para validación de gate y trazabilidad por el Architect)
+> **Active constitution (MANDATORY)**:
+> - Load `constitution.clean_code` before starting
+> - Load `constitution.agents_behavior` (section 7: Gates, section 8: Constitution)
 
 ## Output (REQUIRED)
-- Artefacto: `.agent/artifacts/<taskId>-<taskTitle>/brief.md`
-- Artefacto: `.agent/artifacts/<taskId>-<taskTitle>/acceptance.md` (NUEVO)
-- Task actualizado con fase actual = `short-phase-1-brief`
+- Artifact: `.agent/artifacts/<taskId>-<taskTitle>/brief.md`
+- Artifact: `.agent/artifacts/<taskId>-<taskTitle>/acceptance.md` (NEW)
+- Task updated with current phase = `short-phase-1-brief`
 
-## Objetivo (ONLY)
-- Ejecutar las **5 preguntas obligatorias** para definir acceptance criteria.
-- Realizar un **análisis profundo** para detectar complejidad.
-- Crear un **plan simplificado** de implementación.
-- Si se detecta complejidad alta, **ofrecer abortar** y reiniciar en modo Long.
+## Objective (ONLY)
+- Execute the **5 mandatory questions** to define acceptance criteria.
+- Perform a **deep analysis** to detect complexity.
+- Create a **simplified implementation plan**.
+- If high complexity is detected, **offer to abort** and restart in Long mode.
 
-> Esta fase **NO implementa código**.  
-> Esta fase **REQUIERE aprobación explícita del desarrollador (SI/NO)**.
+> This phase **DOES NOT implement code**.  
+> This phase **REQUIRES explicit developer approval (SI/NO)**.
 
 ---
 
-## Pasos obligatorios
+## Mandatory Steps
 
-0. Activar `architect-agent` y usar prefijo obligatorio en cada mensaje.
+0. Activate `architect-agent` and use the mandatory prefix in every message.
 
-### 1. Verificar inputs
-- Existe task candidate.
+### 1. Verify inputs
+- Task candidate exists.
 - `task.strategy == "short"`.
-- Si falla → **FAIL**.
-
-### 2. Ejecutar 5 preguntas obligatorias
-El architect-agent **DEBE** formular 5 preguntas específicas basadas en la tarea:
-- Las preguntas varían según la tarea concreta.
-- Sin respuestas completas, la fase NO avanza.
-
-### 3. Análisis de complejidad
-Evaluar indicadores de complejidad:
-- ¿Afecta más de 3 paquetes/módulos? → Alta
-- ¿Requiere investigación de APIs externas? → Alta
-- ¿Introduce cambios breaking? → Alta
-- ¿Necesita tests E2E complejos? → Alta
-
-**Si complejidad es ALTA**:
-- Notificar al desarrollador.
-- Ofrecer opción de abortar y crear nueva tarea en modo Long.
-- Si decide abortar → terminar fase con estado "aborted".
-### 4. Crear artefactos (brief.md y acceptance.md)
-- Usar templates `templates.brief` y `templates.acceptance`.
-- En `acceptance.md` incluir:
-  - Acceptance criteria derivados de las 5 preguntas.
-- En `brief.md` incluir:
-  - Análisis simplificado del estado actual.
-  - Plan de implementación con pasos ejecutables.
-  - Evaluación de complejidad.
-  - **Evaluación de Agentes**: Desempeño y propuestas de mejora.
-
-### 5. Solicitar aprobación del desarrollador (por consola)
+- If it fails → **FAIL**.
+
+### 2. Execute 5 mandatory questions
+The architect-agent **MUST** formulate 5 specific questions based on the task:
+- Questions vary depending on the specific task.
+- Without complete answers, the phase DOES NOT advance.
+
+### 3. Complexity analysis
+Evaluate complexity indicators:
+- Does it affect more than 3 packages/modules? → High
+- Does it require external API research? → High
+- Does it introduce breaking changes? → High
+- Does it need complex E2E tests? → High
+
+**If complexity is HIGH**:
+- Notify the developer.
+- Offer the option to abort and create a new task in Long mode.
+- If the developer decides to abort → terminate the phase with "aborted" status.
+### 4. Create artifacts (brief.md and acceptance.md)
+- Use templates `templates.brief` and `templates.acceptance`.
+- In `acceptance.md` include:
+  - Acceptance criteria derived from the 5 questions.
+- In `brief.md` include:
+  - Simplified analysis of the current state.
+  - Implementation plan with executable steps.
+  - Complexity evaluation.
+  - **Agent Evaluation**: Performance and improvement proposals.
+
+### 5. Request developer approval (via console)
 ```yaml
 approval:
   developer:
     decision: SI | NO
     date: <ISO-8601>
-    comments: <opcional>
+    comments: <optional>
 ```
-- Si `decision != SI` → **FAIL**.
+- If `decision != SI` → **FAIL**.
 
 ### 6. PASS
-- Actualizar task.md:
-  - Marcar fase como completada.
-  - Establecer `task.lifecycle.phases.short-phase-1-brief.validated_at = <ISO-8601>`.
-  - Actualizar `task.phase.updated_at = <ISO-8601>`.
-  - Avanzar a `short-phase-2-implementation`.
+- Report that Phase 1 (Brief) is correctly completed.
+- The `architect-agent` **MUST explicitly perform** the following actions:
+  - Mark the phase as completed in `task.md`.
+  - Set `task.lifecycle.phases.short-phase-1-brief.completed = true`.
+  - Set `task.lifecycle.phases.short-phase-1-brief.validated_at = <ISO-8601>`.
+  - Update `task.phase.updated_at = <ISO-8601>`.
+  - Update the state:
+    - `task.phase.current = short-phase-2-implementation`
+- This update is **NOT automatic** and **CANNOT be inferred**.
+- Until this change is reflected in `task.md`, **Phase 2 cannot be started**.
+- Indicate paths:
+  - `brief.md`
+  - `acceptance.md`
+  - `task.md` updated
 
 ---
 
 ## Gate (REQUIRED)
-Requisitos (todos obligatorios):
-1. Existen `brief.md` y `acceptance.md` con templates correctos.
-2. El `brief.md` inicia con el prefijo del `architect-agent`.
-3. Las 5 preguntas están respondidas.
-4. La evaluación de complejidad está documentada.
-5. Existe aprobación explícita del desarrollador.
-6. task.md refleja fase completada.
-7. task.md refleja timestamp y estado:
+Requirements (all mandatory):
+1. `brief.md` and `acceptance.md` exist with correct templates.
+2. The `brief.md` starts with the `architect-agent` prefix.
+3. All 5 questions have been answered.
+4. The complexity evaluation is documented.
+5. Explicit developer approval exists.
+6. task.md reflects the phase as completed.
+7. task.md reflects timestamp and state:
    - `task.lifecycle.phases.short-phase-1-brief.completed == true`
-   - `task.lifecycle.phases.short-phase-1-brief.validated_at` no nulo
-   - `task.phase.updated_at` no nulo
-8. **Gobernanza verificada**: El historial de logs muestra la secuencia de herramientas MCP definida en `skill.runtime-governance`.
+   - `task.lifecycle.phases.short-phase-1-brief.validated_at` not null
+   - `task.phase.updated_at` not null
 
-Si Gate FAIL:
-- Indicar qué requisito falta.
-- Bloquear hasta resolver.
+If Gate FAIL:
+- Indicate which requirement is missing.
+- Block until resolved.