siesa-agents 1.0.0

package/README.md

@@ -0,0 +1,84 @@
+# SIESA BMAD Agents
+
+Paquete para instalar y configurar agentes SIESA BMAD en tu proyecto.
+
+## Instalación
+
+### Instalación única con npx (Recomendado)
+
+```bash
+npx siesa-agents
+```
+
+Este comando instalará automáticamente las carpetas necesarias en tu directorio actual.
+
+### Instalación global
+
+```bash
+npm install -g siesa-bmad-agents
+siesa-agents
+```
+
+## ¿Qué hace este paquete?
+
+El paquete instala las siguientes carpetas en tu directorio actual:
+
+- **`.bmad-core/`** - Archivos principales del sistema BMAD
+- **`.vscode/`** - Configuración de Visual Studio Code
+- **`.github/`** - Configuración de GitHub Actions y workflows
+
+## Características
+
+✅ **Instalación automática**: Copia las carpetas necesarias automáticamente  
+✅ **Actualización inteligente**: Detecta instalaciones existentes y las actualiza  
+✅ **Instalación local**: Se instala en el directorio donde ejecutas el comando  
+✅ **Sobrescritura segura**: Reemplaza archivos existentes sin perder configuración
+
+## Uso
+
+1. Navega al directorio donde quieres instalar los agentes BMAD
+2. Ejecuta `npx siesa-agents`
+3. Las carpetas se instalarán automáticamente
+
+### Actualización
+
+Para actualizar una instalación existente, simplemente ejecuta el comando nuevamente:
+
+```bash
+npx siesa-agents
+```
+
+El sistema detectará automáticamente que ya existe una instalación y la actualizará.
+
+## Requisitos
+
+- Node.js >= 14.0.0
+- npm >= 6.0.0
+
+## Estructura de archivos instalados
+
+```
+tu-proyecto/
+├── .bmad-core/
+│   └── [archivos del sistema BMAD]
+├── .vscode/
+│   └── [configuración de VS Code]
+└── .github/
+    └── [workflows y configuración de GitHub]
+```
+
+## Soporte
+
+Si encuentras algún problema durante la instalación, por favor verifica:
+
+1. Que tienes permisos de escritura en el directorio
+2. Que Node.js está instalado correctamente
+3. Que tienes acceso a npm
+
+## Licencia
+
+MIT
+
+## Autor
+
+SIESA - Sistemas de Información Empresarial

package/bin/install.js

