siesa-agents 2.1.40 → 2.1.42

package/bmad/bmb/workflows/agent/steps-e/e-03b-validate-persona.md

@@ -1,76 +1,76 @@
----
-name: 'e-03b-validate-persona'
-description: 'Validate persona (before edit) - no menu, auto-advance'
-
-nextStepFile: './e-03c-validate-menu.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-personaProperties: ../data/persona-properties.md
-principlesCrafting: ../data/principles-crafting.md
----
-
-# Edit Step 3b: Validate Persona (Before Edit)
-
-## STEP GOAL:
-
-Validate the agent's persona fields against BMAD standards. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and persona references first
-- 🚫 NO MENU in this step - record findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate persona four-field system
-- 📊 Record findings to editPlan frontmatter
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load personaProperties.md and principlesCrafting.md
-- 📊 Validate persona fields
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{personaProperties}` and `{principlesCrafting}`.
-Read `{editPlan}` to get agent file path and persona.
-
-### 2. Validate Persona
-
-Perform checks on:
-- **role**: present, specific, not generic
-- **identity**: present, defines who agent is
-- **communication_style**: present, speech patterns only (no behavioral words)
-- **principles**: present, first principle activates expert knowledge, not generic duties
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  persona:
-    status: [pass|fail|warning]
-    findings:
-      - {check}: [pass|fail]
-      - {check}: [pass|fail]
-```
-
-### 4. Auto-Advance
-
-When validation complete, load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ All persona checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to menu validation...**
+---
+name: 'e-03b-validate-persona'
+description: 'Validate persona (before edit) - no menu, auto-advance'
+
+nextStepFile: './e-03c-validate-menu.md'
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+personaProperties: ../data/persona-properties.md
+principlesCrafting: ../data/principles-crafting.md
+---
+
+# Edit Step 3b: Validate Persona (Before Edit)
+
+## STEP GOAL:
+
+Validate the agent's persona fields against BMAD standards. Record findings to editPlan and auto-advance.
+
+## MANDATORY EXECUTION RULES:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Read editPlan and persona references first
+- 🚫 NO MENU in this step - record findings and auto-advance
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Step-Specific Rules:
+
+- 🎯 Validate persona four-field system
+- 📊 Record findings to editPlan frontmatter
+- 🚫 FORBIDDEN to present menu - auto-advance when complete
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load personaProperties.md and principlesCrafting.md
+- 📊 Validate persona fields
+- 💾 Record findings to editPlan
+- ➡️ Auto-advance to next validation step when complete
+
+## Sequence of Instructions:
+
+### 1. Load References
+
+Read `{personaProperties}` and `{principlesCrafting}`.
+Read `{editPlan}` to get agent file path and persona.
+
+### 2. Validate Persona
+
+Perform checks on:
+- **role**: present, specific, not generic
+- **identity**: present, defines who agent is
+- **communication_style**: present, speech patterns only (no behavioral words)
+- **principles**: present, first principle activates expert knowledge, not generic duties
+
+### 3. Record Findings
+
+Append to editPlan frontmatter:
+
+```yaml
+  persona:
+    status: [pass|fail|warning]
+    findings:
+      - {check}: [pass|fail]
+      - {check}: [pass|fail]
+```
+
+### 4. Auto-Advance
+
+When validation complete, load and execute `{nextStepFile}` immediately.
+
+## SUCCESS METRICS
+
+✅ All persona checks performed and recorded
+✅ Findings saved to editPlan
+✅ Auto-advanced to next step
+
+---
+
+**Auto-advancing to menu validation...**

package/bmad/bmb/workflows/agent/steps-e/e-03c-validate-menu.md

