siesa-agents 2.1.78 → 2.1.79

package/siesa-agents/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}/_siesa-agents/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/siesa-agents/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}/_siesa-agents/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/siesa-agents/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}/_siesa-agents/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/siesa-agents/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}/_siesa-agents/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/siesa-agents/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}/_siesa-agents/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/siesa-agents/bmm/workflows/4-implementation/dev-story/workflow_ext.md

@@ -140,4 +140,10 @@ node "{project_root}/_siesa-agents/observability/scripts/sa-emit.js" --event wor
 
 - If any `sa-emit` call fails, log the error and **continue the workflow normally**. Observability must never block the workflow.
 - Use the exact `{{story_key}}` value as resolved in step-01 (e.g., `1-1-user-authentication`).
-- Do NOT wait for user confirmation to execute these commands — they are silent background operations.
+- Do NOT wait for user confirmation to execute these commands — they are silent background operations.
+---
+
+## 7. Additional Completion Checklist
+
+Before marking a story as complete, verify the Siesa-specific checklist items at:
+`@_siesa-agents/bmm/workflows/4-implementation/dev-story/checklist_ext.md`

package/siesa-agents/bmm/workflows/4-implementation/sprint-planning/workflow_ext.md

@@ -117,3 +117,63 @@ Crear el archivo con la siguiente estructura:
 ## 4. PRIMERA EJECUCIÓN DEL SPRINT-STATUS
 
 Cuando `sprint-status.yaml` NO existe, continuar con el flujo estándar FULL_LOAD sin alteraciones, aplicando las reglas de trazabilidad de la sección 1 y generando el `feature-status.yaml` según la sección 3.
