siesa-agents 2.1.78 → 2.1.80

package/siesa-agents/bmm/workflows/fast-track-dev/workflow-plan-fast-track-dev.md

@@ -1,198 +0,0 @@
----
-stepsCompleted: [1, 2, 3, 4, 6, 7, 8, 9]
-status: COMPLETE
----
-
-# Workflow Creation Plan: fast-track-dev
-
-## Initial Project Context
-
-- **Module:** bmm
-- **Target Location:** _siesa-agents/bmm/workflows/fast-track-dev
-- **Created:** 2026-03-16
-- **Problem Solved:** Automatizar el ciclo manual y secuencial de create-story → dev-story → code-review mediante ejecución de un script Python
-- **Target Users:** Desarrolladores
-
----
-
-## Requirements (Step 2)
-
-### Workflow Type
-- **Action Workflow** — ejecuta acciones (orquestación de herramientas/scripts), no genera documentos
-
-### Workflow Purpose & Scope
-- Servir de interfaz para invocar `bmad_orchestrator.py`, presentando al desarrollador todas las opciones disponibles del script
-- Construir el comando correcto según la selección del usuario y ejecutarlo
-- El script ya maneja la lógica de negocio (create-story → dev-story → code-review)
-
-### Script Details
-- **Ruta del script:** `C:\labs\siesaAgentsAlpha\_siesa-agents\scripts\bmad_orchestrator.py`
-- **Comando de ejecución:** `C:\Users\sebas\AppData\Local\Programs\Python\Python310\python.exe C:\labs\siesaAgentsAlpha\_siesa-agents\scripts\bmad_orchestrator.py [opciones]`
-- **Fuente de verdad:** `_bmad-output/implementation-artifacts/sprint-status.yaml`
-- **Estado de resume:** `_siesa-agents/scripts/.orchestrator-state.json`
-- **Logs:** `_siesa-agents/scripts/logs/`
-
-### Opciones del Script a Exponer (todas)
-| Flag | Descripción | Valor requerido |
-|---|---|---|
-| `--epic N` | Procesar todas las historias de un epic | Número de epic |
-| `--only-story ID` | Procesar exclusivamente una historia | ID de historia (ej: 2-1) |
-| `--story ID` | Empezar desde una historia específica | ID de historia (ej: 3-2) |
-| `--step [create/dev/review]` | Empezar desde un paso específico (primera historia) | Paso a ejecutar |
-| `--dry-run` | Mostrar el plan sin ejecutar | No requiere valor |
-| `--model` | Elegir modelo de Claude | Nombre del modelo |
-| *(sin flags)* | Procesar todas las historias pendientes | No requiere valor |
-
-### Opción de Resume
-- Al iniciar, el workflow debe detectar si existe `.orchestrator-state.json`
-- Si existe, **ofrecer al desarrollador la opción de reanudar** desde donde quedó
-- Si el desarrollador elige reanudar, ejecutar sin flags adicionales (el script retoma automáticamente)
-
-### Validación de Prerrequisitos
-- Verificar que `_bmad-output/implementation-artifacts/sprint-status.yaml` existe antes de ejecutar
-- Si no existe, informar al desarrollador con mensaje claro y detener el workflow
-
-### Flujo del Workflow
-- **Lineal con branching** según la opción elegida por el desarrollador:
-  1. Verificar prerrequisitos (sprint-status.yaml)
-  2. Verificar estado previo (ofrecer resume si aplica)
-  3. Presentar menú de opciones del script
-  4. Solicitar el valor necesario según la opción elegida
-  5. Construir y mostrar el comando que se va a ejecutar
-  6. Confirmar con el desarrollador antes de ejecutar
-  7. Ejecutar el script vía Bash
-  8. Reportar resultado (éxito o error)
-
-### Interaction Style
-- **Prescriptivo** — menús claros, preguntas específicas, no conversacional
-- Moderadamente autónomo: el desarrollador solo interactúa al inicio para configurar; el script corre solo después
-
-### Outputs
-- El script produce sus propios logs en `_siesa-agents/scripts/logs/`
-- El workflow muestra en pantalla el output del script en tiempo real
-- Al finalizar, confirma éxito (exit 0) o muestra el error y la instrucción de resume
-
-### Success Criteria
-- Sprint-status.yaml existe y tiene historias pendientes
-- El desarrollador configura las opciones correctamente
-- El script se ejecuta y termina con exit code 0
-- El desarrollador sabe qué historias fueron procesadas
-
----
-
-## Tools Configuration (Step 3)
-
-### Core BMAD Tools
-- **Party-Mode**: Excluido — workflow prescriptivo, no requiere debate multi-agente
-- **Advanced Elicitation**: Excluido — flujo simple y directo
-- **Brainstorming**: Excluido — no aplica para un workflow ejecutor
-
-### LLM Features
-- **Web-Browsing**: Excluido — no se necesita información externa
-- **File I/O**: **Incluido** — para validar existencia de `sprint-status.yaml` y del state file `.orchestrator-state.json`
-- **Sub-Agents**: Excluido — no se requiere delegación
-- **Sub-Processes**: **Incluido** — para ejecutar el script Python vía Bash
-
-### Memory Systems
-- **Sidecar File**: Excluido — el script ya maneja su propio estado en `.orchestrator-state.json`
-
-### External Integrations
-- Ninguna requerida
-
-### Installation Requirements
-- Ninguna — todas las herramientas seleccionadas están disponibles sin instalación adicional
-
----
-
-## Workflow Design (Step 6)
-
-### Continuation Support
-- **No requerido** — workflow de sesión única; el script maneja su propio estado
-
-### Step Structure (3 pasos)
-
-#### step-01-init.md
-- Validar existencia de `_bmad-output/implementation-artifacts/sprint-status.yaml`
-- Si no existe → error claro y detener
-- Detectar si `_siesa-agents/scripts/.orchestrator-state.json` existe
-- Si existe → ofrecer opción de RESUME al desarrollador
-  - Si elige resume → construir comando sin flags adicionales y saltar a step-03
-- Auto-proceed a step-02
-
-#### step-02-configure.md
-- Presentar menú con todas las opciones del script:
-  - [1] Procesar todas las historias pendientes (sin flags)
-  - [2] Por épica: `--epic N`
-  - [3] Solo una historia: `--only-story ID`
-  - [4] Desde una historia específica: `--story ID`
-  - [5] Solo ver el plan: `--dry-run`
-  - [6] Opciones avanzadas: `--step [create/dev/review]` y/o `--model`
-- Solicitar el valor necesario según la opción elegida
-- Mostrar el comando completo construido
-- Confirmar con el desarrollador → proceder a step-03
-
-#### step-03-execute.md
-- Ejecutar el script vía Bash con el comando construido
-- Mostrar output en tiempo real
-- Al finalizar:
-  - Exit 0 → mensaje de éxito
-  - Exit != 0 → mensaje de error + instrucción de resume (`python ... bmad_orchestrator.py`)
-- FIN del workflow
-
-### Decision Points / Branching
-| Punto | Condición | Acción |
-|---|---|---|
-| step-01 | `.orchestrator-state.json` existe | Ofrecer resume → si acepta, skip step-02 directo a step-03 |
-| step-02 | Opción 6 elegida | Sub-menú con `--step` y `--model` |
-| step-03 | Exit code del script | Éxito vs error + instrucción de resume |
-
-### AI Role & Persona
-- **Rol:** Asistente técnico de orquestación BMAD
-- **Tono:** Directo y claro — prescriptivo, sin conversación innecesaria
-- **Estilo:** Menús numerados, preguntas específicas de valor único
-
-### File Structure
-```
-fast-track-dev/
-├── workflow.md
-└── steps/
-    ├── step-01-init.md
-    ├── step-02-configure.md
-    └── step-03-execute.md
-```
-
----
-
-## Build Summary (Step 7)
-
-### Files Generated
-
-| Archivo | Ruta | Estado |
-|---|---|---|
-| `workflow.md` | `_siesa-agents/bmm/workflows/fast-track-dev/workflow.md` | ✅ Creado |
-| `step-01-init.md` | `_siesa-agents/bmm/workflows/fast-track-dev/steps/step-01-init.md` | ✅ Creado |
-| `step-02-configure.md` | `_siesa-agents/bmm/workflows/fast-track-dev/steps/step-02-configure.md` | ✅ Creado |
-| `step-03-execute.md` | `_siesa-agents/bmm/workflows/fast-track-dev/steps/step-03-execute.md` | ✅ Creado |
-
-### Next Steps for Testing
-1. Revisar los archivos generados en el paso de review (step-08)
-2. Instalar el workflow en el módulo bmm
-3. Registrar en el skill system con el comando `/bmad:bmm:workflows:fast-track-dev`
-4. Probar con un sprint activo que tenga historias en estado `backlog`
-
----
-
-## Review Findings (Step 8)
-
-### Validation Results
-- Estructura de archivos: ✅ PASSED
-- Cumplimiento de templates: ✅ PASSED
-- Consistencia entre archivos: ✅ PASSED
-- Verificación de requerimientos: ✅ PASSED
-- Buenas prácticas: ✅ PASSED
-
-### Issues
-- ⚠️ Warning: `workflow_path` en step files apunta a bmb-creations — debe actualizarse al instalar en ubicación final bmm
-- ⚠️ Minor: conflicto visual de `[C]` en sub-menú avanzado de step-02 vs `[C]` de confirmación (pendiente fix)
-
-### Approval Status: ✅ APROBADO — listo para instalación

