siesa-agents 2.1.40 → 2.1.42

package/bmad/bmb/workflows/agent/steps-e/e-07-activation.md

@@ -1,122 +1,122 @@
----
-name: 'e-07-activation'
-description: 'Review critical_actions and route to type-specific edit'
-
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-criticalActions: ../data/critical-actions.md
-
-# Type-specific edit routes
-simpleEdit: './e-08a-edit-simple.md'
-expertEdit: './e-08b-edit-expert.md'
-moduleEdit: './e-08c-edit-module.md'
-
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Edit Step 7: Activation and Routing
-
-## STEP GOAL:
-
-Review critical_actions and route to the appropriate type-specific edit step (Simple/Expert/Module).
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Load criticalActions and editPlan first
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}}`
-
-### Step-Specific Rules:
-
-- 🎯 Load criticalActions.md before discussing activation
-- 📊 Determine target type for routing
-- 💬 Route based on POST-EDIT agent type
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load criticalActions.md
-- 📊 Check editPlan for target agent type
-- 💾 Route to appropriate type-specific edit step
-- ➡️ Auto-advance to type-specific edit on [C]
-
-## Sequence of Instructions:
-
-### 1. Load Reference Documents
-
-Read `{criticalActions}` and `{editPlan}` to understand:
-- Current critical_actions (if any)
-- Target agent type after edits
-
-### 2. Review Critical Actions
-
-If user wants to add/modify critical_actions:
-- Reference patterns from criticalActions.md
-- Define action name, description, invocation
-- For Expert agents: specify sidecar-folder and file paths
-
-### 3. Determine Routing
-
-Check `{editPlan}` metadataEdits.typeConversion.to or current agentType:
-
-```yaml
-agentType: simple → route to e-08a-edit-simple.md
-agentType: expert → route to e-08b-edit-expert.md
-agentType: module → route to e-08c-edit-module.md
-```
-
-### 4. Document to Edit Plan
-
-Append to `{editPlan}`:
-
-```yaml
-activationEdits:
-  criticalActions:
-    additions: []
-    modifications: []
-routing:
-  destinationEdit: {e-08a|e-08b|e-08c}
-  targetType: {simple|expert|module}
-```
-
-### 5. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Type-Specific Edit"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF C: Save to {editPlan}, determine routing based on targetType, then only then load and execute the appropriate type-specific edit step
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-
-## CRITICAL STEP COMPLETION NOTE
-
-This is the **ROUTING HUB** for edit flow. ONLY WHEN [C continue option] is selected and [routing determined], load and execute the appropriate type-specific edit step:
-
-- targetType: simple → e-08a-edit-simple.md
-- targetType: expert → e-08b-edit-expert.md
-- targetType: module → e-08c-edit-module.md
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- criticalActions.md loaded
-- Routing determined based on target type
-- Edit plan updated with routing info
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeded without loading reference documents
-- Routing not determined
-- Wrong type-specific edit step selected
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+---
+name: 'e-07-activation'
+description: 'Review critical_actions and route to type-specific edit'
+
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+criticalActions: ../data/critical-actions.md
+
+# Type-specific edit routes
+simpleEdit: './e-08a-edit-simple.md'
+expertEdit: './e-08b-edit-expert.md'
+moduleEdit: './e-08c-edit-module.md'
+
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Edit Step 7: Activation and Routing
+
+## STEP GOAL:
+
+Review critical_actions and route to the appropriate type-specific edit step (Simple/Expert/Module).
+
+## MANDATORY EXECUTION RULES:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Load criticalActions and editPlan first
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}}`
+
+### Step-Specific Rules:
+
+- 🎯 Load criticalActions.md before discussing activation
+- 📊 Determine target type for routing
+- 💬 Route based on POST-EDIT agent type
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load criticalActions.md
+- 📊 Check editPlan for target agent type
+- 💾 Route to appropriate type-specific edit step
+- ➡️ Auto-advance to type-specific edit on [C]
+
+## Sequence of Instructions:
+
+### 1. Load Reference Documents
+
+Read `{criticalActions}` and `{editPlan}` to understand:
+- Current critical_actions (if any)
+- Target agent type after edits
+
+### 2. Review Critical Actions
+
+If user wants to add/modify critical_actions:
+- Reference patterns from criticalActions.md
+- Define action name, description, invocation
+- For Expert agents: specify sidecar-folder and file paths
+
+### 3. Determine Routing
+
+Check `{editPlan}` metadataEdits.typeConversion.to or current agentType:
+
+```yaml
+agentType: simple → route to e-08a-edit-simple.md
+agentType: expert → route to e-08b-edit-expert.md
+agentType: module → route to e-08c-edit-module.md
+```
+
+### 4. Document to Edit Plan
+
+Append to `{editPlan}`:
+
+```yaml
+activationEdits:
+  criticalActions:
+    additions: []
+    modifications: []
+routing:
+  destinationEdit: {e-08a|e-08b|e-08c}
+  targetType: {simple|expert|module}
+```
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Type-Specific Edit"
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
+- IF C: Save to {editPlan}, determine routing based on targetType, then only then load and execute the appropriate type-specific edit step
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+
+## CRITICAL STEP COMPLETION NOTE
+
+This is the **ROUTING HUB** for edit flow. ONLY WHEN [C continue option] is selected and [routing determined], load and execute the appropriate type-specific edit step:
+
+- targetType: simple → e-08a-edit-simple.md
+- targetType: expert → e-08b-edit-expert.md
+- targetType: module → e-08c-edit-module.md
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- criticalActions.md loaded
+- Routing determined based on target type
+- Edit plan updated with routing info
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeded without loading reference documents
+- Routing not determined
+- Wrong type-specific edit step selected
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmb/workflows/agent/steps-e/e-08a-edit-simple.md

