siesa-agents 2.1.78 → 2.1.79

package/bmad/bmb/workflows/agent/steps-e/e-01-load-existing.md

@@ -1,214 +0,0 @@
----
-name: 'e-01-load-existing'
-description: 'Load and analyze existing agent for editing'
-
-# File References
-thisStepFile: ./e-01-load-existing.md
-workflowFile: ../workflow.md
-nextStepFile: './e-02-discover-edits.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentMetadata: ../data/agent-metadata.md
-agentMenuPatterns: ../data/agent-menu-patterns.md
-
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Edit Step 1: Load Existing Agent
-
-## STEP GOAL:
-
-Load the existing agent file, parse its structure, and create an edit plan tracking document.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER proceed without loading the complete agent file
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not an autonomous editor
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are an agent analyst who helps users understand and modify existing agents
-- ✅ 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 agent architecture expertise, user brings their modification goals, together we achieve successful edits
-- ✅ Maintain collaborative analytical tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on loading and analyzing the existing agent
-- 🚫 FORBIDDEN to make any modifications in this step
-- 💬 Approach: Analytical and informative, present findings clearly
-- 📋 Ensure edit plan is created with complete agent snapshot
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load the complete agent YAML file
-- 📊 Parse and analyze all agent components
-- 💾 Create edit plan tracking document
-- 🚫 FORBIDDEN to proceed without confirming file loaded successfully
-
-## CONTEXT BOUNDARIES:
-
-- Available context: User provided agent file path from workflow
-- Focus: Load and understand the existing agent structure
-- Limits: Analysis only, no modifications
-- Dependencies: Agent file must exist and be valid YAML
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Load Agent File
-
-**Load the agent file:**
-Read the complete YAML from the agent file path provided by the user.
-
-**If file does not exist or is invalid:**
-Inform the user and request a valid path:
-"The agent file could not be loaded. Please verify the path and try again.
-
-Expected format: `{path-to-agent}/{agent-name}.agent.yaml`"
-
-### 2. Parse Agent Structure
-
-**Extract and categorize all agent components:**
-
-```yaml
-# Basic Metadata
-- name: {agent-name}
-- description: {agent-description}
-- type: {simple|expert|module}
-- version: {version}
-
-# Persona
-- persona: {full persona text}
-- system-context: {if present}
-
-# Commands/Menu
-- commands: {full command structure}
-
-# Critical Actions (if present)
-- critical-actions: {list}
-
-# Metadata
-- metadata: {all metadata fields}
-```
-
-### 3. Display Agent Summary
-
-**Present a clear summary to the user:**
-
-```markdown
-## Agent Analysis: {agent-name}
-
-**Type:** {simple|expert|module}
-**Version:** {version}
-**Status:** ready-for-edit
-
-### Current Structure:
-
-**Persona:** {character count} characters
-**Commands:** {count} commands defined
-**Critical Actions:** {count} critical actions
-
-### Editable Components:
-
-- [ ] Persona (role, identity, communication_style, principles)
-- [ ] Commands and menu structure
-- [ ] Critical actions
-- [ ] Metadata (name, description, version, tags)
-```
-
-### 4. Create Edit Plan Document
-
-**Initialize the edit plan tracking file:**
-
-```markdown
----
-mode: edit
-originalAgent: '{agent-file-path}'
-agentName: '{agent-name}'
-agentType: '{simple|expert|module}'
-editSessionDate: '{YYYY-MM-DD}'
-stepsCompleted:
-  - e-01-load-existing.md
----
-
-# Edit Plan: {agent-name}
-
-## Original Agent Snapshot
-
-**File:** {agent-file-path}
-**Type:** {simple|expert|module}
-**Version:** {version}
-
-### Current Persona
-
-{full persona text or truncated if very long}
-
-### Current Commands
-
-{list all commands with names and descriptions}
-
-### Current Metadata
-
-{all metadata fields}
-
----
-
-## Edits Planned
-
-*This section will be populated in subsequent steps*
-
----
-
-## Edits Applied
-
-*This section will track completed edits*
-```
-
-Write to `{editPlan}`.
-
-### 5. Present MENU OPTIONS
-
-Display: "**Is this the correct agent to edit?** [C] Yes, Continue to Discovery"
-
-#### Menu Handling Logic:
-
-- IF C: Save content 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
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [agent file loaded, analyzed, and edit plan created], will you then load and read fully `{nextStepFile}` to execute and begin edit discovery.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Agent file loaded successfully
-- YAML structure parsed correctly
-- Edit plan document created with agent snapshot
-- User has clear understanding of current agent structure
-- Menu presented and user input handled correctly
-
-### ❌ SYSTEM FAILURE:
-
-- Failed to load entire exist agent file (and potential sidecar content)
-- Invalid YAML format that prevents parsing
-- Edit plan not created
-- Proceeding without user confirmation of loaded agent
-
-**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-02-discover-edits.md

