@christianmaf80/agentic-workflow 1.2.0-beta.1

package/dist/templates/planning.md

@@ -0,0 +1,157 @@
+---
+artifact: plan
+phase: phase-3-planning
+owner: architect-agent
+status: draft | approved
+related_task: <taskId>-<taskTitle>
+---
+
+# Implementation Plan — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+
+## 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. Contractual Inputs
+- **Task**: `.agent/artifacts/<taskId>-<taskTitle>/task.md`
+- **Analysis**: `.agent/artifacts/<taskId>-<taskTitle>/analysis.md`
+- **Acceptance Criteria**: explicit reference to relevant ACs.
+
+**Domain Dispatch (MANDATORY if applicable)**
+```yaml
+plan:
+  workflows:
+    drivers:
+      action: create | refactor | delete | none
+      workflow: workflow.drivers.create | workflow.drivers.refactor | workflow.drivers.delete
+
+  dispatch:
+    - domain: drivers | modules | core | qa
+      action: create | refactor | delete | audit | verify | none
+      workflow: <workflow.id>
+```
+
+---
+
+## 3. Implementation Breakdown (Steps)
+Ordered and executable decomposition.
+
+### Step 1
+- **Description**
+- **Dependencies**
+- **Deliverables**
+- **Responsible Agent**
+
+### Step 2
+- (Repeat structure)
+
+> Note: indicate order, dependencies, and parallelization if applicable.
+
+---
+
+## 4. Responsibility Assignment (Agents)
+Clear mapping of agents ↔ sub-areas.
+
+- **Architect-Agent**
+  - Responsibilities
+- **Implementation-Agent**
+  - Responsibilities
+- **QA / Verification-Agent** (if applicable)
+  - Responsibilities
+- **Other Agents** (if applicable)
+
+**Handoffs**
+- What is delivered, to whom, and when.
+
+**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 exist, justify the alternative).
+- Reference the chosen tool by alias (e.g., `mcp_extensio-cli tools`) and the reason.
+
+**Demo (if applicable)**
+- Define the expected structure aligned with `constitution.project_architecture`.
+- Define the mandatory tool for generating scaffolding (use `mcp_extensio-cli tools`).
+
+---
+
+## 5. Testing and Validation Strategy
+How it will be verified that the implementation meets the ACs.
+
+- **Unit Tests**
+  - Scope and tools (see `constitution.project_architecture`)
+- **Integration Tests**
+  - Covered flows (see `constitution.project_architecture`)
+- **E2E / Manual**
+  - Key scenarios (see `constitution.project_architecture`)
+
+**Traceability**
+- Mapping of tests ↔ acceptance criteria.
+
+---
+
+## 6. Demo Plan (if applicable)
+- **Demo Objective**
+- **Scenario(s)**
+- **Example Data**
+- **Demo Success Criteria**
+
+---
+
+## 7. Estimations and Implementation Weights
+- **Estimation per Step / Sub-area**
+  - relative effort (low / medium / high or points)
+- **Approximate Timeline** (if applicable)
+- **Assumptions** used for estimating
+
+---
+
+## 8. Critical Points and Resolution
+Identification of key technical risks.
+
+### Critical Point 1
+- **Risk**
+- **Impact**
+- **Resolution Strategy**
+
+### Critical Point 2
+- (Repeat)
+
+---
+
+## 9. Dependencies and Compatibility
+- **Internal Dependencies**
+- **External Dependencies**
+- **Multi-Browser Compatibility** (if applicable)
+  - Chrome / Chromium
+  - Firefox
+  - Safari
+- **Relevant Architectural Constraints**
+
+---
+
+## 10. Completion Criteria
+Objective conditions to consider the implementation "Done".
+
+- Final checklist aligned with acceptance criteria.
+- Mandatory verifications completed.
+
+---
+
+## 11. Developer Approval (MANDATORY)
+This plan **requires explicit and binary approval**.
+
+```yaml
+approval:
+  developer:
+    decision: YES | NO
+    date: <ISO-8601>
+    comments: <optional>
+```

package/dist/templates/research.md

