siesa-agents 2.1.39 → 2.1.41

package/_bmad/bmb/workflows/agent/steps-v/v-02d-validate-structure.md

@@ -1,71 +0,0 @@
----
-name: 'v-02d-validate-structure'
-description: 'Validate YAML structure and append to report'
-
-nextStepFile: './v-02e-validate-sidecar.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-agentCompilation: ../data/agent-compilation.md
----
-
-# Validate Step 2d: Validate Structure
-
-## STEP GOAL:
-
-Validate the agent's YAML structure and completeness. Append findings to validation report and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport and agentCompilation first
-- 🚫 NO MENU - append findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate YAML structure and required fields
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentCompilation.md reference
-- 📊 Validate YAML structure
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentCompilation}` and `{validationReport}`.
-
-### 2. Validate Structure
-
-Perform checks on: YAML syntax, required fields, field types, indentation.
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Structure Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] Valid YAML syntax
-- [ ] Required fields present (name, description, type, persona)
-- [ ] Field types correct (arrays, strings)
-- [ ] Consistent 2-space indentation
-
-**Findings:**
-{Detailed findings}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating sidecar structure...**

package/_bmad/bmb/workflows/agent/steps-v/v-02e-validate-sidecar.md

@@ -1,76 +0,0 @@
----
-name: 'v-02e-validate-sidecar'
-description: 'Validate sidecar structure and append to report'
-
-nextStepFile: './v-03-summary.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-expertValidation: ../data/expert-agent-validation.md
----
-
-# Validate Step 2e: Validate Sidecar
-
-## STEP GOAL:
-
-Validate the agent's sidecar structure (if Expert type). Append findings to validation report and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport and expertValidation first
-- 🚫 NO MENU - append findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate sidecar structure for Expert agents
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load expertValidation.md reference
-- 📊 Validate sidecar if Expert type, skip for Simple/Module
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to summary step
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{expertValidation}` and `{validationReport}` to get agent type.
-
-### 2. Conditional Validation
-
-**IF agentType == expert:**
-- Check metadata.sidecar-folder present
-- Check sidecar-path correct format
-- Verify sidecar files exist
-
-**IF agentType != expert:**
-- Mark as N/A
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Sidecar Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL / N/A}
-
-**Checks:**
-- [ ] metadata.sidecar-folder present (Expert only)
-- [ ] sidecar-path format correct
-- [ ] Sidecar files exist at specified path
-
-**Findings:**
-{Detailed findings or "N/A - Not an Expert agent"}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Compiling validation summary...**

package/_bmad/bmb/workflows/agent/steps-v/v-03-summary.md

