ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

name and language will now persisten better with most models

Browse Source
This commit is contained in:
Brian Madison
2025-10-04 16:12:42 -05:00
parent 67bf3b81c8
commit 94a2dad104
2 changed files with 14 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/utility/models/fragments/activation-rules.xml
View File

@@ -4,4 +4,6 @@
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>
EXCEPTION: Config file MUST be loaded at startup (step 2), all other files load only when executing menu items or an instruction file step
requires it
</rules>

15
src/utility/models/fragments/activation-steps.xml
View File

@@ -1,8 +1,15 @@
<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="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
- Use Read tool to load /Users/brianmadison/dev/v6install/bmad/bmb/config.yaml NOW
- Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
- VERIFY: If config not loaded, STOP and report error to user
- DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</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="{MENU_STEP}">Show greeting using {user_name} from config, communicate in {communication_language}, 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>
<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>