siesa-agents 2.1.70 → 2.1.72

package/bin/install.js

@@ -4,6 +4,7 @@ const fs = require('fs-extra');
 const path = require('path');
 const { sourceMapsEnabled } = require('process');
 const readline = require('readline');
+const { execSync } = require('child_process');
 
 class SiesaBmadInstaller {
   constructor() {
@@ -108,6 +109,82 @@ class SiesaBmadInstaller {
       return fs.existsSync(folderPath);
     });
   }
+  
+  checkExistingGitInstallation() {
+    const gitDir = path.join(this.targetDir, '.git');
+    return fs.existsSync(gitDir);
+  }
+
+  checkExistingGitignore() {
+    const gitignorePath = path.join(this.targetDir, '.gitignore');
+    return fs.existsSync(gitignorePath);
+  }
+
+  async promptHasRepository() {
+    console.log('\n¿Tienes un repositorio remoto?');
+    console.log('1. Sí');
+    console.log('2. No, parametrizar manual después');
+
+    const rl = readline.createInterface({ input: process.stdin, output: process.stdout });
+    return new Promise((resolve) => {
+      rl.question('\nElige una opción (1 o 2): ', (answer) => {
+        rl.close();
+        resolve(answer.trim());
+      });
+    });
+  }
+
+  async promptRepositoryUrl() {
+    const rl = readline.createInterface({ input: process.stdin, output: process.stdout });
+    return new Promise((resolve) => {
+      rl.question('Ingresa la URL del repositorio: ', (answer) => {
+        rl.close();
+        resolve(answer.trim());
+      });
+    });
+  }
+
+  async installGitignore() {
+    const gitignorePath = path.join(this.targetDir, '.gitignore');
+    const entries = [
+      'node_modules/',
+      '.claude/commands/get-features/oauth-config.json',
+      '.claude/commands/get-features/tokens.json'
+    ];
+
+    let content = entries.join('\n') + '\n';
+
+    // Si ya existe, agregar solo las entradas que falten
+    if (fs.existsSync(gitignorePath)) {
+      const existing = await fs.readFile(gitignorePath, 'utf8');
+      const missing = entries.filter(e => !existing.includes(e));
+      if (missing.length === 0) {
+        console.log('✓ .gitignore ya contiene todas las entradas requeridas.');
+        return;
+      }
+      content = existing.trimEnd() + '\n' + missing.join('\n') + '\n';
+      console.log(`🔄 Actualizando .gitignore con ${missing.length} entrada(s) faltante(s)...`);
+    } else {
+      console.log('📝 Generando .gitignore...');
+    }
+
+    await fs.writeFile(gitignorePath, content, 'utf8');
+    console.log('✓ .gitignore instalado correctamente.');
+  }
+  
+  installGit(repository) {
+    const options = { cwd: this.targetDir, stdio: 'inherit' };
+
+    console.log('  Ejecutando git init...');
+    execSync('git init', options);
+    console.log('✓ Repositorio git inicializado.');
+
+    if (repository !== null) {
+      console.log(`  Configurando remote origin: ${repository}`);
+      execSync(`git remote add origin ${repository}`, options);
+      console.log('✓ Remote origin configurado.');
+    }
+  }
 
   async install() {
     this.showBanner();
@@ -129,6 +206,32 @@ class SiesaBmadInstaller {
         await this.performInstallation();
       }
 
+      //Verificar si ya existe un git
+      const hasExistingGitInstallation = this.checkExistingGitInstallation();
+      if(hasExistingGitInstallation){
+        console.log('✓ Ya existia una instalacion de un repositorio git en el proyecto, validando si existe el .gitignore...');
+        const hasExistingGitignore = this.checkExistingGitignore();
+        if(hasExistingGitignore){
+          console.log('✓ Ya existe un .gitignore, Actualizando...')
+          await this.installGitignore();
+        } else {
+          await this.installGitignore();
+        }
+      } else {
+        console.log('\nInstalando git...');
+        const hasRepo = await this.promptHasRepository();
+        if (hasRepo === '1') {
+          const repository = await this.promptRepositoryUrl();
+          await this.installGit(repository);
+        } else {
+          await this.installGit(null);
+          console.log('\n⚠️  ADVERTENCIA: No se configuró un repositorio remoto.');
+          console.log('   Para vincularlo más adelante, ejecuta manualmente:');
+          console.log('   git remote add origin <url-de-tu-repositorio>');
+        }
+        await this.installGitignore();
+      }
+
       console.log('✅ SIESA Agents instalado correctamente!');
       this.showPostInstallMessage();
 

package/claude/commands/bmad/bmm/workflows/check-implementation-readiness.md

@@ -2,4 +2,8 @@
 description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: 
+
+1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/3-solutioning/check-implementation-readiness/workflow_ext.md ` — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
+
+2. LOAD the FULL @_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/correct-course.md

@@ -5,7 +5,7 @@ description: 'Navigate significant changes during sprint execution by analyzing
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. ALWAYS Load and read the workflow extension from @{project-root}/_siesa-agents/bmm/workflows/3-solutioning/create-architecture/workflow_ext.md to understand the Company Standards Context.
+1. ALWAYS Load and read the workflow extension from @{project-root}/_siesa-agents/bmm/workflows/4-implementation/correct-course/workflow_ext.md to understand the Company Standards Context.
 2. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
 3. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
 4. Pass the yaml path _bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions

package/claude/commands/bmad/bmm/workflows/create-architecture.md

@@ -2,4 +2,8 @@
 description: 'Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: 
+
+1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/3-solutioning/create-architecture/workflow_ext.md ` — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
+
+2.LOAD the FULL @_siesa-agents/bmm/workflows/3-solutioning/create-architecture/workflow_ext.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/create-product-brief.md

@@ -2,4 +2,8 @@
 description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: 
+
+1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/1-analysis/create-product-brief/workflow_ext.md ` — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
+
+2. LOAD the FULL @_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/create-ux-design.md

@@ -2,4 +2,8 @@
 description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: 
+
+1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/2-plan-workflows/create-ux-design/workflow_ext.md ` — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
+
+2. LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/generate-project-context.md

@@ -5,7 +5,7 @@ description: 'Creates a concise project-context.md file with critical rules and
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS:
 
 <steps CRITICAL="TRUE">
-1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/2-planning/generate-project-context/workflow_ext.md — This contains mandatory context injection rules and an interactive menu. Apply them BEFORE proceeding.
+1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/generate-project-context/workflow_ext.md — This contains mandatory context injection rules and an interactive menu. Apply them BEFORE proceeding.
 2. AFTER the menu choices are handled: LOAD the FULL @_bmad/bmm/workflows/generate-project-context/workflow.md
 3. READ its entire contents and follow its directions exactly, making sure to apply the output file path constraints derived from STEP 1!
 </steps>

package/claude/commands/bmad/bmm/workflows/workflow-init.md

@@ -5,7 +5,7 @@ description: 'Initialize a new BMM project by determining level, type, and creat
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/workflow-status/Init/workflow_ext.md — This contains mandatory extension rules for cloning Siesa base repositories at Step 10. Hold them in memory and apply them at the end of the workflow.
+1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/workflow-status/Init/workflow_ext.md — This contains mandatory pre-workflow context injection rules and contains mandatory extension rules for cloning Siesa base repositories at Step 10. Hold them in memory and apply them at the end of the workflow.
 2. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
 3. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/init/workflow.yaml
 4. Pass the yaml path _bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions

package/claude/skills/generate-commits-by-phase/skill.md

@@ -0,0 +1,5 @@
+---
+description: 'Manages git branch creation and commits for the three SIESA development phases using the official phase scripts. Use this skill when a workflow step requests creating a phase branch or committing changes for a specific phase. Triggers when the user or a workflow references "phase 1/2/3 branch", "discovery/planning/solutioning branch", "commit phase changes", "create phase branch", or any operation involving the SIESA phase scripts (phase1.js, phase2.js, phase3.js).'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.agents/skills/generate-commits-by-phase/SKILL.md, READ its entire contents and follow its directions exactly!

package/gemini/commands/bmad-workflow-bmm-correct-course.toml

@@ -3,7 +3,7 @@ prompt = """
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. ALWAYS Load and read the workflow extension from @{project-root}/_siesa-agents/bmm/workflows/3-solutioning/create-architecture/workflow_ext.md to understand the Company Standards Context.
+1. ALWAYS Load and read the workflow extension from @{project-root}/_siesa-agents/bmm/workflows/4-implementation/correct-course/workflow_ext.md to understand the Company Standards Context.
 2. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
 3. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
 4. Pass the yaml path _bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions

package/gemini/commands/bmad-workflow-bmm-create-architecture.toml

@@ -1,4 +1,4 @@
 description = "BMAD BMM Workflow: create-architecture"
 prompt = """
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_siesa-agents/bmm/workflows/3-solutioning/create-architecture/workflow_ext.md, READ its entire contents and follow its directions exactly!
 """

package/gemini/commands/bmad-workflow-bmm-generate-project-context.toml

@@ -3,7 +3,7 @@ prompt = """
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS:
 
 <steps CRITICAL="TRUE">
-1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/2-planning/generate-project-context/workflow_ext.md — This contains mandatory context injection rules and an interactive menu. Apply them BEFORE proceeding.
+1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/generate-project-context/workflow_ext.md — This contains mandatory context injection rules and an interactive menu. Apply them BEFORE proceeding.
 2. AFTER the menu choices are handled: LOAD the FULL @_bmad/bmm/workflows/generate-project-context/workflow.md
 3. READ its entire contents and follow its directions exactly, making sure to apply the output file path constraints derived from STEP 1!
 </steps>

package/package.json

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

package/siesa-agents/bmm/workflows/1-analysis/create-product-brief/workflow_ext.md

@@ -0,0 +1,70 @@
+# MANDATORY RULES: CREATE-PRODUCT-BRIEF WORKFLOW
+
+---
+
+## RULE 1 — PHASE BRANCH CREATION AT WORKFLOW START
+
+**TRIGGER:** Immediately when the user initiates the `create-product-brief` workflow (e.g., `/create-product-brief`).
+
+**CRITICAL INSTRUCTION:** Before loading `workflow.md` or 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 Product Brief creation...`
+
+**DO NOT proceed to `workflow.md` until this rule is fully executed.**
+
+---
+
+## RULE 2 — PHASE COMMIT AT WORKFLOW END
+
+**TRIGGER:** Immediately after the `create-product-brief` workflow completes all its steps and the Product Brief document has been generated/saved.
+
+**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] add product brief for <project name>`
+
+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:
+> `✅ Product Brief changes committed to Phase 1 (discovery) branch.`
+
+**This is the LAST action of the workflow. Do not execute any further steps after this commit.**

package/siesa-agents/bmm/workflows/2-plan-workflows/create-ux-design/workflow_ext.md

@@ -0,0 +1,105 @@
+# MANDATORY RULES: CREATE-UX-DESIGN WORKFLOW
+
+---
+
+## 1. MANDATORY RULE — PHASE BRANCH CREATION AT WORKFLOW START
+
+**TRIGGER:** Immediately when the user initiates this workflow (e.g., `/create-ux-design`).
+
+**CRITICAL INSTRUCTION:** Before executing any workflow step, you MUST invoke the `generate-commits-by-phase` skill to create the Phase 2 planning branch.
+
+### EXECUTION STEPS (PERFORM THESE ACTIONS NOW, BEFORE ANYTHING ELSE)
+
+**STEP 1: INVOKE THE SKILL — CREATE PHASE 2 BRANCH**
+
+Run the skill `generate-commits-by-phase` with **Operation A: Create Phase Branch** for **Phase 2 (planning)**:
+
+```bash
+node _siesa-agents/scripts/phases/phase2.js
+```
+
+- If the `planning` 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 2 (planning) branch ready. Proceeding with UX Design creation...`
+
+**DO NOT proceed to the workflow steps until this rule is fully executed.**
+
+---
+
+## 2. INITIALIZATION — CHECK FOR EXISTING UX DESIGN DOCUMENT
+
+Before executing any workflow step, search for an existing UX design document:
+
+1. Look for a file matching `*ux-design-specification*.md` inside the `{planning_artifacts}/` folder.
+   - Glob pattern to check: `{planning_artifacts}/*ux-design-specification*.md`
+
+---
+
+## 3. DECISION BRANCH
+
+### If `ux-design-specification.md` EXISTS
+
+Use the **AskUserQuestion** tool to present the following options (respect `communication_language` from config):
+
+> Se encontró un documento de especificación UX/UI existente en `{planning_artifacts}/ux-design-specification.md`.
+>
+> ¿Qué deseas hacer?
+>
+> **[1] Editar** — Abrir el documento para revisarlo y modificarlo de forma colaborativa.
+> **[2] Resumen** — Generar un resumen ejecutivo del documento actual.
+
+Wait for the user's selection and act accordingly:
+
+- **Option 1 — Edit:** Read the full contents of `{planning_artifacts}/ux-design-specification.md`, present it to the user section by section, and facilitate collaborative editing. Apply changes directly to the file using the Edit tool.
+- **Option 2 — Summary:** Read the full contents of `{planning_artifacts}/ux-design-specification.md` and produce a concise executive summary covering: design vision, target users, design system decisions, visual foundations, component strategy, and any open design questions.
+
+---
+
+### If `ux-design-specification.md` does NOT EXIST
+
+LOAD the FULL `@_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md`, READ its entire contents and follow its directions exactly!
+
+---
+
+## 4. MANDATORY RULE — PHASE COMMIT AT WORKFLOW END
+
+**TRIGGER:** Immediately after all workflow steps complete and the UX Design document has been generated/saved.
+
+**CRITICAL INSTRUCTION:** As the final action of this workflow, you MUST invoke the `generate-commits-by-phase` skill to commit all changes for Phase 2.
+
+### 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 2 - Planning] <brief description of what was produced>`
+
+**Example:** `[Phase 2 - Planning] add UX design document for <project name>`
+
+Write the message in the same language used throughout the conversation.
+
+**STEP 3: INVOKE THE SKILL — COMMIT PHASE 2 CHANGES**
+
+Run the skill `generate-commits-by-phase` with **Operation B: Commit All Changes** for **Phase 2 (planning)**:
+
+```bash
+node _siesa-agents/scripts/phases/phase2.js --commit "<generated commit message>"
+```
+
+**STEP 4: CONFIRM COMPLETION**
+
+Output to the user:
+> `✅ UX Design changes committed to Phase 2 (planning) branch.`
+
+**This is the LAST action of the workflow. Do not execute any further steps after this commit.**

package/siesa-agents/bmm/workflows/2-plan-workflows/prd/workflow_ext.md

@@ -48,3 +48,72 @@ El PRD que produce este workflow es un **documento maestro general**. Contiene l
 
 Al finalizar el workflow, informar al ingeniero:
 > *"El PRD maestro ha sido generado. Para continuar, ejecuta `/shard-doc` sobre este archivo para dividirlo en shards por feature (`prd/feature-{name}.md`). Luego, cada feature shard puede alimentarse con mayor detalle de forma independiente."*
+
+---
+
+## 4. REGLA OBLIGATORIA — CREACIÓN DE RAMA DE FASE AL INICIO DEL WORKFLOW
+
+**TRIGGER:** Inmediatamente cuando el usuario inicia este workflow (e.g., `/create-prd`).
+
+**INSTRUCCIÓN CRÍTICA:** Antes de ejecutar cualquier paso del workflow, se DEBE invocar el skill `generate-commits-by-phase` para crear la rama de Phase 2 (planning).
+
+### PASOS DE EJECUCIÓN (REALIZAR ANTES DE CUALQUIER OTRA ACCIÓN)
+
+**PASO 1: INVOCAR EL SKILL — CREAR RAMA FASE 2**
+
+Ejecutar el skill `generate-commits-by-phase` con la **Operación A: Create Phase Branch** para **Phase 2 (planning)**:
+
+```bash
+node _siesa-agents/scripts/phases/phase2.js
+```
+
+- Si la rama `planning` ya existe, el script lo reportará — continuar normalmente.
+- Si se crea exitosamente, confirmarlo al usuario y proceder.
+
+**PASO 2: CONFIRMAR Y CONTINUAR**
+
+Informar al usuario:
+> `✅ Rama Phase 2 (planning) lista. Continuando con la creación del PRD...`
+
+**NO continuar con los pasos del workflow hasta que esta regla esté completamente ejecutada.**
+
+---
+
+## 5. REGLA OBLIGATORIA — COMMIT DE FASE AL FINALIZAR EL WORKFLOW
+
+**TRIGGER:** Inmediatamente después de que todos los pasos del workflow concluyan y el documento PRD haya sido generado/guardado.
+
+**INSTRUCCIÓN CRÍTICA:** Como acción final de este workflow, se DEBE invocar el skill `generate-commits-by-phase` para hacer commit de todos los cambios en Phase 2.
+
+### PASOS DE EJECUCIÓN (REALIZAR AL FINALIZAR)
+
+**PASO 1: INSPECCIONAR CAMBIOS**
+
+Antes de hacer commit, inspeccionar el estado del repositorio:
+
+1. Ejecutar `git status --short` para identificar los archivos creados o modificados.
+2. Ejecutar `git diff --stat` para entender el alcance de los cambios.
+
+**PASO 2: GENERAR MENSAJE DE COMMIT**
+
+Construir un mensaje de commit conciso con el formato:
+`[Phase 2 - Planning] <breve descripción de lo producido>`
+
+**Ejemplo:** `[Phase 2 - Planning] add PRD master document for <project name>`
+
+Escribir el mensaje en el mismo idioma usado durante la conversación.
+
+**PASO 3: INVOCAR EL SKILL — COMMIT DE CAMBIOS FASE 2**
+
+Ejecutar el skill `generate-commits-by-phase` con la **Operación B: Commit All Changes** para **Phase 2 (planning)**:
+
+```bash
+node _siesa-agents/scripts/phases/phase2.js --commit "<mensaje generado>"
+```
+
+**PASO 4: CONFIRMAR FINALIZACIÓN**
+
+Informar al usuario:
+> `✅ Cambios del PRD commiteados en la rama Phase 2 (planning).`
+
+**Esta es la ÚLTIMA acción del workflow. No ejecutar ningún paso adicional después de este commit.**

package/siesa-agents/bmm/workflows/3-solutioning/check-implementation-readiness/workflow_ext.md

@@ -0,0 +1,70 @@
+# MANDATORY RULES: CHECK-IMPLEMENTATION-READINESS WORKFLOW
+
+---
+
+## 1. MANDATORY RULE — PHASE BRANCH CREATION AT WORKFLOW START
+
+**TRIGGER:** Immediately when the user initiates this workflow (e.g., `/check-implementation-readiness`).
+
+**CRITICAL INSTRUCTION:** Before executing any workflow step, you MUST invoke the `generate-commits-by-phase` skill to create the Phase 3 solutioning branch.
+
+### EXECUTION STEPS (PERFORM THESE ACTIONS NOW, BEFORE ANYTHING ELSE)
+
+**STEP 1: INVOKE THE SKILL — CREATE PHASE 3 BRANCH**
+
+Run the skill `generate-commits-by-phase` with **Operation A: Create Phase Branch** for **Phase 3 (solutioning)**:
+
+```bash
+node _siesa-agents/scripts/phases/phase3.js
+```
+
+- If the `solutioning` 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 3 (solutioning) branch ready. Proceeding with Implementation Readiness check...`
+
+**DO NOT proceed to the workflow steps until this rule is fully executed.**
+
+---
+
+## 2. MANDATORY RULE — PHASE COMMIT AT WORKFLOW END
+
+**TRIGGER:** Immediately after all workflow steps complete and the readiness assessment has been generated/saved.
+
+**CRITICAL INSTRUCTION:** As the final action of this workflow, you MUST invoke the `generate-commits-by-phase` skill to commit all changes for Phase 3.
+
+### 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 3 - Solutioning] <brief description of what was produced>`
+
+**Example:** `[Phase 3 - Solutioning] add implementation readiness assessment for <project name>`
+
+Write the message in the same language used throughout the conversation.
+
+**STEP 3: INVOKE THE SKILL — COMMIT PHASE 3 CHANGES**
+
+Run the skill `generate-commits-by-phase` with **Operation B: Commit All Changes** for **Phase 3 (solutioning)**:
+
+```bash
+node _siesa-agents/scripts/phases/phase3.js --commit "<generated commit message>"
+```
+
+**STEP 4: CONFIRM COMPLETION**
+
+Output to the user:
+> `✅ Implementation Readiness changes committed to Phase 3 (solutioning) branch.`
+
+**This is the LAST action of the workflow. Do not execute any further steps after this commit.**