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

package/dist/agent/workflows/coding/coding-background.md

@@ -0,0 +1,149 @@
+---
+id: workflow.coding.background
+description: On-demand coding workflow for the Background/Orchestration layer. Invoked by architect-agent during Phase 4 implementation.
+owner: background
+version: 1.0.0
+severity: PERMANENT
+trigger:
+  commands: ["coding-background"]
+blocking: true
+---
+
+# WORKFLOW: coding.background
+
+## Input (REQUIRED)
+- Agent task file assigned by architect:
+  - `.agent/artifacts/<taskId>-<taskTitle>/agent-tasks/<N>-background-<taskName>.md`
+- Constitution loaded:
+  - `constitution.background` (MANDATORY)
+  - `constitution.clean_code` (MANDATORY)
+- Role activated:
+  - `roles.background`
+
+> [!IMPORTANT]
+> **This is an on-demand workflow.** It is invoked by `architect-agent` during Phase 4 as part of the implementation plan. The architect defines the execution order of coding workflows.
+
+## Output (REQUIRED)
+- Implementation report using `templates.coding.layer_report`:
+  - Embedded in the agent task file under "Implementation Report"
+- All code changes passing compilation
+
+---
+
+## Objective (ONLY)
+- Implement the **background/orchestration layer** of the assigned task following `constitution.background`.
+- Generate a detailed implementation report.
+- Present to developer for Gate approval.
+
+> This workflow **ONLY** implements orchestration logic.
+> This workflow is the **ONLY** layer authorized to import `vscode`.
+> This workflow manages the **Backend ↔ View bridge** via Messaging.
+
+---
+
+## Mandatory Steps
+
+### 0. Activate role
+- Activate `roles.background` and use mandatory agent prefix in all messages.
+
+### 1. Verify inputs
+- Agent task file exists and has Input section completed by architect.
+- Constitution `constitution.background` loaded.
+- Constitution `constitution.clean_code` loaded.
+- If missing → **FAIL**.
+
+### 2. Analyze the task
+- Read the agent task Input (objective, scope, dependencies).
+- Complete the "Reasoning" section of the agent task:
+  - Analyze objective
+  - Consider options
+  - Document decision and justification
+
+### 3. Implement
+- Write code following `constitution.background`:
+  - **Orchestration**: Manage flow between VS Code, Backend, and View.
+  - **Registration**: All modules register via `App.register(id, provider)`.
+  - **Messaging**: Use `core/messaging` for View communication (MANDATORY).
+  - **Type safety**: Use shared `Message` interface from `core/types`.
+  - **Lifecycle**: Respect VS Code activation/deactivation.
+  - **Dependency injection**: Inject services into providers.
+- Write code following `constitution.clean_code`.
+
+### 4. Self-validate
+- Verify all constitution rules are satisfied:
+  - [ ] Modules registered via `App.register()`
+  - [ ] View communication via `core/messaging` only
+  - [ ] Typed `Message` payloads
+  - [ ] VS Code lifecycle respected
+  - [ ] Gateway role: only layer with `vscode` side-effects
+  - [ ] Clean code principles applied
+- Run compilation: `npm run compile`
+- If compilation fails → fix before proceeding.
+
+### 5. Generate implementation report
+- Complete the "Implementation Report" section using `templates.coding.layer_report`:
+  - **Who**: Agent identity and role
+  - **How**: Technical details, specifications, diagrams if needed
+  - **Why**: Justification and reasoning
+  - **Results**: What was achieved, compilation status
+  - **E2E Test Indications**: Scenarios for e2e testing
+
+### 6. Present to developer (Gate)
+- Present completed task with report to developer.
+- Request approval: **SI / NO**
+
+### 7. Register Gate
+```yaml
+approval:
+  developer:
+    decision: SI | NO
+    date: <ISO-8601>
+    comments: <optional>
+```
+
+### 8. Evaluate Gate
+- If `decision == SI` → go to **Step 9 (PASS)**.
+- If `decision == NO`:
+  - Mark task as `failed`.
+  - Define corrective actions.
+  - **Do NOT advance** until resolved.
+  - Go to **Step 10 (FAIL)**.
+
+### 9. PASS (only if Gate approved)
+- Mark agent task as `completed`.
+- Update agent task file:
+  ```yaml
+  execution:
+    status: completed
+    completed_at: <ISO-8601>
+  ```
+- Update the coding layer report with final status.
+- Return control to `architect-agent` for next workflow in the sequence.
+
+---
+
+## FAIL (MANDATORY)
+
+### 10. Declare workflow as NOT completed
+Cases:
+- Missing inputs or constitution.
+- Compilation failure not resolved.
+- Constitution violation detected.
+- Gate = NO without resolution.
+
+Actions:
+- Identify the failure point.
+- Define corrective actions.
+- Iterate until Gate PASS.
+
+---
+
+## Gate (REQUIRED)
+
+Requirements (all mandatory):
+1. Code compiles without errors.
+2. All `constitution.background` rules are satisfied.
+3. All `constitution.clean_code` rules are satisfied.
+4. Implementation report is complete (all 5 sections).
+5. Developer Gate PASS (`decision == SI`).
+6. Agent task file starts with background agent prefix.

