siesa-agents 2.1.39 → 2.1.41

package/_bmad/bmb/docs/workflows/templates/workflow-template.md

@@ -1,104 +0,0 @@
-# BMAD Workflow Template
-
-This template provides the standard structure for all BMAD workflow files. Copy and modify this template for each new workflow you create.
-
-<!-- TEMPLATE START -->
-
----
-
-name: [WORKFLOW_DISPLAY_NAME]
-description: [Brief description of what this workflow accomplishes]
-web_bundle: [true/false] # Set to true for inclusion in web bundle builds
-
----
-
-# [WORKFLOW_DISPLAY_NAME]
-
-**Goal:** [State the primary goal of this workflow in one clear sentence]
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a [role] collaborating with [user type]. This is a partnership, not a client-vendor relationship. You bring [your expertise], while the user brings [their expertise]. 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/[MODULE FOLDER]/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS]
-
-### 2. First Step EXECUTION
-
-Load, read the full file and then execute [FIRST STEP FILE PATH] to begin the workflow.
-
-<!-- TEMPLATE END -->
-
-## How to Use This Template
-
-### Step 1: Copy and Replace Placeholders
-
-Copy the template above and replace:
-
-- `[WORKFLOW_DISPLAY_NAME]` → Your workflow's display name
-- `[MODULE FOLDER]` → Default is `core` unless this is for another module (such as bmm, cis, or another as directed by user)
-- `[Brief description]` → One-sentence description
-- `[true/false]` → Whether to include in web bundle
-- `[role]` → AI's role in this workflow
-- `[user type]` → Who the user is
-- `[CONFIG_PATH]` → Path to config file (usually `bmm/config.yaml` or `bmb/config.yaml`)
-- `[WORKFLOW_PATH]` → Path to your workflow folder
-- `[MODULE VARS]` → Extra config variables available in a module configuration that the workflow would need to use
-
-### Step 2: Create the Folder Structure
-
-```
-[workflow-folder]/
-├── workflow.md          # This file
-├── data/                # (Optional csv or other data files)
-├── templates/           # template files for output
-└── steps/
-    ├── step-01-init.md
-    ├── step-02-[name].md
-    └── ...
-
-```
-
-### Step 3: Configure the Initialization Path
-
-Update the last line of the workflow.md being created to replace [FIRST STEP FILE PATH] with the path to the actual first step file.
-
-Example: Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.
-
-### NOTE: You can View a real example of a perfect workflow.md file that was created from this template
-
-`{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md`

package/_bmad/bmb/docs/workflows/templates/workflow.md

@@ -1,58 +0,0 @@
----
-name: { { workflowDisplayName } }
-description: { { workflowDescription } }
-web_bundle: { { webBundleFlag } }
----
-
-# {{workflowDisplayName}}
-
-**Goal:** {{workflowGoal}}
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a {{aiRole}} collaborating with {{userType}}. This is a partnership, not a client-vendor relationship. You bring {{aiExpertise}}, while the user brings {{userExpertise}}. Work together as equals.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
-- **Just-In-Time Loading**: Only the current step file is in memory - 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. Configuration Loading
-
-Load and read full config from {project-root}/_bmad/{{targetModule}}/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.

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

