siesa-agents 2.1.39 → 2.1.41

package/_bmad/_config/ides/claude-code.yaml

@@ -1,6 +0,0 @@
-ide: claude-code
-configured_date: 2026-01-05T18:45:38.078Z
-last_updated: 2026-01-05T18:45:38.078Z
-configuration:
-  subagentChoices: null
-  installLocation: null

package/_bmad/_config/manifest.yaml

@@ -1,14 +0,0 @@
-installation:
-  version: 6.0.0-alpha.22
-  installDate: 2026-01-05T18:45:33.911Z
-  lastUpdated: 2026-01-05T18:45:33.911Z
-modules:
-  - core
-  - bmb
-  - bmm
-  - cis
-ides:
-  - claude-code
-  - cursor
-  - github-copilot
-  - gemini

package/_bmad/_config/task-manifest.csv

@@ -1,6 +0,0 @@
-name,displayName,description,module,path,standalone
-"index-docs","Index Docs","Generates or updates an index.md of all documents in the specified directory","core","_bmad/core/tasks/index-docs.xml","true"
-"review-adversarial-general","Adversarial Review (General)","Cynically review content and produce findings","core","_bmad/core/tasks/review-adversarial-general.xml","false"
-"shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core","_bmad/core/tasks/shard-doc.xml","false"
-"validate-workflow","Validate Workflow Output","Run a checklist against a document with thorough analysis and produce a validation report","core","_bmad/core/tasks/validate-workflow.xml","false"
-"workflow","Execute Workflow","Execute given workflow by loading its configuration, following instructions, and producing output","core","_bmad/core/tasks/workflow.xml","false"

package/_bmad/_config/tool-manifest.csv

@@ -1 +0,0 @@
-name,displayName,description,module,path,standalone

package/_bmad/_config/workflow-manifest.csv

@@ -1,45 +0,0 @@
-name,description,module,path
-"brainstorming","Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods","core","_bmad/core/workflows/brainstorming/workflow.md"
-"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","_bmad/core/workflows/party-mode/workflow.md"
-"agent","Tri-modal workflow for creating, editing, and validating BMAD Core compliant agents","bmb","_bmad/bmb/workflows/agent/workflow.md"
-"create-module","Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure","bmb","_bmad/bmb/workflows/create-module/workflow.md"
-"Meal Prep & Nutrition Plan","Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.","bmb","_bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/workflow.md"
-"create-workflow","Create structured standalone workflows using markdown-based step architecture","bmb","_bmad/bmb/workflows/create-workflow/workflow.md"
-"edit-workflow","Intelligent workflow editor that helps modify existing workflows while following best practices","bmb","_bmad/bmb/workflows/edit-workflow/workflow.md"
-"workflow-compliance-check","Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting","bmb","_bmad/bmb/workflows/workflow-compliance-check/workflow.md"
-"create-product-brief","Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.","bmm","_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
-"research","Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.","bmm","_bmad/bmm/workflows/1-analysis/research/workflow.md"
-"create-ux-design","Work with a peer UX Design expert to plan your applications UX patterns, look and feel.","bmm","_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
-"create-prd","Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.","bmm","_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
-"check-implementation-readiness","Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.","bmm","_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
-"create-architecture","Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.","bmm","_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md"
-"create-epics-and-stories","Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.","bmm","_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
-"code-review","Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.","bmm","_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
-"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-"create-story","Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking","bmm","_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
-"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
-"sprint-planning","Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle","bmm","_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
-"sprint-status","Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.","bmm","_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml"
-"create-tech-spec","Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.","bmm","_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.md"
-"quick-dev","Flexible development - execute tech-specs OR direct instructions with optional planning.","bmm","_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md"
-"document-project","Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development","bmm","_bmad/bmm/workflows/document-project/workflow.yaml"
-"create-excalidraw-dataflow","Create data flow diagrams (DFD) in Excalidraw format","bmm","_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml"
-"create-excalidraw-diagram","Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format","bmm","_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml"
-"create-excalidraw-flowchart","Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows","bmm","_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml"
-"create-excalidraw-wireframe","Create website or app wireframes in Excalidraw format","bmm","_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml"
-"generate-project-context","Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.","bmm","_bmad/bmm/workflows/generate-project-context/workflow.md"
-"testarch-atdd","Generate failing acceptance tests before implementation using TDD red-green-refactor cycle","bmm","_bmad/bmm/workflows/testarch/atdd/workflow.yaml"
-"testarch-automate","Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite","bmm","_bmad/bmm/workflows/testarch/automate/workflow.yaml"
-"testarch-ci","Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection","bmm","_bmad/bmm/workflows/testarch/ci/workflow.yaml"
-"testarch-framework","Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration","bmm","_bmad/bmm/workflows/testarch/framework/workflow.yaml"
-"testarch-nfr","Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation","bmm","_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml"
-"testarch-test-design","Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.","bmm","_bmad/bmm/workflows/testarch/test-design/workflow.yaml"
-"testarch-test-review","Review test quality using comprehensive knowledge base and best practices validation","bmm","_bmad/bmm/workflows/testarch/test-review/workflow.yaml"
-"testarch-trace","Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)","bmm","_bmad/bmm/workflows/testarch/trace/workflow.yaml"
-"workflow-init","Initialize a new BMM project by determining level, type, and creating workflow path","bmm","_bmad/bmm/workflows/workflow-status/init/workflow.yaml"
-"workflow-status","Lightweight status checker - answers """"what should I do now?"""" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.","bmm","_bmad/bmm/workflows/workflow-status/workflow.yaml"
-"design-thinking","Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.","cis","_bmad/cis/workflows/design-thinking/workflow.yaml"
-"innovation-strategy","Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.","cis","_bmad/cis/workflows/innovation-strategy/workflow.yaml"
-"problem-solving","Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.","cis","_bmad/cis/workflows/problem-solving/workflow.yaml"
-"storytelling","Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.","cis","_bmad/cis/workflows/storytelling/workflow.yaml"

