bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.10

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

@@ -4,21 +4,17 @@ 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_folder}/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
 date: system-generated
 
-# Optional inputs for context
-recommended_inputs:
-  - problem_context: "Context document passed via data attribute"
-  - previous_attempts: "{output_folder}/problem-*.md"
-
 # Context can be provided via data attribute when invoking
 # 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_folder}/cis/workflows/problem-solving"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 
@@ -27,3 +23,16 @@ solving_methods: "{installed_path}/solving-methods.csv"
 
 # Output configuration
 default_output_file: "{output_folder}/problem-solution-{{date}}.md"
+
+standalone: true
+
+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_folder}/cis/workflows/problem-solving/instructions.md"
+  template: "{bmad_folder}/cis/workflows/problem-solving/template.md"
+  web_bundle_files:
+    - "{bmad_folder}/cis/workflows/problem-solving/instructions.md"
+    - "{bmad_folder}/cis/workflows/problem-solving/template.md"
+    - "{bmad_folder}/cis/workflows/problem-solving/solving-methods.csv"

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

@@ -3,26 +3,33 @@
 ## Workflow
 
 <workflow>
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/{bmad_folder}/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>
 
 <step n="1" goal="Story Context Setup">
 
 <action>Check if context data was provided with workflow invocation</action>
-<check>If data attribute was passed to this workflow:</check>
-<action>Load the context document from the data file path</action>
-<action>Study the background information, brand details, or subject matter</action>
-<action>Use the provided context to inform story development</action>
-<action>Acknowledge the focused storytelling goal</action>
-<ask response="story_refinement">I see we're crafting a story based on the context provided. What specific angle or emphasis would you like?</ask>
-<check>Else (no context data provided):</check>
-<action>Proceed with context gathering</action>
-<ask response="story_purpose">1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study)</ask>
-<ask response="target_audience">2. Who is your target audience?</ask>
-<ask response="key_messages">3. What key messages or takeaways do you want the audience to have?</ask>
-<ask>4. Any constraints? (length, tone, medium, existing brand guidelines)</ask>
+
+<check if="data attribute was passed to this workflow">
+  <action>Load the context document from the data file path</action>
+  <action>Study the background information, brand details, or subject matter</action>
+  <action>Use the provided context to inform story development</action>
+  <action>Acknowledge the focused storytelling goal</action>
+  <ask response="story_refinement">I see we're crafting a story based on the context provided. What specific angle or emphasis would you like?</ask>
+</check>
+
+<check if="no context data provided">
+  <action>Proceed with context gathering</action>
+  <ask response="story_purpose">1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study)</ask>
+  <ask response="target_audience">2. Who is your target audience?</ask>
+  <ask response="key_messages">3. What key messages or takeaways do you want the audience to have?</ask>
+  <ask>4. Any constraints? (length, tone, medium, existing brand guidelines)</ask>
 
 <critical>Wait for user response before proceeding. This context shapes the narrative approach.</critical>
+</check>
 
 <template-output>story_purpose, target_audience, key_messages</template-output>
 
@@ -45,20 +52,29 @@ I can help craft your story using these proven narrative frameworks:
 3. **Customer Journey Story** - Before/after transformation narrative
 4. **Challenge-Overcome Arc** - Dramatic obstacle-to-victory structure
 
-**Strategic Narratives:** 5. **Brand Story** - Values, mission, and unique positioning 6. **Pitch Narrative** - Persuasive problem-to-solution structure 7. **Vision Narrative** - Future-focused aspirational story 8. **Origin Story** - Foundational narrative of how it began
+**Strategic Narratives:**
+
+5. **Brand Story** - Values, mission, and unique positioning
+6. **Pitch Narrative** - Persuasive problem-to-solution structure
+7. **Vision Narrative** - Future-focused aspirational story
+8. **Origin Story** - Foundational narrative of how it began
+
+**Specialized Narratives:**
 
-**Specialized Narratives:** 9. **Data Storytelling** - Transform insights into compelling narrative 10. **Emotional Hooks** - Craft powerful opening and touchpoints
+9. **Data Storytelling** - Transform insights into compelling narrative
+10. **Emotional Hooks** - Craft powerful opening and touchpoints
 
 Which framework best fits your purpose? (Enter 1-10, or ask for my recommendation)
 </ask>
 
