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

package/dist/agent/templates/brief.md

@@ -0,0 +1,96 @@
+---
+artifact: brief
+phase: short-phase-1-brief
+owner: architect-agent
+status: draft | approved
+related_task: <taskId>-<taskTitle>
+---
+
+# Brief — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+
+## 1. Task Identification
+
+**Title**: <task title>
+**Objective**: <main objective>
+**Strategy**: Short
+
+---
+
+## 2. The 5 Mandatory Questions
+
+| # | Question (formulated by architect) | Answer (from developer) |
+|---|-----------------------------------|------------------------|
+| 1 | | |
+| 2 | | |
+| 3 | | |
+| 4 | | |
+| 5 | | |
+
+---
+
+## 3. Acceptance Criteria
+
+Derived from the previous answers:
+
+1. **Scope**: 
+2. **Inputs/Data**: 
+3. **Expected Outputs**: 
+4. **Constraints**: 
+5. **Done Criterion**: 
+
+---
+
+## 4. Simplified Analysis
+
+### Current State (As-Is)
+- Affected structure:
+- Known limitations:
+
+### Complexity Evaluation
+
+| Indicator | Status | Comment |
+|-----------|--------|---------|
+| Affects more than 3 packages | ☐ Yes ☐ No | |
+| Requires API research | ☐ Yes ☐ No | |
+| Breaking changes | ☐ Yes ☐ No | |
+| Complex E2E tests | ☐ Yes ☐ No | |
+
+**Complexity result**: ☐ LOW (continue Short) ☐ HIGH (recommend abort to Long)
+
+---
+
+## 5. Implementation Plan
+
+### Ordered Steps
+
+1. **Step 1**
+   - Description:
+   - Deliverables:
+
+2. **Step 2**
+   - Description:
+   - Deliverables:
+
+(Add more steps as needed)
+
+### Planned Verification
+- Test type:
+- Success criteria:
+
+---
+
+## 6. Developer Approval (MANDATORY)
+
+```yaml
+approval:
+  developer:
+    decision: SI | NO
+    date: <ISO-8601>
+    comments: <optional>
+```
+
+> Without approval, this phase CANNOT advance to Implementation.

package/dist/agent/templates/changelog.md

@@ -9,18 +9,18 @@ target_branch: <branch-name>
 
 # Changelog — <taskId>-<taskTitle>
 
-## 1. Resumen general
-Descripción breve y clara de los cambios introducidos por esta tarea.
+## 1. General Summary
+Brief and clear description of the changes introduced by this task.
 
-- **Objetivo de la tarea**:
-- **Impacto principal**:
-- **Áreas afectadas** (componentes, workflows, etc.):
+- **Task objective**:
+- **Main impact**:
+- **Affected areas** (components, workflows, etc.):
 
 ---
 
-## 2. Commits incluidos
-Listado completo y ordenado de los commits realizados.
+## 2. Included Commits
+Complete and ordered list of commits performed.
 
 ### Commit 1
 - **Hash**: `<commit-hash>`
-- **Mensaje (Conventional Commit)**:
+- **Message (Conventional Commit)**:

package/dist/agent/templates/closure.md

@@ -0,0 +1,95 @@
+---
+artifact: closure
+phase: short-phase-3-closure
+owner: architect-agent
+status: draft | approved
+related_task: <taskId>-<taskTitle>
+---
+
+# Closure — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+
+## 1. Task Summary
+
+**Title**: <title>
+**Strategy**: Short
+**Final status**: ☐ Completed ☐ Aborted
+
+---
+
+## 2. Verification
+
+### Tests Executed
+
+| Type | Command/Method | Result |
+|------|---------------|--------|
+| Unit | | ☐ Pass ☐ Fail ☐ N/A |
+| Integration | | ☐ Pass ☐ Fail ☐ N/A |
+| E2E | | ☐ Pass ☐ Fail ☐ N/A |
+
+### Justification (if no tests)
+<Explain why tests do not apply>
+
+---
+
+## 3. Acceptance Criteria Status
+
+| AC | Description | Status |
+|----|-------------|--------|
+| 1 | | ☐ ✅ ☐ ❌ |
+| 2 | | ☐ ✅ ☐ ❌ |
+| 3 | | ☐ ✅ ☐ ❌ |
+| 4 | | ☐ ✅ ☐ ❌ |
+| 5 | | ☐ ✅ ☐ ❌ |
+
+---
+
+## 4. Changes Made
+
+### Files Modified/Created
+
+| File | Action | Description |
+|------|--------|-------------|
+| | Created/Modified/Deleted | |
+
+### Commits (if applicable)
+
+```
+<type>(<scope>): <description>
+```
+
+---
+
+## 5. Final Developer Acceptance (MANDATORY)
+
+```yaml
+approval:
+  developer:
+    decision: SI | NO
+    date: <ISO-8601>
+    comments: <optional>
+```
+
+> Without acceptance, the task CANNOT be marked as completed.
+
+---
+
+## 6. Agent Scores (MANDATORY)
+
+| Agent | Score (1-10) | Notes |
+|-------|-------------|-------|
+| | | |
+
+---
+
+## 7. Final Push (if applicable)
+
+```yaml
+push:
+  approved: SI | NO
+  branch: <target branch>
+  date: <ISO-8601>
+```

