siesa-agents 2.1.40 → 2.1.41

package/bmad/bmb/workflows/agent/steps-v/v-02c-validate-menu.md

@@ -1,71 +1,71 @@
----
-name: 'v-02c-validate-menu'
-description: 'Validate menu structure and append to report'
-
-nextStepFile: './v-02d-validate-structure.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-agentMenuPatterns: ../data/agent-menu-patterns.md
----
-
-# Validate Step 2c: Validate Menu
-
-## STEP GOAL:
-
-Validate the agent's command menu structure against BMAD standards. 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 agentMenuPatterns 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 command/menu structure
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentMenuPatterns.md reference
-- 📊 Validate commands and menu
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentMenuPatterns}` and `{validationReport}`.
-
-### 2. Validate Menu
-
-Perform checks on: A/P/C convention, command names, descriptions.
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Menu Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] A/P/C convention followed
-- [ ] Command names clear and descriptive
-- [ ] Command descriptions specific and actionable
-- [ ] Menu handling logic properly specified
-
-**Findings:**
-{Detailed findings}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating YAML structure...**
+---
+name: 'v-02c-validate-menu'
+description: 'Validate menu structure and append to report'
+
+nextStepFile: './v-02d-validate-structure.md'
+validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
+agentMenuPatterns: ../data/agent-menu-patterns.md
+---
+
+# Validate Step 2c: Validate Menu
+
+## STEP GOAL:
+
+Validate the agent's command menu structure against BMAD standards. 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 agentMenuPatterns 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 command/menu structure
+- 📊 Append findings to validation report
+- 🚫 FORBIDDEN to present menu
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load agentMenuPatterns.md reference
+- 📊 Validate commands and menu
+- 💾 Append findings to validation report
+- ➡️ Auto-advance to next validation step
+
+## Sequence of Instructions:
+
+### 1. Load References
+
+Read `{agentMenuPatterns}` and `{validationReport}`.
+
+### 2. Validate Menu
+
+Perform checks on: A/P/C convention, command names, descriptions.
+
+### 3. Append Findings to Report
+
+Append to `{validationReport}`:
+
+```markdown
+### Menu Validation
+
+**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
+
+**Checks:**
+- [ ] A/P/C convention followed
+- [ ] Command names clear and descriptive
+- [ ] Command descriptions specific and actionable
+- [ ] Menu handling logic properly specified
+
+**Findings:**
+{Detailed findings}
+```
+
+### 4. Auto-Advance
+
+Load and execute `{nextStepFile}` immediately.
+
+---
+
+**Validating YAML structure...**

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

@@ -1,71 +1,71 @@
----
-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...**
+---
+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 +1,76 @@
----
-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...**
+---
+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 +1,100 @@
----
-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.
+---
+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 +1,5 @@
----
-stepsCompleted: []
----
-
-# Agent Design and Build Plan
+---
+stepsCompleted: []
+---
+
+# Agent Design and Build Plan