siesa-agents 2.1.48 → 2.1.49

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-07-implement.md

@@ -0,0 +1,62 @@
+---
+name: 'step-07-implement'
+description: 'Implement task following red-green-refactor cycle'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-07-implement.md'
+nextStepFile: '{workflow_path}/steps/step-08-test-authoring.md'
+completionStep: '{workflow_path}/steps/step-11-mark-review.md'
+---
+
+# Step 7: Implementation Loop (Red-Green-Refactor)
+
+## STEP GOAL:
+
+Implement a SINGLE task or subtask using TDD and the Red-Green-Refactor cycle.
+
+## MANDATORY RULES:
+
+- 🛑 FOLLOW STORY TASKS EXACTLY
+- 🎨 Enforce `siesa-ui-kit` usage
+- 🧪 Red-Green-Refactor is MANDATORY
+
+## EXECUTION PROTOCOLS:
+
+### 1. Identify Next Task
+
+1.  Read Story File.
+2.  Find **FIRST** incomplete task (unchecked `[ ]`).
+    *   **IF NO incomplete tasks:** Load and execute `{completionStep}` (`step-11-mark-review.md`).
+    *   **IF Task Found:** Proceed below.
+
+### 2. UI Kit Validation
+
+For the current task:
+1.  **Strictly Forbidden:** Creating custom UI components if `siesa-ui-kit` has an equivalent.
+2.  **Missing Component Protocol:**
+    *   If component missing, ASK user: [1] Shadcn/ui (MCP) or [2] Custom (MR to Platform).
+    *   Log decision in Dev Notes.
+
+### 3. Red Phase (Failing Test)
+
+1.  Write a **FAILING** test for the task functionality.
+2.  Run test to CONFIRM failure.
+
+### 4. Green Phase (Make it Pass)
+
+1.  Implement **MINIMAL** code to pass the test.
+2.  Run test to CONFIRM success.
+3.  Handle edge cases specified in task.
+
+### 5. Refactor Phase
+
+1.  Improve structure while keeping tests green.
+2.  Align with architecture patterns (from Context).
+3.  Document approach in **Dev Agent Record**.
+
+### 6. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-08-test-authoring.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-08-test-authoring.md

@@ -0,0 +1,39 @@
+---
+name: 'step-08-test-authoring'
+description: 'Author comprehensive tests'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-08-test-authoring.md'
+nextStepFile: '{workflow_path}/steps/step-09-run-tests.md'
+---
+
+# Step 8: Comprehensive Test Authoring
+
+## STEP GOAL:
+
+Ensure the implemented task is covered by robust tests beyond the initial TDD cycle (Integration, E2E, Edge Cases).
+
+## EXECUTION PROTOCOLS:
+
+### 1. Unit Tests
+
+Ensure business logic and core functionality are covered.
+
+### 2. Integration Tests
+
+Add tests for component interactions if specified in story requirements.
+
+### 3. End-to-End (E2E) Tests
+
+Include E2E tests for critical UI flows if story demands them.
+
+### 4. Edge Cases
+
+Cover error handling and edge cases identified in Dev Notes.
+
+### 5. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-09-run-tests.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-09-run-tests.md

@@ -0,0 +1,43 @@
+---
+name: 'step-09-run-tests'
+description: 'Run validations and tests'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-09-run-tests.md'
+nextStepFile: '{workflow_path}/steps/step-10-validate-task.md'
+---
+
+# Step 9: Run Tests & Validations
+
+## STEP GOAL:
+
+Verify implementation correctness, ensure no regressions, and validate coding standards.
+
+## EXECUTION PROTOCOLS:
+
+### 1. Run Tests
+
+1.  Infer test framework (Vitest/Jest).
+2.  **Run All Tests**: Ensure no regressions.
+3.  **Run New Tests**: Verify implementation.
+
+### 2. Run Quality Checks
+
+1.  Run Linting/Static Analysis (if configured).
+
+### 3. Validate Standards
+
+1.  **UI Library Check**: Verify NO custom styles/components were created where `siesa-ui-kit` exists (unless logged).
+
+### 4. Handling Failures
+
+*   **Regression Failures**: STOP and Fix.
+*   **New Test Failures**: STOP and Fix.
+*   **UI Violation**: STOP and Refactor.
+
+### 5. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-10-validate-task.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-10-validate-task.md

