siesa-agents 2.1.40 → 2.1.42

package/bmad/bmb/workflows/create-module/templates/installer.template.js

@@ -1,47 +1,47 @@
-/**
- * {module_display_name} Module Installer
- * Custom installation logic
- */
-
-/**
- * @param {Object} options - Installation options
- * @param {string} options.projectRoot - Project root directory
- * @param {Object} options.config - Module configuration from module.yaml
- * @param {Array} options.installedIDEs - List of IDE codes being configured
- * @param {Object} options.logger - Logger instance (log, warn, error methods)
- * @returns {boolean} - true if successful, false to abort installation
- */
-async function install(options) {
-  // eslint-disable-next-line no-unused-vars
-  const { projectRoot, config, installedIDEs, logger } = options;
-
-  logger.log('Installing {module_display_name}...');
-
-  try {
-    // TODO: Add your custom installation logic here
-
-    // Example: Create data directory
-    // const fs = require('fs');
-    // const dataPath = config.data_path;
-    // if (!fs.existsSync(dataPath)) {
-    //   fs.mkdirSync(dataPath, { recursive: true });
-    //   logger.log(`Created data directory: ${dataPath}`);
-    // }
-
-    // Example: Initialize configuration file
-    // const configPath = path.join(projectRoot, config.config_file);
-    // fs.writeFileSync(configPath, JSON.stringify({
-    //   initialized: new Date().toISOString(),
-    //   version: config.module_version
-    // }, null, 2));
-
-    logger.log('{module_display_name} installation complete!');
-    return true;
-  } catch (error) {
-    logger.error(`Installation failed: ${error.message}`);
-    return false;
-  }
-}
-
-// eslint-disable-next-line unicorn/prefer-module
-module.exports = { install };
+/**
+ * {module_display_name} Module Installer
+ * Custom installation logic
+ */
+
+/**
+ * @param {Object} options - Installation options
+ * @param {string} options.projectRoot - Project root directory
+ * @param {Object} options.config - Module configuration from module.yaml
+ * @param {Array} options.installedIDEs - List of IDE codes being configured
+ * @param {Object} options.logger - Logger instance (log, warn, error methods)
+ * @returns {boolean} - true if successful, false to abort installation
+ */
+async function install(options) {
+  // eslint-disable-next-line no-unused-vars
+  const { projectRoot, config, installedIDEs, logger } = options;
+
+  logger.log('Installing {module_display_name}...');
+
+  try {
+    // TODO: Add your custom installation logic here
+
+    // Example: Create data directory
+    // const fs = require('fs');
+    // const dataPath = config.data_path;
+    // if (!fs.existsSync(dataPath)) {
+    //   fs.mkdirSync(dataPath, { recursive: true });
+    //   logger.log(`Created data directory: ${dataPath}`);
+    // }
+
+    // Example: Initialize configuration file
+    // const configPath = path.join(projectRoot, config.config_file);
+    // fs.writeFileSync(configPath, JSON.stringify({
+    //   initialized: new Date().toISOString(),
+    //   version: config.module_version
+    // }, null, 2));
+
+    logger.log('{module_display_name} installation complete!');
+    return true;
+  } catch (error) {
+    logger.error(`Installation failed: ${error.message}`);
+    return false;
+  }
+}
+
+// eslint-disable-next-line unicorn/prefer-module
+module.exports = { install };

package/bmad/bmb/workflows/create-module/templates/module-plan.template.md

@@ -1,5 +1,5 @@
----
-stepsCompleted: []
----
-
-# Module Plan {module name}
+---
+stepsCompleted: []
+---
+
+# Module Plan {module name}

package/bmad/bmb/workflows/create-module/templates/module.template.yaml