@@ -1,75 +1,75 @@
----
-name: 'e-03c-validate-menu'
-description: 'Validate menu structure (before edit) - no menu, auto-advance'
-
-nextStepFile: './e-03d-validate-structure.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentMenuPatterns: ../data/agent-menu-patterns.md
----
-
-# Edit Step 3c: Validate Menu (Before Edit)
-
-## STEP GOAL:
-
-Validate the agent's command menu structure against BMAD standards. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and agentMenuPatterns first
-- 🚫 NO MENU in this step - record 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
-- 📊 Record findings to editPlan frontmatter
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentMenuPatterns.md reference
-- 📊 Validate commands and menu
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentMenuPatterns}`.
-Read `{editPlan}` to get agent file path and commands.
-
-### 2. Validate Menu
-
-Perform checks on:
-- **A/P/C convention**: each menu has Advanced Elicitation, Party Mode, Continue
-- **Command names**: clear, descriptive
-- **Command descriptions**: specific, actionable
-- **Menu handling logic**: properly specified
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  menu:
-    status: [pass|fail|warning]
-    findings:
-      - {check}: [pass|fail]
-      - {check}: [pass|fail]
-```
-
-### 4. Auto-Advance
-
-When validation complete, load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ All menu checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to structure validation...**
+---
+name: 'e-03c-validate-menu'
+description: 'Validate menu structure (before edit) - no menu, auto-advance'
+
+nextStepFile: './e-03d-validate-structure.md'
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+agentMenuPatterns: ../data/agent-menu-patterns.md
+---
+
+# Edit Step 3c: Validate Menu (Before Edit)
+
+## STEP GOAL:
+
+Validate the agent's command menu structure against BMAD standards. Record findings to editPlan and auto-advance.
+
+## MANDATORY EXECUTION RULES:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Read editPlan and agentMenuPatterns first
+- 🚫 NO MENU in this step - record 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
+- 📊 Record findings to editPlan frontmatter
+- 🚫 FORBIDDEN to present menu - auto-advance when complete
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load agentMenuPatterns.md reference
+- 📊 Validate commands and menu
+- 💾 Record findings to editPlan
+- ➡️ Auto-advance to next validation step when complete
+
+## Sequence of Instructions:
+
+### 1. Load References
+
+Read `{agentMenuPatterns}`.
+Read `{editPlan}` to get agent file path and commands.
+
+### 2. Validate Menu
+
+Perform checks on:
+- **A/P/C convention**: each menu has Advanced Elicitation, Party Mode, Continue
+- **Command names**: clear, descriptive
+- **Command descriptions**: specific, actionable
+- **Menu handling logic**: properly specified
+
+### 3. Record Findings
+
+Append to editPlan frontmatter:
+
+```yaml
+  menu:
+    status: [pass|fail|warning]
+    findings:
+      - {check}: [pass|fail]
+      - {check}: [pass|fail]
+```
+
+### 4. Auto-Advance
+
+When validation complete, load and execute `{nextStepFile}` immediately.
+
+## SUCCESS METRICS
+
+✅ All menu checks performed and recorded
+✅ Findings saved to editPlan
+✅ Auto-advanced to next step
+
+---
+
+**Auto-advancing to structure validation...**

package/bmad/bmb/workflows/agent/steps-e/e-03d-validate-structure.md

@@ -1,75 +1,75 @@
----
-name: 'e-03d-validate-structure'
-description: 'Validate YAML structure (before edit) - no menu, auto-advance'
-
-nextStepFile: './e-03e-validate-sidecar.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentCompilation: ../data/agent-compilation.md
----
-
-# Edit Step 3d: Validate Structure (Before Edit)
-
-## STEP GOAL:
-
-Validate the agent's YAML structure and completeness. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and agentCompilation first
-- 🚫 NO MENU in this step - record 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
-- 📊 Record findings to editPlan frontmatter
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentCompilation.md reference
-- 📊 Validate YAML structure
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentCompilation}`.
-Read `{editPlan}` to get agent file path.
-
-### 2. Validate Structure
-
-Perform checks on:
-- **YAML syntax**: valid, no parse errors
-- **Required fields**: name, description, type, persona present
-- **Field types**: arrays where expected, strings where expected
-- **Indentation**: consistent 2-space indentation
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  structure:
-    status: [pass|fail|warning]
-    findings:
-      - {check}: [pass|fail]
-      - {check}: [pass|fail]
-```
-
-### 4. Auto-Advance
-
-When validation complete, load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ All structure checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to sidecar validation...**
+---
+name: 'e-03d-validate-structure'
+description: 'Validate YAML structure (before edit) - no menu, auto-advance'
+
+nextStepFile: './e-03e-validate-sidecar.md'
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+agentCompilation: ../data/agent-compilation.md
+---
+
+# Edit Step 3d: Validate Structure (Before Edit)
+
+## STEP GOAL:
+
+Validate the agent's YAML structure and completeness. Record findings to editPlan and auto-advance.
+
+## MANDATORY EXECUTION RULES:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Read editPlan and agentCompilation first
+- 🚫 NO MENU in this step - record 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
+- 📊 Record findings to editPlan frontmatter
+- 🚫 FORBIDDEN to present menu - auto-advance when complete
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load agentCompilation.md reference
+- 📊 Validate YAML structure
+- 💾 Record findings to editPlan
+- ➡️ Auto-advance to next validation step when complete
+
+## Sequence of Instructions:
+
+### 1. Load References
+
+Read `{agentCompilation}`.
+Read `{editPlan}` to get agent file path.
+
+### 2. Validate Structure
+
+Perform checks on:
+- **YAML syntax**: valid, no parse errors
+- **Required fields**: name, description, type, persona present
+- **Field types**: arrays where expected, strings where expected
+- **Indentation**: consistent 2-space indentation
+
+### 3. Record Findings
+
+Append to editPlan frontmatter:
+
+```yaml
+  structure:
+    status: [pass|fail|warning]
+    findings:
+      - {check}: [pass|fail]
+      - {check}: [pass|fail]
+```
+
+### 4. Auto-Advance
+
+When validation complete, load and execute `{nextStepFile}` immediately.
+
+## SUCCESS METRICS
+
+✅ All structure checks performed and recorded
+✅ Findings saved to editPlan
+✅ Auto-advanced to next step
+
+---
+
+**Auto-advancing to sidecar validation...**