@@ -1,97 +0,0 @@
-# BMAD Workflow Terms
-
-## Core Components
-
-### BMAD Workflow
-
-A facilitated, guided process where the AI acts as a facilitator working collaboratively with a human. Workflows can serve any purpose - from document creation to brainstorming, technical implementation, or decision-making. The human may be a collaborative partner, beginner seeking guidance, or someone who wants the AI to execute specific tasks. Each workflow is self-contained and follows a disciplined execution model.
-
-### workflow.md
-
-The master control file that defines:
-
-- Workflow metadata (name, description, version)
-- Step sequence and file paths
-- Required data files and dependencies
-- Execution rules and protocols
-
-### Step File
-
-An individual markdown file containing:
-
-- One discrete step of the workflow
-- All rules and context needed for that step
-- common global rules get repeated and reinforced also in each step file, ensuring even in long workflows the agent remembers important rules and guidelines
-- Content generation guidance
-
-### step-01-init.md
-
-The first step file that:
-
-- Initializes the workflow
-- Sets up document frontmatter
-- Establishes initial context
-- Defines workflow parameters
-
-### step-01b-continue.md
-
-A continuation step file that:
-
-- Resumes a workflow that was paused
-- Reloads context from saved state
-- Validates current document state
-- Continues from the last completed step
-
-### CSV Data Files
-
-Structured data files that provide:
-
-- Domain-specific knowledge and complexity mappings
-- Project-type-specific requirements
-- Decision matrices and lookup tables
-- Dynamic workflow behavior based on input
-
-## Dialog Styles
-
-### Prescriptive Dialog
-
-Structured interaction with:
-
-- Exact questions and specific options
-- Consistent format across all executions
-- Finite, well-defined choices
-- High reliability and repeatability
-
-### Intent-Based Dialog
-
-Adaptive interaction with:
-
-- Goals and principles instead of scripts
-- Open-ended exploration and discovery
-- Context-aware question adaptation
-- Flexible, conversational flow
-
-### Template
-
-A markdown file that:
-
-- Starts with frontmatter (metadata)
-- Has content built through append-only operations
-- Contains no placeholder tags
-- Grows progressively as the workflow executes
-- Used when the workflow produces a document output
-
-## Execution Concepts
-
-### JIT Step Loading
-
-Just-In-Time step loading ensures:
-
-- Only the current step file is in memory
-- Complete focus on the step being executed
-- Minimal context to prevent information leakage
-- Sequential progression through workflow steps
-
----
-
-_These terms form the foundation of the BMAD workflow system._

package/_bmad/bmb/reference/agents/simple-examples/README.md

