siesa-agents 2.1.68 → 2.1.71

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/commands/jira_sync/sync-epics-stories.md

@@ -0,0 +1,5 @@
+---
+description: 'Sync Epics and Stories'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_siesa-agents/sa/sync-epics-stories/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/sa-jira-sync.md

@@ -0,0 +1,11 @@
+---
+name: sa-jira-sync
+description: Query Jira and return a minimal hierarchy of Epics → Stories → Subtasks for a given project and epic status. Returns only id, key, name, and status for each level. Use when the user needs to inspect or export the epic/story/subtask structure from siesa-team or siesa-test-sandbox.
+argument-hint: [PROJECT-KEY] [--status "Epic Status"]
+user-invocable: true
+allowed-tools: Bash, Read, Write
+---
+
+Handle the Jira sync request: **$ARGUMENTS**
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_siesa-agents/sa/sa-jira-sync-api/jira-sync-api.md, READ its entire contents and follow its directions exactly!

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-code-review.toml

@@ -3,10 +3,11 @@ 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 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/code-review/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/4-implementation/code-review/workflow.yaml 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
+1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/4-implementation/code-review/workflow_ext.md`. You MUST assimilate these pre-requisites before doing anything else.
+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/code-review/workflow.yaml
+4. Pass the yaml path _bmad/bmm/workflows/4-implementation/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+5. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+6. Save outputs after EACH section when generating any documents from templates
 </steps>
 """

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/gemini/commands/sa-jira-sync.toml

@@ -0,0 +1,9 @@
+description = "SA: Query Jira and return a minimal hierarchy of Epics → Stories → Subtasks for a given project and epic status. Returns only id, key, name, and status for each level."
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_siesa-agents/sa/sa-jira-sync-api/jira-sync-api.md, READ its entire contents and follow its directions exactly!
+
+Parse the user arguments: **$ARGUMENTS**
+- First positional arg → PROJECT_KEY (e.g. PPS)
+- --status "..." → filter epics by this status name (default: En curso)
+- If no PROJECT_KEY is provided, prompt the user for one.
+"""

package/gemini/commands/sa-workflow-sync-epics-stories.toml

@@ -0,0 +1,4 @@
+description = "SA Workflow: sync-epics-stories — Sync Epics and Stories with Jira"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_siesa-agents/sa/sync-epics-stories/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "siesa-agents",
-  "version": "2.1.68",
+  "version": "2.1.71",
   "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,70 @@
+# 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. 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

@@ -16,11 +16,30 @@ Cuando el workflow llegue a la fase de descubrimiento, presentar al usuario este
 > **2. Proporcionarlos manualmente** — Puedes pegarlos aquí, compartir un archivo `.txt` o `.md`, o describirlos en texto libre."
 
 <!-- INSTRUCCIONES DE WORKFLOW — NO mostrar al usuario -->
-- Si el usuario elige **opción 1 (Jira):** Invocar el skill `get-features` (UBICADO EN .claude\commands\get-features\SKILL.md) usando el Skill tool con `skill: "get-features"`. El skill se encargará de autenticarse con Jira, seleccionar instancia y proyecto, y generar el árbol de features en `_bmad-output/planning-artifacts/jira-trees/`. Una vez generado, leer ese archivo y extraer la lista de features del resultado para usarla como estructura del PRD.
-- Si el usuario elige **opción 2 (Manual):** Aceptar la lista de features que el usuario proporcione en cualquier formato (texto libre, `.txt`, `.md` o copia-pegado) y procesarla directamente.
+- Si el usuario elige **opción 1 (Jira):** Invocar el skill `get-features` (UBICADO EN .claude\commands\get-features\SKILL.md) usando el Skill tool con `skill: "get-features"`. El skill se encargará de autenticarse con Jira, seleccionar instancia y proyecto, y generar el árbol de features en `_bmad-output/planning-artifacts/jira-trees/`. Una vez generado, leer ese archivo y extraer la lista de features del resultado para usarla como estructura del PRD. Por cada feature extraído de Jira, **incluir obligatoriamente** el marcador `FEATURE_CODE_JIRA={ISSUE_KEY}` en su sección del PRD (donde `{ISSUE_KEY}` es el ID del issue en Jira, ej: `PROY-123`). Este marcador es crítico para la sincronización posterior con Jira:
+  - Los shards del PRD (`prd/f{N}-*.md`) y los shards de épicas (`epics/f{N}-*.md`) deben contener este marcador.
+  - Al sincronizar, el workflow resuelve el ID con este orden de prioridad: (1) busca `FEATURE_CODE_JIRA=` en el shard de la épica; (2) si no lo encuentra, lo busca en el shard del PRD correspondiente.
+  - ⚠️ Si ninguno de los dos shards contiene el marcador, la sincronización fallará para ese feature. Es responsabilidad del ingeniero asegurar que el marcador exista en al menos uno de los dos shards antes de ejecutar la sincronización.
+- Si el usuario elige **opción 2 (Manual):** Aceptar la lista de features que el usuario proporcione en cualquier formato (texto libre, `.txt`, `.md` o copia-pegado) y procesarla directamente. Por cada feature creado manualmente, incluir el marcador `FEATURE_CODE_JIRA=PENDING:{feature-slug}` (donde `{feature-slug}` es el nombre del feature en kebab-case, ej: `FEATURE_CODE_JIRA=PENDING:gestion-de-clientes`). Este valor temporal indica que el feature aún no existe en Jira y será creado automáticamente cuando el ingeniero ejecute `jira_sync`.
 
 Inyectar los features confirmados como estructura del PRD: cada feature debe quedar como una sección `### feature — {Name}` dentro del documento.
 
+<!-- INSTRUCCIONES DE WORKFLOW — NO mostrar al usuario -->
+**Si el PRD ya fue shardeado (existe la carpeta `prd/` con archivos `f{N}-*.md`):**
+- **NO modificar** el PRD maestro original.
+- Por cada nuevo feature que el ingeniero quiera agregar, ejecutar el siguiente flujo de resolución **antes de crear el shard**:
+
+  1. Invocar el skill `get-features` (usando el Skill tool con `skill: "get-features"`) para traer el árbol actualizado de features desde Jira.
+  2. Leer el árbol generado en `_bmad-output/planning-artifacts/jira-trees/` y filtrar los features que **no tienen shard local** (cuyo `ISSUE_KEY` no aparece en ningún `prd/f{N}-*.md` existente).
+  3. Mostrar al ingeniero la lista filtrada y preguntar:
+     > *"Se encontraron los siguientes features en Jira sin shard local. ¿Alguno corresponde al feature que acabas de describir?"*
+     - Listar cada feature con su KEY y nombre (ej: `PROY-89 — Gestión de Clientes`).
+     - Incluir siempre la opción: **"Ninguno — es un feature completamente nuevo, no existe en Jira"**.
+  4. **Si el ingeniero selecciona un feature de Jira** → crear el shard `f{N}-{feature-name}.md` con `FEATURE_CODE_JIRA={ISSUE_KEY}` del feature seleccionado.
+  5. **Si el ingeniero elige "Ninguno"** → crear el shard `f{N}-{feature-name}.md` con `FEATURE_CODE_JIRA=PENDING:{feature-slug}`.
+
+- Informar al ingeniero qué archivo shard fue creado y que puede enriquecerlo con detalle adicional de forma independiente.
+
 ## 2. Naturaleza del PRD Generado
 
 El PRD que produce este workflow es un **documento maestro general**. Contiene la definición base de cada feature a nivel de alcance, objetivos y requisitos generales — NO el detalle profundo de implementación de cada uno.
@@ -29,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.**