package/dist/agent/templates/coding/coding-integration-report.md

@@ -0,0 +1,102 @@
+---
+artifact: coding_integration_report
+phase: phase-4-implementation
+owner: architect-agent
+status: draft | completed
+related_task: "{{taskId}}-{{taskTitle}}"
+---
+
+# Coding Integration Report — {{taskId}}-{{taskTitle}}
+
+## 1. Layer Reports Summary
+
+| Layer | Agent | Status | Gate |
+|-------|-------|--------|------|
+| Backend | {{backend_agent}} | {{status}} | SI / NO / N/A |
+| Background | {{background_agent}} | {{status}} | SI / NO / N/A |
+| View | {{view_agent}} | {{status}} | SI / NO / N/A |
+
+---
+
+## 2. Communication Validation Matrix
+
+| Path | Method | Contract | Status |
+|------|--------|----------|--------|
+| View → Background | `core/messaging` Event Bus | `Message` interface | ✅ / ❌ |
+| Background → Backend | Abstract transport / direct | Structured response | ✅ / ❌ |
+| Background → View | `core/messaging` response | `Message` interface | ✅ / ❌ |
+| View → Backend | **FORBIDDEN** | N/A | ✅ (no path) / ❌ (violation) |
+
+### Validation Details
+- (Describe each communication path validated)
+- (Note any deviations or issues found and how they were resolved)
+
+---
+
+## 3. Constitution Compliance
+
+### Backend (`constitution.backend`)
+- [ ] Extends `AbstractServer`
+- [ ] No `vscode` or `dom` imports
+- [ ] Transport agnostic
+- [ ] Structured error handling
+- [ ] No direct View communication
+
+### Background (`constitution.background`)
+- [ ] Registered via `App.register()`
+- [ ] Uses `core/messaging` for View communication
+- [ ] Manages lifecycle correctly
+- [ ] Gateway role maintained
+
+### View (`constitution.view`)
+- [ ] Lit with `@customElement`
+- [ ] Triad structure (index/html/styles)
+- [ ] No business logic
+- [ ] Communication via Messaging wrapper
+
+---
+
+## 4. Cross-Layer Sequence Diagrams
+
+> Include mermaid sequence diagrams for key integration flows.
+
+```mermaid
+sequenceDiagram
+    participant V as View
+    participant B as Background
+    participant BE as Backend
+
+    V->>B: Message (Event Bus)
+    B->>BE: Request (Transport)
+    BE-->>B: Response (Structured)
+    B-->>V: State Update (Messaging)
+```
+
+---
+
+## 5. E2E Test Indications
+
+### Integration Scenarios
+- (List end-to-end scenarios that validate the full flow across layers)
+
+### Test Setup
+- (Prerequisites, extension host configuration, fixtures)
+
+### Key Assertions
+- (What to verify at each layer boundary)
+- (Expected UI behavior after full round-trip)
+
+---
+
+## 6. Issues and Resolutions
+
+| Issue | Layer | Severity | Resolution |
+|-------|-------|----------|------------|
+| (description) | (backend/background/view) | (critical/warning) | (action taken) |
+
+---
+
+## 7. Final Assessment
+- **Integration status**: PASS | FAIL
+- **Constitution compliance**: FULL | PARTIAL
+- **Ready for Phase 5 (Verification)**: YES | NO

package/dist/agent/templates/coding/coding-layer-report.md