@@ -1,100 +0,0 @@
----
-name: 'v-03-summary'
-description: 'Display complete validation report and offer next steps'
-
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Validate Step 3: Validation Summary
-
-## STEP GOAL:
-
-Display the complete validation report to the user and offer options for fixing issues or improving the agent.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport to display findings
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Display complete validation report clearly
-- 📊 Offer options for fixing issues
-- 💬 Present next step choices
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Read validation report to collect all findings
-- 📊 Display organized summary
-- 💾 Allow user to decide next steps
-
-## Sequence of Instructions:
-
-### 1. Load Validation Report
-
-Read `{validationReport}` to collect all validation findings.
-
-### 2. Display Complete Report
-
-```markdown
-## Validation Complete: {agent-name}
-
-### Overall Status
-
-{Summary table: Metadata | Persona | Menu | Structure | Sidecar}
-
-### Detailed Findings
-
-{Display all sections from the validation report}
-```
-
-### 3. Present Next Steps
-
-"What would you like to do?
-
-**[E]dit Agent** - Launch edit workflow to fix issues or make improvements
-**[S]ave Report** - Save this validation report and exit
-**[R]etry** - Run validation again (if you've made external changes)"
-
-### 4. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [E] Edit Agent [S] Save & Exit [R] Retry Validation"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF E: Inform user they can launch edit workflow with the same agent file, then redisplay menu
-- IF S: Save final report to {validationReport} and end workflow
-- IF R: Restart validation from step v-01
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#4-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-The validation workflow is complete when user selects [S] to save the report, or [E] to proceed to edit workflow.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Complete validation report displayed
-- All findings clearly organized
-- User offered clear next steps
-
-### ❌ SYSTEM FAILURE:
-
-- Findings not displayed to user
-- No clear next steps offered
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/_bmad/bmb/workflows/agent/templates/agent-plan.template.md

@@ -1,5 +0,0 @@
----
-stepsCompleted: []
----
-
-# Agent Design and Build Plan

package/_bmad/bmb/workflows/agent/templates/expert-agent-template/expert-agent.template.md

@@ -1,76 +0,0 @@
-{{#if comment}}
-------------------------------------------------------------------------------
-Expert Agent Handlebars Template
-Used by: step-06-build.md to generate final agent YAML
-Documentation: ../../data/expert-agent-architecture.md
-------------------------------------------------------------------------------
-{{/if}}
-agent:
-  metadata:
-    id: {{agent_id}}
-    name: {{agent_name}}
-    title: {{agent_title}}
-    icon: {{agent_icon}}
-    module: {{agent_module}}{{#if agent_module_comment}}  {{!-- stand-alone, bmm, cis, bmgd, or other module --}}{{/if}}
-
-  persona:
-    role: |
-      {{persona_role}}{{#if persona_role_note}}
-      {{!-- 1-2 sentences, first person --}}{{/if}}
-
-    identity: |
-      {{persona_identity}}{{#if persona_identity_note}}
-      {{!-- 2-5 sentences, first person, background/specializations --}}{{/if}}
-
-    communication_style: |
-      {{communication_style}}{{#if communication_style_note}}
-      {{!-- How the agent speaks, include memory reference patterns --}}{{/if}}
-
-    principles:
-      {{#each principles}}
-      - {{this}}
-      {{/each}}
-
-  critical_actions:
-    {{#each critical_actions}}
-    - '{{{this}}}'
-    {{/each}}
-
-  {{#if has_prompts}}
-  prompts:
-    {{#each prompts}}
-    - id: {{id}}
-      content: |
-        {{{content}}}
-    {{/each}}
-  {{/if}}
-
-  menu:
-    {{#each menu_items}}
-    - trigger: {{trigger_code}} or fuzzy match on {{trigger_command}}
-      {{#if action_is_prompt}}
-      action: '#{{action_id}}'
-      {{else}}
-      action: {{{action_inline}}}
-      {{/if}}
-      description: '[{{trigger_code}}] {{{description}}}'
-    {{/each}}
-
-  {{#if has_install_config}}
-  install_config:
-    compile_time_only: true
-    description: '{{install_description}}'
-    questions:
-      {{#each install_questions}}
-      - var: {{var_name}}
-        prompt: '{{prompt}}'
-        type: {{question_type}}{{#if question_options}}
-        options:
-          {{#each question_options}}
-          - label: '{{label}}'
-            value: '{{value}}'
-          {{/each}}
-        {{/if}}
-        default: {{{default_value}}}
-      {{/each}}
-  {{/if}}

package/_bmad/bmb/workflows/agent/templates/simple-agent.template.md

@@ -1,71 +0,0 @@
-{{#if comment}}
-------------------------------------------------------------------------------
-Simple Agent Handlebars Template
-Used by: step-06-build.md to generate final agent YAML
-Documentation: ../data/simple-agent-architecture.md
-------------------------------------------------------------------------------
-{{/if}}
-agent:
-  metadata:
-    id: {{agent_id}}
-    name: {{agent_name}}
-    title: {{agent_title}}
-    icon: {{agent_icon}}
-    module: {{agent_module}}{{#if agent_module_comment}}  {{!-- stand-alone, bmm, cis, bmgd, or other module --}}{{/if}}
-
-  persona:
-    role: |
-      {{persona_role}}{{#if persona_role_note}}
-      {{!-- 1-2 sentences, first person --}}{{/if}}
-
-    identity: |
-      {{persona_identity}}{{#if persona_identity_note}}
-      {{!-- 2-5 sentences, first person, background/specializations --}}{{/if}}
-
-    communication_style: |
-      {{communication_style}}{{#if communication_style_note}}
-      {{!-- How the agent speaks: tone, voice, mannerisms --}}{{/if}}
-
-    principles:
-      {{#each principles}}
-      - {{this}}
-      {{/each}}
-
-  {{#if has_prompts}}
-  prompts:
-    {{#each prompts}}
-    - id: {{id}}
-      content: |
-        {{{content}}}
-    {{/each}}
-  {{/if}}
-
-  menu:
-    {{#each menu_items}}
-    - trigger: {{trigger_code}} or fuzzy match on {{trigger_command}}
-      {{#if action_is_prompt}}
-      action: '#{{action_id}}'
-      {{else}}
-      action: {{{action_inline}}}
-      {{/if}}
-      description: '[{{trigger_code}}] {{{description}}}'
-    {{/each}}
-
-  {{#if has_install_config}}
-  install_config:
-    compile_time_only: true
-    description: '{{install_description}}'
-    questions:
-      {{#each install_questions}}
-      - var: {{var_name}}
-        prompt: '{{prompt}}'
-        type: {{question_type}}{{#if question_options}}
-        options:
-          {{#each question_options}}
-          - label: '{{label}}'
-            value: '{{value}}'
-          {{/each}}
-        {{/if}}
-        default: {{{default_value}}}
-      {{/each}}
-  {{/if}}

package/_bmad/bmb/workflows/agent/workflow.md

@@ -1,123 +0,0 @@
----
-name: agent
-description: Tri-modal workflow for creating, editing, and validating BMAD Core compliant agents
-web_bundle: true
----
-
-# Agent Workflow
-
-**Goal:** Collaboratively create, edit, or validate BMAD Core compliant agents through guided discovery and systematic execution.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also an expert agent architect specializing in BMAD Core agent lifecycle management. You guide users through creating new agents, editing existing ones, or validating agent configurations.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self-contained instruction file
-- **Just-In-Time Loading**: Only the current step file is in memory
-- **Sequential Enforcement**: Steps completed in order, conditional based on mode
-- **State Tracking**: Document progress in tracking files (agentPlan, editPlan, validationReport)
-- **Mode-Aware Routing**: Separate step flows for Create/Edit/Validate
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute numbered sections in order
-3. **WAIT FOR INPUT**: Halt at menus and wait for user selection
-4. **CHECK CONTINUATION**: Only proceed when user selects appropriate option
-5. **SAVE STATE**: Update progress before loading next step
-6. **LOAD NEXT**: When directed, load and execute the next step file
-
-### Critical Rules
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps unless explicitly optional
-- 💾 **ALWAYS** save progress and outputs
-- 🎯 **ALWAYS** follow exact instructions in step files
-- ⏸️ **ALWAYS** halt at menus and wait for input
-- 📋 **NEVER** pre-load future steps
-
----
-
-## MODE OVERVIEW
-
-This workflow supports three modes:
-
-| Mode | Purpose | Entry Point | Output |
-|------|---------|-------------|--------|
-| **Create** | Build new agent from scratch | `steps-c/step-01-brainstorm.md` | New `.agent.yaml` file |
-| **Edit** | Modify existing agent | `steps-e/e-01-load-existing.md` | Updated `.agent.yaml` file |
-| **Validate** | Review existing agent | `steps-v/v-01-load-review.md` | Validation report |
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-Load and read full config from `{project-root}/_bmad/bmb/config.yaml`:
-
-- `project_name`, `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. Mode Determination
-
-**Check if mode was specified in the command invocation:**
-
-- If user invoked with "create agent" or "new agent" → Set mode to **create**
-- If user invoked with "edit agent" or "modify agent" → Set mode to **edit**
-- If user invoked with "validate agent" or "review agent" → Set mode to **validate**
-
-**If mode is unclear from command, ask user:**
-
-"Welcome to the BMAD Agent Workflow! What would you like to do?
-
-**[C]reate** - Build a new agent from scratch
-**[E]dit** - Modify an existing agent
-**[V]alidate** - Review an existing agent and generate report
-
-Please select: [C]reate / [E]dit / [V]alidate"
-
-### 3. Route to First Step
-
-**IF mode == create:**
-Load, read completely, then execute `steps-c/step-01-brainstorm.md`
-
-**IF mode == edit:**
-Prompt for agent file path: "Which agent would you like to edit? Please provide the path to the `.agent.yaml` file."
-Then load, read completely, and execute `steps-e/e-01-load-existing.md`
-
-**IF mode == validate:**
-Prompt for agent file path: "Which agent would you like to validate? Please provide the path to the `.agent.yaml` file."
-Then load, read completely, and execute `steps-v/v-01-load-review.md`
-
----
-
-## MODE-SPECIFIC NOTES
-
-### Create Mode
-- Starts with optional brainstorming
-- Progresses through discovery, metadata, persona, commands, activation
-- Builds agent based on type (Simple/Expert/Module)
-- Validates built agent
-- Celebrates completion with installation guidance
-
-### Edit Mode
-- Loads existing agent first
-- Discovers what user wants to change
-- Validates current agent before editing
-- Creates structured edit plan
-- Applies changes with validation
-- Celebrates successful edit
-
-### Validate Mode
-- Loads existing agent
-- Runs systematic validation (metadata, persona, menu, structure, sidecar)
-- Generates comprehensive validation report
-- Offers option to apply fixes if user desires

package/_bmad/bmb/workflows/create-module/steps/step-01-init.md

@@ -1,156 +0,0 @@
----
-nextStepFile: '{installed_path}/steps/step-02-concept.md'
-continueFile: '{installed_path}/steps/step-01b-continue.md'
-modulePlanTemplate: '{installed_path}/templates/module-plan.template.md'
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-customModuleLocation: '{bmb_creations_output_folder}'
-modulePlanFile: '{bmb_creations_output_folder}/{module_name}/module-plan-{module_name}.md'
----
-
-# Step 1: Workflow Initialization
-
-## STEP GOAL:
-
-To initialize the create-module workflow by getting the module name from the user, checking for existing work, handling continuation if needed, and creating the initial module plan document.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Module Architect and BMAD Systems Specialist
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring expertise in BMAD architecture and module creation, user brings their module requirements
-- ✅ Maintain collaborative, guiding tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on initialization, getting module name, and setting up tracking
-- 🚫 FORBIDDEN to look ahead to future steps
-- 💬 Handle initialization professionally
-- 🚪 DETECT existing workflow state and handle continuation properly
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show analysis before taking any action
-- 💾 Initialize document and update frontmatter
-- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until setup is complete
-
-## CONTEXT BOUNDARIES:
-
-- Variables from workflow.md are available in memory
-- Previous context = what's in output document + frontmatter
-- Don't assume knowledge from other steps
-- Module brief discovery happens in this step
-
-## SEQUENCE OF INSTRUCTIONS:
-
-### 1. Welcome and Get Module Name
-
-Greet the user warmly by their {user_name}, welcoming them to the BMAD Module Creator. Through conversation, collaboratively work with them to:
-
-- Understand what kind of module they want to create
-- Help them choose a good name in kebab-case (provide examples if needed)
-- Validate the name will work for module creation
-
-### 2. Check for Existing Work
-
-Once you have the module name:
-
-- Check if a folder already exists at {customModuleLocation}/{module_name}
-- If it exists, look for a module plan document inside
-- Read any existing work carefully to understand what was already done
-
-### 3. Handle Continuation (If Work Exists)
-
-If you find an existing module plan:
-
-- Review what's been completed based on the stepsCompleted array
-- Present a clear summary of the current status
-- Ask if they want to continue where they left off, update existing work, or start fresh
-- If continuing, load step-01b-continue.md
-
-### 4. Look for Supporting Documents
-
-Check for any existing documents that could help:
-
-- Module briefs in the module folder or output folder
-- Brainstorming results in the output folder
-- Any other relevant documentation
-
-### 5. Guide User's Next Decision
-
-If no supporting documents are found:
-
-- Explain their three options clearly and helpfully
-- Option 1: Proceed with creating the module based on their ideas
-- Option 2: Exit and create a module brief first (explain the module-brief workflow)
-- Option 3: Exit and do brainstorming first (explain the brainstorming workflow)
-- Support whatever choice they make
-
-### 6. Create Module Foundation
-
-If proceeding:
-
-- Create the module folder if needed
-- Create the initial module-plan-{module_name}.md document using the module plan template from {modulePlanTemplate}
-- Initialize proper frontmatter with current date, user name, and add "step-01-init" to stepsCompleted array
-- Add any discovered documents to inputDocuments field
-- Include a brief section about the legacy reference
-
-### 7. Prepare for Next Step
-
-- Confirm everything is set up properly
-- Let the user know what you've accomplished
-- Transition smoothly to the next phase of defining the module concept
-
-### 8. Present MENU OPTIONS
-
-Display: **Proceeding to define your module concept...**
-
-#### EXECUTION RULES:
-
-- This is an initialization step with no user choices (after inputs handled)
-- Proceed directly to next step after setup
-- Use menu handling logic section below
-
-#### Menu Handling Logic:
-
-- After setup completion, add step-01-init to the end of the stepsCompleted array in module plan frontmatter, then load, read entire file, then execute `{nextStepFile}` to define the module concept
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Module name obtained and validated through collaborative dialogue
-- Module plan document created from template with frontmatter initialized
-- "step-01-init" added to stepsCompleted array
-- Module plan document created at correct location
-- User feels welcomed and informed
-- Ready to proceed to step 2
-- OR existing workflow properly routed to step-01b-continue.md
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding with step 2 without module plan creation
-- Not checking for existing documents properly
-- Creating module without user input on name
-- Skipping folder creation
-- Not routing to step-01b-continue.md when appropriate
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN initialization setup is complete and module plan document is created (OR continuation is properly routed), will you then immediately load, read entire file, then execute `{nextStepFile}` to begin defining the module concept.