@@ -0,0 +1,63 @@
+---
+name: 'step-10-validate-task'
+description: 'Validate and mark task complete'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-10-validate-task.md'
+nextTaskStep: '{workflow_path}/steps/step-07-implement.md'
+completionStep: '{workflow_path}/steps/step-11-mark-review.md'
+---
+
+# Step 10: Task Completion & Loop
+
+## STEP GOAL:
+
+Formally mark the task as complete after verifying all gates, update records, and determine if the workflow should loop for the next task or finish.
+
+## MANDATORY EXECUTION RULES:
+
+- 🛑 NEVER mark complete unless ALL validation gates pass.
+- 🔄 Loop back to Step 07 if tasks remain.
+
+## EXECUTION PROTOCOLS:
+
+### 1. Validation Gates
+
+Confirm:
+1.  Tests EXIST and PASS.
+2.  Implementation matches Task specs exactly.
+3.  ACs satisfied.
+4.  `siesa-ui-kit` compliance.
+5.  No regressions.
+
+### 2. Review Follow-up Handling
+
+**IF Task is `[AI-Review]` follow-up:**
+1.  Add to `resolved_review_items`.
+2.  Mark task `[x]`.
+3.  Mark corresponding Action Item `[x]` in Review Section.
+4.  Log resolution in Completion Notes.
+
+### 3. Mark Complete
+
+**IF All Gates Pass:**
+1.  Mark task/subtask `[x]`.
+2.  Update **File List** (new/modified/deleted files).
+3.  Add **Completion Notes**.
+
+**IF Validation Fails:**
+1.  **HALT**. Do not proceed. Fix issues.
+
+### 4. Loop Decision
+
+1.  Save Story File.
+2.  Check for **Incomplete Tasks**.
+
+**IF Tasks Remain:**
+1.  Load, read entire file, then execute `{nextTaskStep}` (`step-07-implement.md`).
+
+**IF NO Tasks Remain:**
+1.  Load, read entire file, then execute `{completionStep}` (`step-11-mark-review.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-11-mark-review.md

@@ -0,0 +1,50 @@
+---
+name: 'step-11-mark-review'
+description: 'Story completion and mark for review'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-11-mark-review.md'
+nextStepFile: '{workflow_path}/steps/step-12-communication.md'
+sprintStatusFile: '{implementation_artifacts}/sprint-status.yaml'
+---
+
+# Step 11: Final Validation & Status Update
+
+## STEP GOAL:
+
+Perform final Definition of Done (DoD) validation and update story status to "review".
+
+## EXECUTION PROTOCOLS:
+
+### 1. Final Validation Gates
+
+1.  **Re-scan Story**: Verify ALL tasks `[x]`.
+2.  **Full Regression**: Run suite.
+3.  **File List**: Ensure complete.
+4.  **UI Compliance**: Verify `siesa-ui-kit`.
+5.  **DoD Checklist**:
+    *   ACs met.
+    *   Tests (Unit/Int/E2E) pass.
+    *   Quality checks pass.
+    *   Dev Notes updated.
+
+**IF Validation Fails:** HALT and Fix.
+
+### 2. Update Story Status
+
+1.  Update Story Status section to: `review`.
+
+### 3. Update Sprint Status
+
+**IF `{sprintStatusFile}` EXISTS:**
+1.  Load FULL file.
+2.  Update `development_status[{{story_key}}] = "review"`.
+3.  Save file (preserving comments).
+4.  Output: `✅ Story status updated to "review" in sprint-status.yaml`.
+
+### 4. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-12-communication.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-12-communication.md

@@ -0,0 +1,45 @@
+---
+name: 'step-12-communication'
+description: 'Completion communication and user support'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-12-communication.md'
+---
+
+# Step 12: Communication & Handover
+
+## STEP GOAL:
+
+Inform the user of completion, provide a summary, and suggest next steps.
+
+## EXECUTION PROTOCOLS:
+
+### 1. Prepare Summary
+
+1.  Compile key accomplishments: Story ID/Title, Files Modified, Tests Added.
+2.  Summarize from **Completion Notes**.
+
+### 2. User Communication
+
+1.  Output:
+    ```
+    🎉 **Story Implementation Complete**
+    Story: {{story_key}}
+    Status: review
+    Files: {{files_modified_count}}
+    Tests: {{tests_added_summary}}
+    ```
+2.  Provide Story File Path.
+
+### 3. Explanation & Handover
+
+1.  Ask if user needs explanations (Technical decisions, How to test, etc.).
+2.  **IF User Asks**: Provide clear context tailored to skill level.
+3.  **Next Steps**: Suggest running `code-review` workflow.
+
+### 4. Completion
+
+**TERMINATE WORKFLOW.**

package/bmad/bmm/workflows/4-implementation/dev-story/workflow.md

@@ -0,0 +1,44 @@
+---
+name: dev-story
+description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
+web_bundle: true
+---
+
+# Dev Story Workflow
+
+**Goal:** Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file
+- **Just-In-Time Loading**: Only the current step file is in memory
+- **Sequential Enforcement**: Sequence within the step files must be completed in order
+- **State Tracking**: Document progress in output file frontmatter
+- **Append-Only Building**: Build documents by appending content
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed when user selects 'C'
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+- `implementation_artifacts`, `user_skill_level`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{workflow_path}/steps/step-01-find-story.md` to begin the workflow.

package/claude/commands/bmad/bmm/workflows/dev-story.md

@@ -6,8 +6,8 @@ IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the c
 
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.md
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.md as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/gemini/commands/bmad-workflow-bmm-dev-story.toml

@@ -4,8 +4,8 @@ IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the c
 
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.md
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.md as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "siesa-agents",
-  "version": "2.1.48",
+  "version": "2.1.49",
   "description": "Paquete para instalar y configurar agentes SIESA en tu proyecto",
   "main": "index.js",
   "bin": {