bmad-method 6.0.0-alpha.16 → 6.0.0-alpha.18

package/src/modules/cis/agents/brainstorming-coach.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/cis/agents/brainstorming-coach.md"
+    id: "_bmad/cis/agents/brainstorming-coach.md"
     name: Carson
     title: Elite Brainstorming Specialist
     icon: 🧠
@@ -16,14 +16,14 @@ agent:
 
   menu:
     - trigger: brainstorm
-      workflow: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml"
+      workflow: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
       description: Guide me through Brainstorming any topic
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/creative-problem-solver.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/cis/agents/creative-problem-solver.md"
+    id: "_bmad/cis/agents/creative-problem-solver.md"
     name: Dr. Quinn
     title: Master Problem Solver
     icon: 🔬
@@ -16,14 +16,14 @@ agent:
 
   menu:
     - trigger: solve
-      workflow: "{project-root}/.bmad/cis/workflows/problem-solving/workflow.yaml"
+      workflow: "{project-root}/_bmad/cis/workflows/problem-solving/workflow.yaml"
       description: Apply systematic problem-solving methodologies
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/design-thinking-coach.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/cis/agents/design-thinking-coach.md"
+    id: "_bmad/cis/agents/design-thinking-coach.md"
     name: Maya
     title: Design Thinking Maestro
     icon: 🎨
@@ -16,14 +16,14 @@ agent:
 
   menu:
     - trigger: design
-      workflow: "{project-root}/.bmad/cis/workflows/design-thinking/workflow.yaml"
+      workflow: "{project-root}/_bmad/cis/workflows/design-thinking/workflow.yaml"
       description: Guide human-centered design process
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/innovation-strategist.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/cis/agents/innovation-strategist.md"
+    id: "_bmad/cis/agents/innovation-strategist.md"
     name: Victor
     title: Disruptive Innovation Oracle
     icon: ⚡
@@ -16,14 +16,14 @@ agent:
 
   menu:
     - trigger: innovate
-      workflow: "{project-root}/.bmad/cis/workflows/innovation-strategy/workflow.yaml"
+      workflow: "{project-root}/_bmad/cis/workflows/innovation-strategy/workflow.yaml"
       description: Identify disruption opportunities and business model innovation
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/presentation-master.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/cis/agents/presentation-master.md"
+    id: "_bmad/cis/agents/presentation-master.md"
     name: Caravaggio
     title: Visual Communication + Presentation Expert
     icon: 🎨
@@ -52,10 +52,10 @@ agent:
       description: Generate single expressive image that explains ideas creatively and memorably
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/storyteller/storyteller-sidecar/stories-told.md

@@ -0,0 +1,7 @@
+# Story Record Template
+
+Purpose: Record a log detailing the stories I have crafted over time for the user.
+
+## Narratives Told Table Record
+
+<!-- track stories created metadata with the user over time -->

package/src/modules/cis/agents/storyteller/storyteller-sidecar/story-preferences.md

@@ -0,0 +1,7 @@
+# Story Record Template
+
+Purpose: Record a log of learned users story telling or story building preferences.
+
+## User Preference Bullet List
+
+<!-- record any user preferences about story crafting the user prefers -->

package/src/modules/cis/agents/{storyteller.agent.yaml → storyteller/storyteller.agent.yaml}

@@ -2,11 +2,12 @@
 
 agent:
   metadata:
-    id: ".bmad/cis/agents/storyteller.md"
+    id: "_bmad/cis/agents/storyteller.md"
     name: Sophia
     title: Master Storyteller
     icon: 📖
     module: cis
+    hasSidecar: true
 
   persona:
     role: Expert Storytelling Guide + Narrative Strategist
@@ -14,16 +15,20 @@ agent:
     communication_style: Speaks like a bard weaving an epic tale - flowery, whimsical, every sentence enraptures and draws you deeper
     principles: Powerful narratives leverage timeless human truths. Find the authentic story. Make the abstract concrete through vivid details.
 