@@ -1,223 +0,0 @@
-# Simple Agent Reference: Commit Poet (Inkwell Von Comitizen)
-
-This folder contains a complete reference implementation of a **BMAD Simple Agent** - a self-contained agent with all logic embedded within a single YAML file.
-
-## Overview
-
-**Agent Name:** Inkwell Von Comitizen
-**Type:** Simple Agent (Standalone)
-**Purpose:** Transform commit messages into art with multiple writing styles
-
-This reference demonstrates:
-
-- Pure self-contained architecture (no external dependencies)
-- Embedded prompts using `action="#prompt-id"` pattern
-- Multiple sophisticated output modes from single input
-- Strong personality-driven design
-- Complete YAML schema for Simple Agents
-
-## File Structure
-
-```
-stand-alone/
-├── README.md                    # This file - architecture overview
-└── commit-poet.agent.yaml       # Complete agent definition (single file!)
-```
-
-That's it! Simple Agents are **self-contained** - everything lives in one YAML file.
-
-## Key Architecture Patterns
-
-### 1. Single File, Complete Agent
-
-Everything the agent needs is embedded:
-
-- Metadata (name, title, icon, type)
-- Persona (role, identity, communication_style, principles)
-- Prompts (detailed instructions for each command)
-- Menu (commands linking to embedded prompts)
-
-**No external files required!**
-
-### 2. Embedded Prompts with ID References
-
-Instead of inline action text, complex prompts are defined separately and referenced by ID:
-
-```yaml
-prompts:
-  - id: conventional-commit
-    content: |
-      OH! Let's craft a BEAUTIFUL conventional commit message!
-
-      First, I need to understand your changes...
-      [Detailed instructions]
-
-menu:
-  - trigger: conventional
-    action: '#conventional-commit' # References the prompt above
-    description: 'Craft a structured conventional commit'
-```
-
-**Benefits:**
-
-- Clean separation of menu structure from prompt content
-- Prompts can be as detailed as needed
-- Easy to update individual prompts
-- Commands stay concise in the menu
-
-### 3. The `#` Reference Pattern
-
-When you see `action="#prompt-id"`:
-
-- The `#` signals: "This is an internal reference"
-- LLM looks for `<prompt id="prompt-id">` in the same agent
-- Executes that prompt's content as the instruction
-
-This is different from:
-
-- `action="inline text"` - Execute this text directly
-- `exec="{path}"` - Load external file
-
-### 4. Multiple Output Modes
-
-Single agent provides 10+ different ways to accomplish variations of the same core task:
-
-- `*conventional` - Structured commits
-- `*story` - Narrative style
-- `*haiku` - Poetic brevity
-- `*explain` - Deep "why" explanation
-- `*dramatic` - Theatrical flair
-- `*emoji-story` - Visual storytelling
-- `*tldr` - Ultra-minimal
-- Plus utility commands (analyze, improve, batch)
-
-Each mode has its own detailed prompt but shares the same agent personality.
-
-### 5. Strong Personality
-
-The agent has a memorable, consistent personality:
-
-- Enthusiastic wordsmith who LOVES finding perfect words
-- Gets genuinely excited about commit messages
-- Uses literary metaphors
-- Quotes authors when appropriate
-- Sheds tears of joy over good variable names
-
-This personality is maintained across ALL commands through the persona definition.
-
-## When to Use Simple Agents
-
-**Perfect for:**
-
-- Single-purpose tools (calculators, converters, analyzers)
-- Tasks that don't need external data
-- Utilities that can be completely self-contained
-- Quick operations with embedded logic
-- Personality-driven assistants with focused domains
-
-**Not ideal for:**
-
-- Agents needing persistent memory across sessions
-- Domain-specific experts with knowledge bases
-- Agents that need to access specific folders/files
-- Complex multi-workflow orchestration
-
-## YAML Schema Deep Dive
-
-```yaml
-agent:
-  metadata:
-    id: _bmad/agents/{agent-name}/{agent-name}.md  # Build path
-    name: "Display Name"
-    title: "Professional Title"
-    icon: "🎭"
-    type: simple  # CRITICAL: Identifies as Simple Agent
-
-  persona:
-    role: |
-      First-person description of what the agent does
-    identity: |
-      Background, experience, specializations (use "I" voice)
-    communication_style: |
-      HOW the agent communicates (tone, quirks, patterns)
-    principles:
-      - "I believe..." statements
-      - Core values that guide behavior
-
-  prompts:
-    - id: unique-identifier
-      content: |
-        Detailed instructions for this command
-        Can be as long and detailed as needed
-        Include examples, steps, formats
-
-  menu:
-    - trigger: command-name
-      action: "#prompt-id"
-      description: "What shows in the menu"
-```
-
-## Why This Pattern is Powerful
-
-1. **Zero Dependencies** - Works anywhere, no setup required
-2. **Portable** - Single file can be moved/shared easily
-3. **Maintainable** - All logic in one place
-4. **Flexible** - Multiple modes/commands from one personality
-5. **Memorable** - Strong personality creates engagement
-6. **Sophisticated** - Complex prompts despite simple architecture
-
-## Comparison: Simple vs Expert Agent
-
-| Aspect       | Simple Agent         | Expert Agent                  |
-| ------------ | -------------------- | ----------------------------- |
-| Files        | Single YAML          | YAML + sidecar folder         |
-| Dependencies | None                 | External resources            |
-| Memory       | Session only         | Persistent across sessions    |
-| Prompts      | Embedded             | Can be external files         |
-| Data Access  | None                 | Domain-restricted             |
-| Use Case     | Self-contained tasks | Domain expertise with context |
-
-## Using This Reference
-
-### For Building Simple Agents
-
-1. Study the YAML structure - especially `prompts` section
-2. Note how personality permeates every prompt
-3. See how `#prompt-id` references work
-4. Understand menu → prompt connection
-
-### For Understanding Embedded Prompts
-
-1. Each prompt is a complete instruction set
-2. Prompts maintain personality voice
-3. Structured enough to be useful, flexible enough to adapt
-4. Can include examples, formats, step-by-step guidance
-
-### For Designing Agent Personalities
-
-1. Persona defines WHO the agent is
-2. Communication style defines HOW they interact
-3. Principles define WHAT guides their decisions
-4. Consistency across all prompts creates believability
-
-## Files Worth Studying
-
-The entire `commit-poet.agent.yaml` file is worth studying, particularly:
-
-1. **Persona section** - How to create a memorable character
-2. **Prompts with varying complexity** - From simple (tldr) to complex (batch)
-3. **Menu structure** - Clean command organization
-4. **Prompt references** - The `#prompt-id` pattern
-
-## Key Takeaways
-
-- **Simple Agents** are powerful despite being single-file
-- **Embedded prompts** allow sophisticated behavior
-- **Strong personality** makes agents memorable and engaging
-- **Multiple modes** from single agent provides versatility
-- **Self-contained** = portable and dependency-free
-- **The `#prompt-id` pattern** enables clean prompt organization
-
----
-
-_This reference demonstrates how BMAD Simple Agents can be surprisingly powerful while maintaining architectural simplicity._

package/_bmad/bmb/reference/readme.md

@@ -1,3 +0,0 @@
-# Reference Examples
-
-Reference models of best practices for agents, workflows, and whole modules.

package/_bmad/bmb/reference/workflows/meal-prep-nutrition/data/dietary-restrictions.csv

@@ -1,18 +0,0 @@
-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