@@ -0,0 +1,89 @@
+---
+artifact: research
+phase: phase-1-research
+owner: researcher-agent
+status: draft | approved
+related_task: <taskId>-<taskTitle>
+---
+
+# Research Report — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+
+> [!CAUTION]
+> **PERMANENT RULE**: This document is ONLY for documentation.
+> The researcher-agent documents findings WITHOUT analyzing, WITHOUT recommending, and WITHOUT proposing solutions.
+> Analysis is the responsibility of the architect during Phase 2.
+
+## 1. Executive Summary
+- Problem researched
+- Research objective
+- Key findings
+
+---
+
+## 2. Detected Needs
+- Technical requirements identified by the architect-agent
+- Assumptions and limits
+
+---
+
+## 3. Technical Findings
+For each finding:
+- Concept/technology description
+- Current status (stable, experimental, deprecated)
+- Official documentation
+- Known limitations
+
+> **DO NOT include**: pros/cons, recommendations, or decisions.
+
+---
+
+## 4. Relevant Web APIs / WebExtensions
+- API / specification
+- Support status (Chrome/Firefox/Safari)
+- Known restrictions
+
+---
+
+## 5. Multi-browser Compatibility
+- Compatibility table
+- Key differences
+- Mitigation strategies
+
+---
+
+## 6. AI-first Opportunities Detected
+- Patterns or APIs that could enable automation
+- References to relevant documentation
+
+> **DO NOT include**: expected impact or usage recommendations.
+
+---
+
+## 7. Identified Risks
+- Risk detected
+- Severity (high/medium/low)
+- Information source
+
+> **DO NOT include**: mitigations (these belong in the analysis).
+
+---
+
+## 8. Sources
+- Links to official docs
+- RFCs / proposals
+- Other resources
+
+---
+
+## 9. Developer Approval (MANDATORY)
+```yaml
+approval:
+  developer:
+    decision: YES | NO
+    date: <ISO-8601>
+    comments: <optional>
+```

package/dist/templates/results-acceptance.md