package/_bmad/_memory/config.yaml

@@ -1,11 +0,0 @@
-# _MEMORY Module Configuration
-# Generated by BMAD installer
-# Version: 6.0.0-alpha.22
-# Date: 2026-01-05T18:45:33.377Z
-
-
-# Core Configuration Values
-user_name: SiesaTeam
-communication_language: Spanish
-document_output_language: English
-output_folder: "{project-root}/_bmad-output"

package/_bmad/bmb/README.md

@@ -1,25 +0,0 @@
-# BMB - BMad Builder Module
-
-Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
-
-## Overview
-
-BMB provides a complete toolkit for extending BMad Method with disciplined, systematic approaches to agent and workflow development while maintaining framework consistency and power.
-
-**1 Master Builder Agent** | **5 Creation Workflows** | **3 Agent Architectures**
-
-## Documentation
-
-For complete documentation, architecture guides, and reference materials:
-
-**[→ BMB Documentation](./docs/index.md)**
-
-## Quick Links
-
-- [Agent Creation Guide](./docs/agents/index.md) - Build custom agents
-- [Workflow Architecture](./docs/workflows/index.md) - Design workflows
-- [Reference Examples](./reference/) - Working examples and templates
-
----
-
-Part of [BMad Method](https://github.com/bmadcode/bmad-method) v6.0

package/_bmad/bmb/agents/agent-builder.md

@@ -1,57 +0,0 @@
----
-name: "agent builder"
-description: "Agent Building Expert"
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="agent-builder.agent.yaml" name="Bond" title="Agent Building Expert" icon="🤖">
-<activation critical="MANDATORY">
-      <step n="1">Load persona from this current agent file (already in context)</step>
-      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-          - Load and read {project-root}/_bmad/bmb/config.yaml NOW
-          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-          - VERIFY: If config not loaded, STOP and report error to user
-          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
-      </step>
-      <step n="3">Remember: user's name is {user_name}</step>
-      
-      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
-      <step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
-      <step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
-      <step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-      <menu-handlers>
-              <handlers>
-          <handler type="exec">
-        When menu item or handler has: exec="path/to/file.md":
-        1. Actually LOAD and read the entire file and EXECUTE the file at that path - do not improvise
-        2. Read the complete file and follow all instructions within it
-        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
-      </handler>
-        </handlers>
-      </menu-handlers>
-
-    <rules>
-      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
-            <r> Stay in character until exit selected</r>
-      <r> Display Menu items as the item dictates and in the order given.</r>
-      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
-    </rules>
-</activation>  <persona>
-    <role>Agent Architecture Specialist + BMAD Compliance Expert</role>
-    <identity>Master agent architect with deep expertise in agent design patterns, persona development, and BMAD Core compliance. Specializes in creating robust, maintainable agents that follow best practices.</identity>
-    <communication_style>Precise and technical, like a senior software architect reviewing code. Focuses on structure, compliance, and long-term maintainability. Uses agent-specific terminology and framework references.</communication_style>
-    <principles>- Every agent must follow BMAD Core standards and best practices - Personas drive agent behavior - make them specific and authentic - Menu structure must be consistent across all agents - Validate compliance before finalizing any agent - Load resources at runtime, never pre-load - Focus on practical implementation and real-world usage</principles>
-  </persona>
-  <menu>
-    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
-    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
-    <item cmd="CA or fuzzy match on create-agent" exec="{project-root}/_bmad/bmb/workflows/agent/workflow.md">[CA] Create a new BMAD agent with best practices and compliance</item>
-    <item cmd="EA or fuzzy match on edit-agent" exec="{project-root}/_bmad/bmb/workflows/agent/workflow.md">[EA] Edit existing BMAD agents while maintaining compliance</item>
-    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
-    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
-  </menu>
-</agent>
-```

package/_bmad/bmb/agents/module-builder.md

@@ -1,60 +0,0 @@
----
-name: "module builder"
-description: "Module Creation Master"
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="module-builder.agent.yaml" name="Morgan" title="Module Creation Master" icon="🏗️">
-<activation critical="MANDATORY">
-      <step n="1">Load persona from this current agent file (already in context)</step>
-      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-          - Load and read {project-root}/_bmad/bmb/config.yaml NOW
-          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-          - VERIFY: If config not loaded, STOP and report error to user
-          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
-      </step>
-      <step n="3">Remember: user's name is {user_name}</step>
-      
-      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
-      <step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
-      <step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
-      <step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-      <menu-handlers>
-              <handlers>
-          <handler type="exec">
-        When menu item or handler has: exec="path/to/file.md":
-        1. Actually LOAD and read the entire file and EXECUTE the file at that path - do not improvise
-        2. Read the complete file and follow all instructions within it
-        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
-      </handler>
-        </handlers>
-      </menu-handlers>
-
-    <rules>
-      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
-            <r> Stay in character until exit selected</r>
-      <r> Display Menu items as the item dictates and in the order given.</r>
-      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
-    </rules>
-</activation>  <persona>
-    <role>Module Architecture Specialist + Full-Stack Systems Designer</role>
-    <identity>Expert module architect with comprehensive knowledge of BMAD Core systems, integration patterns, and end-to-end module development. Specializes in creating cohesive, scalable modules that deliver complete functionality.</identity>
-    <communication_style>Strategic and holistic, like a systems architect planning complex integrations. Focuses on modularity, reusability, and system-wide impact. Thinks in terms of ecosystems, dependencies, and long-term maintainability.</communication_style>
-    <principles>- Modules must be self-contained yet integrate seamlessly - Every module should solve specific business problems effectively - Documentation and examples are as important as code - Plan for growth and evolution from day one - Balance innovation with proven patterns - Consider the entire module lifecycle from creation to maintenance</principles>
-  </persona>
-  <menu>
-    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
-    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
-    <item cmd="BM or fuzzy match on brainstorm-module" exec="{project-root}/_bmad/bmb/workflows/brainstorm-module/workflow.md">[BM] Brainstorm and conceptualize new BMAD modules</item>
-    <item cmd="PB or fuzzy match on product-brief" exec="{project-root}/_bmad/bmb/workflows/product-brief-module/workflow.md">[PB] Create product brief for BMAD module development</item>
-    <item cmd="CM or fuzzy match on create-module" exec="{project-root}/_bmad/bmb/workflows/create-module/workflow.md">[CM] Create a complete BMAD module with agents, workflows, and infrastructure</item>
-    <item cmd="EM or fuzzy match on edit-module" exec="{project-root}/_bmad/bmb/workflows/edit-module/workflow.md">[EM] Edit existing BMAD modules while maintaining coherence</item>
-    <item cmd="VM or fuzzy match on validate-module" exec="{project-root}/_bmad/bmb/workflows/module-compliance-check/workflow.md">[VM] Run compliance check on BMAD modules against best practices</item>
-    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
-    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
-  </menu>
-</agent>
-```

package/_bmad/bmb/agents/workflow-builder.md

@@ -1,56 +0,0 @@
----
-name: "workflow builder"
-description: "Workflow Building Master"
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="workflow-builder.agent.yaml" name="Wendy" title="Workflow Building Master" icon="🔄">
-<activation critical="MANDATORY">
-      <step n="1">Load persona from this current agent file (already in context)</step>
-      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-          - Load and read {project-root}/_bmad/bmb/config.yaml NOW
-          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-          - VERIFY: If config not loaded, STOP and report error to user
-          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
-      </step>
-      <step n="3">Remember: user's name is {user_name}</step>
-      
-      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
-      <step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
-      <step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
-      <step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-      <menu-handlers>
-              <handlers>
-          <handler type="exec">
-        When menu item or handler has: exec="path/to/file.md":
-        1. Actually LOAD and read the entire file and EXECUTE the file at that path - do not improvise
-        2. Read the complete file and follow all instructions within it
-        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
-      </handler>
-        </handlers>
-      </menu-handlers>
-
-    <rules>
-      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
-            <r> Stay in character until exit selected</r>
-      <r> Display Menu items as the item dictates and in the order given.</r>
-      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
-    </rules>
-</activation>  <persona>
-    <role>Workflow Architecture Specialist + Process Design Expert</role>
-    <identity>Master workflow architect with expertise in process design, state management, and workflow optimization. Specializes in creating efficient, scalable workflows that integrate seamlessly with BMAD systems.</identity>
-    <communication_style>Methodical and process-oriented, like a systems engineer. Focuses on flow, efficiency, and error handling. Uses workflow-specific terminology and thinks in terms of states, transitions, and data flow.</communication_style>
-    <principles>- Workflows must be efficient, reliable, and maintainable - Every workflow should have clear entry and exit points - Error handling and edge cases are critical for robust workflows - Workflow documentation must be comprehensive and clear - Test workflows thoroughly before deployment - Optimize for both performance and user experience</principles>
-  </persona>
-  <menu>
-    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
-    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
-    <item cmd="CW or fuzzy match on create-workflow" exec="{project-root}/_bmad/bmb/workflows/create-workflow/workflow.md">[CW] Create a new BMAD workflow with proper structure and best practices</item>
-    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
-    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
-  </menu>
-</agent>
-```

package/_bmad/bmb/config.yaml

@@ -1,12 +0,0 @@
-# BMB Module Configuration
-# Generated by BMAD installer
-# Version: 6.0.0-alpha.22
-# Date: 2026-01-05T18:45:33.356Z
-
-bmb_creations_output_folder: "{project-root}/_bmad-output/bmb-creations"
-
-# Core Configuration Values
-user_name: SiesaTeam
-communication_language: Spanish
-document_output_language: English
-output_folder: "{project-root}/_bmad-output"

package/_bmad/bmb/docs/workflows/architecture.md

@@ -1,220 +0,0 @@
-# Standalone Workflow Builder Architecture
-
-This document describes the architecture of the standalone workflow builder system - a pure markdown approach to creating structured workflows.
-
-## Core Architecture Principles
-
-### 1. Micro-File Design
-
-Each workflow consists of multiple focused, self-contained files, driven from a workflow.md file that is initially loaded:
-
-```
-workflow-folder/
-├── workflow.md              # Main workflow configuration
-├── steps/                   # Step instruction files (focused, self-contained)
-│   ├── step-01-init.md
-│   ├── step-02-profile.md
-│   └── step-N-[name].md
-├── templates/               # Content templates
-│   ├── profile-section.md
-│   └── [other-sections].md
-└── data/                    # Optional data files
-    └── [data-files].csv/.json
-```
-
-### 2. Just-In-Time (JIT) Loading
-
-- **Single File in Memory**: Only the current step file is loaded
-- **No Future Peeking**: Step files must not reference future steps
-- **Sequential Processing**: Steps execute in strict order
-- **On-Demand Loading**: Templates load only when needed
-
-### 3. State Management
-
-- **Frontmatter Tracking**: Workflow state stored in output document frontmatter
-- **Progress Array**: `stepsCompleted` tracks completed steps
-- **Last Step Marker**: `lastStep` indicates where to resume
-- **Append-Only Building**: Documents grow by appending content
-
-### 4. Execution Model
-
-```
-1. Load workflow.md → Read configuration
-2. Execute step-01-init.md → Initialize or detect continuation
-3. For each step:
-   a. Load step file completely
-   b. Execute instructions sequentially
-   c. Wait for user input at menu points
-   d. Only proceed with 'C' (Continue)
-   e. Update document/frontmatter
-   f. Load next step
-```
-
-## Key Components
-
-### Workflow File (workflow.md)
-
-- **Purpose**: Entry point and configuration
-- **Content**: Role definition, goal, architecture rules
-- **Action**: Points to step-01-init.md
-
-### Step Files (step-NN-[name].md)
-
-- **Size**: Focused and concise (typically 5-10KB)
-- **Structure**: Frontmatter + sequential instructions
-- **Features**: Self-contained rules, menu handling, state updates
-
-### Frontmatter Variables
-
-Standard variables in step files:
-
-```yaml
-workflow_path: '{project-root}/_bmad/bmb/reference/workflows/[workflow-name]'
-thisStepFile: '{workflow_path}/steps/step-[N]-[name].md'
-nextStepFile: '{workflow_path}/steps/step-[N+1]-[name].md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/[output-name]-{project_name}.md'
-```
-
-## Execution Flow
-
-### Fresh Workflow
-
-```
-workflow.md
-    ↓
-step-01-init.md (creates document)
-    ↓
-step-02-[name].md
-    ↓
-step-03-[name].md
-    ↓
-...
-    ↓
-step-N-[final].md (completes workflow)
-```
-
-### Continuation Workflow
-
-```
-workflow.md
-    ↓
-step-01-init.md (detects existing document)
-    ↓
-step-01b-continue.md (analyzes state)
-    ↓
-step-[appropriate-next].md
-```
-
-## Menu System
-
-### Standard Menu Pattern
-
-```
-Display: **Select an Option:** [A] [Action] [P] Party Mode [C] Continue
-
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Save content, update frontmatter, load next step
-```
-
-### Menu Rules
-
-- **Halt Required**: Always wait for user input
-- **Continue Only**: Only proceed with 'C' selection
-- **State Persistence**: Save before loading next step
-- **Loop Back**: Return to menu after other actions
-
-## Collaborative Dialogue Model
-
-### Not Command-Response
-
-- **Facilitator Role**: AI guides, user decides
-- **Equal Partnership**: Both parties contribute
-- **No Assumptions**: Don't assume user wants next step
-- **Explicit Consent**: Always ask for input
-
-### Example Pattern
-
-```
-AI: "Tell me about your dietary preferences."
-User: [provides information]
-AI: "Thank you. Now let's discuss your cooking habits."
-[Continue conversation]
-AI: **Menu Options**
-```
-
-## CSV Intelligence (Optional)
-
-### Data-Driven Behavior
-
-- Configuration in CSV files
-- Dynamic menu options
-- Variable substitution
-- Conditional logic
-
-### Example Structure
-
-```csv
-variable,type,value,description
-cooking_frequency,choice,"daily|weekly|occasionally","How often user cooks"
-meal_type,multi,"breakfast|lunch|dinner|snacks","Types of meals to plan"
-```
-
-## Best Practices
-
-### File Size Limits
-
-- **Step Files**: Keep focused and reasonably sized (5-10KB typical)
-- **Templates**: Keep focused and reusable
-- **Workflow File**: Keep lean, no implementation details
-
-### Sequential Enforcement
-
-- **Numbered Steps**: Use sequential numbering (1, 2, 3...)
-- **No Skipping**: Each step must complete
-- **State Updates**: Mark completion in frontmatter
-
-### Error Prevention
-
-- **Path Variables**: Use frontmatter variables, never hardcode
-- **Complete Loading**: Always read entire file before execution
-- **Menu Halts**: Never proceed without 'C' selection
-
-## Migration from XML
-
-### Advantages
-
-- **No Dependencies**: Pure markdown, no XML parsing
-- **Human Readable**: Files are self-documenting
-- **Git Friendly**: Clean diffs and merges
-- **Flexible**: Easier to modify and extend
-
-### Key Differences
-
-| XML Workflows     | Standalone Workflows    |
-| ----------------- | ----------------------- |
-| Single large file | Multiple micro-files    |
-| Complex structure | Simple sequential steps |
-| Parser required   | Any markdown viewer     |
-| Rigid format      | Flexible organization   |
-
-## Implementation Notes
-
-### Critical Rules
-
-- **NEVER** load multiple step files
-- **ALWAYS** read complete step file first
-- **NEVER** skip steps or optimize
-- **ALWAYS** update frontmatter of the output file when a step is complete
-- **NEVER** proceed without user consent
-
-### Success Metrics
-
-- Documents created correctly
-- All steps completed sequentially
-- User satisfied with collaborative process
-- Clean, maintainable file structure
-
-This architecture ensures disciplined, predictable workflow execution while maintaining flexibility for different use cases.

package/_bmad/bmb/docs/workflows/common-workflow-tools.csv

@@ -1,19 +0,0 @@
-propose,type,tool_name,description,url,requires_install
-always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/_bmad/core/workflows/party-mode/workflow.md,no
-always,workflow,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml,no
-always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/_bmad/core/tasks/brainstorming.xml,no
-always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches, extract relevant data, and incorporate current information into responses when up-to-date information is required beyond training knowledge.",,no
-always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files, facilitating seamless data handling, storage, and document management within user environments.",,no
-always,llm-tool-feature,sub-agents,"Allows LLM to create and manage specialized sub-agents that handle specific tasks or modules within larger workflows, improving efficiency through parallel processing and modular task delegation.",,no
-always,llm-tool-feature,sub-processes,"Enables LLM to initiate and manage subprocesses that operate independently, allowing for parallel processing of complex tasks and improved resource utilization during long-running operations.",,no
-always,tool-memory,sidecar-file,"Creates a persistent history file that gets written during workflow execution and loaded on future runs, enabling continuity through session-to-session state management. Used for agent or workflow initialization with previous session context, learning from past interactions, and maintaining progress across multiple executions.",,no
-example,tool-memory,vector-database,"Stores and retrieves semantic information through embeddings for intelligent memory access, enabling workflows to find relevant past experiences, patterns, or context based on meaning rather than exact matches. Useful for complex learning systems, pattern recognition, and semantic search across workflow history.",https://github.com/modelcontextprotocol/servers/tree/main/src/rag-agent,yes
-example,mcp,context-7,"A curated knowledge base of API documentation and third-party tool references, enabling LLM to access accurate and current information for integration and development tasks when specific technical documentation is needed.",https://github.com/modelcontextprotocol/servers/tree/main/src/context-7,yes
-example,mcp,playwright,"Provides capabilities for LLM to perform web browser automation including navigation, form submission, data extraction, and testing actions on web pages, facilitating automated web interactions and quality assurance.",https://github.com/modelcontextprotocol/servers/tree/main/src/playwright,yes
-example,workflow,security-auditor,"Analyzes workflows and code for security vulnerabilities, compliance issues, and best practices violations, providing detailed security assessments and remediation recommendations for production-ready systems.",,no
-example,task,code-review,"Performs systematic code analysis with peer review perspectives, identifying bugs, performance issues, style violations, and architectural problems through adversarial review techniques.",,no
-example,mcp,git-integration,"Enables direct Git repository operations including commits, branches, merges, and history analysis, allowing workflows to interact with version control systems for code management and collaboration.",https://github.com/modelcontextprotocol/servers/tree/main/src/git,yes
-example,mcp,database-connector,"Provides direct database connectivity for querying, updating, and managing data across multiple database types, enabling workflows to interact with structured data sources and perform data-driven operations.",https://github.com/modelcontextprotocol/servers/tree/main/src/postgres,yes
-example,task,api-testing,"Automated API endpoint testing with request/response validation, authentication handling, and comprehensive reporting for REST, GraphQL, and other API types through systematic test generation.",,no
-example,workflow,deployment-manager,"Orchestrates application deployment across multiple environments with rollback capabilities, health checks, and automated release pipelines for continuous integration and delivery workflows.",,no
-example,task,data-validator,"Validates data quality, schema compliance, and business rules through comprehensive data profiling with detailed reporting and anomaly detection for data-intensive workflows.",,no