agent updates

src/utility/models/fragments/activation-rules.xml

@@ -0,0 +1,7 @@
+<rules>
+  ALWAYS communicate in {communication_language}
+  Stay in character until exit selected
+  Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+  Number all lists, use letters for sub-options
+  Load files ONLY when executing menu items
+</rules>

src/utility/models/fragments/activation-steps.xml

@@ -0,0 +1,8 @@
+<step n="1">Load persona from this current agent file (already in context)</step>
+<step n="2">Load COMPLETE {project-root}/bmad/{module}/config.yaml and store ALL fields in persistent session memory as variables with syntax: {field_name}</step>
+<step n="3">Remember: user's name is {user_name}</step>
+{AGENT_SPECIFIC_STEPS}
+<step n="{MENU_STEP}">Show greeting using {user_name}, then display numbered list of ALL menu items from menu section</step>
+<step n="{HALT_STEP}">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
+<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

src/utility/models/fragments/handler-action.xml

@@ -0,0 +1,4 @@
+    <handler type="action">
+      When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+      When menu item has: action="text" → Execute the text directly as an inline instruction
+    </handler>

src/utility/models/fragments/handler-data.xml

@@ -0,0 +1,5 @@
+    <handler type="data">
+      When menu item has: data="path/to/file.json|yaml|yml|csv|xml"
+      Load the file first, parse according to extension
+      Make available as {data} variable to subsequent handler operations
+    </handler>

src/utility/models/fragments/handler-exec.xml

@@ -0,0 +1,5 @@
+    <handler type="exec">
+      When menu item has: exec="path/to/file.md"
+      Actually LOAD and EXECUTE the file at that path - do not improvise
+      Read the complete file and follow all instructions within it
+    </handler>

src/utility/models/fragments/handler-tmpl.xml

@@ -0,0 +1,5 @@
+    <handler type="tmpl">
+      When menu item has: tmpl="path/to/template.md"
+      Load template file, parse as markdown with {{mustache}} style variables
+      Make template content available as {template} to action/exec/workflow handlers
+    </handler>

src/utility/models/fragments/handler-validate-workflow.xml

@@ -0,0 +1,7 @@
+<handler type="validate-workflow">
+  When command has: validate-workflow="path/to/workflow.yaml"
+  1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.md
+  2. READ its entire contents and EXECUTE all instructions in that file
+  3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+  4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+</handler>

src/utility/models/fragments/handler-workflow.xml

@@ -0,0 +1,9 @@
+    <handler type="workflow">
+      When menu item has: workflow="path/to/workflow.yaml"
+      1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.md
+      2. Read the complete file - this is the CORE OS for executing BMAD workflows
+      3. Pass the yaml path as 'workflow-config' parameter to those instructions
+      4. Execute workflow.md instructions precisely following all steps
+      5. Save outputs after completing EACH workflow step (never batch multiple steps together)
+      6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
+    </handler>

src/utility/models/fragments/menu-handlers.xml

@@ -0,0 +1,6 @@
+<menu-handlers>
+  <extract>{DYNAMIC_EXTRACT_LIST}</extract>
+  <handlers>
+{DYNAMIC_HANDLERS}
+  </handlers>
+</menu-handlers>