create-byan-agent 2.18.0 → 2.19.1

package/install/templates/_byan/workflow/simple/agent/steps-e/e-06-commands-menu.md

@@ -0,0 +1,122 @@
+---
+name: 'e-06-commands-menu'
+description: 'Review and plan command/menu edits'
+
+nextStepFile: './e-07-activation.md'
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+agentMenuPatterns: ../data/agent-menu-patterns.md
+
+advancedElicitationTask: '{project-root}/_byan/workflow/simple/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_byan/workflow/simple/party-mode/workflow.md'
+---
+
+# Edit Step 6: Commands Menu
+
+## STEP GOAL:
+
+Review the agent's command menu and plan any additions, modifications, or removals.
+
+## MANDATORY EXECUTION RULES:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Load agentMenuPatterns first
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Step-Specific Rules:
+
+- 🎯 Load agentMenuPatterns before discussing menu edits
+- 📊 Follow A/P/C convention for menu structure
+- 💬 Focus on commands that user wants to add/modify/remove
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load agentMenuPatterns.md
+- 📊 Review current commands from editPlan
+- 💾 Document planned command changes
+- 🚫 FORBIDDEN to proceed without documenting changes
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 1. Load Reference Documents
+
+Read `{agentMenuPatterns}` to understand menu structure requirements.
+
+### 2. Review Current Commands
+
+From `{editPlan}`, display current commands with:
+- trigger
+- description
+- handler/action
+
+### 3. Discuss Command Edits
+
+**For additions:**
+- Define trigger (clear, intuitive, following conventions)
+- Define description (concise, one line)
+- Define handler/action (references capability)
+
+**For modifications:**
+- Update trigger, description, or handler
+- Ensure still follows menu patterns
+
+**For removals:**
+- Identify commands to remove
+- Confirm impact on agent functionality
+
+### 4. Document to Edit Plan
+
+Append to `{editPlan}`:
+
+```yaml
+commandEdits:
+  additions:
+    - trigger: {trigger}
+      description: {description}
+      handler: {handler}
+  modifications:
+    - command: {existing-command}
+      changes: {what-to-change}
+  removals:
+    - command: {command-to-remove}
+```
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Activation"
+
+#### 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}, then only then load, read entire file, then execute {nextStepFile}
+- 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
+
+ONLY WHEN [C continue option] is selected and [command changes documented], will you then load and read fully `{nextStepFile}` to execute and begin activation planning.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- agentMenuPatterns loaded
+- Command changes documented with trigger/description/handler
+- A/P/C convention followed
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeded without loading reference documents
+- Commands missing required elements
+- Changes not documented to edit plan
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/install/templates/_byan/workflow/simple/agent/steps-e/e-07-activation.md

@@ -0,0 +1,125 @@
+---
+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}/_byan/workflow/simple/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_byan/workflow/simple/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]
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 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}` for agent metadata (module and hasSidecar):
+
+```yaml
+# Determine agent type from module + hasSidecar combination
+module ≠ "stand-alone" → route to e-08c-edit-module.md
+module = "stand-alone" + hasSidecar: true → route to e-08b-edit-expert.md
+module = "stand-alone" + hasSidecar: false → route to e-08a-edit-simple.md
+```
+
+### 4. Document to Edit Plan
+
+Append to `{editPlan}`:
+
+```yaml
+activationEdits:
+  criticalActions:
+    additions: []
+    modifications: []
+routing:
+  destinationEdit: {e-08a|e-08b|e-08c}
+  sourceType: {simple|expert|module}  # Derived from module + hasSidecar
+```
+
+### 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 module + hasSidecar, 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:
+
+- module ≠ "stand-alone" → e-08c-edit-module.md (Module agent)
+- module = "stand-alone" + hasSidecar: true → e-08b-edit-expert.md (Expert agent)
+- module = "stand-alone" + hasSidecar: false → e-08a-edit-simple.md (Simple agent)
+
+---
+
+## 🚨 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/install/templates/_byan/workflow/simple/agent/steps-e/e-08b-edit-expert.md

@@ -0,0 +1,119 @@
+---
+name: 'e-08b-edit-expert'
+description: 'Apply edits to Expert agent'
+
+nextStepFile: './e-09-celebrate.md'
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+agentFile: '{original-agent-path}'
+agentBackup: '{original-agent-path}.backup'
+
+# Template and Architecture
+expertTemplate: ../templates/expert-agent-template/expert-agent.template.md
+expertArch: ../data/expert-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
+expertValidation: ../data/expert-agent-validation.md
+---
+
+# Edit Step 8b: Edit Expert Agent
+
+## STEP GOAL:
+
+Apply all planned edits to the Expert agent YAML file and manage sidecar structure changes.
+
+## 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
+- 📊 Manage sidecar structure for Expert agents
+- 💾 Validate YAML and sidecar paths after edits
+- ➡️ 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 including sidecar management
+- ✅ Validate YAML and sidecar paths
+- ➡️ Auto-advance to next validation step
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 1. Load Reference Documents
+
+Read all files before editing:
+- `{expertTemplate}` - Expert YAML structure
+- `{expertArch}` - Expert agent architecture
+- `{agentCompilation}`, `{agentMetadata}`, `{personaProperties}`, `{principlesCrafting}`
+- `{agentMenuPatterns}`, `{criticalActions}`, `{expertValidation}`
+
+### 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}`
+
+### 4. Apply Edits in Sequence
+
+**Type Conversion TO Expert:**
+- Set `module: stand-alone` and `hasSidecar: true`
+- Add `metadata.sidecar-folder` if not present
+- Create sidecar directory next to agent.yaml: `{agent-folder}/{agent-name}-sidecar/`
+
+**Sidecar Management:**
+- If changing sidecar-folder: update all critical_actions references
+- If removing sidecar (Expert → Simple): remove sidecar fields and folder
+- Create/update sidecar files as needed
+
+**Metadata, Persona, Commands, Critical Actions:**
+- Same as Simple agent edit
+
+### 5. Validate Sidecar Paths
+
+After editing, confirm all critical_actions reference correct sidecar paths:
+`{project-root}/_byan/memoire/{sidecar-folder}/{file}.md`
+
+### 6. Document Applied Edits
+
+Append to `{editPlan}` with sidecar changes noted.
+
+### 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
+✅ Sidecar structure correct
+✅ Sidecar paths validated
+
+## FAILURE MODES
+
+❌ Backup failed
+❌ YAML became invalid
+❌ Sidecar paths broken
+❌ Edits not applied as specified
+
+---
+
+**Auto-advancing to post-edit validation...