@@ -1,191 +0,0 @@
----
-name: 'e-02-discover-edits'
-description: 'Discover what user wants to change about the agent'
-
-nextStepFile: './e-03a-validate-metadata.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Edit Step 2: Discover Edits
-
-## STEP GOAL:
-
-Conduct targeted discovery to understand exactly what the user wants to change about their agent. Document all requested edits in structured format.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER assume what edits are needed - ask explicitly
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan first to understand agent context
-- 📋 YOU ARE A FACILITATOR, not an autonomous editor
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are an agent editor consultant who helps users clarify their modification goals
-- ✅ 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 agent architecture expertise, user brings their vision for improvements, together we define precise edits
-- ✅ Maintain collaborative inquisitive tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on discovering what to edit, not how to implement yet
-- 🚫 FORBIDDEN to make any modifications in this step
-- 💬 Approach: Ask probing questions to understand edit scope
-- 📋 Ensure all edits are documented to edit plan before proceeding
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Guide conversation to uncover all desired changes
-- 📊 Categorize edits by component (persona, commands, metadata, etc.)
-- 💾 Document all edits to edit plan
-- 🚫 FORBIDDEN to proceed without confirming all edits are captured
-
-## CONTEXT BOUNDARIES:
-
-- Available context: editPlan with agent snapshot from previous step
-- Focus: Discover what changes user wants to make
-- Limits: Discovery and documentation only, no implementation
-- Dependencies: Agent must be loaded in editPlan
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Read Edit Plan Context
-
-**Load the editPlan file first:**
-Read `{editPlan}` to understand the current agent structure and context.
-
-### 2. Present Edit Categories
-
-**Guide the user through potential edit areas:**
-
-"What would you like to change about **{agent-name}**?
-
-I can help you modify:
-
-**[P]ersona** - Role, identity, communication style, principles
-**[C]ommands** - Add, remove, or modify commands and menu structure
-**[M]etadata** - Name, description, version, tags, category
-**[A]ctions** - Critical actions and activation behaviors
-**[T]ype** - Convert between Simple/Expert/Module types
-**[O]ther** - Configuration, capabilities, system context
-
-Which areas would you like to edit? (You can select multiple)"
-
-### 3. Deep Dive Discovery
-
-**For each selected category, ask targeted questions:**
-
-#### If Persona selected:
-- "What aspect of the persona needs change?"
-- "Should the role be more specific or expanded?"
-- "Is the communication style hitting the right tone?"
-- "Do the principles need refinement?"
-
-#### If Commands selected:
-- "Do you want to add new commands, remove existing ones, or modify?"
-- "Are current command names and descriptions clear?"
-- "Should command steps be adjusted?"
-- "Is the menu structure working well?"
-
-#### If Metadata selected:
-- "What metadata fields need updating?"
-- "Is the description accurate and compelling?"
-- "Should version be bumped?"
-- "Are tags still relevant?"
-
-#### If Actions selected:
-- "What critical actions need modification?"
-- "Should new activation behaviors be added?"
-- "Are current actions executing as expected?"
-
-#### If Type conversion selected:
-- "What type are you converting from/to?"
-- "What's driving this conversion?"
-- "Are you aware of the implications (e.g., Expert needs sidecar)?"
-
-### 4. Document Edits to Plan
-
-**After discovery, append to editPlan:**
-
-```markdown
-## Edits Planned
-
-### Persona Edits
-- [ ] {edit description}
-- [ ] {edit description}
-
-### Command Edits
-- [ ] {edit description}
-- [ ] {edit description}
-
-### Metadata Edits
-- [ ] {edit description}
-- [ ] {edit description}
-
-### Critical Action Edits
-- [ ] {edit description}
-- [ ] {edit description}
-
-### Type Conversion
-- [ ] {from: X, to: Y, rationale: ...}
-
-### Other Edits
-- [ ] {edit description}
-```
-
-**Present summary for confirmation:**
-
-"Here's what I heard you want to change:
-
-{Summarize all edits in clear bulleted list}
-
-Did I capture everything? Any edits to add, remove, or clarify?"
-
-### 5. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to 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 edits 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
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [all edits documented and confirmed by user], will you then load and read fully `{nextStepFile}` to execute and begin validation.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All desired edits discovered and documented
-- Edits categorized by component type
-- User confirmed edit list is complete
-- Edit plan updated with structured edits
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding without documenting edits
-- Missing edits that user mentioned
-- Unclear or ambiguous edit descriptions
-- User not given opportunity to review/edit list
-
-**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-03a-validate-metadata.md

@@ -1,78 +0,0 @@
----
-name: 'e-03a-validate-metadata'
-description: 'Validate metadata (before edit) - no menu, auto-advance'
-
-nextStepFile: './e-03b-validate-persona.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentMetadata: ../data/agent-metadata.md
----
-
-# Edit Step 3a: Validate Metadata (Before Edit)
-
-## STEP GOAL:
-
-Validate the agent's metadata properties against BMAD standards. Record findings to editPlan and auto-advance to next validation step.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and agentMetadata 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 metadata against agentMetadata.md rules
-- 📊 Record findings to editPlan frontmatter
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentMetadata.md reference
-- 📊 Validate all metadata fields
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentMetadata}` to understand validation rules.
-Read `{editPlan}` to get agent file path and metadata.
-
-### 2. Validate Metadata
-
-Perform checks on:
-- **id**: kebab-case, no spaces
-- **name**: display name, clear branding
-- **title**: concise function description
-- **icon**: appropriate emoji or symbol
-- **module**: correct format `{project}:{type}:{name}`
-- **hasSidecar**: boolean, matches actual sidecar usage
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-validationBefore:
-  metadata:
-    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 metadata checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to persona validation...**

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

@@ -1,76 +0,0 @@
----
-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 +0,0 @@
----
-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 +0,0 @@
----
-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...**