siesa-agents 2.1.71 → 2.1.72-qa.0

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/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.71",
+  "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/2-plan-workflows/create-ux-design/workflow_ext.md

@@ -30,7 +30,42 @@ Output to the user:
 
 ---
 
-## 2. MANDATORY RULE — PHASE COMMIT AT WORKFLOW END
+## 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.
 

package/siesa-agents/bmm/workflows/3-solutioning/create-architecture/workflow_ext.md

@@ -39,6 +39,8 @@ Before doing anything else, search for an existing architecture document:
 
 ### If `architecture.md` EXISTS
 
+Use the **AskUserQuestion** tool to present the following options:
+
 Present the user with the following options (respect `communication_language` from config):
 
 > Se encontró un documento de arquitectura existente en `{planning_artifacts}/architecture.md`.

package/siesa-agents/bmm/workflows/3-solutioning/quality-process/prompts/prompt_design_test.md

@@ -92,4 +92,4 @@ Analiza cada **Feature** simulando arquetipos universales para encontrar riesgos
    - [Otras tablas de cobertura técnica relevantes].
 
 ### APÉNDICE: MATRIZ DE TRAZABILIDAD
-- **Funcionalidad → Features → Casos**: [Listado jerárquico que conecte el Feature con sus historias de origen y los IDs de los casos de prueba generados].
+- **Funcionalidad → Features → Casos**: [Listado jerárquico que conecte el Feature con sus historias de origen y los IDs de los casos de prueba generados].