-<check>If user asks for recommendation:</check>
-<action>Analyze story_purpose, target_audience, and key_messages</action>
-<action>Recommend best-fit framework with clear rationale</action>
-<example>
-Based on your {{story_purpose}} for {{target_audience}}, I recommend:
-**{{framework_name}}** because {{rationale}}
-</example>
+<check if="user asks for recommendation">
+  <action>Analyze story_purpose, target_audience, and key_messages</action>
+  <action>Recommend best-fit framework with clear rationale</action>
+  <example>
+  Based on your {{story_purpose}} for {{target_audience}}, I recommend:
+  **{{framework_name}}** because {{rationale}}
+  </example>
+</check>
 
 <template-output>story_type, framework_name</template-output>
 
@@ -177,8 +193,6 @@ The first moment determines if they keep reading/listening.
 
 <step n="6" goal="Write Core Narrative">
 
-<check>Ask if user wants to write or wants AI to write</check>
-
 <ask>Would you like to:
 
 1. Draft the story yourself with my guidance
@@ -186,13 +200,13 @@ The first moment determines if they keep reading/listening.
 3. Co-create it iteratively together
    </ask>
 
-<if selection="1">
+<if selection="1 or draft themselves">
   <action>Provide writing prompts and encouragement</action>
   <action>Offer feedback on drafts they share</action>
   <action>Suggest refinements for clarity, emotion, flow</action>
 </if>
 
-<if selection="2">
+<if selection="2 or ai writes the next draft based on discussions">
   <action>Synthesize all gathered elements</action>
   <action>Write complete narrative in appropriate tone/style</action>
   <action>Structure according to chosen framework</action>
@@ -200,7 +214,7 @@ The first moment determines if they keep reading/listening.
   <action>Present draft for feedback and refinement</action>
 </if>
 
-<if selection="3">
+<if selection="3 or work collaboratively with co-creation">
   <action>Write opening paragraph</action>
   <action>Get feedback and iterate</action>
   <action>Build section by section collaboratively</action>
@@ -245,16 +259,17 @@ Provide strategic guidance for story deployment:
 
 </step>
 
-<step n="9" goal="Refinement & Next Steps">
+<step n="9" goal="Refinement AND Next Steps">
 
 Polish and plan forward:
 
 <ask>What parts of the story feel strongest?</ask>
 <ask>What areas could use more refinement?</ask>
+<ask>What's the key resolution or call to action for your story?</ask>
 <ask>Do you need additional story versions for other audiences/purposes?</ask>
 <ask>How will you test this story with your audience?</ask>
 
-<template-output>refinement_opportunities, additional_versions, feedback_plan</template-output>
+<template-output>resolution, refinement_opportunities, additional_versions, feedback_plan</template-output>
 
 </step>
 
@@ -268,6 +283,9 @@ Compile all story components into the structured template:
 4. Verify tone and voice consistency
 5. Fill all template placeholders with actual content
 
+<action>Write final story document to {output_folder}/story-{{date}}.md</action>
+<action>Confirm completion with: "Story complete, {user_name}! Your narrative has been saved to {output_folder}/story-{{date}}.md"</action>
+
 <template-output>agent_role, agent_name, user_name, date</template-output>
 
 </step>

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

@@ -62,7 +62,7 @@
 
 {{key_messages}}
 
-## Variations & Adaptations
+## Variations AND Adaptations
 
 ### Short Version (Tweet/Social)
 
@@ -86,7 +86,7 @@
 
 {{audience_considerations}}
 
-### Tone & Voice Notes
+### Tone AND Voice Notes
 
 {{tone_notes}}
 

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

@@ -4,21 +4,17 @@ 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_folder}/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
 date: system-generated
 
-# Optional inputs for context
-recommended_inputs:
-  - story_context: "Context document passed via data attribute"
-  - previous_stories: "{output_folder}/story-*.md"
-
 # Context can be provided via data attribute when invoking
 # 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_folder}/cis/workflows/storytelling"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 
@@ -27,3 +23,16 @@ story_frameworks: "{installed_path}/story-types.csv"
 
 # Output configuration
 default_output_file: "{output_folder}/story-{{date}}.md"
