siesa-agents 2.1.40 → 2.1.42

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

@@ -1,104 +1,104 @@
-# 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`
+# 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 +1,58 @@
----
-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.
+---
+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 +1,97 @@
-# 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._
+# 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._