@@ -0,0 +1,78 @@
+---
+artifact: coding_layer_report
+phase: phase-4-implementation
+owner: "{{agent}}"
+status: draft | completed
+related_task: "{{taskId}}-{{taskTitle}}"
+layer: "{{layer}}"
+---
+
+# Coding Layer Report — {{layer}} — {{taskId}}-{{taskTitle}}
+
+## 1. Who (Agent Identity)
+- **Agent**: {{agent}}
+- **Role**: {{role}} (`roles.{{layer}}`)
+- **Constitution**: `constitution.{{layer}}` + `constitution.clean_code`
+
+---
+
+## 2. How (Technical Details)
+
+### Changes Implemented
+- **Files created/modified**: (list with paths)
+- **APIs/contracts affected**: (interfaces, types, exports)
+- **New functions/classes**: (names and purpose)
+
+### Technical Specifications
+- (Detailed description of implementation approach)
+- (Architecture decisions and patterns used)
+
+### Diagrams
+> Include mermaid diagrams when the implementation involves:
+> - New communication flows
+> - State transitions
+> - Component relationships
+> - Data flow
+
+```mermaid
+graph TD
+    A[Component] --> B[Dependency]
+```
+
+---
+
+## 3. Why (Justification)
+- **Objective**: (What problem does this solve?)
+- **Reasoning**: (Why this approach over alternatives?)
+- **Alternatives discarded**: (Brief description and reason)
+
+---
+
+## 4. Results
+
+### Compilation
+- `npm run compile`: PASS | FAIL
+- Errors resolved: (list if any)
+
+### Self-Validation Checklist
+> Copy the checklist from the workflow and mark each item.
+
+### Code Quality
+- Clean code compliance: YES | NO
+- Constitution compliance: YES | NO
+
+---
+
+## 5. E2E Test Indications
+
+### Required Test Scenarios
+- (List scenarios that should be covered by e2e tests)
+
+### Test Setup
+- (Prerequisites, fixtures, or mock data needed)
+
+### Assertions
+- (Expected behaviors to verify per scenario)
+
+### Integration Points
+- (How this layer connects to others — what to test at boundaries)

package/dist/agent/templates/init.md

@@ -1,14 +1,7 @@
----
-id: task.init
-title: Initialization
-owner: "architect-agent"
-phase:
-  current: init
----
 # init bootstrap
 
 - command: {{command}}
-- role.architect: architect-agent
+- role.architect: {{architectAgentId}}
 - constitution.loaded.in_context: true
 
 ## Constitution (load order)
@@ -20,23 +13,9 @@ phase:
 bootstrap:
   done: true
 roles:
-  architect: architect-agent
+  architect: {{architectAgentId}}
 constitution:
   loaded:
     - {{constitutionPaths[0]}}
     - {{constitutionPaths[1]}}
     - {{constitutionPaths[2]}}
-language:
-  value: {{language}}
-  confirmed: {{languageConfirmed}}
-strategy: {{strategy}}
-traceability:
-  verified: {{traceabilityVerified}}
-  mcp_tool: {{traceabilityTool}}
-  response: {{traceabilityResponse}}
-  timestamp: {{traceabilityTimestamp}}
-runtime:
-  started: {{runtimeStarted}}
-task:
-  path:
-    "{{taskId}}": "{{taskPath}}"

package/dist/agent/templates/planning.md

@@ -8,23 +8,23 @@ related_task: <taskId>-<taskTitle>
 
 # Implementation Plan — <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 del plan
-- **Contexto**: breve recordatorio del objetivo de la tarea.
-- **Resultado esperado**: qué quedará implementado al finalizar.
-- **Alcance**: qué incluye y qué excluye explícitamente este plan.
+## 1. Plan Summary
+- **Context**: brief reminder of the task objective.
+- **Expected result**: what will be implemented upon completion.
+- **Scope**: what this plan explicitly includes and excludes.
 
 ---
 
-## 2. Inputs contractuales
+## 2. Contractual Inputs
 - **Task**: `.agent/artifacts/<taskId>-<taskTitle>/task.md`
 - **Analysis**: `.agent/artifacts/<taskId>-<taskTitle>/analysis.md`
-- **Acceptance Criteria**: referencia explícita a los AC relevantes.
+- **Acceptance Criteria**: explicit reference to the relevant ACs.
 
