siesa-agents 2.1.78 → 2.1.80

package/bmad/bmm/workflows/4-implementation/sprint-status/instructions.md

@@ -1,229 +0,0 @@
-# Sprint Status - Multi-Mode Service
-
-<critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml</critical>
-<critical>Modes: interactive (default), validate, data</critical>
-<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.</critical>
-
-<workflow>
-
-<step n="0" goal="Determine execution mode">
-  <action>Set mode = {{mode}} if provided by caller; otherwise mode = "interactive"</action>
-
-  <check if="mode == data">
-    <action>Jump to Step 20</action>
-  </check>
-
-  <check if="mode == validate">
-    <action>Jump to Step 30</action>
-  </check>
-
-  <check if="mode == interactive">
-    <action>Continue to Step 1</action>
-  </check>
-</step>
-
-<step n="1" goal="Locate sprint status file">
-  <action>Try {sprint_status_file}</action>
-  <check if="file not found">
-    <output>❌ sprint-status.yaml not found.
-Run `/bmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
-    <action>Exit workflow</action>
-  </check>
-  <action>Continue to Step 2</action>
-</step>
-
-<step n="2" goal="Read and parse sprint-status.yaml">
-  <action>Read the FULL file: {sprint_status_file}</action>
-  <action>Parse fields: generated, project, project_key, tracking_system, story_location</action>
-  <action>Parse development_status map. Classify keys:</action>
-  - Epics: keys starting with "epic-" (and not ending with "-retrospective")
-  - Retrospectives: keys ending with "-retrospective"
-  - Stories: everything else (e.g., 1-2-login-form)
-  <action>Map legacy story status "drafted" → "ready-for-dev"</action>
-  <action>Count story statuses: backlog, ready-for-dev, in-progress, review, done</action>
-  <action>Map legacy epic status "contexted" → "in-progress"</action>
-  <action>Count epic statuses: backlog, in-progress, done</action>
-  <action>Count retrospective statuses: optional, done</action>
-
-<action>Validate all statuses against known values:</action>
-
-- Valid story statuses: backlog, ready-for-dev, in-progress, review, done, drafted (legacy)
-- Valid epic statuses: backlog, in-progress, done, contexted (legacy)
-- Valid retrospective statuses: optional, done
-
-  <check if="any status is unrecognized">
-    <output>
-⚠️ **Unknown status detected:**
-{{#each invalid_entries}}
-
-- `{{key}}`: "{{status}}" (not recognized)
-  {{/each}}
-
-**Valid statuses:**
-
-- Stories: backlog, ready-for-dev, in-progress, review, done
-- Epics: backlog, in-progress, done
-- Retrospectives: optional, done
-  </output>
-  <ask>How should these be corrected?
-  {{#each invalid_entries}}
-  {{@index}}. {{key}}: "{{status}}" → [select valid status]
-  {{/each}}
-
-Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue without fixing:</ask>
-<check if="user provided corrections">
-<action>Update sprint-status.yaml with corrected values</action>
-<action>Re-parse the file with corrected statuses</action>
-</check>
-</check>
-
-<action>Detect risks:</action>
-
-- IF any story has status "review": suggest `/bmad:bmm:workflows:code-review`
-- IF any story has status "in-progress" AND no stories have status "ready-for-dev": recommend staying focused on active story
-- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/bmad:bmm:workflows:create-story`
-- IF `generated` timestamp is more than 7 days old: warn "sprint-status.yaml may be stale"
-- IF any story key doesn't match an epic pattern (e.g., story "5-1-..." but no "epic-5"): warn "orphaned story detected"
-- IF any epic has status in-progress but has no associated stories: warn "in-progress epic has no stories"
-  </step>
-
-<step n="3" goal="Select next action recommendation">
-  <action>Pick the next recommended workflow using priority:</action>
-  <note>When selecting "first" story: sort by epic number, then story number (e.g., 1-1 before 1-2 before 2-1)</note>
-  1. If any story status == in-progress → recommend `dev-story` for the first in-progress story
-  2. Else if any story status == review → recommend `code-review` for the first review story
-  3. Else if any story status == ready-for-dev → recommend `dev-story`
-  4. Else if any story status == backlog → recommend `create-story`
-  5. Else if any retrospective status == optional → recommend `retrospective`
-  6. Else → All implementation items done; suggest `workflow-status` to plan next phase
-  <action>Store selected recommendation as: next_story_id, next_workflow_id, next_agent (SM/DEV as appropriate)</action>
-</step>
-
-<step n="4" goal="Display summary">
-  <output>
-## 📊 Sprint Status
-
-- Project: {{project}} ({{project_key}})
-- Tracking: {{tracking_system}}
-- Status file: {sprint_status_file}
-
-**Stories:** backlog {{count_backlog}}, ready-for-dev {{count_ready}}, in-progress {{count_in_progress}}, review {{count_review}}, done {{count_done}}
-
-**Epics:** backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}}
-
-**Next Recommendation:** /bmad:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})
-
-{{#if risks}}
-**Risks:**
-{{#each risks}}
-
-- {{this}}
-  {{/each}}
-  {{/if}}
-
-  </output>
-  </step>
-
-<step n="5" goal="Offer actions">
-  <ask>Pick an option:
-1) Run recommended workflow now
-2) Show all stories grouped by status
-3) Show raw sprint-status.yaml
-4) Exit
-Choice:</ask>
-
-  <check if="choice == 1">
-    <output>Run `/bmad:bmm:workflows:{{next_workflow_id}}`.
-If the command targets a story, set `story_key={{next_story_id}}` when prompted.</output>
-  </check>
-
-  <check if="choice == 2">
-    <output>
-### Stories by Status
-- In Progress: {{stories_in_progress}}
-- Review: {{stories_in_review}}
-- Ready for Dev: {{stories_ready_for_dev}}
-- Backlog: {{stories_backlog}}
-- Done: {{stories_done}}
-    </output>
-  </check>
-
-  <check if="choice == 3">
-    <action>Display the full contents of {sprint_status_file}</action>
-  </check>
-
-  <check if="choice == 4">
-    <action>Exit workflow</action>
-  </check>
-</step>
-
-<!-- ========================= -->
-<!-- Data mode for other flows -->
-<!-- ========================= -->
-
-<step n="20" goal="Data mode output">
-  <action>Load and parse {sprint_status_file} same as Step 2</action>
-  <action>Compute recommendation same as Step 3</action>
-  <template-output>next_workflow_id = {{next_workflow_id}}</template-output>
-  <template-output>next_story_id = {{next_story_id}}</template-output>
-  <template-output>count_backlog = {{count_backlog}}</template-output>
-  <template-output>count_ready = {{count_ready}}</template-output>
-  <template-output>count_in_progress = {{count_in_progress}}</template-output>
-  <template-output>count_review = {{count_review}}</template-output>
-  <template-output>count_done = {{count_done}}</template-output>
-  <template-output>epic_backlog = {{epic_backlog}}</template-output>
-  <template-output>epic_in_progress = {{epic_in_progress}}</template-output>
-  <template-output>epic_done = {{epic_done}}</template-output>
-  <template-output>risks = {{risks}}</template-output>
-  <action>Return to caller</action>
-</step>
-
-<!-- ========================= -->
-<!-- Validate mode -->
-<!-- ========================= -->
-
-<step n="30" goal="Validate sprint-status file">
-  <action>Check that {sprint_status_file} exists</action>
-  <check if="missing">
-    <template-output>is_valid = false</template-output>
-    <template-output>error = "sprint-status.yaml missing"</template-output>
-    <template-output>suggestion = "Run sprint-planning to create it"</template-output>
-    <action>Return</action>
-  </check>
-
-<action>Read and parse {sprint_status_file}</action>
-
-<action>Validate required metadata fields exist: generated, project, project_key, tracking_system, story_location</action>
-<check if="any required field missing">
-<template-output>is_valid = false</template-output>
-<template-output>error = "Missing required field(s): {{missing_fields}}"</template-output>
-<template-output>suggestion = "Re-run sprint-planning or add missing fields manually"</template-output>
-<action>Return</action>
-</check>
-
-<action>Verify development_status section exists with at least one entry</action>
-<check if="development_status missing or empty">
-<template-output>is_valid = false</template-output>
-<template-output>error = "development_status missing or empty"</template-output>
-<template-output>suggestion = "Re-run sprint-planning or repair the file manually"</template-output>
-<action>Return</action>
-</check>
-
-<action>Validate all status values against known valid statuses:</action>
-
-- Stories: backlog, ready-for-dev, in-progress, review, done (legacy: drafted)
-- Epics: backlog, in-progress, done (legacy: contexted)
-- Retrospectives: optional, done
-  <check if="any invalid status found">
-  <template-output>is_valid = false</template-output>
-  <template-output>error = "Invalid status values: {{invalid_entries}}"</template-output>
-  <template-output>suggestion = "Fix invalid statuses in sprint-status.yaml"</template-output>
-  <action>Return</action>
-  </check>
-
-<template-output>is_valid = true</template-output>
-<template-output>message = "sprint-status.yaml valid: metadata complete, all statuses recognized"</template-output>
-</step>
-
-</workflow>