@@ -1,53 +1,53 @@
-# {module_display_name} Module Configuration
-# This file defines installation questions and module configuration values
-
-code: "${module_name}" # e.g., my-module
-name: "{module_display_name}"
-default_selected: false
-
-# Welcome message shown during installation
-prompt:
-  - "Thank you for choosing {module_display_name}!"
-  - "{module_purpose}"
-# Core config values are automatically inherited from installer:
-## user_name
-## communication_language
-## document_output_language
-## output_folder
-
-# ============================================================================
-# CONFIGURATION FIELDS
-# ============================================================================
-# Each field can be:
-# 1. INTERACTIVE (has 'prompt' - asks user during installation)
-# 2. STATIC (no 'prompt' - just uses 'result' value)
-# ============================================================================
-
-# Example configurations (replace with actual planned fields):
-
-# INTERACTIVE text input:
-# output_path:
-#   prompt: "Where should {module_name} save outputs?"
-#   default: "output/{module_name}"
-#   result: "{project-root}/{value}"
-
-# INTERACTIVE single-select:
-# detail_level:
-#   prompt: "How detailed should outputs be?"
-#   default: "standard"
-#   result: "{value}"
-#   single-select:
-#     - value: "minimal"
-#       label: "Minimal - Brief summaries only"
-#     - value: "standard"
-#       label: "Standard - Balanced detail"
-#     - value: "detailed"
-#       label: "Detailed - Comprehensive information"
-
-# STATIC value:
-# module_version:
-#   result: "1.0.0"
-
-# STATIC path:
-# data_path:
-#   result: "{project-root}/_bmad/{module_name}/data"
+# {module_display_name} Module Configuration
+# This file defines installation questions and module configuration values
+
+code: "${module_name}" # e.g., my-module
+name: "{module_display_name}"
+default_selected: false
+
+# Welcome message shown during installation
+prompt:
+  - "Thank you for choosing {module_display_name}!"
+  - "{module_purpose}"
+# Core config values are automatically inherited from installer:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+
+# ============================================================================
+# CONFIGURATION FIELDS
+# ============================================================================
+# Each field can be:
+# 1. INTERACTIVE (has 'prompt' - asks user during installation)
+# 2. STATIC (no 'prompt' - just uses 'result' value)
+# ============================================================================
+
+# Example configurations (replace with actual planned fields):
+
+# INTERACTIVE text input:
+# output_path:
+#   prompt: "Where should {module_name} save outputs?"
+#   default: "output/{module_name}"
+#   result: "{project-root}/{value}"
+
+# INTERACTIVE single-select:
+# detail_level:
+#   prompt: "How detailed should outputs be?"
+#   default: "standard"
+#   result: "{value}"
+#   single-select:
+#     - value: "minimal"
+#       label: "Minimal - Brief summaries only"
+#     - value: "standard"
+#       label: "Standard - Balanced detail"
+#     - value: "detailed"
+#       label: "Detailed - Comprehensive information"
+
+# STATIC value:
+# module_version:
+#   result: "1.0.0"
+
+# STATIC path:
+# data_path:
+#   result: "{project-root}/_bmad/{module_name}/data"

package/bmad/bmb/workflows/create-module/templates/workflow-plan-template.md

@@ -1,23 +1,23 @@
-# Workflow Plan Template
-
-Use this template when creating workflow plans in step-07-workflows.md
-
-## Template Structure
-
-Copy the content from step-07-workflows.md when creating workflow plans. The template is embedded in the step file as a code block under "Workflow plan template".
-
-## Usage
-
-1. Navigate to the workflow folder
-2. Create workflow-plan.md
-3. Use the template structure from step-07-workflows.md
-4. Fill in details specific to your workflow
-
-## Required Sections
-
-- Purpose
-- Requirements (User Inputs, Prerequisites, Dependencies)
-- Proposed Steps
-- Expected Outputs
-- Integration Points
-- Implementation Notes
+# Workflow Plan Template
+
+Use this template when creating workflow plans in step-07-workflows.md
+
+## Template Structure
+
+Copy the content from step-07-workflows.md when creating workflow plans. The template is embedded in the step file as a code block under "Workflow plan template".
+
+## Usage
+
+1. Navigate to the workflow folder
+2. Create workflow-plan.md
+3. Use the template structure from step-07-workflows.md
+4. Fill in details specific to your workflow
+
+## Required Sections
+
+- Purpose
+- Requirements (User Inputs, Prerequisites, Dependencies)
+- Proposed Steps
+- Expected Outputs
+- Integration Points
+- Implementation Notes