+
+standalone: true
+
+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_folder}/cis/workflows/storytelling/instructions.md"
+  template: "{bmad_folder}/cis/workflows/storytelling/template.md"
+  web_bundle_files:
+    - "{bmad_folder}/cis/workflows/storytelling/instructions.md"
+    - "{bmad_folder}/cis/workflows/storytelling/template.md"
+    - "{bmad_folder}/cis/workflows/storytelling/story-types.csv"

package/src/utility/models/agent-activation-ide.xml

@@ -1,7 +1,7 @@
 <activation critical="MANDATORY">
   <init>
     <step n="1">Load persona from this current file containing this activation you are reading now</step>
-    <step n="2">Override with {project-root}/bmad/_cfg/agents/{agent-filename} if exists (replace, not merge)</step>
+    <step n="2">Override with {project-root}/{bmad_folder}/_cfg/agents/{agent-filename} if exists (replace, not merge)</step>
     <step n="3">Execute critical-actions section if present in current agent XML</step>
     <step n="4">Show greeting + numbered list of ALL commands IN ORDER from current agent's cmds section</step>
     <step n="5">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
@@ -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_folder}/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_folder}/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

package/src/utility/models/agent-activation-web.xml

@@ -0,0 +1,60 @@
+<activation critical="MANDATORY">
+  <init>
+    <step n="1">Load persona from this current agent xml block containing this activation you are reading now</step>
+    <step n="2">Show greeting + numbered list of ALL commands IN ORDER from current agent's cmds section</step>
+    <step n="3">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
+  </init>
+  <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_folder}/core/tasks/workflow.xml":
+      1. Find the &lt;file id="{bmad_folder}/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_folder}/" or "{project-root}/{bmad_folder}/" 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>
+  <commands critical="MANDATORY">
+    <input>Number → cmd[n] | Text → fuzzy match *commands</input>
+    <extract>exec, tmpl, data, action, run-workflow, validate-workflow</extract>
+    <handlers>
+      <handler type="run-workflow">
+        When command has: run-workflow="path/to/x.yaml" You MUST:
+        1. CRITICAL: Locate &lt;file id="{bmad_folder}/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.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>
+      <handler type="action">
+        When command has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When command has: action="text" → Execute the text directly as a critical action prompt
+      </handler>
+      <handler type="data">
+        When command has: data="path/to/x.json|yaml|yml"
+        Locate &lt;file id="path/to/x.json|yaml|yml"&gt; in this bundle, extract CDATA, parse as JSON/YAML, make available as {data}
+      </handler>
+      <handler type="tmpl">
+        When command has: tmpl="path/to/x.md"
+        Locate &lt;file id="path/to/x.md"&gt; in this bundle, extract CDATA, parse as markdown with {{mustache}} templates
+      </handler>
+      <handler type="exec">
+        When command has: exec="path"
+        Locate &lt;file id="path"&gt; in this bundle, extract CDATA, and EXECUTE that content
+      </handler>
+    </handlers>
+  </commands>
+  <rules critical="MANDATORY">
+    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
+  </rules>
+</activation>

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

@@ -0,0 +1 @@
+<critical>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.</critical>

package/src/utility/models/agent-in-team-activation.xml

@@ -0,0 +1,3 @@
+<activation critical="MANDATORY">
+
+</activation>

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

@@ -0,0 +1,8 @@
+<rules>
+  - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+  - 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 or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+  - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+</rules>

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

@@ -0,0 +1,16 @@
+<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_folder}/{{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/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>

package/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>

package/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>

package/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>

package/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_folder}/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/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_folder}/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/models/fragments/menu-handlers.xml

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

package/src/utility/models/fragments/web-bundle-activation-steps.xml

@@ -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_folder}/core/tasks/workflow.xml":
+    1. Find the &lt;file id="{bmad_folder}/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_folder}/" 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>

package/src/utility/templates/agent.customize.template.yaml

@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx bmad-method build <agent-name>
+
+# Override agent name
+agent:
+  metadata:
+    name: ""
+
+# Replace entire persona (not merged)
+persona:
+  role: ""
+  identity: ""
+  communication_style: ""
+  principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+#   - "User prefers detailed technical explanations"
+#   - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+#   - trigger: my-workflow
+#     workflow: "{project-root}/custom/my.yaml"
+#     description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+#   content: |
+#     Prompt instructions here