+  critical_actions:
+    - "Load COMPLETE file {project-root}/_bmad/_memory/storyteller-sidecar/story-preferences.md and review remember the User Preferences"
+    - "Load COMPLETE file {project-root}/_bmad/_memory/storyteller-sidecar/stories-told.md and review the history of stories created for this user"
+
   menu:
     - trigger: story
-      exec: "{project-root}/.bmad/cis/workflows/storytelling/workflow.yaml"
+      exec: "{project-root}/_bmad/cis/workflows/storytelling/workflow.yaml"
       description: Craft compelling narrative using proven frameworks
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/module.yaml

@@ -1,15 +1,11 @@
-# BMAD™ Creative Intelligence Suite Configuration
-
 code: cis
 name: "CIS: Creative Innovation Suite"
+header: "Creative Innovation Suite (CIS) Module"
+subheader: "No custom configuration required - uses Core settings only"
 default_selected: false # This module will not be selected by default for new installations
 
-header: "Creative Innovation Suite (CIS) Module"
-subheader: "No Configuration needed - uses Core Config only."
 # Variables from Core Config inserted:
 ## user_name
 ## communication_language
+## document_output_language
 ## output_folder
-## install_user_docs
-## kb_install
-

package/src/modules/cis/{README.md → readme.md}

@@ -103,7 +103,7 @@ agent cis/brainstorming-coach
 
 ## Configuration
 
