create-byan-agent 2.18.0 → 2.19.0

package/install/templates/_byan/bmb/workflows/agent/steps-e/e-04-type-metadata.md

@@ -1,124 +0,0 @@
----
-name: 'e-04-type-metadata'
-description: 'Review and plan metadata edits'
-
-nextStepFile: './e-05-persona.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentMetadata: ../data/agent-metadata.md
-agentTypesDoc: ../data/understanding-agent-types.md
-
-advancedElicitationTask: '{project-root}/_byan/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_byan/core/workflows/party-mode/workflow.md'
----
-
-# Edit Step 4: Type and Metadata
-
-## STEP GOAL:
-
-Review the agent's type and metadata, and plan any changes. If edits involve type conversion, identify the implications.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Load agentMetadata and agentTypesDoc first
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Load reference documents before discussing edits
-- 📊 Document type conversion requirements if applicable
-- 💬 Focus on metadata that user wants to change
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentMetadata.md and agentTypesDoc.md
-- 📊 Review current metadata from editPlan
-- 💾 Document planned metadata 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 `{agentMetadata}` and `{agentTypesDoc}` to understand validation rules and type implications.
-
-### 2. Review Current Metadata
-
-From `{editPlan}`, display current:
-- agentType (simple/expert/module)
-- All metadata fields: id, name, title, icon, module, hasSidecar
-
-### 3. Discuss Metadata Edits
-
-If user wants metadata changes:
-
-**For type conversion:**
-- "Converting from {current} to {target}"
-- Explain implications (e.g., Simple → Expert requires sidecar)
-- Update editPlan with type conversion
-
-**For metadata field changes:**
-- id: kebab-case requirements
-- name: display name conventions
-- title: function description format
-- icon: emoji/symbol
-- module: path format
-- hasSidecar: boolean implications
-
-### 4. Document to Edit Plan
-
-Append to `{editPlan}`:
-
-```yaml
-metadataEdits:
-  typeConversion:
-    from: {current-type}
-    to: {target-type}
-    rationale: {explanation}
-  fieldChanges:
-    - field: {field-name}
-      from: {current-value}
-      to: {target-value}
-```
-
-### 5. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Persona"
-
-#### 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 [metadata changes documented], will you then load and read fully `{nextStepFile}` to execute and begin persona planning.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Reference documents loaded
-- Metadata changes discussed and documented
-- Type conversion implications understood
-- Edit plan updated
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeded without loading reference documents
-- Type conversion without understanding implications
-- 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/bmb/workflows/agent/steps-e/e-05-persona.md

@@ -1,134 +0,0 @@
----
-name: 'e-05-persona'
-description: 'Review and plan persona edits'
-
-nextStepFile: './e-06-commands-menu.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-personaProperties: ../data/persona-properties.md
-principlesCrafting: ../data/principles-crafting.md
-communicationPresets: ../data/communication-presets.csv
-
-advancedElicitationTask: '{project-root}/_byan/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_byan/core/workflows/party-mode/workflow.md'
----
-
-# Edit Step 5: Persona
-
-## STEP GOAL:
-
-Review the agent's persona and plan any changes using the four-field persona system.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Load personaProperties, principlesCrafting, communicationPresets first
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Load reference documents before discussing persona edits
-- 📊 Maintain four-field system purity
-- 💬 Focus on persona fields that user wants to change
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load personaProperties.md, principlesCrafting.md, communicationPresets.csv
-- 📊 Review current persona from editPlan
-- 💾 Document planned persona 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 `{personaProperties}`, `{principlesCrafting}`, `{communicationPresets}` to understand the four-field system.
-
-### 2. Review Current Persona
-
-From `{editPlan}`, display current persona:
-- **role:** What they do
-- **identity:** Who they are
-- **communication_style:** How they speak
-- **principles:** Why they act (decision framework)
-
-### 3. Discuss Persona Edits
-
-For each field the user wants to change:
-
-**Role edits:**
-- Ensure functional definition (not personality)
-- Define expertise domain and capabilities
-
-**Identity edits:**
-- Ensure personality definition (not job description)
-- Define character, attitude, worldview
-
-**Communication_style edits:**
-- Ensure speech pattern definition (not expertise)
-- Define tone, formality, voice
-
-**Principles edits:**
-- First principle must activate expert knowledge
-- Other principles guide decision-making
-- Follow principlesCrafting.md guidance
-
-### 4. Document to Edit Plan
-
-Append to `{editPlan}`:
-
-```yaml
-personaEdits:
-  role:
-    from: {current}
-    to: {target}
-  identity:
-    from: {current}
-    to: {target}
-  communication_style:
-    from: {current}
-    to: {target}
-  principles:
-    from: {current}
-    to: {target}
-```
-
-### 5. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Commands Menu"
-
-#### 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 [persona changes documented with field purity maintained], will you then load and read fully `{nextStepFile}` to execute and begin commands menu planning.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Reference documents loaded
-- Four-field system purity maintained
-- Persona changes documented
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeded without loading reference documents
-- Field purity violated (mixed concepts)
-- 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/bmb/workflows/agent/steps-e/e-06-commands-menu.md

@@ -1,122 +0,0 @@
----
-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/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_byan/core/workflows/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/bmb/workflows/agent/steps-e/e-07-activation.md

@@ -1,125 +0,0 @@
----
-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/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_byan/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]
-
-## 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/bmb/workflows/agent/steps-e/e-08b-edit-expert.md

@@ -1,119 +0,0 @@
----
-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/_memory/{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...