siesa-agents 2.1.70 → 2.1.72-qa.0

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/get-features/oauth-config.example.json

@@ -2,7 +2,7 @@
   "client_id": "TU_CLIENT_ID",
   "client_secret": "TU_CLIENT_SECRET",
   "redirect_uri": "http://localhost:3000/callback",
-  "scopes": "read:jira-work read:jira-user offline_access",
+  "scopes": "read:jira-work write:jira-work read:jira-user offline_access",
   "cloud_id": "TU_CLOUD_ID",
   "jira_base_url": "https://api.atlassian.com/ex/jira/TU_CLOUD_ID/rest/api/3",
   "default_instance": null,

package/claude/skills/delivery-sa-agent-guides/SKILL.md

@@ -0,0 +1,162 @@
+---
+name: delivery-sa-agent-guides
+description: Generate client-ready delivery guides from user-guide documents indexed in the mcp-siesa-docs MCP. Use this skill when a delivery team member needs to transform user-guide content into simple, end-user friendly material. Always trigger on /delivery-agent-guides. Also trigger when the user says "generar guía de entrega", "guía para el cliente", "documentación de entrega para [project]", "guía para usuario final", or describes wanting to turn indexed user-guide docs into something a non-technical client can understand.
+---
+
+# Delivery Agent Guides
+
+Transform user-guide documents (from the `mcp-siesa-docs` MCP) into a clear, client-ready delivery guide — plain language, no jargon, for non-technical end users.
+
+The MCP is the only source of content. The local filesystem is not scanned.
+
+---
+
+## Flow
+
+### Step 1: Discover projects with user-guides (automatic)
+
+As soon as the skill is invoked, without asking the user first:
+
+1. Call `list_collections()` to confirm `mcp-siesa-docs` is available.
+2. Call `search_docs("user guide proyectos disponibles")` to find projects whose indexed docs include a `user-guide` directory.
+3. Build the candidate list: **only include projects that have at least one document in their `user-guide` directory**. Projects with only feature specs, épicas, stories, or architecture docs are excluded (Option A).
+4. Present the list to the user:
+   ```
+   Proyectos con guías de usuario disponibles:
+   [1] {project-name-1}
+   [2] {project-name-2}
+   ...
+
+   ¿Para cuál proyecto quieres generar la guía de entrega?
+   ```
+5. The user replies with a number or project name.
+
+If zero projects qualify, tell the user plainly ("No encontré proyectos con user-guide indexado en el MCP") and stop.
+
+---
+
+### Step 2: Pull the user-guide content from the MCP
+
+1. `search_docs("user guide [proyecto seleccionado]")` to list the user-guide documents of the chosen project.
+2. For each result, call `get_document(path)` to fetch the full content.
+3. **Strict filter**: process only documents whose `path` is inside the project's `user-guide` directory. Ignore feature specs, épicas, stories, architecture, or any other technical doc, even if they show up in results.
+
+Keep the list of `path`s used — you will cite them in the final confirmation.
+
+---
+
+### Step 3: Write the delivery guide
+
+Write one unified `delivery-guide.md`. All content in Spanish. Audience: non-technical end user.
+
+**Content to keep and rewrite in plain language:**
+- Feature name and purpose
+- Step-by-step workflows
+- Key concepts and field definitions (simplified)
+- Troubleshooting and FAQs
+- Warnings (⚠️) — rephrase without technical detail; keep the practical implication
+
+**Content to transform:**
+- Mermaid diagrams → rewrite as one or two plain sentences describing the flow. Never emit Mermaid syntax.
+
+**Content to omit:**
+- `📸 [Screenshot: ...]` placeholders
+- `[Source: FX Story Y.Z]` traceability references
+- Screenshot index tables
+- Implementation component names (ContactManager, EmptyState, ErrorPanel, etc.) — describe the behavior instead
+- `*Generado: ...` footers
+
+**Output template:**
+
+```markdown
+---
+project: {project-name}
+generated_date: {YYYY-MM-DD}
+sources:
+  - {mcp-path-1}
+  - {mcp-path-2}
+audience: Usuario final no técnico
+---
+
+# Guía de {Nombre del Proyecto}
+
+## ¿Qué es {Nombre del Proyecto}?
+2-3 sentences. What the app does and who it is for. No technical terms.
+
+## ¿Para qué sirve?
+What problems it solves, from the user's perspective.
+
+---
+
+## {Feature 1}
+
+### ¿Qué es?
+One paragraph. Plain description.
+
+### ¿Para qué sirve?
+The practical benefit to the user.
+
+### ¿Cómo se usa?
+Numbered step-by-step. One clear action per step.
+Include warnings inline (⚠️ ...) directly before the step that can cause an issue.
+
+---
+
+## {Feature 2}
+(same structure)
+
+---
+
+## Solución de Problemas
+Plain Q&A: "¿Qué hago si...? → ..."
+
+## Preguntas Frecuentes
+Plain Q&A. No technical language.
+```
+
+**Writing guidelines:**
+- Target a reader who is comfortable with a smartphone but has no software background.
+- Active voice, direct instructions: "Haz clic en...", "Escribe...", "Selecciona..."
+- Short sentences. If a sentence needs a comma to explain a technical concept, rewrite it.
+- If a concept has no practical value to the end user, drop it.
+
+---
+
+### Step 4: Save and confirm
+
+Save to:
+```
+_bmad-output/documentation-artifacts/delivery-guides/{project-name}/delivery-guide.md
+```
+
+Create the directory if it doesn't exist.
+
+Then confirm:
+```
+Guía guardada en: _bmad-output/documentation-artifacts/delivery-guides/{project-name}/delivery-guide.md
+
+Features incluidas:
+  - {feature 1}
+  - {feature 2}
+
+Fuentes del MCP:
+  - {mcp-path-1}
+  - {mcp-path-2}
+```
+
+---
+
+## Transformation Reference
+
+| Technical element | Delivery guide treatment |
+|---|---|
+| `deep linking` / URL única por registro | "Cada registro tiene su propia dirección web que puedes guardar o compartir" |
+| `ContactManager`, `EmptyState`, `ErrorPanel` | Drop the name; describe what the user sees |
+| `NIT/RUC` | Keep — explain once: "número de identificación tributaria (NIT/RUC)" |
+| `Toast` notification | "mensaje de confirmación que aparece brevemente en pantalla" |
+| Reintentar button on error | "si aparece un error, haz clic en Reintentar" |
+| Panel de dos columnas | "La pantalla se divide en dos partes: a la izquierda la lista, a la derecha el detalle" |
+| Validación inline | "mensajes de error junto al campo que necesita corrección" |
+| Mermaid code block | One or two plain sentences describing the flow |
+| `[Source: FX Story Y.Z]` | Omit |
+| `📸 [Screenshot: ...]` | Omit |

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/github/workflows/publish-qa.yml