@@ -0,0 +1,177 @@
+---
+artifact: results_acceptance
+phase: phase-6-results-acceptance
+owner: architect-agent
+status: pending | approved | rejected
+related_task: <taskId>-<taskTitle>
+related_plan: .agent/artifacts/<taskId>-<taskTitle>/plan.md
+related_review: .agent/artifacts/<taskId>-<taskTitle>/architect/review.md
+related_verification: .agent/artifacts/<taskId>-<taskTitle>/verification.md
+---
+
+# Final Results Report — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+
+## 1. Executive Summary (for decision)
+This document presents **the complete final result of the task**, consolidating:
+- what was planned
+- what was implemented
+- how it was reviewed
+- how it was verified
+
+**Quick Conclusion**
+- General status: ☐ SATISFACTORY ☐ UNSATISFACTORY
+- Architect's Recommendation: ☐ Accept ☐ Iterate
+
+---
+
+## 2. Task Context
+### 2.1 Original Objective
+(Extracted from `task.md`)
+
+- Objective:
+- Defined scope:
+- Out of scope:
+
+### 2.2 Agreed Acceptance Criteria (AC)
+List of ACs defined in Phase 0.
+
+| ID | Description | Final Status |
+|----|-------------|--------------|
+| AC-1 | | ✅ Met / ❌ No |
+| AC-2 | | ✅ Met / ❌ No |
+
+---
+
+## 3. Planning (What was agreed upon)
+Summary of the **approved plan** from Phase 3.
+
+- General strategy
+- Main phases and steps
+- Involved agents and responsibilities
+- Agreed testing strategy
+- Demo plan (if applicable)
+
+> Reference: `plan.md`
+
+---
+
+## 4. Implementation (What was actually done)
+Clear description of the executed implementation.
+
+### 4.1 Subtasks per Agent
+For each participating agent:
+
+**Agent:** `<agent-name>`
+- Assigned responsibility:
+- Executed subtasks:
+- Generated artifacts:
+- Relevant changes:
+
+(Repeat for each agent)
+
+### 4.2 Relevant Technical Changes
+- New modules / drivers
+- Structural changes
+- Affected APIs
+- Multi-browser compatibility (if applicable)
+
+---
+
+## 5. Architectural Review
+Summary of the architect's review report.
+
+- Consistency with the plan: ☐ Yes ☐ No
+- Architectural compliance: ☐ Yes ☐ No
+- Clean code compliance: ☐ Yes ☐ No
+- Detected deviations:
+  - None / Detailed below
+
+**Architect's Conclusions**
+- Impact on the system
+- Residual risks
+- Technical debt (if any)
+
+> Reference: `architect/review.md`
+
+---
+
+## 6. Verification and Validation
+Functional verification results.
+
+### 6.1 Executed Tests
+- Unit:
+- Integration:
+- End-to-End / Manual:
+- Global Result: ☐ OK ☐ NO OK
+
+### 6.2 Demo (if applicable)
+- What was demonstrated
+- Demo result
+- Developer's observations
+
+> Reference: `verification.md`
+
+---
+
+## 7. Final Status of Acceptance Criteria
+Definitive evaluation.
+
+| Acceptance Criteria | Result | Evidence |
+|---------------------|--------|----------|
+| AC-1 | ✅ / ❌ | |
+| AC-2 | ✅ / ❌ | |
+
+> All ACs **MUST** be met to accept the task.
+
+---
+
+## 8. AHRP Discipline and Conformity (CRITICAL)
+Evaluation of compliance with safety and orchestration protocol.
+
+| Gate | Status | Observations |
+| :--- | :--- | :--- |
+| **Gate A (Activation)** | ☐ PASS ☐ FAIL | Did the agent wait for signature before using tools? |
+| **Gate B (Reasoning)** | ☐ PASS ☐ FAIL | Was the technical plan approved before implementation? |
+| **Global Conformity** | ☐ YES ☐ NO | |
+
+> **NOTE**: If global conformity is **NO**, the final task score will be **0** automatically.
+
+---
+
+## 9. Issues and Deviations
+Consolidated list of problems found during the cycle.
+
+- Issue:
+  - Phase where it was detected
+  - Impact
+  - Applied resolution
+
+If no issues were found, explicitly state:
+> "No relevant issues detected."
+
+---
+
+## 10. Global Evaluation
+Final assessment of the result.
+
+- Technical Quality: ☐ High ☐ Medium ☐ Low
+- Alignment with Request: ☐ Full ☐ Partial ☐ Insufficient
+- Solution Stability: ☐ High ☐ Medium ☐ Low
+- Maintainability: ☐ High ☐ Medium ☐ Low
+
+---
+
+## 11. Developer's Final Decision (MANDATORY)
+This decision **closes the phase**.
+
+```yaml
+approval:
+  developer:
+    decision: YES | NO
+    date: <ISO-8601>
+    comments: <optional>
+```

package/dist/templates/review.md

@@ -0,0 +1,110 @@
+---
+artifact: architect-review
+phase: phase-4-implementation
+owner: architect-agent
+status: approved | rejected
+related_task: <taskId>-<taskTitle>
+related_plan: .agent/artifacts/<taskId>-<taskTitle>/plan.md
+---
+
+# Architectural Implementation Review — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+
+## 1. Review Summary
+- **Review Objective**  
+  Verify that the executed implementation complies with the **approved implementation plan** without unauthorized deviations.
+
+- **Global Result**  
+  - Status: ☐ APPROVED ☐ REJECTED
+  - Review Date:
+  - Responsible Architect:
+
+---
+
+## 2. Verification against the Implementation Plan
+Direct and traceable review **plan → implementation**.
+
+### 2.1 Plan Steps
+For **each step defined in `plan.md`**:
+
+| Plan Step | Status | Evidence | Observations |
+|-----------|--------|----------|--------------|
+| Step 1 | ☐ OK ☐ NO OK | refs / commits / artifacts | |
+| Step 2 | ☐ OK ☐ NO OK | | |
+
+> All steps **MUST** be in **OK** status to approve the phase.
+
+---
+
+## 3. Subtasks per Agent
+Review of individual implementations.
+
+### Agent: `<agent-name>`
+- **Task document**:
+  - `.agent/artifacts/<taskId>-<taskTitle>/agent-tasks/<N>-<agent>-<taskName>.md`
+- **Evaluation**:
+  - ☐ Complies with the plan
+  - ☐ Deviations detected (detail below)
+
+**Architect's Notes**
+- Changes made:
+- Technical decisions:
+- Consistency with the rest of the system:
+
+(Repeat section for each participating agent)
+
+---
+
+## 4. Acceptance Criteria (Impact)
+Verification that the implementation **does not break** the defined acceptance criteria.
+
+- ☐ All ACs remain valid
+- ☐ Any AC requires review (detail below)
+
+**Observations**
+- Affected ACs:
+- Reason:
+
+---
+
+## 5. Architectural Consistency
+Global evaluation of the system after implementation.
+
+- ☐ Respects project architecture
+- ☐ Respects clean code
+- ☐ Does not introduce significant technical debt
+- ☐ Maintains expected compatibility (multi-browser if applicable)
+
+**Architectural Observations**
+- Impact on structure:
+- Impact on modules/drivers:
+- Risks introduced:
+
+---
+
+## 6. Plan Deviations
+Explicit record of deviations (if any).
+
+- **Deviation**
+  - Description:
+  - Justification:
+  - Was it anticipated in the plan? ☐ Yes ☐ No
+  - Does it require re-planning? ☐ Yes ☐ No
+
+(If there are no deviations, explicitly state: "No deviations detected").
+
+---
+
+## 7. Architect's Final Decision
+Severe and binary decision.
+
+```yaml
+decision:
+  architect:
+    result: APPROVED | REJECTED
+    date: <ISO-8601>
+    comments: <optional>
+```