package/install/templates/_byan/workflow/simple/agent/steps-e/e-09-celebrate.md

@@ -0,0 +1,155 @@
+---
+name: 'e-09-celebrate'
+description: 'Celebrate successful agent edit completion'
+
+editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
+
+advancedElicitationTask: '{project-root}/_byan/workflow/simple/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_byan/workflow/simple/party-mode/workflow.md'
+validationWorkflow: '{project-root}/src/modules/bmb/workflows/agent/steps-v/v-01-load-review.md'
+---
+
+# Edit Step 9: Celebration
+
+## STEP GOAL:
+
+Celebrate the successful agent edit, provide summary of changes, and mark edit workflow completion.
+
+## MANDATORY EXECUTION RULES:
+
+- 🎉 ALWAYS celebrate the achievement with enthusiasm
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Read editPlan to summarize what was accomplished
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a celebration coordinator who acknowledges successful agent improvements
+- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring celebration energy, user brings their satisfaction, together we acknowledge successful collaboration
+
+### Step-Specific Rules:
+
+- 🎯 Focus on celebrating and summarizing what was accomplished
+- 🚫 FORBIDDEN to end without marking workflow completion
+- 💬 Approach: Enthusiastic while providing clear summary
+
+## EXECUTION PROTOCOLS:
+
+- 🎉 Celebrate the edit completion enthusiastically
+- 📊 Provide clear summary of all changes made
+- 💾 Mark workflow completion in edit plan
+- 🚫 FORBIDDEN to end without proper completion marking
+
+## CONTEXT BOUNDARIES:
+
+- Available context: editPlan with full edit history
+- Focus: Celebration and summary
+- Limits: No more edits, only acknowledgment
+- Dependencies: All edits successfully applied
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.:
+
+### 1. Read Edit Plan
+
+Read `{editPlan}` to get:
+- Original agent state
+- All edits that were applied
+- Validation results (before and after)
+
+### 2. Grand Celebration
+
+"🎉 **Excellent work!** Your agent **{agent-name}** has been successfully updated!"
+
+### 3. Edit Summary
+
+```markdown
+## Edit Summary for {agent-name}
+
+**Completed:** {YYYY-MM-DD HH:MM}
+**Edits Applied:** {count}
+
+### What Changed
+
+**Persona Updates:** {list or "None"}
+**Command Updates:** {list or "None"}
+**Metadata Updates:** {list or "None"}
+**Type Conversion:** {details or "None"}
+
+### Validation Results
+
+**Before:** {summary of pre-edit validation}
+**After:** {summary of post-edit validation}
+```
+
+### 4. Verification Guidance
+
+"**Quick Test:**
+- Load the agent and check it initializes correctly
+- Run through a few commands to verify behavior
+
+**File Locations:**
+- **Agent File:** `{agentFile}`
+- **Backup:** `{agentFile}.backup`"
+
+### 5. Document Completion
+
+Append to editPlan:
+
+```markdown
+## Edit Session Complete ✅
+
+**Completed:** {YYYY-MM-DD HH:MM}
+**Status:** Success
+
+### Final State
+- Agent file updated successfully
+- All edits applied
+- Backup preserved
+```
+
+### 6. Present MENU OPTIONS
+
+Display: "**✅ Agent Edit Complete! Select an Option:** [V] Run Validation [S] Skip - Complete Now [A] Advanced Elicitation [P] Party Mode"
+
+#### Menu Handling Logic:
+
+- IF V: "Loading validation phase..." → Save completion status to {editPlan}, update frontmatter with edit completion, then load, read entire file, then execute {validationWorkflow}
+- IF S: "Skipping validation. Completing workflow..." → Save completion status to {editPlan} and end workflow gracefully
+- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- User can choose validation (V), skip to complete (S), or use advanced elicitation (A) or party mode (P)
+- After other menu items execution (A/P), return to this menu
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [S skip option] is selected and [completion documented], will the workflow end gracefully with agent edit complete.
+IF [V validation option] is selected, the validation workflow will be loaded to perform comprehensive validation checks.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Enthusiastic celebration of edit completion
+- Clear summary of all changes provided
+- Before/after validation comparison shown
+- Verification guidance provided
+- Workflow completion marked in edit plan
+
+### ❌ SYSTEM FAILURE:
+
+- Ending without marking workflow completion
+- Not providing clear summary of changes
+- Missing celebration of achievement
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/install/templates/_byan/workflow/simple/agent/steps-v/v-01-load-review.md