package/bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml

@@ -1,35 +0,0 @@
-# Sprint Status - Implementation Tracker
-name: sprint-status
-description: "Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-implementation_artifacts: "{config_source}:implementation_artifacts"
-planning_artifacts: "{config_source}:planning_artifacts"
-
-# Workflow components
-installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-status"
-instructions: "{installed_path}/instructions.md"
-
-# Inputs
-variables:
-  sprint_status_file: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
-  tracking_system: "file-system"
-
-# Smart input file references
-input_file_patterns:
-  sprint_status:
-    description: "Sprint status file generated by sprint-planning"
-    whole: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
-    load_strategy: "FULL_LOAD"
-
-# Standalone so IDE commands get generated
-standalone: true
-
-# No web bundle needed

package/bmad/bmm/workflows/5-documentation/README.md

@@ -1,235 +0,0 @@
-# 5-Documentation Phase - BMM Module
-
-**Phase:** Documentation
-**Module:** BMM (Build & Management Module)
-**Purpose:** Workflows for generating user documentation, API documentation, technical guides, and other end-user/developer documentation artifacts from project artifacts (PRDs, Epics, Architecture, Stories)
-
----
-
-## Overview
-
-La fase **5-documentation** contiene workflows especializados en la generación de documentación técnica y de usuario a partir de artefactos de proyecto existentes. Estos workflows automatizan la creación de guías comprehensivas, asegurando consistencia, trazabilidad y calidad en la documentación producida.
-
----
-
-## Workflows Disponibles
-
-### 📚 create-user-guide
-
-**Ruta:** `_bmad/bmm/workflows/5-documentation/create-user-guide/`
-**Comando:** `/bmad:bmm:workflows:create-user-guide`
-**Versión:** 1.0.0
-
-#### Descripción
-
-Genera guías de usuario en español desde features del proyecto (archivos individuales `prd/feature-*.md` + `epics/epic-*.md`), con diagramas Mermaid, screenshot placeholders y trazabilidad `[Source: FX Story Y.Z]`.
-
-#### Características Principales
-
-- ✅ **Salida en Español:** Archivo único por audiencia, actualizable con nuevos features
-- ✅ **Diagramas Mermaid:** Incluye diagramas para cada feature y workflow
-- ✅ **Screenshot Placeholders:** Sistema estructurado de placeholders con índice
-- ✅ **Trazabilidad:** Citaciones a épicas y stories de origen
-- ✅ **Continuación:** Soporte para resumir workflows interrumpidos
-- ✅ **Enfocado en Features:** Lee `prd/feature-*.md` + `epics/epic-*.md` por feature seleccionada
-
-#### Estructura de Archivos (15 archivos)
-
-```
-create-user-guide/
-├── workflow.md                              # Entry point del workflow
-├── workflow-plan-create-user-guide.md       # Documento de planificación
-│
-├── steps/                                   # 8 step files
-│   ├── step-01-init.md                     # Inicialización + detección continuación
-│   ├── step-01b-continue.md                # Reanudación de workflow
-│   ├── step-02-seleccion-epicas.md         # Selección de épicas (PRESCRIPTIVE)
-│   ├── step-03-analisis-fuentes.md         # Análisis de artefactos (INTENT-BASED)
-│   ├── step-04-elicitacion.md              # Elicitación de info (INTENT-BASED)
-│   ├── step-05-generacion-espanol.md       # Generación español (PRESCRIPTIVE)
-│   ├── step-06-traduccion-ingles.md        # Traducción inglés (PRESCRIPTIVE)
-│   └── step-07-validacion-guardado.md      # Validación final (PRESCRIPTIVE)
-│
-├── templates/                               # 2 templates bilingües
-│   ├── user-guide-template-es.md           # Template español con frontmatter
-│   └── user-guide-template-en.md           # Template inglés con frontmatter
-│
-└── data/                                    # 3 CSV data files
-    ├── audience-types.csv                  # 4 tipos de audiencia
-    ├── diagram-types.csv                   # 5 tipos de diagramas Mermaid
-    └── section-structure.csv               # 9 secciones de guía
-
-```
-
-#### Flujo del Workflow (8 pasos)
-
-1. **step-01-init** → Inicialización y configuración de audiencia
-   - Detecta workflows existentes
-   - Configura audiencia (enduser/admin/api/mixed)
-   - Crea documento inicial con frontmatter
-
-2. **step-01b-continue** → Continuación (si aplica)
-   - Carga estado guardado
-   - Resume desde último paso completado
-
-3. **step-02-seleccion-epicas** → Selección de Features
-   - Escanea `planning_artifacts/prd/feature-*.md`
-   - Usuario selecciona qué features documentar
-   - Verifica existencia de épica correspondiente por feature
-   - Registra selección en frontmatter (`features_selected`)
-
-4. **step-03-analisis-fuentes** → Análisis de Features
-   - Por cada feature: lee `prd/feature-*.md` (descripción, FRs, key behaviors)
-   - Si existe: lee `epics/epic-*.md` (historias, GWT, acceptance criteria)
-   - Lee contexto general (goals.md, background-context.md)
-   - Genera sección "Contexto del Proyecto"
-
-5. **step-04-elicitacion** → Elicitación de preferencias
-   - Conversación para capturar nivel técnico
-   - Escenarios adicionales
-   - Features a excluir
-
-6. **step-05-generacion-espanol** → Generación en español
-   - Genera 9 secciones completas
-   - Incluye diagramas Mermaid para cada feature
-   - Agrega screenshot placeholders
-   - Cita fuentes `[Source: FX Story Y.Z]`
-
-7. **step-06-traduccion-ingles** → ⛔ DESHABILITADO
-   - Paso conservado como referencia pero no se ejecuta
-   - El workflow salta directamente a step-07
-
-8. **step-07-validacion-guardado** → Validación y guardado
-   - Ejecuta TOP 5 validaciones
-   - Presenta resultados al usuario
-   - Permite loop a step-05 para correcciones
-   - Guarda ambas versiones + index.md
-
-#### Datos Estructurados
-
-**audience-types.csv** (4 tipos de audiencia)
-```csv
-audience_id,audience_name_es,audience_name_en,description_es,description_en,filename_prefix
-enduser,Usuarios Finales,End Users,...,enduser-guide
-admin,Administradores,Administrators,...,admin-guide
-api,Consumidores de API,API Consumers,...,api-guide
-mixed,Audiencia Mixta,Mixed Audience,...,complete-guide
-```
-
-**diagram-types.csv** (5 tipos de diagramas)
-```csv
-content_type,diagram_type,mermaid_syntax,use_case_es,use_case_en
-feature_overview,flowchart,"flowchart LR",...
-user_workflow,flowchart,"flowchart TD",...
-sequential_process,sequenceDiagram,...
-state_changes,stateDiagram-v2,...
-user_journey,journey,...
-```
-
-**section-structure.csv** (9 secciones)
-```csv
-section_id,section_name_es,section_name_en,description,required
-1,Introducción,Introduction,...,true
-2,Primeros Pasos,Getting Started,...,true
-3,Conceptos Clave,Core Concepts,...,true
-4,Funcionalidades,Features and How to Use Them,...,true
-5,Flujos de Trabajo,Common Workflows,...,true
-6,Solución de Problemas,Troubleshooting,...,false
-7,Preguntas Frecuentes,FAQ,...,true
-8,Glosario,Glossary,...,true
-9,Índice de Capturas,Screenshot Index,...,true
-```
-
-#### Criterios de Validación (TOP 5)
-
-1. **📄 Bilingual Output Completo** - Ambas versiones existen con estructura idéntica
-2. **🔗 Source Citations Obligatorias** - Cada feature tiene citación de origen
-3. **📊 Diagramas Mermaid Completos** - Cada feature/workflow tiene diagrama
-4. **📸 Screenshot Placeholders Presentes** - Formato correcto + índice
-5. **✅ Self-Check Pasado** - Completeness >= 90%, sin TODOs
-
-#### Output Generado
-
-**Ubicación:** `docs/user-guide/`
-
-```
-docs/user-guide/
-├── index.md                          # Selector de idioma
-├── es/
-│   └── {audience}-guide.md          # Guía en español
-└── en/
-    └── {audience}-guide.md          # Guía en inglés
-```
-
-Donde `{audience}` = `enduser-guide` | `admin-guide` | `api-guide` | `complete-guide`
-
-#### Patrones de Interacción
-
-- **PRESCRIPTIVE Steps** (01, 02, 05, 06, 07): Instrucciones exactas, ejecución paso a paso
-- **INTENT-BASED Steps** (03, 04): Objetivo claro, libertad de implementación
-- **Collaboration Level:** 40% user input / 60% autonomous generation
-
-#### Tecnologías Utilizadas
-
-- Mermaid.js para diagramas
-- Markdown con frontmatter YAML
-- CSV para datos estructurados
-- Sistema de templates bilingües
-
----
-
-## Estadísticas de la Fase
-
-| Métrica | Valor |
-|---------|-------|
-| Total Workflows | 1 |
-| Total Archivos | 15 |
-| Step Files | 8 |
-| Templates | 2 |
-| Data Files | 3 |
-| Idiomas Soportados | 2 (ES/EN) |
-
----
-
-## Uso
-
-Para ejecutar el workflow create-user-guide:
-
-```bash
-/bmad:bmm:workflows:create-user-guide
-```
-
-O mediante Skill tool:
-```bash
-bmad:bmm:workflows:create-user-guide
-```
-
----
-
-## Arquitectura
-
-Todos los workflows en esta fase utilizan **step-file architecture**:
-
-- **Micro-file Design**: Cada step es autocontenido
-- **Just-In-Time Loading**: Solo el step actual en memoria
-- **Sequential Enforcement**: Secuencia estricta sin optimizaciones
-- **State Tracking**: Progreso en frontmatter `stepsCompleted`
-- **Append-Only Building**: Construcción incremental de documentos
-
----
-
-## Próximos Workflows (Planificados)
-
-- `create-api-docs` - Generación de documentación API desde arquitectura
-- `create-tech-guide` - Guías técnicas para desarrolladores
-- `create-deployment-guide` - Documentación de deployment y operaciones
-- `update-documentation` - Actualización de docs existentes con cambios
-
----
-
-## Metadatos
-
-**Última Actualización:** 2026-01-14
-**Creado Por:** BMAD Module Builder Workflow
-**Versión BMAD:** 6.0
-**Módulo:** BMM (Build & Management Module)