+
+---
+
+## 5. DATE IDEMPOTENCY — STEP 3.5 (Siesa Extension)
+
+**TRIGGER:** Before generating the `sprint-status.yaml` output file (between step 3 and step 4 of the base workflow).
+
+### Step 3.5: Preserve Existing Date Fields
+
+Before writing the output, load any existing date fields to prevent overwriting them:
+
+```
+existing_dates = {}           // map of preserved dates
+original_generated = {date}   // default: today
+
+IF FILE_EXISTS({status_file}):
+  existing_yaml = PARSE_YAML( READ_FILE({status_file}) )
+
+  // Preserve each epic-n-last-update already recorded
+  FOR each key IN existing_yaml.development_status:
+    IF key MATCHES "epic-{n}-last-update":
+      IF existing_yaml.development_status[key] IS NOT EMPTY:
+        existing_dates[key] = existing_yaml.development_status[key]
+
+  // Preserve the original generation date (never bump it on re-runs)
+  IF existing_yaml.generated IS NOT NULL:
+    original_generated = existing_yaml.generated
+```
+
+### Resolution Function (used in Step 4)
+
+```
+FUNCTION resolve_epic_date(epic_n):
+  date_key = "epic-{n}-last-update"
+  IF date_key IN existing_dates:
+    RETURN existing_dates[date_key]   // existing date — DO NOT overwrite
+  ELSE:
+    RETURN {date}                     // new epic — initialize with today
+```
+
+### Rules
+
+- `epic-n-last-update` is initialized ONLY if the key does not already exist in `{status_file}`.
+- Once set, the value is **NEVER** modified by `sprint-planning`.
+- Use `original_generated` (not today's date) for the `generated` field header.
+- Use `resolve_epic_date(n)` for every `epic-n-last-update` — never hardcode `{date}` directly.
+- Running `sprint-planning` multiple times must produce **identical** date fields.
+
+### sprint-status.yaml Date Field Format
+
+Each epic entry must include:
+```yaml
+epic-{n}: {status}
+epic-{n}-last-update: {resolve_epic_date(n)}   # preserved if exists, today if new
+```
+
+### Additional Checklist Item
+
+Before finalizing:
+- [ ] Every epic has a corresponding `epic-n-last-update` entry with a non-empty date value.

package/siesa-agents/bmm/workflows/4-implementation/sprint-status/workflow_ext.md

@@ -36,7 +36,7 @@ Invocar `AskUserQuestion` con la siguiente configuración:
 ➡️ Encadenando con Retrospective tal como seleccionaste al inicio...
 ```
 
-Luego invocar `/bmad:bmm:workflows:retrospective`.
+Luego invocar `/bmad-retrospective `.
 
 ---
 

package/siesa-agents/bmm/workflows/5-documentation/README.md

@@ -0,0 +1,235 @@
+# 5-Documentation Phase - BMM Module
+
+**Phase:** Documentation
+**Module:** BMM (Build & Management Module)
+**Purpose:** Workflows for generating user documentation, API documentation, technical guides, and other end-user/developer documentation artifacts from project artifacts (PRDs, Epics, Architecture, Stories)
+
+---
+
+## Overview
+
+La fase **5-documentation** contiene workflows especializados en la generación de documentación técnica y de usuario a partir de artefactos de proyecto existentes. Estos workflows automatizan la creación de guías comprehensivas, asegurando consistencia, trazabilidad y calidad en la documentación producida.
+
+---
+
+## Workflows Disponibles
+
+### 📚 create-user-guide
+
+**Ruta:** `_siesa-agents/bmm/workflows/5-documentation/create-user-guide/`
+**Comando:** `/sa-create-user-guide`
+**Versión:** 1.0.0
+
+#### Descripción
+
+Genera guías de usuario en español desde features del proyecto (archivos individuales `prd/feature-*.md` + `epics/epic-*.md`), con diagramas Mermaid, screenshot placeholders y trazabilidad `[Source: FX Story Y.Z]`.
+
+#### Características Principales
+
+- ✅ **Salida en Español:** Archivo único por audiencia, actualizable con nuevos features
+- ✅ **Diagramas Mermaid:** Incluye diagramas para cada feature y workflow
+- ✅ **Screenshot Placeholders:** Sistema estructurado de placeholders con índice
+- ✅ **Trazabilidad:** Citaciones a épicas y stories de origen
+- ✅ **Continuación:** Soporte para resumir workflows interrumpidos
+- ✅ **Enfocado en Features:** Lee `prd/feature-*.md` + `epics/epic-*.md` por feature seleccionada
+
+#### Estructura de Archivos (15 archivos)
+
+```
+create-user-guide/
+├── workflow.md                              # Entry point del workflow
+├── workflow-plan-create-user-guide.md       # Documento de planificación
+│
+├── steps/                                   # 8 step files
+│   ├── step-01-init.md                     # Inicialización + detección continuación
+│   ├── step-01b-continue.md                # Reanudación de workflow
+│   ├── step-02-seleccion-epicas.md         # Selección de épicas (PRESCRIPTIVE)
+│   ├── step-03-analisis-fuentes.md         # Análisis de artefactos (INTENT-BASED)
+│   ├── step-04-elicitacion.md              # Elicitación de info (INTENT-BASED)
+│   ├── step-05-generacion-espanol.md       # Generación español (PRESCRIPTIVE)
+│   ├── step-06-traduccion-ingles.md        # Traducción inglés (PRESCRIPTIVE)
+│   └── step-07-validacion-guardado.md      # Validación final (PRESCRIPTIVE)
+│
+├── templates/                               # 2 templates bilingües
+│   ├── user-guide-template-es.md           # Template español con frontmatter
+│   └── user-guide-template-en.md           # Template inglés con frontmatter
+│
+└── data/                                    # 3 CSV data files
+    ├── audience-types.csv                  # 4 tipos de audiencia
+    ├── diagram-types.csv                   # 5 tipos de diagramas Mermaid
+    └── section-structure.csv               # 9 secciones de guía
+
+```
+
+#### Flujo del Workflow (8 pasos)
+
+1. **step-01-init** → Inicialización y configuración de audiencia
+   - Detecta workflows existentes
+   - Configura audiencia (enduser/admin/api/mixed)
+   - Crea documento inicial con frontmatter
+
+2. **step-01b-continue** → Continuación (si aplica)
+   - Carga estado guardado
+   - Resume desde último paso completado
+
+3. **step-02-seleccion-epicas** → Selección de Features
+   - Escanea `planning_artifacts/prd/feature-*.md`
+   - Usuario selecciona qué features documentar
+   - Verifica existencia de épica correspondiente por feature
+   - Registra selección en frontmatter (`features_selected`)
+
+4. **step-03-analisis-fuentes** → Análisis de Features
+   - Por cada feature: lee `prd/feature-*.md` (descripción, FRs, key behaviors)
+   - Si existe: lee `epics/epic-*.md` (historias, GWT, acceptance criteria)
+   - Lee contexto general (goals.md, background-context.md)
+   - Genera sección "Contexto del Proyecto"
+
+5. **step-04-elicitacion** → Elicitación de preferencias
+   - Conversación para capturar nivel técnico
+   - Escenarios adicionales
+   - Features a excluir
+
+6. **step-05-generacion-espanol** → Generación en español
+   - Genera 9 secciones completas
+   - Incluye diagramas Mermaid para cada feature
+   - Agrega screenshot placeholders
+   - Cita fuentes `[Source: FX Story Y.Z]`
+
+7. **step-06-traduccion-ingles** → ⛔ DESHABILITADO
+   - Paso conservado como referencia pero no se ejecuta
+   - El workflow salta directamente a step-07
+
+8. **step-07-validacion-guardado** → Validación y guardado
+   - Ejecuta TOP 5 validaciones
+   - Presenta resultados al usuario
+   - Permite loop a step-05 para correcciones
+   - Guarda ambas versiones + index.md
+
+#### Datos Estructurados
+
+**audience-types.csv** (4 tipos de audiencia)
+```csv
+audience_id,audience_name_es,audience_name_en,description_es,description_en,filename_prefix
+enduser,Usuarios Finales,End Users,...,enduser-guide
+admin,Administradores,Administrators,...,admin-guide
+api,Consumidores de API,API Consumers,...,api-guide
+mixed,Audiencia Mixta,Mixed Audience,...,complete-guide
+```
+
+**diagram-types.csv** (5 tipos de diagramas)
+```csv
+content_type,diagram_type,mermaid_syntax,use_case_es,use_case_en
+feature_overview,flowchart,"flowchart LR",...
+user_workflow,flowchart,"flowchart TD",...
+sequential_process,sequenceDiagram,...
+state_changes,stateDiagram-v2,...
+user_journey,journey,...
+```
+
+**section-structure.csv** (9 secciones)
+```csv
+section_id,section_name_es,section_name_en,description,required
+1,Introducción,Introduction,...,true
+2,Primeros Pasos,Getting Started,...,true
+3,Conceptos Clave,Core Concepts,...,true
+4,Funcionalidades,Features and How to Use Them,...,true
+5,Flujos de Trabajo,Common Workflows,...,true
+6,Solución de Problemas,Troubleshooting,...,false
+7,Preguntas Frecuentes,FAQ,...,true
+8,Glosario,Glossary,...,true
+9,Índice de Capturas,Screenshot Index,...,true
+```
+
+#### Criterios de Validación (TOP 5)
+
+1. **📄 Bilingual Output Completo** - Ambas versiones existen con estructura idéntica
+2. **🔗 Source Citations Obligatorias** - Cada feature tiene citación de origen
+3. **📊 Diagramas Mermaid Completos** - Cada feature/workflow tiene diagrama
+4. **📸 Screenshot Placeholders Presentes** - Formato correcto + índice
+5. **✅ Self-Check Pasado** - Completeness >= 90%, sin TODOs
+
+#### Output Generado
+
+**Ubicación:** `docs/user-guide/`
+
+```
+docs/user-guide/
+├── index.md                          # Selector de idioma
+├── es/
+│   └── {audience}-guide.md          # Guía en español
+└── en/
+    └── {audience}-guide.md          # Guía en inglés
+```
+
+Donde `{audience}` = `enduser-guide` | `admin-guide` | `api-guide` | `complete-guide`
+
+#### Patrones de Interacción
+
+- **PRESCRIPTIVE Steps** (01, 02, 05, 06, 07): Instrucciones exactas, ejecución paso a paso
+- **INTENT-BASED Steps** (03, 04): Objetivo claro, libertad de implementación
+- **Collaboration Level:** 40% user input / 60% autonomous generation
+
+#### Tecnologías Utilizadas
+
+- Mermaid.js para diagramas
+- Markdown con frontmatter YAML
+- CSV para datos estructurados
+- Sistema de templates bilingües
+
+---
+
+## Estadísticas de la Fase
+
+| Métrica | Valor |
+|---------|-------|
+| Total Workflows | 1 |
+| Total Archivos | 15 |
+| Step Files | 8 |
+| Templates | 2 |
+| Data Files | 3 |
+| Idiomas Soportados | 2 (ES/EN) |
+
+---
+
+## Uso
+
+Para ejecutar el workflow create-user-guide:
+
+```bash
+/sa-create-user-guide
+```
+
+O mediante Skill tool:
+```bash
+sa-create-user-guide
+```
+
+---
+
+## Arquitectura
+
+Todos los workflows en esta fase utilizan **step-file architecture**:
+
+- **Micro-file Design**: Cada step es autocontenido
+- **Just-In-Time Loading**: Solo el step actual en memoria
+- **Sequential Enforcement**: Secuencia estricta sin optimizaciones
+- **State Tracking**: Progreso en frontmatter `stepsCompleted`
+- **Append-Only Building**: Construcción incremental de documentos
+
+---
+
+## Próximos Workflows (Planificados)
+
+- `create-api-docs` - Generación de documentación API desde arquitectura
+- `create-tech-guide` - Guías técnicas para desarrolladores
+- `create-deployment-guide` - Documentación de deployment y operaciones
+- `update-documentation` - Actualización de docs existentes con cambios
+
+---
+
+## Metadatos
+
+**Última Actualización:** 2026-01-14
+**Creado Por:** BMAD Module Builder Workflow
+**Versión BMAD:** 6.0
+**Módulo:** BMM (Build & Management Module)