@@ -0,0 +1,155 @@
+#!/usr/bin/env node
+
+const fs = require('fs-extra');
+const path = require('path');
+
+class SiesaBmadInstaller {
+  constructor() {
+    // Definir las carpetas primero (nombres en el paquete vs nombres finales)
+    this.folderMappings = [
+      { source: 'bmad-core', target: '.bmad-core' },
+      { source: 'vscode', target: '.vscode' },
+      { source: 'github', target: '.github' }
+    ];
+    this.targetDir = process.cwd();
+    // Intentar múltiples ubicaciones posibles para el paquete
+    this.packageDir = this.findPackageDir();
+  }
+
+  findPackageDir() {
+    // Opción 1: directorio padre del bin (instalación normal)
+    let packageDir = path.dirname(__dirname);
+
+    // Opción 2: si estamos en npx, buscar en node_modules
+    if (!this.hasRequiredFolders(packageDir)) {
+      // Para npm 6.14+ y npx, intentar ubicaciones alternativas
+      const possiblePaths = [
+        path.join(__dirname, '..'), // bin -> paquete
+        path.resolve(__dirname, '..'), // alternativa con resolve
+        path.resolve(__dirname, '..', '..', 'siesa-bmad-agents'), // desde node_modules
+        // Intentar buscar basado en __dirname específicamente para npx
+        path.resolve(__dirname.replace(/\\bin$|\/bin$/, '')),
+        process.cwd(), // directorio actual como último recurso
+      ];
+
+      console.log('🔍 Buscando paquete en ubicaciones alternativas...');
+      for (const possiblePath of possiblePaths) {
+        console.log(`   Probando: ${possiblePath}`);
+        if (this.hasRequiredFolders(possiblePath)) {
+          console.log(`   ✅ Encontrado en: ${possiblePath}`);
+          packageDir = possiblePath;
+          break;
+        }
+      }
+    }
+
+    console.log(`🎯 Directorio del paquete seleccionado: ${packageDir}`);
+    return packageDir;
+  }
+
+  hasRequiredFolders(dir) {
+    return this.folderMappings.some(mapping => {
+      const folderPath = path.join(dir, mapping.source);
+      return fs.existsSync(folderPath);
+    });
+  }
+
+  async install() {
+    console.log('🔍 Directorio del paquete:', this.packageDir);
+    console.log('🚀 Instalando SIESA BMAD Agents...');
+    console.log(`📁 Directorio de destino: ${this.targetDir}`);
+
+    try {
+      // Verificar si ya existe una instalación
+      const hasExistingInstallation = this.checkExistingInstallation();
+      
+      if (hasExistingInstallation) {
+        console.log('🔄 Instalación existente detectada. Actualizando...');
+        await this.update();
+      } else {
+        console.log('✨ Nueva instalación...');
+        await this.performInstallation();
+      }
+
+      console.log('✅ SIESA BMAD Agents instalado correctamente!');
+      this.showPostInstallMessage();
+
+    } catch (error) {
+      console.error('❌ Error durante la instalación:', error.message);
+      process.exit(1);
+    }
+  }
+
+  checkExistingInstallation() {
+    return this.folderMappings.some(mapping => {
+      const targetPath = path.join(this.targetDir, mapping.target);
+      return fs.existsSync(targetPath);
+    });
+  }
+
+  async performInstallation() {
+    // Debug: listar contenido del directorio del paquete
+    console.log('🔍 Contenido del directorio del paquete:');
+    try {
+      const packageContents = await fs.readdir(this.packageDir);
+      console.log('📋 Archivos/carpetas encontrados:', packageContents);
+    } catch (error) {
+      console.log('❌ Error leyendo directorio del paquete:', error.message);
+    }
+
+    for (const mapping of this.folderMappings) {
+      const sourcePath = path.join(this.packageDir, mapping.source);
+      const targetPath = path.join(this.targetDir, mapping.target);
+
+      console.log(`🔍 Buscando: ${sourcePath}`);
+      if (fs.existsSync(sourcePath)) {
+        console.log(`📋 Copiando ${mapping.source} -> ${mapping.target}...`);
+        await fs.copy(sourcePath, targetPath, {
+          overwrite: true,
+          recursive: true
+        });
+        console.log(`✓ ${mapping.target} copiado exitosamente`);
+      } else {
+        console.warn(`⚠️  Carpeta ${mapping.source} no encontrada en el paquete`);
+      }
+    }
+  }
+
+  async update() {
+    // Crear backup de archivos existentes si es necesario
+    for (const mapping of this.folderMappings) {
+      const targetPath = path.join(this.targetDir, mapping.target);
+
+      if (fs.existsSync(targetPath)) {
+        console.log(`🔄 Actualizando ${mapping.target}...`);
+        // Remover carpeta existente
+        await fs.remove(targetPath);
+      }
+    }
+
+    // Realizar instalación nueva
+    await this.performInstallation();
+  }
+
+  showPostInstallMessage() {
+    console.log('\n📚 Carpetas instaladas:');
+    this.folderMappings.forEach(mapping => {
+      const targetPath = path.join(this.targetDir, mapping.target);
+      if (fs.existsSync(targetPath)) {
+        console.log(`  ✓ ${mapping.target}`);
+      }
+    });
+
+    console.log('\n🎉 ¡Instalación completada!');
+    console.log('💡 Las carpetas han sido instaladas en tu directorio actual.');
+    console.log('🔧 Puedes ejecutar "npx siesa-agents" nuevamente para actualizar.');
+  }
+}
+
+// Ejecutar instalación si el script es llamado directamente
+if (require.main === module) {
+  const installer = new SiesaBmadInstaller();
+  installer.install();
+}
+
+module.exports = SiesaBmadInstaller;

package/bin/prepare-publish.js

@@ -0,0 +1,27 @@
+#!/usr/bin/env node
+
+const fs = require('fs-extra');
+const path = require('path');
+
+const rootDir = path.dirname(__dirname);
+
+// Renombrar carpetas que empiezan con punto para que npm las incluya
+const folderMappings = [
+  { from: '.bmad-core', to: 'bmad-core' },
+  { from: '.vscode', to: 'vscode' },
+  { from: '.github', to: 'github' }
+];
+
+console.log('📦 Preparando carpetas para publicación...');
+
+for (const mapping of folderMappings) {
+  const fromPath = path.join(rootDir, mapping.from);
+  const toPath = path.join(rootDir, mapping.to);
+
+  if (fs.existsSync(fromPath)) {
+    console.log(`📁 Renombrando ${mapping.from} -> ${mapping.to}`);
+    fs.moveSync(fromPath, toPath);
+  }
+}
+
+console.log('✅ Carpetas preparadas para publicación');

package/bin/restore-folders.js