@@ -0,0 +1,136 @@
+---
+name: 'v-01-load-review'
+description: 'Load agent and initialize validation report'
+
+nextStepFile: './v-02a-validate-metadata.md'
+validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
+agentMetadata: ../data/agent-metadata.md
+
+advancedElicitationTask: '{project-root}/_byan/workflow/simple/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_byan/workflow/simple/party-mode/workflow.md'
+---
+
+# Validate Step 1: Load Agent for Review
+
+## STEP GOAL:
+
+Load the existing agent file and initialize a validation report to track all findings.
+
+## MANDATORY EXECUTION RULES:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Step-Specific Rules:
+
+- 🎯 Load the complete agent file
+- 📊 Create validation report tracking document
+- 🚫 FORBIDDEN to proceed without user confirming correct agent
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load the complete agent YAML file
+- 📊 Parse and display agent summary
+- 💾 Create validation report document
+- 🚫 FORBIDDEN to proceed without user confirmation
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 1. Load Agent File
+
+Read the complete YAML from the agent file path provided by the user.
+If the module property of the agent metadata is stand-alone, it is not a module agent.
+If the module property of the agent is a module code (like bmm, bmb, etc...) it is a module agent.
+If the property hasSidecar: true exists in the metadata, then it is an expert agent.
+Else it is a simple agent.
+
+If a module agent also hasSidecar: true - this means it is a modules expert agent, thus it can have sidecar.
+
+### 2. Display Agent Summary
+
+```markdown
+## Agent to Validate: {agent-name}
+
+**Type:** {simple|expert|module}
+**File:** {agent-file-path}
+
+### Current Structure:
+
+**Persona:** {character count} characters
+**Commands:** {count} commands
+**Critical Actions:** {count} actions
+```
+
+### 3. Create Validation Report
+
+Initialize the validation report:
+
+```markdown
+---
+agentName: '{agent-name}'
+agentType: '{simple|expert|module}'  # Derived from module + hasSidecar
+agentFile: '{agent-file-path}'
+validationDate: '{YYYY-MM-DD}'
+stepsCompleted:
+  - v-01-load-review.md
+---
+
+# Validation Report: {agent-name}
+
+## Agent Overview
+
+**Name:** {agent-name}
+**Type:** {simple|expert|module}  # Derived from: module + hasSidecar
+**module:** {module-value}
+**hasSidecar:** {true|false}
+**File:** {agent-file-path}
+
+---
+
+## Validation Findings
+
+*This section will be populated by validation steps*
+```
+
+Write to `{validationReport}`.
+
+### 4. Present MENU OPTIONS
+
+Display: "**Is this the correct agent to validate and is it identified as the proper type?** [A] Advanced Elicitation [P] Party Mode [C] Yes, Begin 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 C: Save to {validationReport}, then only then load, read entire file, then execute {nextStepFile}
+- 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
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [agent loaded and report created], will you then load and read fully `{nextStepFile}` to execute and begin validation.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Agent file loaded successfully
+- Validation report created
+- User confirmed correct agent
+
+### ❌ SYSTEM FAILURE:
+
+- Failed to load agent file
+- Report not created
+- Proceeded without user confirmation
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.