npm - siesa-agents - Versions diffs - 2.1.78 → 2.1.80 - Mend

siesa-agents 2.1.78 → 2.1.80

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (968) hide show

package/bmad/bmb/workflows/agent/steps-e/e-03e-validate-sidecar.md DELETED Viewed

@@ -1,78 +0,0 @@
----
-name: 'e-03e-validate-sidecar'
-description: 'Validate sidecar structure (before edit) - no menu, auto-advance'
-nextStepFile: './e-03f-validation-summary.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-expertValidation: ../data/expert-agent-validation.md
----
-# Edit Step 3e: Validate Sidecar (Before Edit)
-## STEP GOAL:
-Validate the agent's sidecar structure 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
-- 🚫 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}`.
-Read `{editPlan}` to get agent type.
-### 2. Conditional Validation
-**IF agentType == expert:**
-- Check metadata.sidecar-folder is present
-- Check sidecar-path is correct format
-- Verify sidecar files exist at specified path
-**IF agentType != expert:**
-- Mark as N/A (not applicable)
-- Skip detailed checks
-### 3. Record Findings
-Append to editPlan frontmatter:
-```yaml
-  sidecar:
-    status: [pass|fail|warning|n/a]
-    findings:
-      - {check}: [pass|fail|n/a]
-      - {check}: [pass|fail|n/a]
-```
-### 4. Auto-Advance
-When validation complete, 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-03f-validation-summary.md DELETED Viewed

@@ -1,119 +0,0 @@
----
-name: 'e-03f-validation-summary'
-description: 'Display all validation findings before edit'
-nextStepFile: './e-04-type-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 3f: Validation Summary (Before Edit)
-## STEP GOAL:
-Display all validation findings from the previous 5 validation steps to the user. Present findings clearly and await confirmation to proceed.
-## 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
-- 📊 Aggregate findings from all 5 validation steps
-- 💬 Present options for handling any issues found
-## EXECUTION PROTOCOLS:
-- 🎯 Read editPlan to get validation findings
-- 📊 Display organized summary
-- 💾 Allow user to decide how to proceed
-- ➡️ Proceed to edit plan on [C]
-## Sequence of Instructions:
-### 1. Load Validation Findings
-Read `{editPlan}` frontmatter to collect:
-- validationBefore.metadata.status and findings
-- validationBefore.persona.status and findings
-- validationBefore.menu.status and findings
-- validationBefore.structure.status and findings
-- validationBefore.sidecar.status and findings
-### 2. Display Validation Summary
-```markdown
-## Pre-Edit Validation Report for {agent-name}
-### Metadata Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-{Findings summary}
-### Persona Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-{Findings summary}
-### Menu Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-{Findings summary}
-### Structure Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-{Findings summary}
-### Sidecar Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL / N/A}
-{Findings summary}
-```
-### 3. Present Options
-"How would you like to proceed?
-**[I**ntegrate fixes**] - Add validation fixes to your edit plan
-**[S]kip** - Proceed with your planned edits only
-**[A]dvanced** - Deeper exploration of any issues"
-### 4. Present MENU OPTIONS
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Edit Plan"
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF I: Add validation fixes to editPlan, 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 begin edit planning.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- All validation findings displayed clearly
-- User given options for handling issues
-- Validation summary saved to editPlan
-### ❌ 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-04-type-metadata.md DELETED Viewed

@@ -1,122 +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}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/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
-## Sequence of Instructions:
-### 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/bmad/bmb/workflows/agent/steps-e/e-05-persona.md DELETED Viewed

@@ -1,132 +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}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/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
-## Sequence of Instructions:
-### 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/bmad/bmb/workflows/agent/steps-e/e-06-commands-menu.md DELETED Viewed

@@ -1,120 +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}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/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
-## Sequence of Instructions:
-### 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/bmad/bmb/workflows/agent/steps-e/e-07-activation.md DELETED Viewed

@@ -1,122 +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}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/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]
-## Sequence of Instructions:
-### 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}` metadataEdits.typeConversion.to or current agentType:
-```yaml
-agentType: simple → route to e-08a-edit-simple.md
-agentType: expert → route to e-08b-edit-expert.md
-agentType: module → route to e-08c-edit-module.md
-```
-### 4. Document to Edit Plan
-Append to `{editPlan}`:
-```yaml
-activationEdits:
-  criticalActions:
-    additions: []
-    modifications: []
-routing:
-  destinationEdit: {e-08a|e-08b|e-08c}
-  targetType: {simple|expert|module}
-```
-### 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 targetType, 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:
-- targetType: simple → e-08a-edit-simple.md
-- targetType: expert → e-08b-edit-expert.md
-- targetType: module → e-08c-edit-module.md
----
-## 🚨 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.