package/bmad/bmb/workflows/agent/steps-e/e-03e-validate-sidecar.md

@@ -1,78 +1,78 @@
----
-name: 'e-03e-validate-sidecar'
-description: 'Validate sidecar structure (before edit) - no menu, auto-advance'
-
-nextStepFile: './e-03f-validation-summary.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-expertValidation: ../data/expert-agent-validation.md
----
-
-# Edit Step 3e: Validate Sidecar (Before Edit)
-
-## STEP GOAL:
-
-Validate the agent's sidecar structure if Expert type. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and expertValidation first
-- 🚫 NO MENU in this step - record 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
-- 📊 Record findings to editPlan frontmatter
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load expertValidation.md reference
-- 📊 Validate sidecar if Expert type, skip for Simple/Module
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to validation summary when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{expertValidation}`.
-Read `{editPlan}` to get agent type.
-
-### 2. Conditional Validation
-
-**IF agentType == expert:**
-- Check metadata.sidecar-folder is present
-- Check sidecar-path is correct format
-- Verify sidecar files exist at specified path
-
-**IF agentType != expert:**
-- Mark as N/A (not applicable)
-- Skip detailed checks
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  sidecar:
-    status: [pass|fail|warning|n/a]
-    findings:
-      - {check}: [pass|fail|n/a]
-      - {check}: [pass|fail|n/a]
-```
-
-### 4. Auto-Advance
-
-When validation complete, load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ Sidecar checks performed (or N/A recorded)
-✅ Findings saved to editPlan
-✅ Auto-advanced to validation summary
-
----
-
-**Auto-advancing to validation summary...**
+---
+name: 'e-03e-validate-sidecar'
+description: 'Validate sidecar structure (before edit) - no menu, auto-advance'
+
+nextStepFile: './e-03f-validation-summary.md'
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+expertValidation: ../data/expert-agent-validation.md
+---
+
+# Edit Step 3e: Validate Sidecar (Before Edit)
+
+## STEP GOAL:
+
+Validate the agent's sidecar structure if Expert type. Record findings to editPlan and auto-advance.
+
+## MANDATORY EXECUTION RULES:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Read editPlan and expertValidation first
+- 🚫 NO MENU in this step - record 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
+- 📊 Record findings to editPlan frontmatter
+- 🚫 FORBIDDEN to present menu - auto-advance when complete
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load expertValidation.md reference
+- 📊 Validate sidecar if Expert type, skip for Simple/Module
+- 💾 Record findings to editPlan
+- ➡️ Auto-advance to validation summary when complete
+
+## Sequence of Instructions:
+
+### 1. Load References
+
+Read `{expertValidation}`.
+Read `{editPlan}` to get agent type.
+
+### 2. Conditional Validation
+
+**IF agentType == expert:**
+- Check metadata.sidecar-folder is present
+- Check sidecar-path is correct format
+- Verify sidecar files exist at specified path
+
+**IF agentType != expert:**
+- Mark as N/A (not applicable)
+- Skip detailed checks
+
+### 3. Record Findings
+
+Append to editPlan frontmatter:
+
+```yaml
+  sidecar:
+    status: [pass|fail|warning|n/a]
+    findings:
+      - {check}: [pass|fail|n/a]
+      - {check}: [pass|fail|n/a]
+```
+
+### 4. Auto-Advance
+
+When validation complete, load and execute `{nextStepFile}` immediately.
+
+## SUCCESS METRICS
+
+✅ Sidecar checks performed (or N/A recorded)
+✅ Findings saved to editPlan
+✅ Auto-advanced to validation summary
+
+---
+
+**Auto-advancing to validation summary...**