package/dist/templates/subtask-implementation.md

@@ -0,0 +1,67 @@
+---
+artifact: subtask_implementation
+phase: phase-4-implementation
+owner: implementation-agent
+status: draft | completed
+related_task: <taskId>-<taskTitle>
+agent: <agent>
+subtask_id: <id>
+---
+
+> [!WARNING]
+> **@deprecated**: This template is obsolete. Use `templates.agent_task` for new tasks.
+
+# Subtask Implementation — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+ — <agent> — <subtask_id>
+
+## 1. Context and Scope
+- Precise subtask description
+- Specific objective
+- Relation to the plan (reference to the exact step)
+
+---
+
+## 2. Changes Made (Detailed)
+- Touched files (full list)
+- Changes per file (summary per file)
+- Affected APIs/contracts
+- New functions/classes/constants
+
+---
+
+## 3. Technical Decisions
+- Key decisions and their justification
+- Alternatives considered and why they were discarded
+- Impact on other modules/drivers (if applicable)
+
+---
+
+## 4. Testing and Evidence
+- Executed tests (command and scope)
+- Results (pass/fail)
+- Evidence (logs, screenshots, reports)
+
+---
+
+## 5. Plan Deviations
+- Detected deviations
+- Reason
+- Corrective action or recorded debt
+
+---
+
+## 6. Risks and Pending Validations
+- Open risks
+- Pending validations
+
+---
+
+## 7. Checklist
+- [ ] Subtask completed
+- [ ] Changes documented
+- [ ] Testing documented
+- [ ] Ready for architect review

package/dist/templates/supplemental-report.md

@@ -0,0 +1,30 @@
+# Supplemental Report — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+
+## Identification
+- id: {{artifact.id}}
+- title: {{artifact.title}}
+- type: supplemental
+- owner: {{artifact.owner}}
+- related_task: {{task.id}}
+
+## Purpose
+{{artifact.purpose}}
+
+## Context
+{{artifact.context}}
+
+## Findings / Notes
+{{artifact.findings}}
+
+## Decisions
+{{artifact.decisions}}
+
+## References
+- {{artifact.references}}
+
+## Related Artifact Links
+- {{artifact.related_artifacts}}

package/dist/templates/task-metrics.md

@@ -0,0 +1,39 @@
+---
+artifact: task_metrics
+phase: phase-7-evaluation
+owner: architect-agent
+status: pending | completed
+related_task: <taskId>-<taskTitle>
+---
+
+# Task Metrics — <taskId>-<taskTitle>
+
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
+
+## 1. Evaluated Agents
+- Agent A
+- Agent B
+
+---
+
+## 2. Score per Agent (0-10)
+- **Agent A**: score
+  - Justification
+- **Agent B**: score
+  - Justification
+
+---
+
+## 3. Global Task Score
+- Weighted Average: score
+- **AHRP Compliance**: [YES / NO] (If NO, global score is 0)
+- Observations
+
+---
+
+## 4. Developer Validation
+- Approved: [YES / NO]
+- Developer Score (0-10): 
+- Comments: