siesa-agents 2.1.89 → 2.1.91

package/claude/skills/sa-init-devops/SKILL.md

@@ -1,33 +1,33 @@
 ---
 name: sa-init-devops
-description: 'Bootstrap the DevOps workspace and skills in Siesa-Agents in one shot: clones architecture-sa-devops into `_siesa-agents/devops/`, detects conflicts between local and upstream copies of the `sa-*` DevOps skills and the deploy workflows (asks the user via AskUserQuestion which side to keep when there are diffs), then MOVES the chosen versions into `.claude/skills/` (and `claude/skills/`) so `/sa-aplicar`, `/sa-nuevo-servicio`, `/sa-auditar-servicio`, etc. become immediately invocable, MOVES the workflows into `.github/workflows/`, deletes the now-empty `.claude/` and `.github/` directories from the clone, then mirrors the cleaned tree to `siesa-agents/devops/`. Use whenever the user wants to set up the DevOps workspace for the first time, refresh it after upstream changes, mentions needing terraform/k8s/environments files, or when any `sa-*` deploy skill is missing from Claude Code.'
+description: 'Bootstrap the DevOps workspace and commands in Siesa-Agents in one shot: clones business-shared-deploy into `_siesa-agents/devops/`, detects conflicts between local and upstream copies of the `flow-*`/`agent-*` DevOps slash commands and the deploy workflows (asks the user via AskUserQuestion which side to keep when there are diffs), then MOVES the chosen versions into `.claude/commands/` (and `claude/commands/`) so `/flow-aplicar`, `/flow-nuevo-servicio`, `/flow-auditar-servicio`, etc. become immediately invocable, MOVES the workflows into `.github/workflows/`, deletes the now-empty `.claude/` and `.github/` directories from the clone, then mirrors the cleaned tree to `siesa-agents/devops/`. Use whenever the user wants to set up the DevOps workspace for the first time, refresh it after upstream changes, mentions needing terraform/k8s/environments files, or when any `flow-*` deploy command is missing from Claude Code.'
 ---
 
-# Init DevOps — clone the workspace + materialize the DevOps skills
+# Init DevOps — clone the workspace + materialize the DevOps commands
 
-**Goal:** In a single invocation, populate Siesa-Agents with everything an engineer needs to run the Finance DevOps skills. After a successful run the layout is:
+**Goal:** In a single invocation, populate Siesa-Agents with everything an engineer needs to run the Finance DevOps commands. After a successful run the layout is:
 
 | Location | Contents |
 |---|---|
-| `_siesa-agents/devops/` | Git working tree cloned from `architecture-sa-devops`. **Only** the deployment workspace: `terraform/`, `k8s/`, `environments/`, `scripts/`, `cicd-templates/`, `docs/`, `CLAUDE.md`, `README.md`, `.gitignore`. The `.claude/` and `.github/` directories from upstream are wiped from the clone after their contents are moved to Siesa-Agents level. |
+| `_siesa-agents/devops/` | Git working tree cloned from `business-shared-deploy`. **Only** the deployment workspace: `terraform/`, `k8s/`, `environments/`, `scripts/`, `cicd-templates/`, `docs/`, `seed/`, `CLAUDE.md`, `README.md`, `.gitignore`. The `.claude/` and `.github/` directories from upstream are wiped from the clone after their contents are moved to Siesa-Agents level. |
 | `siesa-agents/devops/` | Flat snapshot mirror of the cleaned clone (no `.git/`, no `.claude/`, no `.github/`). The npm-publishable copy. |
-| `.claude/skills/sa-*/SKILL.md` | The 8 DevOps skills moved out of the clone: `sa-aplicar`, `sa-auditar-servicio`, `sa-nueva-transversal`, `sa-nuevo-ambiente`, `sa-nuevo-servicio`, `sa-onboard-db`, `sa-registrar-permisos`, `sa-agent-sre-sentinel`. |
-| `claude/skills/sa-*/SKILL.md` | Same skills, in the npm mirror. |
-| `.github/workflows/*.yml` | The 4 deploy workflow files moved out of the clone (`infra-pipeline-dev/qa/shared.yml`, `reconcile-geographic-projections.yml`). **These do not fire from Siesa-Agents** — gitignored, for visibility only. They fire from `architecture-sa-devops` where they originally live. |
+| `.claude/commands/*.md` | The DevOps slash commands moved out of the clone: `flow-aplicar`, `flow-auditar-servicio`, `flow-nueva-transversal`, `flow-nuevo-ambiente`, `flow-nuevo-servicio`, `flow-onboard-db`, `flow-registrar-permisos`, `agent-sre-sentinel`. |
+| `claude/commands/*.md` | Same commands, in the npm mirror. |
+| `.github/workflows/*.yml` | The deploy workflow files moved out of the clone (`infra-pipeline-dev.yml`, `infra-pipeline-qa.yml`, `infra-pipeline-shared.yml`). **These do not fire from Siesa-Agents** — gitignored, for visibility only. They fire from `business-shared-deploy` where they originally live. |
 
-**Why this matters:** Without this skill, Siesa-Agents is missing every Finance DevOps capability. The DevOps skills cannot live statically in this repo because they evolve with the deploy workspace (`environments/`, `terraform/`, `k8s/`) — keeping them in sync would require a PR every time Finance bumps the workspace. Instead the upstream `architecture-sa-devops` repo is the single source of truth, and this skill pulls everything down on demand.
+**Why this matters:** Without this skill, Siesa-Agents is missing every Finance DevOps capability. The DevOps commands cannot live statically in this repo because they evolve with the deploy workspace (`environments/`, `terraform/`, `k8s/`) — keeping them in sync would require a PR every time Finance bumps the workspace. Instead the upstream `business-shared-deploy` repo is the single source of truth, and this skill pulls everything down on demand.
 
 ## When to use this skill
 
 Trigger immediately when the user:
 
-- Says "init devops", "setup devops", "clone architecture-sa-devops", "trae el workspace de despliegue", or similar
-- Tries to invoke any deploy skill (`/sa-aplicar`, `/sa-nuevo-servicio`, etc.) and Claude Code reports the skill is not available
-- Tries to invoke a deploy skill and it complains about missing paths (`environments/shared.yaml`, `terraform/environments/`, `k8s/overlays/`, etc.)
-- Mentions wanting to refresh / pull latest from `architecture-sa-devops`
-- Has just cloned Siesa-Agents and is preparing to use the deploy skills
+- Says "init devops", "setup devops", "clone business-shared-deploy", "trae el workspace de despliegue", or similar
+- Tries to invoke any deploy command (`/flow-aplicar`, `/flow-nuevo-servicio`, etc.) and Claude Code reports the command is not available
+- Tries to invoke a deploy command and it complains about missing paths (`environments/shared.yaml`, `terraform/environments/`, `k8s/overlays/`, etc.)
+- Mentions wanting to refresh / pull latest from `business-shared-deploy`
+- Has just cloned Siesa-Agents and is preparing to use the deploy commands
 
-Do **not** trigger for: editing the deploy skills themselves (those edits must go to `architecture-sa-devops`), modifying terraform/k8s contents (those go to `architecture-sa-devops` too), or anything unrelated to bootstrapping.
+Do **not** trigger for: editing the deploy commands themselves (those edits must go to `business-shared-deploy`), modifying terraform/k8s contents (those go to `business-shared-deploy` too), or anything unrelated to bootstrapping.
 
 ## Prerequisites
 
@@ -35,7 +35,7 @@ Do **not** trigger for: editing the deploy skills themselves (those edits must g
 - The user has network access to GitHub.com.
 - The helper script lives at `_siesa-agents/sa/sa-init-devops/scripts/sa-init-devops.js` (source of truth) and is mirrored to `siesa-agents/sa/sa-init-devops/scripts/sa-init-devops.js` (npm copy). Prefer the source-of-truth path when both exist.
 
-If the script is missing or `git` is unavailable, stop and tell the user — do not improvise the work inline. The script handles all the edge cases (existing clone with wrong remote, partial state, conflicting local edits, skill/workflow copy overwrites) that an inline shell sequence would miss.
+If the script is missing or `git` is unavailable, stop and tell the user — do not improvise the work inline. The script handles all the edge cases (existing clone with wrong remote, partial state, conflicting local edits, command/workflow copy overwrites) that an inline shell sequence would miss.
 
 ## Workflow
 
@@ -52,19 +52,19 @@ node _siesa-agents/sa/sa-init-devops/scripts/sa-init-devops.js
 Default mode does:
 
 1. **Clone or update.** `git clone` (if `_siesa-agents/devops/` does not exist) **or** `git checkout HEAD -- .claude .github && git fetch && git checkout main && git pull --ff-only` (if it does). The `git checkout HEAD -- .claude .github` step restores files that the previous run wiped so the pull doesn't fail on "uncommitted deletions".
-2. **Dry-run conflict detection.** For each upstream `.claude/skills/sa-*/SKILL.md` and `.github/workflows/*.yml`, compare to the local copy in Siesa-Agents (`.claude/skills/`, `claude/skills/`, and `.github/workflows/`). The bootstrap skill `sa-init-devops` is always excluded from this comparison.
-3. **If any local file differs from upstream → abort.** Exit 4 with `status: "conflicts"` and lists `skill_conflicts` / `workflow_conflicts`. Nothing is mutated. The model proceeds to Step 2.
+2. **Dry-run conflict detection.** For each upstream `.claude/commands/*.md` and `.github/workflows/*.yml`, compare to the local copy in Siesa-Agents (`.claude/commands/`, `claude/commands/`, and `.github/workflows/`).
+3. **If any local file differs from upstream → abort.** Exit 4 with `status: "conflicts"` and lists `command_conflicts` / `workflow_conflicts`. Nothing is mutated. The model proceeds to Step 2.
 4. **If no conflicts → apply.** Copy the upstream files into Siesa-Agents (creating new files, leaving identical ones alone), then delete `.claude/` and `.github/` from the clone working tree, then mirror the cleaned tree to `siesa-agents/devops/`. Exit 0.
 
 ### Step 2 — Handle conflicts (only when `status: "conflicts"`)
 
-When the JSON output has `status: "conflicts"`, **ask the user which side to keep** before any local file is changed. Use `AskUserQuestion` with the list of conflicting items from `skill_conflicts` and `workflow_conflicts`.
+When the JSON output has `status: "conflicts"`, **ask the user which side to keep** before any local file is changed. Use `AskUserQuestion` with the list of conflicting items from `command_conflicts` and `workflow_conflicts`.
 
 For most cases, one question with three options is enough:
 
 ```
-question: "Estos N archivos locales difieren del upstream architecture-sa-devops:
-           <list with skill_conflicts + workflow_conflicts>
+question: "Estos N archivos locales difieren del upstream business-shared-deploy:
+           <list with command_conflicts + workflow_conflicts>
            ¿Cómo resuelvo?"
 options:
   - "Take all from upstream" (overwrite all conflicts with upstream version)
@@ -87,7 +87,7 @@ node _siesa-agents/sa/sa-init-devops/scripts/sa-init-devops.js --keep-local
 If the user picks **"Resolve per file"**, ask one more question per conflicting item (with `AskUserQuestion`, max 4 items per call — chunk if needed) collecting which ones to keep local, then re-run with `--keep-local=<csv>`:
 
 ```bash
-node _siesa-agents/sa/sa-init-devops/scripts/sa-init-devops.js --keep-local=sa-aplicar,infra-pipeline-qa.yml
+node _siesa-agents/sa/sa-init-devops/scripts/sa-init-devops.js --keep-local=flow-aplicar.md,infra-pipeline-qa.yml
 ```
 
 The named items keep their local version; everything else takes upstream.
@@ -96,21 +96,21 @@ The named items keep their local version; everything else takes upstream.
 
 After the (possibly second) successful invocation, read the `status` field:
 
-- **`status: "cloned"`** — Fresh clone. Tell the user: "Cloned `architecture-sa-devops`. Created `<N>` skills + `<M>` workflows in Siesa-Agents. The deploy skills (`/sa-aplicar`, `/sa-nuevo-servicio`, etc.) are now available in Claude Code."
-- **`status: "updated"`** — Existing clone pulled new commits. Report `before_sha..after_sha` and the per-category counts (`skills_created`, `skills_overwritten`, `skills_kept_local`, `skills_unchanged`, same for workflows).
+- **`status: "cloned"`** — Fresh clone. Tell the user: "Cloned `business-shared-deploy`. Created `<N>` commands + `<M>` workflows in Siesa-Agents. The deploy commands (`/flow-aplicar`, `/flow-nuevo-servicio`, etc.) are now available in Claude Code."
+- **`status: "updated"`** — Existing clone pulled new commits. Report `before_sha..after_sha` and the per-category counts (`commands_created`, `commands_overwritten`, `commands_kept_local`, `commands_unchanged`, same for workflows).
 - **`status: "already-cloned"`** — Local clone was already at the latest HEAD; no upstream change. The counts reflect what happened in the apply step (likely all `unchanged` if everything matched).
 - **`status: "conflicts"`** — Should only appear on the FIRST run when conflicts exist; never on a re-run with a policy flag. If you see this twice, surface it as a bug.
 - **`status: "invalid-source"`** — `_siesa-agents/devops/` exists but is not a git working tree. Surface the message verbatim and stop. Do not try to delete the directory automatically.
 - **`status: "wrong-remote"`** — Same directory is a clone of a different repo. Surface the message and stop.
 - **`status: "clone-failed"` / `"fetch-failed"` / `"pull-failed"` / `"checkout-failed"`** — Git operation failed. Surface the underlying git error verbatim. Common causes: no network, branch diverged, local edits blocking ff-pull.
 
-### Step 3 — Remind the user about cwd for the deploy skills
+### Step 3 — Remind the user about cwd for the deploy commands
 
 After a successful run (any of `cloned`, `updated`, `already-cloned`), remind the user once:
 
-> Las skills de despliegue (`/sa-aplicar`, `/sa-nuevo-servicio`, etc.) asumen que el cwd está dentro de `_siesa-agents/devops/`. Cambia de directorio (`cd _siesa-agents/devops/`) antes de invocarlas, para que las rutas relativas (`environments/`, `terraform/`, `k8s/`) se resuelvan correctamente.
+> Los comandos de despliegue (`/flow-aplicar`, `/flow-nuevo-servicio`, etc.) asumen que el cwd está dentro de `_siesa-agents/devops/`. Cambia de directorio (`cd _siesa-agents/devops/`) antes de invocarlos, para que las rutas relativas (`environments/`, `terraform/`, `k8s/`) se resuelvan correctamente.
 
-If the user invokes one of those skills from elsewhere, the relative paths in their workflows won't resolve and they'll see confusing "file not found" errors.
+If the user invokes one of those commands from elsewhere, the relative paths in their instructions won't resolve and they'll see confusing "file not found" errors.
 
 ## Optional flags
 
@@ -118,28 +118,27 @@ If the user invokes one of those skills from elsewhere, the relative paths in th
 - `--mirror-only` — Skip the git + move steps; rebuild `siesa-agents/devops/` from the existing clone. Useful when only the mirror is out of sync.
 - `--take-upstream` — Resolve all conflicts in favor of upstream (overwrite every conflicting local file). Use after the user confirms they want the upstream versions.
 - `--keep-local` — Keep every local file as-is; only create files that are entirely new in upstream. Use when the user wants to preserve all local edits.
-- `--keep-local=<csv>` — Keep these specific items local (comma-separated names matching `skill_conflicts` / `workflow_conflicts` entries); overwrite all other conflicts with upstream. Example: `--keep-local=sa-aplicar,infra-pipeline-qa.yml`.
+- `--keep-local=<csv>` — Keep these specific items local (comma-separated names matching `command_conflicts` / `workflow_conflicts` entries); overwrite all other conflicts with upstream. Example: `--keep-local=flow-aplicar.md,infra-pipeline-qa.yml`.
 
 The three policy flags are mutually exclusive; passing more than one returns exit code 1.
 
 ## Edge cases
 
-- **Skill conflicts.** The default run aborts on any conflict (local file differs from upstream) and lists them in `skill_conflicts` / `workflow_conflicts`. The model then asks the user with `AskUserQuestion` and re-runs with `--take-upstream`, `--keep-local`, or `--keep-local=<csv>`. Engineers who want their custom edits to survive automatic refresh should fork `architecture-sa-devops` and update `REMOTE_URL` at the top of the helper script — that keeps their fork as the upstream source of truth.
-- **The bootstrap skill is never overwritten.** `sa-init-devops/` is explicitly excluded from the copy loop in the helper, so re-running the skill cannot trash itself.
-- **The clone has 12 "deleted" files in `git status` after every run.** Expected. The script moves `.claude/skills/sa-*/SKILL.md` and `.github/workflows/*.yml` out of the clone and deletes those directories, but the files are still tracked in upstream HEAD. The next run restores them via `git checkout HEAD -- .claude .github` before pulling, then moves and deletes them again. Engineers should never `git add` or `git commit` those deletions inside `_siesa-agents/devops/` — they are intentional working-tree-only state.
-- **Workflows in Siesa-Agents `.github/workflows/`** — moved for inspection but gitignored (see `.gitignore`), so engineers can read them locally but they never fire on Siesa-Agents PRs. The same workflows fire on PRs / pushes to `architecture-sa-devops`, which is where they live.
+- **Command conflicts.** The default run aborts on any conflict (local file differs from upstream) and lists them in `command_conflicts` / `workflow_conflicts`. The model then asks the user with `AskUserQuestion` and re-runs with `--take-upstream`, `--keep-local`, or `--keep-local=<csv>`. Engineers who want their custom edits to survive automatic refresh should fork `business-shared-deploy` and update `REMOTE_URL` at the top of the helper script — that keeps their fork as the upstream source of truth.
+- **The clone shows the moved files as "deleted" in `git status` after every run.** Expected. The script moves `.claude/commands/*.md` and `.github/workflows/*.yml` out of the clone and deletes those directories, but the files are still tracked in upstream HEAD. The next run restores them via `git checkout HEAD -- .claude .github` before pulling, then moves and deletes them again. Engineers should never `git add` or `git commit` those deletions inside `_siesa-agents/devops/` — they are intentional working-tree-only state.
+- **Workflows in Siesa-Agents `.github/workflows/`** — moved for inspection but gitignored (see `.gitignore`), so engineers can read them locally but they never fire on Siesa-Agents PRs. The same workflows fire on PRs / pushes to `business-shared-deploy`, which is where they live.
 - **`_siesa-agents/devops/` exists from a previous run with local edits to non-managed paths.** The restore step touches only `.claude` and `.github`; edits to `environments/`, `terraform/`, `k8s/`, etc. survive the restore step but `git pull --ff-only` will fail if they conflict with upstream. The script surfaces the git error verbatim. The user should commit, stash, or discard their local changes and re-run.
-- **The directory exists but isn't a clone of `architecture-sa-devops`.** The script reports `invalid-source` or `wrong-remote` and refuses to delete. The user must move it aside manually.
-- **The mirror or local skills/workflows have manual edits.** The script overwrites them on every run — that is by design. If you need to preserve edits, make them in the upstream `architecture-sa-devops` repo, not locally.
+- **The directory exists but isn't a clone of `business-shared-deploy`.** The script reports `invalid-source` or `wrong-remote` and refuses to delete. The user must move it aside manually.
+- **The mirror or local commands/workflows have manual edits.** The script overwrites them on every run — that is by design. If you need to preserve edits, make them in the upstream `business-shared-deploy` repo, not locally.
 - **No `git` on PATH.** The first `tryGit` call fails; the script surfaces a `clone-failed` or `fetch-failed` status. Tell the user to install git or add it to PATH.
 
 ## Upstream URL
 
-The script currently points at `https://github.com/ssancheze912/architecture-sa-devops.git` as a temporary location while SiesaTeams org-create permissions are being arranged. When the repo is transferred to `https://github.com/SiesaTeams/architecture-sa-devops.git`, update `REMOTE_URL` at the top of the helper script and ship the change.
+The script points at `https://github.com/SiesaTeams/business-shared-deploy.git`. If Finance forks or relocates the deploy repo, update `REMOTE_URL` at the top of the helper script (both the source-of-truth and mirror copies) and ship the change.
 
 ## Reminders
 
-- Step 1 is always safe to re-run. Idempotency is built into the script — on `already-cloned` it does nothing destructive other than refresh the mirror and re-copy the skills/workflows from upstream (which is the intended behavior — keeping local in sync with upstream).
+- Step 1 is always safe to re-run. Idempotency is built into the script — on `already-cloned` it does nothing destructive other than refresh the mirror and re-copy the commands/workflows from upstream (which is the intended behavior — keeping local in sync with upstream).
 - Never delete `_siesa-agents/devops/` from this skill. The user owns that directory once cloned; they may have in-progress edits.
-- Do not modify the DevOps skills themselves from this skill. If a deploy skill's behavior needs to change, that is a PR to `architecture-sa-devops`, not a local edit (which would be wiped on the next run).
+- Do not modify the DevOps commands themselves from this skill. If a deploy command's behavior needs to change, that is a PR to `business-shared-deploy`, not a local edit (which would be wiped on the next run).
 - The script's JSON output is the contract. If a future field appears (e.g. a new status), surface it to the user rather than guessing what it means.

package/claude/skills/sa-wds-visual-proposals/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: sa-wds-visual-proposals
+description: 'Toma los artefactos de planning ya hechos (PRD, épicas/historias, UX spec, arquitectura) como base y dirige el módulo WDS (Freya) para generar propuestas visuales — escenarios UX, page-specs y prototipos renderizados con siesa-ui-kit — ayudando a los diseñadores. Úsalo cuando el usuario diga "generar propuestas visuales", "wds visual proposals", "diseñar pantallas desde el planning" o quiera convertir el planning en mockups con siesa-ui-kit.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: FIRST load the FULL @_siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals/workflow_ext.md and apply its mandatory Siesa rules. THEN load the FULL @_siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals/workflow.md, READ its entire contents and follow its directions exactly!

package/package.json

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

package/siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals/data/component-mapping.csv

@@ -0,0 +1,47 @@
+ui_need,siesa_uikit_component,level,notes
+Botón de acción / CTA,Button,atom,"variantes Default/Outline/Plain, soporta icono"
+Grupo de botones tipo toggle,ButtonGroup,atom,selección estilo radio
+Contenedor de contenido,Card,atom,"subcomponentes Header/Title/Content/Footer"
+Etiqueta / estado / categoría,Badge,atom,variantes de color
+Diálogo modal / confirmación,Alert Dialog,atom,alertas y diálogos del sistema
+Imagen de perfil de usuario,Avatar,atom,
+Casilla de verificación,Checkbox,atom,
+Selección única en grupo,Radio,atom,"RadioGroup, RadioGroupItem"
+Interruptor on/off,Switch,atom,
+Campo de texto,Input,atom,
+Campo numérico,InputNumber,atom,
+Área de texto multilínea,Textarea,atom,
+Selector desplegable,Select,atom,navegación por teclado
+Menú de opciones,Dropdown,atom,"items, headings, dividers"
+Navegación por pestañas,Tabs,atom,soporta icono/badge
+Tabla de datos,Table,atom,"ordenamiento, variantes visuales"
+Separador de contenido,Divider,atom,
+Paginación,Pagination,atom,
+Selección jerárquica con checkboxes,Tree,atom,cascada
+Mensaje informativo / banner,Info,atom,
+Notificación temporal,Toast,atom,sistema de notificaciones
+Contador de alertas,Notification,atom,badge con contador
+Navegación lateral,NavigationRail,navigation,"con NavigationRailGroup/Item/Panel"
+Navegación inferior móvil,NavigationBar,navigation,3-5 destinos
+Carga de archivos,FileUploader,file,"drag-and-drop, progreso, validación"
+Galería de archivos,FileUploaderGallery,file,
+Búsqueda de entidad relacionada,LookupField,form,relación entre entidades
+Lista clave-valor,DescriptionList,form,
+Guardar/restaurar filtros,FormCacheSelector,form,
+Gestión CRUD de entidad,MasterCrud,enterprise,"listados+formularios+acciones; modos Modal/Sidebar/Page; consultar skill MasterCrud"
+Contenedor de formulario CRUD,MasterPatternView,enterprise,
+Gestión documental,MasterDocument,enterprise,"InstallmentsPanel, WithholdingsPanel, etc."
+Auditoría (historial + detalle),AuditHistoryPanel,audit,"timeline + diff campo a campo"
+Pantalla de login,LoginView,view,vista completa de inicio de sesión
+Pantalla de registro,SignUpView,view,con aceptación de términos
+Recuperar contraseña,RecoverPasswordView,view,
+Layout comercial (rail + navbar),LayoutBase,view,
+Contenedor principal con toolbar,LayoutContent,view,
+Vista de lista genérica,ListView,view,
+Tablero / dashboard,Dashboard,view,
+Selección de productos POS,ProductsView,view,categorías/grid/carrito
+Gestión de mesas POS,TableLayoutView,view,
+Gestión de contactos,ContactManager,view,CRUD completo de contactos
+Chat de soporte,ChatWidget,view,flotante
+Edición de parámetros del sistema,ParameterEditor,config,Server-Driven UI
+Administración de entidades dinámicas,Dynamic Entities/Admin,dynamic,no-code

package/siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals/steps/step-01-init.md

@@ -0,0 +1,148 @@
+---
+name: 'step-01-init'
+description: 'Inicializa el workflow: carga config, detecta continuación, descubre artefactos de planning y el catálogo siesa-ui-kit, y define el alcance de las propuestas visuales'
+
+# Path Definitions
+workflow_path: '{project-root}/_siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
+nextStepFile: '{workflow_path}/steps/step-02-bridge.md'
+workflowFile: '{workflow_path}/workflow.md'
+
+# WDS module
+wds_module_path: '{project-root}/_siesa-agents/wds'
+wds_config: '{wds_module_path}/config.yaml'
+wds_scripts_path: '{wds_module_path}/scripts'
+
+# Catalog / standards
+siesa_uikit_catalog_url: 'https://siesa-ui-kit.pages.dev/llms.txt'
+company_standards_path: '{project-root}/_siesa-agents/bmm/workflows/3-solutioning/create-architecture/data/company-standards'
+base_ux_spec: '{project-root}/_siesa-agents/resources/ux-ui/ux-design-specification.md'
+
+# Data References
+componentMappingData: '{workflow_path}/data/component-mapping.csv'
+
+# Config
+bmmConfig: '{project-root}/_bmad/bmm/config.yaml'
+---
+
+# Step 1: Inicialización y Descubrimiento
+
+## STEP GOAL
+
+Preparar todo el contexto para construir el puente planning → WDS: cargar configuración, detectar si es una re-ejecución, descubrir los artefactos de planning existentes, resolver el catálogo y el paquete de siesa-ui-kit, y acordar con el usuario el **alcance** (qué épicas/features se convierten en propuestas visuales).
+
+## MANDATORY EXECUTION RULES (READ FIRST)
+
+- 🛑 NEVER generate WDS artifacts in this step — solo descubrimiento y alcance
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- 🇪🇸 Texto de UI siempre en español; siesa-ui-kit primero
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+## INITIALIZATION SEQUENCE
+
+### 1. Load Configuration
+
+Load `{bmmConfig}` and resolve: `{project_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{implementation_artifacts}`, `{project_knowledge}`, `{output_folder}`.
+
+Load `{wds_config}` and resolve `{design_artifacts}` (WDS base output path) and `{wds_output_folder}`. **WDS config wins for WDS paths** (see workflow_ext.md §4).
+
+### 2. Detect Continuation
+
+Check whether a WDS project already exists for visual proposals:
+
+- `{design_artifacts}/_progress/wds-project-outline.yaml`
+- `{design_artifacts}/A-Product-Brief/product-brief.md`
+- `{design_artifacts}/C-UX-Scenarios/` (any scenario folders)
+
+**If any exist** → this is a re-run. Load `{continueStepFile}`, read it fully, and execute it. STOP here.
+
+**If none exist** → fresh run. Continue to section 3.
+
+### 3. Discover Planning Artifacts (the BASE)
+
+Search the workspace for the SIESA planning artifacts that will feed the bridge. Look under `{planning_artifacts}/`, `{project_knowledge}/`, `{output_folder}/`, and the repo root:
+
+| Artifact | Typical location / glob | Used for |
+|---|---|---|
+| PRD | `*PRD*.md`, `prd/*.md`, `prd/feature-*.md` | Vision, goals, target users, scope → Product Brief |
+| Épicas/historias | `epics*.md`, `epics/epic-*.md`, `stories/*.md` | Flows + acceptance criteria → Scenarios & pages |
+| UX design spec | `*ux-design-specification*.md` | Design tokens, component strategy → render fidelity |
+| Arquitectura | `*architecture*.md`, `solution-architecture*.md` | Technical constraints on what can be proposed |
+
+Build an in-memory inventory: `{ prd: [...], epics: [...], ux_spec: path|null, architecture: [...] }`.
+
+**If NO planning artifacts are found**, inform the user and offer:
+- `[B]` Buscar en otra ruta (pídela)
+- `[X]` Cancelar — este workflow requiere planning previo (usa `/create-prd`, `/create-epics-and-stories`, `/create-ux-design` primero)
+
+HALT and wait. Do not fabricate planning content.
+
+### 3b. Detect & Render the Reference Design (if the user provided one)
+
+🔴 **Aplica workflow_ext §3C.** Busca un **diseño de referencia** aportado por el usuario que la propuesta deba replicar: un mockup/`*.html` (incluidos HTML autocontenidos/bundled), imágenes (`*.png/*.jpg`), un PDF de pantallas, o un enlace de Figma — en el prompt del usuario, en la raíz del repo, o junto a los planning artifacts.
+
+**Si existe un diseño de referencia:**
+1. **Renderízalo a screenshots AHORA** (no diseñes contra una descripción textual): imagen → úsala tal cual; HTML autocontenido → Chrome headless (`--screenshot`, con `--virtual-time-budget` amplio); HTML interactivo/multi-pantalla → condúcelo con `puppeteer-core` haciendo clic hacia cada estado (lista/crear/editar/diálogos) y captura uno por pantalla; Figma → exporta frames a PNG. Guárdalos en `{design_artifacts}/_design-ref/`.
+2. Si el diseño define tokens CSS (`:root { --… }`), **extrae ese bloque** para copiarlo luego al harness en step-02b/05 (evita que los componentes custom salgan sin estilo).
+3. Registra `reference_design: [rutas de los screenshots]` para el outline y anótalo para que step-05 verifique **lado a lado** contra estas imágenes.
+
+**Si NO hay diseño de referencia:** continúa normal (la fidelidad se guía por `{base_ux_spec}` + tokens de marca).
+
+### 4. Resolve siesa-ui-kit Catalog & Package
+
+1. Fetch `{siesa_uikit_catalog_url}` and keep the component catalog in memory (atoms + view-level components like `LoginView`, `Dashboard`, `MasterCrud`, `LayoutBase`).
+   - If unreachable, warn: "⚠️ No se pudo acceder al catálogo de siesa-ui-kit; usaré la semilla local `{componentMappingData}` y los tokens de `{base_ux_spec}`."
+2. El paquete siesa-ui-kit lo **fija el repo base BaseFrontend** (`siesa-ui-kit@^1.0.109` en su `package.json`) que step-02b clona como harness (workflow_ext §3A) — no hay que resolver el nombre a mano ni requiere una app consumidora previa.
+3. Load `{componentMappingData}` (seed mapping) and `{company_standards_path}/frontend-standards.md`.
+
+### 5. Define Scope (AUTO — todas las épicas con frontend, sin preguntar)
+
+🚫 **NO preguntes al usuario.** Selecciona automáticamente **TODAS las épicas que requieren frontend** — es decir, las que contienen al menos una historia con UI de cara al usuario. **Excluye** épicas/historias puramente backend o de infraestructura (p. ej. init de proyecto, configuración de base de datos, endpoints API sin pantalla) porque no tienen UI que proponer.
+
+Reporta la selección (sin HALT) y continúa:
+
+```
+📋 Inventario de planning: PRD {n} · épicas {n} · UX spec {sí/no} · arquitectura {n}
+🧩 Catálogo siesa-ui-kit: {cargado / fallback local} · paquete: {nombre}
+🎯 Alcance (automático): todas las épicas con frontend → {lista de épicas seleccionadas}
+   Excluidas por ser backend/infra: {lista o "ninguna"}
+```
+
+Store `scope` (todas las épicas con frontend) en memoria y **procede directamente** a la sección 6 — sin menú, sin esperar.
+
+### 6. Confirm and Proceed
+
+Confirm:
+```
+✅ Configuración lista.
+- Alcance: {scope}
+- Salida WDS: {design_artifacts}
+Continuando a construir el puente estratégico (Product Brief + Trigger Map)...
+```
+
+Load, read entire file, then execute `{nextStepFile}` immediately (no further menu).
+
+## CRITICAL STEP COMPLETION NOTE
+
+Two exit paths: continuation (`{continueStepFile}`) OR fresh → `{nextStepFile}`. Never both.
+
+---
+
+## 🚨 SUCCESS / FAILURE METRICS
+
+### ✅ SUCCESS
+- Both configs loaded; WDS `design_artifacts` resolved
+- Continuation correctly detected
+- Planning inventory built from real files (not invented)
+- siesa-ui-kit catalog fetched + render mode + package resolved
+- Scope = todas las épicas con frontend, auto-seleccionadas (sin preguntar)
+
+### ❌ FAILURE
+- Inventing planning content when none found
+- Hardcoding output paths instead of reading `{wds_config}`
+- Assuming the npm package name instead of reading `package.json`
+- Preguntar el alcance al usuario en vez de auto-seleccionar todas las épicas con frontend

package/siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals/steps/step-01b-continue.md

@@ -0,0 +1,79 @@
+---
+name: 'step-01b-continue'
+description: 'Reanuda una ejecución previa del workflow de propuestas visuales a partir del estado WDS guardado'
+
+workflow_path: '{project-root}/_siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals'
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+bridgeStep: '{workflow_path}/steps/step-02-bridge.md'
+warmupStep: '{workflow_path}/steps/step-02b-kit-warmup.md'
+scenariosStep: '{workflow_path}/steps/step-03-scenarios.md'
+specsStep: '{workflow_path}/steps/step-04-specs.md'
+prototypeStep: '{workflow_path}/steps/step-05-prototype.md'
+handoffStep: '{workflow_path}/steps/step-06-handoff.md'
+wds_validate: '{project-root}/_siesa-agents/wds/scripts/wds-validate.js'
+---
+
+# Step 1b: Reanudación
+
+## STEP GOAL
+
+Detectar dónde quedó la generación previa de propuestas visuales y reanudar en el paso correcto, sin rehacer trabajo ya hecho.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the complete step file before acting
+- 🚫 NEVER overwrite existing WDS artifacts — append/continue only
+- ✅ Speak in `{communication_language}`
+
+## RESUME SEQUENCE
+
+### 1. Read the WDS State
+
+Read `{design_artifacts}/_progress/wds-project-outline.yaml` and `{design_artifacts}/_progress/00-design-log.md` (if present). Extract phase status and the "Current" task.
+
+### 2. Assess What Exists
+
+Check, under `{design_artifacts}`:
+
+| Evidence | Means stage complete |
+|---|---|
+| `A-Product-Brief/product-brief.md` + `B-Trigger-Map/trigger-map.md` | Bridge (step-02) done |
+| `_kit-playground/` (clon BaseFrontend) + `_kit-playground/kit-grounding.md` | Kit Warm-up (step-02b) done |
+| `C-UX-Scenarios/<scenario>/README.md` + page folders | Scenarios (step-03) done |
+| Page specs pass `node {wds_validate} --all --output {design_artifacts}` | Specs (step-04) done |
+| Módulos del dominio en `_kit-playground/src/modules/` + screenshots `-real.png` | Prototype (step-05) done |
+| `proposal-index.md` present | Handoff (step-06) done |
+
+### 3. Present Resume Menu (HALT)
+
+```
+🔁 Encontré una ejecución previa de propuestas visuales.
+Estado: {resumen del outline}
+
+¿Cómo continúo?
+[R] Reanudar donde quedó ({siguiente paso detectado})
+[E] Ir a un paso específico (bridge / kit-warmup / scenarios / specs / prototype / handoff)
+[N] Empezar de cero (conservará los archivos existentes; pediré confirmación antes de sobrescribir)
+[X] Cancelar
+```
+
+HALT and wait.
+
+### 4. Route
+
+Load and execute the chosen step file:
+- bridge → `{bridgeStep}`
+- kit-warmup → `{warmupStep}`
+- scenarios → `{scenariosStep}`
+- specs → `{specsStep}`
+- prototype → `{prototypeStep}`
+- handoff → `{handoffStep}`
+
+Read the chosen file fully before executing.
+
+---
+
+## 🚨 SUCCESS / FAILURE
+
+✅ Correct stage detected and resumed without redoing finished work.
+❌ Re-running the bridge over existing artifacts, or overwriting specs without confirmation.

package/siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals/steps/step-02-bridge.md

@@ -0,0 +1,114 @@
+---
+name: 'step-02-bridge'
+description: 'Traduce los artefactos de planning de SIESA a la fundación estratégica que WDS/Freya exige: Product Brief, Trigger Map, personas, tokens y project outline'
+
+workflow_path: '{project-root}/_siesa-agents/bmm/workflows/3-solutioning/wds-visual-proposals'
+thisStepFile: '{workflow_path}/steps/step-02-bridge.md'
+nextStepFile: '{workflow_path}/steps/step-02b-kit-warmup.md'
+
+productBriefTemplate: '{workflow_path}/templates/product-brief-bridge.md'
+triggerMapTemplate: '{workflow_path}/templates/trigger-map-bridge.md'
+base_ux_spec: '{project-root}/_siesa-agents/resources/ux-ui/ux-design-specification.md'
+
+# WDS guides to honor while writing the foundation
+freya_strategic_guide: '{project-root}/_siesa-agents/wds/data/agent-guides/freya/strategic-design.md'
+saga_existing_materials: '{project-root}/_siesa-agents/wds/data/agent-guides/saga/working-with-existing-materials.md'
+wds_glossary: '{project-root}/_siesa-agents/wds/data/wds-glossary.md'
+---
+
+# Step 2: Puente Estratégico (Planning → WDS)
+
+## STEP GOAL
+
+Producir, a partir de los artefactos de planning ya hechos, los prerequisitos EXACTOS que Freya valida antes de diseñar:
+
+1. `{design_artifacts}/A-Product-Brief/product-brief.md`
+2. `{design_artifacts}/B-Trigger-Map/trigger-map.md` (+ personas + feature-impact)
+3. Semilla de tokens/decisiones visuales desde la UX spec (para fidelidad de marca)
+4. `{design_artifacts}/_progress/wds-project-outline.yaml` y `_progress/00-design-log.md`
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read this entire file first
+- 🧭 Load `{saga_existing_materials}` — usa el patrón "import existing materials": referenciar → validar vigencia → llenar huecos → sintetizar. NO inventes; deriva todo del planning.
+- 🧠 Load `{freya_strategic_guide}` — el Product Brief y el Trigger Map deben quedar en términos que Freya pueda usar (golden circle WHY→HOW→WHAT, driving forces, awareness stages).
+- 📚 Load `{wds_glossary}` para respetar nombres/estructura de artefactos WDS.
+- 🇪🇸 Comunicación en `{communication_language}`; el contenido de documentos sigue `{document_output_language}`, PERO el texto de UI de ejemplo siempre en español.
+
+## EXECUTION SEQUENCE
+
+### 1. Map PRD → Product Brief
+
+Read the PRD artifacts from the step-01 inventory. Using `{productBriefTemplate}`, populate:
+
+| WDS Product Brief field | Source in SIESA planning |
+|---|---|
+| Vision / WHY | PRD problem statement, goals, value proposition |
+| Target users | PRD user segments / personas section |
+| Business goals & KPIs | PRD objectives / success metrics |
+| Scope & constraints | PRD scope + architecture constraints |
+| Content language / tone | UX spec voice (default: español, tono corporativo Siesa) |
+| Visual direction | UX spec tokens (color primario `#0e79fd`, tipografía Inter, etc.) |
+
+Write to `{design_artifacts}/A-Product-Brief/product-brief.md`. Add a provenance footer listing the source files. Where the PRD is silent, mark `⚠️ [Asunción — confirmar]` and ask the user before finalizing.
+
+### 2. Map PRD + Epics → Trigger Map & Personas
+
+Using `{triggerMapTemplate}`:
+
+- **Personas:** derive from PRD user segments. Use alliterative names per WDS convention (e.g. "Carla la Cajera"). One file each: `{design_artifacts}/B-Trigger-Map/NN-persona-<nombre>-<arquetipo>.md`.
+- **Driving forces:** map each persona's positive forces (wishes, aspirations) and negative forces (fears, frustrations) from the PRD pains/gains and epic goals.
+- **Awareness stage** per persona (Unaware → … → Most Aware) inferred from the product context.
+- **Feature impact:** build `{design_artifacts}/B-Trigger-Map/feature-impact.md` cross-referencing each in-scope epic/feature × persona × driving force.
+
+Write the main `{design_artifacts}/B-Trigger-Map/trigger-map.md`.
+
+### 3. Seed Visual Foundation from UX Spec
+
+Read `{base_ux_spec}` and the project-specific `ux-design-specification.md` (if found in step-01). Extract into a short note `{design_artifacts}/A-Product-Brief/visual-direction.md`:
+- Color tokens (primary/secondary/tertiary scales)
+- Typography (Inter), spacing scale, dark mode availability
+- Component strategy summary (siesa-ui-kit first)
+
+This note is what step-05 uses to keep prototypes brand-faithful.
+
+### 4. Write the WDS Project Outline & Design Log
+
+Create `{design_artifacts}/_progress/wds-project-outline.yaml` so Freya's activation recognizes the project:
+
+```yaml
+project_name: {project_name}
+methodology_version: wds-v6
+source: siesa-planning-bridge
+phases:
+  "1-product-brief": complete
+  "2-trigger-map": complete
+  "3-ux-scenarios": pending
+  "4-ux-design": pending
+scope: {scope from step-01}
+siesa_uikit_package: {resolved package name}
+```
+
+Initialize `{design_artifacts}/_progress/00-design-log.md` with a "Current" table pointing to "Phase 3 — generar escenarios".
+
+### 5. Review Gate (HALT)
+
+Present a concise summary of the generated foundation (personas, driving forces, visual direction) and ask:
+
+```
+He construido la base estratégica WDS desde tu planning:
+- Product Brief ✅   - Trigger Map + {n} personas ✅   - Dirección visual ✅
+
+[C] Continuar al Kit Warm-up (grounding del UI kit real) y luego a escenarios
+[E] Editar algo de la base antes de continuar
+[X] Detener aquí (la base queda lista para usar /freya manualmente)
+```
+
+HALT. On `C`, update the design log and load+execute `{nextStepFile}` (Kit Warm-up — step-02b).
+
+---
+
+## 🚨 SUCCESS / FAILURE
+
+✅ product-brief.md, trigger-map.md, personas, visual-direction.md y wds-project-outline.yaml creados, todos trazables al planning.
+❌ Inventar personas/objetivos sin fuente; omitir el outline (Freya no reconocería el proyecto); escribir UI de ejemplo en inglés.