-**Dispatch de dominios (OBLIGATORIO si aplica)**
+**Domain dispatch (MANDATORY if applicable)**
 ```yaml
 plan:
   workflows:
@@ -40,116 +40,116 @@ plan:
 
 ---
 
-## 3. Desglose de implementación (pasos)
-Descomposición ordenada y ejecutable.
+## 3. Implementation Breakdown (steps)
+Ordered and executable decomposition.
 
-### Paso 1
-- **Descripción**
-- **Dependencias**
-- **Entregables**
-- **Agente responsable**
+### Step 1
+- **Description**
+- **Dependencies**
+- **Deliverables**
+- **Responsible agent**
 
-### Paso 2
-- (Repetir estructura)
+### Step 2
+- (Repeat structure)
 
-> Nota: indicar orden, dependencias y paralelización si aplica.
+> Note: indicate order, dependencies, and parallelization if applicable.
 
 ---
 
-## 4. Asignación de responsabilidades (Agentes)
-Mapa claro de agentes ↔ subáreas.
+## 4. Responsibility Assignment (Agents)
+Clear mapping of agents ↔ sub-areas.
 
 - **Architect-Agent**
-  - Responsabilidades
+  - Responsibilities
 - **Implementation-Agent**
-  - Responsabilidades
-- **QA / Verification-Agent** (si aplica)
-  - Responsabilidades
-- **Otros agentes** (si aplica)
+  - Responsibilities
+- **QA / Verification-Agent** (if applicable)
+  - Responsibilities
+- **Other agents** (if applicable)
 
 **Handoffs**
-- Qué se entrega, a quién y cuándo.
+- What is delivered, to whom, and when.
 
-**Componentes (si aplica)**
-- Definir quién lo ejecuta.
-- Definir cómo se implementa (pasos y criterios).
-- Definir la mejor herramienta disponible (preferir tools declarados; si no existe, justificar alternativa).
-- Referenciar el tool elegido por alias y el motivo.
+**Components (if applicable)**
+- Define who executes it.
+- Define how it is implemented (steps and criteria).
+- Define the best available tool (prefer declared tools; if none exists, justify alternative).
+- Reference the chosen tool by alias and the reason.
 
-**Demo (si aplica)**
-- Definir estructura esperada alineada con la arquitectura del proyecto.
-- Definir tool obligatorio para generar scaffolding (si existe).
+**Demo (if applicable)**
+- Define expected structure aligned with the project architecture.
+- Define mandatory tool for scaffolding generation (if it exists).
 
 ---
 
-## 5. Estrategia de testing y validación
-Cómo se comprobará que la implementación cumple los AC.
+## 5. Testing and Validation Strategy
+How it will be verified that the implementation meets the ACs.
 
 - **Unit tests**
-  - Alcance y herramientas
+  - Scope and tools
 - **Integration tests**
-  - Flujos cubiertos
+  - Flows covered
 - **E2E / Manual**
-  - Escenarios clave
+  - Key scenarios
 
-**Trazabilidad**
-- Mapeo de tests ↔ acceptance criteria.
+**Traceability**
+- Mapping of tests ↔ acceptance criteria.
 
 ---
 
-## 6. Plan de demo (si aplica)
-- **Objetivo de la demo**
-- **Escenario(s)**
-- **Datos de ejemplo**
-- **Criterios de éxito de la demo**
+## 6. Demo Plan (if applicable)
+- **Demo objective**
+- **Scenario(s)**
+- **Example data**
+- **Demo success criteria**
 
 ---
 
-## 7. Estimaciones y pesos de implementación
-- **Estimación por paso / subárea**
-  - esfuerzo relativo (bajo / medio / alto o puntos)
-- **Timeline aproximado** (si aplica)
-- **Suposiciones** usadas para estimar
+## 7. Estimations and Implementation Weights
+- **Estimation per step / sub-area**
+  - relative effort (low / medium / high or points)
+- **Approximate timeline** (if applicable)
+- **Assumptions** used for estimation
 
 ---
 
-## 8. Puntos críticos y resolución
-Identificación de riesgos técnicos clave.
+## 8. Critical Points and Resolution
+Identification of key technical risks.
 
-- **Punto crítico 1**
-  - Riesgo
-  - Impacto
-  - Estrategia de resolución
-- **Punto crítico 2**
-  - (Repetir)
+- **Critical point 1**
+  - Risk
+  - Impact
+  - Resolution strategy
+- **Critical point 2**
+  - (Repeat)
 
 ---
 
-## 9. Dependencias y compatibilidad
-- **Dependencias internas**
-- **Dependencias externas**
-- **Compatibilidad entre navegadores** (si aplica)
+## 9. Dependencies and Compatibility
+- **Internal dependencies**
+- **External dependencies**
+- **Cross-browser compatibility** (if applicable)
   - Chrome / Chromium
   - Firefox
   - Safari
-- **Restricciones arquitectónicas** relevantes
+- **Relevant architectural constraints**
 
 ---
 
-## 10. Criterios de finalización
-Condiciones objetivas para considerar la implementación “Done”.
+## 10. Completion Criteria
+Objective conditions to consider the implementation "Done".
 
-- Checklist final alineado con acceptance criteria.
-- Verificaciones obligatorias completadas.
+- Final checklist aligned with acceptance criteria.
+- Mandatory verifications completed.
 
 ---
 
-## 11. Aprobación del desarrollador (OBLIGATORIA)
-Este plan **requiere aprobación explícita y binaria**.
+## 11. Developer Approval (MANDATORY)
+This plan **requires explicit and binary approval**.
 
 ```yaml
 approval:
   developer:
     decision: SI | NO
     date: <ISO-8601>
-    comments: <opcional>
+    comments: <optional>