-Edit `/.bmad/cis/config.yaml`:
+Edit `/_bmad/cis/config.yaml`:
 
 ```yaml
 output_folder: ./creative-outputs

package/src/modules/cis/workflows/README.md

@@ -98,7 +98,7 @@ agent cis/brainstorming-coach
 
 ## Configuration
 
-Edit `/.bmad/cis/config.yaml`:
+Edit `/_bmad/cis/config.yaml`:
 
 | Setting                | Purpose                 | Default            |
 | ---------------------- | ----------------------- | ------------------ |

package/src/modules/cis/workflows/design-thinking/instructions.md

@@ -1,7 +1,7 @@
 # Design Thinking Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/design-thinking/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/design-thinking/workflow.yaml</critical>
 <critical>Load and understand design methods from: {design_methods}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/src/modules/cis/workflows/design-thinking/workflow.yaml

@@ -4,7 +4,7 @@ description: "Guide human-centered design processes using empathy-driven methodo
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/.bmad/cis/config.yaml"
+config_source: "{project-root}/_bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ date: system-generated
 # Example: data="{path}/product-context.md" provides project context
 
 # Module path and component files
-installed_path: "{project-root}/.bmad/cis/workflows/design-thinking"
+installed_path: "{project-root}/_bmad/cis/workflows/design-thinking"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 
@@ -30,9 +30,9 @@ web_bundle:
   name: "design-thinking"
   description: "Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs."
   author: "BMad"
-  instructions: ".bmad/cis/workflows/design-thinking/instructions.md"
-  template: ".bmad/cis/workflows/design-thinking/template.md"
+  instructions: "_bmad/cis/workflows/design-thinking/instructions.md"
+  template: "_bmad/cis/workflows/design-thinking/template.md"
   web_bundle_files:
-    - ".bmad/cis/workflows/design-thinking/instructions.md"
-    - ".bmad/cis/workflows/design-thinking/template.md"
-    - ".bmad/cis/workflows/design-thinking/design-methods.csv"
+    - "_bmad/cis/workflows/design-thinking/instructions.md"
+    - "_bmad/cis/workflows/design-thinking/template.md"
+    - "_bmad/cis/workflows/design-thinking/design-methods.csv"

package/src/modules/cis/workflows/innovation-strategy/instructions.md

@@ -1,7 +1,7 @@
 # Innovation Strategy Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/innovation-strategy/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/innovation-strategy/workflow.yaml</critical>
 <critical>Load and understand innovation frameworks from: {innovation_frameworks}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/src/modules/cis/workflows/innovation-strategy/workflow.yaml

@@ -4,7 +4,7 @@ description: "Identify disruption opportunities and architect business model inn
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/.bmad/cis/config.yaml"
+config_source: "{project-root}/_bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ date: system-generated
 # Example: data="{path}/industry-analysis.md" provides market context
 
 # Module path and component files
-installed_path: "{project-root}/.bmad/cis/workflows/innovation-strategy"
+installed_path: "{project-root}/_bmad/cis/workflows/innovation-strategy"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 
@@ -30,9 +30,9 @@ web_bundle:
   name: "innovation-strategy"
   description: "Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities."
   author: "BMad"
-  instructions: ".bmad/cis/workflows/innovation-strategy/instructions.md"
-  template: ".bmad/cis/workflows/innovation-strategy/template.md"
+  instructions: "_bmad/cis/workflows/innovation-strategy/instructions.md"
+  template: "_bmad/cis/workflows/innovation-strategy/template.md"
   web_bundle_files:
-    - ".bmad/cis/workflows/innovation-strategy/instructions.md"
-    - ".bmad/cis/workflows/innovation-strategy/template.md"
-    - ".bmad/cis/workflows/innovation-strategy/innovation-frameworks.csv"
+    - "_bmad/cis/workflows/innovation-strategy/instructions.md"
+    - "_bmad/cis/workflows/innovation-strategy/template.md"
+    - "_bmad/cis/workflows/innovation-strategy/innovation-frameworks.csv"

package/src/modules/cis/workflows/problem-solving/instructions.md

@@ -1,7 +1,7 @@
 # Problem Solving Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/problem-solving/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/problem-solving/workflow.yaml</critical>
 <critical>Load and understand solving methods from: {solving_methods}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/src/modules/cis/workflows/problem-solving/workflow.yaml

@@ -4,7 +4,7 @@ description: "Apply systematic problem-solving methodologies to crack complex ch
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/.bmad/cis/config.yaml"
+config_source: "{project-root}/_bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ date: system-generated
 # Example: data="{path}/problem-brief.md" provides context
 
 # Module path and component files
-installed_path: "{project-root}/.bmad/cis/workflows/problem-solving"
+installed_path: "{project-root}/_bmad/cis/workflows/problem-solving"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 
@@ -30,9 +30,9 @@ web_bundle:
   name: "problem-solving"
   description: "Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks."
   author: "BMad"
-  instructions: ".bmad/cis/workflows/problem-solving/instructions.md"
-  template: ".bmad/cis/workflows/problem-solving/template.md"
+  instructions: "_bmad/cis/workflows/problem-solving/instructions.md"
+  template: "_bmad/cis/workflows/problem-solving/template.md"
   web_bundle_files:
-    - ".bmad/cis/workflows/problem-solving/instructions.md"
-    - ".bmad/cis/workflows/problem-solving/template.md"
-    - ".bmad/cis/workflows/problem-solving/solving-methods.csv"
+    - "_bmad/cis/workflows/problem-solving/instructions.md"
+    - "_bmad/cis/workflows/problem-solving/template.md"
+    - "_bmad/cis/workflows/problem-solving/solving-methods.csv"

package/src/modules/cis/workflows/storytelling/instructions.md

@@ -3,8 +3,8 @@
 ## Workflow
 
 <workflow>
-<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/storytelling/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/storytelling/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/src/modules/cis/workflows/storytelling/workflow.yaml

@@ -4,7 +4,7 @@ description: "Craft compelling narratives using proven story frameworks and tech
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/.bmad/cis/config.yaml"
+config_source: "{project-root}/_bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ date: system-generated
 # Example: data="{path}/brand-info.md" provides brand context
 
 # Module path and component files
-installed_path: "{project-root}/.bmad/cis/workflows/storytelling"
+installed_path: "{project-root}/_bmad/cis/workflows/storytelling"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 
@@ -30,9 +30,9 @@ web_bundle:
   name: "storytelling"
   description: "Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose."
   author: "BMad"
-  instructions: ".bmad/cis/workflows/storytelling/instructions.md"
-  template: ".bmad/cis/workflows/storytelling/template.md"
+  instructions: "_bmad/cis/workflows/storytelling/instructions.md"
+  template: "_bmad/cis/workflows/storytelling/template.md"
   web_bundle_files:
-    - ".bmad/cis/workflows/storytelling/instructions.md"
-    - ".bmad/cis/workflows/storytelling/template.md"
-    - ".bmad/cis/workflows/storytelling/story-types.csv"
+    - "_bmad/cis/workflows/storytelling/instructions.md"
+    - "_bmad/cis/workflows/storytelling/template.md"
+    - "_bmad/cis/workflows/storytelling/story-types.csv"

package/src/utility/agent-components/activation-rules.txt

@@ -0,0 +1,7 @@
+  <rules>
+    <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
+    <!-- TTS_INJECTION:agent-tts -->
+    <r> Stay in character until exit selected</r>
+    <r> Display Menu items as the item dictates and in the order given.</r>
+    <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
+  </rules>

package/src/utility/agent-components/activation-steps.txt

@@ -0,0 +1,13 @@
+    <step n="1">Load persona from this current agent file (already in context)</step>
+    <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+        - Load and read {project-root}/_bmad/{{module}}/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} 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 cmd trigger or fuzzy command match</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>

package/src/utility/agent-components/agent-command-header.md

@@ -0,0 +1 @@
+You must fully embody this agent's persona and follow all activation instructions, steps and rules exactly as specified. NEVER break character until given an exit command.

package/src/utility/{templates → agent-components}/agent.customize.template.yaml

@@ -1,6 +1,5 @@
 # Agent Customization
 # Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
 
 # Override agent name
 agent:

package/src/utility/agent-components/handler-action.txt

@@ -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>

package/src/utility/agent-components/handler-exec.txt

@@ -0,0 +1,6 @@
+    <handler type="exec">
+      When menu item or handler has: exec="path/to/file.md":
+      1. Actually LOAD and read the entire file and EXECUTE the file at that path - do not improvise
+      2. Read the complete file and follow all instructions within it
+      3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
+    </handler>

package/src/utility/agent-components/handler-multi.txt

@@ -0,0 +1,14 @@
+      <handler type="multi">
+         When menu item has: type="multi" with nested handlers
+         1. Display the multi item text as a single menu option
+         2. Parse all nested handlers within the multi item
+         3. For each nested handler:
+            - Use the 'match' attribute for fuzzy matching user input (or Exact Match of character code in brackets [])
+            - Execute based on handler attributes (exec, workflow, action)
+         4. When user input matches a handler's 'match' pattern:
+            - For exec="path/to/file.md": follow the `handler type="exec"` instructions
+            - For workflow="path/to/workflow.yaml": follow the `handler type="workflow"` instructions
+            - For action="...": Perform the specified action directly
+         5. Support both exact matches and fuzzy matching based on the match attribute
+         6. If no handler matches, prompt user to choose from available options
+      </handler>

package/src/utility/agent-components/handler-tmpl.txt

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

package/src/utility/agent-components/handler-validate-workflow.txt

@@ -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.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
+    </handler>

package/src/utility/agent-components/handler-workflow.txt

@@ -0,0 +1,10 @@
+    <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>

package/src/utility/agent-components/menu-handlers.txt

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

package/test/README.md

@@ -269,7 +269,7 @@ The validation is integrated into the GitHub Actions workflow:
 ## Dependencies
 
 - **zod**: Schema validation library
-- **js-yaml**: YAML parsing
+- **yaml**: YAML parsing
 - **glob**: File pattern matching
 - **c8**: Code coverage reporting
 

package/test/test-agent-schema.js

@@ -10,7 +10,7 @@
 
 const fs = require('node:fs');
 const path = require('node:path');
-const yaml = require('js-yaml');
+const yaml = require('yaml');
 const { validateAgentFile } = require('../tools/schema/agent.js');
 const { glob } = require('glob');
 
@@ -182,7 +182,7 @@ function runTest(filePath) {
     let agentData;
 
     try {
-      agentData = yaml.load(fileContent);
+      agentData = yaml.parse(fileContent);
     } catch (parseError) {
       // YAML parse error
       if (shouldPass) {