siesa-agents 2.1.78 → 2.1.80

package/bmad/bmb/workflows/agent/steps-e/e-09e-validate-sidecar.md

@@ -1,70 +0,0 @@
----
-name: 'e-09e-validate-sidecar'
-description: 'Validate sidecar structure (after edit) - no menu, auto-advance'
-
-nextStepFile: './e-09f-validation-summary.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-expertValidation: ../data/expert-agent-validation.md
----
-
-# Edit Step 9e: Validate Sidecar (After Edit)
-
-## STEP GOAL:
-
-Validate the agent's sidecar structure after edits (if Expert type). Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and expertValidation 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 sidecar structure for Expert agents
-- 📊 Record findings to editPlan frontmatter (validationAfter section)
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load expertValidation.md reference
-- 📊 Validate sidecar if Expert type, skip for Simple/Module
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to validation summary when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{expertValidation}` and `{editPlan}` to get agent type.
-
-### 2. Conditional Validation
-
-**IF agentType == expert:** Check sidecar-folder, sidecar-path, file existence
-**IF agentType != expert:** Mark as N/A
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  sidecar:
-    status: [pass|fail|warning|n/a]
-    findings:
-      - {check}: [pass|fail|n/a]
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ Sidecar checks performed (or N/A recorded)
-✅ Findings saved to editPlan
-✅ Auto-advanced to validation summary
-
----
-
-**Auto-advancing to validation summary...**

package/bmad/bmb/workflows/agent/steps-e/e-09f-validation-summary.md

@@ -1,111 +0,0 @@
----
-name: 'e-09f-validation-summary'
-description: 'Display all validation findings after edit'
-
-nextStepFile: './e-10-celebrate.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 9f: Validation Summary (After Edit)
-
-## STEP GOAL:
-
-Display all post-edit validation findings and compare with pre-edit state. Present findings and await confirmation to proceed to celebration.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan to collect all validation findings
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Display all validation findings clearly organized
-- 📊 Compare before/after states
-- 💬 Present options for handling any remaining issues
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Read editPlan to get validation findings
-- 📊 Display organized summary with before/after comparison
-- 💾 Allow user to decide how to proceed
-
-## Sequence of Instructions:
-
-### 1. Load Validation Findings
-
-Read `{editPlan}` frontmatter to collect validationBefore and validationAfter findings.
-
-### 2. Display Validation Summary
-
-```markdown
-## Post-Edit Validation Report for {agent-name}
-
-### Before vs After Comparison
-
-| Component | Before | After | Status |
-|-----------|--------|-------|--------|
-| Metadata | {status} | {status} | {Δ} |
-| Persona | {status} | {status} | {Δ} |
-| Menu | {status} | {status} | {Δ} |
-| Structure | {status} | {status} | {Δ} |
-| Sidecar | {status} | {status} | {Δ} |
-
-### Detailed Findings (After Edit)
-
-**Metadata:** {summary}
-**Persona:** {summary}
-**Menu:** {summary}
-**Structure:** {summary}
-**Sidecar:** {summary}
-```
-
-### 3. Present Options
-
-"How do the edits look?
-
-**[R]eview** - Show detailed before/after for any component
-**[F]ix** - Address any remaining issues
-**[A]ccept** - Proceed to celebration"
-
-### 4. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Celebration"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF R: Show detailed before/after comparison, then redisplay menu
-- IF C: Save validation summary 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](#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 [validation summary displayed], will you then load and read fully `{nextStepFile}` to execute and celebrate completion.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All validation findings displayed clearly
-- Before/after comparison shown
-- User given options for handling issues
-
-### ❌ SYSTEM FAILURE:
-
-- Findings not displayed to user
-- Proceeding without user acknowledgment
-
-**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-10-celebrate.md

@@ -1,150 +0,0 @@
----
-name: 'e-10-celebrate'
-description: 'Celebrate successful agent edit completion'
-
-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 10: 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
-
-## Sequence of Instructions:
-
-### 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: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [X] Exit Workflow"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF X: Save completion status to {editPlan} and end workflow gracefully
-- 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
-- ONLY complete workflow when user selects 'X'
-- After other menu items execution, return to this menu
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [X exit option] is selected and [completion documented], will the workflow end gracefully with agent edit complete.
-
----
-
-## 🚨 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/bmad/bmb/workflows/agent/steps-v/v-01-load-review.md

@@ -1,128 +0,0 @@
----
-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}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/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
-
-## Sequence of Instructions:
-
-### 1. Load Agent File
-
-Read the complete YAML from the agent file path provided by the user.
-
-### 2. Display Agent Summary
-
-```markdown
-## Agent to Validate: {agent-name}
-
-**Type:** {simple|expert|module}
-**Version:** {version}
-**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}'
-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}
-**Version:** {version}
-**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?** [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/bmad/bmb/workflows/agent/steps-v/v-02a-validate-metadata.md

@@ -1,73 +0,0 @@
----
-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
----
-
-# Validate Step 2a: Validate Metadata
-
-## STEP GOAL:
-
-Validate the agent's metadata properties against BMAD standards. 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
-- 🚫 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
-- 📊 Validate all metadata fields
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentMetadata}` and `{validationReport}`.
-
-### 2. Validate Metadata
-
-Perform checks on: id, name, title, icon, module, hasSidecar.
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Metadata Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] id: kebab-case, no spaces
-- [ ] name: clear display name
-- [ ] title: concise function description
-- [ ] icon: appropriate emoji/symbol
-- [ ] module: correct format `{project}:{type}:{name}`
-- [ ] hasSidecar: matches actual usage
-
-**Findings:**
-{Detailed findings}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating persona...**

package/bmad/bmb/workflows/agent/steps-v/v-02b-validate-persona.md

@@ -1,72 +0,0 @@
----
-name: 'v-02b-validate-persona'
-description: 'Validate persona and append to report'
-
-nextStepFile: './v-02c-validate-menu.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-personaProperties: ../data/persona-properties.md
-principlesCrafting: ../data/principles-crafting.md
----
-
-# Validate Step 2b: Validate Persona
-
-## STEP GOAL:
-
-Validate the agent's persona against BMAD standards. 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 persona references first
-- 🚫 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 persona four-field system
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load personaProperties.md and principlesCrafting.md
-- 📊 Validate persona fields
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{personaProperties}`, `{principlesCrafting}`, and `{validationReport}`.
-
-### 2. Validate Persona
-
-Perform checks on: role, identity, communication_style, principles.
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Persona Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] role: specific, not generic
-- [ ] identity: defines who agent is
-- [ ] communication_style: speech patterns only
-- [ ] principles: first principle activates expert knowledge
-
-**Findings:**
-{Detailed findings}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating menu structure...**

package/bmad/bmb/workflows/agent/steps-v/v-02c-validate-menu.md

@@ -1,71 +0,0 @@
----
-name: 'v-02c-validate-menu'
-description: 'Validate menu structure and append to report'
-
-nextStepFile: './v-02d-validate-structure.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-agentMenuPatterns: ../data/agent-menu-patterns.md
----
-
-# Validate Step 2c: Validate Menu
-
-## STEP GOAL:
-
-Validate the agent's command menu structure against BMAD standards. 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 agentMenuPatterns first
-- 🚫 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 command/menu structure
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentMenuPatterns.md reference
-- 📊 Validate commands and menu
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentMenuPatterns}` and `{validationReport}`.
-
-### 2. Validate Menu
-
-Perform checks on: A/P/C convention, command names, descriptions.
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Menu Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] A/P/C convention followed
-- [ ] Command names clear and descriptive
-- [ ] Command descriptions specific and actionable
-- [ ] Menu handling logic properly specified
-
-**Findings:**
-{Detailed findings}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating YAML structure...**