create-byan-agent 2.1.1 → 2.2.2

package/install/templates/_byan/bmb/workflows/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/_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...

package/install/templates/_byan/bmb/workflows/agent/steps-e/e-08c-edit-module.md

@@ -0,0 +1,123 @@
+---
+name: 'e-08c-edit-module'
+description: 'Apply edits to Module 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 (use expert as baseline for Module)
+expertTemplate: ../templates/expert-agent-template/expert-agent.template.md
+expertArch: ../data/expert-agent-architecture.md
+moduleArch: ../data/module-agent-validation.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 8c: Edit Module Agent
+
+## STEP GOAL:
+
+Apply all planned edits to the Module agent YAML file and manage workflow integration and sidecar structure.
+
+## 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 workflow integration paths for Module agents
+- 💾 Validate YAML and workflow 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 workflow paths
+- ✅ Validate YAML and workflow 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 - these are RULES that must be followed when editing agents:
+- `{expertTemplate}` - Module uses expert as baseline
+- `{expertArch}`, `{moduleArch}` - Architecture references
+- `{agentCompilation}`, `{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}`
+
+### 4. Apply Edits in Sequence
+
+**Type Conversion TO Module:**
+- Set `module` to module code (e.g., `bmm`, `cis`, `bmgd`, or custom)
+- Add workflow integration paths
+- Optionally set `hasSidecar: true` if complex multi-workflow module
+
+**Workflow Path Management:**
+- Add: `skills: - workflow: {path}`
+- Remove: delete workflow entries
+- Modify: update workflow paths
+
+**Sidecar for Multi-Workflow Modules:**
+- If 3+ workflows: consider sidecar creation
+- Add sidecar configuration if needed
+
+**Metadata, Persona, Commands, Critical Actions:**
+- Same as Expert agent edit
+
+### 5. Validate Workflow Paths
+
+After editing, confirm all workflow paths are valid:
+`{project-root}/_byan/{module-id}/workflows/{workflow-name}/workflow.md`
+
+### 6. Document Applied Edits
+
+Append to `{editPlan}` with workflow 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
+✅ Workflow paths validated
+✅ Sidecar structure correct (if applicable)
+
+## FAILURE MODES
+
+❌ Backup failed
+❌ YAML became invalid
+❌ Workflow paths broken
+❌ Edits not applied as specified
+
+---
+
+**Auto-advancing to post-edit validation...

package/install/templates/_byan/bmb/workflows/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/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_byan/core/workflows/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/bmb/workflows/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/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_byan/core/workflows/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.

package/install/templates/_byan/bmb/workflows/agent/steps-v/v-02a-validate-metadata.md

@@ -0,0 +1,116 @@
+---
+name: 'v-02a-validate-metadata'
+description: 'Validate metadata and append to report'
+
+nextStepFile: './v-02b-validate-persona.md'
+validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
+agentMetadata: ../data/agent-metadata.md
+agentFile: '{agent-file-path}'
+---
+
+# Validate Step 2a: Validate Metadata
+
+## STEP GOAL
+
+Validate the agent's metadata properties against BMAD standards as defined in agentMetadata.md. 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 agentMetadata first
+- 🔄 CRITICAL: Load the actual agent file to validate metadata
+- 🚫 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 metadata against agentMetadata.md rules
+- 📊 Append findings to validation report
+- 🚫 FORBIDDEN to present menu
+
+## EXECUTION PROTOCOLS
+
+- 🎯 Load agentMetadata.md reference
+- 🎯 Load the actual agent file for validation
+- 📊 Validate all metadata fields
+- 💾 Append findings to validation report
+- ➡️ 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 References
+
+Read `{agentMetadata}`, `{validationReport}`, and `{agentFile}`.
+
+### 2. Validate Metadata
+
+Perform these checks systematically - validate EVERY rule specified in agentMetadata.md:
+
+1. **Required Fields Existence**
+   - [ ] id: Present and non-empty
+   - [ ] name: Present and non-empty (display name)
+   - [ ] title: Present and non-empty
+   - [ ] icon: Present (emoji or symbol)
+   - [ ] module: Present and valid format
+   - [ ] hasSidecar: Present (boolean, if applicable)
+
+2. **Format Validation**
+   - [ ] id: Uses kebab-case, no spaces, unique identifier
+   - [ ] name: Clear display name for UI
+   - [ ] title: Concise functional description
+   - [ ] icon: Appropriate emoji or unicode symbol
+   - [ ] module: Either a 3-4 letter module code OR 'stand-alone'
+   - [ ] hasSidecar: Boolean value, matches actual agent structure
+
+3. **Content Quality**
+   - [ ] id: Unique and descriptive
+   - [ ] name: Clear and user-friendly
+   - [ ] title: Accurately describes agent's function
+   - [ ] icon: Visually representative of agent's purpose
+   - [ ] module: Correctly identifies module membership
+   - [ ] hasSidecar: Correctly indicates if agent uses sidecar files
+
+4. **Agent Type Consistency**
+   - [ ] If hasSidecar: true, sidecar folder path must be specified
+   - [ ] If module is a module code, agent is a module agent
+   - [ ] If module is 'stand-alone', agent is not part of a module
+   - [ ] No conflicting type indicators
+
+### 3. Append Findings to Report
+
+Append to `{validationReport}`:
+
+```markdown
+### Metadata Validation
+
+**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
+
+**Checks:**
+- [ ] id: kebab-case, no spaces, unique
+- [ ] name: clear display name
+- [ ] title: concise function description
+- [ ] icon: appropriate emoji/symbol
+- [ ] module: correct format (code or stand-alone)
+- [ ] hasSidecar: matches actual usage
+
+**Detailed Findings:**
+
+*PASSING:*
+{List of passing checks}
+
+*WARNINGS:*
+{List of non-blocking issues}
+
+*FAILURES:*
+{List of blocking issues that must be fixed}
+```
+
+### 4. Auto-Advance
+
+Load and execute `{nextStepFile}` immediately.
+
+---
+
+**Validating persona...**