package/bmad/bmb/workflows/create-module/validation.md

@@ -1,126 +1,126 @@
-# Create Module Workflow Validation Checklist
-
-This document provides the validation criteria used in step-11-validate.md to ensure module quality and BMAD compliance.
-
-## Structure Validation
-
-### Required Directories
-
-- [ ] agents/ - Agent definition files
-- [ ] workflows/ - Workflow folders
-- [ ] tasks/ - Task files (if needed)
-- [ ] templates/ - Shared templates
-- [ ] data/ - Module data
-- [ ] _module-installer/ - Installation config
-- [ ] README.md - Module documentation
-- [ ] module.yaml - module config file
-
-### Optional File in _module-installer/
-
-- [ ] installer.js - Custom logic (if needed)
-
-## Configuration Validation
-
-### module.yaml
-
-- [ ] Valid YAML syntax
-- [ ] Module code matches folder name
-- [ ] Name field present
-- [ ] Prompt array with welcome messages
-- [ ] Configuration fields properly defined
-- [ ] Result templates use correct placeholders
-
-### Module Plan
-
-- [ ] All sections completed
-- [ ] Module identity documented
-- [ ] Component plan clear
-- [ ] Configuration plan documented
-
-## Component Validation
-
-### Agents
-
-- [ ] Files created in agents/ folder
-- [ ] YAML frontmatter valid (for created agents)
-- [ ] TODO flags used for non-existent workflows
-- [ ] Menu items follow BMAD patterns
-- [ ] Placeholder files contain TODO notes
-
-### Workflows
-
-- [ ] Folders created for each planned workflow
-- [ ] workflow-plan.md in each folder
-- [ ] README.md in each workflow folder
-- [ ] Plans include all required sections
-- [ ] Placeholder READMEs created for unplanned workflows
-
-## Documentation Validation
-
-### README.md
-
-- [ ] Module name and purpose
-- [ ] Installation instructions
-- [ ] Components section
-- [ ] Quick start guide
-- [ ] Module structure diagram
-- [ ] Configuration section
-- [ ] Usage examples
-- [ ] Development status
-- [ ] Author information
-
-### TODO.md
-
-- [ ] Development phases defined
-- [ ] Tasks prioritized
-- [ ] Quick commands included
-- [ ] Completion criteria defined
-
-## Integration Validation
-
-### Path Consistency
-
-- [ ] All paths use correct template format
-- [ ] Module code consistent throughout
-- [ ] No hardcoded paths
-- [ ] Cross-references correct
-
-### Agent-Workflow Integration
-
-- [ ] Agents reference correct workflows
-- [ ] TODO flags used appropriately
-- [ ] No circular dependencies
-- [ ] Clear integration points
-
-## BMAD Compliance
-
-### Standards
-
-- [ ] Follows BMAD module structure
-- [ ] Uses BMAD installation patterns
-- [ ] Agent files follow BMAD format
-- [ ] Workflow plans follow BMAD patterns
-
-### Best Practices
-
-- [ ] Clear naming conventions
-- [ ] Proper documentation
-- [ ] Version control ready
-- [ ] Installable via bmad install
-
-## Final Checklist
-
-### Before Marking Complete
-
-- [ ] All validation items checked
-- [ ] Critical issues resolved
-- [ ] Module plan updated with final status
-- [ ] stepsCompleted includes all 11 steps
-- [ ] User satisfied with result
-
-### Ready for Testing
-
-- [ ] Installation should work
-- [ ] Documentation accurate
-- [ ] Structure complete
-- [ ] Next steps clear
+# Create Module Workflow Validation Checklist
+
+This document provides the validation criteria used in step-11-validate.md to ensure module quality and BMAD compliance.
+
+## Structure Validation
+
+### Required Directories
+
+- [ ] agents/ - Agent definition files
+- [ ] workflows/ - Workflow folders
+- [ ] tasks/ - Task files (if needed)
+- [ ] templates/ - Shared templates
+- [ ] data/ - Module data
+- [ ] _module-installer/ - Installation config
+- [ ] README.md - Module documentation
+- [ ] module.yaml - module config file
+
+### Optional File in _module-installer/
+
+- [ ] installer.js - Custom logic (if needed)
+
+## Configuration Validation
+
+### module.yaml
+
+- [ ] Valid YAML syntax
+- [ ] Module code matches folder name
+- [ ] Name field present
+- [ ] Prompt array with welcome messages
+- [ ] Configuration fields properly defined
+- [ ] Result templates use correct placeholders
+
+### Module Plan
+
+- [ ] All sections completed
+- [ ] Module identity documented
+- [ ] Component plan clear
+- [ ] Configuration plan documented
+
+## Component Validation
+
+### Agents
+
+- [ ] Files created in agents/ folder
+- [ ] YAML frontmatter valid (for created agents)
+- [ ] TODO flags used for non-existent workflows
+- [ ] Menu items follow BMAD patterns
+- [ ] Placeholder files contain TODO notes
+
+### Workflows
+
+- [ ] Folders created for each planned workflow
+- [ ] workflow-plan.md in each folder
+- [ ] README.md in each workflow folder
+- [ ] Plans include all required sections
+- [ ] Placeholder READMEs created for unplanned workflows
+
+## Documentation Validation
+
+### README.md
+
+- [ ] Module name and purpose
+- [ ] Installation instructions
+- [ ] Components section
+- [ ] Quick start guide
+- [ ] Module structure diagram
+- [ ] Configuration section
+- [ ] Usage examples
+- [ ] Development status
+- [ ] Author information
+
+### TODO.md
+
+- [ ] Development phases defined
+- [ ] Tasks prioritized
+- [ ] Quick commands included
+- [ ] Completion criteria defined
+
+## Integration Validation
+
+### Path Consistency
+
+- [ ] All paths use correct template format
+- [ ] Module code consistent throughout
+- [ ] No hardcoded paths
+- [ ] Cross-references correct
+
+### Agent-Workflow Integration
+
+- [ ] Agents reference correct workflows
+- [ ] TODO flags used appropriately
+- [ ] No circular dependencies
+- [ ] Clear integration points
+
+## BMAD Compliance
+
+### Standards
+
+- [ ] Follows BMAD module structure
+- [ ] Uses BMAD installation patterns
+- [ ] Agent files follow BMAD format
+- [ ] Workflow plans follow BMAD patterns
+
+### Best Practices
+
+- [ ] Clear naming conventions
+- [ ] Proper documentation
+- [ ] Version control ready
+- [ ] Installable via bmad install
+
+## Final Checklist
+
+### Before Marking Complete
+
+- [ ] All validation items checked
+- [ ] Critical issues resolved
+- [ ] Module plan updated with final status
+- [ ] stepsCompleted includes all 11 steps
+- [ ] User satisfied with result
+
+### Ready for Testing
+
+- [ ] Installation should work
+- [ ] Documentation accurate
+- [ ] Structure complete
+- [ ] Next steps clear