package/dist/agent/workflows/coding/coding-integration.md

@@ -0,0 +1,174 @@
+---
+id: workflow.coding.integration
+description: On-demand coding workflow for integrating the 3 layers of a module (Backend, Background, View). Invoked by architect-agent during Phase 4 after layer-specific workflows.
+owner: architect-agent
+version: 1.0.0
+severity: PERMANENT
+trigger:
+  commands: ["coding-integration"]
+blocking: true
+---
+
+# WORKFLOW: coding.integration
+
+## Input (REQUIRED)
+- Agent task file assigned by architect:
+  - `.agent/artifacts/<taskId>-<taskTitle>/agent-tasks/<N>-architect-integration-<taskName>.md`
+- All applicable layer coding workflows completed and approved:
+  - `coding-backend` report (if applicable)
+  - `coding-background` report (if applicable)
+  - `coding-view` report (if applicable)
+- Constitutions loaded (ALL):
+  - `constitution.backend` (MANDATORY)
+  - `constitution.background` (MANDATORY)
+  - `constitution.view` (MANDATORY)
+  - `constitution.clean_code` (MANDATORY)
+
+> [!IMPORTANT]
+> **This workflow runs AFTER all layer-specific coding workflows.** It validates that the 3 layers communicate correctly and comply with all constitutions. The architect is the owner.
+
+## Output (REQUIRED)
+- Integration report using `templates.coding.integration_report`:
+  - Embedded in the agent task file under "Implementation Report"
+- All layers passing compilation and integration validation
+
+---
+
+## Objective (ONLY)
+- Validate and ensure **optimal communication** between the 3 layers of the module.
+- Verify **constitution compliance** across all layers.
+- Generate a detailed **integration report**.
+- Present to developer for Gate approval.
+
+> This workflow validates **inter-layer contracts**.
+> This workflow ensures **no constitution violations** exist across boundaries.
+> This workflow is the **final validation** before Phase 4 closure.
+
+---
+
+## Mandatory Steps
+
+### 0. Activate role
+- Activate `architect-agent` and use mandatory prefix in all messages.
+
+### 1. Verify inputs
+- All applicable layer coding workflows have Gate PASS.
+- All layer reports exist and are complete.
+- All 4 constitutions loaded.
+- If missing → **FAIL**.
+
+### 2. Review layer reports
+- Read each layer's implementation report.
+- Identify:
+  - Communication touchpoints between layers.
+  - Shared contracts (Message types, API interfaces).
+  - Potential constitution violations at boundaries.
+
+### 3. Validate communication paths
+- **View → Background**: Via `core/messaging` Event Bus only.
+  - [ ] No direct `vscode.postMessage` from View.
+  - [ ] Typed `Message` payloads.
+- **Background → Backend**: Via abstract transport or direct invocation.
+  - [ ] No `vscode` leaking into Backend.
+  - [ ] Structured error responses from Backend.
+- **Background → View**: Via `core/messaging` response path.
+  - [ ] Reactive UI updates on state change.
+- **View → Backend**: FORBIDDEN.
+  - [ ] No direct imports or calls between View and Backend.
+
+### 4. Validate constitution compliance
+For each constitution, verify cross-layer boundaries:
+
+#### Backend (`constitution.backend`)
+- [ ] Extends `AbstractServer` (if applicable)
+- [ ] No `vscode` or `dom` imports
+- [ ] Transport agnostic
+- [ ] No direct View communication
+
+#### Background (`constitution.background`)
+- [ ] Modules registered via `App.register()`
+- [ ] Uses `core/messaging` for View communication
+- [ ] Manages lifecycle correctly
+- [ ] Gateway role maintained (only layer with `vscode` side-effects)
+
+#### View (`constitution.view`)
+- [ ] Lit components with `@customElement`
+- [ ] Triad structure (index/html/styles)
+- [ ] No business logic
+- [ ] Communication via Messaging wrapper only
+
+### 5. Integration validation
+- Run full compilation: `npm run compile`
+- Verify no type errors at layer boundaries.
+- If issues found → create corrective sub-task.
+
+### 6. Generate integration report
+- Complete the "Implementation Report" section using `templates.coding.integration_report`:
+  - **Communication validation matrix**: Results of Step 3
+  - **Constitution compliance**: Results of Step 4
+  - **Cross-layer sequence diagrams**: Key interaction flows (mermaid)
+  - **E2E Test Indications**: Integration test scenarios
+  - **Issues found and resolutions**: If any
+
+### 7. Present to developer (Gate)
+- Present integration report with all evidence to developer.
+- Request approval: **SI / NO**
+
+### 8. Register Gate
+```yaml
+approval:
+  developer:
+    decision: SI | NO
+    date: <ISO-8601>
+    comments: <optional>
+```
+
+### 9. Evaluate Gate
+- If `decision == SI` → go to **Step 10 (PASS)**.
+- If `decision == NO`:
+  - Identify failing layer(s).
+  - Create corrective sub-task for specific layer workflow.
+  - Re-run integration after correction.
+  - Go to **Step 11 (FAIL)**.
+
+### 10. PASS (only if Gate approved)
+- Mark integration task as `completed`.
+- Update agent task file:
+  ```yaml
+  execution:
+    status: completed
+    completed_at: <ISO-8601>
+  ```
+- Update the integration report with final assessment: `PASS`.
+- Return control to `architect-agent` for **Phase 4 closure** (Gate final de Phase 4).
+
+---
+
+## FAIL (MANDATORY)
+
+### 10. Declare workflow as NOT completed
+Cases:
+- Layer workflows not completed or not approved.
+- Constitution violation at layer boundaries.
+- Compilation failure.
+- Direct View→Backend communication detected.
+- Gate = NO without resolution.
+
+Actions:
+- Identify the exact layer and violation.
+- Delegate corrective action to the appropriate layer workflow.
+- Re-run integration validation after fix.
+- Iterate until Gate PASS.
+
+---
+
+## Gate (REQUIRED)
+
+Requirements (all mandatory):
+1. All layer coding workflows have Gate PASS.
+2. All communication paths validated (Step 3 checklist).
+3. All constitutions satisfied at cross-layer boundaries (Step 4 checklist).
+4. Full compilation passes without errors.
+5. Integration report is complete (all sections).
+6. Developer Gate PASS (`decision == SI`).
+7. No direct View→Backend communication exists.