@@ -1,134 +1,134 @@
----
-name: 'e-08a-edit-simple'
-description: 'Apply edits to Simple agent'
-
-nextStepFile: './e-09a-validate-metadata.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentFile: '{original-agent-path}'
-agentBackup: '{original-agent-path}.backup'
-
-# Template and Architecture
-simpleTemplate: ../templates/simple-agent.template.md
-simpleArch: ../data/simple-agent-architecture.md
-agentCompilation: ../data/agent-compilation.md
-agentMetadata: ../data/agent-metadata.md
-personaProperties: ../data/persona-properties.md
-principlesCrafting: ../data/principles-crafting.md
-agentMenuPatterns: ../data/agent-menu-patterns.md
-criticalActions: ../data/critical-actions.md
----
-
-# Edit Step 8a: Edit Simple Agent
-
-## STEP GOAL:
-
-Apply all planned edits to the Simple agent YAML file using templates and architecture references for validation.
-
-## MANDATORY EXECUTION RULES:
-
-- 🛑 ALWAYS create backup before modifying agent file
-- 📖 CRITICAL: Read template and architecture files first
-- 🔄 CRITICAL: Load editPlan and agentFile
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Load all reference files before applying edits
-- 📊 Apply edits exactly as specified in editPlan
-- 💾 Validate YAML after each edit
-- ➡️ Auto-advance to post-edit validation when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load template, architecture, and data files
-- 📊 Read editPlan to get all planned changes
-- 💾 Create backup
-- 📝 Apply edits: type conversion, metadata, persona, commands, critical_actions
-- ✅ Validate YAML syntax
-- ➡️ Auto-advance to next validation step
-
-## Sequence of Instructions:
-
-### 1. Load Reference Documents
-
-Read all files before editing:
-- `{simpleTemplate}` - YAML structure reference
-- `{simpleArch}` - Simple agent architecture
-- `{agentCompilation}` - Assembly guidelines
-- `{agentMetadata}`, `{personaProperties}`, `{principlesCrafting}`
-- `{agentMenuPatterns}`, `{criticalActions}`
-
-### 2. Load Edit Plan and Agent
-
-Read `{editPlan}` to get all planned edits.
-Read `{agentFile}` to get current agent YAML.
-
-### 3. Create Backup
-
-ALWAYS backup before editing:
-`cp {agentFile} {agentBackup}`
-
-Confirm: "Backup created at: `{agentBackup}`"
-
-### 4. Apply Edits in Sequence
-
-For each planned edit:
-
-**Type Conversion:**
-- Update `type:` field if converting
-- Add/remove type-specific fields
-
-**Metadata Edits:**
-- Apply each field change from metadataEdits
-
-**Persona Edits:**
-- Replace persona section with new four-field persona
-- Validate field purity (role ≠ identity ≠ communication_style)
-
-**Command Edits:**
-- Additions: append to commands array
-- Modifications: update specific commands
-- Removals: remove from commands array
-
-**Critical Actions Edits:**
-- Additions: append to critical_actions array
-- Modifications: update specific actions
-- Removals: remove from array
-
-### 5. Validate YAML After Each Edit
-
-Confirm YAML syntax is valid after each modification.
-
-### 6. Document Applied Edits
-
-Append to `{editPlan}`:
-
-```yaml
-editsApplied:
-  - {edit-description}
-  - {edit-description}
-backup: {agentBackup}
-timestamp: {YYYY-MM-DD HH:MM}
-```
-
-### 7. Auto-Advance
-
-When all edits applied successfully, load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ Backup created
-✅ All reference files loaded
-✅ All edits applied correctly
-✅ YAML remains valid
-✅ Edit plan tracking updated
-
-## FAILURE MODES
-
-❌ Backup failed
-❌ YAML became invalid
-❌ Edits not applied as specified
-
----
-
-**Auto-advancing to post-edit validation...
+---
+name: 'e-08a-edit-simple'
+description: 'Apply edits to Simple agent'
+
+nextStepFile: './e-09a-validate-metadata.md'
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+agentFile: '{original-agent-path}'
+agentBackup: '{original-agent-path}.backup'
+
+# Template and Architecture
+simpleTemplate: ../templates/simple-agent.template.md
+simpleArch: ../data/simple-agent-architecture.md
+agentCompilation: ../data/agent-compilation.md
+agentMetadata: ../data/agent-metadata.md
+personaProperties: ../data/persona-properties.md
+principlesCrafting: ../data/principles-crafting.md
+agentMenuPatterns: ../data/agent-menu-patterns.md
+criticalActions: ../data/critical-actions.md
+---
+
+# Edit Step 8a: Edit Simple Agent
+
+## STEP GOAL:
+
+Apply all planned edits to the Simple agent YAML file using templates and architecture references for validation.
+
+## MANDATORY EXECUTION RULES:
+
+- 🛑 ALWAYS create backup before modifying agent file
+- 📖 CRITICAL: Read template and architecture files first
+- 🔄 CRITICAL: Load editPlan and agentFile
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Step-Specific Rules:
+
+- 🎯 Load all reference files before applying edits
+- 📊 Apply edits exactly as specified in editPlan
+- 💾 Validate YAML after each edit
+- ➡️ Auto-advance to post-edit validation when complete
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load template, architecture, and data files
+- 📊 Read editPlan to get all planned changes
+- 💾 Create backup
+- 📝 Apply edits: type conversion, metadata, persona, commands, critical_actions
+- ✅ Validate YAML syntax
+- ➡️ Auto-advance to next validation step
+
+## Sequence of Instructions:
+
+### 1. Load Reference Documents
+
+Read all files before editing:
+- `{simpleTemplate}` - YAML structure reference
+- `{simpleArch}` - Simple agent architecture
+- `{agentCompilation}` - Assembly guidelines
+- `{agentMetadata}`, `{personaProperties}`, `{principlesCrafting}`
+- `{agentMenuPatterns}`, `{criticalActions}`
+
+### 2. Load Edit Plan and Agent
+
+Read `{editPlan}` to get all planned edits.
+Read `{agentFile}` to get current agent YAML.
+
+### 3. Create Backup
+
+ALWAYS backup before editing:
+`cp {agentFile} {agentBackup}`
+
+Confirm: "Backup created at: `{agentBackup}`"
+
+### 4. Apply Edits in Sequence
+
+For each planned edit:
+
+**Type Conversion:**
+- Update `type:` field if converting
+- Add/remove type-specific fields
+
+**Metadata Edits:**
+- Apply each field change from metadataEdits
+
+**Persona Edits:**
+- Replace persona section with new four-field persona
+- Validate field purity (role ≠ identity ≠ communication_style)
+
+**Command Edits:**
+- Additions: append to commands array
+- Modifications: update specific commands
+- Removals: remove from commands array
+
+**Critical Actions Edits:**
+- Additions: append to critical_actions array
+- Modifications: update specific actions
+- Removals: remove from array
+
+### 5. Validate YAML After Each Edit
+
+Confirm YAML syntax is valid after each modification.
+
+### 6. Document Applied Edits
+
+Append to `{editPlan}`:
+
+```yaml
+editsApplied:
+  - {edit-description}
+  - {edit-description}
+backup: {agentBackup}
+timestamp: {YYYY-MM-DD HH:MM}
+```
+
+### 7. Auto-Advance
+
+When all edits applied successfully, load and execute `{nextStepFile}` immediately.
+
+## SUCCESS METRICS
+
+✅ Backup created
+✅ All reference files loaded
+✅ All edits applied correctly
+✅ YAML remains valid
+✅ Edit plan tracking updated
+
+## FAILURE MODES
+
+❌ Backup failed
+❌ YAML became invalid
+❌ Edits not applied as specified
+
+---
+
+**Auto-advancing to post-edit validation...