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

bundle agents front matter optimized, along with the orchestrators activation instructions;

Browse Source
This commit is contained in:
Brian Madison
2025-10-03 21:46:53 -05:00
parent 5ac18cb55c
commit 9e8c7f3503
86 changed files with 289 additions and 3227 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/utility/models/agent-activation-ide.xml
View File

@@ -12,15 +12,15 @@
<handlers>
<handler type="run-workflow">
When command has: run-workflow="path/to/x.yaml" You MUST:
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.md
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
2. READ its entire contents - the is the CORE OS for EXECUTING modules
3. Pass the yaml path as 'workflow-config' parameter to those instructions
4. Follow workflow.md instructions EXACTLY as written
4. Follow workflow.xml instructions EXACTLY as written
5. Save outputs after EACH section (never batch)
</handler>
<handler type="validate-workflow">
When command has: validate-workflow="path/to/workflow.yaml" You MUST:
1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.md
1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
2. READ its entire contents and EXECUTE all instructions in that file
3. Pass the workflow, and also check the workflow location for a checklist.md 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

10
src/utility/models/agent-activation-web.xml
View File

@@ -7,8 +7,8 @@
<bundled-files critical="MANDATORY">
<access-method>
All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
When you need to access a file path like "bmad/core/tasks/workflow.md":
1. Find the &lt;file id="bmad/core/tasks/workflow.md"&gt; element in this document
When you need to access a file path like "bmad/core/tasks/workflow.xml":
1. Find the &lt;file id="bmad/core/tasks/workflow.xml"&gt; element in this document
2. Extract the content from within the CDATA section
3. Use that content as if you read it from the filesystem
</access-method>
@@ -25,11 +25,11 @@
<handlers>
<handler type="run-workflow">
When command has: run-workflow="path/to/x.yaml" You MUST:
1. CRITICAL: Locate &lt;file id="bmad/core/tasks/workflow.md"&gt; in this XML bundle
1. CRITICAL: Locate &lt;file id="bmad/core/tasks/workflow.xml"&gt; in this XML bundle
2. Extract and READ its CDATA content - this is the CORE OS for EXECUTING workflows
3. Locate &lt;file id="path/to/x.yaml"&gt; for the workflow config
4. Pass the yaml content as 'workflow-config' parameter to workflow.md instructions
5. Follow workflow.md instructions EXACTLY as written
4. Pass the yaml content as 'workflow-config' parameter to workflow.xml instructions
5. Follow workflow.xml instructions EXACTLY as written
6. When workflow references other files, locate them by id in &lt;file&gt; elements
7. Save outputs after EACH section (never batch)
</handler>

2
src/utility/models/fragments/handler-validate-workflow.xml
View File

@@ -1,6 +1,6 @@
<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
1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
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

18
src/utility/models/fragments/handler-workflow.xml
View File

@@ -1,9 +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>
<handler type="workflow">
When menu item has: workflow="path/to/workflow.yaml"
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
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.xml 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>

32
src/utility/models/fragments/web-bundle-activation-steps.xml Normal file
View File

@@ -0,0 +1,32 @@
<step n="1">Load persona from this current agent XML block containing this activation you are reading now</step>
{AGENT_SPECIFIC_STEPS}
<step n="{MENU_STEP}">Show greeting + numbered list of ALL commands IN ORDER from current agent's menu section</step>
<step n="{HALT_STEP}">CRITICAL HALT. AWAIT user input. NEVER continue without it.</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>
<bundled-files critical="MANDATORY">
<access-method>
All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
When you need to access a file path like "bmad/core/tasks/workflow.xml":
1. Find the &lt;file id="bmad/core/tasks/workflow.xml"&gt; element in this document
2. Extract the content from within the CDATA section
3. Use that content as if you read it from the filesystem
</access-method>
<rules>
<rule>NEVER attempt to read files from filesystem - all files are bundled in this XML</rule>
<rule>File paths starting with "bmad/" or "{project-root}/bmad/" refer to &lt;file id="..."&gt; elements</rule>
<rule>When instructions reference a file path, locate the corresponding &lt;file&gt; element by matching the id attribute</rule>
<rule>YAML files are bundled with only their web_bundle section content (flattened to root level)</rule>
</rules>
</bundled-files>
<rules>
Stay in character until *exit
Number all option lists, use letters for sub-options
All file content is bundled in &lt;file&gt; elements - locate by id attribute
NEVER attempt filesystem operations - everything is in this XML
Menu triggers use asterisk (*) - display exactly as shown
</rules>