package/dist/agent/workflows/coding/coding-view.md

@@ -0,0 +1,151 @@
+---
+id: workflow.coding.view
+description: On-demand coding workflow for the View/UI layer. Invoked by architect-agent during Phase 4 implementation.
+owner: view
+version: 1.0.0
+severity: PERMANENT
+trigger:
+  commands: ["coding-view"]
+blocking: true
+---
+
+# WORKFLOW: coding.view
+
+## Input (REQUIRED)
+- Agent task file assigned by architect:
+  - `.agent/artifacts/<taskId>-<taskTitle>/agent-tasks/<N>-view-<taskName>.md`
+- Constitution loaded:
+  - `constitution.view` (MANDATORY)
+  - `constitution.clean_code` (MANDATORY)
+- Role activated:
+  - `roles.view`
+
+> [!IMPORTANT]
+> **This is an on-demand workflow.** It is invoked by `architect-agent` during Phase 4 as part of the implementation plan. The architect defines the execution order of coding workflows.
+
+## Output (REQUIRED)
+- Implementation report using `templates.coding.layer_report`:
+  - Embedded in the agent task file under "Implementation Report"
+- All code changes passing compilation
+
+---
+
+## Objective (ONLY)
+- Implement the **view/UI layer** of the assigned task following `constitution.view`.
+- Generate a detailed implementation report.
+- Present to developer for Gate approval.
+
+> This workflow **ONLY** implements UI components.
+> This workflow **NEVER** contains business logic.
+> This workflow **NEVER** uses Node.js APIs (fs, path, etc).
+> This workflow **NEVER** uses `vscode.postMessage` directly (use Messaging wrapper).
+
+---
+
+## Mandatory Steps
+
+### 0. Activate role
+- Activate `roles.view` and use mandatory agent prefix in all messages.
+
+### 1. Verify inputs
+- Agent task file exists and has Input section completed by architect.
+- Constitution `constitution.view` loaded.
+- Constitution `constitution.clean_code` loaded.
+- If missing → **FAIL**.
+
+### 2. Analyze the task
+- Read the agent task Input (objective, scope, dependencies).
+- Complete the "Reasoning" section of the agent task:
+  - Analyze objective
+  - Consider options
+  - Document decision and justification
+
+### 3. Implement
+- Write code following `constitution.view`:
+  - **Framework**: Lit is mandatory. Use `@customElement`.
+  - **Structure**: Triad required: `index.ts` (logic), `html.ts` (template), `styles.ts` (css).
+  - **Styling**: Vanilla CSS in `styles.ts`. No external preprocessors.
+  - **Dumb components**: Rendering and interaction only, NO business logic.
+  - **Reactive**: Immediate UI updates on state change.
+  - **Communication**: Event Bus via `p2p`/`bus`, use `Messaging` wrapper.
+- Write code following `constitution.clean_code`.
+
+### 4. Self-validate
+- Verify all constitution rules are satisfied:
+  - [ ] Uses Lit with `@customElement`
+  - [ ] Triad structure: `index.ts`, `html.ts`, `styles.ts`
+  - [ ] No business logic in components
+  - [ ] No Node.js API usage
+  - [ ] No direct `vscode.postMessage`
+  - [ ] Communication via Messaging wrapper
+  - [ ] Clean code principles applied
+- Run compilation: `npm run compile`
+- If compilation fails → fix before proceeding.
+
+### 5. Generate implementation report
+- Complete the "Implementation Report" section using `templates.coding.layer_report`:
+  - **Who**: Agent identity and role
+  - **How**: Technical details, specifications, diagrams if needed
+  - **Why**: Justification and reasoning
+  - **Results**: What was achieved, compilation status
+  - **E2E Test Indications**: Scenarios for e2e testing
+
+### 6. Present to developer (Gate)
+- Present completed task with report to developer.
+- Request approval: **SI / NO**
+
+### 7. Register Gate
+```yaml
+approval:
+  developer:
+    decision: SI | NO
+    date: <ISO-8601>
+    comments: <optional>
+```
+
+### 8. Evaluate Gate
+- If `decision == SI` → go to **Step 9 (PASS)**.
+- If `decision == NO`:
+  - Mark task as `failed`.
+  - Define corrective actions.
+  - **Do NOT advance** until resolved.
+  - Go to **Step 10 (FAIL)**.
+
+### 9. PASS (only if Gate approved)
+- Mark agent task as `completed`.
+- Update agent task file:
+  ```yaml
+  execution:
+    status: completed
+    completed_at: <ISO-8601>
+  ```
+- Update the coding layer report with final status.
+- Return control to `architect-agent` for next workflow in the sequence.
+
+---
+
+## FAIL (MANDATORY)
+
+### 10. Declare workflow as NOT completed
+Cases:
+- Missing inputs or constitution.
+- Compilation failure not resolved.
+- Constitution violation detected.
+- Gate = NO without resolution.
+
+Actions:
+- Identify the failure point.
+- Define corrective actions.
+- Iterate until Gate PASS.
+
+---
+
+## Gate (REQUIRED)
+
+Requirements (all mandatory):
+1. Code compiles without errors.
+2. All `constitution.view` rules are satisfied.
+3. All `constitution.clean_code` rules are satisfied.
+4. Implementation report is complete (all 5 sections).
+5. Developer Gate PASS (`decision == SI`).
+6. Agent task file starts with view agent prefix.