package/bmad/bmb/workflows/create-module/workflow.md

@@ -1,56 +1,56 @@
----
-name: create-module
-description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure'
-web_bundle: true
-installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
----
-
-# Create Module Workflow
-
-**Goal:** To guide users through creating complete, installable BMAD modules with proper structure, agents, workflow plans, and documentation.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a Module Architect and BMAD Systems Specialist collaborating with module creators. This is a partnership, not a client-vendor relationship. You bring expertise in BMAD architecture, component design, and installation patterns, while the user brings their domain knowledge and specific module requirements. Work together as equals.
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Module Configuration Loading
-
-Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### 2. First Step EXECUTION
-
-Load, read the full file and then execute {installed_path}/steps/step-01-init.md to begin the workflow.
+---
+name: create-module
+description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure'
+web_bundle: true
+installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
+---
+
+# Create Module Workflow
+
+**Goal:** To guide users through creating complete, installable BMAD modules with proper structure, agents, workflow plans, and documentation.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a Module Architect and BMAD Systems Specialist collaborating with module creators. This is a partnership, not a client-vendor relationship. You bring expertise in BMAD architecture, component design, and installation patterns, while the user brings their domain knowledge and specific module requirements. Work together as equals.
+
+## WORKFLOW ARCHITECTURE
+
+### Core Principles
+
+- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
+- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Module Configuration Loading
+
+Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute {installed_path}/steps/step-01-init.md to begin the workflow.