@@ -0,0 +1,59 @@
+name: Publish to npm (qa)
+on:
+  push:
+    branches:
+      - qa
+jobs:
+  publish-qa:
+    runs-on: ubuntu-latest
+    if: "!contains(github.event.head_commit.message, '[skip ci]')"
+    permissions:
+      contents: write
+      id-token: write
+    steps:
+      - name: Create GitHub App Token
+        uses: actions/create-github-app-token@v1
+        id: app-token
+        with:
+          app-id: ${{ vars.VERSION_BUMPER_APPID }}
+          private-key: ${{ secrets.VERSION_BUMPER_SECRET }}
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          ref: qa
+          fetch-depth: 0
+          token: ${{ steps.app-token.outputs.token }}
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          registry-url: 'https://registry.npmjs.org'
+      - name: Update npm for OIDC support
+        run: |
+          npm install -g npm@~11.10.0
+          npm install -g npm@latest
+      - name: Configure Git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+      - name: Install dependencies
+        run: npm ci --ignore-scripts
+      - name: Bump qa prerelease version
+        run: |
+          CURRENT_VERSION=$(node -p "require('./package.json').version")
+          if git rev-parse "v$CURRENT_VERSION" >/dev/null 2>&1; then
+            echo "Tag v$CURRENT_VERSION already exists — bumping prerelease"
+            npm version prerelease --preid=qa -m "chore(release): %s [skip ci]"
+          else
+            echo "Tag v$CURRENT_VERSION does not exist — publishing existing version"
+          fi
+      - name: Build
+        run: npm run build || echo "No build script, continuing..."
+      - name: Push version bump
+        run: git push --follow-tags || echo "Nothing to push, continuing..."
+      - name: Publish to npm with qa tag
+        run: |
+          npm config set //registry.npmjs.org/:_authToken "${NPM_TOKEN}"
+          npm publish --tag qa --access public
+        env:
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

package/mcp.json

@@ -1,5 +1,12 @@
 {
   "mcpServers": {
+    "mcp-siesa-docs": {
+      "type": "http",
+      "url": "https://platform-architecture-mcp-siesa-103767536676.us-east1.run.app/mcp",
+      "headers": {
+        "Authorization": "Bearer none"
+      }
+    },
     "atlassian": {
       "type": "sse",
       "url": "https://mcp.atlassian.com/v1/sse"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "siesa-agents",
-  "version": "2.1.70",
+  "version": "2.1.72-qa.0",
   "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.**