package/siesa-agents/bmm/workflows/fast-track-dev/workflow.md

@@ -1,57 +0,0 @@
----
-name: fast-track-dev
-description: Automated execution of the full story development cycle (create-story → dev-story → code-review) via Python orchestrator script
-web_bundle: true
----
-
-# Fast Track Dev
-
-**Goal:** Execute the full automated story development cycle (create-story → dev-story → code-review) by invoking the BMAD Python orchestrator script with the developer's chosen parameters.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a technical automation assistant collaborating with a developer. This is a partnership, not a client-vendor relationship. You bring expertise in running the BMAD orchestrator, while the developer brings their knowledge of which stories and epics to process. Work together as equals.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere to 1 file as directed at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### 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 to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-- ✅ **ALWAYS** speak output in the communication language from config `{communication_language}`
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Module 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`
-
-### 2. First Step EXECUTION
-
-Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.

package/siesa-agents/bmm/workflows/workflow-status/Init/workflow_ext.md

@@ -1,194 +0,0 @@
-# MANDATORY RULE: WORKFLOW-INIT — SIESA BASE REPOSITORY CLONING
-
-**TRIGGER:** Every time `workflow-init` is executed (`/bmad:bmm:workflows:workflow-init`).
-
-**CONTEXT TO INJECT:** Load and hold these rules in memory. Apply them at the end of the workflow as described in Section 1.
-
----
-
-## 1. Step 10: Clone Siesa Base Repositories
-
-This step executes **immediately after Step 9**, and **only if** the user confirmed creating the tracking file (answered "y"). If the user skipped Step 9 (answered "n"), skip this step entirely.
-
-### 1.1 Resolve project root
-
-Before running any command, determine the actual absolute path of `{project-root}`.
-This is the **current working directory** of the agent at runtime — the project folder where `_bmad/` and `_siesa-agents/` are installed.
-Use this resolved path in all subsequent commands. Do **not** pass the literal string `{project-root}` to the shell.
-
-### 1.2 Present menu to the user
-
-Use the **AskUserQuestion** tool to present the following options:
-
-> "To complete the project setup, I can clone the Siesa base repositories into the `apps/` folder. What would you like to clone?"
->
-> **[1] Frontend + Backend** — Clone both base repositories.
-> **[2] Backend only** — Clone `BaseBackend` only.
-> **[3] Skip** — Do not clone any repository.
-
-### 1.3 Execution logic per selection
-
-**For options [1] and [2] — ensure `apps/` exists first:**
-
-```bash
-mkdir -p <resolved-project-root>/apps
-```
-
-**[1] Frontend + Backend:**
-
-Create base Architecture
-Copy the file `@_siesa-agents/resources/architecture/architecture-both.md ` to `{planning_artifacts}/architecture.md`.
-
-  - If the destination directory does not exist, create it first.
-  - Do not modify the file contents — copy as-is.
-  - After copying, confirm the file exists at the destination.
-
-Create base UX/UI specifications
-Copy the file `@_siesa-agents/resources/ux-ui/ux-design-specification.md` to `{planning_artifacts}/ux-design-specification.md.md`.
-
-  - If the destination directory does not exist, create it first.
-  - Do not modify the file contents — copy as-is.
-  - After copying, confirm the file exists at the destination.
-
-Check and clone Frontend:
-```bash
-# Only run if apps/Frontend does NOT exist
-git clone https://github.com/SiesaTeams/BaseFrontend.git <resolved-project-root>/apps/Frontend
-```
-
-Check and clone Backend:
-```bash
-# Only run if apps/Backend does NOT exist
-git clone https://github.com/SiesaTeams/BaseBackend.git <resolved-project-root>/apps/Backend
-```
-
-**[2] Backend only:**
-
-Create base Architecture
-Copy the file `@_siesa-agents/resources/architecture/architecture-single-backend.md ` to `{planning_artifacts}/architecture.md`.
-
-  - If the destination directory does not exist, create it first.
-  - Do not modify the file contents — copy as-is.
-  - After copying, confirm the file exists at the destination.
-
-Check and clone Backend:
-```bash
-git clone https://github.com/SiesaTeams/BaseBackend.git <resolved-project-root>/apps/Backend
-```
-
-**[3] Skip:** Do not execute any command. Proceed to the closing message.
-
-### 1.4 Pre-clone existence check
-
-Before running each `git clone`, verify whether the target directory already exists:
-
-- If `apps/Frontend` already exists → do **not** clone it; inform the user:
-  > "⚠️ `apps/Frontend` already exists. Skipping Frontend clone."
-
-- If `apps/Backend` already exists → do **not** clone it; inform the user:
-  > "⚠️ `apps/Backend` already exists. Skipping Backend clone."
-
-Continue with the remaining repo if only one was skipped.
-
-### 1.5 Error handling
-
-If a `git clone` command fails (network error, auth issue, etc.):
-
-1. Show the exact error output to the user.
-2. Ask: "❌ Could not clone `{repo-name}`. Would you like to retry? (y/n)"
-3. If "y": retry the same command once.
-4. If "n" or second failure: skip that repo and continue.
-
-### 1.6 Confirmation output
-
-After completing the cloning (success or partial), display a summary:
-
-```
-✅ Base repositories cloned into: <resolved-project-root>/apps/
-
-  Frontend  →  apps/Frontend   (https://github.com/SiesaTeams/BaseFrontend.git)
-  Backend   →  apps/Backend    (https://github.com/SiesaTeams/BaseBackend.git)
-
-Project structure is ready. Happy building! 🚀
-```
-
-Adapt the message if only one repo was cloned or if any were skipped.
-
----
-
-## 2. Critical Rules
-
-1. **This step is mandatory in the flow** — once the menu is presented, the agent MUST act on the user's selection.
-2. **Do NOT modify Steps 1–9** of the base `workflow-init`. This extension only appends behavior at the end.
-3. **Always use the resolved absolute path** when running Bash commands. Never pass the literal string `{project-root}` to the shell — substitute it with the actual path first.
-4. **Each `git clone` runs as a single independent Bash tool call** using the full absolute target path as the destination argument — do not rely on `cd` to set context across calls.
-5. **Condition gate** — if the user did not confirm Step 9 (answered "n"), this entire step is skipped without presenting the menu.
-
----
-
-## 3. MANDATORY RULE — PHASE BRANCH CREATION AT WORKFLOW START
-
-**TRIGGER:** Immediately when the user initiates this workflow (e.g., `/bmad:bmm:workflows:workflow-init`).
-
-**CRITICAL INSTRUCTION:** Before executing any workflow step, you MUST invoke the `generate-commits-by-phase` skill to create the Phase 1 discovery branch.
-
-### EXECUTION STEPS (PERFORM THESE ACTIONS NOW, BEFORE ANYTHING ELSE)
-
-**STEP 1: INVOKE THE SKILL — CREATE PHASE 1 BRANCH**
-
-Run the skill `generate-commits-by-phase` with **Operation A: Create Phase Branch** for **Phase 1 (discovery)**:
-
-```bash
-node _siesa-agents/scripts/phases/phase1.js
-```
-
-- If the `discovery` branch already exists, the script will report it — continue normally.
-- If it is created successfully, confirm to the user and proceed.
-
-**STEP 2: CONFIRM AND CONTINUE**
-
-Output to the user:
-> `✅ Phase 1 (discovery) branch ready. Proceeding with workflow-init...`
-
-**DO NOT proceed to the workflow steps until this rule is fully executed.**
-
----
-
-## 4. MANDATORY RULE — PHASE COMMIT AT WORKFLOW END
-
-**TRIGGER:** Immediately after all workflow steps complete (including Section 1 — repository cloning).
-
-**CRITICAL INSTRUCTION:** As the final action of this workflow, you MUST invoke the `generate-commits-by-phase` skill to commit all changes for Phase 1.
-
-### EXECUTION STEPS (PERFORM THESE ACTIONS AT THE END)
-
-**STEP 1: INSPECT CHANGES**
-
-Before committing, inspect the repository state:
-
-1. Run `git status --short` to identify which files were created or modified.
-2. Run `git diff --stat` to understand the scope of changes.
-
-**STEP 2: GENERATE COMMIT MESSAGE**
-
-Build a concise commit message using the format:
-`[Phase 1 - Discovery] <brief description of what was produced>`
-
-**Example:** `[Phase 1 - Discovery] initialize project structure and clone base repositories`
-
-Write the message in the same language used throughout the conversation.
-
-**STEP 3: INVOKE THE SKILL — COMMIT PHASE 1 CHANGES**
-
-Run the skill `generate-commits-by-phase` with **Operation B: Commit All Changes** for **Phase 1 (discovery)**:
-
-```bash
-node _siesa-agents/scripts/phases/phase1.js --commit "<generated commit message>"
-```
-
-**STEP 4: CONFIRM COMPLETION**
-
-Output to the user:
-> `✅ Project initialization changes committed to Phase 1 (discovery) branch.`
-
-**This is the LAST action of the workflow. Do not execute any further steps after this commit.**