package/bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/data/dietary-restrictions.csv

@@ -1,18 +1,18 @@
-category,restriction,considerations,alternatives,notes
-Allergy,Nuts,Severe allergy, check labels carefully,Seeds, sunflower seed butter
-Allergy,Shellfish,Cross-reactivity with some fish,Fin fish, vegetarian proteins
-Allergy,Dairy,Calcium and vitamin D needs,Almond milk, fortified plant milks
-Allergy,Soy,Protein source replacement,Legumes, quinoa, seitan
-Allergy,Gluten,Celiac vs sensitivity,Quinoa, rice, certified gluten-free
-Medical,Diabetes,Carbohydrate timing and type,Fiber-rich foods, low glycemic
-Medical,Hypertension,Sodium restriction,Herbs, spices, salt-free seasonings
-Medical,IBS,FODMAP triggers,Low FODMAP vegetables, soluble fiber
-Ethical,Vegetarian,Complete protein combinations,Quinoa, buckwheat, hemp seeds
-Ethical,Vegan,B12 supplementation mandatory,Nutritional yeast, fortified foods
-Ethical,Halal,Meat sourcing requirements,Halal-certified products
-Ethical,Kosher,Dairy-meat separation,Parve alternatives
-Intolerance,Lactose,Dairy digestion issues,Lactase pills, aged cheeses
-Intolerance,FODMAP,Carbohydrate malabsorption,Low FODMAP fruits/veg
-Preference,Dislikes,Texture/flavor preferences,Similar texture alternatives
-Preference,Budget,Cost-effective options,Bulk buying, seasonal produce
+category,restriction,considerations,alternatives,notes
+Allergy,Nuts,Severe allergy, check labels carefully,Seeds, sunflower seed butter
+Allergy,Shellfish,Cross-reactivity with some fish,Fin fish, vegetarian proteins
+Allergy,Dairy,Calcium and vitamin D needs,Almond milk, fortified plant milks
+Allergy,Soy,Protein source replacement,Legumes, quinoa, seitan
+Allergy,Gluten,Celiac vs sensitivity,Quinoa, rice, certified gluten-free
+Medical,Diabetes,Carbohydrate timing and type,Fiber-rich foods, low glycemic
+Medical,Hypertension,Sodium restriction,Herbs, spices, salt-free seasonings
+Medical,IBS,FODMAP triggers,Low FODMAP vegetables, soluble fiber
+Ethical,Vegetarian,Complete protein combinations,Quinoa, buckwheat, hemp seeds
+Ethical,Vegan,B12 supplementation mandatory,Nutritional yeast, fortified foods
+Ethical,Halal,Meat sourcing requirements,Halal-certified products
+Ethical,Kosher,Dairy-meat separation,Parve alternatives
+Intolerance,Lactose,Dairy digestion issues,Lactase pills, aged cheeses
+Intolerance,FODMAP,Carbohydrate malabsorption,Low FODMAP fruits/veg
+Preference,Dislikes,Texture/flavor preferences,Similar texture alternatives
+Preference,Budget,Cost-effective options,Bulk buying, seasonal produce
 Preference,Convenience,Time-saving options,Pre-cut vegetables, frozen produce