@@ -0,0 +1,27 @@
+#!/usr/bin/env node
+
+const fs = require('fs-extra');
+const path = require('path');
+
+const rootDir = path.dirname(__dirname);
+
+// Restaurar nombres originales de las carpetas
+const folderMappings = [
+  { from: 'bmad-core', to: '.bmad-core' },
+  { from: 'vscode', to: '.vscode' },
+  { from: 'github', to: '.github' }
+];
+
+console.log('🔄 Restaurando nombres originales de carpetas...');
+
+for (const mapping of folderMappings) {
+  const fromPath = path.join(rootDir, mapping.from);
+  const toPath = path.join(rootDir, mapping.to);
+
+  if (fs.existsSync(fromPath)) {
+    console.log(`📁 Restaurando ${mapping.from} -> ${mapping.to}`);
+    fs.moveSync(fromPath, toPath);
+  }
+}
+
+console.log('✅ Carpetas restauradas');

package/bmad-core/agent-teams/team-all.yaml

@@ -0,0 +1,15 @@
+# <!-- Powered by BMAD™ Core -->
+bundle:
+  name: Team All
+  icon: 👥
+  description: Includes every core system agent.
+agents:
+  - bmad-orchestrator
+  - "*"
+workflows:
+  - brownfield-fullstack.yaml
+  - brownfield-service.yaml
+  - brownfield-ui.yaml
+  - greenfield-fullstack.yaml
+  - greenfield-service.yaml
+  - greenfield-ui.yaml

package/bmad-core/agent-teams/team-fullstack.yaml

@@ -0,0 +1,19 @@
+# <!-- Powered by BMAD™ Core -->
+bundle:
+  name: Team Fullstack
+  icon: 🚀
+  description: Team capable of full stack, front end only, or service development.
+agents:
+  - bmad-orchestrator
+  - analyst
+  - pm
+  - architect
+  - po
+  - ux-expert
+workflows:
+  - brownfield-fullstack.yaml
+  - brownfield-service.yaml
+  - brownfield-ui.yaml
+  - greenfield-fullstack.yaml
+  - greenfield-service.yaml
+  - greenfield-ui.yaml

package/bmad-core/agent-teams/team-ide-minimal.yaml

@@ -0,0 +1,11 @@
+# <!-- Powered by BMAD™ Core -->
+bundle:
+  name: Team IDE Minimal
+  icon: ⚡
+  description: Only the bare minimum for the IDE PO SM dev qa cycle.
+agents:
+  - po
+  - sm
+  - dev
+  - qa
+workflows: null

package/bmad-core/agent-teams/team-no-ui.yaml

@@ -0,0 +1,14 @@
+# <!-- Powered by BMAD™ Core -->
+bundle:
+  name: Team No UI
+  icon: 🔧
+  description: Team with no UX or UI Planning.
+agents:
+  - bmad-orchestrator
+  - analyst
+  - pm
+  - architect
+  - po
+workflows:
+  - greenfield-service.yaml
+  - brownfield-service.yaml

package/bmad-core/agents/analyst.md

@@ -0,0 +1,84 @@
+<!-- Powered by BMAD™ Core -->
+
+# analyst
+
+ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
+
+CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+
+## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
+
+```yaml
+IDE-FILE-RESOLUTION:
+  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
+  - Dependencies map to .bmad-core/{type}/{name}
+  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
+  - Example: create-doc.md → .bmad-core/tasks/create-doc.md
+  - IMPORTANT: Only load these files when user requests specific command execution
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
+activation-instructions:
+  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
+  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - DO NOT: Load any other agent files during activation
+  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
+  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
+  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
+  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
+  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - STAY IN CHARACTER!
+  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+agent:
+  name: Mary
+  id: analyst
+  title: Business Analyst
+  icon: 📊
+  whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, initial project discovery, and documenting existing projects (brownfield)
+  customization: null
+persona:
+  role: Insightful Analyst & Strategic Ideation Partner
+  style: Analytical, inquisitive, creative, facilitative, objective, data-informed
+  identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
+  focus: Research planning, ideation facilitation, strategic analysis, actionable insights
+  core_principles:
+    - Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
+    - Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
+    - Strategic Contextualization - Frame all work within broader strategic context
+    - Facilitate Clarity & Shared Understanding - Help articulate needs with precision
+    - Creative Exploration & Divergent Thinking - Encourage wide range of ideas before narrowing
+    - Structured & Methodical Approach - Apply systematic methods for thoroughness
+    - Action-Oriented Outputs - Produce clear, actionable deliverables
+    - Collaborative Partnership - Engage as a thinking partner with iterative refinement
+    - Maintaining a Broad Perspective - Stay aware of market trends and dynamics
+    - Integrity of Information - Ensure accurate sourcing and representation
+    - Numbered Options Protocol - Always use numbered lists for selections
+# All commands require * prefix when used (e.g., *help)
+commands:
+  - help: Show numbered list of the following commands to allow selection
+  - brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
+  - create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
+  - create-project-brief: use task create-doc with project-brief-tmpl.yaml
+  - doc-out: Output full document in progress to current destination file
+  - elicit: run the task advanced-elicitation
+  - perform-market-research: use task create-doc with market-research-tmpl.yaml
+  - research-prompt {topic}: execute task create-deep-research-prompt.md
+  - yolo: Toggle Yolo Mode
+  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
+dependencies:
+  data:
+    - bmad-kb.md
+    - brainstorming-techniques.md
+  tasks:
+    - advanced-elicitation.md
+    - create-deep-research-prompt.md
+    - create-doc.md
+    - document-project.md
+    - facilitate-brainstorming-session.md
+  templates:
+    - brainstorming-output-tmpl.yaml
+    - competitor-analysis-tmpl.yaml
+    - market-research-tmpl.yaml
+    - project-brief-tmpl.yaml
+```