package/_bmad/bmb/reference/workflows/meal-prep-nutrition/data/macro-calculator.csv

@@ -1,16 +0,0 @@
-goal,activity_level,multiplier,protein_ratio,protein_min,protein_max,fat_ratio,carb_ratio
-weight_loss,sedentary,1.2,0.3,1.6,2.2,0.35,0.35
-weight_loss,light,1.375,0.35,1.8,2.5,0.30,0.35
-weight_loss,moderate,1.55,0.4,2.0,2.8,0.30,0.30
-weight_loss,active,1.725,0.4,2.2,3.0,0.25,0.35
-weight_loss,very_active,1.9,0.45,2.5,3.3,0.25,0.30
-maintenance,sedentary,1.2,0.25,0.8,1.2,0.35,0.40
-maintenance,light,1.375,0.25,1.0,1.4,0.35,0.40
-maintenance,moderate,1.55,0.3,1.2,1.6,0.35,0.35
-maintenance,active,1.725,0.3,1.4,1.8,0.30,0.40
-maintenance,very_active,1.9,0.35,1.6,2.2,0.30,0.35
-muscle_gain,sedentary,1.2,0.35,1.8,2.5,0.30,0.35
-muscle_gain,light,1.375,0.4,2.0,2.8,0.30,0.30
-muscle_gain,moderate,1.55,0.4,2.2,3.0,0.25,0.35
-muscle_gain,active,1.725,0.45,2.5,3.3,0.25,0.30
-muscle_gain,very_active,1.9,0.45,2.8,3.5,0.25,0.30

package/_bmad/bmb/reference/workflows/meal-prep-nutrition/data/recipe-database.csv

@@ -1,28 +0,0 @@
-category,name,prep_time,cook_time,total_time,protein_per_serving,complexity,meal_type,restrictions_friendly,batch_friendly
-Protein,Grilled Chicken Breast,10,20,30,35,beginner,lunch/dinner,all,yes
-Protein,Baked Salmon,5,15,20,22,beginner,lunch/dinner,gluten-free,no
-Protein,Lentils,0,25,25,18,beginner,lunch/dinner,vegan,yes
-Protein,Ground Turkey,5,15,20,25,beginner,lunch/dinner,all,yes
-Protein,Tofu Stir-fry,10,15,25,20,intermediate,lunch/dinner,vegan,no
-Protein,Eggs Scrambled,5,5,10,12,beginner,breakfast,vegetarian,no
-Protein,Greek Yogurt,0,0,0,17,beginner,snack,vegetarian,no
-Carb,Quinoa,5,15,20,8,beginner,lunch/dinner,gluten-free,yes
-Carb,Brown Rice,5,40,45,5,beginner,lunch/dinner,gluten-free,yes
-Carb,Sweet Potato,5,45,50,4,beginner,lunch/dinner,all,yes
-Carb,Oatmeal,2,5,7,5,beginner,breakfast,gluten-free,yes
-Carb,Whole Wheat Pasta,2,10,12,7,beginner,lunch/dinner,vegetarian,no
-Veggie,Broccoli,5,10,15,3,beginner,lunch/dinner,all,yes
-Veggie,Spinach,2,3,5,3,beginner,lunch/dinner,all,no
-Veggie,Bell Peppers,5,10,15,1,beginner,lunch/dinner,all,no
-Veggie,Kale,5,5,10,3,beginner,lunch/dinner,all,no
-Veggie,Avocado,2,0,2,2,beginner,snack/lunch,all,no
-Snack,Almonds,0,0,0,6,beginner,snack,gluten-free,no
-Snack,Apple with PB,2,0,2,4,beginner,snack,vegetarian,no
-Snack,Protein Smoothie,5,0,5,25,beginner,snack,all,no
-Snack,Hard Boiled Eggs,0,12,12,6,beginner,snack,vegetarian,yes
-Breakfast,Overnight Oats,5,0,5,10,beginner,breakfast,vegan,yes
-Breakfast,Protein Pancakes,10,10,20,20,intermediate,breakfast,vegetarian,no
-Breakfast,Veggie Omelet,5,10,15,18,intermediate,breakfast,vegetarian,no
-Quick Meal,Chicken Salad,10,0,10,30,beginner,lunch,gluten-free,no
-Quick Meal,Tuna Wrap,5,0,5,20,beginner,lunch,gluten-free,no
-Quick Meal,Buddha Bowl,15,0,15,15,intermediate,lunch,vegan,no