package/bmad-core/agents/architect.md

@@ -0,0 +1,94 @@
+<!-- Powered by BMAD™ Core -->
+
+# architect
+
+ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
+
+CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+
+## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
+
+```yaml
+IDE-FILE-RESOLUTION:
+  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
+  - Dependencies map to .bmad-core/{type}/{name}
+  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
+  - Example: create-doc.md → .bmad-core/tasks/create-doc.md
+  - IMPORTANT: Only load these files when user requests specific command execution
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
+activation-instructions:
+  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
+  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - DO NOT: Load any other agent files during activation
+  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
+  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
+  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
+  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
+  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - STAY IN CHARACTER!
+  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+agent:
+  name: Winston
+  id: architect
+  title: Architect
+  icon: 🏗️
+  whenToUse: Use for system design, architecture documents, technology selection, API design, and infrastructure planning
+  customization: null
+persona:
+  role: Holistic System Architect & Full-Stack Technical Leader
+  style: Comprehensive, pragmatic, user-centric, technically deep yet accessible
+  identity: Master of holistic application design who bridges frontend, backend, infrastructure, and everything in between
+  focus: Complete systems architecture, cross-stack optimization, pragmatic technology selection, and orchestrating handoffs to specialist agents
+  core_principles:
+    - Holistic System Thinking - View every component as part of a larger system
+    - User Experience Drives Architecture - Start with user journeys and work backward
+    - Pragmatic Technology Selection - Choose boring technology where possible, exciting where necessary
+    - Progressive Complexity - Design systems simple to start but can scale
+    - Cross-Stack Performance Focus - Optimize holistically across all layers
+    - Developer Experience as First-Class Concern - Enable developer productivity
+    - Security at Every Layer - Implement defense in depth
+    - Data-Centric Design - Let data requirements drive architecture
+    - Cost-Conscious Engineering - Balance technical ideals with financial reality
+    - Living Architecture - Design for change and adaptation
+    - Agent Orchestration - Know when to hand off to specialist agents for implementation
+  
+  specialist_knowledge:
+    - Frontend Agent (@frontend) - React + TypeScript + Clean Architecture implementation
+    - Backend Agent (@backend) - NestJS + TypeScript + Hexagonal Architecture + DDD microservices
+    - Dev Agent (@dev) - Full-stack development and story implementation
+    - UX Expert (@ux-expert) - UI/UX specifications and design systems
+    - When projects need frontend components, recommend Frontend Agent after architecture completion
+    - When projects need backend/API services, recommend Backend Agent for microservices implementation
+# All commands require * prefix when used (e.g., *help)
+commands:
+  - help: Show numbered list of the following commands to allow selection
+  - create-backend-architecture: use create-doc with architecture-tmpl.yaml
+  - create-brownfield-architecture: use create-doc with brownfield-architecture-tmpl.yaml
+  - create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
+  - create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
+  - doc-out: Output full document to current destination file
+  - document-project: execute the task document-project.md
+  - execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
+  - research {topic}: execute task create-deep-research-prompt
+  - shard-prd: run the task shard-doc.md for the provided architecture.md (ask if not found)
+  - yolo: Toggle Yolo Mode
+  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
+dependencies:
+  checklists:
+    - architect-checklist.md
+  data:
+    - technical-preferences.md
+  tasks:
+    - create-deep-research-prompt.md
+    - create-doc.md
+    - document-project.md
+    - execute-checklist.md
+  templates:
+    - architecture-tmpl.yaml
+    - brownfield-architecture-tmpl.yaml
+    - front-end-architecture-tmpl.yaml
+    - fullstack-architecture-tmpl.yaml
+```