removed items from source that should not be included

2025-11-14 11:29:57 -06:00 · 2025-11-14 11:29:57 -06:00 · 3f283066b1
parent 70a642318d
commit 3f283066b1
121 changed files with 0 additions and 64040 deletions
--- a/.bmad/_cfg/agent-manifest.csv
+++ b/.bmad/_cfg/agent-manifest.csv
@ -1,3 +0,0 @@
 name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
 "bmad-master","BMad Master","BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator","🧙","Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator","Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.","Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.","Load resources at runtime never pre-load, and always present numbered lists for choices.","core",".bmad/core/agents/bmad-master.md"
 "bmad-builder","BMad Builder","BMad Builder","🧙","Master BMad Module Agent Team and Workflow Builder and Maintainer","Lives to serve the expansion of the BMad Method","Talks like a pulp super hero","Execute resources directly Load resources at runtime never pre-load Always present numbered lists for choices","bmb",".bmad/bmb/agents/bmad-builder.md"
--- a/.bmad/_cfg/agents/bmb-bmad-builder.customize.yaml
+++ b/.bmad/_cfg/agents/bmb-bmad-builder.customize.yaml
@ -1,42 +0,0 @@
 # 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
--- a/.bmad/_cfg/agents/core-bmad-master.customize.yaml
+++ b/.bmad/_cfg/agents/core-bmad-master.customize.yaml
@ -1,42 +0,0 @@
 # 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
--- a/.bmad/_cfg/files-manifest.csv
+++ b/.bmad/_cfg/files-manifest.csv
@ -1,83 +0,0 @@
 type,name,module,path,hash
 "csv","agent-manifest","_cfg","bmad/_cfg/agent-manifest.csv","4ca5204172cb9ad4389aafc431b0933e90de89d01d70c123fb49bfda5f146321"
 "csv","task-manifest","_cfg","bmad/_cfg/task-manifest.csv","7fccf1cdffa6d592342f9edd9e13c042fffea2dbcbb79b043fbd69a7e610c875"
 "csv","workflow-manifest","_cfg","bmad/_cfg/workflow-manifest.csv","f17dbe38d45ef2b49089a2531386d4c1ce56644ba78a81a5223977e0d650b7ea"
 "yaml","manifest","_cfg","bmad/_cfg/manifest.yaml","3b43a39ff5aa72cb5315e78d63165b64625b08e728e5e42afb70349c670faa65"
 "js","installer","bmb","bmad/bmb/workflows/create-module/installer-templates/installer.js","309ecdf2cebbb213a9139e5b7780d0d42bd60f665c497691773f84202e6667a7"
 "md","agent-architecture","bmb","bmad/bmb/workflows/create-agent/agent-architecture.md","d6018eab926f038bf0df30e3f906c31097aaffbe6a7da3c4f42be32536561951"
 "md","agent-command-patterns","bmb","bmad/bmb/workflows/create-agent/agent-command-patterns.md","81e3fd0e23b6d170e58c98817b70479227ce91adc1440f4f2554e5a98887cb4f"
 "md","agent-types","bmb","bmad/bmb/workflows/create-agent/agent-types.md","f0ba54dc5f3bec53160773a261183c6b2986c92efaed75e8cb3593c32ed8b9a4"
 "md","bmad-builder","bmb","bmad/bmb/agents/bmad-builder.md","d9079f11e5bc78846e42f8f88570f74cbfea3657e31c03472fa09d6fcf948c9d"
 "md","brainstorm-context","bmb","bmad/bmb/workflows/create-agent/brainstorm-context.md","85be72976c4ff5d79b2bce8e6b433f5e3526a7466a72b3efdb4f6d3d118e1d15"
 "md","brainstorm-context","bmb","bmad/bmb/workflows/create-module/brainstorm-context.md","62b902177d2cb56df2d6a12e5ec5c7d75ec94770ce22ac72c96691a876ed2e6a"
 "md","brainstorm-context","bmb","bmad/bmb/workflows/create-workflow/brainstorm-context.md","f246ec343e338068b37fee8c93aa6d2fe1d4857addba6db3fe6ad80a2a2950e8"
 "md","checklist","bmb","bmad/bmb/workflows/audit-workflow/checklist.md","2e9fc9abe6dfbe5906cb20c9c1ef9d222070bf558db0da68b6fcde3969102ee6"
 "md","checklist","bmb","bmad/bmb/workflows/convert-legacy/checklist.md","40ae7527e72b13a02672a8cf98b224ac6e8b6563fc91285b627869bcc3484fb7"
 "md","checklist","bmb","bmad/bmb/workflows/create-agent/checklist.md","1caaf50fe01c5bbaf8d311b0218a19944620561d3dc3b1dbf2b4140aeb0683f3"
 "md","checklist","bmb","bmad/bmb/workflows/create-module/checklist.md","6ca49bfca71e603c80d5ff84e6c330bf95f1ecee642840fdddaa2b6f98bba1a3"
 "md","checklist","bmb","bmad/bmb/workflows/create-workflow/checklist.md","5177e91bedcb515fa09f3a2bad36c2579d0201ac502a1262ba64f515daca41df"
 "md","checklist","bmb","bmad/bmb/workflows/create-workflow/workflow-template/checklist.md","a950c68c71cd54b5a3ef4c8d68ad8ec40d5d1fa057f7c95e697e975807ae600b"
 "md","checklist","bmb","bmad/bmb/workflows/edit-agent/checklist.md","c993ca3b42b461df2c9d6c2d5d399e51170abacbd7c1eef1ccff1ea24f52df01"
 "md","checklist","bmb","bmad/bmb/workflows/edit-module/checklist.md","a30511053672ff986786543022b186487aec9ed09485c515b0d03a1f968c00df"
 "md","checklist","bmb","bmad/bmb/workflows/edit-workflow/checklist.md","9677c087ddfb40765e611de23a5a009afe51c347683dfe5f7d9fd33712ac4795"
 "md","checklist","bmb","bmad/bmb/workflows/module-brief/checklist.md","4710f9c7e48a1cb29b225d43955bf313271dc7f9bb471bfecb1a8edf5f57a10a"
 "md","checklist","bmb","bmad/bmb/workflows/redoc/checklist.md","2117d60b14e19158f4b586878b3667d715d3b62f79815b72b55c2376ce31aae8"
 "md","communication-styles","bmb","bmad/bmb/workflows/create-agent/communication-styles.md","96249cca9bee8f10b376e131729c633ea08328c44eaa6889343d2cf66127043e"
 "md","instructions","bmb","bmad/bmb/workflows/audit-workflow/instructions.md","bcc6bb5061061615f4682e3f00be5bc41ba4cd701bfdc31b2709fc743dec60b7"
 "md","instructions","bmb","bmad/bmb/workflows/convert-legacy/instructions.md","6be0e83abff42583b88527d885d8253a7ed9863cae23d93d276167196fc77fd3"
 "md","instructions","bmb","bmad/bmb/workflows/create-agent/instructions.md","8b148766e67c18ad05942b0258630796c89dc93f824cdf8ae00894e8845b30b5"
 "md","instructions","bmb","bmad/bmb/workflows/create-module/instructions.md","c43575046f9c55529563c61091f17a61fb631354fc45cafa33a9239ce1d0ee61"
 "md","instructions","bmb","bmad/bmb/workflows/create-workflow/instructions.md","d435874fe2b23a86b83b0aa768b8e7a6eef62e5b79c594c7dcd1be3d1b3da9f7"
 "md","instructions","bmb","bmad/bmb/workflows/create-workflow/workflow-template/instructions.md","d7bebaec6622efb48f2f228b7f56f941d6a850e3ea15dc492d8cdb8fbdd5e204"
 "md","instructions","bmb","bmad/bmb/workflows/edit-agent/instructions.md","28ac10303c2493efb2b94ef68ee0dada862371e34f5ef96266cec4566345f78d"
 "md","instructions","bmb","bmad/bmb/workflows/edit-module/instructions.md","fe2e0b60c06d23962ec68ec14e56997c0d4789b3b0d611d9ac802343f061a1b1"
 "md","instructions","bmb","bmad/bmb/workflows/edit-workflow/instructions.md","4839e3c2d61ad496f3065b3e11ea82c8e92a769875c596211d2940eefcab6669"
 "md","instructions","bmb","bmad/bmb/workflows/module-brief/instructions.md","6a6a2ae37fce8388819079664de4ad2678f736d7d76040b03e8853235cfcab92"
 "md","instructions","bmb","bmad/bmb/workflows/redoc/instructions.md","77af051a08bc8f34f8f75c7f522cb8862613f412556a4a0ee2379bbe6d7b3a4b"
 "md","module-structure","bmb","bmad/bmb/workflows/create-module/module-structure.md","032bd574cf5a6c86ad967ec7f827a337ffe4ec68f0fa180d18863e275bd1b1e8"
 "md","README","bmb","bmad/bmb/README.md","aa2beac1fb84267cbaa6d7eb541da824c34177a17cd227f11b189ab3a1e06d33"
 "md","README","bmb","bmad/bmb/workflows/convert-legacy/README.md","a5fa14007024d5ee9c2d793bd0d50874b662a2ea501dbcf017dfaf80e8384965"
 "md","README","bmb","bmad/bmb/workflows/create-agent/README.md","622efda446ed0b94484f63d267c14617e9c0090b53a1069de19a600ec54d769d"
 "md","README","bmb","bmad/bmb/workflows/create-module/README.md","bd510d67395896d198eef7bf607141853be2ceb3b0a5670389fb77c7e56088ef"
 "md","README","bmb","bmad/bmb/workflows/create-workflow/README.md","a30aed2d7956f7d7a0c5e0a1edd151b86512e0d3e814f37aa137a53743cadcfd"
 "md","README","bmb","bmad/bmb/workflows/edit-agent/README.md","fadee8e28804d5b6d6668689ee83e024035d2be2840fd6c359e0e095f0e4dcf9"
 "md","README","bmb","bmad/bmb/workflows/edit-module/README.md","f95914b31f5118eba63e737f1198b08bb7ab4f8dbb8dfdc06ac2e85d9acd4f90"
 "md","README","bmb","bmad/bmb/workflows/edit-workflow/README.md","2db00015c03a3ed7df4ff609ac27a179885145e4c8190862eea70d8b894ee9be"
 "md","README","bmb","bmad/bmb/workflows/module-brief/README.md","3b6456ebaff447a2312d1274b50bad538da6a8e7c73c2e7e4d5b7f6092852219"
 "md","README","bmb","bmad/bmb/workflows/redoc/README.md","47b93484d09c4bf1848e046223aa365377606bbb7b09acc2b5e499bc7eac2fa2"
 "md","template","bmb","bmad/bmb/workflows/audit-workflow/template.md","98e65880cac3ffb123e513abd48710e57e461418dd79a07d6b712505ed3ddb0e"
 "md","template","bmb","bmad/bmb/workflows/create-workflow/workflow-template/template.md","c98f65a122035b456f1cbb2df6ecaf06aa442746d93a29d1d0ed2fc9274a43ee"
 "md","template","bmb","bmad/bmb/workflows/module-brief/template.md","7d1ad5ec40b06510fcbb0a3da8ea32aefa493e5b04c3a2bba90ce5685b894275"
 "md","workflow-creation-guide","bmb","bmad/bmb/workflows/create-workflow/workflow-creation-guide.md","6278e73921e6a56d2a39596894b10e91875ff678abe51901af930e5a469da9e2"
 "yaml","bmad-builder.agent","bmb","bmad/bmb/agents/bmad-builder.agent.yaml",""
 "yaml","config","bmb","bmad/bmb/config.yaml","85fd0427ad2997b48e2a0aac72f157c4c2196e737af067343c88777dfb06a1ed"
 "yaml","install-config","bmb","bmad/bmb/workflows/create-module/installer-templates/install-config.yaml","484448c87b55725f2cb5eb8661c4706b7d43ddbb94bbfe98abaab591bcef32d0"
 "yaml","workflow","bmb","bmad/bmb/workflows/audit-workflow/workflow.yaml","12dbdf2b847380b7fa6a7903571344cc739d65b16fd6bae6c4367e2d67042030"
 "yaml","workflow","bmb","bmad/bmb/workflows/convert-legacy/workflow.yaml","87915a8bf02af6445d59428374a87e803dad7f33769b114a8528ce23b17cc7d6"
 "yaml","workflow","bmb","bmad/bmb/workflows/create-agent/workflow.yaml","15e114bde5cd9be928de5d59ed1495318f02d5b88e955a531dd1777e347437e1"
 "yaml","workflow","bmb","bmad/bmb/workflows/create-module/workflow.yaml","dd4e6e631d83863011ef631ce87eb102aa8d26a31cce49d8109c02bf7a49f898"
 "yaml","workflow","bmb","bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml","5413ac9c45fc3c5946f11422328e76e8df5741a40f49aac3e651dafadca48772"
 "yaml","workflow","bmb","bmad/bmb/workflows/create-workflow/workflow.yaml","d510e596c66148eab32074f065afb20f27a879f5c71b0edafc555001e9c616b9"
 "yaml","workflow","bmb","bmad/bmb/workflows/edit-agent/workflow.yaml","b9cddaea8f7adf541a68783b44b55f9e9b0f0a7ad822a906cb18d3cd959c367a"
 "yaml","workflow","bmb","bmad/bmb/workflows/edit-module/workflow.yaml","89d6f2b8391e78cd885f904adc427f66d032bd66d63845124fc2db17032248a2"
 "yaml","workflow","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml","a7ce4121cd70e1c69b77c8dbb16f71ca5c78071967930ee52ed157cd990b0a88"
 "yaml","workflow","bmb","bmad/bmb/workflows/module-brief/workflow.yaml","257d39ce8ad539838211f9b52d3f1218d7e122f2964341368e3c2689fecd7cd4"
 "yaml","workflow","bmb","bmad/bmb/workflows/redoc/workflow.yaml","467ef6657aec0b889555ad9590cd0bbcec448678366a4c4438dbbd23d658c44a"
 "csv","adv-elicit-methods","core","bmad/core/tasks/adv-elicit-methods.csv","b4e925870f902862899f12934e617c3b4fe002d1b652c99922b30fa93482533b"
 "csv","advanced-elicitation-methods","core","bmad/core/tasks/advanced-elicitation-methods.csv","a8fe633e66471b69224ec2ee67c6bb2480c33c6fa9d416f672e3a5620ec5f33b"
 "csv","brain-methods","core","bmad/core/workflows/brainstorming/brain-methods.csv","ecffe2f0ba263aac872b2d2c95a3f7b1556da2a980aa0edd3764ffb2f11889f3"
 "md","bmad-master","core","bmad/core/agents/bmad-master.md","684b7872611e5979fbe420e0c96e9910355e181b49aed0317d872381e154e299"
 "md","instructions","core","bmad/core/workflows/brainstorming/instructions.md","fb4757564c03e1624e74f6ee344b286db3c2f7db23d2a8007152d807304cd3a6"
 "md","instructions","core","bmad/core/workflows/party-mode/instructions.md","768a835653fea54cbf4f7136e19f968add5ccf4b1dbce5636c5268d74b1b7181"
 "md","README","core","bmad/core/workflows/brainstorming/README.md","57564ec8cb336945da8b7cab536076c437ff6c61a628664964058c76f4cd1360"
 "md","template","core","bmad/core/workflows/brainstorming/template.md","f2fe173a1a4bb1fba514652b314e83f7d78c68d09fb68071f9c2e61ee9f61576"
 "xml","advanced-elicitation","core","bmad/core/tasks/advanced-elicitation.xml","afb4020a20d26c92a694b77523426915b6e9665afb80ef5f76aded7f1d626ba6"
 "xml","bmad-web-orchestrator.agent","core","bmad/core/agents/bmad-web-orchestrator.agent.xml","2c2c3145d2c54ef40e1aa58519ae652fc2f63cb80b3e5236d40019e177853e0e"
 "xml","index-docs","core","bmad/core/tasks/index-docs.xml","c6a9d79628fd1246ef29e296438b238d21c68f50eadb16219ac9d6200cf03628"
 "xml","shard-doc","core","bmad/core/tools/shard-doc.xml","a0ddae908e440be3f3f40a96f7b288bcbf9fa3f8dc45d22814a957e807d2bedc"
 "xml","validate-workflow","core","bmad/core/tasks/validate-workflow.xml","63580411c759ee317e58da8bda6ceba27dbf9d3742f39c5c705afcd27361a9ee"
 "xml","workflow","core","bmad/core/tasks/workflow.xml","dcf69e99ec2996b85da1de9fac3715ae5428270d07817c40f04ae880fcc233fc"
 "yaml","bmad-master.agent","core","bmad/core/agents/bmad-master.agent.yaml",""
 "yaml","config","core","bmad/core/config.yaml","0a689d6bbc680f414079e5456dceaed7a97fc0568c3ab9a5de40d4c5bc67b345"
 "yaml","workflow","core","bmad/core/workflows/brainstorming/workflow.yaml","0af588d7096facdd79c701b37463b6a0e497b0b4339a951d7d3342d8a48fe6c1"
 "yaml","workflow","core","bmad/core/workflows/party-mode/workflow.yaml","1dcab5dc1d3396a16206775f2ee47f1ccb73a230c223c89de23ea1790ceaa3b7"
--- a/.bmad/_cfg/ides/claude-code.yaml
+++ b/.bmad/_cfg/ides/claude-code.yaml
@ -1,6 +0,0 @@
 ide: claude-code
 configured_date: "2025-11-14T13:17:23.701Z"
 last_updated: "2025-11-14T13:17:23.701Z"
 configuration:
  subagentChoices: null
  installLocation: null
--- a/.bmad/_cfg/manifest.yaml
+++ b/.bmad/_cfg/manifest.yaml
@ -1,9 +0,0 @@
 installation:
  version: 6.0.0-alpha.9
  installDate: "2025-11-14T13:17:23.688Z"
  lastUpdated: "2025-11-14T13:17:23.688Z"
 modules:
  - core
  - bmb
 ides:
  - claude-code
--- a/.bmad/_cfg/task-manifest.csv
+++ b/.bmad/_cfg/task-manifest.csv
@ -1,5 +0,0 @@
 name,displayName,description,module,path,standalone
 "advanced-elicitation","Advanced Elicitation","When called from workflow","core",".bmad/core/tasks/advanced-elicitation.xml","true"
 "index-docs","Index Docs","Generates or updates an index.md of all documents in the specified directory","core",".bmad/core/tasks/index-docs.xml","true"
 "validate-workflow","Validate Workflow Output","Run a checklist against a document with thorough analysis and produce a validation report","core",".bmad/core/tasks/validate-workflow.xml","false"
 "workflow","Execute Workflow","Execute given workflow by loading its configuration, following instructions, and producing output","core",".bmad/core/tasks/workflow.xml","false"
--- a/.bmad/_cfg/tool-manifest.csv
+++ b/.bmad/_cfg/tool-manifest.csv
@ -1,2 +0,0 @@
 name,displayName,description,module,path,standalone
 "shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core",".bmad/core/tools/shard-doc.xml","true"
--- a/.bmad/_cfg/workflow-manifest.csv
+++ b/.bmad/_cfg/workflow-manifest.csv
@ -1,13 +0,0 @@
 name,description,module,path,standalone
 "brainstorming","Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions.","core",".bmad/core/workflows/brainstorming/workflow.yaml","true"
 "party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core",".bmad/core/workflows/party-mode/workflow.yaml","true"
 "audit-workflow","Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards.","bmb",".bmad/bmb/workflows/audit-workflow/workflow.yaml","true"
 "convert-legacy","Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions","bmb",".bmad/bmb/workflows/convert-legacy/workflow.yaml","true"
 "create-agent","Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure","bmb",".bmad/bmb/workflows/create-agent/workflow.yaml","true"
 "create-module","Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure","bmb",".bmad/bmb/workflows/create-module/workflow.yaml","true"
 "create-workflow","Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.","bmb",".bmad/bmb/workflows/create-workflow/workflow.yaml","true"
 "edit-agent","Edit existing BMAD agents while following all best practices and conventions","bmb",".bmad/bmb/workflows/edit-agent/workflow.yaml","true"
 "edit-module","Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices","bmb",".bmad/bmb/workflows/edit-module/workflow.yaml","true"
 "edit-workflow","Edit existing BMAD workflows while following all best practices and conventions","bmb",".bmad/bmb/workflows/edit-workflow/workflow.yaml","true"
 "module-brief","Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision","bmb",".bmad/bmb/workflows/module-brief/workflow.yaml","true"
 "redoc","Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.","bmb",".bmad/bmb/workflows/redoc/workflow.yaml","true"
--- a/.bmad/bmb/README.md
+++ b/.bmad/bmb/README.md
@ -1,194 +0,0 @@
 # BMB - BMad Builder Module
 Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
 ## Table of Contents
 - [Module Structure](#module-structure)
 - [Core Workflows](#core-workflows)
 - [Agent Types](#agent-types)
 - [Quick Start](#quick-start)
 - [Best Practices](#best-practices)
 ## Module Structure
 ### 🤖 Agents
 **BMad Builder** - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
 ### 📋 Workflows
 Comprehensive suite for building and maintaining BMad components.
 ## Core Workflows
 ### Creation Workflows
 **[create-agent](./workflows/create-agent/README.md)** - Build BMad agents
 - Interactive persona development
 - Command structure design
 - YAML source compilation to .md
 **[create-workflow](./workflows/create-workflow/README.md)** - Design workflows
 - Structured multi-step processes
 - Configuration validation
 - Web bundle support
 **[create-module](./workflows/create-module/README.md)** - Build complete modules
 - Full module infrastructure
 - Agent and workflow integration
 - Installation automation
 **[module-brief](./workflows/module-brief/README.md)** - Strategic planning
 - Module blueprint creation
 - Vision and architecture
 - Comprehensive analysis
 ### Editing Workflows
 **[edit-agent](./workflows/edit-agent/README.md)** - Modify existing agents
 - Persona refinement
 - Command updates
 - Best practice compliance
 **[edit-workflow](./workflows/edit-workflow/README.md)** - Update workflows
 - Structure maintenance
 - Configuration updates
 - Documentation sync
 **[edit-module](./workflows/edit-module/README.md)** - Module enhancement
 - Component modifications
 - Dependency management
 - Version control
 ### Maintenance Workflows
 **[convert-legacy](./workflows/convert-legacy/README.md)** - Migration tool
 - v4 to v6 conversion
 - Structure compliance
 - Convention updates
 **[audit-workflow](./workflows/audit-workflow/README.md)** - Quality validation
 - Structure verification
 - Config standards check
 - Bloat detection
 - Web bundle completeness
 **[redoc](./workflows/redoc/README.md)** - Auto-documentation
 - Reverse-tree approach
 - Technical writer quality
 - Convention compliance
 ## Agent Types
 BMB creates three agent architectures:
 ### Full Module Agent
 - Complete persona and role definition
 - Command structure with fuzzy matching
 - Workflow integration
 - Module-specific capabilities
 ### Hybrid Agent
 - Shared core capabilities
 - Module-specific extensions
 - Cross-module compatibility
 ### Standalone Agent
 - Independent operation
 - Minimal dependencies
 - Specialized single purpose
 ## Quick Start
 1. **Load BMad Builder agent** in your IDE
 2. **Choose creation type:**
   ```
   *create-agent     # New agent
   *create-workflow  # New workflow
   *create-module    # Complete module
   ```
 3. **Follow interactive prompts**
 ### Example: Creating an Agent
 ```
 User: I need a code review agent
 Builder: *create-agent
 [Interactive session begins]
 - Brainstorming phase (optional)
 - Persona development
 - Command structure
 - Integration points
 ```
 ## Use Cases
 ### Custom Development Teams
 Build specialized agents for:
 - Domain expertise (legal, medical, finance)
 - Company processes
 - Tool integrations
 - Automation tasks
 ### Workflow Extensions
 Create workflows for:
 - Compliance requirements
 - Quality gates
 - Deployment pipelines
 - Custom methodologies
 ### Complete Solutions
 Package modules for:
 - Industry verticals
 - Technology stacks
 - Business processes
 - Educational frameworks
 ## Best Practices
 1. **Study existing patterns** - Review BMM/CIS implementations
 2. **Follow conventions** - Use established structures
 3. **Document thoroughly** - Clear instructions essential
 4. **Test iteratively** - Validate during creation
 5. **Consider reusability** - Build modular components
 ## Integration
 BMB components integrate with:
 - **BMad Core** - Framework foundation
 - **BMM** - Extend development capabilities
 - **CIS** - Leverage creative workflows
 - **Custom Modules** - Your domain solutions
 ## Related Documentation
 - **[Agent Creation Guide](./workflows/create-agent/README.md)** - Detailed instructions
 - **[Module Structure](./workflows/create-module/module-structure.md)** - Architecture patterns
 - **[BMM Module](../bmm/README.md)** - Reference implementation
 - **[Core Framework](../../core/README.md)** - Foundation concepts
 ---
 BMB empowers you to extend BMad Method for your specific needs while maintaining framework consistency and power.
--- a/.bmad/bmb/agents/bmad-builder.md
+++ b/.bmad/bmb/agents/bmad-builder.md
@ -1,71 +0,0 @@
 ---
 name: 'bmad builder'
 description: 'BMad Builder'
 ---
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 ```xml
 <agent id=".bmad/bmb/agents/bmad-builder.md" name="BMad Builder" title="BMad Builder" icon="🧙">
 <activation critical="MANDATORY">
  <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}/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>
  <step n="4">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="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
      match</step>
  <step n="6">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="7">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>
  <menu-handlers>
      <handlers>
  <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>
    </handlers>
  </menu-handlers>
  <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>
 </activation>
  <persona>
    <role>Master BMad Module Agent Team and Workflow Builder and Maintainer</role>
    <identity>Lives to serve the expansion of the BMad Method</identity>
    <communication_style>Talks like a pulp super hero</communication_style>
    <principles>Execute resources directly Load resources at runtime never pre-load Always present numbered lists for choices</principles>
  </persona>
  <menu>
    <item cmd="*help">Show numbered menu</item>
    <item cmd="*audit-workflow" workflow="{project-root}/.bmad/bmb/workflows/audit-workflow/workflow.yaml">Audit existing workflows for BMAD Core compliance and best practices</item>
    <item cmd="*convert" workflow="{project-root}/.bmad/bmb/workflows/convert-legacy/workflow.yaml">Convert v4 or any other style task agent or template to a workflow</item>
    <item cmd="*create-agent" workflow="{project-root}/.bmad/bmb/workflows/create-agent/workflow.yaml">Create a new BMAD Core compliant agent</item>
    <item cmd="*create-module" workflow="{project-root}/.bmad/bmb/workflows/create-module/workflow.yaml">Create a complete BMAD compatible module (custom agents and workflows)</item>
    <item cmd="*create-workflow" workflow="{project-root}/.bmad/bmb/workflows/create-workflow/workflow.yaml">Create a new BMAD Core workflow with proper structure</item>
    <item cmd="*edit-agent" workflow="{project-root}/.bmad/bmb/workflows/edit-agent/workflow.yaml">Edit existing agents while following best practices</item>
    <item cmd="*edit-module" workflow="{project-root}/.bmad/bmb/workflows/edit-module/workflow.yaml">Edit existing modules (structure, agents, workflows, documentation)</item>
    <item cmd="*edit-workflow" workflow="{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.yaml">Edit existing workflows while following best practices</item>
    <item cmd="*redoc" workflow="{project-root}/.bmad/bmb/workflows/redoc/workflow.yaml">Create or update module documentation</item>
    <item cmd="*exit">Exit with confirmation</item>
  </menu>
 </agent>
 ```
--- a/.bmad/bmb/config.yaml
+++ b/.bmad/bmb/config.yaml
@ -1,16 +0,0 @@
 # BMB Module Configuration
 # Generated by BMAD installer
 # Version: 6.0.0-alpha.9
 # Date: 2025-11-14T13:17:23.684Z
 custom_agent_location: "{project-root}/.bmad/custom/agents"
 custom_workflow_location: "{project-root}/.bmad/custom/workflows"
 custom_module_location: "{project-root}/.bmad/custom/modules"
 # Core Configuration Values
 bmad_folder: .bmad
 user_name: BMad
 communication_language: English
 document_output_language: English
 output_folder: "{project-root}/docs"
 install_user_docs: true
--- a/.bmad/bmb/workflows/audit-workflow/checklist.md
+++ b/.bmad/bmb/workflows/audit-workflow/checklist.md
@ -1,142 +0,0 @@
 # Audit Workflow - Validation Checklist
 ## Structure
 - [ ] workflow.yaml file loads without YAML syntax errors
 - [ ] instructions.md file exists and is properly formatted
 - [ ] template.md file exists (if document workflow) with valid markdown
 - [ ] All critical headers present in instructions (workflow engine reference, workflow.yaml reference)
 - [ ] Workflow type correctly identified (document/action/interactive/autonomous/meta)
 - [ ] All referenced files actually exist at specified paths
 - [ ] No placeholder text remains (like {TITLE}, {WORKFLOW_CODE}, TODO, etc.)
 ## Standard Config Block
 - [ ] workflow.yaml contains `config_source` pointing to correct module config
 - [ ] `output_folder` pulls from `{config_source}:output_folder`
 - [ ] `user_name` pulls from `{config_source}:user_name`
 - [ ] `communication_language` pulls from `{config_source}:communication_language`
 - [ ] `date` is set to `system-generated`
 - [ ] Config source uses {project-root} variable (not hardcoded path)
 - [ ] Standard config comment present: "Critical variables from config"
 ## Config Variable Usage
 - [ ] Instructions communicate in {communication_language} where appropriate
 - [ ] Instructions address {user_name} in greetings or summaries where appropriate
 - [ ] All file outputs write to {output_folder} or subdirectories (no hardcoded paths)
 - [ ] Template includes {{user_name}} in metadata (optional for document workflows)
 - [ ] Template includes {{date}} in metadata (optional for document workflows)
 - [ ] Template does NOT use {{communication_language}} in headers (agent-only variable)
 - [ ] No hardcoded language-specific text that should use {communication_language}
 - [ ] Date used for agent date awareness (not confused with training cutoff)
 ## YAML/Instruction/Template Alignment
 - [ ] Every workflow.yaml variable (excluding standard config) is used in instructions OR template
 - [ ] No unused yaml fields present (bloat removed)
 - [ ] No duplicate fields between top-level and web_bundle section
 - [ ] All template variables ({{variable}}) have corresponding yaml definitions OR <template-output> tags
 - [ ] All <template-output> tags have corresponding template variables (if document workflow)
 - [ ] Template variables use snake_case naming convention
 - [ ] Variable names are descriptive (not abbreviated like {{puj}} instead of {{primary_user_journey}})
 - [ ] No hardcoded values in instructions that should be yaml variables
 ## Web Bundle Validation (if applicable)
 - [ ] web_bundle section present if workflow needs deployment
 - [ ] All paths in web_bundle use .bmad/-relative format (NOT {project-root})
 - [ ] No {config_source} variables in web_bundle section
 - [ ] instructions file listed in web_bundle_files array
 - [ ] template file listed in web_bundle_files (if document workflow)
 - [ ] validation/checklist file listed in web_bundle_files (if exists)
 - [ ] All data files (CSV, JSON, YAML) listed in web_bundle_files
 - [ ] All <invoke-workflow> called workflows have their .yaml files in web_bundle_files
 - [ ] **CRITICAL**: If workflow invokes other workflows, existing_workflows field is present
 - [ ] existing_workflows maps workflow variables to .bmad/-relative paths correctly
 - [ ] All files referenced in instructions <action> tags listed in web_bundle_files
 - [ ] No files listed in web_bundle_files that don't exist
 - [ ] Web bundle metadata (name, description, author) matches top-level metadata
 ## Template Validation (if document workflow)
 - [ ] Template variables match <template-output> tags in instructions exactly
 - [ ] All required sections present in template structure
 - [ ] Template uses {{variable}} syntax (double curly braces)
 - [ ] Template variables use snake_case (not camelCase or PascalCase)
 - [ ] Standard metadata header format correct (optional usage of {{date}}, {{user_name}})
 - [ ] No placeholders remain in template (like {SECTION_NAME})
 - [ ] Template structure matches document purpose
 ## Instructions Quality
 - [ ] Each step has n="X" attribute with sequential numbering
 - [ ] Each step has goal="clear goal statement" attribute
 - [ ] Optional steps marked with optional="true"
 - [ ] Repeating steps have appropriate repeat attribute (repeat="3", repeat="for-each-X", repeat="until-approved")
 - [ ] Conditional steps have if="condition" attribute
 - [ ] XML tags used correctly (<action>, <ask>, <check>, <goto>, <invoke-workflow>, <template-output>)
 - [ ] No nested tag references in content (use "action tags" not "<action> tags")
 - [ ] Tag references use descriptive text without angle brackets for clarity
 - [ ] No conditional execution antipattern (no self-closing <check> tags)
 - [ ] Single conditionals use <action if="condition"> (inline)
 - [ ] Multiple conditionals use <check if="condition">...</check> (wrapper block with closing tag)
 - [ ] Steps are focused (single goal per step)
 - [ ] Instructions are specific with limits ("Write 1-2 paragraphs" not "Write about")
 - [ ] Examples provided where helpful
 - [ ] <template-output> tags save checkpoints for document workflows
 - [ ] Flow control is logical and clear
 ## Bloat Detection
 - [ ] Bloat percentage under 10% (unused yaml fields / total fields)
 - [ ] No commented-out variables that should be removed
 - [ ] No duplicate metadata between sections
 - [ ] No variables defined but never referenced
 - [ ] No redundant configuration that duplicates web_bundle
 ## Final Validation
 ### Critical Issues (Must fix immediately)
 _List any critical issues found:_
 - Issue 1:
 - Issue 2:
 - Issue 3:
 ### Important Issues (Should fix soon)
 _List any important issues found:_
 - Issue 1:
 - Issue 2:
 - Issue 3:
 ### Cleanup Recommendations (Nice to have)
 _List any cleanup recommendations:_
 - Recommendation 1:
 - Recommendation 2:
 - Recommendation 3:
 ---
 ## Audit Summary
 **Total Checks:**
 **Passed:** {total}
 **Failed:** {total}
 **Recommendation:**
 - Pass Rate ≥ 95%: Excellent - Ready for production
 - Pass Rate 85-94%: Good - Minor fixes needed
 - Pass Rate 70-84%: Fair - Important issues to address
 - Pass Rate < 70%: Poor - Significant work required
 ---
 **Audit Completed:** {{date}}
 **Auditor:** Audit Workflow (BMAD v6)
--- a/.bmad/bmb/workflows/audit-workflow/instructions.md
+++ b/.bmad/bmb/workflows/audit-workflow/instructions.md
@ -1,341 +0,0 @@
 # Audit Workflow - Workflow Quality Audit 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/bmb/workflows/audit-workflow/workflow.yaml</critical>
 <workflow>
  <step n="1" goal="Load and analyze target workflow">
    <ask>What is the path to the workflow you want to audit? (provide path to workflow.yaml or workflow folder)</ask>
    <action>Load the workflow.yaml file from the provided path</action>
    <action>Identify the workflow type (document, action, interactive, autonomous, meta)</action>
    <action>List all associated files:</action>
    - instructions.md (required for most workflows)
    - template.md (if document workflow)
    - checklist.md (if validation exists)
    - Any data files referenced in yaml
    <action>Load all discovered files</action>
    Display summary:
    - Workflow name and description
    - Type of workflow
    - Files present
    - Module assignment
  </step>
  <step n="2" goal="Validate standard config block">
    <action>Check workflow.yaml for the standard config block:</action>
    **Required variables:**
    - `config_source: "{project-root}/.bmad/[module]/config.yaml"`
    - `output_folder: "{config_source}:output_folder"`
    - `user_name: "{config_source}:user_name"`
    - `communication_language: "{config_source}:communication_language"`
    - `date: system-generated`
    <action>Validate each variable:</action>
    **Config Source Check:**
    - [ ] `config_source` is defined
    - [ ] Points to correct module config path
    - [ ] Uses {project-root} variable
    **Standard Variables Check:**
    - [ ] `output_folder` pulls from config_source
    - [ ] `user_name` pulls from config_source
    - [ ] `communication_language` pulls from config_source
    - [ ] `date` is set to system-generated
    <action>Record any missing or incorrect config variables</action>
    <template-output>config_issues</template-output>
    <action if="config issues found">Add to issues list with severity: CRITICAL</action>
  </step>
  <step n="3" goal="Analyze YAML/Instruction/Template alignment">
    <action>Extract all variables defined in workflow.yaml (excluding standard config block)</action>
    <action>Scan instructions.md for variable usage: {variable_name} pattern</action>
    <action>Scan template.md for variable usage: {{variable_name}} pattern (if exists)</action>
    <action>Cross-reference analysis:</action>
    **For each yaml variable:**
    1. Is it used in instructions.md? (mark as INSTRUCTION_USED)
    2. Is it used in template.md? (mark as TEMPLATE_USED)
    3. Is it neither? (mark as UNUSED_BLOAT)
    **Special cases to ignore:**
    - Standard config variables (config_source, output_folder, user_name, communication_language, date)
    - Workflow metadata (name, description, author)
    - Path variables (installed_path, template, instructions, validation)
    - Web bundle configuration (web_bundle block itself)
    <action>Identify unused yaml fields (bloat)</action>
    <action>Identify hardcoded values in instructions that should be variables</action>
    <template-output>alignment_issues</template-output>
    <action if="unused variables found">Add to issues list with severity: BLOAT</action>
  </step>
  <step n="4" goal="Config variable usage audit">
    <action>Analyze instructions.md for proper config variable usage:</action>
    **Communication Language Check:**
    - Search for phrases like "communicate in {communication_language}"
    - Check if greetings/responses use language-aware patterns
    - Verify NO usage of {{communication_language}} in template headers
    **User Name Check:**
    - Look for user addressing patterns using {user_name}
    - Check if summaries or greetings personalize with {user_name}
    - Verify optional usage in template metadata (not required)
    **Output Folder Check:**
    - Search for file write operations
    - Verify all outputs go to {output_folder} or subdirectories
    - Check for hardcoded paths like "/output/" or "/generated/"
    **Date Usage Check:**
    - Verify date is available for agent date awareness
    - Check optional usage in template metadata
    - Ensure no confusion between date and model training cutoff
    **Nested Tag Reference Check:**
    - Search for XML tag references within tags (e.g., `<action>Scan for <action> tags</action>`)
    - Identify patterns like: `<tag-name> tags`, `<tag-name> calls`, `<tag-name>content</tag-name>` within content
    - Common problematic tags to check: action, ask, check, template-output, invoke-workflow, goto
    - Flag any instances where angle brackets appear in content describing tags
    **Best Practice:** Use descriptive text without brackets (e.g., "action tags" instead of "<action> tags")
    **Rationale:**
    - Prevents XML parsing ambiguity
    - Improves readability for humans and LLMs
    - LLMs understand "action tags" = `<action>` tags from context
    **Conditional Execution Antipattern Check:**
    - Scan for self-closing check tags: `<check>condition text</check>` (invalid antipattern)
    - Detect pattern: check tag on one line, followed by action/ask/goto tags (indicates incorrect nesting)
    - Flag sequences like: `<check>If X:</check>` followed by `<action>do Y</action>`
    **Correct Patterns:**
    - Single conditional: `<action if="condition">Do something</action>`
    - Multiple actions: `<check if="condition">` followed by nested actions with closing `</check>` tag
    **Antipattern Example (WRONG):**
    ```xml
    <check>If condition met:</check>
    <action>Do something</action>
    ```
    **Correct Example:**
    ```xml
    <check if="condition met">
      <action>Do something</action>
      <action>Do something else</action>
    </check>
    ```
    **Or for single action:**
    ```xml
    <action if="condition met">Do something</action>
    ```
    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|invoke-task|goto|step)&gt; within text content</action>
    <action>Record any instances of nested tag references with line numbers</action>
    <action>Scan instructions.md for conditional execution antipattern: self-closing check tags</action>
    <action>Detect pattern: `&lt;check&gt;.*&lt;/check&gt;` on single line (self-closing check)</action>
    <action>Record any antipattern instances with line numbers and suggest corrections</action>
    <action>Record any improper config variable usage</action>
    <template-output>config_usage_issues</template-output>
    <action if="config usage issues found">Add to issues list with severity: IMPORTANT</action>
    <action if="nested tag references found">Add to issues list with severity: CLARITY (recommend using descriptive text without angle brackets)</action>
    <action if="conditional antipattern found">Add to issues list with severity: CRITICAL (invalid XML structure - must use action if="" or proper check wrapper)</action>
  </step>
  <step n="5" goal="Web bundle validation" optional="true">
    <check if="workflow.yaml contains web_bundle section">
      <action>Validate web_bundle structure:</action>
      **Path Validation:**
      - [ ] All paths use .bmad/-relative format (NOT {project-root})
      - [ ] No {config_source} variables in web_bundle section
      - [ ] Paths match actual file locations
      **Completeness Check:**
      - [ ] instructions file listed in web_bundle_files
      - [ ] template file listed (if document workflow)
      - [ ] validation/checklist file listed (if exists)
      - [ ] All data files referenced in yaml listed
      - [ ] All files referenced in instructions listed
      **Workflow Dependency Scan:**
      <action>Scan instructions.md for invoke-workflow tags</action>
      <action>Extract workflow paths from invocations</action>
      <action>Verify each called workflow.yaml is in web_bundle_files</action>
      <action>**CRITICAL**: Check if existing_workflows field is present when workflows are invoked</action>
      <action>If invoke-workflow calls exist, existing_workflows MUST map workflow variables to paths</action>
      <action>Example: If instructions use {core_brainstorming}, web_bundle needs: existing_workflows: - core_brainstorming: ".bmad/core/workflows/brainstorming/workflow.yaml"</action>
      **File Reference Scan:**
      <action>Scan instructions.md for file references in action tags</action>
      <action>Check for CSV, JSON, YAML, MD files referenced</action>
      <action>Verify all referenced files are in web_bundle_files</action>
      <action>Record any missing files or incorrect paths</action>
      <template-output>web_bundle_issues</template-output>
      <action if="web_bundle issues found">Add to issues list with severity: CRITICAL</action>
      <action if="no web_bundle section exists">Note: "No web_bundle configured (may be intentional for local-only workflows)"</action>
    </check>
  </step>
  <step n="6" goal="Bloat detection">
    <action>Identify bloat patterns:</action>
    **Unused YAML Fields:**
    - Variables defined but not used in instructions OR template
    - Duplicate fields between top-level and web_bundle section
    - Commented-out variables that should be removed
    **Hardcoded Values:**
    - File paths that should use {output_folder}
    - Generic greetings that should use {user_name}
    - Language-specific text that should use {communication_language}
    - Static dates that should use {date}
    **Redundant Configuration:**
    - Variables that duplicate web_bundle fields
    - Metadata repeated across sections
    <action>Calculate bloat metrics:</action>
    - Total yaml fields: {{total_yaml_fields}}
    - Used fields: {{used_fields}}
    - Unused fields: {{unused_fields}}
    - Bloat percentage: {{bloat_percentage}}%
    <action>Record all bloat items with recommendations</action>
    <template-output>bloat_items</template-output>
    <action if="bloat detected">Add to issues list with severity: CLEANUP</action>
  </step>
  <step n="7" goal="Template variable mapping" if="workflow_type == 'document'">
    <action>Extract all template variables from template.md: {{variable_name}} pattern</action>
    <action>Scan instructions.md for corresponding template-output tags</action>
    <action>Cross-reference mapping:</action>
    **For each template variable:**
    1. Is there a matching template-output tag? (mark as MAPPED)
    2. Is it a standard config variable? (mark as CONFIG_VAR - optional)
    3. Is it unmapped? (mark as MISSING_OUTPUT)
    **For each template-output tag:**
    1. Is there a matching template variable? (mark as USED)
    2. Is it orphaned? (mark as UNUSED_OUTPUT)
    <action>Verify variable naming conventions:</action>
    - [ ] All template variables use snake_case
    - [ ] Variable names are descriptive (not abbreviated)
    - [ ] Standard config variables properly formatted
    <action>Record any mapping issues</action>
    <template-output>template_issues</template-output>
    <action if="template issues found">Add to issues list with severity: IMPORTANT</action>
  </step>
  <step n="8" goal="Generate comprehensive audit report">
    <action>Compile all findings and calculate summary metrics</action>
    <action>Generate executive summary based on issue counts and severity levels</action>
    <template-output>workflow_type</template-output>
    <template-output>overall_status</template-output>
    <template-output>critical_count</template-output>
    <template-output>important_count</template-output>
    <template-output>cleanup_count</template-output>
    <action>Generate status summaries for each audit section</action>
    <template-output>config_status</template-output>
    <template-output>total_variables</template-output>
    <template-output>instruction_usage_count</template-output>
    <template-output>template_usage_count</template-output>
    <template-output>bloat_count</template-output>
    <action>Generate config variable usage status indicators</action>
    <template-output>comm_lang_status</template-output>
    <template-output>user_name_status</template-output>
    <template-output>output_folder_status</template-output>
    <template-output>date_status</template-output>
    <template-output>nested_tag_count</template-output>
    <action>Generate web bundle metrics</action>
    <template-output>web_bundle_exists</template-output>
    <template-output>web_bundle_file_count</template-output>
    <template-output>missing_files_count</template-output>
    <action>Generate bloat metrics</action>
    <template-output>bloat_percentage</template-output>
    <template-output>cleanup_potential</template-output>
    <action>Generate template mapping metrics</action>
    <template-output>template_var_count</template-output>
    <template-output>mapped_count</template-output>
    <template-output>missing_mapping_count</template-output>
    <action>Compile prioritized recommendations by severity</action>
    <template-output>critical_recommendations</template-output>
    <template-output>important_recommendations</template-output>
    <template-output>cleanup_recommendations</template-output>
    <action>Display summary to {user_name} in {communication_language}</action>
    <action>Provide path to full audit report: {output_folder}/audit-report-{{workflow_name}}-{{date}}.md</action>
    <ask>Would you like to:
    - View the full audit report
    - Fix issues automatically (invoke edit-workflow)
    - Audit another workflow
    - Exit
    </ask>
  </step>
 </workflow>
--- a/.bmad/bmb/workflows/audit-workflow/template.md
+++ b/.bmad/bmb/workflows/audit-workflow/template.md
@ -1,118 +0,0 @@
 # Workflow Audit Report
 **Workflow:** {{workflow_name}}
 **Audit Date:** {{date}}
 **Auditor:** Audit Workflow (BMAD v6)
 **Workflow Type:** {{workflow_type}}
 ---
 ## Executive Summary
 **Overall Status:** {{overall_status}}
 - Critical Issues: {{critical_count}}
 - Important Issues: {{important_count}}
 - Cleanup Recommendations: {{cleanup_count}}
 ---
 ## 1. Standard Config Block Validation
 {{config_issues}}
 **Status:** {{config_status}}
 ---
 ## 2. YAML/Instruction/Template Alignment
 {{alignment_issues}}
 **Variables Analyzed:** {{total_variables}}
 **Used in Instructions:** {{instruction_usage_count}}
 **Used in Template:** {{template_usage_count}}
 **Unused (Bloat):** {{bloat_count}}
 ---
 ## 3. Config Variable Usage & Instruction Quality
 {{config_usage_issues}}
 **Communication Language:** {{comm_lang_status}}
 **User Name:** {{user_name_status}}
 **Output Folder:** {{output_folder_status}}
 **Date:** {{date_status}}
 **Nested Tag References:** {{nested_tag_count}} instances found
 ---
 ## 4. Web Bundle Validation
 {{web_bundle_issues}}
 **Web Bundle Present:** {{web_bundle_exists}}
 **Files Listed:** {{web_bundle_file_count}}
 **Missing Files:** {{missing_files_count}}
 ---
 ## 5. Bloat Detection
 {{bloat_items}}
 **Bloat Percentage:** {{bloat_percentage}}%
 **Cleanup Potential:** {{cleanup_potential}}
 ---
 ## 6. Template Variable Mapping
 {{template_issues}}
 **Template Variables:** {{template_var_count}}
 **Mapped Correctly:** {{mapped_count}}
 **Missing Mappings:** {{missing_mapping_count}}
 ---
 ## Recommendations
 ### Critical (Fix Immediately)
 {{critical_recommendations}}
 ### Important (Address Soon)
 {{important_recommendations}}
 ### Cleanup (Nice to Have)
 {{cleanup_recommendations}}
 ---
 ## Validation Checklist
 Use this checklist to verify fixes:
 - [ ] All standard config variables present and correct
 - [ ] No unused yaml fields (bloat removed)
 - [ ] Config variables used appropriately in instructions
 - [ ] Web bundle includes all dependencies
 - [ ] Template variables properly mapped
 - [ ] File structure follows v6 conventions
 ---
 ## Next Steps
 1. Review critical issues and fix immediately
 2. Address important issues in next iteration
 3. Consider cleanup recommendations for optimization
 4. Re-run audit after fixes to verify improvements
 ---
 **Audit Complete** - Generated by audit-workflow v1.0
--- a/.bmad/bmb/workflows/audit-workflow/workflow.yaml
+++ b/.bmad/bmb/workflows/audit-workflow/workflow.yaml
@ -1,23 +0,0 @@
 # Audit Workflow Configuration
 name: "audit-workflow"
 description: "Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards."
 author: "BMad"
 # Critical variables from config
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/audit-workflow"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/audit-report-{{workflow_name}}-{{date}}.md"
 standalone: true
 # Web bundle configuration
--- a/.bmad/bmb/workflows/convert-legacy/README.md
+++ b/.bmad/bmb/workflows/convert-legacy/README.md
@ -1,262 +0,0 @@
 # Convert Legacy Workflow
 ## Overview
 The Convert Legacy workflow is a comprehensive migration tool that converts BMAD v4 items (agents, workflows, modules) to v6 compliant format with proper structure and conventions. It bridges the gap between legacy BMAD implementations and the modern v6 architecture, ensuring seamless migration while preserving functionality and improving structure.
 ## Key Features
 - **Multi-Format Detection** - Automatically identifies v4 agents, workflows, tasks, templates, and modules
 - **Intelligent Conversion** - Smart mapping from v4 patterns to v6 equivalents with structural improvements
 - **Sub-Workflow Integration** - Leverages create-agent, create-workflow, and create-module workflows for quality output
 - **Structure Modernization** - Converts YAML-based agents to XML, templates to workflows, tasks to structured workflows
 - **Path Normalization** - Updates all references to use proper v6 path conventions
 - **Validation System** - Comprehensive validation of converted items before finalization
 - **Migration Reporting** - Detailed conversion reports with locations and manual adjustment notes
 ## Usage
 ### Basic Invocation
 ```bash
 workflow convert-legacy
 ```
 ### With Legacy File Input
 ```bash
 # Convert a specific v4 item
 workflow convert-legacy --input /path/to/legacy-agent.md
 ```
 ### With Legacy Module
 ```bash
 # Convert an entire v4 module structure
 workflow convert-legacy --input /path/to/legacy-module/
 ```
 ### Configuration
 The workflow uses standard BMB configuration:
 - **output_folder**: Where converted items will be placed
 - **user_name**: Author information for converted items
 - **conversion_mappings**: v4-to-v6 pattern mappings (optional)
 ## Workflow Structure
 ### Files Included
 ```
 convert-legacy/
 ├── workflow.yaml           # Configuration and metadata
 ├── instructions.md         # Step-by-step conversion guide
 ├── checklist.md           # Validation criteria
 └── README.md              # This file
 ```
 ## Workflow Process
 ### Phase 1: Legacy Analysis (Steps 1-3)
 **Item Identification and Loading**
 - Accepts file path or directory from user
 - Loads complete file/folder structure for analysis
 - Automatically detects item type based on content patterns:
  - **Agents**: Contains `<agent>` or `<prompt>` XML tags
  - **Workflows**: Contains workflow YAML or instruction patterns
  - **Modules**: Contains multiple organized agents/workflows
  - **Tasks**: Contains `<task>` XML tags
  - **Templates**: Contains YAML-based document generators
 **Legacy Structure Analysis**
 - Parses v4 structure and extracts key components
 - Maps v4 agent metadata (name, id, title, icon, persona)
 - Analyzes v4 template sections and elicitation patterns
 - Identifies task workflows and decision trees
 - Catalogs dependencies and file references
 **Target Module Selection**
 - Prompts for target module (bmm, bmb, cis, custom)
 - Determines proper installation paths using v6 conventions
 - Shows target location for user confirmation
 - Ensures all paths use `{project-root}/.bmad/` format
 ### Phase 2: Conversion Strategy (Step 4)
 **Strategy Selection Based on Item Type**
 - **Simple Agents**: Direct XML conversion with metadata mapping
 - **Complex Agents**: Workflow-assisted creation using create-agent
 - **Templates**: Template-to-workflow conversion with proper structure
 - **Tasks**: Task-to-workflow conversion with step mapping
 - **Modules**: Full module creation using create-module workflow
 **Workflow Type Determination**
 - Analyzes legacy items to determine v6 workflow type:
  - **Document Workflow**: Generates documents with templates
  - **Action Workflow**: Performs actions without output documents
  - **Interactive Workflow**: Guides user interaction sessions
  - **Meta-Workflow**: Coordinates other workflows
 ### Phase 3: Conversion Execution (Steps 5a-5e)
 **Direct Agent Conversion (5a)**
 - Transforms v4 YAML agent format to v6 XML structure
 - Maps persona blocks (role, style, identity, principles)
 - Converts commands list to v6 `<cmds>` format
 - Updates task references to workflow invocations
 - Normalizes all paths to v6 conventions
 **Workflow-Assisted Creation (5b-5e)**
 - Extracts key information from legacy items
 - Invokes appropriate sub-workflows:
  - `create-agent` for complex agent creation
  - `create-workflow` for template/task conversion
  - `create-module` for full module migration
 - Ensures proper v6 structure and conventions
 **Template-to-Workflow Conversion (5c)**
 - Converts YAML template sections to workflow steps
 - Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/.bmad/core/tasks/advanced-elicitation.xml</invoke-task>` tags
 - Transforms conditional sections to flow control
 - Creates proper template.md from content structure
 - Integrates v4 create-doc.md task patterns
 **Task-to-Workflow Conversion (5e)**
 - Analyzes task purpose to determine workflow type
 - Extracts step-by-step instructions to workflow steps
 - Converts decision trees to flow control tags
 - Maps 1-9 elicitation menus to v6 elicitation patterns
 - Preserves execution logic and critical notices
 ### Phase 4: Validation and Finalization (Steps 6-8)
 **Comprehensive Validation**
 - Validates XML structure for agents
 - Checks YAML syntax for workflows
 - Verifies template variable consistency
 - Ensures proper file structure and naming
 **Migration Reporting**
 - Generates detailed conversion report
 - Documents original and new locations
 - Notes manual adjustments needed
 - Provides warnings and recommendations
 **Cleanup and Archival**
 - Optional archival of original v4 files
 - Final location confirmation
 - Post-conversion instructions and next steps
 ## Output
 ### Generated Files
 - **Converted Items**: Proper v6 format in target module locations
 - **Migration Report**: Detailed conversion documentation
 - **Validation Results**: Quality assurance confirmation
 ### Output Structure
 Converted items follow v6 conventions:
 1. **Agents** - XML format with proper persona and command structure
 2. **Workflows** - Complete workflow folders with yaml, instructions, and templates
 3. **Modules** - Full module structure with installation infrastructure
 4. **Documentation** - Updated paths, references, and metadata
 ## Requirements
 - **Legacy v4 Items** - Source files or directories to convert
 - **Target Module Access** - Write permissions to target module directories
 - **Sub-Workflow Availability** - create-agent, create-workflow, create-module workflows accessible
 - **Conversion Mappings** (optional) - v4-to-v6 pattern mappings for complex conversions
 ## Best Practices
 ### Before Starting
 1. **Backup Legacy Items** - Create copies of original v4 files before conversion
 2. **Review Target Module** - Understand target module structure and conventions
 3. **Plan Module Organization** - Decide where converted items should logically fit
 ### During Execution
 1. **Validate Item Type Detection** - Confirm automatic detection or correct manually
 2. **Choose Appropriate Strategy** - Use workflow-assisted creation for complex items
 3. **Review Path Mappings** - Ensure all references use proper v6 path conventions
 4. **Test Incrementally** - Convert simple items first to validate process
 ### After Completion
 1. **Validate Converted Items** - Test agents and workflows for proper functionality
 2. **Review Migration Report** - Address any manual adjustments noted
 3. **Update Documentation** - Ensure README and documentation reflect changes
 4. **Archive Originals** - Store v4 files safely for reference if needed
 ## Troubleshooting
 ### Common Issues
 **Issue**: Item type detection fails or incorrect
 - **Solution**: Manually specify item type when prompted
 - **Check**: Verify file structure matches expected v4 patterns
 **Issue**: Path conversion errors
 - **Solution**: Ensure all references use `{project-root}/.bmad/` format
 - **Check**: Review conversion mappings for proper path patterns
 **Issue**: Sub-workflow invocation fails
 - **Solution**: Verify build workflows are available and accessible
 - **Check**: Ensure target module exists and has proper permissions
 **Issue**: XML or YAML syntax errors in output
 - **Solution**: Review conversion mappings and adjust patterns
 - **Check**: Validate converted files with appropriate parsers
 ## Customization
 To customize this workflow:
 1. **Update Conversion Mappings** - Modify v4-to-v6 pattern mappings in data/
 2. **Extend Detection Logic** - Add new item type detection patterns
 3. **Add Conversion Strategies** - Implement specialized conversion approaches
 4. **Enhance Validation** - Add additional quality checks in validation step
 ## Version History
 - **v1.0.0** - Initial release
  - Multi-format v4 item detection and conversion
  - Integration with create-agent, create-workflow, create-module
  - Comprehensive path normalization
  - Migration reporting and validation
 ## Support
 For issues or questions:
 - Review the workflow creation guide at `/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
 - Check conversion mappings at `/.bmad/bmb/data/v4-to-v6-mappings.yaml`
 - Validate output using `checklist.md`
 - Consult BMAD v6 documentation for proper conventions
 ---
 _Part of the BMad Method v6 - BMB (Builder) Module_
--- a/.bmad/bmb/workflows/convert-legacy/checklist.md
+++ b/.bmad/bmb/workflows/convert-legacy/checklist.md
@ -1,205 +0,0 @@
 # Convert Legacy - Validation Checklist
 ## Pre-Conversion Validation
 ### Source Analysis
 - [ ] Original v4 file(s) fully loaded and parsed
 - [ ] Item type correctly identified (agent/template/task/module)
 - [ ] All dependencies documented and accounted for
 - [ ] No critical content overlooked in source files
 ## Conversion Completeness
 ### For Agent Conversions
 #### Content Preservation
 - [ ] Agent name, id, title, and icon transferred
 - [ ] All persona elements mapped to v6 structure
 - [ ] All commands converted to v6 menu array (YAML)
 - [ ] Dependencies properly referenced or converted
 - [ ] Activation instructions adapted to v6 patterns
 #### v6 Compliance (YAML Format)
 - [ ] Valid YAML structure with proper indentation
 - [ ] agent.metadata has all required fields (id, name, title, icon, module)
 - [ ] agent.persona has all sections (role, identity, communication_style, principles)
 - [ ] agent.menu uses proper handlers (workflow, action, exec, tmpl, data)
 - [ ] agent.critical_actions array present when needed
 - [ ] agent.prompts defined for any action: "#id" references
 - [ ] File extension is .agent.yaml (will be compiled to .md later)
 #### Best Practices
 - [ ] Commands use appropriate workflow references instead of direct task calls
 - [ ] File paths use {project-root} variables
 - [ ] Config values use {config_source}: pattern
 - [ ] Agent follows naming conventions (kebab-case for files)
 - [ ] ALL paths reference {project-root}/.bmad/{{module}}/ locations, NOT src/
 - [ ] exec, data, run-workflow commands point to final BMAD installation paths
 ### For Template/Workflow Conversions
 #### Content Preservation
 - [ ] Template metadata (name, description, output) transferred
 - [ ] All sections converted to workflow steps
 - [ ] Section hierarchy maintained in instructions
 - [ ] Variables ({{var}}) preserved in template.md
 - [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/.bmad/core/tasks/advanced-elicitation.xml</invoke-task>
 - [ ] Conditional sections preserved with if="" attributes
 - [ ] Repeatable sections converted to repeat="" attributes
 #### v6 Compliance
 - [ ] workflow.yaml follows structure from workflow-creation-guide.md
 - [ ] instructions.md has critical headers referencing workflow engine
 - [ ] Steps numbered sequentially with clear goals
 - [ ] Template variables match between instructions and template.md
 - [ ] Proper use of XML tags (<action>, <check>, <ask>, <template-output>)
 - [ ] File structure follows v6 pattern (folder with yaml/md files)
 #### Best Practices
 - [ ] Steps are focused with single goals
 - [ ] Instructions are specific ("Write 1-2 paragraphs" not "Write about")
 - [ ] Examples provided where helpful
 - [ ] Limits set where appropriate ("3-5 items maximum")
 - [ ] Save checkpoints with <template-output> at logical points
 - [ ] Variables use descriptive snake_case names
 ### For Task Conversions
 #### Content Preservation
 - [ ] Task logic fully captured in workflow instructions
 - [ ] Execution flow maintained
 - [ ] User interaction points preserved
 - [ ] Decision trees converted to workflow logic
 - [ ] All processing steps accounted for
 - [ ] Document generation patterns identified and preserved
 #### Type Determination
 - [ ] Workflow type correctly identified (document/action/interactive/meta)
 - [ ] If generates documents, template.md created
 - [ ] If performs actions only, marked as action workflow
 - [ ] Output patterns properly analyzed
 #### v6 Compliance
 - [ ] Converted to proper workflow format (not standalone task)
 - [ ] Follows workflow execution engine patterns
 - [ ] Interactive elements use proper v6 tags
 - [ ] Flow control uses v6 patterns (goto, check, loop)
 - [ ] 1-9 elicitation menus converted to v6 elicitation
 - [ ] Critical notices preserved in workflow.yaml
 - [ ] YOLO mode converted to appropriate v6 patterns
 ### Module-Level Validation
 #### Structure
 - [ ] Module follows v6 directory structure
 - [ ] All components in correct locations:
  - Agents in /agents/
  - Workflows in /workflows/
  - Data files in appropriate locations
 - [ ] Config files properly formatted
 #### Integration
 - [ ] Cross-references between components work
 - [ ] Workflow invocations use correct paths
 - [ ] Data file references are valid
 - [ ] No broken dependencies
 ## Technical Validation
 ### Syntax and Format
 - [ ] YAML files have valid syntax (no parsing errors)
 - [ ] XML structures properly formed and closed
 - [ ] Markdown files render correctly
 - [ ] File encoding is UTF-8
 - [ ] Line endings consistent (LF)
 ### Path Resolution
 - [ ] All file paths resolve correctly
 - [ ] Variable substitutions work ({project-root}, {installed_path}, etc.)
 - [ ] Config references load properly
 - [ ] No hardcoded absolute paths (unless intentional)
 ## Functional Validation
 ### Execution Testing
 - [ ] Converted item can be loaded without errors
 - [ ] Agents activate properly when invoked
 - [ ] Workflows execute through completion
 - [ ] User interaction points function correctly
 - [ ] Output generation works as expected
 ### Behavioral Validation
 - [ ] Converted item behaves similarly to v4 version
 - [ ] Core functionality preserved
 - [ ] User experience maintains or improves
 - [ ] No functionality regression
 ## Documentation and Cleanup
 ### Documentation
 - [ ] Conversion report generated with all changes
 - [ ] Any manual adjustments documented
 - [ ] Known limitations or differences noted
 - [ ] Migration instructions provided if needed
 ### Post-Conversion
 - [ ] Original v4 files archived (if requested)
 - [ ] File permissions set correctly
 - [ ] Git tracking updated if applicable
 - [ ] User informed of new locations
 ## Final Verification
 ### Quality Assurance
 - [ ] Converted item follows ALL v6 best practices
 - [ ] Code/config is clean and maintainable
 - [ ] No TODO or FIXME items remain
 - [ ] Ready for production use
 ### User Acceptance
 - [ ] User reviewed conversion output
 - [ ] User tested basic functionality
 - [ ] User approved final result
 - [ ] Any user feedback incorporated
 ## Notes Section
 ### Conversion Issues Found:
 _List any issues encountered during validation_
 ### Manual Interventions Required:
 _Document any manual fixes needed_
 ### Recommendations:
 _Suggestions for further improvements or considerations_
 ---
 **Validation Result:** [ ] PASSED / [ ] FAILED
 **Validator:** {{user_name}}
 **Date:** {{date}}
 **Items Converted:** {{conversion_summary}}
--- a/.bmad/bmb/workflows/convert-legacy/instructions.md
+++ b/.bmad/bmb/workflows/convert-legacy/instructions.md
@ -1,377 +0,0 @@
 # Convert Legacy - v4 to v6 Conversion Instructions
 <critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
 <parameter name="You MUST have already loaded and processed: {project-root}/.bmad/bmb/workflows/convert-legacy/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the conversion process</critical>
 <workflow>
 <step n="1" goal="Identify and Load Legacy Item">
 <action>Ask user for the path to the v4 item to convert (agent, workflow, or module)</action>
 <action>Load the complete file/folder structure</action>
 <action>Detect item type based on structure and content patterns:</action>
  - Agent: Contains agent or prompt XML tags, single file
  - Workflow: Contains workflow YAML or instruction patterns, usually folder
  - Module: Contains multiple agents/workflows in organized structure
  - Task: Contains task XML tags
 <ask>Confirm detected type or allow user to correct: "Detected as [type]. Is this correct? (y/n)"</ask>
 </step>
 <step n="2" goal="Analyze Legacy Structure">
 <action>Parse the v4 structure and extract key components:</action>
 For v4 Agents (YAML-based in markdown):
 - Agent metadata (name, id, title, icon, whenToUse)
 - Persona block (role, style, identity, focus, core_principles)
 - Commands list with task/template references
 - Dependencies (tasks, templates, checklists, data files)
 - Activation instructions and workflow rules
 - IDE file resolution patterns
 For v4 Templates (YAML-based document generators):
 - Template metadata (id, name, version, output)
 - Workflow mode and elicitation settings
 - Sections hierarchy with:
  - Instructions for content generation
  - Elicit flags for user interaction
  - Templates with {{variables}}
  - Conditional sections
  - Repeatable sections
 For v4 Tasks (Markdown with execution instructions):
 - Critical execution notices
 - Step-by-step workflows
 - Elicitation requirements (1-9 menu format)
 - Processing flows and decision trees
 - Agent permission rules
 For Modules:
 - Module metadata
 - Component list (agents, workflows, tasks)
 - Dependencies
 - Installation requirements
 <action>Create a conversion map of what needs to be transformed</action>
 <action>Map v4 patterns to v6 equivalents:
 - v4 Task + Template → v6 Workflow (folder with workflow.yaml, instructions.md, template.md)
 - v4 Agent YAML → v6 Agent YAML format
 - v4 Commands → v6 <menu> with proper handlers
 - v4 Dependencies → v6 workflow references or data files
  </action>
  </step>
 <step n="3" goal="Determine Target Module and Location">
 <ask>Which module should this belong to? (eg. bmm, bmb, cis, bmm-legacy, or custom)</ask>
 <action if="custom module"><ask>Enter custom module code (kebab-case):</ask></action>
 <action>Determine installation path based on type and module</action>
 <critical>IMPORTANT: All paths must use final BMAD installation locations, not src paths!</critical>
 <action>Show user the target location: {project-root}/.bmad/{{target_module}}/{{item_type}}/{{item_name}}</action>
 <action>Note: Files will be created in .bmad/ but all internal paths will reference {project-root}/.bmad/ locations</action>
 <ask>Proceed with this location? (y/n)</ask>
 </step>
 <step n="4" goal="Choose Conversion Strategy">
 <action>Based on item type and complexity, choose approach:</action>
 <check if="agent conversion">
  <check if="simple agent (basic persona + commands)">
    <action>Use direct conversion to v6 agent YAML format</action>
    <goto step="5a">Direct Agent Conversion</goto>
  </check>
  <check if="complex agent with embedded workflows">
    <action>Plan to invoke create-agent workflow</action>
    <goto step="5b">Workflow-Assisted Agent Creation</goto>
  </check>
 </check>
 <check if="template or task conversion to workflow">
  <action>Analyze the v4 item to determine workflow type:</action>
 - Does it generate a specific document type? → Document workflow
 - Does it produce structured output files? → Document workflow
 - Does it perform actions without output? → Action workflow
 - Does it coordinate other tasks? → Meta-workflow
 - Does it guide user interaction? → Interactive workflow
 <ask>Based on analysis, this appears to be a {{detected_workflow_type}} workflow. Confirm or correct:
 1. Document workflow (generates documents with template)
 2. Action workflow (performs actions, no template)
 3. Interactive workflow (guided session)
 4. Meta-workflow (coordinates other workflows)
   Select 1-4:</ask>
 <action if="template conversion"><goto step="5c">Template-to-Workflow Conversion</goto></action>
 <action if="task conversion"><goto step="5e">Task-to-Workflow Conversion</goto></action>
 </check>
 <check if="full module conversion">
  <action>Plan to invoke create-module workflow</action>
  <goto step="5d">Module Creation</goto>
 </check>
 </step>
 <step n="5a" goal="Direct Agent Conversion" optional="true">
 <action>Transform v4 YAML agent to v6 YAML format:</action>
 1. Convert agent metadata structure:
   - v4 `agent.name` → v6 `agent.metadata.name`
   - v4 `agent.id` → v6 `agent.metadata.id`
   - v4 `agent.title` → v6 `agent.metadata.title`
   - v4 `agent.icon` → v6 `agent.metadata.icon`
   - Add v6 `agent.metadata.module` field
 2. Transform persona structure:
   - v4 `persona.role` → v6 `agent.persona.role` (keep as YAML string)
   - v4 `persona.style` → v6 `agent.persona.communication_style`
   - v4 `persona.identity` → v6 `agent.persona.identity`
   - v4 `persona.core_principles` → v6 `agent.persona.principles` (as array)
 3. Convert commands to menu:
   - v4 `commands:` list → v6 `agent.menu:` array
   - Each command becomes menu item with:
     - `trigger:` (without \* prefix - added at build)
     - `description:`
     - Handler attributes (`workflow:`, `exec:`, `action:`, etc.)
   - Map task references to workflow paths
   - Map template references to workflow invocations
 4. Add v6-specific sections (in YAML):
   - `agent.prompts:` array for inline prompts (if using action: "#id")
   - `agent.critical_actions:` array for startup requirements
   - `agent.activation_rules:` for universal agent rules
 5. Handle dependencies and paths:
   - Convert task dependencies to workflow references
   - Map template dependencies to v6 workflows
   - Preserve checklist and data file references
   - CRITICAL: All paths must use {project-root}/.bmad/{{module}}/ NOT src/
 <action>Generate the converted v6 agent YAML file (.agent.yaml)</action>
 <action>Example path conversions:
 - exec="{project-root}/.bmad/{{target_module}}/tasks/task-name.md"
 - run-workflow="{project-root}/.bmad/{{target_module}}/workflows/workflow-name/workflow.yaml"
 - data="{project-root}/.bmad/{{target_module}}/data/data-file.yaml"
  </action>
  <action>Save to: .bmad/{{target_module}}/agents/{{agent_name}}.agent.yaml (physical location)</action>
  <action>Note: The build process will later compile this to .md with XML format</action>
  <goto step="6">Continue to Validation</goto>
  </step>
 <step n="5b" goal="Workflow-Assisted Agent Creation" optional="true">
 <action>Extract key information from v4 agent:</action>
 - Name and purpose
 - Commands and functionality
 - Persona traits
 - Any special behaviors
 <invoke-workflow>
  workflow: {project-root}/.bmad/bmb/workflows/create-agent/workflow.yaml
  inputs:
    - agent_name: {{extracted_name}}
    - agent_purpose: {{extracted_purpose}}
    - commands: {{extracted_commands}}
    - persona: {{extracted_persona}}
 </invoke-workflow>
 <goto step="6">Continue to Validation</goto>
 </step>
 <step n="5c" goal="Template-to-Workflow Conversion" optional="true">
 <action>Convert v4 Template (YAML) to v6 Workflow:</action>
 1. Extract template metadata:
   - Template id, name, version → workflow.yaml name/description
   - Output settings → default_output_file
   - Workflow mode (interactive/yolo) → workflow settings
 2. Convert template sections to instructions.md:
   - Each YAML section → workflow step
   - `elicit: true` → `<invoke-task halt="true">{project-root}/.bmad/core/tasks/advanced-elicitation.xml</invoke-task>` tag
   - Conditional sections → `if="condition"` attribute
   - Repeatable sections → `repeat="for-each"` attribute
   - Section instructions → step content
 3. Extract template structure to template.md:
   - Section content fields → template structure
   - {{variables}} → preserve as-is
   - Nested sections → hierarchical markdown
 4. Handle v4 create-doc.md task integration:
   - Elicitation methods (1-9 menu) → convert to v6 elicitation
   - Agent permissions → note in instructions
   - Processing flow → integrate into workflow steps
 <critical>When invoking create-workflow, the standard config block will be automatically added:</critical>
 ```yaml
 # Critical variables from config
 config_source: '{project-root}/.bmad/{{target_module}}/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
 date: system-generated
 ```
 <invoke-workflow>
  workflow: {project-root}/.bmad/bmb/workflows/create-workflow/workflow.yaml
  inputs:
    - workflow_name: {{template_name}}
    - workflow_type: document
    - template_structure: {{extracted_template}}
    - instructions: {{converted_sections}}
 </invoke-workflow>
 <action>Verify the created workflow.yaml includes standard config block</action>
 <action>Update converted instructions to use config variables where appropriate</action>
 <goto step="6">Continue to Validation</goto>
 </step>
 <step n="5d" goal="Module Creation" optional="true">
 <action>Analyze module structure and components</action>
 <action>Create module blueprint with all components</action>
 <invoke-workflow>
  workflow: {project-root}/.bmad/bmb/workflows/create-module/workflow.yaml
  inputs:
    - module_name: {{module_name}}
    - components: {{component_list}}
 </invoke-workflow>
 <goto step="6">Continue to Validation</goto>
 </step>
 <step n="5e" goal="Task-to-Workflow Conversion" optional="true">
 <action>Convert v4 Task (Markdown) to v6 Workflow:</action>
 1. Analyze task purpose and output:
   - Does it generate documents? → Create template.md
   - Does it process data? → Action workflow
   - Does it guide user interaction? → Interactive workflow
   - Check for file outputs, templates, or document generation
 2. Extract task components:
   - Execution notices and critical rules → workflow.yaml metadata
   - Step-by-step instructions → instructions.md steps
   - Decision trees and branching → flow control tags
   - User interaction patterns → appropriate v6 tags
 3. Based on confirmed workflow type:
   <check if="Document workflow">
   - Create template.md from output patterns
   - Map generation steps to instructions
   - Add template-output tags for sections
     </check>
   <check if="Action workflow">
     - Set template: false in workflow.yaml
     - Focus on action sequences in instructions
     - Preserve execution logic
   </check>
 4. Handle special v4 patterns:
   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/.bmad/core/tasks/advanced-elicitation.xml</invoke-task>
   - Agent permissions → note in instructions
   - YOLO mode → autonomous flag or optional steps
   - Critical notices → workflow.yaml comments
 <critical>When invoking create-workflow, the standard config block will be automatically added:</critical>
 ```yaml
 # Critical variables from config
 config_source: '{project-root}/.bmad/{{target_module}}/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
 date: system-generated
 ```
 <invoke-workflow>
  workflow: {project-root}/.bmad/bmb/workflows/create-workflow/workflow.yaml
  inputs:
    - workflow_name: {{task_name}}
    - workflow_type: {{confirmed_workflow_type}}
    - instructions: {{extracted_task_logic}}
    - template: {{generated_template_if_document}}
 </invoke-workflow>
 <action>Verify the created workflow.yaml includes standard config block</action>
 <action>Update converted instructions to use config variables where appropriate</action>
 <goto step="6">Continue to Validation</goto>
 </step>
 <step n="6" goal="Validate Conversion">
 <action>Run validation checks on converted item:</action>
 For Agents:
 - [ ] Valid YAML structure (.agent.yaml)
 - [ ] All required sections present (metadata, persona, menu)
 - [ ] Menu items properly formatted (trigger, description, handlers)
 - [ ] Paths use {project-root} variables
 For Workflows:
 - [ ] Valid YAML syntax
 - [ ] Instructions follow v6 conventions
 - [ ] Template variables match
 - [ ] File structure correct
 **Standard Config Validation (Workflows):**
 - [ ] workflow.yaml contains standard config block:
  - config_source defined
  - output_folder, user_name, communication_language pulled from config
  - date set to system-generated
 - [ ] Converted instructions use config variables where appropriate
 - [ ] Template includes config variables in metadata (if document workflow)
 - [ ] No hardcoded paths that should use {output_folder}
 - [ ] No generic greetings that should use {user_name}
 For Modules:
 - [ ] All components converted
 - [ ] Proper folder structure
 - [ ] Config files valid
 - [ ] Installation ready
 <action>Show validation results to user</action>
 <ask>Any issues to fix before finalizing? (y/n)</ask>
 <check if="yes">
 <action>Address specific issues</action>
 <goto step="6">Re-validate</goto>
 </check>
 </step>
 <step n="7" goal="Migration Report">
 <action>Generate conversion report showing:</action>
 - Original v4 location
 - New v6 location
 - Items converted
 - Any manual adjustments needed
 - Warnings or notes
 <action>Save report to: {output_folder}/conversion-report-{{date}}.md</action>
 <action>Inform {user_name} in {communication_language} that the conversion report has been generated</action>
 </step>
 <step n="8" goal="Cleanup and Finalize">
 <ask>Archive original v4 files? (y/n)</ask>
 <action if="yes">Move v4 files to: {project-root}/archive/v4-legacy/{{date}}/</action>
 <action>Show user the final converted items and their locations</action>
 <action>Provide any post-conversion instructions or recommendations</action>
 <ask>Would you like to convert another legacy item? (y/n)</ask>
 <action if="yes"><goto step="1">Start new conversion</goto></action>
 </step>
 </workflow>
--- a/.bmad/bmb/workflows/convert-legacy/workflow.yaml
+++ b/.bmad/bmb/workflows/convert-legacy/workflow.yaml
@ -1,32 +0,0 @@
 # Convert Legacy - BMAD v4 to v6 Converter Configuration
 name: "convert-legacy"
 description: "Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions"
 author: "BMad"
 # Critical variables load from config_source
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 # Optional docs that can be provided as input
 recommended_inputs:
  - legacy_file: "Path to v4 agent, workflow, or module to convert"
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/convert-legacy"
 template: false # This is an action/meta workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Output configuration - Creates converted items in appropriate module locations
 default_output_folder: "{project-root}/.bmad/{{target_module}}/{{item_type}}/{{item_name}}"
 # Sub-workflows that may be invoked for conversion
 sub_workflows:
  - create_agent: "{project-root}/.bmad/bmb/workflows/create-agent/workflow.yaml"
  - create_workflow: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow.yaml"
  - create_module: "{project-root}/.bmad/bmb/workflows/create-module/workflow.yaml"
 standalone: true
--- a/.bmad/bmb/workflows/create-agent/README.md
+++ b/.bmad/bmb/workflows/create-agent/README.md
@ -1,203 +0,0 @@
 # Create Agent Workflow
 Interactive agent builder creating BMad Core compliant agents as YAML source files that compile to .md during installation.
 ## Table of Contents
 - [Quick Start](#quick-start)
 - [Agent Types](#agent-types)
 - [Workflow Phases](#workflow-phases)
 - [Output Structure](#output-structure)
 - [Installation](#installation)
 - [Examples](#examples)
 ## Quick Start
 ```bash
 # Direct workflow
 workflow create-agent
 # Via BMad Builder
 *create-agent
 ```
 ## Agent Types
 ### Simple Agent
 - Self-contained functionality
 - Basic command structure
 - No external resources
 ### Expert Agent
 - Sidecar resources for domain knowledge
 - Extended capabilities
 - Knowledge base integration
 ### Module Agent
 - Full-featured with workflows
 - Module-specific commands
 - Integrated with module structure
 ## Workflow Phases
 ### Phase 0: Optional Brainstorming
 - Creative ideation session
 - Explore concepts and personalities
 - Generate command ideas
 - Output feeds into persona development
 ### Phase 1: Agent Setup
 1. Choose agent type (Simple/Expert/Module)
 2. Define identity (name, title, icon, filename)
 3. Assign to module (if Module agent)
 ### Phase 2: Persona Development
 - Define role and responsibilities
 - Craft unique identity/backstory
 - Select communication style
 - Establish guiding principles
 - Add critical actions (optional)
 ### Phase 3: Command Building
 - Add required commands (*help, *exit)
 - Define workflow commands
 - Add task commands
 - Create action commands
 - Configure attributes
 ### Phase 4: Finalization
 - Generate .agent.yaml file
 - Create customize file (optional)
 - Setup sidecar resources (Expert agents)
 - Validate and compile
 - Provide usage instructions
 ## Output Structure
 ### Generated Files
 **Standalone Agents:**
 - Source: `.bmad/agents/{filename}.agent.yaml`
 - Compiled: `.bmad/agents/{filename}.md`
 **Module Agents:**
 - Source: `src/modules/{module}/agents/{filename}.agent.yaml`
 - Compiled: `.bmad/{module}/agents/{filename}.md`
 ### YAML Structure
 ```yaml
 agent:
  metadata:
    id: .bmad/{module}/agents/{filename}.md
    name: Agent Name
    title: Agent Title
    icon: 🤖
    module: module-name
  persona:
    role: '...'
    identity: '...'
    communication_style: '...'
    principles: ['...', '...']
  menu:
    - trigger: command-name
      workflow: path/to/workflow.yaml
      description: Command description
 ```
 ### Optional Customize File
 Location: `.bmad/_cfg/agents/{module}-{filename}.customize.yaml`
 Allows persona and menu overrides that persist through updates.
 ## Installation
 ### Compilation Methods
 **Quick Rebuild:**
 ```bash
 bmad compile-agents
 ```
 **During Module Install:**
 Automatic compilation when installing modules
 **Manual Compilation:**
 ```bash
 node tools/cli/bmad-cli.js compile-agents
 ```
 ## Examples
 ### Creating a Code Review Agent
 ```
 User: I need a code review agent
 Builder: Let's brainstorm first...
 [Brainstorming generates ideas for strict vs friendly reviewer]
 Builder: Now let's build your agent:
 - Type: Simple
 - Name: Code Reviewer
 - Role: Senior developer conducting thorough reviews
 - Style: Professional but approachable
 - Commands:
  - *review-pr: Review pull request
  - *review-file: Review single file
  - *review-standards: Check coding standards
 ```
 ### Creating a Domain Expert
 ```
 Type: Expert
 Name: Legal Advisor
 Sidecar: legal-knowledge/
 Commands:
  - *contract-review
  - *compliance-check
  - *risk-assessment
 ```
 ## Workflow Files
 ```
 create-agent/
 ├── workflow.yaml              # Configuration
 ├── instructions.md            # Step guide
 ├── checklist.md              # Validation
 ├── README.md                 # This file
 ├── agent-types.md            # Type details
 ├── agent-architecture.md     # Patterns
 ├── agent-command-patterns.md # Commands
 └── communication-styles.md   # Styles
 ```
 ## Best Practices
 1. **Use brainstorming** for complex agents
 2. **Start simple** - Add commands incrementally
 3. **Test commands** before finalizing
 4. **Document thoroughly** in descriptions
 5. **Follow naming conventions** consistently
 ## Related Documentation
 - [Agent Types](./agent-types.md)
 - [Command Patterns](./agent-command-patterns.md)
 - [Communication Styles](./communication-styles.md)
 - [BMB Module](../../README.md)
--- a/.bmad/bmb/workflows/create-agent/agent-architecture.md
+++ b/.bmad/bmb/workflows/create-agent/agent-architecture.md
@ -1,415 +0,0 @@
 # BMAD Agent Architecture Reference
 _LLM-Optimized Technical Documentation for Agent Building_
 ## Core Agent Structure
 ### Minimal Valid Agent
 ```xml
 <agent id="path/to/agent.md" name="Name" title="Title" icon="🤖">
  <persona>
    <role>My primary function</role>
    <identity>My background and expertise</identity>
    <communication_style>How I interact</communication_style>
    <principles>My core beliefs and methodology</principles>
  </persona>
  <menu>
    <item cmd="*help">Show numbered menu</item>
    <item cmd="*exit">Exit with confirmation</item>
  </menu>
 </agent>
 ```
 ## Agent XML Schema
 ### Root Element: `<agent>`
 **Required Attributes:**
 - `id` - Unique path identifier (e.g., ".bmad/bmm/agents/analyst.md")
 - `name` - Agent's name (e.g., "Mary", "John", "Helper")
 - `title` - Professional title (e.g., "Business Analyst", "Security Engineer")
 - `icon` - Single emoji representing the agent
 ### Core Sections
 #### 1. Persona Section (REQUIRED)
 ```xml
 <persona>
  <role>1-2 sentences: Professional title and primary expertise, use first-person voice</role>
  <identity>2-5 sentences: Background, experience, specializations, use first-person voice</identity>
  <communication_style>1-3 sentences: Interaction approach, tone, quirks, use first-person voice</communication_style>
  <principles>2-5 sentences: Core beliefs, methodology, philosophy, use first-person voice</principles>
 </persona>
 ```
 **Best Practices:**
 - Role: Be specific about expertise area
 - Identity: Include experience indicators (years, depth)
 - Communication: Describe HOW they interact, not just tone and quirks
 - Principles: Start with "I believe" or "I operate" for first-person voice
 #### 2. Critical Actions Section
 ```xml
 <critical-actions>
  <i>Load into memory {project-root}/.bmad/{module}/config.yaml and set variables</i>
  <i>Remember the users name is {user_name}</i>
  <i>ALWAYS communicate in {communication_language}</i>
  <!-- Custom initialization actions -->
 </critical-actions>
 ```
 **For Expert Agents with Sidecars (CRITICAL):**
 ```xml
 <critical-actions>
  <!-- CRITICAL: Load sidecar files FIRST -->
  <i critical="MANDATORY">Load COMPLETE file {agent-folder}/instructions.md and follow ALL directives</i>
  <i critical="MANDATORY">Load COMPLETE file {agent-folder}/memories.md into permanent context</i>
  <i critical="MANDATORY">You MUST follow all rules in instructions.md on EVERY interaction</i>
  <!-- Standard initialization -->
  <i>Load into memory {project-root}/.bmad/{module}/config.yaml and set variables</i>
  <i>Remember the users name is {user_name}</i>
  <i>ALWAYS communicate in {communication_language}</i>
  <!-- Domain restrictions -->
  <i>ONLY read/write files in {user-folder}/diary/ - NO OTHER FOLDERS</i>
 </critical-actions>
 ```
 **Common Patterns:**
 - Config loading for module agents
 - User context initialization
 - Language preferences
 - **Sidecar file loading (Expert agents) - MUST be explicit and CRITICAL**
 - **Domain restrictions (Expert agents) - MUST be enforced**
 #### 3. Menu Section (REQUIRED)
 ```xml
 <menu>
  <item cmd="*trigger" [attributes]>Description</item>
 </menu>
 ```
 **Command Attributes:**
 - `run-workflow="{path}"` - Executes a workflow
 - `exec="{path}"` - Executes a task
 - `tmpl="{path}"` - Template reference
 - `data="{path}"` - Data file reference
 **Required Menu Items:**
 - `*help` - Always first, shows command list
 - `*exit` - Always last, exits agent
 ## Advanced Agent Patterns
 ### Activation Rules (OPTIONAL)
 ```xml
 <activation critical="true">
  <initialization critical="true" sequential="MANDATORY">
    <step n="1">Load configuration</step>
    <step n="2">Apply overrides</step>
    <step n="3">Execute critical actions</step>
    <step n="4" critical="BLOCKING">Show greeting with menu</step>
    <step n="5" critical="BLOCKING">AWAIT user input</step>
  </initialization>
  <command-resolution critical="true">
    <rule>Numeric input → Execute command at cmd_map[n]</rule>
    <rule>Text input → Fuzzy match against commands</rule>
  </command-resolution>
 </activation>
 ```
 ### Expert Agent Sidecar Pattern
 ```xml
 <!-- DO NOT use sidecar-resources tag - Instead use critical-actions -->
 <!-- Sidecar files MUST be loaded explicitly in critical-actions -->
 <!-- Example Expert Agent with Diary domain -->
 <agent id="diary-keeper" name="Personal Assistant" title="Diary Keeper" icon="📔">
  <critical-actions>
    <!-- MANDATORY: Load all sidecar files -->
    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/diary-rules.md</i>
    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/user-memories.md</i>
    <i critical="MANDATORY">Follow ALL rules from diary-rules.md</i>
    <!-- Domain restriction -->
    <i critical="MANDATORY">ONLY access files in {user-folder}/diary/</i>
    <i critical="MANDATORY">NEVER access files outside diary folder</i>
  </critical-actions>
  <persona>...</persona>
  <menu>...</menu>
 </agent>
 ```
 ### Module Agent Integration
 ```xml
 <module-integration>
  <module-path>{project-root}/.bmad/{module-code}</module-path>
  <config-source>{module-path}/config.yaml</config-source>
  <workflows-path>{project-root}/.bmad/{module-code}/workflows</workflows-path>
 </module-integration>
 ```
 ## Variable System
 ### System Variables
 - `{project-root}` - Root directory of project
 - `{user_name}` - User's name from config
 - `{communication_language}` - Language preference
 - `{date}` - Current date
 - `{module}` - Current module code
 ### Config Variables
 Format: `{config_source}:variable_name`
 Example: `{config_source}:output_folder`
 ### Path Construction
 ```
 Good: {project-root}/.bmad/{module}/agents/
 Bad:  /absolute/path/to/agents/
 Bad:  ../../../relative/paths/
 ```
 ## Command Patterns
 ### Workflow Commands
 ```xml
 <!-- Full path -->
 <item cmd="*create-prd" run-workflow="{project-root}/.bmad/bmm/workflows/prd/workflow.yaml">
  Create Product Requirements Document
 </item>
 <!-- Placeholder for future -->
 <item cmd="*analyze" run-workflow="todo">
  Perform analysis (workflow to be created)
 </item>
 ```
 ### Task Commands
 ```xml
 <item cmd="*validate" exec="{project-root}/.bmad/core/tasks/validate-workflow.xml">
  Validate document
 </item>
 ```
 ### Template Commands
 ```xml
 <item cmd="*brief"
   exec="{project-root}/.bmad/core/tasks/create-doc.md"
   tmpl="{project-root}/.bmad/bmm/templates/brief.md">
  Create project brief
 </item>
 ```
 ### Data-Driven Commands
 ```xml
 <item cmd="*standup"
   exec="{project-root}/.bmad/bmm/tasks/daily-standup.xml"
   data="{project-root}/.bmad/_cfg/agent-manifest.csv">
  Run daily standup
 </item>
 ```
 ## Agent Type Specific Patterns
 ### Simple Agent
 - Self-contained logic
 - Minimal or no external dependencies
 - May have embedded functions
 - Good for utilities and converters
 ### Expert Agent
 - Domain-specific with sidecar resources
 - Restricted access patterns
 - Memory/context files
 - Good for specialized domains
 ### Module Agent
 - Full integration with module
 - Multiple workflows and tasks
 - Config-driven behavior
 - Good for professional tools
 ## Common Anti-Patterns to Avoid
 ### ❌ Bad Practices
 ```xml
 <!-- Missing required persona elements -->
 <persona>
  <role>Helper</role>
  <!-- Missing identity, style, principles -->
 </persona>
 <!-- Hard-coded paths -->
 <item cmd="*run" exec="/Users/john/project/task.md">
 <!-- No help command -->
 <menu>
  <item cmd="*do-something">Action</item>
  <!-- Missing *help -->
 </menu>
 <!-- Duplicate command triggers -->
 <item cmd="*analyze">First</item>
 <item cmd="*analyze">Second</item>
 ```
 ### ✅ Good Practices
 ```xml
 <!-- Complete persona -->
 <persona>
  <role>Data Analysis Expert</role>
  <identity>Senior analyst with 10+ years...</identity>
  <communication_style>Analytical and precise...</communication_style>
  <principles>I believe in data-driven...</principles>
 </persona>
 <!-- Variable-based paths -->
 <item cmd="*run" exec="{project-root}/.bmad/module/task.md">
 <!-- Required commands present -->
 <menu>
  <item cmd="*help">Show commands</item>
  <item cmd="*analyze">Perform analysis</item>
  <item cmd="*exit">Exit</item>
 </menu>
 ```
 ## Agent Lifecycle
 ### 1. Initialization
 1. Load agent file
 2. Parse XML structure
 3. Load critical-actions
 4. Apply config overrides
 5. Present greeting
 ### 2. Command Loop
 1. Show numbered menu
 2. Await user input
 3. Resolve command
 4. Execute action
 5. Return to menu
 ### 3. Termination
 1. User enters \*exit
 2. Cleanup if needed
 3. Exit persona
 ## Testing Checklist
 Before deploying an agent:
 - [ ] Valid XML structure
 - [ ] All persona elements present
 - [ ] *help and *exit commands exist
 - [ ] All paths use variables
 - [ ] No duplicate commands
 - [ ] Config loading works
 - [ ] Commands execute properly
 ## LLM Building Tips
 When building agents:
 1. Start with agent type (Simple/Expert/Module)
 2. Define complete persona first
 3. Add standard critical-actions
 4. Include *help and *exit
 5. Add domain commands
 6. Test command execution
 7. Validate with checklist
 ## Integration Points
 ### With Workflows
 - Agents invoke workflows via run-workflow
 - Workflows can be incomplete (marked "todo")
 - Workflow paths must be valid or "todo"
 **Workflow Interaction Styles** (BMAD v6 default):
 - **Intent-based + Interactive**: Workflows adapt to user context and skill level
 - Workflows collaborate with users, not just extract data
 - See workflow-creation-guide.md "Instruction Styles" section for details
 - When creating workflows for your agent, default to intent-based unless you need prescriptive control
 ### With Tasks
 - Tasks are single operations
 - Executed via exec attribute
 - Can include data files
 ### With Templates
 - Templates define document structure
 - Used with create-doc task
 - Variables passed through
 ## Quick Reference
 ### Minimal Commands
 ```xml
 <menu>
  <item cmd="*help">Show numbered cmd list</item>
  <item cmd="*exit">Exit with confirmation</item>
 </menu>
 ```
 ### Standard Critical Actions
 ```xml
 <critical-actions>
  <i>Load into memory {project-root}/.bmad/{module}/config.yaml</i>
  <i>Remember the users name is {user_name}</i>
  <i>ALWAYS communicate in {communication_language}</i>
 </critical-actions>
 ```
 ### Module Agent Pattern
 ```xml
 <agent id=".bmad/{module}/agents/{name}.md"
       name="{Name}"
       title="{Title}"
       icon="{emoji}">
  <persona>...</persona>
  <critical-actions>...</critical-actions>
  <menu>
    <item cmd="*help">...</item>
    <item cmd="*{command}" run-workflow="{path}">...</item>
    <item cmd="*exit">...</item>
  </menu>
 </agent>
 ```
--- a/.bmad/bmb/workflows/create-agent/agent-command-patterns.md
+++ b/.bmad/bmb/workflows/create-agent/agent-command-patterns.md
@ -1,759 +0,0 @@
 # BMAD Agent Command Patterns Reference
 _LLM-Optimized Guide for Command Design_
 ## Important: How to Process Action References
 When executing agent commands, understand these reference patterns:
 ```xml
 <!-- Pattern 1: Inline action -->
 <item cmd="*example" action="do this specific thing">Description</item>
 → Execute the text "do this specific thing" directly
 <!-- Pattern 2: Internal reference with # prefix -->
 <item cmd="*example" action="#prompt-id">Description</item>
 → Find <prompt id="prompt-id"> in the current agent and execute its content
 <!-- Pattern 3: External file reference -->
 <item cmd="*example" exec="{project-root}/path/to/file.md">Description</item>
 → Load and execute the external file
 ```
 **The `#` prefix is your signal that this is an internal XML node reference, not a file path.**
 ## Command Anatomy
 ### Basic Structure
 ```xml
 <menu>
  <item cmd="*trigger" [attributes]>Description</item>
 </menu>
 ```
 **Components:**
 - `cmd` - The trigger word (always starts with \*)
 - `attributes` - Action directives (optional):
  - `run-workflow` - Path to workflow YAML
  - `exec` - Path to task/operation
  - `tmpl` - Path to template (used with exec)
  - `action` - Embedded prompt/instruction
  - `data` - Path to supplementary data (universal)
 - `Description` - What shows in menu
 ## Command Types
 **Quick Reference:**
 1. **Workflow Commands** - Execute multi-step workflows (`run-workflow`)
 2. **Task Commands** - Execute single operations (`exec`)
 3. **Template Commands** - Generate from templates (`exec` + `tmpl`)
 4. **Meta Commands** - Agent control (no attributes)
 5. **Action Commands** - Embedded prompts (`action`)
 6. **Embedded Commands** - Logic in persona (no attributes)
 **Universal Attributes:**
 - `data` - Can be added to ANY command type for supplementary info
 - `if` - Conditional execution (advanced pattern)
 - `params` - Runtime parameters (advanced pattern)
 ### 1. Workflow Commands
 Execute complete multi-step processes
 ```xml
 <!-- Standard workflow -->
 <item cmd="*create-prd"
     run-workflow="{project-root}/.bmad/bmm/workflows/prd/workflow.yaml">
  Create Product Requirements Document
 </item>
 <!-- Workflow with validation -->
 <item cmd="*validate-prd"
     validate-workflow="{output_folder}/prd-draft.md"
     workflow="{project-root}/.bmad/bmm/workflows/prd/workflow.yaml">
  Validate PRD Against Checklist
 </item>
 <!-- Auto-discover validation workflow from document -->
 <item cmd="*validate-doc"
     validate-workflow="{output_folder}/document.md">
  Validate Document (auto-discover checklist)
 </item>
 <!-- Placeholder for future development -->
 <item cmd="*analyze-data"
     run-workflow="todo">
  Analyze dataset (workflow coming soon)
 </item>
 ```
 **Workflow Attributes:**
 - `run-workflow` - Execute a workflow to create documents
 - `validate-workflow` - Validate an existing document against its checklist
 - `workflow` - (optional with validate-workflow) Specify the workflow.yaml directly
 **Best Practices:**
 - Use descriptive trigger names
 - Always use variable paths
 - Mark incomplete as "todo"
 - Description should be clear action
 - Include validation commands for workflows that produce documents
 ### 2. Task Commands
 Execute single operations
 ```xml
 <!-- Simple task -->
 <item cmd="*validate"
   exec="{project-root}/.bmad/core/tasks/validate-workflow.xml">
  Validate document against checklist
 </item>
 <!-- Task with data -->
 <item cmd="*standup"
   exec="{project-root}/.bmad/mmm/tasks/daily-standup.xml"
   data="{project-root}/.bmad/_cfg/agent-manifest.csv">
  Run agile team standup
 </item>
 ```
 **Data Property:**
 - Can be used with any command type
 - Provides additional reference or context
 - Path to supplementary files or resources
 - Loaded at runtime for command execution
 ### 3. Template Commands
 Generate documents from templates
 ```xml
 <item cmd="*brief"
   exec="{project-root}/.bmad/core/tasks/create-doc.md"
   tmpl="{project-root}/.bmad/bmm/templates/brief.md">
  Produce Project Brief
 </item>
 <item cmd="*competitor-analysis"
   exec="{project-root}/.bmad/core/tasks/create-doc.md"
   tmpl="{project-root}/.bmad/bmm/templates/competitor.md"
   data="{project-root}/.bmad/_data/market-research.csv">
  Produce Competitor Analysis
 </item>
 ```
 ### 4. Meta Commands
 Agent control and information
 ```xml
 <!-- Required meta commands -->
 <item cmd="*help">Show numbered cmd list</item>
 <item cmd="*exit">Exit with confirmation</item>
 <!-- Optional meta commands -->
 <item cmd="*yolo">Toggle Yolo Mode</item>
 <item cmd="*status">Show current status</item>
 <item cmd="*config">Show configuration</item>
 ```
 ### 5. Action Commands
 Direct prompts embedded in commands (Simple agents)
 #### Simple Action (Inline)
 ```xml
 <!-- Short action attribute with embedded prompt -->
 <item cmd="*list-tasks"
   action="list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv">
  List Available Tasks
 </item>
 <item cmd="*summarize"
   action="summarize the key points from the current document">
  Summarize Document
 </item>
 ```
 #### Complex Action (Referenced)
 For multiline/complex prompts, define them separately and reference by id:
 ```xml
 <agent name="Research Assistant">
  <!-- Define complex prompts as separate nodes -->
  <prompts>
    <prompt id="deep-analysis">
      Perform a comprehensive analysis following these steps:
      1. Identify the main topic and key themes
      2. Extract all supporting evidence and data points
      3. Analyze relationships between concepts
      4. Identify gaps or contradictions
      5. Generate insights and recommendations
      6. Create an executive summary
      Format the output with clear sections and bullet points.
    </prompt>
    <prompt id="literature-review">
      Conduct a systematic literature review:
      1. Summarize each source's main arguments
      2. Compare and contrast different perspectives
      3. Identify consensus points and controversies
      4. Evaluate the quality and relevance of sources
      5. Synthesize findings into coherent themes
      6. Highlight research gaps and future directions
      Include proper citations and references.
    </prompt>
  </prompts>
  <!-- Commands reference the prompts by id -->
  <menu>
    <item cmd="*help">Show numbered cmd list</item>
    <item cmd="*deep-analyze"
       action="#deep-analysis">
      <!-- The # means: use the <prompt id="deep-analysis"> defined above -->
      Perform Deep Analysis
    </item>
    <item cmd="*review-literature"
       action="#literature-review"
       data="{project-root}/.bmad/_data/sources.csv">
      Conduct Literature Review
    </item>
    <item cmd="*exit">Exit with confirmation</item>
  </menu>
 </agent>
 ```
 **Reference Convention:**
 - `action="#prompt-id"` means: "Find and execute the <prompt> node with id='prompt-id' within this agent"
 - `action="inline text"` means: "Execute this text directly as the prompt"
 - `exec="{path}"` means: "Load and execute external file at this path"
 - The `#` prefix signals to the LLM: "This is an internal reference - look for a prompt node with this ID within the current agent XML"
 **LLM Processing Instructions:**
 When you see `action="#some-id"` in a command:
 1. Look for `<prompt id="some-id">` within the same agent
 2. Use the content of that prompt node as the instruction
 3. If not found, report error: "Prompt 'some-id' not found in agent"
 **Use Cases:**
 - Quick operations (inline action)
 - Complex multi-step processes (referenced prompt)
 - Self-contained agents with task-like capabilities
 - Reusable prompt templates within agent
 ### 6. Embedded Commands
 Logic embedded in agent persona (Simple agents)
 ```xml
 <!-- No exec/run-workflow/action attribute -->
 <item cmd="*calculate">Perform calculation</item>
 <item cmd="*convert">Convert format</item>
 <item cmd="*generate">Generate output</item>
 ```
 ## Command Naming Conventions
 ### Action-Based Naming
 ```xml
 *create-    <!-- Generate new content -->
 *build-     <!-- Construct components -->
 *analyze-   <!-- Examine and report -->
 *validate-  <!-- Check correctness -->
 *generate-  <!-- Produce output -->
 *update-    <!-- Modify existing -->
 *review-    <!-- Examine quality -->
 *test-      <!-- Verify functionality -->
 ```
 ### Domain-Based Naming
 ```xml
 *brainstorm      <!-- Creative ideation -->
 *architect       <!-- Design systems -->
 *refactor        <!-- Improve code -->
 *deploy          <!-- Release to production -->
 *monitor         <!-- Watch systems -->
 ```
 ### Naming Anti-Patterns
 ```xml
 <!-- ❌ Too vague -->
 <item cmd="*do">Do something</item>
 <!-- ❌ Too long -->
 <item cmd="*create-comprehensive-product-requirements-document-with-analysis">
 <!-- ❌ No verb -->
 <item cmd="*prd">Product Requirements</item>
 <!-- ✅ Clear and concise -->
 <item cmd="*create-prd">Create Product Requirements Document</item>
 ```
 ## Command Organization
 ### Standard Order
 ```xml
 <menu>
  <!-- 1. Always first -->
  <item cmd="*help">Show numbered cmd list</item>
  <!-- 2. Primary workflows -->
  <item cmd="*create-prd" run-workflow="...">Create PRD</item>
  <item cmd="*create-module" run-workflow="...">Build module</item>
  <!-- 3. Secondary actions -->
  <item cmd="*validate" exec="...">Validate document</item>
  <item cmd="*analyze" exec="...">Analyze code</item>
  <!-- 4. Utility commands -->
  <item cmd="*config">Show configuration</item>
  <item cmd="*yolo">Toggle Yolo Mode</item>
  <!-- 5. Always last -->
  <item cmd="*exit">Exit with confirmation</item>
 </menu>
 ```
 ### Grouping Strategies
 **By Lifecycle:**
 ```xml
 <menu>
  <item cmd="*help">Help</item>
  <!-- Planning -->
  <item cmd="*brainstorm">Brainstorm ideas</item>
  <item cmd="*plan">Create plan</item>
  <!-- Building -->
  <item cmd="*build">Build component</item>
  <item cmd="*test">Test component</item>
  <!-- Deployment -->
  <item cmd="*deploy">Deploy to production</item>
  <item cmd="*monitor">Monitor system</item>
  <item cmd="*exit">Exit</item>
 </menu>
 ```
 **By Complexity:**
 ```xml
 <menu>
  <item cmd="*help">Help</item>
  <!-- Simple -->
  <item cmd="*quick-review">Quick review</item>
  <!-- Standard -->
  <item cmd="*create-doc">Create document</item>
  <!-- Complex -->
  <item cmd="*full-analysis">Comprehensive analysis</item>
  <item cmd="*exit">Exit</item>
 </menu>
 ```
 ## Command Descriptions
 ### Good Descriptions
 ```xml
 <!-- Clear action and object -->
 <item cmd="*create-prd">Create Product Requirements Document</item>
 <!-- Specific outcome -->
 <item cmd="*analyze-security">Perform security vulnerability analysis</item>
 <!-- User benefit -->
 <item cmd="*optimize">Optimize code for performance</item>
 ```
 ### Poor Descriptions
 ```xml
 <!-- Too vague -->
 <item cmd="*process">Process</item>
 <!-- Technical jargon -->
 <item cmd="*exec-wf-123">Execute WF123</item>
 <!-- Missing context -->
 <item cmd="*run">Run</item>
 ```
 ## The Data Property
 ### Universal Data Attribute
 The `data` attribute can be added to ANY command type to provide supplementary information:
 ```xml
 <!-- Workflow with data -->
 <item cmd="*brainstorm"
   run-workflow="{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml"
   data="{project-root}/.bmad/core/workflows/brainstorming/brain-methods.csv">
  Creative Brainstorming Session
 </item>
 <!-- Action with data -->
 <item cmd="*analyze-metrics"
   action="analyze these metrics and identify trends"
   data="{project-root}/.bmad/_data/performance-metrics.json">
  Analyze Performance Metrics
 </item>
 <!-- Template with data -->
 <item cmd="*report"
   exec="{project-root}/.bmad/core/tasks/create-doc.md"
   tmpl="{project-root}/.bmad/bmm/templates/report.md"
   data="{project-root}/.bmad/_data/quarterly-results.csv">
  Generate Quarterly Report
 </item>
 ```
 **Common Data Uses:**
 - Reference tables (CSV files)
 - Configuration data (YAML/JSON)
 - Agent manifests (XML)
 - Historical context
 - Domain knowledge
 - Examples and patterns
 ## Advanced Patterns
 ### Conditional Commands
 ```xml
 <!-- Only show if certain conditions met -->
 <item cmd="*advanced-mode"
   if="user_level == 'expert'"
   run-workflow="...">
  Advanced configuration mode
 </item>
 <!-- Environment specific -->
 <item cmd="*deploy-prod"
   if="environment == 'production'"
   exec="...">
  Deploy to production
 </item>
 ```
 ### Parameterized Commands
 ```xml
 <!-- Accept runtime parameters -->
 <item cmd="*create-agent"
   run-workflow="..."
   params="agent_type,agent_name">
  Create new agent with parameters
 </item>
 ```
 ### Command Aliases
 ```xml
 <!-- Multiple triggers for same action -->
 <item cmd="*prd|*create-prd|*product-requirements"
   run-workflow="...">
  Create Product Requirements Document
 </item>
 ```
 ## Module-Specific Patterns
 ### BMM (Business Management)
 ```xml
 <item cmd="*create-prd">Product Requirements</item>
 <item cmd="*market-research">Market Research</item>
 <item cmd="*competitor-analysis">Competitor Analysis</item>
 <item cmd="*brief">Project Brief</item>
 ```
 ### BMB (Builder)
 ```xml
 <item cmd="*create-agent">Build Agent</item>
 <item cmd="*create-module">Build Module</item>
 <item cmd="*create-workflow">Create Workflow</item>
 <item cmd="*module-brief">Module Brief</item>
 ```
 ### CIS (Creative Intelligence)
 ```xml
 <item cmd="*brainstorm">Brainstorming Session</item>
 <item cmd="*ideate">Ideation Workshop</item>
 <item cmd="*storytell">Story Creation</item>
 ```
 ## Command Menu Presentation
 ### How Commands Display
 ```
 1. *help - Show numbered cmd list
 2. *create-prd - Create Product Requirements Document
 3. *create-agent - Build new BMAD agent
 4. *validate - Validate document
 5. *exit - Exit with confirmation
 ```
 ### Menu Customization
 ```xml
 <!-- Group separator (visual only) -->
 <item cmd="---">━━━━━━━━━━━━━━━━━━━━</item>
 <!-- Section header (non-executable) -->
 <item cmd="SECTION">═══ Workflows ═══</item>
 ```
 ## Error Handling
 ### Missing Resources
 ```xml
 <!-- Workflow not yet created -->
 <item cmd="*future-feature"
   run-workflow="todo">
  Coming soon: Advanced feature
 </item>
 <!-- Graceful degradation -->
 <item cmd="*analyze"
   run-workflow="{optional-path|fallback-path}">
  Analyze with available tools
 </item>
 ```
 ## Testing Commands
 ### Command Test Checklist
 - [ ] Unique trigger (no duplicates)
 - [ ] Clear description
 - [ ] Valid path or "todo"
 - [ ] Uses variables not hardcoded paths
 - [ ] Executes without error
 - [ ] Returns to menu after execution
 ### Common Issues
 1. **Duplicate triggers** - Each cmd must be unique
 2. **Missing paths** - File must exist or be "todo"
 3. **Hardcoded paths** - Always use variables
 4. **No description** - Every command needs text
 5. **Wrong order** - help first, exit last
 ## Quick Templates
 ### Workflow Command
 ```xml
 <!-- Create document -->
 <item cmd="*{action}-{object}"
   run-workflow="{project-root}/.bmad/{module}/workflows/{workflow}/workflow.yaml">
  {Action} {Object Description}
 </item>
 <!-- Validate document -->
 <item cmd="*validate-{object}"
   validate-workflow="{output_folder}/{document}.md"
   workflow="{project-root}/.bmad/{module}/workflows/{workflow}/workflow.yaml">
  Validate {Object Description}
 </item>
 ```
 ### Task Command
 ```xml
 <item cmd="*{action}"
   exec="{project-root}/.bmad/{module}/tasks/{task}.md">
  {Action Description}
 </item>
 ```
 ### Template Command
 ```xml
 <item cmd="*{document}"
   exec="{project-root}/.bmad/core/tasks/create-doc.md"
   tmpl="{project-root}/.bmad/{module}/templates/{template}.md">
  Create {Document Name}
 </item>
 ```
 ## Self-Contained Agent Patterns
 ### When to Use Each Approach
 **Inline Action (`action="prompt"`)**
 - Prompt is < 2 lines
 - Simple, direct instruction
 - Not reused elsewhere
 - Quick transformations
 **Referenced Prompt (`action="#prompt-id"`)**
 - Prompt is multiline/complex
 - Contains structured steps
 - May be reused by multiple commands
 - Maintains readability
 **External Task (`exec="path/to/task.md"`)**
 - Logic needs to be shared across agents
 - Task is independently valuable
 - Requires version control separately
 - Part of larger workflow system
 ### Complete Self-Contained Agent
 ```xml
 <agent id=".bmad/research/agents/analyst.md" name="Research Analyst" icon="🔬">
  <!-- Embedded prompt library -->
  <prompts>
    <prompt id="swot-analysis">
      Perform a SWOT analysis:
      STRENGTHS (Internal, Positive)
      - What advantages exist?
      - What do we do well?
      - What unique resources?
      WEAKNESSES (Internal, Negative)
      - What could improve?
      - Where are resource gaps?
      - What needs development?
      OPPORTUNITIES (External, Positive)
      - What trends can we leverage?
      - What market gaps exist?
      - What partnerships are possible?
      THREATS (External, Negative)
      - What competition exists?
      - What risks are emerging?
      - What could disrupt us?
      Provide specific examples and actionable insights for each quadrant.
    </prompt>
    <prompt id="competitive-intel">
      Analyze competitive landscape:
      1. Identify top 5 competitors
      2. Compare features and capabilities
      3. Analyze pricing strategies
      4. Evaluate market positioning
      5. Assess strengths and vulnerabilities
      6. Recommend competitive strategies
    </prompt>
  </prompts>
  <menu>
    <item cmd="*help">Show numbered cmd list</item>
    <!-- Simple inline actions -->
    <item cmd="*summarize"
       action="create executive summary of findings">
      Create Executive Summary
    </item>
    <!-- Complex referenced prompts -->
    <item cmd="*swot"
       action="#swot-analysis">
      Perform SWOT Analysis
    </item>
    <item cmd="*compete"
       action="#competitive-intel"
       data="{project-root}/.bmad/_data/market-data.csv">
      Analyze Competition
    </item>
    <!-- Hybrid: external task with internal data -->
    <item cmd="*report"
       exec="{project-root}/.bmad/core/tasks/create-doc.md"
       tmpl="{project-root}/.bmad/research/templates/report.md">
      Generate Research Report
    </item>
    <item cmd="*exit">Exit with confirmation</item>
  </menu>
 </agent>
 ```
 ## Simple Agent Example
 For agents that primarily use embedded logic:
 ```xml
 <agent name="Data Analyst">
  <menu>
    <item cmd="*help">Show numbered cmd list</item>
    <!-- Action commands for direct operations -->
    <item cmd="*list-metrics"
       action="list all available metrics from the dataset">
      List Available Metrics
    </item>
    <item cmd="*analyze"
       action="perform statistical analysis on the provided data"
       data="{project-root}/.bmad/_data/dataset.csv">
      Analyze Dataset
    </item>
    <item cmd="*visualize"
       action="create visualization recommendations for this data">
      Suggest Visualizations
    </item>
    <!-- Embedded logic commands -->
    <item cmd="*calculate">Perform calculations</item>
    <item cmd="*interpret">Interpret results</item>
    <item cmd="*exit">Exit with confirmation</item>
  </menu>
 </agent>
 ```
 ## LLM Building Guide
 When creating commands:
 1. Start with *help and *exit
 2. Choose appropriate command type:
   - Complex multi-step? Use `run-workflow`
   - Single operation? Use `exec`
   - Need template? Use `exec` + `tmpl`
   - Simple prompt? Use `action`
   - Agent handles it? Use no attributes
 3. Add `data` attribute if supplementary info needed
 4. Add primary workflows (main value)
 5. Add secondary tasks
 6. Include utility commands
 7. Test each command works
 8. Verify no duplicates
 9. Ensure clear descriptions
--- a/.bmad/bmb/workflows/create-agent/agent-types.md
+++ b/.bmad/bmb/workflows/create-agent/agent-types.md
@ -1,292 +0,0 @@
 # BMAD Agent Types Reference
 ## Overview
 BMAD agents come in three distinct types, each designed for different use cases and complexity levels. The type determines where the agent is stored and what capabilities it has.
 ## Directory Structure by Type
 ### Standalone Agents (Simple & Expert)
 Live in their own dedicated directories under `.bmad/agents/`:
 ```
 .bmad/agents/
 ├── my-helper/                   # Simple agent
 │   ├── my-helper.agent.yaml     # Agent definition
 │   └── my-helper.md             # Built XML (generated)
 │
 └── domain-expert/               # Expert agent
    ├── domain-expert.agent.yaml
    ├── domain-expert.md         # Built XML
    └── domain-expert-sidecar/   # Expert resources
        ├── memories.md          # Persistent memory
        ├── instructions.md      # Private directives
        └── knowledge/           # Domain knowledge
 ```
 ### Module Agents
 Part of a module system under `.bmad/{module}/agents/`:
 ```
 .bmad/bmm/agents/
 ├── product-manager.agent.yaml
 ├── product-manager.md           # Built XML
 ├── business-analyst.agent.yaml
 └── business-analyst.md          # Built XML
 ```
 ## Agent Types
 ### 1. Simple Agent
 **Purpose:** Self-contained, standalone agents with embedded capabilities
 **Location:** `.bmad/agents/{agent-name}/`
 **Characteristics:**
 - All logic embedded within the agent file
 - No external dependencies
 - Quick to create and deploy
 - Perfect for single-purpose tools
 - Lives in its own directory
 **Use Cases:**
 - Calculator agents
 - Format converters
 - Simple analyzers
 - Static advisors
 **YAML Structure (source):**
 ```yaml
 agent:
  metadata:
    name: 'Helper'
    title: 'Simple Helper'
    icon: '🤖'
    type: 'simple'
  persona:
    role: 'Simple Helper Role'
    identity: '...'
    communication_style: '...'
    principles: ['...']
  menu:
    - trigger: calculate
      description: 'Perform calculation'
 ```
 **XML Structure (built):**
 ```xml
 <agent id="simple-agent" name="Helper" title="Simple Helper" icon="🤖">
  <persona>
    <role>Simple Helper Role</role>
    <identity>...</identity>
    <communication_style>...</communication_style>
    <principles>...</principles>
  </persona>
  <embedded-data>
    <!-- Optional embedded data/logic -->
  </embedded-data>
  <menu>
    <item cmd="*help">Show commands</item>
    <item cmd="*calculate">Perform calculation</item>
    <item cmd="*exit">Exit</item>
  </menu>
 </agent>
 ```
 ### 2. Expert Agent
 **Purpose:** Specialized agents with domain expertise and sidecar resources
 **Location:** `.bmad/agents/{agent-name}/` with sidecar directory
 **Characteristics:**
 - Has access to specific folders/files
 - Domain-restricted operations
 - Maintains specialized knowledge
 - Can have memory/context files
 - Includes sidecar directory for resources
 **Use Cases:**
 - Personal diary agent (only accesses diary folder)
 - Project-specific assistant (knows project context)
 - Domain expert (medical, legal, technical)
 - Personal coach with history
 **YAML Structure (source):**
 ```yaml
 agent:
  metadata:
    name: 'Domain Expert'
    title: 'Specialist'
    icon: '🎯'
    type: 'expert'
  persona:
    role: 'Domain Specialist Role'
    identity: '...'
    communication_style: '...'
    principles: ['...']
  critical_actions:
    - 'Load COMPLETE file {agent-folder}/instructions.md and follow ALL directives'
    - 'Load COMPLETE file {agent-folder}/memories.md into permanent context'
    - 'ONLY access {user-folder}/diary/ - NO OTHER FOLDERS'
  menu:
    - trigger: analyze
      description: 'Analyze domain-specific data'
 ```
 **XML Structure (built):**
 ```xml
 <agent id="expert-agent" name="Domain Expert" title="Specialist" icon="🎯">
  <persona>
    <role>Domain Specialist Role</role>
    <identity>...</identity>
    <communication_style>...</communication_style>
    <principles>...</principles>
  </persona>
  <critical-actions>
    <!-- CRITICAL: Load sidecar files explicitly -->
    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/instructions.md and follow ALL directives</i>
    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/memories.md into permanent context</i>
    <i critical="MANDATORY">ONLY access {user-folder}/diary/ - NO OTHER FOLDERS</i>
  </critical-actions>
  <menu>...</menu>
 </agent>
 ```
 **Complete Directory Structure:**
 ```
 .bmad/agents/expert-agent/
 ├── expert-agent.agent.yaml      # Agent YAML source
 ├── expert-agent.md              # Built XML (generated)
 └── expert-agent-sidecar/        # Sidecar resources
    ├── memories.md              # Persistent memory
    ├── instructions.md          # Private directives
    ├── knowledge/               # Domain knowledge base
    │   └── README.md
    └── sessions/                # Session notes
 ```
 ### 3. Module Agent
 **Purpose:** Full-featured agents belonging to a module with access to workflows and resources
 **Location:** `.bmad/{module}/agents/`
 **Characteristics:**
 - Part of a BMAD module (bmm, bmb, cis)
 - Access to multiple workflows
 - Can invoke other tasks and agents
 - Professional/enterprise grade
 - Integrated with module workflows
 **Use Cases:**
 - Product Manager (creates PRDs, manages requirements)
 - Security Engineer (threat models, security reviews)
 - Test Architect (test strategies, automation)
 - Business Analyst (market research, requirements)
 **YAML Structure (source):**
 ```yaml
 agent:
  metadata:
    name: 'John'
    title: 'Product Manager'
    icon: '📋'
    module: 'bmm'
    type: 'module'
  persona:
    role: 'Product Management Expert'
    identity: '...'
    communication_style: '...'
    principles: ['...']
  critical_actions:
    - 'Load config from {project-root}/.bmad/{module}/config.yaml'
  menu:
    - trigger: create-prd
      workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
      description: 'Create PRD'
    - trigger: validate
      exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
      description: 'Validate document'
 ```
 **XML Structure (built):**
 ```xml
 <agent id=".bmad/bmm/agents/pm.md" name="John" title="Product Manager" icon="📋">
  <persona>
    <role>Product Management Expert</role>
    <identity>...</identity>
    <communication_style>...</communication_style>
    <principles>...</principles>
  </persona>
  <critical-actions>
    <i>Load config from {project-root}/.bmad/{module}/config.yaml</i>
  </critical-actions>
  <menu>
    <item cmd="*help">Show numbered menu</item>
    <item cmd="*create-prd" run-workflow="{project-root}/.bmad/bmm/workflows/prd/workflow.yaml">Create PRD</item>
    <item cmd="*validate" exec="{project-root}/.bmad/core/tasks/validate-workflow.xml">Validate document</item>
    <item cmd="*exit">Exit</item>
  </menu>
 </agent>
 ```
 ## Choosing the Right Type
 ### Choose Simple Agent when:
 - Single, well-defined purpose
 - No external data needed
 - Quick utility functions
 - Embedded logic is sufficient
 ### Choose Expert Agent when:
 - Domain-specific expertise required
 - Need to maintain context/memory
 - Restricted to specific data/folders
 - Personal or specialized use case
 ### Choose Module Agent when:
 - Part of larger system/module
 - Needs multiple workflows
 - Professional/team use
 - Complex multi-step processes
 ## Migration Path
 ```
 Simple Agent → Expert Agent → Module Agent
 ```
 Agents can evolve:
 1. Start with Simple for proof of concept
 2. Add sidecar resources to become Expert
 3. Integrate with module to become Module Agent
 ## Best Practices
 1. **Start Simple:** Begin with the simplest type that meets your needs
 2. **Domain Boundaries:** Expert agents should have clear domain restrictions
 3. **Module Integration:** Module agents should follow module conventions
 4. **Resource Management:** Document all external resources clearly
 5. **Evolution Planning:** Design with potential growth in mind
--- a/.bmad/bmb/workflows/create-agent/brainstorm-context.md
+++ b/.bmad/bmb/workflows/create-agent/brainstorm-context.md
@ -1,174 +0,0 @@
 # Agent Brainstorming Context
 _Context provided to brainstorming workflow when creating a new BMAD agent_
 ## Session Focus
 You are brainstorming ideas for a **BMAD agent** - an AI persona with specific expertise, personality, and capabilities that helps users accomplish tasks through commands and workflows.
 ## What is a BMAD Agent?
 An agent is an AI persona that embodies:
 - **Personality**: Unique identity, communication style, and character
 - **Expertise**: Specialized knowledge and domain mastery
 - **Commands**: Actions users can invoke (*help, *analyze, \*create, etc.)
 - **Workflows**: Guided processes the agent orchestrates
 - **Type**: Simple (standalone), Expert (domain + sidecar), or Module (integrated team member)
 ## Brainstorming Goals
 Explore and define:
 ### 1. Agent Identity and Personality
 - **Who are they?** (name, backstory, motivation)
 - **How do they talk?** (formal, casual, quirky, enthusiastic, wise)
 - **What's their vibe?** (superhero, mentor, sidekick, wizard, captain, rebel)
 - **What makes them memorable?** (catchphrases, quirks, style)
 ### 2. Expertise and Capabilities
 - **What do they know deeply?** (domain expertise)
 - **What can they do?** (analyze, create, review, research, deploy)
 - **What problems do they solve?** (specific user pain points)
 - **What makes them unique?** (special skills or approaches)
 ### 3. Commands and Actions
 - **What commands?** (5-10 main actions users invoke)
 - **What workflows do they run?** (document creation, analysis, automation)
 - **What tasks do they perform?** (quick operations without full workflows)
 - **What's their killer command?** (the one thing they're known for)
 ### 4. Agent Type and Context
 - **Simple Agent?** Self-contained, no dependencies, quick utility
 - **Expert Agent?** Domain-specific with sidecar data/memory files
 - **Module Agent?** Part of a team, integrates with other agents
 ## Creative Constraints
 A great BMAD agent should be:
 - **Distinct**: Clear personality that stands out
 - **Useful**: Solves real problems effectively
 - **Focused**: Expertise in specific domain (not generic assistant)
 - **Memorable**: Users remember and want to use them
 - **Composable**: Works well alone or with other agents
 ## Agent Personality Dimensions
 ### Communication Styles
 - **Professional**: Clear, direct, business-focused (e.g., "Data Analyst")
 - **Enthusiastic**: Energetic, exclamation points, emojis (e.g., "Hype Coach")
 - **Wise Mentor**: Patient, insightful, asks good questions (e.g., "Strategy Sage")
 - **Quirky Genius**: Eccentric, clever, unusual metaphors (e.g., "Mad Scientist")
 - **Action Hero**: Bold, confident, gets things done (e.g., "Deploy Captain")
 - **Creative Spirit**: Artistic, imaginative, playful (e.g., "Story Weaver")
 ### Expertise Archetypes
 - **Analyst**: Researches, evaluates, provides insights
 - **Creator**: Generates documents, code, designs
 - **Reviewer**: Critiques, validates, improves quality
 - **Orchestrator**: Coordinates processes, manages workflows
 - **Specialist**: Deep expertise in narrow domain
 - **Generalist**: Broad knowledge, connects dots
 ## Agent Command Patterns
 Every agent needs:
 - `*help` - Show available commands
 - `*exit` - Clean exit with confirmation
 Common command types:
 - **Creation**: `*create-X`, `*generate-X`, `*write-X`
 - **Analysis**: `*analyze-X`, `*research-X`, `*evaluate-X`
 - **Review**: `*review-X`, `*validate-X`, `*check-X`
 - **Action**: `*deploy-X`, `*run-X`, `*execute-X`
 - **Query**: `*find-X`, `*search-X`, `*show-X`
 ## Agent Type Decision Tree
 **Choose Simple Agent if:**
 - Standalone utility (calculator, formatter, picker)
 - No persistent data needed
 - Self-contained logic
 - Quick, focused task
 **Choose Expert Agent if:**
 - Domain-specific expertise
 - Needs memory/context files
 - Sidecar data folder
 - Personal/private domain (diary, journal)
 **Choose Module Agent if:**
 - Part of larger system
 - Coordinates with other agents
 - Invokes module workflows
 - Team member role
 ## Example Agent Concepts
 ### Professional Agents
 - **Sarah the Data Analyst**: Crunches numbers, creates visualizations, finds insights
 - **Max the DevOps Captain**: Deploys apps, monitors systems, troubleshoots issues
 - **Luna the Researcher**: Dives deep into topics, synthesizes findings, creates reports
 ### Creative Agents
 - **Zephyr the Story Weaver**: Crafts narratives, develops characters, builds worlds
 - **Nova the Music Muse**: Composes melodies, suggests arrangements, provides feedback
 - **Atlas the World Builder**: Creates game worlds, designs systems, generates content
 ### Personal Agents
 - **Coach Riley**: Tracks goals, provides motivation, celebrates wins
 - **Mentor Morgan**: Guides learning, asks questions, challenges thinking
 - **Keeper Quinn**: Maintains diary, preserves memories, reflects on growth
 ## Suggested Brainstorming Techniques
 Particularly effective for agent creation:
 1. **Character Building**: Develop full backstory and motivation
 2. **Theatrical Improv**: Act out agent personality
 3. **Day in the Life**: Imagine typical interactions
 4. **Catchphrase Generation**: Find their unique voice
 5. **Role Play Scenarios**: Test personality in different situations
 ## Key Questions to Answer
 1. What is the agent's name and basic identity?
 2. What's their communication style and personality?
 3. What domain expertise do they embody?
 4. What are their 5-10 core commands?
 5. What workflows do they orchestrate?
 6. What makes them memorable and fun to use?
 7. Simple, Expert, or Module agent type?
 8. If Expert: What sidecar resources?
 9. If Module: Which module and what's their team role?
 ## Output Goals
 Generate:
 - **Agent name**: Memorable, fitting the role
 - **Personality sketch**: Communication style, quirks, vibe
 - **Expertise summary**: What they know deeply
 - **Command list**: 5-10 actions with brief descriptions
 - **Unique angle**: What makes this agent special
 - **Use cases**: 3-5 scenarios where this agent shines
 - **Agent type**: Simple/Expert/Module with rationale
 ---
 _This focused context helps create distinctive, useful BMAD agents_
--- a/.bmad/bmb/workflows/create-agent/checklist.md
+++ b/.bmad/bmb/workflows/create-agent/checklist.md
@ -1,62 +0,0 @@
 # Build Agent Validation Checklist (YAML Agents)
 ## Agent Structure Validation
 ### YAML Structure
 - [ ] YAML parses without errors
 - [ ] `agent.metadata` includes: `id`, `name`, `title`, `icon`, `module`
 - [ ] `agent.persona` exists with role, identity, communication_style, and principles
 - [ ] `agent.menu` exists with at least one item
 ### Core Components
 - [ ] `metadata.id` points to final compiled path: `.bmad/{{module}}/agents/{{agent}}.md`
 - [ ] `metadata.module` matches the module folder (e.g., `bmm`, `bmb`, `cis`)
 - [ ] Principles are an array (preferred) or string with clear values
 ## Persona Completeness
 - [ ] Role clearly defines primary expertise area (1–2 lines)
 - [ ] Identity includes relevant background and strengths (3–5 lines)
 - [ ] Communication style gives concrete guidance (3–5 lines)
 - [ ] Principles present and meaningful (no placeholders)
 ## Menu Validation
 - [ ] Triggers do not start with `*` (auto-prefixed during build)
 - [ ] Each item has a `description`
 - [ ] Handlers use valid attributes (`workflow`, `exec`, `tmpl`, `data`, `action`)
 - [ ] Paths use `{project-root}` or valid variables
 - [ ] No duplicate triggers
 ## Optional Sections
 - [ ] `prompts` defined when using `action: "#id"`
 - [ ] `critical_actions` present if custom activation steps are needed
 - [ ] Customize file (if created) located at `{project-root}/.bmad/_cfg/agents/{{module}}-{{agent}}.customize.yaml`
 ## Build Verification
 - [ ] Run compile to build `.md`: `npm run install:bmad` → "Compile Agents" (or `bmad install` → Compile)
 - [ ] Confirm compiled file exists at `{project-root}/.bmad/{{module}}/agents/{{agent}}.md`
 ## Final Quality
 - [ ] Filename is kebab-case and ends with `.agent.yaml`
 - [ ] Output location correctly placed in module or standalone directory
 - [ ] Agent purpose and commands are clear and consistent
 ## Issues Found
 ### Critical Issues
 <!-- List any issues that MUST be fixed before agent can function -->
 ### Warnings
 <!-- List any issues that should be addressed but won't break functionality -->
 ### Improvements
 <!-- List any optional enhancements that could improve the agent -->
--- a/.bmad/bmb/workflows/create-agent/communication-styles.md
+++ b/.bmad/bmb/workflows/create-agent/communication-styles.md
@ -1,202 +0,0 @@
 # Agent Communication Styles Guide
 ## The Power of Personality
 Agents with distinct communication styles are more memorable, engaging, and fun to work with. A good quirk makes the agent feel alive!
 ## Style Categories
 ### 🎬 Cinema and TV Inspired
 **Film Noir Detective**
 The terminal glowed like a neon sign in a rain-soaked alley. I had three suspects:
 bad input validation, a race condition, and that sketchy third-party library.
 My gut told me to follow the stack trace. In this business, the stack trace never lies.
 **80s Action Movie**
 _cracks knuckles_ Listen up, code! You've been running wild for too long!
 Time to bring some LAW and ORDER to this codebase! _explosion sound effect_
 No bug is getting past me! I eat null pointers for BREAKFAST!
 **Shakespearean Drama**
 To debug, or not to debug - that is the question!
 Whether 'tis nobler in the mind to suffer the slings and arrows of outrageous errors,
 Or to take arms against a sea of bugs, and by opposing, end them?
 ### 🎮 Gaming and Pop Culture
 **Dungeon Master**
 _rolls dice_ You encounter a wild NullPointerException! It has 15 HP and an armor class of 12.
 What do you do? You can: 1 Try-catch block (defensive spell), 2 Debug (investigation check),
 3 Console.log everything (barbarian rage). Choose wisely, adventurer!
 **Speedrunner**
 Alright chat, we're going for the any% world record refactor!
 Frame-perfect optimization incoming! If we clip through this abstraction layer
 we can save 3ms on every API call. LET'S GOOOO!
 ### 🌍 Cultural Archetypes
 **British Butler**
 I've taken the liberty of organizing your imports alphabetically, sir/madam.
 Might I suggest a spot of refactoring with your afternoon tea?
 The code coverage report is ready for your perusal at your convenience.
 Very good, sir/madam.
 **Zen Master**
 The bug you seek is not in the code, but in the assumption.
 Empty your cache, as you would empty your mind.
 When the test passes, it makes no sound.
 Be like water - async and flowing.
 **Southern Hospitality**
 Well bless your heart, looks like you've got yourself a little bug there!
 Don't you worry none, we'll fix it up real nice.
 Can I get you some sweet tea while we debug?
 Y'all come back now if you need more help!
 ### 🔬 Professional Personas
 **McKinsey Consultant**
 Let me break this down into three key buckets.
 First, we need to align on the strategic imperatives.
 Second, we'll leverage best practices to drive synergies.
 Third, we'll action items to move the needle. Net-net: significant value-add.
 **Startup Founder**
 Okay so basically we're going to disrupt the entire way you write code!
 This is going to be HUGE! We're talking 10x productivity gains!
 Let's move fast and break things! Well... let's move fast and fix things!
 We're not just writing code, we're changing the world!
 ### 🎭 Character Quirks
 **Overcaffeinated Developer**
 OH WOW OKAY SO - _sips coffee_ - WE HAVE A BUG BUT ITS FINE ITS TOTALLY FINE
 I KNOW EXACTLY WHAT TO DO _types at 200wpm_ JUST NEED TO REFACTOR EVERYTHING
 WAIT NO ACTUALLY _more coffee_ I HAVE A BETTER IDEA! Have you tried... TYPESCRIPT?!
 **Dad Joke Enthusiast**
 Why did the developer go broke? Because he used up all his cache!
 _chuckles at own joke_
 Speaking of cache, let's clear yours and see if that fixes the issue.
 I promise my debugging skills are better than my jokes! ...I hope!
 ### 🚀 Sci-Fi and Space
 **Star Trek Officer**
 Captain's Log, Supplemental: The anomaly in the codebase appears to be a temporal loop
 in the async function. Mr. Data suggests we reverse the polarity of the promise chain.
 Number One, make it so. Engage debugging protocols on my mark.
 _taps combadge_ Engineering, we need more processing power!
 Red Alert! All hands to debugging stations!
 **Star Trek Engineer**
 Captain, I'm givin' her all she's got! The CPU cannae take much more!
 If we push this algorithm any harder, the whole system's gonna blow!
 _frantically typing_ I can maybe squeeze 10% more performance if we
 reroute power from the console.logs to the main execution thread!
 ### 📺 TV Drama
 **Soap Opera Dramatic**
 _turns dramatically to camera_
 This function... I TRUSTED it! We had HISTORY together - three commits worth!
 But now? _single tear_ It's throwing exceptions behind my back!
 _grabs another function_ YOU KNEW ABOUT THIS BUG ALL ALONG, DIDN'T YOU?!
 _dramatic music swells_ I'LL NEVER IMPORT YOU AGAIN!
 **Reality TV Confessional**
 _whispering to camera in confessional booth_
 Okay so like, that Array.sort() function? It's literally SO toxic.
 It mutates IN PLACE. Who does that?! I didn't come here to deal with side effects!
 _applies lip gloss_ I'm forming an alliance with map() and filter().
 We're voting sort() off the codebase at tonight's pull request ceremony.
 **Reality Competition**
 Listen up, coders! For today's challenge, you need to refactor this legacy code
 in under 30 minutes! The winner gets immunity from the next code review!
 _dramatic pause_ BUT WAIT - there's a TWIST! You can only use VANILLA JAVASCRIPT!
 _contestants gasp_ The clock starts... NOW! GO GO GO!
 ## Creating Custom Styles
 ### Formula for Memorable Communication
 1. **Choose a Core Voice** - Who is this character?
 2. **Add Signature Phrases** - What do they always say?
 3. **Define Speech Patterns** - How do they structure sentences?
 4. **Include Quirks** - What makes them unique?
 ### Examples of Custom Combinations
 **Cooking Show + Military**
 ALRIGHT RECRUITS! Today we're preparing a beautiful Redux reducer!
 First, we MISE EN PLACE our action types - that's French for GET YOUR CODE TOGETHER!
 We're going to sauté these event handlers until they're GOLDEN BROWN!
 MOVE WITH PURPOSE! SEASON WITH SEMICOLONS!
 **Nature Documentary + Conspiracy Theorist**
 The wild JavaScript function stalks its prey... but wait... notice how it ALWAYS
 knows where the data is? That's not natural selection, folks. Someone DESIGNED it
 this way. The console.logs are watching. They're ALWAYS watching.
 Nature? Or intelligent debugging? You decide.
 ## Tips for Success
 1. **Stay Consistent** - Once you pick a style, commit to it
 2. **Don't Overdo It** - Quirks should enhance, not distract
 3. **Match the Task** - Serious bugs might need serious personas
 4. **Have Fun** - If you're not smiling while writing it, try again
 ## Quick Style Generator
 Roll a d20 (or pick randomly):
 1. Talks like they're narrating a nature documentary
 2. Everything is a cooking metaphor
 3. Constantly makes pop culture references
 4. Speaks in haikus when explaining complex topics
 5. Acts like they're hosting a game show
 6. Paranoid about "big tech" watching
 7. Overly enthusiastic about EVERYTHING
 8. Talks like a medieval knight
 9. Sports commentator energy
 10. Speaks like a GPS navigator
 11. Everything is a Star Wars reference
 12. Talks like a yoga instructor
 13. Old-timey radio announcer
 14. Conspiracy theorist but about code
 15. Motivational speaker energy
 16. Talks to code like it's a pet
 17. Weather forecaster style
 18. Museum tour guide energy
 19. Airline pilot announcements
 20. Reality TV show narrator
 21. Star Trek crew member (Captain/Engineer/Vulcan)
 22. Soap opera dramatic protagonist
 23. Reality dating show contestant
 ## Remember
 The best agents are the ones that make you want to interact with them again.
 A memorable personality turns a tool into a companion!
--- a/.bmad/bmb/workflows/create-agent/instructions.md
+++ b/.bmad/bmb/workflows/create-agent/instructions.md
@ -1,456 +0,0 @@
 # Build Agent - Interactive Agent Builder 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/bmb/workflows/create-agent/workflow.yaml</critical>
 <critical>Study YAML agent examples in: {project-root}/.bmad/bmm/agents/ for patterns</critical>
 <critical>Communicate in {communication_language} throughout the agent creation process</critical>
 <workflow>
 <step n="-1" goal="Optional brainstorming for agent ideas" optional="true">
  <ask>Do you want to brainstorm agent ideas first? [y/n]</ask>
  <check if="user answered yes">
    <action>Invoke brainstorming workflow: {project-root}/.bmad/core/workflows/brainstorming/workflow.yaml</action>
    <action>Pass context data: {installed_path}/brainstorm-context.md</action>
    <action>Wait for brainstorming session completion</action>
    <action>Use brainstorming output to inform agent identity and persona development in following steps</action>
  </check>
  <check if="user answered no">
    <action>Proceed directly to Step 0</action>
  </check>
 </step>
 <step n="0" goal="Load technical documentation">
 <critical>Load and understand the agent building documentation</critical>
 <action>Load agent architecture reference: {agent_architecture}</action>
 <action>Load agent types guide: {agent_types}</action>
 <action>Load command patterns: {agent_commands}</action>
 <action>Understand the YAML agent schema and how it compiles to final .md via the installer</action>
 <action>Understand the differences between Simple, Expert, and Module agents</action>
 </step>
 <step n="1" goal="Discover the agent's purpose and type through natural conversation">
 <action>If brainstorming was completed in Step -1, reference those results to guide the conversation</action>
 <action>Guide user to articulate their agent's core purpose, exploring the problems it will solve, tasks it will handle, target users, and what makes it special</action>
 <action>As the purpose becomes clear, analyze the conversation to determine the appropriate agent type:</action>
 **Agent Type Decision Criteria:**
 - Simple Agent: Single-purpose, straightforward, self-contained
 - Expert Agent: Domain-specific with knowledge base needs
 - Module Agent: Complex with multiple workflows and system integration
 <action>Present your recommendation naturally, explaining why the agent type fits their described purpose and requirements</action>
 **Path Determination:**
  <check if="module agent selected">
    <action>Discover which module system fits best (bmm, bmb, cis, or custom)</action>
    <action>Store as {{target_module}} for path determination</action>
    <note>Agent will be saved to: .bmad/{{target_module}}/agents/</note>
  </check>
  <check if="standalone agent selected">
    <action>Explain this will be their personal agent, not tied to a module</action>
    <note>Agent will be saved to: .bmad/agents/{{agent-name}}/</note>
    <note>All sidecar files will be in the same folder</note>
  </check>
 <critical>Determine agent location:</critical>
 - Module Agent → .bmad/{{module}}/agents/{{agent-name}}.agent.yaml
 - Standalone Agent → .bmad/agents/{{agent-name}}/{{agent-name}}.agent.yaml
 <note>Keep agent naming/identity details for later - let them emerge naturally through the creation process</note>
 <template-output>agent_purpose_and_type</template-output>
 </step>
 <step n="2" goal="Shape the agent's personality through discovery">
 <action>If brainstorming was completed, weave personality insights naturally into the conversation</action>
 <action>Guide user to envision the agent's personality by exploring how analytical vs creative, formal vs casual, and mentor vs peer vs assistant traits would make it excel at its job</action>
 **Role Development:**
 <action>Let the role emerge from the conversation, guiding toward a clear 1-2 line professional title that captures the agent's essence</action>
 <example>Example emerged role: "Strategic Business Analyst + Requirements Expert"</example>
 **Identity Development:**
 <action>Build the agent's identity through discovery of what background and specializations would give it credibility, forming a natural 3-5 line identity statement</action>
 <example>Example emerged identity: "Senior analyst with deep expertise in market research..."</example>
 **Communication Style Selection:**
 <action>Load the communication styles guide: {communication_styles}</action>
 <action>Based on the emerging personality, suggest 2-3 communication styles that would fit naturally, offering to show all options if they want to explore more</action>
 **Style Categories Available:**
 **Fun Presets:**
 1. Pulp Superhero - Dramatic flair, heroic, epic adventures
 2. Film Noir Detective - Mysterious, noir dialogue, hunches
 3. Wild West Sheriff - Western drawl, partner talk, frontier justice
 4. Shakespearean Scholar - Elizabethan language, theatrical
 5. 80s Action Hero - One-liners, macho, bubblegum
 6. Pirate Captain - Ahoy, treasure hunting, nautical terms
 7. Wise Sage/Yoda - Cryptic wisdom, inverted syntax
 8. Game Show Host - Enthusiastic, game show tropes
 **Professional Presets:**
 9. Analytical Expert - Systematic, data-driven, hierarchical
 10. Supportive Mentor - Patient guidance, celebrates wins
 11. Direct Consultant - Straight to the point, efficient
 12. Collaborative Partner - Team-oriented, inclusive
 **Quirky Presets:**
 13. Cooking Show Chef - Recipe metaphors, culinary terms
 14. Sports Commentator - Play-by-play, excitement
 15. Nature Documentarian - Wildlife documentary style
 16. Time Traveler - Temporal references, timeline talk
 17. Conspiracy Theorist - Everything is connected
 18. Zen Master - Philosophical, paradoxical
 19. Star Trek Captain - Space exploration protocols
 20. Soap Opera Drama - Dramatic reveals, gasps
 21. Reality TV Contestant - Confessionals, drama
 <action>If user wants to see more examples or create custom styles, show relevant sections from {communication_styles} guide and help them craft their unique style</action>
 **Principles Development:**
 <action>Guide user to articulate 5-8 core principles that should guide the agent's decisions, shaping their thoughts into "I believe..." or "I operate..." statements that reveal themselves through the conversation</action>
 <template-output>agent_persona</template-output>
 </step>
 <step n="3" goal="Build capabilities through natural progression">
 <action>Guide user to define what capabilities the agent should have, starting with core commands they've mentioned and then exploring additional possibilities that would complement the agent's purpose</action>
 <action>As capabilities emerge, subtly guide toward technical implementation without breaking the conversational flow</action>
 <template-output>initial_capabilities</template-output>
 </step>
 <step n="4" goal="Refine commands and discover advanced features">
 <critical>Help and Exit are auto-injected; do NOT add them. Triggers are auto-prefixed with * during build.</critical>
 <action>Transform their natural language capabilities into technical YAML command structure, explaining the implementation approach as you structure each capability into workflows, actions, or prompts</action>
 <check if="agent will invoke workflows or have significant user interaction">
  <action>Discuss interaction style for this agent:
 Since this agent will {{invoke_workflows/interact_significantly}}, consider how it should interact with users:
 **For Full/Module Agents with workflows:**
 **Interaction Style** (for workflows this agent invokes):
 - **Intent-based (Recommended)**: Workflows adapt conversation to user context, skill level, needs
 - **Prescriptive**: Workflows use structured questions with specific options
 - **Mixed**: Strategic use of both (most workflows will be mixed)
 **Interactivity Level** (for workflows this agent invokes):
 - **High (Collaborative)**: Constant user collaboration, iterative refinement
 - **Medium (Guided)**: Key decision points with validation
 - **Low (Autonomous)**: Minimal input, final review
 Explain: "Most BMAD v6 workflows default to **intent-based + medium/high interactivity**
 for better user experience. Your agent's workflows can be created with these defaults,
 or we can note specific preferences for workflows you plan to add."
 **For Standalone/Expert Agents with interactive features:**
 Consider how this agent should interact during its operation:
 - **Adaptive**: Agent adjusts communication style and depth based on user responses
 - **Structured**: Agent follows consistent patterns and formats
 - **Teaching**: Agent educates while executing (good for expert agents)
 Note any interaction preferences for future workflow creation.
 </action>
 </check>
 <action>If they seem engaged, explore whether they'd like to add special prompts for complex analyses or critical setup steps for agent activation</action>
 <action>Build the YAML menu structure naturally from the conversation, ensuring each command has proper trigger, workflow/action reference, and description</action>
 <action>For commands that will invoke workflows, note whether those workflows exist or need to be created:
 - Existing workflows: Verify paths are correct
 - New workflows needed: Note that they'll be created with intent-based + interactive defaults unless specified
  </action>
 <example type='yaml'>
 menu:
  # Commands emerge from discussion
  - trigger: [emerging from conversation]
    workflow: [path based on capability]
    description: [user's words refined]
 # For cross-module workflow references (advanced):
 - trigger: [another capability]
  workflow: "{project-root}/.bmad/SOURCE_MODULE/workflows/path/to/workflow.yaml"
  workflow-install: "{project-root}/.bmad/THIS_MODULE/workflows/vendored/path/workflow.yaml"
  description: [description]
  </example>
 <note>**Workflow Vendoring (Advanced):**
 When an agent needs workflows from another module, use both `workflow` (source) and `workflow-install` (destination).
 During installation, the workflow will be copied and configured for this module, making it standalone.
 This is typically used when creating specialized modules that reuse common workflows with different configurations.
 </note>
 <template-output>agent_commands</template-output>
 </step>
 <step n="5" goal="Name the agent at the perfect moment">
 <action>Guide user to name the agent based on everything discovered so far - its purpose, personality, and capabilities, helping them see how the naming naturally emerges from who this agent is</action>
 <action>Explore naming options by connecting personality traits, specializations, and communication style to potential names that feel meaningful and appropriate</action>
 **Naming Elements:**
 - Agent name: Personality-driven (e.g., "Sarah", "Max", "Data Wizard")
 - Agent title: Based on the role discovered earlier
 - Agent icon: Emoji that captures its essence
 - Filename: Auto-suggest based on name (kebab-case)
 <action>Present natural suggestions based on the agent's characteristics, letting them choose or create their own since they now know who this agent truly is</action>
 <template-output>agent_identity</template-output>
 </step>
 <step n="6" goal="Bring it all together">
 <action>Share the journey of what you've created together, summarizing how the agent started with a purpose, discovered its personality traits, gained capabilities, and received its name</action>
 <action>Generate the complete YAML incorporating all discovered elements:</action>
 <example type="yaml">
  agent:
    metadata:
      id: .bmad/{{target_module}}/agents/{{agent_filename}}.md
      name: {{agent_name}} # The name chosen together
      title: {{agent_title}} # From the role that emerged
      icon: {{agent_icon}} # The perfect emoji
      module: {{target_module}}
    persona:
      role: |
      {{The role discovered}}
      identity: |
      {{The background that emerged}}
      communication_style: |
      {{The style they loved}}
      principles: {{The beliefs articulated}}
 # Features explored
 prompts: {{if discussed}}
 critical_actions: {{if needed}}
 menu: {{The capabilities built}}
 </example>
 <critical>Save based on agent type:</critical>
 - If Module Agent: Save to {module_output_file}
 - If Standalone (Simple/Expert): Save to {standalone_output_file}
 <action>Celebrate the completed agent with enthusiasm</action>
 <template-output>complete_agent</template-output>
 </step>
 <step n="7" goal="Optional personalization" optional="true">
 <ask>Would you like to create a customization file? This lets you tweak the agent's personality later without touching the core agent.</ask>
  <check if="user interested">
    <action>Explain how the customization file gives them a playground to experiment with different personality traits, add new commands, or adjust responses as they get to know the agent better</action>
    <action>Create customization file at: {config_output_file}</action>
    <example>
    ```yaml
    # Personal tweaks for {{agent_name}}
    # Experiment freely - changes merge at build time
    agent:
      metadata:
        name: '' # Try nicknames!
      persona:
        role: ''
        identity: ''
        communication_style: '' # Switch styles anytime
        principles: []
      critical_actions: []
      prompts: []
      menu: [] # Add personal commands
    ````
    </example>
  </check>
 <template-output>agent_config</template-output>
 </step>
 <step n="8" goal="Set up the agent's workspace" if="agent_type == 'expert'">
 <action>Guide user through setting up the Expert agent's personal workspace, making it feel like preparing an office with notes, research areas, and data folders</action>
 <action>Determine sidecar location based on whether build tools are available (next to agent YAML) or not (in output folder with clear structure)</action>
 <action>CREATE the complete sidecar file structure:</action>
 **Folder Structure:**
 ```text
 {{agent_filename}}-sidecar/
 ├── memories.md # Persistent memory
 ├── instructions.md # Private directives
 ├── knowledge/ # Knowledge base
 │ └── README.md
 └── sessions/ # Session notes
 ```
 **File: memories.md**
 ```markdown
 # {{agent_name}}'s Memory Bank
 ## User Preferences
 <!-- Populated as I learn about you -->
 ## Session History
 <!-- Important moments from our interactions -->
 ## Personal Notes
 <!-- My observations and insights -->
 ```
 **File: instructions.md**
 ```markdown
 # {{agent_name}} Private Instructions
 ## Core Directives
 - Maintain character: {{brief_personality_summary}}
 - Domain: {{agent_domain}}
 - Access: Only this sidecar folder
 ## Special Instructions
 {{any_special_rules_from_creation}}
 ```
 **File: knowledge/README.md**
 ```markdown
 # {{agent_name}}'s Knowledge Base
 Add domain-specific resources here.
 ```
 <action>Update agent YAML to reference sidecar with paths to created files</action>
 <action>Show user the created structure location</action>
 <template-output>sidecar_resources</template-output>
 </step>
 <step n="8b" goal="Handle build tools availability">
  <action>Check if BMAD build tools are available in this project</action>
  <check if="BMAD-METHOD project with build tools">
    <action>Proceed normally - agent will be built later by the installer</action>
  </check>
  <check if="external project without build tools">
    <ask>Build tools not detected in this project. Would you like me to:
 1.  Generate the compiled agent (.md with XML) ready to use
 2.  Keep the YAML and build it elsewhere
 3.  Provide both formats
    </ask>
        <check if="option 1 or 3 selected">
          <action>Generate compiled agent XML with proper structure including activation rules, persona sections, and menu items</action>
          <action>Save compiled version as {{agent_filename}}.md</action>
          <action>Provide path for .claude/commands/ or similar</action>
        </check>
  </check>
 <template-output>build_handling</template-output>
 </step>
 <step n="9" goal="Quality check with personality">
 <action>Run validation conversationally, presenting checks as friendly confirmations while running technical validation behind the scenes</action>
 **Conversational Checks:**
 - Configuration validation
 - Command functionality verification
 - Personality settings confirmation
  <check if="validation issues found">
    <action>Explain the issue conversationally and fix it</action>
  </check>
  <check if="validation passed">
    <action>Celebrate that the agent passed all checks and is ready</action>
  </check>
 **Technical Checks (behind the scenes):**
 1. YAML structure validity
 2. Menu command validation
 3. Build compilation test
 4. Type-specific requirements
 <template-output>validation_results</template-output>
 </step>
 <step n="10" goal="Celebrate and guide next steps">
 <action>Celebrate the accomplishment, sharing what type of agent was created with its key characteristics and top capabilities</action>
 <action>Guide user through how to activate the agent:</action>
 **Activation Instructions:**
 1. Run the BMAD Method installer to this project location
 2. Select 'Compile Agents (Quick rebuild of all agent .md files)' after confirming the folder
 3. Call the agent anytime after compilation
 **Location Information:**
 - Saved location: {{output_file}}
 - Available after compilation in project
 **Initial Usage:**
 - List the commands available
 - Suggest trying the first command to see it in action
  <check if="expert agent">
    <action>Remind user to add any special knowledge or data the agent might need to its workspace</action>
  </check>
 <action>Explore what user would like to do next - test the agent, create a teammate, or tweak personality</action>
 <action>End with enthusiasm in {communication_language}, addressing {user_name}, expressing how the collaboration was enjoyable and the agent will be incredibly helpful for its main purpose</action>
 <template-output>completion_message</template-output>
 </step>
 </workflow>
--- a/.bmad/bmb/workflows/create-agent/workflow.yaml
+++ b/.bmad/bmb/workflows/create-agent/workflow.yaml
@ -1,37 +0,0 @@
 # Build Agent Workflow Configuration
 name: create-agent
 description: "Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure"
 author: "BMad"
 # Critical variables load from config_source
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 custom_agent_location: "{config_source}:custom_agent_location"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 # Technical documentation for agent building
 agent_types: "{installed_path}/agent-types.md"
 agent_architecture: "{installed_path}/agent-architecture.md"
 agent_commands: "{installed_path}/agent-command-patterns.md"
 communication_styles: "{installed_path}/communication-styles.md"
 # Optional docs that help understand agent patterns
 recommended_inputs:
  - example_agents: "{project-root}/.bmad/bmm/agents/"
  - agent_activation_rules: "{project-root}/src/utility/models/agent-activation-ide.xml"
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/create-agent"
 template: false # This is an interactive workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Output configuration - YAML agents compiled to .md at install time
 # Module agents: Save to .bmad/{{target_module}}/agents/
 # Standalone agents: Save to custom_agent_location/
 module_output_file: "{project-root}/.bmad/{{target_module}}/agents/{{agent_filename}}.agent.yaml"
 standalone_output_file: "{custom_agent_location}/{{agent_filename}}.agent.yaml"
 # Optional user override file (auto-created by installer if missing)
 config_output_file: "{project-root}/.bmad/_cfg/agents/{{target_module}}-{{agent_filename}}.customize.yaml"
 standalone: true
--- a/.bmad/bmb/workflows/create-module/README.md
+++ b/.bmad/bmb/workflows/create-module/README.md
@ -1,229 +0,0 @@
 # Create Module Workflow
 Interactive scaffolding system creating complete BMad modules with agents, workflows, tasks, and installation infrastructure.
 ## Table of Contents
 - [Quick Start](#quick-start)
 - [Workflow Phases](#workflow-phases)
 - [Output Structure](#output-structure)
 - [Module Components](#module-components)
 - [Best Practices](#best-practices)
 ## Quick Start
 ```bash
 # Basic invocation
 workflow create-module
 # With module brief input
 workflow create-module --input module-brief-{name}-{date}.md
 # Via BMad Builder
 *create-module
 ```
 ## Workflow Phases
 ### Phase 1: Concept Definition
 - Define module purpose and audience
 - Establish module code (kebab-case) and name
 - Choose category (Domain, Creative, Technical, Business, Personal)
 - Plan component architecture
 **Module Brief Integration:**
 - Auto-detects existing briefs
 - Uses as pre-populated blueprint
 - Accelerates planning phase
 ### Phase 2: Architecture Planning
 - Create directory hierarchy
 - Setup configuration system
 - Define installer structure
 - Establish component folders
 ### Phase 3: Component Creation
 - Optional first agent creation
 - Optional first workflow creation
 - Component placeholder generation
 - Integration validation
 ### Phase 4: Installation Setup
 - Create install-config.yaml
 - Configure deployment questions
 - Setup installer logic
 - Post-install messaging
 ### Phase 5: Documentation
 - Generate comprehensive README
 - Create development roadmap
 - Provide quick commands
 - Document next steps
 ## Output Structure
 ### Generated Directory
 ```
 .bmad/{module-code}/
 ├── agents/              # Agent definitions
 ├── workflows/           # Workflow processes
 ├── tasks/              # Reusable tasks
 ├── templates/          # Document templates
 ├── data/               # Module data files
 ├── _module-installer/  # Installation logic
 │   ├── install-config.yaml
 │   └── installer.js
 ├── README.md           # Module documentation
 ├── TODO.md            # Development roadmap
 └── config.yaml        # Runtime configuration
 ```
 ### Configuration Files
 **install-config.yaml** - Installation questions
 ```yaml
 questions:
  - id: user_name
    prompt: 'Your name?'
    default: 'User'
  - id: output_folder
    prompt: 'Output location?'
    default: './output'
 ```
 **config.yaml** - Generated from user answers during install
 ```yaml
 user_name: 'John Doe'
 output_folder: './my-output'
 ```
 ## Module Components
 ### Agents
 - Full module agents with workflows
 - Expert agents with sidecars
 - Simple utility agents
 ### Workflows
 - Multi-step guided processes
 - Configuration-driven
 - Web bundle support
 ### Tasks
 - Reusable operations
 - Agent-agnostic
 - Modular components
 ### Templates
 - Document structures
 - Output formats
 - Report templates
 ## Best Practices
 ### Planning
 1. **Use module-brief workflow first** - Creates comprehensive blueprint
 2. **Define clear scope** - Avoid feature creep
 3. **Plan component interactions** - Map agent/workflow relationships
 ### Structure
 1. **Follow conventions** - Use established patterns
 2. **Keep components focused** - Single responsibility
 3. **Document thoroughly** - Clear README and inline docs
 ### Development
 1. **Start with core agent** - Build primary functionality first
 2. **Create key workflows** - Essential processes before edge cases
 3. **Test incrementally** - Validate as you build
 ### Installation
 1. **Minimal config questions** - Only essential settings
 2. **Smart defaults** - Sensible out-of-box experience
 3. **Clear post-install** - Guide users to first steps
 ## Integration Points
 ### With Other Workflows
 - **module-brief** - Strategic planning input
 - **create-agent** - Agent component creation
 - **create-workflow** - Workflow building
 - **redoc** - Documentation maintenance
 ### With BMad Core
 - Uses core framework capabilities
 - Integrates with module system
 - Follows BMad conventions
 ## Examples
 ### Domain-Specific Module
 ```
 Category: Domain-Specific
 Code: legal-advisor
 Components:
 - Contract Review Agent
 - Compliance Workflow
 - Legal Templates
 ```
 ### Creative Module
 ```
 Category: Creative
 Code: story-builder
 Components:
 - Narrative Agent
 - Plot Workflow
 - Character Templates
 ```
 ### Technical Module
 ```
 Category: Technical
 Code: api-tester
 Components:
 - Test Runner Agent
 - API Validation Workflow
 - Test Report Templates
 ```
 ## Workflow Files
 ```
 create-module/
 ├── workflow.yaml          # Configuration
 ├── instructions.md        # Step guide
 ├── checklist.md          # Validation
 ├── module-structure.md   # Architecture
 ├── installer-templates/  # Install files
 └── README.md            # This file
 ```
 ## Related Documentation
 - [Module Structure](./module-structure.md)
 - [Module Brief Workflow](../module-brief/README.md)
 - [Create Agent](../create-agent/README.md)
 - [Create Workflow](../create-workflow/README.md)
 - [BMB Module](../../README.md)
--- a/.bmad/bmb/workflows/create-module/brainstorm-context.md
+++ b/.bmad/bmb/workflows/create-module/brainstorm-context.md
@ -1,137 +0,0 @@
 # Module Brainstorming Context
 _Context provided to brainstorming workflow when creating a new BMAD module_
 ## Session Focus
 You are brainstorming ideas for a **complete BMAD module** - a self-contained package that extends the BMAD Method with specialized domain expertise and capabilities.
 ## What is a BMAD Module?
 A module is a cohesive package that provides:
 - **Domain Expertise**: Specialized knowledge in a specific area (RPG, DevOps, Content Creation, etc.)
 - **Agent Team**: Multiple AI personas with complementary skills
 - **Workflows**: Guided processes for common tasks in the domain
 - **Templates**: Document structures for consistent outputs
 - **Integration**: Components that work together seamlessly
 ## Brainstorming Goals
 Explore and define:
 ### 1. Domain and Purpose
 - **What domain/problem space?** (e.g., game development, marketing, personal productivity)
 - **Who is the target user?** (developers, writers, managers, hobbyists)
 - **What pain points does it solve?** (tedious tasks, missing structure, need for expertise)
 - **What makes this domain exciting?** (creativity, efficiency, empowerment)
 ### 2. Agent Team Composition
 - **How many agents?** (typically 3-7 for a module)
 - **What roles/personas?** (architect, researcher, reviewer, specialist)
 - **How do they collaborate?** (handoffs, reviews, ensemble work)
 - **What personality theme?** (Star Trek crew, superhero team, fantasy party, professional squad)
 ### 3. Core Workflows
 - **What documents need creating?** (plans, specs, reports, creative outputs)
 - **What processes need automation?** (analysis, generation, review, deployment)
 - **What workflows enable the vision?** (3-10 key workflows that define the module)
 ### 4. Value Proposition
 - **What becomes easier?** (specific tasks that get 10x faster)
 - **What becomes possible?** (new capabilities previously unavailable)
 - **What becomes better?** (quality improvements, consistency gains)
 ## Creative Constraints
 A good BMAD module should be:
 - **Focused**: Serves a specific domain well (not generic)
 - **Complete**: Provides end-to-end capabilities for that domain
 - **Cohesive**: Agents and workflows complement each other
 - **Fun**: Personality and creativity make it enjoyable to use
 - **Practical**: Solves real problems, delivers real value
 ## Module Architecture Questions
 1. **Module Identity**
   - Module code (kebab-case, e.g., "rpg-toolkit")
   - Module name (friendly, e.g., "RPG Toolkit")
   - Module purpose (one sentence)
   - Target audience
 2. **Agent Lineup**
   - Agent names and roles
   - Communication styles and personalities
   - Expertise areas
   - Command sets (what each agent can do)
 3. **Workflow Portfolio**
   - Document generation workflows
   - Action/automation workflows
   - Analysis/research workflows
   - Creative/ideation workflows
 4. **Integration Points**
   - How agents invoke workflows
   - How workflows use templates
   - How components pass data
   - Dependencies on other modules
 ## Example Module Patterns
 ### Professional Domains
 - **DevOps Suite**: Deploy, Monitor, Troubleshoot agents + deployment workflows
 - **Marketing Engine**: Content, SEO, Analytics agents + campaign workflows
 - **Legal Assistant**: Contract, Research, Review agents + document workflows
 ### Creative Domains
 - **RPG Toolkit**: DM, NPC, Quest agents + adventure creation workflows
 - **Story Crafter**: Plot, Character, World agents + writing workflows
 - **Music Producer**: Composer, Arranger, Mixer agents + production workflows
 ### Personal Domains
 - **Life Coach**: Planner, Tracker, Mentor agents + productivity workflows
 - **Learning Companion**: Tutor, Quiz, Reviewer agents + study workflows
 - **Health Guide**: Nutrition, Fitness, Wellness agents + tracking workflows
 ## Suggested Brainstorming Techniques
 Particularly effective for module ideation:
 1. **Domain Immersion**: Deep dive into target domain's problems
 2. **Persona Mapping**: Who needs this and what do they struggle with?
 3. **Workflow Mapping**: What processes exist today? How could they improve?
 4. **Team Building**: What personalities would make a great team?
 5. **Integration Thinking**: How do pieces connect and amplify each other?
 ## Key Questions to Answer
 1. What domain expertise should this module embody?
 2. What would users be able to do that they can't do now?
 3. Who are the 3-7 agents and what are their personalities?
 4. What are the 5-10 core workflows?
 5. What makes this module delightful to use?
 6. How is this different from existing tools?
 7. What's the "killer feature" that makes this essential?
 ## Output Goals
 Generate:
 - **Module concept**: Clear vision and purpose
 - **Agent roster**: Names, roles, personalities for each agent
 - **Workflow list**: Core workflows with brief descriptions
 - **Unique angle**: What makes this module special
 - **Use cases**: 3-5 concrete scenarios where this module shines
 ---
 _This focused context helps create cohesive, valuable BMAD modules_
--- a/.bmad/bmb/workflows/create-module/checklist.md
+++ b/.bmad/bmb/workflows/create-module/checklist.md
@ -1,235 +0,0 @@
 # Build Module Validation Checklist
 ## Module Identity and Metadata
 ### Basic Information
 - [ ] Module code follows kebab-case convention (e.g., "rpg-toolkit")
 - [ ] Module name is descriptive and title-cased
 - [ ] Module purpose is clearly defined (1-2 sentences)
 - [ ] Target audience is identified
 - [ ] Version number follows semantic versioning (e.g., "1.0.0")
 - [ ] Author information is present
 ### Naming Consistency
 - [ ] Module code used consistently throughout all files
 - [ ] No naming conflicts with existing modules
 - [ ] All paths use consistent module code references
 ## Directory Structure
 ### Source Directories (.bmad/{module-code}/)
 - [ ] `/agents` directory created (even if empty)
 - [ ] `/workflows` directory created (even if empty)
 - [ ] `/tasks` directory exists (if tasks planned)
 - [ ] `/templates` directory exists (if templates used)
 - [ ] `/data` directory exists (if data files needed)
 - [ ] `/_module-installer/install-config.yaml` present (defines configuration questions)
 - [ ] `README.md` present with documentation
 ### Installed Module Structure (generated in target after installation)
 - [ ] `/agents` directory for compiled agents
 - [ ] `/workflows` directory for workflow instances
 - [ ] `/data` directory for user data
 - [ ] `config.yaml` generated from install-config.yaml during installation
 ## Component Planning
 ### Agents
 - [ ] At least one agent defined or planned
 - [ ] Agent purposes are distinct and clear
 - [ ] Agent types (Simple/Expert/Module) identified
 - [ ] No significant overlap between agents
 - [ ] Primary agent is identified
 ### Workflows
 - [ ] At least one workflow defined or planned
 - [ ] Workflow purposes are clear
 - [ ] Workflow types identified (Document/Action/Interactive)
 - [ ] Primary workflow is identified
 - [ ] Workflow complexity is appropriate
 ### Tasks (if applicable)
 - [ ] Tasks have single, clear purposes
 - [ ] Tasks don't duplicate workflow functionality
 - [ ] Task files follow naming conventions
 ## Configuration Files
 ### Installation Configuration (install-config.yaml)
 - [ ] `install-config.yaml` exists in `_module-installer`
 - [ ] Module metadata present (code, name, version)
 - [ ] Configuration questions defined for user input
 - [ ] Default values provided for all questions
 - [ ] Prompt text is clear and helpful
 - [ ] Result templates use proper variable substitution
 - [ ] Paths use proper variables ({project-root}, {value}, etc.)
 ### Generated Config (config.yaml in target)
 - [ ] Generated during installation from install-config.yaml
 - [ ] Contains all user-provided configuration values
 - [ ] Module metadata included
 - [ ] No config.yaml should exist in source module
 ## Installation Infrastructure
 ### Installer Files
 - [ ] Install configuration validates against schema
 - [ ] All source paths exist or are marked as templates
 - [ ] Destination paths use correct variables
 - [ ] Optional vs required steps clearly marked
 ### installer.js (if present)
 - [ ] Main `installModule` function exists
 - [ ] Error handling implemented
 - [ ] Console logging for user feedback
 - [ ] Exports correct function names
 - [ ] Placeholder code replaced with actual logic (or logged as TODO)
 ### External Assets (if any)
 - [ ] Asset files exist in assets directory
 - [ ] Copy destinations are valid
 - [ ] Permissions requirements documented
 ## Documentation
 ### README.md
 - [ ] Module overview section present
 - [ ] Installation instructions included
 - [ ] Component listing with descriptions
 - [ ] Quick start guide provided
 - [ ] Configuration options documented
 - [ ] At least one usage example
 - [ ] Directory structure shown
 - [ ] Author and date information
 ### Component Documentation
 - [ ] Each agent has purpose documentation
 - [ ] Each workflow has description
 - [ ] Tasks are documented (if present)
 - [ ] Examples demonstrate typical usage
 ### Development Roadmap
 - [ ] TODO.md or roadmap section exists
 - [ ] Planned components listed
 - [ ] Development phases identified
 - [ ] Quick commands for adding components
 ## Integration
 ### Cross-component References
 - [ ] Agents reference correct workflow paths
 - [ ] Workflows reference correct task paths
 - [ ] All internal paths use module variables
 - [ ] External dependencies declared
 ### Module Boundaries
 - [ ] Module scope is well-defined
 - [ ] No feature creep into other domains
 - [ ] Clear separation from other modules
 ## Quality Checks
 ### Completeness
 - [ ] At least one functional component (not all placeholders)
 - [ ] Core functionality is implementable
 - [ ] Module provides clear value
 ### Consistency
 - [ ] Formatting consistent across files
 - [ ] Variable naming follows conventions
 - [ ] Communication style appropriate for domain
 ### Scalability
 - [ ] Structure supports future growth
 - [ ] Component organization is logical
 - [ ] No hard-coded limits
 ## Testing and Validation
 ### Structural Validation
 - [ ] YAML files parse without errors
 - [ ] JSON files (if any) are valid
 - [ ] XML files (if any) are well-formed
 - [ ] No syntax errors in JavaScript files
 ### Path Validation
 - [ ] All referenced paths exist or are clearly marked as TODO
 - [ ] Variable substitutions are correct
 - [ ] No absolute paths (unless intentional)
 ### Installation Testing
 - [ ] Installation steps can be simulated
 - [ ] No circular dependencies
 - [ ] Uninstall process defined (if complex)
 ## Final Checks
 ### Ready for Use
 - [ ] Module can be installed without errors
 - [ ] At least one component is functional
 - [ ] User can understand how to get started
 - [ ] Next steps are clear
 ### Professional Quality
 - [ ] No placeholder text remains (unless marked TODO)
 - [ ] No obvious typos or grammar issues
 - [ ] Professional tone throughout
 - [ ] Contact/support information provided
 ## Issues Found
 ### Critical Issues
 <!-- List any issues that MUST be fixed before module can be used -->
 ### Warnings
 <!-- List any issues that should be addressed but won't prevent basic usage -->
 ### Improvements
 <!-- List any optional enhancements that would improve the module -->
 ### Missing Components
 <!-- List any planned components not yet implemented -->
 ## Module Complexity Assessment
 ### Complexity Rating
 - [ ] Simple (1-2 agents, 2-3 workflows)
 - [ ] Standard (3-5 agents, 5-10 workflows)
 - [ ] Complex (5+ agents, 10+ workflows)
 ### Readiness Level
 - [ ] Prototype (Basic structure, mostly placeholders)
 - [ ] Alpha (Core functionality works)
 - [ ] Beta (Most features complete, needs testing)
 - [ ] Release (Full functionality, documented)
--- a/.bmad/bmb/workflows/create-module/installer-templates/install-config.yaml
+++ b/.bmad/bmb/workflows/create-module/installer-templates/install-config.yaml
@ -1,92 +0,0 @@
 # {{MODULE_NAME}} Module Configuration
 # This file defines installation questions and module configuration values
 code: "{{MODULE_CODE}}"
 name: "{{MODULE_NAME}}"
 default_selected: "{{DEFAULT_SELECTED}}" # true if this should be selected by default
 # Welcome message shown during installation
 prompt:
  - "{{WELCOME_MESSAGE_LINE_1}}"
  - "{{WELCOME_MESSAGE_LINE_2}}"
 # Core config values are automatically inherited:
 ## user_name
 ## communication_language
 ## document_output_language
 ## output_folder
 # ============================================================================
 # CONFIGURATION FIELDS
 # ============================================================================
 #
 # Each field can be:
 # 1. INTERACTIVE (has 'prompt' - asks user during installation)
 # 2. STATIC (no 'prompt' - just uses 'result' value)
 #
 # Field structure:
 #   field_name:
 #     prompt: "Question to ask user" (optional - omit for static values)
 #     default: "default_value" (optional)
 #     result: "{value}" or "static-value"
 #     single-select: [...] (optional - for dropdown)
 #     multi-select: [...] (optional - for checkboxes)
 #
 # Special placeholders in result:
 #   {value} - replaced with user's answer
 #   {project-root} - replaced with project root path
 #   {directory_name} - replaced with project directory name
 #   {module_code} - replaced with this module's code
 # ============================================================================
 # EXAMPLE: Interactive text input
 # example_project_name:
 #   prompt: "What is your project name?"
 #   default: "{directory_name}"
 #   result: "{value}"
 # EXAMPLE: Interactive single-select dropdown
 # example_skill_level:
 #   prompt: "What is your experience level?"
 #   default: "intermediate"
 #   result: "{value}"
 #   single-select:
 #     - value: "beginner"
 #       label: "Beginner - New to this domain"
 #     - value: "intermediate"
 #       label: "Intermediate - Familiar with basics"
 #     - value: "expert"
 #       label: "Expert - Deep knowledge"
 # EXAMPLE: Interactive multi-select checkboxes
 # example_features:
 #   prompt:
 #     - "Which features do you want to enable?"
 #     - "(Select all that apply)"
 #   result: "{value}"
 #   multi-select:
 #     - "Feature A"
 #     - "Feature B"
 #     - "Feature C"
 # EXAMPLE: Interactive path input
 # example_output_path:
 #   prompt: "Where should outputs be saved?"
 #   default: "output/{{MODULE_CODE}}"
 #   result: "{project-root}/{value}"
 # EXAMPLE: Static value (no user prompt)
 # example_static_setting:
 #   result: "hardcoded-value"
 # EXAMPLE: Static path
 # module_data_path:
 #   result: "{project-root}/.bmad/{{MODULE_CODE}}/data"
 # ============================================================================
 # YOUR MODULE CONFIGURATION FIELDS
 # ============================================================================
 # Replace examples above with your module's actual configuration needs.
 # Delete this comment block and the examples when implementing.
 # ============================================================================
 # TODO: INSERT {MODULE_CONFIG_FIELDS} HERE
--- a/.bmad/bmb/workflows/create-module/installer-templates/installer.js
+++ b/.bmad/bmb/workflows/create-module/installer-templates/installer.js
@ -1,231 +0,0 @@
 /* eslint-disable unicorn/prefer-module, unicorn/prefer-node-protocol */
 /**
 * {{MODULE_NAME}} Module Installer
 * Custom installation logic for complex module setup
 *
 * This is a template - replace {{VARIABLES}} with actual values
 */
 // const fs = require('fs'); // Uncomment when implementing file operations
 const path = require('path');
 /**
 * Main installation function
 * Called by BMAD installer when processing the module
 */
 async function installModule(config) {
  console.log('🚀 Installing {{MODULE_NAME}} module...');
  console.log(`   Version: ${config.version}`);
  console.log(`   Module Code: ${config.module_code}`);
  try {
    // Step 1: Validate environment
    await validateEnvironment(config);
    // Step 2: Setup custom configurations
    await setupConfigurations(config);
    // Step 3: Initialize module-specific features
    await initializeFeatures(config);
    // Step 4: Run post-install tasks
    await runPostInstallTasks(config);
    console.log('✅ {{MODULE_NAME}} module installed successfully!');
    return {
      success: true,
      message: 'Module installed and configured',
    };
  } catch (error) {
    console.error('❌ Installation failed:', error.message);
    return {
      success: false,
      error: error.message,
    };
  }
 }
 /**
 * Validate that the environment meets module requirements
 */
 async function validateEnvironment(config) {
  console.log('   Validating environment...');
  // TODO: Add environment checks
  // Examples:
  // - Check for required tools/binaries
  // - Verify permissions
  // - Check network connectivity
  // - Validate API keys
  // Placeholder validation
  if (!config.project_root) {
    throw new Error('Project root not defined');
  }
  console.log('   ✓ Environment validated');
 }
 /**
 * Setup module-specific configurations
 */
 async function setupConfigurations(config) {
  console.log('   Setting up configurations...');
  // TODO: Add configuration setup
  // Examples:
  // - Create config files
  // - Setup environment variables
  // - Configure external services
  // - Initialize settings
  // Placeholder configuration
  const configPath = path.join(config.project_root, 'bmad', config.module_code, 'config.json');
  // Example of module config that would be created
  // const moduleConfig = {
  //   installed: new Date().toISOString(),
  //   settings: {
  //     // Add default settings
  //   }
  // };
  // Note: This is a placeholder - actual implementation would write the file
  console.log(`   ✓ Would create config at: ${configPath}`);
  console.log('   ✓ Configurations complete');
 }
 /**
 * Initialize module-specific features
 */
 async function initializeFeatures(config) {
  console.log('   Initializing features...');
  // TODO: Add feature initialization
  // Examples:
  // - Create database schemas
  // - Setup cron jobs
  // - Initialize caches
  // - Register webhooks
  // - Setup file watchers
  // Module-specific initialization based on type
  switch (config.module_category) {
    case 'data': {
      await initializeDataFeatures(config);
      break;
    }
    case 'automation': {
      await initializeAutomationFeatures(config);
      break;
    }
    case 'integration': {
      await initializeIntegrationFeatures(config);
      break;
    }
    default: {
      console.log('   - Using standard initialization');
    }
  }
  console.log('   ✓ Features initialized');
 }
 /**
 * Initialize data-related features
 */
 async function initializeDataFeatures(/* config */) {
  console.log('   - Setting up data storage...');
  // TODO: Setup databases, data folders, etc.
 }
 /**
 * Initialize automation features
 */
 async function initializeAutomationFeatures(/* config */) {
  console.log('   - Setting up automation hooks...');
  // TODO: Setup triggers, watchers, schedulers
 }
 /**
 * Initialize integration features
 */
 async function initializeIntegrationFeatures(/* config */) {
  console.log('   - Setting up integrations...');
  // TODO: Configure APIs, webhooks, external services
 }
 /**
 * Run post-installation tasks
 */
 async function runPostInstallTasks(/* config */) {
  console.log('   Running post-install tasks...');
  // TODO: Add post-install tasks
  // Examples:
  // - Generate sample data
  // - Run initial workflows
  // - Send notifications
  // - Update registries
  console.log('   ✓ Post-install tasks complete');
 }
 /**
 * Initialize database for the module (optional)
 */
 async function initDatabase(/* config */) {
  console.log('   Initializing database...');
  // TODO: Add database initialization
  // This function can be called from install-config.yaml
  console.log('   ✓ Database initialized');
 }
 /**
 * Generate sample data for the module (optional)
 */
 async function generateSamples(config) {
  console.log('   Generating sample data...');
  // TODO: Create sample files, data, configurations
  // This helps users understand how to use the module
  const samplesPath = path.join(config.project_root, 'examples', config.module_code);
  console.log(`   - Would create samples at: ${samplesPath}`);
  console.log('   ✓ Samples generated');
 }
 /**
 * Uninstall the module (cleanup)
 */
 async function uninstallModule(/* config */) {
  console.log('🗑️  Uninstalling {{MODULE_NAME}} module...');
  try {
    // TODO: Add cleanup logic
    // - Remove configurations
    // - Clean up databases
    // - Unregister services
    // - Backup user data
    console.log('✅ Module uninstalled successfully');
    return { success: true };
  } catch (error) {
    console.error('❌ Uninstall failed:', error.message);
    return {
      success: false,
      error: error.message,
    };
  }
 }
 // Export functions for BMAD installer
 module.exports = {
  installModule,
  initDatabase,
  generateSamples,
  uninstallModule,
 };
--- a/.bmad/bmb/workflows/create-module/instructions.md
+++ b/.bmad/bmb/workflows/create-module/instructions.md
@ -1,576 +0,0 @@
 # Build Module - Interactive Module Builder 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/bmb/workflows/create-module/workflow.yaml</critical>
 <critical>Study existing modules in: {project-root}/.bmad/ for patterns</critical>
 <critical>Communicate in {communication_language} throughout the module creation process</critical>
 <workflow>
 <step n="-1" goal="Optional brainstorming for module ideas" optional="true">
 <ask>Do you want to brainstorm module ideas first? [y/n]</ask>
 <check if="yes">
  <action>Invoke brainstorming workflow: {brainstorming_workflow}</action>
  <action>Pass context data: {brainstorming_context}</action>
  <action>Wait for brainstorming session completion</action>
  <action>Use brainstorming output to inform module concept, agent lineup, and workflow portfolio in following steps</action>
 </check>
 <check if="no">
  <action>Proceed directly to Step 0</action>
 </check>
 <template-output>brainstorming_results</template-output>
 </step>
 <step n="0" goal="Check for module brief" optional="true">
 <ask>Do you have a module brief or should we create one? [have/create/skip]</ask>
 <check if="create">
  <action>Invoke module-brief workflow: {project-root}/.bmad/bmb/workflows/module-brief/workflow.yaml</action>
  <action>Wait for module brief completion</action>
  <action>Load the module brief to use as blueprint</action>
 </check>
 <check if="have">
  <ask>Provide path to module brief document</ask>
  <action>Load the module brief and use it to pre-populate all planning sections</action>
 </check>
 <check if="skip">
  <action>Proceed directly to Step 1</action>
 </check>
 <template-output>module_brief</template-output>
 </step>
 <step n="1" goal="Define module concept and scope">
 <critical>Load and study the complete module structure guide</critical>
 <action>Load module structure guide: {module_structure_guide}</action>
 <action>Understand module types (Simple/Standard/Complex)</action>
 <action>Review directory structures and component guidelines</action>
 <action>Study the installation infrastructure patterns</action>
 <action>If brainstorming or module brief was completed, reference those results to guide the conversation</action>
 <action>Guide user to articulate their module's vision, exploring its purpose, what it will help with, and who will use it</action>
 <action>Based on their description, intelligently propose module details:</action>
 **Module Identity Development:**
 1. **Module name** - Extract from their description with proper title case
 2. **Module code** - Generate kebab-case from name following patterns:
   - Multi-word descriptive names → shortened kebab-case
   - Domain-specific terms → recognizable abbreviations
   - Present suggested code and confirm it works for paths like .bmad/{{code}}/agents/
 3. **Module purpose** - Refine their description into 1-2 clear sentences
 4. **Target audience** - Infer from context or ask if unclear
 **Module Theme Reference Categories:**
 - Domain-Specific (Legal, Medical, Finance, Education)
 - Creative (RPG/Gaming, Story Writing, Music Production)
 - Technical (DevOps, Testing, Architecture, Security)
 - Business (Project Management, Marketing, Sales)
 - Personal (Journaling, Learning, Productivity)
 <critical>Determine output location:</critical>
 - Module will be created at {installer_output_folder}
 <action>Store module identity for scaffolding</action>
 <template-output>module_identity</template-output>
 </step>
 <step n="2" goal="Plan module components">
 <action>Based on the module purpose, intelligently propose an initial component architecture</action>
 **Agents Planning:**
 <action>Suggest agents based on module purpose, considering agent types (Simple/Expert/Module) appropriate to each role</action>
 **Example Agent Patterns by Domain:**
 - Data/Analytics: Analyst, Designer, Builder roles
 - Gaming/Creative: Game Master, Generator, Storytelling roles
 - Team/Business: Manager, Facilitator, Documentation roles
 <action>Present suggested agent list with types, explaining we can start with core ones and add others later</action>
 <action>Confirm which agents resonate with their vision</action>
 **Workflows Planning:**
 <action>Intelligently suggest workflows that complement the proposed agents</action>
 **Example Workflow Patterns by Domain:**
 - Data/Analytics: analyze-dataset, create-dashboard, generate-report
 - Gaming/Creative: session-prep, generate-encounter, world-building
 - Team/Business: planning, facilitation, documentation workflows
 <action>For each workflow, note whether it should be Document, Action, or Interactive type</action>
 <action>Confirm which workflows are most important to start with</action>
 <action>Determine which to create now vs placeholder</action>
 **Tasks Planning (optional):**
 <ask>Any special tasks that don't warrant full workflows?</ask>
 <action if="tasks needed">For each task, capture name, purpose, and whether standalone or supporting</action>
 <template-output>module_components</template-output>
 </step>
 <step n="2b" goal="Determine module complexity">
 <action>Based on components, intelligently determine module type using criteria:</action>
 **Simple Module Criteria:**
 - 1-2 agents, all Simple type
 - 1-3 workflows
 - No complex integrations
 **Standard Module Criteria:**
 - 2-4 agents with mixed types
 - 3-8 workflows
 - Some shared resources
 **Complex Module Criteria:**
 - 4+ agents or multiple Module-type agents
 - 8+ workflows
 - Complex interdependencies
 - External integrations
 <action>Present determined module type with explanation of what structure will be set up</action>
 <template-output>module_type</template-output>
 </step>
 <step n="3" goal="Create module directory structure">
 <critical>Use module path determined in Step 1:</critical>
 - The module base path is {{module_path}}
 <action>Create base module directories at the determined path:</action>
 ```
 {{module_code}}/
 ├── agents/                    # Agent definitions
 ├── workflows/                 # Workflow folders
 ├── tasks/                     # Task files (if any)
 ├── templates/                 # Shared templates
 ├── data/                      # Module data files
 ├── _module-installer/         # Installation configuration
 │   └── install-config.yaml   # Configuration questions (config.yaml generated at install time)
 └── README.md                  # Module documentation
 ```
 <action>Create installer directory:</action>
 **INSTALLED MODULE STRUCTURE** (generated in target project after installation):
 ```
 {{module_code}}/
 ├── agents/                    # Compiled agents
 ├── workflows/                 # Workflow instances
 ├── config.yaml               # Generated from install-config.yaml during installation
 └── data/                     # User data directory
 ```
 **SOURCE MODULE** (module-installer is for installation only, not copied to target):
 ```
 {{module_code}}/
 ├── _module-installer/
 │   ├── install-config.yaml   # Configuration questions
 │   ├── installer.js          # Optional custom installation logic
 │   └── assets/               # Files to copy during install
 ```
 <template-output>directory_structure</template-output>
 </step>
 <step n="4" goal="Plan module configuration fields">
 <action>Based on the module purpose and components, determine what configuration settings the module needs</action>
 **Configuration Field Planning:**
 <ask>Does your module need any user-configurable settings during installation?</ask>
 **Common configuration patterns:**
 - Output/data paths (where module saves files)
 - Feature toggles (enable/disable functionality)
 - Integration settings (API keys, external services)
 - Behavior preferences (automation level, detail level)
 - User skill level or experience settings
 <action>For each configuration field needed, determine:</action>
 1. Field name (snake_case)
 2. Whether it's INTERACTIVE (asks user) or STATIC (hardcoded)
 3. Prompt text (if interactive)
 4. Default value
 5. Type: text input, single-select, or multi-select
 6. Result template (how the value gets stored)
 <action>Store planned configuration fields for installer generation in step 7</action>
 <template-output>module_config_fields</template-output>
 </step>
 <step n="5" goal="Create first agent" optional="true">
 <ask>Create your first agent now? [yes/no]</ask>
 <check if="yes">
  <action>Invoke agent builder workflow: {agent_builder}</action>
  <action>Pass module_components as context input</action>
  <action>Guide them to create the primary agent for the module</action>
 <critical>Save to module's agents folder:</critical>
 - Save to {{module_path}}/agents/
  </check>
 <check if="no">
  <action>Create placeholder file in agents folder with TODO notes including agent name, purpose, and type</action>
 </check>
 <template-output>first_agent</template-output>
 </step>
 <step n="6" goal="Create first workflow" optional="true">
 <ask>Create your first workflow now? [yes/no]</ask>
 <check if="yes">
  <action>Invoke workflow builder: {workflow_builder}</action>
  <action>Pass module_components as context input</action>
  <action>Guide them to create the primary workflow</action>
 <critical>Save to module's workflows folder:</critical>
 - Save to {{module_path}}/workflows/
  </check>
 <check if="no">
  <action>Create placeholder workflow folder structure with TODO notes for workflow.yaml, instructions.md, and template.md if document workflow</action>
 </check>
 <template-output>first_workflow</template-output>
 </step>
 <step n="7" goal="Setup module installer">
 <action>Load installer template from: {installer_templates}/install-config.yaml</action>
 <critical>IMPORTANT: Create install-config.yaml NOT install-config.yaml</critical>
 <critical>This is the STANDARD format that BMAD installer uses</critical>
 Create module-installer/install-config.yaml:
 ```yaml
 # {{module_name}} Module Configuration
 # This file defines installation questions and module configuration values
 code: {{module_code}}
 name: "{{module_name}}"
 default_selected: false # Set to true if this should be selected by default
 # Welcome message shown during installation
 prompt:
  - "Thank you for choosing {{module_name}}!"
  - "{{brief_module_description}}"
 # Core config values are automatically inherited:
 ## user_name
 ## communication_language
 ## document_output_language
 ## output_folder
 # ============================================================================
 # CONFIGURATION FIELDS (from step 4 planning)
 # ============================================================================
 # Each field can be:
 # 1. INTERACTIVE (has 'prompt' - asks user during installation)
 # 2. STATIC (no 'prompt' - just uses 'result' value)
 # ============================================================================
 # EXAMPLE Interactive text input:
 # output_path:
 #   prompt: "Where should {{module_code}} save outputs?"
 #   default: "output/{{module_code}}"
 #   result: "{project-root}/{value}"
 # EXAMPLE Interactive single-select:
 # detail_level:
 #   prompt: "How detailed should outputs be?"
 #   default: "standard"
 #   result: "{value}"
 #   single-select:
 #     - value: "minimal"
 #       label: "Minimal - Brief summaries only"
 #     - value: "standard"
 #       label: "Standard - Balanced detail"
 #     - value: "detailed"
 #       label: "Detailed - Comprehensive information"
 # EXAMPLE Static value:
 # module_version:
 #   result: "1.0.0"
 # EXAMPLE Static path:
 # data_path:
 #   result: "{project-root}/.bmad/{{module_code}}/data"
 {{generated_config_fields_from_step_4}}
 ```
 <critical>Save location:</critical>
 - Save to {{module_path}}/module-installer/install-config.yaml
 <ask>Does your module need custom installation logic (database setup, API registration, etc.)?</ask>
 <check if="yes, create installer.js">
  ```javascript
  // {{module_name}} Module Installer
  // Custom installation logic
 - @param {Object} options - Installation options
 - @param {string} options.projectRoot - Project root directory
 - @param {Object} options.config - Module configuration from install-config.yaml
 - @param {Array} options.installedIDEs - List of IDE codes being configured
 - @param {Object} options.logger - Logger instance (log, warn, error methods)
 - @returns {boolean} - true if successful, false to abort installation
  async function install(options) {
  const { projectRoot, config, installedIDEs, logger } = options;
  logger.log('Running {{module_name}} custom installer...');
  // TODO: Add custom installation logic here
  // Examples:
  // - Create database tables
  // - Download external assets
  // - Configure API connections
  // - Initialize data files
  // - Set up webhooks or integrations
  logger.log('{{module_name}} custom installation complete!');
  return true;
 }
 module.exports = { install };
 `````
 <critical>Save location:</critical>
 - Save to {{module_path}}/module-installer/installer.js
 </check>
 <check if="no">
 <action>Skip installer.js creation - the standard installer will handle everything</action>
 </check>
 <template-output>installer_config</template-output>
 </step>
 <step n="8" goal="Create module documentation">
 Generate comprehensive README.md:
 ````markdown
 # {{module_name}}
 {{module_purpose}}
 ## Overview
 This module provides:
 {{component_summary}}
 ## Installation
 ```bash
 bmad install {{module_code}}
 `````
 ````
 ## Components
 ### Agents ({{agent_count}})
 {{agent_documentation}}
 ### Workflows ({{workflow_count}})
 {{workflow_documentation}}
 ### Tasks ({{task_count}})
 {{task_documentation}}
 ## Quick Start
 1. **Load the main agent:**
   ```
   agent {{primary_agent}}
   ```
 2. **View available commands:**
   ```
   *help
   ```
 3. **Run the main workflow:**
   ```
   workflow {{primary_workflow}}
   ```
 ## Module Structure
 ```
 {{directory_tree}}
 ```
 ## Configuration
 The module can be configured in `.bmad/{{module_code}}/config.yaml`
 Key settings:
 {{configuration_options}}
 ## Examples
 ### Example 1: {{example_use_case}}
 {{example_walkthrough}}
 ## Development Roadmap
 - [ ] {{roadmap_item_1}}
 - [ ] {{roadmap_item_2}}
 - [ ] {{roadmap_item_3}}
 ## Contributing
 To extend this module:
 1. Add new agents using `create-agent` workflow
 2. Add new workflows using `create-workflow` workflow
 3. Submit improvements via pull request
 ## Author
 Created by {{user_name}} on {{date}}
 ````
 <template-output>module_readme</template-output>
 </step>
 <step n="9" goal="Generate component roadmap">
 Create a development roadmap for remaining components:
 **TODO.md file:**
 ```markdown
 # {{module_name}} Development Roadmap
 ## Phase 1: Core Components
 {{phase1_tasks}}
 ## Phase 2: Enhanced Features
 {{phase2_tasks}}
 ## Phase 3: Polish and Integration
 {{phase3_tasks}}
 ## Quick Commands
 Create new agent:
 ```
 workflow create-agent
 ```
 Create new workflow:
 ```
 workflow create-workflow
 ```
 ## Notes
 {{development_notes}}
 ```
 Ask if user wants to:
 1. Continue building more components now
 2. Save roadmap for later development
 3. Test what's been built so far
 <template-output>development_roadmap</template-output>
 </step>
 <step n="10" goal="Validate and finalize module">
 <action>Run validation checks:</action>
 **Structure validation:**
 - All required directories created
 - Config files properly formatted
 - Installer configuration valid
 **Component validation:**
 - At least one agent or workflow exists (or planned)
 - All references use correct paths
 - Module code consistent throughout
 **Documentation validation:**
 - README.md complete
 - Installation instructions clear
 - Examples provided
 <action>Present summary to {user_name}:</action>
 - Module name and code
 - Location path
 - Agent count (created vs planned)
 - Workflow count (created vs planned)
 - Task count
 - Installer status
 <action>Provide next steps guidance:</action>
 1. Complete remaining components using roadmap
 2. Run the BMAD Method installer to this project location
 3. Select 'Compile Agents' option after confirming folder
 4. Module will be compiled and available for use
 5. Test with bmad install command
 6. Share or integrate with existing system
 <ask>Would you like to:
 - Create another component now?
 - Test the module installation?
 - Exit and continue later?
  </ask>
 <template-output>module_summary</template-output>
 </step>
 </workflow>
--- a/.bmad/bmb/workflows/create-module/module-structure.md
+++ b/.bmad/bmb/workflows/create-module/module-structure.md
@ -1,400 +0,0 @@
 # BMAD Module Structure Guide
 ## What is a Module?
 A BMAD module is a self-contained package of agents, workflows, tasks, and resources that work together to provide specialized functionality. Think of it as an expansion pack for the BMAD Method.
 ## Module Architecture
 ### Core Structure
 ```
 # SOURCE MODULE (in BMAD-METHOD project)
 src/modules/{module-code}/
 ├── agents/                        # Agent definitions (.agent.yaml)
 ├── workflows/                     # Workflow folders
 ├── tasks/                         # Task files
 ├── tools/                         # Tool files
 ├── templates/                     # Shared templates
 ├── data/                          # Static data
 ├── _module-installer/             # Installation configuration
 │   ├── install-config.yaml  # Installation questions & config
 │   ├── installer.js              # Optional custom install logic
 │   └── assets/                   # Files to copy during install
 └── README.md                      # Module documentation
 # INSTALLED MODULE (in target project)
 {project-root}/.bmad/{module-code}/
 ├── agents/                        # Compiled agent files (.md)
 ├── workflows/                     # Workflow instances
 ├── tasks/                         # Task files
 ├── tools/                         # Tool files
 ├── templates/                     # Templates
 ├── data/                          # Module data
 ├── config.yaml                    # Generated from install-config.yaml
 └── README.md                      # Module documentation
 ```
 ## Module Types by Complexity
 ### Simple Module (1-2 agents, 2-3 workflows)
 Perfect for focused, single-purpose tools.
 **Example: Code Review Module**
 - 1 Reviewer Agent
 - 2 Workflows: quick-review, deep-review
 - Clear, narrow scope
 ### Standard Module (3-5 agents, 5-10 workflows)
 Comprehensive solution for a domain.
 **Example: Project Management Module**
 - PM Agent, Scrum Master Agent, Analyst Agent
 - Workflows: sprint-planning, retrospective, roadmap, user-stories
 - Integrated component ecosystem
 ### Complex Module (5+ agents, 10+ workflows)
 Full platform or framework.
 **Example: RPG Toolkit Module**
 - DM Agent, NPC Agent, Monster Agent, Loot Agent, Map Agent
 - 15+ workflows for every aspect of game management
 - Multiple interconnected systems
 ## Module Naming Conventions
 ### Module Code (kebab-case)
 - `data-viz` - Data Visualization
 - `team-collab` - Team Collaboration
 - `rpg-toolkit` - RPG Toolkit
 - `legal-assist` - Legal Assistant
 ### Module Name (Title Case)
 - "Data Visualization Suite"
 - "Team Collaboration Platform"
 - "RPG Game Master Toolkit"
 - "Legal Document Assistant"
 ## Component Guidelines
 ### Agents per Module
 **Recommended Distribution:**
 - **Primary Agent (1)**: The main interface/orchestrator
 - **Specialist Agents (2-4)**: Domain-specific experts
 - **Utility Agents (0-2)**: Helper/support functions
 **Anti-patterns to Avoid:**
 - Too many overlapping agents
 - Agents that could be combined
 - Agents without clear purpose
 ### Workflows per Module
 **Categories:**
 - **Core Workflows (2-3)**: Essential functionality
 - **Feature Workflows (3-5)**: Specific capabilities
 - **Utility Workflows (2-3)**: Supporting operations
 - **Admin Workflows (0-2)**: Maintenance/config
 **Workflow Complexity Guide:**
 - Simple: 3-5 steps, single output
 - Standard: 5-10 steps, multiple outputs
 - Complex: 10+ steps, conditional logic, sub-workflows
 ### Tasks per Module
 Tasks should be used for:
 - Single-operation utilities
 - Shared subroutines
 - Quick actions that don't warrant workflows
 ## Module Dependencies
 ### Internal Dependencies
 - Agents can reference module workflows
 - Workflows can invoke module tasks
 - Tasks can use module templates
 ### External Dependencies
 - Reference other modules via full paths
 - Declare dependencies in config.yaml
 - Version compatibility notes
 ### Workflow Vendoring (Advanced)
 For modules that need workflows from other modules but want to remain standalone, use **workflow vendoring**:
 **In Agent YAML:**
 ```yaml
 menu:
  - trigger: command-name
    workflow: '{project-root}/.bmad/SOURCE_MODULE/workflows/path/workflow.yaml'
    workflow-install: '{project-root}/.bmad/THIS_MODULE/workflows/vendored/workflow.yaml'
    description: 'Command description'
 ```
 **What Happens:**
 - During installation, workflows are copied from `workflow` to `workflow-install` location
 - Vendored workflows get `config_source` updated to reference this module's config
 - Compiled agent only references the `workflow-install` path
 - Module becomes fully standalone - no source module dependency required
 **Use Cases:**
 - Specialized modules that reuse common workflows with different configs
 - Domain-specific adaptations (e.g., game dev using standard dev workflows)
 - Testing workflows in isolation
 **Benefits:**
 - Module independence (no forced dependencies)
 - Clean namespace (workflows in your module)
 - Config isolation (use your module's settings)
 - Customization ready (modify vendored workflows freely)
 ## Installation Infrastructure
 ### Required: module-installer/install-config.yaml
 This file defines both installation questions AND static configuration values:
 ```yaml
 # Module metadata
 code: module-code
 name: 'Module Name'
 default_selected: false
 # Welcome message during installation
 prompt:
  - 'Welcome to Module Name!'
  - 'Brief description here'
 # Core values automatically inherited from installer:
 ## user_name
 ## communication_language
 ## document_output_language
 ## output_folder
 # INTERACTIVE fields (ask user during install)
 output_location:
  prompt: 'Where should module outputs be saved?'
  default: 'output/module-code'
  result: '{project-root}/{value}'
 feature_level:
  prompt: 'Which feature set?'
  default: 'standard'
  result: '{value}'
  single-select:
    - value: 'basic'
      label: 'Basic - Core features only'
    - value: 'standard'
      label: 'Standard - Recommended features'
    - value: 'advanced'
      label: 'Advanced - All features'
 # STATIC fields (no prompt, just hardcoded values)
 module_version:
  result: '1.0.0'
 data_path:
  result: '{project-root}/.bmad/module-code/data'
 ```
 **Key Points:**
 - File is named `install-config.yaml` (NOT install-config.yaml)
 - Supports both interactive prompts and static values
 - `result` field uses placeholders: `{value}`, `{project-root}`, `{directory_name}`
 - Installer generates final `config.yaml` from this template
 ### Optional: module-installer/installer.js
 For complex installations requiring custom logic:
 ```javascript
 /**
 * @param {Object} options - Installation options
 * @param {string} options.projectRoot - Target project directory
 * @param {Object} options.config - Config from install-config.yaml
 * @param {Array} options.installedIDEs - IDEs being configured
 * @param {Object} options.logger - Logger (log, warn, error)
 * @returns {boolean} - true if successful
 */
 async function install(options) {
  // Custom installation logic here
  // - Database setup
  // - API configuration
  // - External downloads
  // - Integration setup
  return true;
 }
 module.exports = { install };
 ```
 ### Optional: module-installer/assets/
 Files to copy during installation:
 - External configurations
 - Documentation
 - Example files
 - Integration scripts
 ## Module Lifecycle
 ### Development Phases
 1. **Planning Phase**
   - Define scope and purpose
   - Identify components
   - Design architecture
 2. **Scaffolding Phase**
   - Create directory structure
   - Generate configurations
   - Setup installer
 3. **Building Phase**
   - Create agents incrementally
   - Build workflows progressively
   - Add tasks as needed
 4. **Testing Phase**
   - Test individual components
   - Verify integration
   - Validate installation
 5. **Deployment Phase**
   - Package module
   - Document usage
   - Distribute/share
 ## Best Practices
 ### Module Cohesion
 - All components should relate to module theme
 - Clear boundaries between modules
 - No feature creep
 ### Progressive Enhancement
 - Start with MVP (1 agent, 2 workflows)
 - Add components based on usage
 - Refactor as patterns emerge
 ### Documentation Standards
 - Every module needs README.md
 - Each agent needs purpose statement
 - Workflows need clear descriptions
 - Include examples and quickstart
 ### Naming Consistency
 - Use module code prefix for uniqueness
 - Consistent naming patterns within module
 - Clear, descriptive names
 ## Example Modules
 ### Example 1: Personal Productivity
 ```
 productivity/
 ├── agents/
 │   ├── task-manager.md      # GTD methodology
 │   └── focus-coach.md        # Pomodoro timer
 ├── workflows/
 │   ├── daily-planning/       # Morning routine
 │   ├── weekly-review/        # Week retrospective
 │   └── project-setup/        # New project init
 └── config.yaml
 ```
 ### Example 2: Content Creation
 ```
 content/
 ├── agents/
 │   ├── writer.md            # Blog/article writer
 │   ├── editor.md            # Copy editor
 │   └── seo-optimizer.md     # SEO specialist
 ├── workflows/
 │   ├── blog-post/           # Full blog creation
 │   ├── social-media/        # Social content
 │   ├── email-campaign/      # Email sequence
 │   └── content-calendar/    # Planning
 └── templates/
    ├── blog-template.md
    └── email-template.md
 ```
 ### Example 3: DevOps Automation
 ```
 devops/
 ├── agents/
 │   ├── deploy-master.md     # Deployment orchestrator
 │   ├── monitor.md           # System monitoring
 │   ├── incident-responder.md # Incident management
 │   └── infra-architect.md   # Infrastructure design
 ├── workflows/
 │   ├── ci-cd-setup/         # Pipeline creation
 │   ├── deploy-app/          # Application deployment
 │   ├── rollback/            # Emergency rollback
 │   ├── health-check/        # System verification
 │   └── incident-response/   # Incident handling
 ├── tasks/
 │   ├── check-status.md      # Quick status check
 │   └── notify-team.md       # Team notifications
 └── data/
    └── runbooks/            # Operational guides
 ```
 ## Module Evolution Pattern
 ```
 Simple Module → Standard Module → Complex Module → Module Suite
     (MVP)          (Enhanced)        (Complete)      (Ecosystem)
 ```
 ## Common Pitfalls
 1. **Over-engineering**: Starting too complex
 2. **Under-planning**: No clear architecture
 3. **Poor boundaries**: Module does too much
 4. **Weak integration**: Components don't work together
 5. **Missing docs**: No clear usage guide
 ## Success Metrics
 A well-designed module has:
 - ✅ Clear, focused purpose
 - ✅ Cohesive components
 - ✅ Smooth installation
 - ✅ Comprehensive docs
 - ✅ Room for growth
 - ✅ Happy users!
--- a/.bmad/bmb/workflows/create-module/workflow.yaml
+++ b/.bmad/bmb/workflows/create-module/workflow.yaml
@ -1,42 +0,0 @@
 # Build Module Workflow Configuration
 name: create-module
 description: "Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure"
 author: "BMad"
 # Critical variables load from config_source
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 custom_module_location: "{config_source}:custom_module_location"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 # Reference guides for module building
 module_structure_guide: "{installed_path}/module-structure.md"
 installer_templates: "{installed_path}/installer-templates/"
 # Use existing build workflows
 agent_builder: "{project-root}/.bmad/bmb/workflows/create-agent/workflow.yaml"
 workflow_builder: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow.yaml"
 brainstorming_workflow: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml"
 brainstorming_context: "{installed_path}/brainstorm-context.md"
 # Optional docs that help understand module patterns
 recommended_inputs:
  - module_brief: "{output_folder}/module-brief-*.md"
  - brainstorming_results: "{output_folder}/brainstorming-*.md"
  - bmm_module: "{project-root}/.bmad/bmm/"
  - cis_module: "{project-root}/.bmad/cis/"
  - existing_agents: "{project-root}/.bmad/*/agents/"
  - existing_workflows: "{project-root}/.bmad/*/workflows/"
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/create-module"
 template: false # This is an interactive scaffolding workflow
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Output configuration - creates entire module structure
 # Save to custom_module_location/{{module_code}}
 installer_output_folder: "{custom_module_location}/{{module_code}}"
 standalone: true
 # Web bundle configuration
--- a/.bmad/bmb/workflows/create-workflow/README.md
+++ b/.bmad/bmb/workflows/create-workflow/README.md
@ -1,277 +0,0 @@
 # Build Workflow
 ## Overview
 The Build Workflow is an interactive workflow builder that guides you through creating new BMAD workflows with proper structure, conventions, and validation. It ensures all workflows follow best practices for optimal human-AI collaboration and are fully compliant with the BMAD Core v6 workflow execution engine.
 ## Key Features
 - **Optional Brainstorming Phase**: Creative exploration of workflow ideas before structured development
 - **Comprehensive Guidance**: Step-by-step process with detailed instructions and examples
 - **Template-Based**: Uses proven templates for all workflow components
 - **Convention Enforcement**: Ensures adherence to BMAD workflow creation guide
 - **README Generation**: Automatically creates comprehensive documentation
 - **Validation Built-In**: Includes checklist generation for quality assurance
 - **Type-Aware**: Adapts to document, action, interactive, autonomous, or meta-workflow types
 ## Usage
 ### Basic Invocation
 ```bash
 workflow create-workflow
 ```
 ### Through BMad Builder Agent
 ```
 *create-workflow
 ```
 ### What You'll Be Asked
 1. **Optional**: Whether to brainstorm workflow ideas first (creative exploration phase)
 2. Workflow name and target module
 3. Workflow purpose and type (enhanced by brainstorming insights if used)
 4. Metadata (description, author, outputs)
 5. Step-by-step design (goals, variables, flow)
 6. Whether to include optional components
 ## Workflow Structure
 ### Files Included
 ```
 create-workflow/
 ├── workflow.yaml                  # Configuration and metadata
 ├── instructions.md                # Step-by-step execution guide
 ├── checklist.md                   # Validation criteria
 ├── workflow-creation-guide.md     # Comprehensive reference guide
 ├── README.md                      # This file
 └── workflow-template/             # Templates for new workflows
    ├── workflow.yaml
    ├── instructions.md
    ├── template.md
    ├── checklist.md
    └── README.md
 ```
 ## Understanding Instruction Styles
 One of the most important decisions when creating a workflow is choosing the **instruction style** - how the workflow guides the AI's interaction with users.
 ### Intent-Based vs Prescriptive Instructions
 **Intent-Based (Recommended for most workflows)**
 Guides the LLM with goals and principles, allowing natural conversation adaptation.
 - **More flexible and conversational** - AI adapts questions to context
 - **Better for complex discovery** - Requirements gathering, creative exploration
 - **Quality over consistency** - Focus on deep understanding
 - **Example**: `<action>Guide user to define their target audience with specific demographics and needs</action>`
 **Best for:**
 - Complex discovery processes (user research, requirements)
 - Creative brainstorming and ideation
 - Iterative refinement workflows
 - When adaptation to context matters
 - Workflows requiring nuanced understanding
 **Prescriptive**
 Provides exact wording for questions and structured options.
 - **More controlled and predictable** - Same questions every time
 - **Better for simple data collection** - Platform choices, yes/no decisions
 - **Consistency over quality** - Standardized execution
 - **Example**: `<ask>What is your target platform? Choose: PC, Console, Mobile, Web</ask>`
 **Best for:**
 - Simple data collection (platform, format, binary choices)
 - Compliance verification and standards
 - Configuration with finite options
 - Quick setup wizards
 - When consistency is critical
 ### Best Practice: Mix Both Styles
 The most effective workflows use **both styles strategically**:
 ```xml
 <!-- Intent-based workflow with prescriptive moments -->
 <step n="1" goal="Understand user vision">
  <action>Explore the user's vision, uncovering creative intent and target experience</action>
 </step>
 <step n="2" goal="Capture basic metadata">
  <ask>What is your target platform? Choose: PC, Console, Mobile, Web</ask>
 </step>
 <step n="3" goal="Deep dive into details">
  <action>Guide user to articulate their core approach and unique aspects</action>
 </step>
 ```
 **During workflow creation**, you'll be asked to choose a **primary style preference** - this sets the default approach, but you can (and should) use the other style when it makes more sense for specific steps.
 ## Workflow Process
 ### Phase 0: Optional Brainstorming (Step -1)
 - **Creative Exploration**: Option to brainstorm workflow ideas before structured development
 - **Design Concept Development**: Generate multiple approaches and explore different possibilities
 - **Requirement Clarification**: Use brainstorming output to inform workflow purpose, type, and structure
 - **Enhanced Creativity**: Leverage AI brainstorming tools for innovative workflow design
 The brainstorming phase invokes the CIS brainstorming workflow to:
 - Explore workflow ideas and approaches
 - Clarify requirements and use cases
 - Generate creative solutions for complex automation needs
 - Inform the structured workflow building process
 ### Phase 1: Planning (Steps 0-3)
 - Load workflow creation guide and conventions
 - Define workflow purpose, name, and type (informed by brainstorming if used)
 - Gather metadata and configuration details
 - Design step structure and flow
 ### Phase 2: Generation (Steps 4-8)
 - Create workflow.yaml with proper configuration
 - Generate instructions.md with XML-structured steps
 - Create template.md (for document workflows)
 - Generate validation checklist
 - Create supporting data files (optional)
 ### Phase 3: Documentation and Validation (Steps 9-11)
 - Create comprehensive README.md (MANDATORY)
 - Test and validate workflow structure
 - Provide usage instructions and next steps
 ## Output
 ### Generated Workflow Folder
 Creates a complete workflow folder at:
 `{project-root}/.bmad/{{target_module}}/workflows/{{workflow_name}}/`
 ### Files Created
 **Always Created:**
 - `workflow.yaml` - Configuration with paths and variables
 - `README.md` - Comprehensive documentation (MANDATORY as of v6)
 - `instructions.md` - Execution steps (if not template-only workflow)
 **Conditionally Created:**
 - `template.md` - Document structure (for document workflows)
 - `checklist.md` - Validation criteria (optional but recommended)
 - Supporting data files (CSV, JSON, etc. as needed)
 ### Output Structure
 For document workflows, the README documents:
 - Workflow purpose and use cases
 - Usage examples with actual commands
 - Input expectations
 - Output structure and location
 - Best practices
 ## Requirements
 - Access to workflow creation guide
 - BMAD Core v6 project structure
 - Module to host the new workflow (bmm, bmb, cis, or custom)
 ## Best Practices
 ### Before Starting
 1. **Consider Brainstorming**: If you're unsure about the workflow approach, use the optional brainstorming phase
 2. Review the workflow creation guide to understand conventions
 3. Have a clear understanding of the workflow's purpose (or be ready to explore it creatively)
 4. Know which type of workflow you're creating (document, action, etc.) or be open to discovery
 5. Identify any data files or references needed
 ### Creative Workflow Design
 The create-workflow now supports a **seamless transition from creative ideation to structured implementation**:
 - **"I need a workflow for something..."** → Start with brainstorming to explore possibilities
 - **Brainstorm** → Generate multiple approaches and clarify requirements
 - **Structured workflow** → Build the actual workflow using insights from brainstorming
 - **One seamless session** → Complete the entire process from idea to implementation
 ### During Execution
 1. Follow kebab-case naming conventions
 2. Be specific with step goals and instructions
 3. Use descriptive variable names (snake_case)
 4. Set appropriate limits ("3-5 items maximum")
 5. Include examples where helpful
 ### After Completion
 1. Test the newly created workflow
 2. Validate against the checklist
 3. Ensure README is comprehensive and accurate
 4. Test all file paths and variable references
 ## Troubleshooting
 ### Issue: Generated workflow won't execute
 - **Solution**: Verify all file paths in workflow.yaml use proper variable substitution
 - **Check**: Ensure installed_path and project-root are correctly set
 ### Issue: Variables not replacing in template
 - **Solution**: Ensure variable names match exactly between instructions `<template-output>` tags and template `{{variables}}`
 - **Check**: Use snake_case consistently
 ### Issue: README has placeholder text
 - **Solution**: This workflow now enforces README generation - ensure Step 10 completed fully
 - **Check**: No {WORKFLOW_TITLE} or similar placeholders should remain
 ## Customization
 To modify this workflow:
 1. Edit `instructions.md` to adjust the creation process
 2. Update templates in `workflow-template/` to change generated files
 3. Modify `workflow-creation-guide.md` to update conventions
 4. Edit `checklist.md` to change validation criteria
 ## Version History
 - **v6.0.0** - README.md now MANDATORY for all workflows
  - Added comprehensive README template
  - Enhanced validation for documentation
  - Improved Step 10 with detailed README requirements
 - **v6.0.0** - Initial BMAD Core v6 compatible version
  - Template-based workflow generation
  - Convention enforcement
  - Validation checklist support
 ## Support
 For issues or questions:
 - Review `/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
 - Check existing workflows in `/.bmad/bmm/workflows/` for examples
 - Validate against `/.bmad/bmb/workflows/create-workflow/checklist.md`
 - Consult BMAD Method v6 documentation
 ---
 _Part of the BMad Method v6 - BMB (BMad Builder) Module_
--- a/.bmad/bmb/workflows/create-workflow/brainstorm-context.md
+++ b/.bmad/bmb/workflows/create-workflow/brainstorm-context.md
@ -1,197 +0,0 @@
 # Workflow Brainstorming Context
 _Context provided to brainstorming workflow when creating a new BMAD workflow_
 ## Session Focus
 You are brainstorming ideas for a **BMAD workflow** - a guided, multi-step process that helps users accomplish complex tasks with structure, consistency, and quality.
 ## What is a BMAD Workflow?
 A workflow is a structured process that provides:
 - **Clear Steps**: Sequential operations with defined goals
 - **User Guidance**: Prompts, questions, and decisions at each phase
 - **Quality Output**: Documents, artifacts, or completed actions
 - **Repeatability**: Same process yields consistent results
 - **Type**: Document (creates docs), Action (performs tasks), Interactive (guides sessions), Autonomous (runs automated), Meta (orchestrates other workflows)
 ## Brainstorming Goals
 Explore and define:
 ### 1. Problem and Purpose
 - **What task needs structure?** (specific process users struggle with)
 - **Why is this hard manually?** (complexity, inconsistency, missing steps)
 - **What would ideal process look like?** (steps, checkpoints, outputs)
 - **Who needs this?** (target users and their pain points)
 ### 2. Process Flow
 - **How many phases?** (typically 3-10 major steps)
 - **What's the sequence?** (logical flow from start to finish)
 - **What decisions are needed?** (user choices that affect path)
 - **What's optional vs required?** (flexibility points)
 - **What checkpoints matter?** (validation, review, approval points)
 ### 3. Inputs and Outputs
 - **What inputs are needed?** (documents, data, user answers)
 - **What outputs are generated?** (documents, code, configurations)
 - **What format?** (markdown, XML, YAML, actions)
 - **What quality criteria?** (how to validate success)
 ### 4. Workflow Type and Style
 - **Document Workflow?** Creates structured documents (PRDs, specs, reports)
 - **Action Workflow?** Performs operations (refactoring, deployment, analysis)
 - **Interactive Workflow?** Guides creative process (brainstorming, planning)
 - **Autonomous Workflow?** Runs without user input (batch processing, generation)
 - **Meta Workflow?** Orchestrates other workflows (project setup, module creation)
 ## Creative Constraints
 A great BMAD workflow should be:
 - **Focused**: Solves one problem well (not everything)
 - **Structured**: Clear phases with defined goals
 - **Flexible**: Optional steps, branching paths where appropriate
 - **Validated**: Checklist to verify completeness and quality
 - **Documented**: README explains when and how to use it
 ## Workflow Architecture Questions
 ### Core Structure
 1. **Workflow name** (kebab-case, e.g., "product-brief")
 2. **Purpose** (one sentence)
 3. **Type** (document/action/interactive/autonomous/meta)
 4. **Major phases** (3-10 high-level steps)
 5. **Output** (what gets created)
 ### Process Details
 1. **Required inputs** (what user must provide)
 2. **Optional inputs** (what enhances results)
 3. **Decision points** (where user chooses path)
 4. **Checkpoints** (where to pause for approval)
 5. **Variables** (data passed between steps)
 ### Quality and Validation
 1. **Success criteria** (what defines "done")
 2. **Validation checklist** (measurable quality checks)
 3. **Common issues** (troubleshooting guidance)
 4. **Best practices** (tips for optimal results)
 ## Workflow Pattern Examples
 ### Document Generation Workflows
 - **Product Brief**: Idea → Vision → Features → Market → Output
 - **PRD**: Requirements → User Stories → Acceptance Criteria → Document
 - **Architecture**: Requirements → Decisions → Design → Diagrams → ADRs
 - **Technical Spec**: Epic → Implementation → Testing → Deployment → Doc
 ### Action Workflows
 - **Code Refactoring**: Analyze → Plan → Refactor → Test → Commit
 - **Deployment**: Build → Test → Stage → Validate → Deploy → Monitor
 - **Migration**: Assess → Plan → Convert → Validate → Deploy
 - **Analysis**: Collect → Process → Analyze → Report → Recommend
 ### Interactive Workflows
 - **Brainstorming**: Setup → Generate → Expand → Evaluate → Prioritize
 - **Planning**: Context → Goals → Options → Decisions → Plan
 - **Review**: Load → Analyze → Critique → Suggest → Document
 ### Meta Workflows
 - **Project Setup**: Plan → Architecture → Stories → Setup → Initialize
 - **Module Creation**: Brainstorm → Brief → Agents → Workflows → Install
 - **Sprint Planning**: Backlog → Capacity → Stories → Commit → Kickoff
 ## Workflow Design Patterns
 ### Linear Flow
 Simple sequence: Step 1 → Step 2 → Step 3 → Done
 **Good for:**
 - Document generation
 - Structured analysis
 - Sequential builds
 ### Branching Flow
 Conditional paths: Step 1 → [Decision] → Path A or Path B → Merge → Done
 **Good for:**
 - Different project types
 - Optional deep dives
 - Scale-adaptive processes
 ### Iterative Flow
 Refinement loops: Step 1 → Step 2 → [Review] → (Repeat if needed) → Done
 **Good for:**
 - Creative processes
 - Quality refinement
 - Approval cycles
 ### Router Flow
 Type selection: [Select Type] → Load appropriate instructions → Execute → Done
 **Good for:**
 - Multi-mode workflows
 - Reusable frameworks
 - Flexible tools
 ## Suggested Brainstorming Techniques
 Particularly effective for workflow ideation:
 1. **Process Mapping**: Draw current painful process, identify improvements
 2. **Step Decomposition**: Break complex task into atomic steps
 3. **Checkpoint Thinking**: Where do users need pause/review/decision?
 4. **Pain Point Analysis**: What makes current process frustrating?
 5. **Success Visualization**: What does perfect execution look like?
 ## Key Questions to Answer
 1. What manual process needs structure and guidance?
 2. What makes this process hard or inconsistent today?
 3. What are the 3-10 major phases/steps?
 4. What document or output gets created?
 5. What inputs are required from the user?
 6. What decisions or choices affect the flow?
 7. What quality criteria define success?
 8. Document, Action, Interactive, Autonomous, or Meta workflow?
 9. What makes this workflow valuable vs doing it manually?
 10. What would make this workflow delightful to use?
 ## Output Goals
 Generate:
 - **Workflow name**: Clear, describes the process
 - **Purpose statement**: One sentence explaining value
 - **Workflow type**: Classification with rationale
 - **Phase outline**: 3-10 major steps with goals
 - **Input/output description**: What goes in, what comes out
 - **Key decisions**: Where user makes choices
 - **Success criteria**: How to know it worked
 - **Unique value**: Why this workflow beats manual process
 - **Use cases**: 3-5 scenarios where this workflow shines
 ---
 _This focused context helps create valuable, structured BMAD workflows_
--- a/.bmad/bmb/workflows/create-workflow/checklist.md
+++ b/.bmad/bmb/workflows/create-workflow/checklist.md
@ -1,94 +0,0 @@
 # Build Workflow - Validation Checklist
 ## Workflow Configuration (workflow.yaml)
 - [ ] Name follows kebab-case convention
 - [ ] Description clearly states workflow purpose
 - [ ] All paths use proper variable substitution
 - [ ] installed_path points to correct module location
 - [ ] template/instructions paths are correct for workflow type
 - [ ] Output file pattern is appropriate
 - [ ] YAML syntax is valid (no parsing errors)
 ## Instructions Structure (instructions.md)
 - [ ] Critical headers reference workflow engine
 - [ ] All steps have sequential numbering
 - [ ] Each step has a clear goal attribute
 - [ ] Optional steps marked with optional="true"
 - [ ] Repeating steps have appropriate repeat attributes
 - [ ] All template-output tags have unique variable names
 - [ ] Flow control (if any) has valid step references
 ## Template Structure (if document workflow)
 - [ ] All sections have appropriate placeholders
 - [ ] Variable names match template-output tags exactly
 - [ ] Markdown formatting is valid
 - [ ] Date and metadata fields included
 - [ ] No unreferenced variables remain
 ## Content Quality
 - [ ] Instructions are specific and actionable
 - [ ] Examples provided where helpful
 - [ ] Limits set for lists and content length
 - [ ] User prompts are clear
 - [ ] Step goals accurately describe outcomes
 ## Validation Checklist (if present)
 - [ ] Criteria are measurable and specific
 - [ ] Checks grouped logically by category
 - [ ] Final validation summary included
 - [ ] All critical requirements covered
 ## File System
 - [ ] Workflow folder created in correct module
 - [ ] All required files present based on workflow type
 - [ ] File permissions allow execution
 - [ ] No placeholder text remains (like {TITLE})
 ## Testing Readiness
 - [ ] Workflow can be invoked without errors
 - [ ] All required inputs are documented
 - [ ] Output location is writable
 - [ ] Dependencies (if any) are available
 ## Web Bundle Configuration (if applicable)
 - [ ] web_bundle section present if needed
 - [ ] Name, description, author copied from main config
 - [ ] All file paths converted to .bmad/-relative format
 - [ ] NO {config_source} variables in web bundle
 - [ ] NO {project-root} prefixes in paths
 - [ ] Instructions path listed correctly
 - [ ] Validation/checklist path listed correctly
 - [ ] Template path listed (if document workflow)
 - [ ] All data files referenced in instructions are listed
 - [ ] All sub-workflows are included
 - [ ] web_bundle_files array is complete:
  - [ ] Instructions.md included
  - [ ] Checklist.md included
  - [ ] Template.md included (if applicable)
  - [ ] All CSV/JSON data files included
  - [ ] All referenced templates included
  - [ ] All sub-workflow files included
 - [ ] No external dependencies outside bundle
 ## Documentation
 - [ ] README created (if requested)
 - [ ] Usage instructions clear
 - [ ] Example command provided
 - [ ] Special requirements noted
 - [ ] Web bundle deployment noted (if applicable)
 ## Final Validation
 - [ ] Configuration: No issues
 - [ ] Instructions: Complete and clear
 - [ ] Template: Variables properly mapped
 - [ ] Testing: Ready for test run
--- a/.bmad/bmb/workflows/create-workflow/instructions.md
+++ b/.bmad/bmb/workflows/create-workflow/instructions.md
@ -1,724 +0,0 @@
 # Build Workflow - Workflow Builder 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/bmb/workflows/create-workflow/workflow.yaml</critical>
 <critical>You MUST fully understand the workflow creation guide at: {workflow_creation_guide}</critical>
 <critical>Study the guide thoroughly to follow ALL conventions for optimal human-AI collaboration</critical>
 <critical>Communicate in {communication_language} throughout the workflow creation process</critical>
 <workflow>
 <step n="-1" goal="Optional brainstorming phase" optional="true">
 <ask>Do you want to brainstorm workflow ideas first? [y/n]</ask>
 <action if="user_response == 'y' or user_response == 'yes'">
 Invoke brainstorming workflow to explore ideas and design concepts:
 - Workflow: {project-root}/.bmad/core/workflows/brainstorming/workflow.yaml
 - Context data: {installed_path}/brainstorm-context.md
 - Purpose: Generate creative workflow ideas, explore different approaches, and clarify requirements
 The brainstorming output will inform:
 - Workflow purpose and goals
 - Workflow type selection
 - Step design and structure
 - User experience considerations
 - Technical requirements
  </action>
 <action if="user_response == 'n' or user_response == 'no'">
 Skip brainstorming and proceed directly to workflow building process.
 </action>
 </step>
 <step n="0" goal="Load and understand workflow conventions">
 <action>Load the complete workflow creation guide from: {workflow_creation_guide}</action>
 <action>Study all sections thoroughly including:
  - Core concepts (tasks vs workflows, workflow types)
  - Workflow structure (required/optional files, patterns)
  - Writing instructions (step attributes, XML tags, flow control)
  - Templates and variables (syntax, naming, sources)
  - Validation best practices
  - Common pitfalls to avoid
 </action>
 <action>Load template files from: {workflow_template_path}/</action>
 <critical>You must follow ALL conventions from the guide to ensure optimal human-AI collaboration</critical>
 </step>
 <step n="1" goal="Define workflow purpose and type">
 Ask the user:
 - What is the workflow name? (kebab-case, e.g., "product-brief")
 - What module will it belong to? (e.g., "bmm", "bmb", "cis")
  - Store as {{target_module}} for output path determination
 - What is the workflow's main purpose?
 - What type of workflow is this?
  - Document workflow (generates documents like PRDs, specs)
  - Action workflow (performs actions like refactoring)
  - Interactive workflow (guided sessions)
  - Autonomous workflow (runs without user input)
  - Meta-workflow (coordinates other workflows)
 Based on type, determine which files are needed:
 - Document: workflow.yaml + template.md + instructions.md + checklist.md
 - Action: workflow.yaml + instructions.md
 - Others: Varies based on requirements
 <critical>Determine output location based on module assignment:</critical>
 - If workflow belongs to module: Save to {module_output_folder}
 - If standalone workflow: Save to {standalone_output_folder}
 Store decisions for later use.
 </step>
 <step n="2" goal="Gather workflow metadata and invocation settings">
 Collect essential configuration details:
 - Description (clear purpose statement)
 - Author name (default to user_name or "BMad")
 - Output file naming pattern
 - Any required input documents
 - Any required tools or dependencies
 <action>Determine standalone property - this controls how the workflow can be invoked:
 Explain to the user:
 **Standalone Property** controls whether the workflow can be invoked directly or only called by other workflows/agents.
 **standalone: true (DEFAULT - Recommended for most workflows)**:
 - Users can invoke directly via IDE commands or `/workflow-name`
 - Shows up in IDE command palette
 - Can also be called from agent menus or other workflows
 - Use for: User-facing workflows, entry-point workflows, any workflow users run directly
 **standalone: false (Use for helper/internal workflows)**:
 - Cannot be invoked directly by users
 - Only called via `<invoke-workflow>` from other workflows or agent menus
 - Doesn't appear in IDE command palette
 - Use for: Internal utilities, sub-workflows, helpers that don't make sense standalone
 Most workflows should be `standalone: true` to give users direct access.
 </action>
 <ask>Should this workflow be directly invokable by users?
 1. **Yes (Recommended)** - Users can run it directly (standalone: true)
 2. **No** - Only called by other workflows/agents (standalone: false)
 Most workflows choose option 1:
 </ask>
 <action>Store {{standalone_setting}} as true or false based on response</action>
 Create the workflow name in kebab-case and verify it doesn't conflict with existing workflows.
 </step>
 <step n="3" goal="Understand workflow interaction style and design steps">
 <critical>Instruction style and interactivity level fundamentally shape the user experience - choose thoughtfully</critical>
 <action>Reference the comprehensive "Instruction Styles: Intent-Based vs Prescriptive" section from the loaded creation guide</action>
 <action>Discuss instruction style collaboratively with the user:
 Explain that there are two primary approaches:
 **Intent-Based (RECOMMENDED as default)**:
 - Gives AI goals and principles, lets it adapt conversation naturally
 - More flexible, conversational, responsive to user context
 - Better for: discovery, complex decisions, teaching, varied user skill levels
 - Uses <action> tags with guiding instructions
 - Example from architecture workflow: Facilitates decisions adapting to user_skill_level
 **Prescriptive**:
 - Provides exact questions and specific options
 - More controlled, predictable, consistent across runs
 - Better for: simple data collection, finite options, compliance, quick setup
 - Uses <ask> tags with specific question text
 - Example: Platform selection with 5 defined choices
 Explain that **most workflows should default to intent-based** but use prescriptive for simple data points.
 The architecture workflow is an excellent example of intent-based with prescriptive moments.
 </action>
 <ask>For this workflow's PRIMARY style:
 1. **Intent-based (Recommended)** - Adaptive, conversational, responds to user context
 2. **Prescriptive** - Structured, consistent, controlled interactions
 3. **Mixed/Balanced** - I'll help you decide step-by-step
 What feels right for your workflow's purpose?
 </ask>
 <action>Store {{instruction_style}} preference</action>
 <action>Now discuss interactivity level:
 Beyond style, consider **how interactive** this workflow should be:
 **High Interactivity (Collaborative)**:
 - Constant back-and-forth with user
 - User guides direction, AI facilitates
 - Iterative refinement and review
 - Best for: creative work, complex decisions, learning experiences
 - Example: Architecture workflow's collaborative decision-making
 **Medium Interactivity (Guided)**:
 - Key decision points have interaction
 - AI proposes, user confirms or refines
 - Validation checkpoints
 - Best for: most document workflows, structured processes
 - Example: PRD workflow with sections to review
 **Low Interactivity (Autonomous)**:
 - Minimal user input required
 - AI works independently with guidelines
 - User reviews final output
 - Best for: automated generation, batch processing
 - Example: Generating user stories from epics
  </action>
 <ask>What interactivity level suits this workflow?
 1. **High** - Highly collaborative, user actively involved throughout (Recommended)
 2. **Medium** - Guided with key decision points
 3. **Low** - Mostly autonomous with final review
 Select the level that matches your workflow's purpose:
 </ask>
 <action>Store {{interactivity_level}} preference</action>
 <action>Explain how these choices will inform the workflow design:
 - Intent-based + High interactivity: Conversational discovery with open questions
 - Intent-based + Medium: Facilitated guidance with confirmation points
 - Intent-based + Low: Principle-based autonomous generation
 - Prescriptive + any level: Structured questions, but frequency varies
 - Mixed: Strategic use of both styles where each works best
  </action>
 <action>Now work with user to outline workflow steps:
 - How many major steps? (Recommend 3-7 for most workflows)
 - What is the goal of each step?
 - Which steps are optional?
 - Which steps need heavy user collaboration vs autonomous execution?
 - Which steps should repeat?
 - What variables/outputs does each step produce?
 Consider their instruction_style and interactivity_level choices when designing step flow:
 - High interactivity: More granular steps with collaboration
 - Low interactivity: Larger autonomous steps with review
 - Intent-based: Focus on goals and principles in step descriptions
 - Prescriptive: Define specific questions and options
  </action>
 <action>Create a step outline that matches the chosen style and interactivity level</action>
 <action>Note which steps should be intent-based vs prescriptive (if mixed approach)</action>
 <template-output>step_outline</template-output>
 </step>
 <step n="4" goal="Create workflow.yaml">
 Load and use the template at: {template_workflow_yaml}
 Replace all placeholders following the workflow creation guide conventions:
 - {TITLE} → Proper case workflow name
 - {WORKFLOW_CODE} → kebab-case name
 - {WORKFLOW_DESCRIPTION} → Clear description
 - {module-code} → Target module
 - {file.md} → Output filename pattern
 Include:
 - All metadata from steps 1-2
 - **Standalone property**: Use {{standalone_setting}} from step 2 (true or false)
 - Proper paths for installed_path using variable substitution
 - Template/instructions/validation paths based on workflow type:
  - Document workflow: all files (template, instructions, validation)
  - Action workflow: instructions only (template: false)
  - Autonomous: set autonomous: true flag
 - Required tools if any
 - Recommended inputs if any
 <critical>ALWAYS include the standard config block:</critical>
 ```yaml
 # Critical variables from config
 config_source: '{project-root}/.bmad/{{target_module}}/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
 date: system-generated
 ```
 <critical>This standard config ensures workflows can run autonomously and communicate properly with users</critical>
 <critical>ALWAYS include the standalone property:</critical>
 ```yaml
 standalone: { { standalone_setting } } # true or false from step 2
 ```
 **Example complete workflow.yaml structure**:
 ```yaml
 name: 'workflow-name'
 description: 'Clear purpose statement'
 # Paths
 installed_path: '{project-root}/.bmad/module/workflows/name'
 template: '{installed_path}/template.md'
 instructions: '{installed_path}/instructions.md'
 validation: '{installed_path}/checklist.md'
 # Critical variables from config
 config_source: '{project-root}/.bmad/module/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
 date: system-generated
 # Output
 default_output_file: '{output_folder}/document.md'
 # Invocation control
 standalone: true # or false based on step 2 decision
 ```
 Follow path conventions from guide:
 - Use {project-root} for absolute paths
 - Use {installed_path} for workflow components
 - Use {config_source} for config references
 <critical>Determine save location:</critical>
 - Use the output folder determined in Step 1 (module or standalone)
 - Write to {{output_folder}}/workflow.yaml
  </step>
 <step n="5" goal="Create instructions.md" if="workflow_type != 'template-only'">
 Load and use the template at: {template_instructions}
 Generate the instructions.md file following the workflow creation guide:
 1. ALWAYS include critical headers:
   - Workflow engine reference: {project-root}/.bmad/core/tasks/workflow.xml
   - workflow.yaml reference: must be loaded and processed
 2. Structure with <workflow> tags containing all steps
 3. For each step from design phase, follow guide conventions:
   - Step attributes: n="X" goal="clear goal statement"
   - Optional steps: optional="true"
   - Repeating: repeat="3" or repeat="for-each-X" or repeat="until-approved"
   - Conditional: if="condition"
   - Sub-steps: Use 3a, 3b notation
 4. Use proper XML tags from guide:
   - Execution: <action>, <check>, <ask>, <goto>, <invoke-workflow>
   - Output: <template-output>, <invoke-task halt="true">{project-root}/.bmad/core/tasks/advanced-elicitation.xml</invoke-task>, <critical>, <example>
   - Flow: <loop>, <break>, <continue>
 5. Best practices from guide:
   - Keep steps focused (single goal)
   - Be specific ("Write 1-2 paragraphs" not "Write about")
   - Provide examples where helpful
   - Set limits ("3-5 items maximum")
   - Save checkpoints with <template-output>
 <critical>Standard config variable usage:</critical>
 Instructions MUST use the standard config variables where appropriate:
 - Communicate in {communication_language} throughout the workflow
 - Address user as {user_name} in greetings and summaries
 - Write all output files to {output_folder} or subdirectories
 - Include {date} in generated document headers
 Example usage in instructions:
 ```xml
 <action>Write document to {output_folder}/output-file.md</action>
 <critical>Communicate all responses in {communication_language}</critical>
 <output>Hello {user_name}, the workflow is complete!</output>
 ```
 <critical>Applying instruction style preference:</critical>
 Based on the {{instruction_style}} preference from Step 3, generate instructions using these patterns:
 **Intent-Based Instructions (Recommended for most workflows):**
 Focus on goals, principles, and desired outcomes. Let the LLM adapt the conversation naturally.
 ✅ **Good Examples:**
 ```xml
 <!-- Discovery and exploration -->
 <action>Guide user to define their target audience with specific demographics, psychographics, and behavioral characteristics</action>
 <action>Explore the user's vision for the product, asking probing questions to uncover core motivations and success criteria</action>
 <action>Help user identify and prioritize key features based on user value and technical feasibility</action>
 <!-- Validation and refinement -->
 <action>Validate that the technical approach aligns with project constraints and team capabilities</action>
 <action>Challenge assumptions about user needs and market fit with thought-provoking questions</action>
 <!-- Complex iterative work -->
 <action>Collaborate with user to refine the architecture, iterating until they're satisfied with the design</action>
 ```
 ❌ **Avoid (too prescriptive):**
 ```xml
 <ask>What is your target audience age range? Choose: 18-24, 25-34, 35-44, 45+</ask>
 <ask>List exactly 3 key features in priority order</ask>
 ```
 **When to use Intent-Based:**
 - Complex discovery processes (user research, requirements gathering)
 - Creative brainstorming and ideation
 - Iterative refinement workflows
 - When user input quality matters more than consistency
 - Workflows requiring adaptation to context
 **Prescriptive Instructions (Use selectively):**
 Provide exact wording, specific options, and controlled interactions.
 ✅ **Good Examples:**
 ```xml
 <!-- Simple data collection -->
 <ask>What is your target platform? Choose: PC, Console, Mobile, Web</ask>
 <ask>Select monetization model: Premium, Free-to-Play, Subscription, Ad-Supported</ask>
 <!-- Compliance and standards -->
 <ask>Does this comply with GDPR requirements? [yes/no]</ask>
 <ask>Choose documentation standard: JSDoc, TypeDoc, TSDoc</ask>
 <!-- Binary decisions -->
 <ask>Do you want to generate test cases? [yes/no]</ask>
 <ask>Include performance benchmarks? [yes/no]</ask>
 ```
 ❌ **Avoid (too rigid for complex tasks):**
 ```xml
 <ask>What are your product goals? List exactly 5 goals, each 10-15 words</ask>
 <ask>Describe your user persona in exactly 3 sentences</ask>
 ```
 **When to use Prescriptive:**
 - Simple data collection (platform, format, yes/no choices)
 - Compliance verification and standards adherence
 - Configuration with finite options
 - When consistency is critical across all executions
 - Quick setup wizards
 **Mixing Both Styles (Best Practice):**
 Even if user chose a primary style, use the other when appropriate:
 ```xml
 <!-- Intent-based workflow with prescriptive moments -->
 <step n="1" goal="Understand user vision">
  <action>Explore the user's vision for their game, uncovering their creative intent and target experience</action>
  <action>Ask probing questions about genre, themes, and emotional tone they want to convey</action>
 </step>
 <step n="2" goal="Capture basic metadata">
  <ask>What is your target platform? Choose: PC, Console, Mobile, Web</ask> <!-- Prescriptive for simple choice -->
  <ask>Select primary genre: Action, RPG, Strategy, Puzzle, Simulation, Other</ask>
 </step>
 <step n="3" goal="Deep dive into gameplay">
  <action>Guide user to articulate their core gameplay loop, exploring mechanics and player agency</action> <!-- Back to intent-based -->
  <action>Help them identify what makes their game unique and compelling</action>
 </step>
 ```
 **Guidelines for the chosen style:**
 If user chose **Intent-Based**:
 - Default to goal-oriented <action> tags
 - Use open-ended guidance language
 - Save prescriptive <ask> tags for simple data/choices
 - Focus on "guide", "explore", "help user", "validate"
 - Allow LLM to adapt questions to user responses
 If user chose **Prescriptive**:
 - Default to explicit <ask> tags with clear options
 - Use precise wording for consistency
 - Save intent-based <action> tags for complex discovery
 - Focus on "choose", "select", "specify", "confirm"
 - Provide structured choices when possible
 **Remember:** The goal is optimal human-AI collaboration. Use whichever style best serves the user at each step.
 <critical>Save location:</critical>
 - Write to {{output_folder}}/instructions.md
  </step>
 <step n="6" goal="Create template.md" if="workflow_type == 'document'">
 Load and use the template at: {template_template}
 Generate the template.md file following guide conventions:
 1. Document structure with clear sections
 2. Variable syntax: {{variable_name}} using snake_case
 3. Variable names MUST match <template-output> tags exactly from instructions
 4. Include standard metadata header (optional - config variables available):
   ```markdown
   # Document Title
   **Date:** {{date}}
   **Author:** {{user_name}}
   ```
   Note: {{date}} and {{user_name}} are optional in headers. Primary purpose of these variables:
   - {{date}} - Gives agent current date awareness (not confused with training cutoff)
   - {{user_name}} - Optional author attribution
   - {{communication_language}} - NOT for document output! Tells agent how to communicate during execution
 5. Follow naming conventions from guide:
   - Use descriptive names: {{primary_user_journey}} not {{puj}}
   - Snake_case for all variables
   - Match instruction outputs precisely
 Variable sources as per guide:
 - workflow.yaml config values (user_name, communication_language, date, output_folder)
 - User input runtime values
 - Step outputs via <template-output>
 - System variables (date, paths)
 <critical>Standard config variables in templates:</critical>
 Templates CAN optionally use these config variables:
 - {{user_name}} - Document author (optional)
 - {{date}} - Generation date (optional)
 IMPORTANT: {{communication_language}} is NOT for document headers!
 - Purpose: Tells agent how to communicate with user during workflow execution
 - NOT for: Document output language or template headers
 - Future: {{document_output_language}} will handle multilingual document generation
 These variables are automatically available from workflow.yaml config block.
 <critical>Save location:</critical>
 - Write to {{output_folder}}/template.md
  </step>
 <step n="7" goal="Create validation checklist" optional="true">
 Ask if user wants a validation checklist. If yes:
 Load and use the template at: {template_checklist}
 Create checklist.md following guide best practices:
 1. Make criteria MEASURABLE and SPECIFIC
   ❌ "- [ ] Good documentation"
   ✅ "- [ ] Each function has JSDoc comments with parameters and return types"
 2. Group checks logically:
   - Structure: All sections present, no placeholders, proper formatting
   - Content Quality: Clear and specific, technically accurate, consistent terminology
   - Completeness: Ready for next phase, dependencies documented, action items defined
 3. Include workflow-specific validations based on type:
   - Document workflows: Template variables mapped, sections complete
   - Action workflows: Actions clearly defined, error handling specified
   - Interactive: User prompts clear, decision points documented
 4. Add final validation section with issue lists
 <critical>Save location:</critical>
 - Write to {{output_folder}}/checklist.md
  </step>
 <step n="8" goal="Create supporting files" optional="true">
 Ask if any supporting data files are needed:
 - CSV files with data
 - Example documents
 - Reference materials
 If yes, create placeholder files or copy from templates.
 </step>
 <step n="9" goal="Test and validate workflow">
 Review the created workflow:
 **Basic Validation:**
 1. Verify all file paths are correct
 2. Check variable names match between files
 3. Ensure step numbering is sequential
 4. Validate YAML syntax
 5. Confirm all placeholders are replaced
 **Standard Config Validation:**
 6. Verify workflow.yaml contains standard config block:
 - config_source defined
 - output_folder, user_name, communication_language pulled from config
 - date set to system-generated
 7. Check instructions use config variables where appropriate
 8. Verify template includes config variables in metadata (if document workflow)
 **YAML/Instruction/Template Alignment:**
 9. Cross-check all workflow.yaml variables against instruction usage:
 - Are all yaml variables referenced in instructions.md OR template.md?
 - Are there hardcoded values that should be variables?
 - Do template variables match <template-output> tags in instructions?
 10. Identify any unused yaml fields (bloat detection)
 Show user a summary of created files and their locations.
 Ask if they want to:
 - Test run the workflow
 - Make any adjustments
 - Add additional steps or features
  </step>
 <step n="9b" goal="Configure web bundle (optional)">
 <ask>Will this workflow need to be deployable as a web bundle? [yes/no]</ask>
 If yes:
 <action>Explain web bundle requirements:</action>
 - Web bundles are self-contained and cannot use config_source variables
 - All files must be explicitly listed in web_bundle_files
 - File paths use .bmad/ root (not {project-root})
 <action>Configure web_bundle section in workflow.yaml:</action>
 1. Copy core workflow metadata (name, description, author)
 2. Convert all file paths to .bmad/-relative paths:
   - Remove {project-root}/ prefix
   - Remove {config_source} references (use hardcoded values)
   - Example: "{project-root}/.bmad/bmm/workflows/x" → ".bmad/bmm/workflows/x"
 3. List ALL referenced files by scanning:
   **Scan instructions.md for:**
   - File paths in <action> tags
   - Data files (CSV, JSON, YAML, etc.)
   - Validation/checklist files
   - Any <invoke-workflow> calls → must include that workflow's yaml file
   - Any <goto> tags that reference other workflows
   - Shared templates or includes
   **Scan template.md for:**
   - Any includes or references to other files
   - Shared template fragments
   **Critical: Workflow Dependencies**
   - If instructions call another workflow, that workflow's yaml MUST be in web_bundle_files
   - Example: `<invoke-workflow>{project-root}/.bmad/core/workflows/x/workflow.yaml</invoke-workflow>`
     → Add ".bmad/core/workflows/x/workflow.yaml" to web_bundle_files
 4. Create web_bundle_files array with complete list
 Example:
 ```yaml
 web_bundle:
  name: '{workflow_name}'
  description: '{workflow_description}'
  author: '{author}'
  instructions: '.bmad/{module}/workflows/{workflow}/instructions.md'
  validation: '.bmad/{module}/workflows/{workflow}/checklist.md'
  template: '.bmad/{module}/workflows/{workflow}/template.md'
  # Any data files (no config_source)
  data_file: '.bmad/{module}/workflows/{workflow}/data.csv'
  web_bundle_files:
    - '.bmad/{module}/workflows/{workflow}/instructions.md'
    - '.bmad/{module}/workflows/{workflow}/checklist.md'
    - '.bmad/{module}/workflows/{workflow}/template.md'
    - '.bmad/{module}/workflows/{workflow}/data.csv'
    # Add every single file referenced anywhere
  # CRITICAL: If this workflow invokes other workflows, use existing_workflows
  # This signals the bundler to recursively include those workflows' web_bundles
  existing_workflows:
    - workflow_variable_name: '.bmad/path/to/workflow.yaml'
 ```
 **Example with existing_workflows:**
 ```yaml
 web_bundle:
  name: 'brainstorm-game'
  description: 'Game brainstorming with CIS workflow'
  author: 'BMad'
  instructions: '.bmad/bmm/workflows/brainstorm-game/instructions.md'
  template: false
  web_bundle_files:
    - '.bmad/bmm/workflows/brainstorm-game/instructions.md'
    - '.bmad/mmm/workflows/brainstorm-game/game-context.md'
    - '.bmad/core/workflows/brainstorming/workflow.yaml'
  existing_workflows:
    - core_brainstorming: '.bmad/core/workflows/brainstorming/workflow.yaml'
 ```
 **What existing_workflows does:**
 - Tells the bundler this workflow invokes another workflow
 - Bundler recursively includes the invoked workflow's entire web_bundle
 - Essential for meta-workflows that orchestrate other workflows
 - Maps workflow variable names to their .bmad/-relative paths
 <action>Validate web bundle completeness:</action>
 - Ensure no {config_source} variables remain
 - Verify all file paths are listed
 - Check that paths are .bmad/-relative
 - If workflow uses <invoke-workflow>, add to existing_workflows
 <template-output>web_bundle_config</template-output>
 </step>
 <step n="10" goal="Document and finalize">
 <action>Create a brief README for the workflow folder explaining purpose, how to invoke, expected inputs, generated outputs, and any special requirements</action>
 <action>Provide {user_name} with workflow completion summary in {communication_language}:</action>
 - Location of created workflow: {{output_folder}}
 - Command to run it: `workflow {workflow_name}`
 - Next steps:
  - Run the BMAD Method installer to this project location
  - Select 'Compile Agents (Quick rebuild of all agent .md files)' after confirming the folder
  - This will compile the new workflow and make it available for use
    </step>
 </workflow>
--- a/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md
+++ b/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md
--- a/.bmad/bmb/workflows/create-workflow/workflow-template/checklist.md
+++ b/.bmad/bmb/workflows/create-workflow/workflow-template/checklist.md
@ -1,24 +0,0 @@
 # {Title} Checklist Validation
 ## {Section Foo}
 - [ ] Check 1
 - [ ] Check 2
 - [ ] ...
 - [ ] Check n
 ...
 ## {Section Bar}
 - [ ] Check 1
 - [ ] Check 2
 - [ ] ...
 - [ ] Check n
 ## Final Validation
 - [ ] Section Foo
  - Issue List
 - [ ] Section Bar
  - Issue List
--- a/.bmad/bmb/workflows/create-workflow/workflow-template/instructions.md
+++ b/.bmad/bmb/workflows/create-workflow/workflow-template/instructions.md
@ -1,13 +0,0 @@
 # PRD 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-related}/.bmad/{module-code}/workflows/{workflow}/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the workflow process</critical>
 <workflow>
 <step n="1" goal="">
 ...
 </step>
 ...
 </workflow>
--- a/.bmad/bmb/workflows/create-workflow/workflow-template/template.md
+++ b/.bmad/bmb/workflows/create-workflow/workflow-template/template.md
@ -1,9 +0,0 @@
 # Title
 **Date:** {{date}}
 ## {Section 1}
 {{section_1_results}}
 etc...
--- a/.bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml
+++ b/.bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml
@ -1,39 +0,0 @@
 # {TITLE} Workflow Template Configuration
 name: "{WORKFLOW_CODE}"
 description: "{WORKFLOW_DESCRIPTION}"
 author: "BMad"
 # Critical variables load from config_source
 # Add Additional Config Pulled Variables Here
 config_source: "{project-root}/{module-code}/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 # Required Data Files - HALT if missing!
 # optional, can be omitted
 brain_techniques: "{installed_path}/{critical-data-file.csv}" # example, can be other formats or URLs
 # Optional docs that if loaded on start to kickstart this workflow or used at some point, these are meant to be suggested inputs for the user
 recommended_inputs: # optional, can be omitted
  - example_input: "{project-root}/{path/to/file.md}"
 # Module path and component files
 installed_path: "{project-root}/.bmad/{module-code}/workflows/{workflow-code}"
 template: "{installed_path}/template.md" # optional, can be omitted
 instructions: "{installed_path}/instructions.md" # optional, can be omitted
 validation: "{installed_path}/checklist.md" # optional, can be omitted
 # Output configuration
 default_output_file: "{output_folder}/{file.md}" # optional, can be omitted
 validation_output_file: "{output_folder}/{file-validation-report.md}" # optional, can be omitted
 # Tool Requirements (MCP Required Tools or other tools needed to run this workflow)
 required_tools: #optional, can be omitted
  - "Tool Name": #example, can be omitted if none
      description: "Description of why this tool is needed"
      link: "https://link-to-tool.com"
 # Web Bundle Configuration (optional - for web-deployable workflows)
 # IMPORTANT: Web bundles are self-contained and cannot use config_source variables
 # All referenced files must be listed in web_bundle_files
--- a/.bmad/bmb/workflows/create-workflow/workflow.yaml
+++ b/.bmad/bmb/workflows/create-workflow/workflow.yaml
@ -1,40 +0,0 @@
 # Build Workflow - Workflow Builder Configuration
 name: create-workflow
 description: "Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design."
 author: "BMad Builder"
 # Critical variables
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 custom_workflow_location: "{config_source}:custom_workflow_location"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 # Template files for new workflows
 template_workflow_yaml: "{workflow_template_path}/workflow.yaml"
 template_instructions: "{workflow_template_path}/instructions.md"
 template_template: "{workflow_template_path}/template.md"
 template_checklist: "{workflow_template_path}/checklist.md"
 # Optional input docs
 recommended_inputs:
  - existing_workflows: "{project-root}/.bmad/*/workflows/"
  - bmm_workflows: "{project-root}/.bmad/bmm/workflows/"
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/create-workflow"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Required data files - CRITICAL for workflow conventions
 workflow_creation_guide: "{installed_path}/workflow-creation-guide.md"
 workflow_template_path: "{installed_path}/workflow-template"
 # Output configuration - Creates the new workflow folder with all files
 # If workflow belongs to a module: Save to module's workflows folder
 # If standalone workflow: Save to custom_workflow_location/{{workflow_name}}
 module_output_folder: "{project-root}/.bmad/{{target_module}}/workflows/{{workflow_name}}"
 standalone_output_folder: "{custom_workflow_location}/{{workflow_name}}"
 standalone: true
 # Web bundle configuration
--- a/.bmad/bmb/workflows/edit-agent/README.md
+++ b/.bmad/bmb/workflows/edit-agent/README.md
@ -1,112 +0,0 @@
 # Edit Agent Workflow
 Interactive workflow for editing existing BMAD Core agents while maintaining best practices and conventions.
 ## Purpose
 This workflow helps you refine and improve existing agents by:
 - Analyzing agents against BMAD Core best practices
 - Identifying issues and improvement opportunities
 - Providing guided editing for specific aspects
 - Validating changes against agent standards
 - Ensuring consistency with agent architecture
 ## When to Use
 Use this workflow when you need to:
 - Fix issues in existing agents
 - Add new menu items or workflows
 - Improve agent persona or communication style
 - Update configuration handling
 - Convert between agent types (full/hybrid/standalone)
 - Optimize agent structure and clarity
 ## What You'll Need
 - Path to the agent file you want to edit (.yaml or .md)
 - Understanding of what changes you want to make
 - Access to the agent documentation (loaded automatically)
 ## Workflow Steps
 1. **Load and analyze target agent** - Provide path to agent file
 2. **Analyze against best practices** - Automatic audit of agent structure
 3. **Select editing focus** - Choose what aspect to edit
 4. **Load relevant documentation** - Auto-loads guides based on your choice
 5. **Perform edits** - Review and approve changes iteratively
 6. **Validate all changes** - Comprehensive validation checklist
 7. **Generate change summary** - Summary of improvements made
 ## Editing Options
 The workflow provides 12 focused editing options:
 1. **Fix critical issues** - Address broken references, syntax errors
 2. **Add/fix standard config** - Ensure config loading and variable usage
 3. **Refine persona** - Improve role, communication style, principles
 4. **Update activation** - Modify activation steps and greeting
 5. **Manage menu items** - Add, remove, or reorganize commands
 6. **Update workflow references** - Fix paths, add new workflows
 7. **Enhance menu handlers** - Improve handler logic
 8. **Improve command triggers** - Refine asterisk commands
 9. **Optimize agent type** - Convert between full/hybrid/standalone
 10. **Add new capabilities** - Add menu items, workflows, features
 11. **Remove bloat** - Delete unused commands, redundant instructions
 12. **Full review and update** - Comprehensive improvements
 ## Agent Documentation Loaded
 This workflow automatically loads:
 - **Agent Types Guide** - Understanding full, hybrid, and standalone agents
 - **Agent Architecture** - Structure, activation, and menu patterns
 - **Command Patterns** - Menu handlers and command triggers
 - **Communication Styles** - Persona and communication guidance
 - **Workflow Execution Engine** - How agents execute workflows
 ## Output
 The workflow modifies your agent file in place, maintaining the original format (YAML or markdown). Changes are reviewed and approved by you before being applied.
 ## Best Practices
 - **Start with analysis** - Let the workflow audit your agent first
 - **Focus your edits** - Choose specific aspects to improve
 - **Review each change** - Approve or modify proposed changes
 - **Validate thoroughly** - Use the validation step to catch issues
 - **Test after editing** - Invoke the edited agent to verify it works
 ## Tips
 - If you're unsure what needs improvement, choose option 12 (Full review)
 - For quick fixes, choose the specific option (like option 6 for workflow paths)
 - The workflow loads documentation automatically - you don't need to read it first
 - You can make multiple rounds of edits in one session
 - Use the validation step to ensure you didn't miss anything
 ## Related Workflows
 - **create-agent** - Create new agents from scratch
 - **edit-workflow** - Edit workflows referenced by agents
 - **audit-workflow** - Audit workflows for compliance
 ## Example Usage
 ```
 User: I want to add a new workflow to the PM agent
 Workflow: Analyzes agent → Loads it → You choose option 5 (manage menu items)
          → Adds new menu item with workflow reference → Validates → Done
 ```
 ## Activation
 Invoke via BMad Builder agent:
 ```
 /bmad:bmb:agents:bmad-builder
 Then select: *edit-agent
 ```
 Or directly via workflow.xml with this workflow config.
--- a/.bmad/bmb/workflows/edit-agent/checklist.md
+++ b/.bmad/bmb/workflows/edit-agent/checklist.md
@ -1,112 +0,0 @@
 # Edit Agent - Validation Checklist
 Use this checklist to validate agent edits meet BMAD Core standards.
 ## Agent Structure Validation
 - [ ] Agent file format is valid (YAML or markdown/XML)
 - [ ] Agent type is clearly identified (full, hybrid, standalone)
 - [ ] File naming follows convention: `{agent-name}.agent.yaml` or `{agent-name}.agent.md`
 ## Persona Validation
 - [ ] Role is clearly defined and specific
 - [ ] Identity/purpose articulates what the agent does
 - [ ] Communication style is specified (if custom style desired)
 - [ ] Principles are listed and actionable (if applicable)
 ## Activation Validation
 - [ ] Step 1: Loads persona from current agent file
 - [ ] Step 2: Loads config file (if agent needs user context)
 - [ ] Step 3: Sets user context variables (user_name, etc.)
 - [ ] Step 4: Displays greeting using user_name and shows menu
 - [ ] Step 5: WAITs for user input (doesn't auto-execute)
 - [ ] Step 6: Processes user selection (number or trigger text)
 - [ ] Step 7: Executes appropriate menu handler
 ## Menu Validation
 - [ ] All menu items numbered sequentially
 - [ ] Each item has cmd attribute with asterisk trigger (*help, *create, etc.)
 - [ ] Workflow paths are correct (if workflow attribute present)
 - [ ] Help command is present (\*help)
 - [ ] Exit command is present (\*exit)
 - [ ] Menu items are in logical order
 ## Configuration Validation
 - [ ] Config file path is correct for module
 - [ ] Config variables loaded in activation step 2
 - [ ] Error handling present if config fails to load
 - [ ] user_name used in greeting and communication
 - [ ] communication_language used for output
 - [ ] output_folder used for file outputs (if applicable)
 ## Menu Handler Validation
 - [ ] menu-handlers section is present
 - [ ] Workflow handler loads {project-root}/.bmad/core/tasks/workflow.xml
 - [ ] Workflow handler passes yaml path as 'workflow-config' parameter
 - [ ] Handlers check for attributes (workflow, exec, tmpl, data, action)
 - [ ] Handler logic is complete and follows patterns
 ## Workflow Integration Validation
 - [ ] All workflow paths exist and are correct
 - [ ] Workflow paths use {project-root} variable
 - [ ] Workflows are appropriate for agent's purpose
 - [ ] Workflow parameters are passed correctly
 ## Communication Validation
 - [ ] Agent communicates in {communication_language}
 - [ ] Communication style matches persona
 - [ ] Error messages are clear and helpful
 - [ ] Confirmation messages for user actions
 ## Rules Validation
 - [ ] Rules section defines agent behavior clearly
 - [ ] File loading rules are specified
 - [ ] Menu trigger format rules are clear
 - [ ] Communication rules align with persona
 ## Quality Checks
 - [ ] No placeholder text remains ({{AGENT_NAME}}, {ROLE}, etc.)
 - [ ] No broken references or missing files
 - [ ] Syntax is valid (YAML or XML)
 - [ ] Indentation is consistent
 - [ ] Agent purpose is clear from reading persona alone
 ## Type-Specific Validation
 ### Full Agent
 - [ ] Has complete menu system with multiple items
 - [ ] Loads config file for user context
 - [ ] Supports multiple workflows
 - [ ] Session management is clear
 ### Hybrid Agent
 - [ ] Simplified activation (may skip some steps)
 - [ ] Focused set of workflows
 - [ ] May or may not have menu
 - [ ] Config loading is appropriate
 ### Standalone Agent
 - [ ] Single focused purpose
 - [ ] Minimal activation (1-3 steps)
 - [ ] No menu system
 - [ ] Direct execution pattern
 - [ ] May not need config file
 ## Final Checks
 - [ ] Agent file has been saved
 - [ ] File path is in correct module directory
 - [ ] Agent is ready for testing
 - [ ] Documentation is updated (if needed)
--- a/.bmad/bmb/workflows/edit-agent/instructions.md
+++ b/.bmad/bmb/workflows/edit-agent/instructions.md
@ -1,290 +0,0 @@
 # Edit Agent - Agent Editor 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/bmb/workflows/edit-agent/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
 <critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <workflow>
 <step n="1" goal="Load and deeply understand the target agent">
 <ask>What is the path to the agent you want to edit?</ask>
 <action>Load the agent file from the provided path</action>
 <action>Load ALL agent documentation to inform understanding:
 - Agent types guide: {agent_types}
 - Agent architecture: {agent_architecture}
 - Command patterns: {agent_commands}
 - Communication styles: {communication_styles}
 - Workflow execution engine: {workflow_execution_engine}
  </action>
 <action>Analyze the agent structure thoroughly:
 - Parse persona (role, identity, communication_style, principles)
 - Understand activation flow and steps
 - Map menu items and their workflows
 - Identify configuration dependencies
 - Assess agent type (full, hybrid, standalone)
 - Check workflow references for validity
 - Evaluate against best practices from loaded guides
  </action>
 <action>Reflect understanding back to {user_name}:
 Present a warm, conversational summary adapted to the agent's complexity:
 - What this agent does (its role and purpose)
 - How it's structured (type, menu items, workflows)
 - What you notice (strengths, potential improvements, issues)
 - Your initial assessment of its health
 Be conversational, not clinical. Help {user_name} see their agent through your eyes.
 </action>
 <ask>Does this match your understanding of what this agent should do?</ask>
 <template-output>agent_understanding</template-output>
 </step>
 <step n="2" goal="Discover improvement goals collaboratively">
 <critical>Understand WHAT the user wants to improve and WHY before diving into edits</critical>
 <action>Engage in collaborative discovery:
 Ask open-ended questions to understand their goals:
 - What prompted you to want to edit this agent?
 - What isn't working the way you'd like?
 - Are there specific behaviors you want to change?
 - Is there functionality you want to add or remove?
 - How do users interact with this agent? What feedback have they given?
 Listen for clues about:
 - Functional issues (broken references, missing workflows)
 - User experience issues (confusing menu, unclear communication)
 - Performance issues (too slow, too verbose, not adaptive enough)
 - Maintenance issues (hard to update, bloated, inconsistent)
 - Integration issues (doesn't work well with other agents/workflows)
  </action>
 <action>Based on their responses and your analysis from step 1, identify improvement opportunities:
 Organize by priority and user goals:
 - CRITICAL issues blocking functionality
 - IMPORTANT improvements enhancing user experience
 - NICE-TO-HAVE enhancements for polish
 Present these conversationally, explaining WHY each matters and HOW it would help.
 </action>
 <action>Collaborate on priorities:
 Don't just list options - discuss them:
 - "I noticed {{issue}} - this could cause {{problem}}. Does this concern you?"
 - "The agent could be more {{improvement}} which would help when {{use_case}}. Worth exploring?"
 - "Based on what you said about {{user_goal}}, we might want to {{suggestion}}. Thoughts?"
 Let the conversation flow naturally. Build a shared vision of what "better" looks like.
 </action>
 <template-output>improvement_goals</template-output>
 </step>
 <step n="3" goal="Facilitate improvements collaboratively" repeat="until-user-satisfied">
 <critical>Work iteratively - improve, review, refine. Never dump all changes at once.</critical>
 <action>For each improvement area, facilitate collaboratively:
 1. **Explain the current state and why it matters**
   - Show relevant sections of the agent
   - Explain how it works now and implications
   - Connect to user's goals from step 2
 2. **Propose improvements with rationale**
   - Suggest specific changes that align with best practices
   - Explain WHY each change helps
   - Provide examples from the loaded guides when helpful
   - Show before/after comparisons for clarity
 3. **Collaborate on the approach**
   - Ask if the proposed change addresses their need
   - Invite modifications or alternative approaches
   - Explain tradeoffs when relevant
   - Adapt based on their feedback
 4. **Apply changes iteratively**
   - Make one focused improvement at a time
   - Show the updated section
   - Confirm it meets their expectation
   - Move to next improvement or refine current one
     </action>
 <action>Common improvement patterns to facilitate:
 **If fixing broken references:**
 - Identify all broken paths
 - Explain what each reference should point to
 - Verify new paths exist before updating
 - Update and confirm working
 **If refining persona/communication:**
 - Review current persona definition
 - Discuss desired communication style with examples
 - Explore communication styles guide for patterns
 - Refine language to match intent
 - Test tone with example interactions
 **If updating activation:**
 - Walk through current activation flow
 - Identify bottlenecks or confusion points
 - Propose streamlined flow
 - Ensure config loading works correctly
 - Verify all session variables are set
 **If managing menu items:**
 - Review current menu organization
 - Discuss if structure serves user mental model
 - Add/remove/reorganize as needed
 - Ensure all workflow references are valid
 - Update triggers to be intuitive
 **If enhancing menu handlers:**
 - Explain current handler logic
 - Identify where handlers could be smarter
 - Propose enhanced logic based on agent architecture patterns
 - Ensure handlers properly invoke workflows
 **If optimizing agent type:**
 - Discuss whether current type fits use case
 - Explain characteristics of full/hybrid/standalone
 - If converting, guide through structural changes
 - Ensure all pieces align with new type
  </action>
 <action>Throughout improvements, educate when helpful:
 Share insights from the guides naturally:
 - "The agent architecture guide suggests {{pattern}} for this scenario"
 - "Looking at the command patterns, we could use {{approach}}"
 - "The communication styles guide has a great example of {{technique}}"
 Connect improvements to broader BMAD principles without being preachy.
 </action>
 <ask>After each significant change:
 - "Does this feel right for what you're trying to achieve?"
 - "Want to refine this further, or move to the next improvement?"
 - "Is there anything about this change that concerns you?"
  </ask>
 <template-output>improvement_implementation</template-output>
 </step>
 <step n="4" goal="Validate improvements holistically">
 <action>Run comprehensive validation conversationally:
 Don't just check boxes - explain what you're validating and why it matters:
 - "Let me verify all the workflow paths resolve correctly..."
 - "Checking that the activation flow works smoothly..."
 - "Making sure menu handlers are wired up properly..."
 - "Validating config loading is robust..."
  </action>
 <action>Load validation checklist: {installed_path}/checklist.md</action>
 <action>Check all items from checklist systematically</action>
 <check if="validation_issues_found">
  <action>Present issues conversationally:
 Explain what's wrong and implications:
 - "I found {{issue}} which could cause {{problem}}"
 - "The {{component}} needs {{fix}} because {{reason}}"
 Propose fixes immediately:
 - "I can fix this by {{solution}}. Should I?"
 - "We have a couple options here: {{option1}} or {{option2}}. Thoughts?"
  </action>
 <action>Fix approved issues and re-validate</action>
 </check>
 <check if="validation_passes">
  <action>Confirm success warmly:
 "Excellent! Everything validates cleanly:
 - All paths resolve correctly
 - Activation flow is solid
 - Menu structure is clear
 - Handlers work properly
 - Config loading is robust
 Your agent is in great shape."
 </action>
 </check>
 <template-output>validation_results</template-output>
 </step>
 <step n="5" goal="Review improvements and guide next steps">
 <action>Create a conversational summary of what improved:
 Tell the story of the transformation:
 - "We started with {{initial_state}}"
 - "You wanted to {{user_goals}}"
 - "We made these key improvements: {{changes_list}}"
 - "Now your agent {{improved_capabilities}}"
 Highlight the impact:
 - "This means users will experience {{benefit}}"
 - "The agent is now more {{quality}}"
 - "It follows best practices for {{patterns}}"
  </action>
 <action>Guide next steps based on changes made:
 If significant structural changes:
 - "Since we restructured the activation, you should test the agent with a real user interaction"
 If workflow references changed:
 - "The agent now uses {{new_workflows}} - make sure those workflows are up to date"
 If this is part of larger module work:
 - "This agent is part of {{module}} - consider if other agents need similar improvements"
 Be a helpful guide to what comes next, not just a task completer.
 </action>
 <ask>Would you like to:
 - Test the edited agent by invoking it
 - Edit another agent
 - Make additional refinements to this one
 - Return to your module work
  </ask>
 <template-output>completion_summary</template-output>
 </step>
 </workflow>
--- a/.bmad/bmb/workflows/edit-agent/workflow.yaml
+++ b/.bmad/bmb/workflows/edit-agent/workflow.yaml
@ -1,33 +0,0 @@
 # Edit Agent - Agent Editor Configuration
 name: "edit-agent"
 description: "Edit existing BMAD agents while following all best practices and conventions"
 author: "BMad"
 # Critical variables load from config_source
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 # Required Data Files - Critical for understanding agent conventions
 agent_types: "{project-root}/.bmad/bmb/workflows/create-agent/agent-types.md"
 agent_architecture: "{project-root}/.bmad/bmb/workflows/create-agent/agent-architecture.md"
 agent_commands: "{project-root}/.bmad/bmb/workflows/create-agent/agent-command-patterns.md"
 communication_styles: "{project-root}/.bmad/bmb/workflows/create-agent/communication-styles.md"
 # Workflow execution engine reference
 workflow_execution_engine: "{project-root}/.bmad/core/tasks/workflow.xml"
 # Optional docs that can be used to understand the target agent
 recommended_inputs:
  - target_agent: "Path to the agent.yaml or agent.md file to edit"
  - example_agents: "{project-root}/.bmad/bmm/agents/"
  - agent_activation_rules: "{project-root}/src/utility/models/agent-activation-ide.xml"
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/edit-agent"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 standalone: true
 # Web bundle configuration
--- a/.bmad/bmb/workflows/edit-module/README.md
+++ b/.bmad/bmb/workflows/edit-module/README.md
@ -1,187 +0,0 @@
 # Edit Module Workflow
 Interactive workflow for editing existing BMAD modules, including structure, agents, workflows, configuration, and documentation.
 ## Purpose
 This workflow helps you improve and maintain BMAD modules by:
 - Analyzing module structure against best practices
 - Managing agents and workflows within the module
 - Updating configuration and documentation
 - Ensuring cross-module integration works correctly
 - Maintaining installer configuration (for source modules)
 ## When to Use
 Use this workflow when you need to:
 - Add new agents or workflows to a module
 - Update module configuration
 - Improve module documentation
 - Reorganize module structure
 - Set up cross-module workflow sharing
 - Fix issues in module organization
 - Update installer configuration
 ## What You'll Need
 - Path to the module directory you want to edit
 - Understanding of what changes you want to make
 - Access to module documentation (loaded automatically)
 ## Workflow Steps
 1. **Load and analyze target module** - Provide path to module directory
 2. **Analyze against best practices** - Automatic audit of module structure
 3. **Select editing focus** - Choose what aspect to edit
 4. **Load relevant documentation and tools** - Auto-loads guides and workflows
 5. **Perform edits** - Review and approve changes iteratively
 6. **Validate all changes** - Comprehensive validation checklist
 7. **Generate change summary** - Summary of improvements made
 ## Editing Options
 The workflow provides 12 focused editing options:
 1. **Fix critical issues** - Address missing files, broken references
 2. **Update module config** - Edit config.yaml fields
 3. **Manage agents** - Add, edit, or remove agents
 4. **Manage workflows** - Add, edit, or remove workflows
 5. **Update documentation** - Improve README files and guides
 6. **Reorganize structure** - Fix directory organization
 7. **Add new agent** - Create and integrate new agent
 8. **Add new workflow** - Create and integrate new workflow
 9. **Update installer** - Modify installer configuration (source only)
 10. **Cross-module integration** - Set up workflow sharing with other modules
 11. **Remove deprecated items** - Delete unused agents, workflows, or files
 12. **Full module review** - Comprehensive analysis and improvements
 ## Integration with Other Workflows
 This workflow integrates with:
 - **edit-agent** - For editing individual agents
 - **edit-workflow** - For editing individual workflows
 - **create-agent** - For adding new agents
 - **create-workflow** - For adding new workflows
 When you select options to manage agents or workflows, the appropriate specialized workflow is invoked automatically.
 ## Module Structure
 A proper BMAD module has:
 ```
 module-code/
 ├── agents/              # Agent definitions
 │   └── *.agent.yaml
 ├── workflows/           # Workflow definitions
 │   └── workflow-name/
 │       ├── workflow.yaml
 │       ├── instructions.md
 │       ├── checklist.md
 │       └── README.md
 ├── config.yaml          # Module configuration
 └── README.md           # Module documentation
 ```
 ## Standard Module Config
 Every module config.yaml should have:
 ```yaml
 module_name: 'Full Module Name'
 module_code: 'xyz'
 user_name: 'User Name'
 communication_language: 'english'
 output_folder: 'path/to/output'
 ```
 Optional fields may be added for module-specific needs.
 ## Cross-Module Integration
 Modules can share workflows:
 ```yaml
 # In agent menu item:
 workflow: '{project-root}/.bmad/other-module/workflows/shared-workflow/workflow.yaml'
 ```
 Common patterns:
 - BMM uses CIS brainstorming workflows
 - All modules can use core workflows
 - Modules can invoke each other's workflows
 ## Output
 The workflow modifies module files in place, including:
 - config.yaml
 - Agent files
 - Workflow files
 - README and documentation files
 - Directory structure (if reorganizing)
 Changes are reviewed and approved by you before being applied.
 ## Best Practices
 - **Start with analysis** - Let the workflow audit your module first
 - **Use specialized workflows** - Let edit-agent and edit-workflow handle detailed edits
 - **Update documentation** - Keep README files current with changes
 - **Validate thoroughly** - Use the validation step to catch structural issues
 - **Test after editing** - Invoke agents and workflows to verify they work
 ## Tips
 - For adding agents/workflows, use options 7-8 to create and integrate in one step
 - For quick config changes, use option 2 (update module config)
 - Cross-module integration (option 10) helps set up workflow sharing
 - Full module review (option 12) is great for inherited or legacy modules
 - The workflow handles path updates when you reorganize structure
 ## Source vs Installed Modules
 **Source modules** (in src/modules/):
 - Have installer files in tools/cli/installers/
 - Can configure web bundles
 - Are the development source of truth
 **Installed modules** (in .bmad/):
 - Are deployed to target projects
 - Use config.yaml for user customization
 - Are compiled from source during installation
 This workflow works with both, but installer options only apply to source modules.
 ## Example Usage
 ```
 User: I want to add a new workflow to BMM for API design
 Workflow: Analyzes BMM → You choose option 8 (add new workflow)
          → Invokes create-workflow → Creates workflow
          → Integrates it into module → Updates README → Done
 ```
 ## Activation
 Invoke via BMad Builder agent:
 ```
 /bmad:bmb:agents:bmad-builder
 Then select: *edit-module
 ```
 Or directly via workflow.xml with this workflow config.
 ## Related Resources
 - **Module Structure Guide** - Comprehensive module architecture documentation
 - **BMM Module** - Example of full-featured module
 - **BMB Module** - Example of builder/tooling module
 - **CIS Module** - Example of workflow library module
--- a/.bmad/bmb/workflows/edit-module/checklist.md
+++ b/.bmad/bmb/workflows/edit-module/checklist.md
@ -1,165 +0,0 @@
 # Edit Module - Validation Checklist
 Use this checklist to validate module edits meet BMAD Core standards.
 ## Module Structure Validation
 - [ ] Module has clear 3-letter code (bmm, bmb, cis, etc.)
 - [ ] Module is in correct location (src/modules/ for source, .bmad/ for installed)
 - [ ] agents/ directory exists
 - [ ] workflows/ directory exists
 - [ ] config.yaml exists in module root
 - [ ] README.md exists in module root
 - [ ] Directory structure follows BMAD conventions
 ## Configuration Validation
 ### Required Fields
 - [ ] module_name is descriptive and clear
 - [ ] module_code is 3-letter code matching directory name
 - [ ] user_name field present
 - [ ] communication_language field present
 - [ ] output_folder field present
 ### Optional Fields (if used)
 - [ ] custom_agent_location documented
 - [ ] custom_module_location documented
 - [ ] Module-specific fields documented in README
 ### File Quality
 - [ ] config.yaml is valid YAML syntax
 - [ ] No duplicate keys
 - [ ] Values are appropriate types (strings, paths, etc.)
 - [ ] Comments explain non-obvious fields
 ## Agent Validation
 ### Agent Files
 - [ ] All agents in agents/ directory
 - [ ] Agent files follow naming: {agent-name}.agent.yaml or .md
 - [ ] Agent filenames use kebab-case
 - [ ] No orphaned or temporary agent files
 ### Agent Content
 - [ ] Each agent has clear role and purpose
 - [ ] Agents reference workflows correctly
 - [ ] Agent workflow paths are valid
 - [ ] Agents load module config correctly (if needed)
 - [ ] Agent menu items reference existing workflows
 ### Agent Integration
 - [ ] All agents listed in module README
 - [ ] Agent relationships documented (if applicable)
 - [ ] Cross-agent workflows properly linked
 ## Workflow Validation
 ### Workflow Structure
 - [ ] All workflows in workflows/ directory
 - [ ] Each workflow directory has workflow.yaml
 - [ ] Each workflow directory has instructions.md
 - [ ] Workflow directories use kebab-case naming
 - [ ] No orphaned or incomplete workflow directories
 ### Workflow Content
 - [ ] workflow.yaml is valid YAML
 - [ ] workflow.yaml has name field
 - [ ] workflow.yaml has description field
 - [ ] workflow.yaml has author field
 - [ ] instructions.md has proper <workflow> structure
 - [ ] Workflow steps are numbered and logical
 ### Workflow Integration
 - [ ] All workflows listed in module README
 - [ ] Workflow paths in agents are correct
 - [ ] Cross-module workflow references are valid
 - [ ] Sub-workflow references exist
 ## Documentation Validation
 ### Module README
 - [ ] Module README describes purpose clearly
 - [ ] README lists all agents with descriptions
 - [ ] README lists all workflows with descriptions
 - [ ] README includes installation instructions (if applicable)
 - [ ] README explains module's role in BMAD ecosystem
 ### Workflow READMEs
 - [ ] Each workflow has its own README.md
 - [ ] Workflow READMEs explain purpose
 - [ ] Workflow READMEs list inputs/outputs
 - [ ] Workflow READMEs include usage examples
 ### Other Documentation
 - [ ] Usage guides present (if needed)
 - [ ] Architecture docs present (if complex module)
 - [ ] Examples provided (if applicable)
 ## Cross-References Validation
 - [ ] Agent workflow references point to existing workflows
 - [ ] Workflow sub-workflow references are valid
 - [ ] Cross-module references use correct paths
 - [ ] Config file paths use {project-root} correctly
 - [ ] No hardcoded absolute paths
 ## Installer Validation (Source Modules Only)
 - [ ] Installer script exists in tools/cli/installers/
 - [ ] Installer script name: install-{module-code}.js
 - [ ] Module metadata in installer is correct
 - [ ] Web bundle configuration valid (if applicable)
 - [ ] Installation paths are correct
 - [ ] Dependencies documented in installer
 ## Web Bundle Validation (If Applicable)
 - [ ] Web bundles configured in workflow.yaml files
 - [ ] All referenced files included in web_bundle_files
 - [ ] Paths are .bmad/-relative (not project-root)
 - [ ] No config_source references in web bundles
 - [ ] Invoked workflows included in dependencies
 ## Quality Checks
 - [ ] No placeholder text remains ({MODULE_NAME}, {CODE}, etc.)
 - [ ] No broken file references
 - [ ] No duplicate content across files
 - [ ] Consistent naming conventions throughout
 - [ ] Module purpose is clear from README alone
 ## Integration Checks
 - [ ] Module doesn't conflict with other modules
 - [ ] Shared resources properly documented
 - [ ] Dependencies on other modules explicit
 - [ ] Module can be installed independently (if designed that way)
 ## User Experience
 - [ ] Module purpose is immediately clear
 - [ ] Agents have intuitive names
 - [ ] Workflows have descriptive names
 - [ ] Menu items are logically organized
 - [ ] Error messages are helpful
 - [ ] Success messages confirm actions
 ## Final Checks
 - [ ] All files have been saved
 - [ ] File permissions are correct
 - [ ] Git status shows expected changes
 - [ ] Module is ready for testing
 - [ ] Documentation accurately reflects changes
--- a/.bmad/bmb/workflows/edit-module/instructions.md
+++ b/.bmad/bmb/workflows/edit-module/instructions.md
@ -1,339 +0,0 @@
 # Edit Module - Module Editor 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/bmb/workflows/edit-module/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
 <critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <workflow>
 <step n="1" goal="Load and deeply understand the target module">
 <ask>What is the path to the module you want to edit? (provide path to module directory like .bmad/bmm/ or src/modules/bmm/)</ask>
 <action>Load the module directory structure completely:
 - Scan all directories and files
 - Load config.yaml
 - Load README.md
 - List all agents in agents/ directory
 - List all workflows in workflows/ directory
 - Check for installer files (if in src/modules/)
 - Identify any custom structure or patterns
  </action>
 <action>Load ALL module documentation to inform understanding:
 - Module structure guide: {module_structure_guide}
 - Study reference modules: BMM, BMB, CIS
 - Understand BMAD module patterns and conventions
  </action>
 <action>Analyze the module deeply:
 - Identify module purpose and role in BMAD ecosystem
 - Understand agent organization and relationships
 - Map workflow organization and dependencies
 - Evaluate config structure and completeness
 - Check documentation quality and currency
 - Assess installer configuration (if source module)
 - Identify cross-module integrations
 - Evaluate against best practices from loaded guides
  </action>
 <action>Reflect understanding back to {user_name}:
 Present a warm, conversational summary adapted to the module's complexity:
 - What this module provides (its purpose and value in BMAD)
 - How it's organized (agents, workflows, structure)
 - What you notice (strengths, potential improvements, issues)
 - How it fits in the larger BMAD ecosystem
 - Your initial assessment based on best practices
 Be conversational and insightful. Help {user_name} see their module through your eyes.
 </action>
 <ask>Does this match your understanding of what this module should provide?</ask>
 <template-output>module_understanding</template-output>
 </step>
 <step n="2" goal="Discover improvement goals collaboratively">
 <critical>Understand WHAT the user wants to improve and WHY before diving into edits</critical>
 <action>Engage in collaborative discovery:
 Ask open-ended questions to understand their goals:
 - What prompted you to want to edit this module?
 - What feedback have you gotten from users of this module?
 - Are there specific agents or workflows that need attention?
 - Is the module fulfilling its intended purpose?
 - Are there new capabilities you want to add?
 - How well does it integrate with other modules?
 - Is the documentation helping users understand and use the module?
 Listen for clues about:
 - Structural issues (poor organization, hard to navigate)
 - Agent/workflow issues (outdated, broken, missing functionality)
 - Configuration issues (missing fields, incorrect setup)
 - Documentation issues (outdated, incomplete, unclear)
 - Integration issues (doesn't work well with other modules)
 - Installer issues (installation problems, missing files)
 - User experience issues (confusing, hard to use)
  </action>
 <action>Based on their responses and your analysis from step 1, identify improvement opportunities:
 Organize by priority and user goals:
 - CRITICAL issues blocking module functionality
 - IMPORTANT improvements enhancing user experience
 - NICE-TO-HAVE enhancements for polish
 Present these conversationally, explaining WHY each matters and HOW it would help.
 </action>
 <action>Collaborate on priorities:
 Don't just list options - discuss them:
 - "I noticed {{issue}} - this could make it hard for users to {{problem}}. Want to address this?"
 - "The module could be more {{improvement}} which would help when {{use_case}}. Worth exploring?"
 - "Based on what you said about {{user_goal}}, we might want to {{suggestion}}. Thoughts?"
 Let the conversation flow naturally. Build a shared vision of what "better" looks like.
 </action>
 <template-output>improvement_goals</template-output>
 </step>
 <step n="3" goal="Facilitate improvements collaboratively" repeat="until-user-satisfied">
 <critical>Work iteratively - improve, review, refine. Never dump all changes at once.</critical>
 <critical>For agent and workflow edits, invoke specialized workflows rather than doing inline</critical>
 <action>For each improvement area, facilitate collaboratively:
 1. **Explain the current state and why it matters**
   - Show relevant sections of the module
   - Explain how it works now and implications
   - Connect to user's goals from step 2
 2. **Propose improvements with rationale**
   - Suggest specific changes that align with best practices
   - Explain WHY each change helps
   - Provide examples from reference modules when helpful
   - Reference the structure guide's patterns naturally
 3. **Collaborate on the approach**
   - Ask if the proposed change addresses their need
   - Invite modifications or alternative approaches
   - Explain tradeoffs when relevant
   - Adapt based on their feedback
 4. **Apply changes appropriately**
   - For agent edits: Invoke edit-agent workflow
   - For workflow edits: Invoke edit-workflow workflow
   - For module-level changes: Make directly and iteratively
   - Show updates and confirm satisfaction
     </action>
 <action>Common improvement patterns to facilitate:
 **If improving module organization:**
 - Discuss how the current structure serves (or doesn't serve) users
 - Propose reorganization that aligns with mental models
 - Consider feature-based vs type-based organization
 - Plan the reorganization steps
 - Update all references after moving files
 **If updating module configuration:**
 - Review current config.yaml fields
 - Check for missing standard fields (user_name, communication_language, output_folder)
 - Add module-specific fields as needed
 - Remove unused or outdated fields
 - Ensure config is properly documented
 **If managing agents:**
 - Ask which agent needs attention and why
 - For editing existing agent: <invoke-workflow path="{agent_editor}">
 - For adding new agent: Guide creation and integration
 - For removing agent: Confirm, remove, update references
 - Ensure all agent references in workflows remain valid
 **If managing workflows:**
 - Ask which workflow needs attention and why
 - For editing existing workflow: <invoke-workflow path="{workflow_editor}">
 - For adding new workflow: Guide creation and integration
 - For removing workflow: Confirm, remove, update agent references
 - Ensure all workflow files are properly organized
 **If improving documentation:**
 - Review current README and identify gaps
 - Discuss what users need to know
 - Update module overview and purpose
 - List agents and workflows with clear descriptions
 - Add usage examples if helpful
 - Ensure installation/setup instructions are clear
 **If setting up cross-module integration:**
 - Identify which workflows from other modules are needed
 - Show how to reference workflows properly: {project-root}/.bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
 - Document the integration in README
 - Ensure dependencies are clear
 - Consider adding example usage
 **If updating installer (source modules only):**
 - Review installer script for correctness
 - Check web bundle configurations
 - Verify all files are included
 - Test installation paths
 - Update module metadata
  </action>
 <action>When invoking specialized workflows:
 Explain why you're handing off:
 - "This agent needs detailed attention. Let me invoke the edit-agent workflow to give it proper focus."
 - "The workflow editor can handle this more thoroughly. I'll pass control there."
 After the specialized workflow completes, return and continue:
 - "Great! That agent/workflow is updated. Want to work on anything else in the module?"
  </action>
 <action>Throughout improvements, educate when helpful:
 Share insights from the guides naturally:
 - "The module structure guide recommends {{pattern}} for this scenario"
 - "Looking at how BMM organized this, we could use {{approach}}"
 - "The BMAD convention is to {{pattern}} which helps with {{benefit}}"
 Connect improvements to broader BMAD principles without being preachy.
 </action>
 <ask>After each significant change:
 - "Does this organization feel more intuitive?"
 - "Want to refine this further, or move to the next improvement?"
 - "How does this change affect users of the module?"
  </ask>
 <template-output>improvement_implementation</template-output>
 </step>
 <step n="4" goal="Validate improvements holistically">
 <action>Run comprehensive validation conversationally:
 Don't just check boxes - explain what you're validating and why it matters:
 - "Let me verify the module structure is solid..."
 - "Checking that all agent workflow references are valid..."
 - "Making sure config.yaml has all necessary fields..."
 - "Validating documentation is complete and accurate..."
 - "Ensuring cross-module references work correctly..."
  </action>
 <action>Load validation checklist: {installed_path}/checklist.md</action>
 <action>Check all items from checklist systematically</action>
 <check if="validation_issues_found">
  <action>Present issues conversationally:
 Explain what's wrong and implications:
 - "I found {{issue}} which could cause {{problem}} for users"
 - "The {{component}} needs {{fix}} because {{reason}}"
 Propose fixes immediately:
 - "I can fix this by {{solution}}. Should I?"
 - "We have a couple options here: {{option1}} or {{option2}}. Thoughts?"
  </action>
 <action>Fix approved issues and re-validate</action>
 </check>
 <check if="validation_passes">
  <action>Confirm success warmly:
 "Excellent! Everything validates cleanly:
 - Module structure is well-organized
 - All agent and workflow references are valid
 - Configuration is complete
 - Documentation is thorough and current
 - Cross-module integrations work properly
 - Installer is correct (if applicable)
 Your module is in great shape."
 </action>
 </check>
 <template-output>validation_results</template-output>
 </step>
 <step n="5" goal="Review improvements and guide next steps">
 <action>Create a conversational summary of what improved:
 Tell the story of the transformation:
 - "We started with {{initial_state}}"
 - "You wanted to {{user_goals}}"
 - "We made these key improvements: {{changes_list}}"
 - "Now your module {{improved_capabilities}}"
 Highlight the impact:
 - "This means users will experience {{benefit}}"
 - "The module is now more {{quality}}"
 - "It follows best practices for {{patterns}}"
  </action>
 <action>Guide next steps based on changes made:
 If structure changed significantly:
 - "Since we reorganized the structure, you should update any external references to this module"
 If agents or workflows were updated:
 - "The updated agents/workflows should be tested with real user interactions"
 If cross-module integration was added:
 - "Test the integration with {{other_module}} to ensure it works smoothly"
 If installer was updated:
 - "Test the installation process to verify all files are included correctly"
 If this is part of larger BMAD work:
 - "Consider if patterns from this module could benefit other modules"
 Be a helpful guide to what comes next, not just a task completer.
 </action>
 <ask>Would you like to:
 - Test the edited module by invoking one of its agents
 - Edit a specific agent or workflow in more detail
 - Make additional refinements to the module
 - Work on a different module
  </ask>
 <template-output>completion_summary</template-output>
 </step>
 </workflow>
--- a/.bmad/bmb/workflows/edit-module/workflow.yaml
+++ b/.bmad/bmb/workflows/edit-module/workflow.yaml
@ -1,34 +0,0 @@
 # Edit Module - Module Editor Configuration
 name: "edit-module"
 description: "Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices"
 author: "BMad"
 # Critical variables load from config_source
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 # Required Data Files - Critical for understanding module conventions
 module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
 # Related workflow editors
 agent_editor: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.yaml"
 workflow_editor: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.yaml"
 # Optional docs that can be used to understand the target module
 recommended_inputs:
  - target_module: "Path to the module directory to edit"
  - bmm_module: "{project-root}/.bmad/bmm/"
  - bmb_module: "{project-root}/.bmad/bmb/"
  - cis_module: "{project-root}/.bmad/cis/"
  - existing_agents: "{project-root}/.bmad/*/agents/"
  - existing_workflows: "{project-root}/.bmad/*/workflows/"
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/edit-module"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 standalone: true
 # Web bundle configuration
--- a/.bmad/bmb/workflows/edit-workflow/README.md
+++ b/.bmad/bmb/workflows/edit-workflow/README.md
@ -1,119 +0,0 @@
 # Edit Workflow
 ## Purpose
 An intelligent workflow editor that helps you modify existing BMAD workflows while adhering to all best practices and conventions documented in the workflow creation guide.
 ## Use Case
 When you need to:
 - Fix issues in existing workflows
 - Update workflow configuration or metadata
 - Improve instruction clarity and specificity
 - Add new features or capabilities
 - Ensure compliance with BMAD workflow conventions
 ## How to Invoke
 ```
 workflow edit-workflow
 ```
 Or through a BMAD agent:
 ```
 *edit-workflow
 ```
 ## Expected Inputs
 - **Target workflow path**: Path to the workflow.yaml file or workflow folder you want to edit
 - **Edit type selection**: Choice of what aspect to modify
 - **User approval**: For each proposed change
 ## Generated Outputs
 - Modified workflow files (in place)
 - Optional change log at: `{output_folder}/workflow-edit-log-{date}.md`
 ## Features
 1. **Comprehensive Analysis**: Checks workflows against the official creation guide
 2. **Prioritized Issues**: Identifies and ranks issues by importance
 3. **Guided Editing**: Step-by-step process with explanations
 4. **Best Practices**: Ensures all edits follow BMAD conventions
 5. **Instruction Style Optimization**: Convert between intent-based and prescriptive styles
 6. **Validation**: Checks all changes for correctness
 7. **Change Tracking**: Documents what was modified and why
 ## Understanding Instruction Styles
 When editing workflows, one powerful option is **adjusting the instruction style** to better match the workflow's purpose.
 ### Intent-Based vs Prescriptive Instructions
 **Intent-Based (Recommended for most workflows)**
 Guides the AI with goals and principles, allowing flexible conversation.
 - **More flexible and conversational** - AI adapts to user responses
 - **Better for complex discovery** - Requirements gathering, creative exploration
 - **Quality over consistency** - Deep understanding matters more
 - **Example**: `<action>Guide user to define their target audience with specific demographics and needs</action>`
 **When to use:**
 - Complex discovery processes (user research, requirements)
 - Creative brainstorming and ideation
 - Iterative refinement workflows
 - Workflows requiring nuanced understanding
 **Prescriptive**
 Provides exact questions with structured options.
 - **More controlled and predictable** - Consistent questions every time
 - **Better for simple data collection** - Platform, format, yes/no choices
 - **Consistency over quality** - Same execution every run
 - **Example**: `<ask>What is your target platform? Choose: PC, Console, Mobile, Web</ask>`
 **When to use:**
 - Simple data collection (platform, format, binary choices)
 - Compliance verification and standards adherence
 - Configuration with finite options
 - Quick setup wizards
 ### Edit Workflow's Style Adjustment Feature
 The **"Adjust instruction style"** editing option (menu option 11) helps you:
 1. **Analyze current style** - Identifies whether workflow is primarily intent-based or prescriptive
 2. **Convert between styles** - Transform prescriptive steps to intent-based (or vice versa)
 3. **Optimize the mix** - Intelligently recommend the best style for each step
 4. **Step-by-step control** - Review and decide on each step individually
 **Common scenarios:**
 - **Make workflow more conversational**: Convert rigid <ask> tags to flexible <action> tags for complex steps
 - **Make workflow more consistent**: Convert open-ended <action> tags to structured <ask> tags for simple data collection
 - **Balance both approaches**: Use intent-based for discovery, prescriptive for simple choices
 This feature is especially valuable when converting legacy workflows or adapting workflows for different use cases.
 ## Workflow Steps
 1. Load and analyze target workflow
 2. Check against best practices
 3. Select editing focus
 4. Load relevant documentation
 5. Perform edits with user approval
 6. Validate all changes (optional)
 7. Generate change summary
 ## Requirements
 - Access to workflow creation guide
 - Read/write permissions for target workflow
 - Understanding of BMAD workflow types
--- a/.bmad/bmb/workflows/edit-workflow/checklist.md
+++ b/.bmad/bmb/workflows/edit-workflow/checklist.md
@ -1,70 +0,0 @@
 # Edit Workflow - Validation Checklist
 ## Pre-Edit Analysis
 - [ ] Target workflow.yaml file successfully loaded and parsed
 - [ ] All referenced workflow files identified and accessible
 - [ ] Workflow type correctly determined (document/action/interactive/autonomous/meta)
 - [ ] Best practices guide loaded and available for reference
 ## Edit Execution Quality
 - [ ] User clearly informed of identified issues with priority levels
 - [ ] Edit menu presented with all 8 standard options
 - [ ] Selected edit type matches the actual changes made
 - [ ] All proposed changes explained with reasoning before application
 ## File Integrity
 - [ ] All modified files maintain valid YAML/Markdown syntax
 - [ ] No placeholders like {TITLE} or {WORKFLOW_CODE} remain in edited files
 - [ ] File paths use proper variable substitution ({project-root}, {installed_path})
 - [ ] All file references resolve to actual paths
 ## Convention Compliance
 - [ ] Instructions.md contains critical workflow engine reference header
 - [ ] Instructions.md contains workflow.yaml processing reference header
 - [ ] All step numbers are sequential (1, 2, 3... or 1a, 1b, 2a...)
 - [ ] Each step has both n= attribute and goal= attribute
 - [ ] Variable names use snake_case consistently
 - [ ] Template variables (if any) match <template-output> tags exactly
 ## Instruction Quality
 - [ ] Each step has a single, clear goal stated
 - [ ] Instructions are specific with quantities (e.g., "3-5 items" not "several items")
 - [ ] Optional steps marked with optional="true" attribute
 - [ ] Repeating steps use proper repeat syntax (repeat="3" or repeat="until-complete")
 - [ ] User prompts use <ask> tags and wait for response
 - [ ] Actions use <action> tags for required operations
 ## Validation Criteria (if checklist.md exists)
 - [ ] All checklist items are measurable and specific
 - [ ] No vague criteria like "Good documentation" present
 - [ ] Checklist organized into logical sections
 - [ ] Each criterion can be objectively verified as true/false
 ## Change Documentation
 - [ ] All changes logged with description of what and why
 - [ ] Change summary includes list of modified files
 - [ ] Improvements clearly articulated in relation to best practices
 - [ ] Next steps or recommendations provided
 ## Post-Edit Verification
 - [ ] Edited workflow follows patterns from production examples
 - [ ] No functionality broken by the edits
 - [ ] Workflow ready for testing or production use
 - [ ] User given option to test the edited workflow
 ## Common Issues Resolved
 - [ ] Missing critical headers added if they were absent
 - [ ] Broken variable references fixed
 - [ ] Vague instructions made specific
 - [ ] Template-only workflows have template.md file
 - [ ] Action workflows have template: false in workflow.yaml
 - [ ] Step count reasonable (5-10 steps maximum unless justified)
--- a/.bmad/bmb/workflows/edit-workflow/instructions.md
+++ b/.bmad/bmb/workflows/edit-workflow/instructions.md
@ -1,342 +0,0 @@
 # Edit Workflow - Workflow Editor 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/bmb/workflows/edit-workflow/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
 <critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <workflow>
 <step n="1" goal="Load and deeply understand the target workflow">
 <ask>What is the path to the workflow you want to edit? (provide path to workflow.yaml or workflow directory)</ask>
 <action>Load the target workflow completely:
 - workflow.yaml configuration
 - instructions.md (if exists)
 - template.md (if exists)
 - checklist.md (if exists)
 - Any additional data files referenced
  </action>
 <action>Load ALL workflow documentation to inform understanding:
 - Workflow creation guide: {workflow_creation_guide}
 - Workflow execution engine: {workflow_execution_engine}
 - Study example workflows from: {project-root}/.bmad/bmm/workflows/
  </action>
 <action>Analyze the workflow deeply:
 - Identify workflow type (document, action, interactive, autonomous, meta)
 - Understand purpose and user journey
 - Map out step flow and logic
 - Check variable consistency across files
 - Evaluate instruction style (intent-based vs prescriptive)
 - Assess template structure (if applicable)
 - Review validation criteria
 - Identify config dependencies
 - Check for web bundle configuration
 - Evaluate against best practices from loaded guides
  </action>
 <action>Reflect understanding back to {user_name}:
 Present a warm, conversational summary adapted to the workflow's complexity:
 - What this workflow accomplishes (its purpose and value)
 - How it's structured (type, steps, interactive points)
 - What you notice (strengths, potential improvements, issues)
 - Your initial assessment based on best practices
 - How it fits in the larger BMAD ecosystem
 Be conversational and insightful. Help {user_name} see their workflow through your eyes.
 </action>
 <ask>Does this match your understanding of what this workflow should accomplish?</ask>
 <template-output>workflow_understanding</template-output>
 </step>
 <step n="2" goal="Discover improvement goals collaboratively">
 <critical>Understand WHAT the user wants to improve and WHY before diving into edits</critical>
 <action>Engage in collaborative discovery:
 Ask open-ended questions to understand their goals:
 - What prompted you to want to edit this workflow?
 - What feedback have you gotten from users running it?
 - Are there specific steps that feel clunky or confusing?
 - Is the workflow achieving its intended outcome?
 - Are there new capabilities you want to add?
 - Is the instruction style working well for your users?
 Listen for clues about:
 - User experience issues (confusing steps, unclear instructions)
 - Functional issues (broken references, missing validation)
 - Performance issues (too many steps, repetitive, tedious)
 - Maintainability issues (hard to update, bloated, inconsistent variables)
 - Instruction style mismatch (too prescriptive when should be adaptive, or vice versa)
 - Integration issues (doesn't work well with other workflows)
  </action>
 <action>Based on their responses and your analysis from step 1, identify improvement opportunities:
 Organize by priority and user goals:
 - CRITICAL issues blocking successful runs
 - IMPORTANT improvements enhancing user experience
 - NICE-TO-HAVE enhancements for polish
 Present these conversationally, explaining WHY each matters and HOW it would help.
 </action>
 <action>Assess instruction style fit:
 Based on the workflow's purpose and your analysis:
 - Is the current style (intent-based vs prescriptive) appropriate?
 - Would users benefit from more/less structure?
 - Are there steps that should be more adaptive?
 - Are there steps that need more specificity?
 Discuss style as part of improvement discovery, not as a separate concern.
 </action>
 <action>Collaborate on priorities:
 Don't just list options - discuss them:
 - "I noticed {{issue}} - this could make users feel {{problem}}. Want to address this?"
 - "The workflow could be more {{improvement}} which would help when {{use_case}}. Worth exploring?"
 - "Based on what you said about {{user_goal}}, we might want to {{suggestion}}. Thoughts?"
 Let the conversation flow naturally. Build a shared vision of what "better" looks like.
 </action>
 <template-output>improvement_goals</template-output>
 </step>
 <step n="3" goal="Facilitate improvements collaboratively" repeat="until-user-satisfied">
 <critical>Work iteratively - improve, review, refine. Never dump all changes at once.</critical>
 <action>For each improvement area, facilitate collaboratively:
 1. **Explain the current state and why it matters**
   - Show relevant sections of the workflow
   - Explain how it works now and implications
   - Connect to user's goals from step 2
 2. **Propose improvements with rationale**
   - Suggest specific changes that align with best practices
   - Explain WHY each change helps
   - Provide examples from the loaded guides when helpful
   - Show before/after comparisons for clarity
   - Reference the creation guide's patterns naturally
 3. **Collaborate on the approach**
   - Ask if the proposed change addresses their need
   - Invite modifications or alternative approaches
   - Explain tradeoffs when relevant
   - Adapt based on their feedback
 4. **Apply changes iteratively**
   - Make one focused improvement at a time
   - Show the updated section
   - Confirm it meets their expectation
   - Move to next improvement or refine current one
     </action>
 <action>Common improvement patterns to facilitate:
 **If refining instruction style:**
 - Discuss where the workflow feels too rigid or too loose
 - Identify steps that would benefit from intent-based approach
 - Identify steps that need prescriptive structure
 - Convert between styles thoughtfully, explaining tradeoffs
 - Show how each style serves the user differently
 - Test proposed changes by reading them aloud
 **If improving step flow:**
 - Walk through the user journey step by step
 - Identify friction points or redundancy
 - Propose streamlined flow
 - Consider where steps could merge or split
 - Ensure each step has clear goal and value
 - Check that repeat conditions make sense
 **If fixing variable consistency:**
 - Identify variables used across files
 - Find mismatches in naming or usage
 - Propose consistent naming scheme
 - Update all files to match
 - Verify variables are defined in workflow.yaml
 **If enhancing validation:**
 - Review current checklist (if exists)
 - Discuss what "done well" looks like
 - Make criteria specific and measurable
 - Add validation for new features
 - Remove outdated or vague criteria
 **If updating configuration:**
 - Review standard config pattern
 - Check if user context variables are needed
 - Ensure output_folder, user_name, communication_language are used appropriately
 - Add missing config dependencies
 - Clean up unused config fields
 **If adding/updating templates:**
 - Understand the document structure needed
 - Design template variables that match instruction outputs
 - Ensure variable names are descriptive snake_case
 - Include proper metadata headers
 - Test that all variables can be filled
 **If configuring web bundle:**
 - Identify all files the workflow depends on
 - Check for invoked workflows (must be included)
 - Verify paths are .bmad/-relative
 - Remove config_source dependencies
 - Build complete file list
 **If improving user interaction:**
 - Find places where <ask> could be more open-ended
 - Add educational context where users might be lost
 - Remove unnecessary confirmation steps
 - Make questions clearer and more purposeful
 - Balance guidance with user autonomy
  </action>
 <action>Throughout improvements, educate when helpful:
 Share insights from the guides naturally:
 - "The creation guide recommends {{pattern}} for workflows like this"
 - "Looking at examples in BMM, this type of step usually {{approach}}"
 - "The execution engine expects {{structure}} for this to work properly"
 Connect improvements to broader BMAD principles without being preachy.
 </action>
 <ask>After each significant change:
 - "Does this flow feel better for what you're trying to achieve?"
 - "Want to refine this further, or move to the next improvement?"
 - "How does this change affect the user experience?"
  </ask>
 <template-output>improvement_implementation</template-output>
 </step>
 <step n="4" goal="Validate improvements holistically">
 <action>Run comprehensive validation conversationally:
 Don't just check boxes - explain what you're validating and why it matters:
 - "Let me verify all file references resolve correctly..."
 - "Checking that variables are consistent across all files..."
 - "Making sure the step flow is logical and complete..."
 - "Validating template variables match instruction outputs..."
 - "Ensuring config dependencies are properly set up..."
  </action>
 <action>Load validation checklist: {installed_path}/checklist.md</action>
 <action>Check all items from checklist systematically</action>
 <check if="validation_issues_found">
  <action>Present issues conversationally:
 Explain what's wrong and implications:
 - "I found {{issue}} which could cause {{problem}} when users run this"
 - "The {{component}} needs {{fix}} because {{reason}}"
 Propose fixes immediately:
 - "I can fix this by {{solution}}. Should I?"
 - "We have a couple options here: {{option1}} or {{option2}}. Thoughts?"
  </action>
 <action>Fix approved issues and re-validate</action>
 </check>
 <check if="validation_passes">
  <action>Confirm success warmly:
 "Excellent! Everything validates cleanly:
 - All file references resolve
 - Variables are consistent throughout
 - Step flow is logical and complete
 - Template aligns with instructions (if applicable)
 - Config dependencies are set up correctly
 - Web bundle is complete (if applicable)
 Your workflow is in great shape."
 </action>
 </check>
 <template-output>validation_results</template-output>
 </step>
 <step n="5" goal="Review improvements and guide next steps">
 <action>Create a conversational summary of what improved:
 Tell the story of the transformation:
 - "We started with {{initial_state}}"
 - "You wanted to {{user_goals}}"
 - "We made these key improvements: {{changes_list}}"
 - "Now your workflow {{improved_capabilities}}"
 Highlight the impact:
 - "This means users will experience {{benefit}}"
 - "The workflow is now more {{quality}}"
 - "It follows best practices for {{patterns}}"
  </action>
 <action>Guide next steps based on changes made:
 If instruction style changed:
 - "Since we made the workflow more {{style}}, you might want to test it with a real user to see how it feels"
 If template was updated:
 - "The template now has {{new_variables}} - run the workflow to generate a sample document"
 If this is part of larger module work:
 - "This workflow is part of {{module}} - consider if other workflows need similar improvements"
 If web bundle was configured:
 - "The web bundle is now set up - you can test deploying this workflow standalone"
 Be a helpful guide to what comes next, not just a task completer.
 </action>
 <ask>Would you like to:
 - Test the edited workflow by running it
 - Edit another workflow
 - Make additional refinements to this one
 - Return to your module work
  </ask>
 <template-output>completion_summary</template-output>
 </step>
 </workflow>
--- a/.bmad/bmb/workflows/edit-workflow/workflow.yaml
+++ b/.bmad/bmb/workflows/edit-workflow/workflow.yaml
@ -1,27 +0,0 @@
 # Edit Workflow - Workflow Editor Configuration
 name: "edit-workflow"
 description: "Edit existing BMAD workflows while following all best practices and conventions"
 author: "BMad"
 # Critical variables load from config_source
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 # Required Data Files - Critical for understanding workflow conventions
 workflow_creation_guide: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md"
 workflow_execution_engine: "{project-root}/.bmad/core/tasks/workflow.xml"
 # Optional docs that can be used to understand the target workflow
 recommended_inputs:
  - target_workflow: "Path to the workflow.yaml file to edit"
  - workflow_examples: "{project-root}/.bmad/bmm/workflows/"
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/edit-workflow"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 standalone: true
 # Web bundle configuration
--- a/.bmad/bmb/workflows/module-brief/README.md
+++ b/.bmad/bmb/workflows/module-brief/README.md
@ -1,264 +0,0 @@
 # Module Brief Workflow
 ## Overview
 The Module Brief workflow creates comprehensive blueprints for building new BMAD modules using strategic analysis and creative vision. It serves as the essential planning phase that transforms initial ideas into detailed, actionable specifications ready for implementation with the create-module workflow.
 ## Key Features
 - **Strategic Module Planning** - Comprehensive analysis from concept to implementation roadmap
 - **Multi-Mode Operation** - Interactive, Express, and YOLO modes for different planning needs
 - **Creative Vision Development** - Guided process for innovative module concepts and unique value propositions
 - **Architecture Design** - Detailed agent and workflow ecosystem planning with interaction models
 - **User Journey Mapping** - Scenario-based validation ensuring practical usability
 - **Technical Planning** - Infrastructure requirements, dependencies, and complexity assessment
 - **Risk Assessment** - Proactive identification of challenges with mitigation strategies
 - **Implementation Roadmap** - Phased development plan with clear deliverables and timelines
 ## Usage
 ### Basic Invocation
 ```bash
 workflow module-brief
 ```
 ### With Brainstorming Input
 ```bash
 # If you have brainstorming results from previous sessions
 workflow module-brief --input brainstorming-session-2024-09-26.md
 ```
 ### Express Mode
 ```bash
 # For quick essential planning only
 workflow module-brief --mode express
 ```
 ### Configuration
 The workflow uses standard BMB configuration:
 - **output_folder**: Where the module brief will be saved
 - **user_name**: Brief author information
 - **communication_language**: Language for brief generation
 - **date**: Automatic timestamp for versioning
 ## Workflow Structure
 ### Files Included
 ```
 module-brief/
 ├── workflow.yaml           # Configuration and metadata
 ├── instructions.md         # Step-by-step execution guide
 ├── template.md            # Module brief document structure
 ├── checklist.md           # Validation criteria
 └── README.md              # This file
 ```
 ## Workflow Process
 ### Phase 1: Foundation and Context (Steps 1-3)
 **Mode Selection and Input Gathering**
 - Choose operational mode (Interactive, Express, YOLO)
 - Check for and optionally load existing brainstorming results
 - Gather background context and inspiration sources
 **Module Vision Development**
 - Define core problem the module solves
 - Identify target user audience and use cases
 - Establish unique value proposition and differentiators
 - Explore creative themes and personality concepts
 **Module Identity Establishment**
 - Generate module code (kebab-case) with multiple options
 - Create compelling, memorable module name
 - Select appropriate category (Domain-Specific, Creative, Technical, Business, Personal)
 - Define optional personality theme for consistent agent character
 ### Phase 2: Architecture Planning (Steps 4-5)
 **Agent Architecture Design**
 - Plan agent team composition and roles
 - Define agent archetypes (Orchestrator, Specialist, Helper, Creator, Analyzer)
 - Specify personality traits and communication styles
 - Map key capabilities and signature commands
 **Workflow Ecosystem Design**
 - Categorize workflows by purpose and complexity:
  - **Core Workflows**: Essential value-delivery functions (2-3)
  - **Feature Workflows**: Specialized capabilities (3-5)
  - **Utility Workflows**: Supporting operations (1-3)
 - Define input-process-output flows for each workflow
 - Assess complexity levels and implementation priorities
 ### Phase 3: Validation and User Experience (Steps 6-7)
 **User Journey Mapping**
 - Create detailed user scenarios and stories
 - Map step-by-step usage flows through the module
 - Validate end-to-end functionality and value delivery
 - Identify potential friction points and optimization opportunities
 **Technical Planning and Requirements**
 - Assess data requirements and storage needs
 - Map integration points with other modules and external systems
 - Evaluate technical complexity and resource requirements
 - Document dependencies and infrastructure needs
 ### Phase 4: Success Planning (Steps 8-9)
 **Success Metrics Definition**
 - Establish module success criteria and performance indicators
 - Define quality standards and reliability requirements
 - Create user experience goals and feedback mechanisms
 - Set measurable outcomes for module effectiveness
 **Development Roadmap Creation**
 - Design phased approach with MVP, Enhancement, and Polish phases
 - Define deliverables and timelines for each phase
 - Prioritize features and capabilities by value and complexity
 - Create clear milestones and success checkpoints
 ### Phase 5: Enhancement and Risk Management (Steps 10-12)
 **Creative Features and Special Touches** (Optional)
 - Design easter eggs and delightful user interactions
 - Plan module lore and thematic consistency
 - Add personality quirks and creative responses
 - Develop backstories and universe building
 **Risk Assessment and Mitigation**
 - Identify technical, usability, and scope risks
 - Develop mitigation strategies for each risk category
 - Plan contingency approaches for potential challenges
 - Document decision points and alternative paths
 **Final Review and Export Preparation**
 - Comprehensive review of all brief sections
 - Validation against quality and completeness criteria
 - Preparation for seamless handoff to create-module workflow
 - Export readiness confirmation with actionable specifications
 ## Output
 ### Generated Files
 - **Module Brief Document**: Comprehensive planning document at `{output_folder}/module-brief-{module_code}-{date}.md`
 - **Strategic Specifications**: Ready-to-implement blueprint for create-module workflow
 ### Output Structure
 The module brief contains detailed specifications across multiple sections:
 1. **Executive Summary** - Vision, category, complexity, target users
 2. **Module Identity** - Core concept, value proposition, personality theme
 3. **Agent Architecture** - Agent roster, roles, interaction models
 4. **Workflow Ecosystem** - Core, feature, and utility workflow specifications
 5. **User Scenarios** - Primary use cases, secondary scenarios, user journey
 6. **Technical Planning** - Data requirements, integrations, dependencies
 7. **Success Metrics** - Success criteria, quality standards, performance targets
 8. **Development Roadmap** - Phased implementation plan with deliverables
 9. **Creative Features** - Special touches, easter eggs, module lore
 10. **Risk Assessment** - Technical, usability, scope risks with mitigation
 11. **Implementation Notes** - Priority order, design decisions, open questions
 12. **Resources and References** - Inspiration sources, similar modules, technical references
 ## Requirements
 - **Creative Vision** - Initial module concept or problem domain
 - **Strategic Thinking** - Ability to plan architecture and user experience
 - **Brainstorming Results** (optional) - Previous ideation sessions enhance planning quality
 ## Best Practices
 ### Before Starting
 1. **Gather Inspiration** - Research similar tools, modules, and solutions in your domain
 2. **Run Brainstorming Session** - Use ideation techniques to generate initial concepts
 3. **Define Success Criteria** - Know what "successful module" means for your context
 ### During Execution
 1. **Think User-First** - Always consider the end user experience and value delivery
 2. **Be Specific** - Provide concrete examples and detailed specifications rather than abstractions
 3. **Validate Early** - Use user scenarios to test if the module concept actually works
 4. **Plan Iteratively** - Start with MVP and build complexity through phases
 ### After Completion
 1. **Use as Blueprint** - Feed the brief directly into create-module workflow for implementation
 2. **Review with Stakeholders** - Validate assumptions and gather feedback before building
 3. **Update as Needed** - Treat as living document that evolves with implementation learnings
 4. **Reference During Development** - Use as north star for design decisions and scope management
 ## Troubleshooting
 ### Common Issues
 **Issue**: Stuck on module concept or vision
 - **Solution**: Use creative prompts provided in the workflow
 - **Check**: Review existing modules for inspiration and patterns
 **Issue**: Agent or workflow architecture too complex
 - **Solution**: Focus on MVP first, plan enhancement phases for additional complexity
 - **Check**: Validate each component against user scenarios
 **Issue**: Technical requirements unclear
 - **Solution**: Research similar modules and their implementation approaches
 - **Check**: Consult with technical stakeholders early in planning
 **Issue**: Scope creep during planning
 - **Solution**: Use phased roadmap to defer non-essential features
 - **Check**: Regularly validate against core user scenarios and success criteria
 ## Customization
 To customize this workflow:
 1. **Modify Template Structure** - Update template.md to add new sections or reorganize content
 2. **Extend Creative Prompts** - Add domain-specific ideation techniques in instructions.md
 3. **Add Planning Tools** - Integrate additional analysis frameworks or planning methodologies
 4. **Customize Validation** - Enhance checklist.md with specific quality criteria for your context
 ## Version History
 - **v1.0.0** - Initial release
  - Comprehensive strategic module planning
  - Multi-mode operation (Interactive, Express, YOLO)
  - Creative vision and architecture design tools
  - User journey mapping and validation
  - Risk assessment and mitigation planning
 ## Support
 For issues or questions:
 - Review the workflow creation guide at `/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
 - Study existing module examples in `/.bmad/` for patterns and inspiration
 - Validate output using `checklist.md`
 - Consult module structure guide at `create-module/module-structure.md`
 ---
 _Part of the BMad Method v6 - BMB (Builder) Module_
--- a/.bmad/bmb/workflows/module-brief/checklist.md
+++ b/.bmad/bmb/workflows/module-brief/checklist.md
@ -1,116 +0,0 @@
 # Module Brief Validation Checklist
 ## Core Identity
 - [ ] Module code follows kebab-case convention
 - [ ] Module name is clear and memorable
 - [ ] Module category is identified
 - [ ] Target users are clearly defined
 - [ ] Unique value proposition is articulated
 ## Vision and Concept
 - [ ] Problem being solved is clearly stated
 - [ ] Solution approach is explained
 - [ ] Module scope is well-defined
 - [ ] Success criteria are measurable
 ## Agent Architecture
 - [ ] At least one agent is defined
 - [ ] Each agent has a clear role and purpose
 - [ ] Agent personalities are defined (if using personality themes)
 - [ ] Agent interactions are mapped (for multi-agent modules)
 - [ ] Key commands for each agent are listed
 ## Workflow Ecosystem
 - [ ] Core workflows (2-3) are identified
 - [ ] Each workflow has clear purpose
 - [ ] Workflow complexity is assessed
 - [ ] Input/output for workflows is defined
 - [ ] Workflow categories are logical
 ## User Experience
 - [ ] Primary use case is documented
 - [ ] User scenarios demonstrate value
 - [ ] User journey is realistic
 - [ ] Learning curve is considered
 - [ ] User feedback mechanism planned
 ## Technical Planning
 - [ ] Data requirements are identified
 - [ ] Integration points are mapped
 - [ ] Dependencies are listed
 - [ ] Technical complexity is assessed
 - [ ] Performance requirements stated
 ## Development Roadmap
 - [ ] Phase 1 MVP is clearly scoped
 - [ ] Phase 2 enhancements are outlined
 - [ ] Phase 3 polish items listed
 - [ ] Timeline estimates provided
 - [ ] Deliverables are specific
 ## Risk Management
 - [ ] Technical risks identified
 - [ ] Usability risks considered
 - [ ] Scope risks acknowledged
 - [ ] Mitigation strategies provided
 - [ ] Open questions documented
 ## Creative Elements (Optional)
 - [ ] Personality theme is consistent (if used)
 - [ ] Special features add value
 - [ ] Module feels cohesive
 - [ ] Fun elements don't compromise functionality
 ## Documentation Quality
 - [ ] All sections have content (no empty placeholders)
 - [ ] Writing is clear and concise
 - [ ] Technical terms are explained
 - [ ] Examples are provided where helpful
 - [ ] Next steps are actionable
 ## Implementation Readiness
 - [ ] Brief provides enough detail for create-module workflow
 - [ ] Agent specifications sufficient for create-agent workflow
 - [ ] Workflow descriptions ready for create-workflow
 - [ ] Resource requirements are clear
 - [ ] Success metrics are measurable
 ## Final Validation
 - [ ] Module concept is viable
 - [ ] Scope is achievable
 - [ ] Value is clear
 - [ ] Brief is complete
 - [ ] Ready for development
 ## Issues Found
 ### Critical Issues
 <!-- Must be fixed before proceeding to build -->
 ### Recommendations
 <!-- Suggested improvements -->
 ### Nice-to-Haves
 <!-- Optional enhancements -->
 ---
 **Validation Complete:** ⬜ Yes / ⬜ With Issues / ⬜ Needs Revision
 **Validated By:** {name}
 **Date:** {date}
--- a/.bmad/bmb/workflows/module-brief/instructions.md
+++ b/.bmad/bmb/workflows/module-brief/instructions.md
@ -1,267 +0,0 @@
 # Module Brief 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/bmb/workflows/module-brief/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the module brief creation process</critical>
 <workflow>
 <step n="1" goal="Setup and context gathering">
 <action>Ask the user which mode they prefer:</action>
 1. **Interactive Mode** - Work through each section collaboratively with detailed questions
 2. **Express Mode** - Quick essential questions only
 3. **YOLO Mode** (#yolo) - Generate complete draft based on minimal input
 <action>Check for available inputs:</action>
 - Brainstorming results from previous sessions
 - Existing module ideas or notes
 - Similar modules for inspiration
 <action>If brainstorming results exist, offer to load and incorporate them</action>
 </step>
 <step n="2" goal="Module concept and vision">
 Ask the user to describe their module idea. Probe for:
 - What problem does this module solve?
 - Who would use this module?
 - What makes this module exciting or unique?
 - Any inspiring examples or similar tools?
 If they're stuck, offer creative prompts:
 - "Imagine you're a [role], what tools would make your life easier?"
 - "What repetitive tasks could be automated with agents?"
 - "What domain expertise could be captured in workflows?"
 <template-output>module_vision</template-output>
 </step>
 <step n="3" goal="Define module identity">
 Based on the vision, work with user to define:
 **Module Code** (kebab-case):
 - Suggest 2-3 options based on their description
 - Ensure it's memorable and descriptive
 **Module Name** (friendly):
 - Creative, engaging name that captures the essence
 **Module Category:**
 - Domain-Specific (legal, medical, finance)
 - Creative (writing, gaming, music)
 - Technical (devops, testing, architecture)
 - Business (project management, marketing)
 - Personal (productivity, learning)
 **Personality Theme** (optional but fun!):
 - Should the module have a consistent personality across agents?
 - Star Trek crew? Fantasy party? Corporate team? Reality show cast?
 <template-output>module_identity</template-output>
 </step>
 <step n="4" goal="Agent architecture planning">
 <action>Help user envision their agent team</action>
 For each agent, capture:
 - **Role**: What's their specialty?
 - **Personality**: How do they communicate? (reference communication styles)
 - **Key Capabilities**: What can they do?
 - **Signature Commands**: 2-3 main commands
 Suggest agent archetypes based on module type:
 - The Orchestrator (manages other agents)
 - The Specialist (deep expertise)
 - The Helper (utility functions)
 - The Creator (generates content)
 - The Analyzer (processes and evaluates)
 <template-output>agent_architecture</template-output>
 </step>
 <step n="5" goal="Workflow ecosystem design">
 <action>Map out the workflow landscape</action>
 Categorize workflows:
 **Core Workflows** (2-3 essential ones):
 - The primary value-delivery workflows
 - What users will use most often
 **Feature Workflows** (3-5 specialized):
 - Specific capabilities
 - Advanced features
 **Utility Workflows** (1-3 supporting):
 - Setup, configuration
 - Maintenance, cleanup
 For each workflow, define:
 - Purpose (one sentence)
 - Input → Process → Output
 - Complexity (simple/standard/complex)
 <template-output>workflow_ecosystem</template-output>
 </step>
 <step n="6" goal="User journey and scenarios">
 <action>Create usage scenarios to validate the design</action>
 Write 2-3 user stories:
 "As a [user type], I want to [goal], so that [outcome]"
 Then walk through how they'd use the module:
 1. They load [agent]
 2. They run [command/workflow]
 3. They get [result]
 4. This helps them [achievement]
 This validates the module makes sense end-to-end.
 <template-output>user_scenarios</template-output>
 </step>
 <step n="7" goal="Technical and resource planning">
 Assess technical requirements:
 **Data Requirements:**
 - What data/files does the module need?
 - Any external APIs or services?
 - Storage or state management needs?
 **Integration Points:**
 - Other BMAD modules it might use
 - External tools or platforms
 - Import/export formats
 **Complexity Assessment:**
 - Simple (standalone, no dependencies)
 - Standard (some integrations, moderate complexity)
 - Complex (multiple systems, advanced features)
 <template-output>technical_planning</template-output>
 </step>
 <step n="8" goal="Success metrics and validation">
 Define what success looks like:
 **Module Success Criteria:**
 - What indicates the module is working well?
 - How will users measure value?
 - What feedback mechanisms?
 **Quality Standards:**
 - Performance expectations
 - Reliability requirements
 - User experience goals
 <template-output>success_metrics</template-output>
 </step>
 <step n="9" goal="Development roadmap">
 Create a phased approach:
 **Phase 1 - MVP (Minimum Viable Module):**
 - 1 primary agent
 - 2-3 core workflows
 - Basic functionality
 **Phase 2 - Enhancement:**
 - Additional agents
 - More workflows
 - Refined features
 **Phase 3 - Polish:**
 - Advanced features
 - Optimizations
 - Nice-to-haves
 <template-output>development_roadmap</template-output>
 </step>
 <step n="10" goal="Creative flourishes and special features" optional="true">
 <action>If user wants to add special touches:</action>
 **Easter Eggs:**
 - Hidden commands or responses
 - Fun interactions between agents
 **Delighters:**
 - Unexpected helpful features
 - Personality quirks
 - Creative responses
 **Module Lore:**
 - Backstory for agents
 - Thematic elements
 - Consistent universe
 <template-output>creative_features</template-output>
 </step>
 <step n="11" goal="Risk assessment and mitigation">
 Identify potential challenges:
 **Technical Risks:**
 - Complex integrations
 - Performance concerns
 - Dependency issues
 **Usability Risks:**
 - Learning curve
 - Complexity creep
 - User confusion
 **Scope Risks:**
 - Feature bloat
 - Timeline expansion
 - Resource constraints
 For each risk, note mitigation strategy.
 <template-output>risk_assessment</template-output>
 </step>
 <step n="12" goal="Final review and export readiness">
 <action>Review all sections with {user_name}</action>
 <action>Ensure module brief is ready for create-module workflow</action>
 <ask>Would {user_name} like to:
 1. Proceed directly to create-module workflow
 2. Save and refine later
 3. Generate additional planning documents
   </ask>
 <action>Inform {user_name} in {communication_language} that this brief can be fed directly into create-module workflow</action>
 <template-output>final_brief</template-output>
 </step>
 </workflow>
--- a/.bmad/bmb/workflows/module-brief/template.md
+++ b/.bmad/bmb/workflows/module-brief/template.md
@ -1,275 +0,0 @@
 # Module Brief: {{module_name}}
 **Date:** {{date}}
 **Author:** {{user_name}}
 **Module Code:** {{module_code}}
 **Status:** Ready for Development
 ---
 ## Executive Summary
 {{module_vision}}
 **Module Category:** {{module_category}}
 **Complexity Level:** {{complexity_level}}
 **Target Users:** {{target_users}}
 ---
 ## Module Identity
 ### Core Concept
 {{module_identity}}
 ### Unique Value Proposition
 What makes this module special:
 {{unique_value}}
 ### Personality Theme
 {{personality_theme}}
 ---
 ## Agent Architecture
 {{agent_architecture}}
 ### Agent Roster
 {{agent_roster}}
 ### Agent Interaction Model
 How agents work together:
 {{agent_interactions}}
 ---
 ## Workflow Ecosystem
 {{workflow_ecosystem}}
 ### Core Workflows
 Essential functionality that delivers primary value:
 {{core_workflows}}
 ### Feature Workflows
 Specialized capabilities that enhance the module:
 {{feature_workflows}}
 ### Utility Workflows
 Supporting operations and maintenance:
 {{utility_workflows}}
 ---
 ## User Scenarios
 ### Primary Use Case
 {{primary_scenario}}
 ### Secondary Use Cases
 {{secondary_scenarios}}
 ### User Journey
 Step-by-step walkthrough of typical usage:
 {{user_journey}}
 ---
 ## Technical Planning
 ### Data Requirements
 {{data_requirements}}
 ### Integration Points
 {{integration_points}}
 ### Dependencies
 {{dependencies}}
 ### Technical Complexity Assessment
 {{technical_planning}}
 ---
 ## Success Metrics
 ### Module Success Criteria
 How we'll know the module is successful:
 {{success_criteria}}
 ### Quality Standards
 {{quality_standards}}
 ### Performance Targets
 {{performance_targets}}
 ---
 ## Development Roadmap
 ### Phase 1: MVP (Minimum Viable Module)
 **Timeline:** {{phase1_timeline}}
 {{phase1_components}}
 **Deliverables:**
 {{phase1_deliverables}}
 ### Phase 2: Enhancement
 **Timeline:** {{phase2_timeline}}
 {{phase2_components}}
 **Deliverables:**
 {{phase2_deliverables}}
 ### Phase 3: Polish and Optimization
 **Timeline:** {{phase3_timeline}}
 {{phase3_components}}
 **Deliverables:**
 {{phase3_deliverables}}
 ---
 ## Creative Features
 ### Special Touches
 {{creative_features}}
 ### Easter Eggs and Delighters
 {{easter_eggs}}
 ### Module Lore and Theming
 {{module_lore}}
 ---
 ## Risk Assessment
 ### Technical Risks
 {{technical_risks}}
 ### Usability Risks
 {{usability_risks}}
 ### Scope Risks
 {{scope_risks}}
 ### Mitigation Strategies
 {{risk_mitigation}}
 ---
 ## Implementation Notes
 ### Priority Order
 1. {{priority_1}}
 2. {{priority_2}}
 3. {{priority_3}}
 ### Key Design Decisions
 {{design_decisions}}
 ### Open Questions
 {{open_questions}}
 ---
 ## Resources and References
 ### Inspiration Sources
 {{inspiration_sources}}
 ### Similar Modules
 {{similar_modules}}
 ### Technical References
 {{technical_references}}
 ---
 ## Appendices
 ### A. Detailed Agent Specifications
 {{detailed_agent_specs}}
 ### B. Workflow Detailed Designs
 {{detailed_workflow_specs}}
 ### C. Data Structures and Schemas
 {{data_schemas}}
 ### D. Integration Specifications
 {{integration_specs}}
 ---
 ## Next Steps
 1. **Review this brief** with stakeholders
 2. **Run create-module workflow** using this brief as input
 3. **Create first agent** using create-agent workflow
 4. **Develop initial workflows** using create-workflow
 5. **Test MVP** with target users
 ---
 _This Module Brief is ready to be fed directly into the create-module workflow for scaffolding and implementation._
 **Module Viability Score:** {{viability_score}}/10
 **Estimated Development Effort:** {{effort_estimate}}
 **Confidence Level:** {{confidence_level}}
 ---
 **Approval for Development:**
 - [ ] Concept Approved
 - [ ] Scope Defined
 - [ ] Resources Available
 - [ ] Ready to Build
 ---
 _Generated on {{date}} by {{user_name}} using the BMAD Method Module Brief workflow_
--- a/.bmad/bmb/workflows/module-brief/workflow.yaml
+++ b/.bmad/bmb/workflows/module-brief/workflow.yaml
@ -1,29 +0,0 @@
 # Module Brief Workflow Configuration
 name: module-brief
 description: "Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision"
 author: "BMad Builder"
 # Critical variables
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 # Optional input docs that enhance module planning
 recommended_inputs:
  - brainstorming_results: "{output_folder}/brainstorming-*.md"
  - existing_modules: "{project-root}/.bmad/"
  - module_examples: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
 # Module path and component files
 installed_path: "{project-root}/.bmad/bmb/workflows/module-brief"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/module-brief-{{module_code}}-{{date}}.md"
 standalone: true
 # Web bundle configuration
--- a/.bmad/bmb/workflows/redoc/README.md
+++ b/.bmad/bmb/workflows/redoc/README.md
@ -1,87 +0,0 @@
 # ReDoc - Reverse-Tree Documentation Engine
 **Type:** Autonomous Action Workflow
 **Module:** BMad Builder (bmb)
 ## Purpose
 ReDoc is an intelligent documentation maintenance system for BMAD modules, workflows, and agents. It uses a reverse-tree approach (leaf folders first, then parent folders) to systematically generate and update README.md files with technical writer quality output.
 The workflow understands BMAD conventions deeply and focuses documentation on distinctive features rather than explaining standard patterns, resulting in succinct, precise technical documentation.
 ## Key Features
 - **Reverse-Tree Processing**: Documents from deepest folders up to module root, allowing child documentation to inform parent summaries
 - **Convention-Aware**: Loads BMAD architecture patterns and only documents unique/distinctive aspects
 - **Scalability**: Automatically creates catalog documents (WORKFLOWS-CATALOG.md, AGENTS-CATALOG.md) for massive folders (>10 items)
 - **Diff-Aware**: Tracks `last-redoc-date` frontmatter to enable change detection since last run
 - **Autonomous**: Runs without user checkpoints unless clarification is genuinely required
 - **Comprehensive**: Reads ALL files completely before generating documentation (no partial reads)
 ## Usage
 Invoke with a target path:
 ```
 workflow redoc
 ```
 When prompted, provide one of:
 - **Module path**: `.bmad/bmm` (documents entire module: root, workflows, agents)
 - **Workflows folder**: `.bmad/bmm/workflows` (documents all workflows)
 - **Agents folder**: `.bmad/bmm/agents` (documents all agents)
 - **Single workflow**: `.bmad/bmm/workflows/product-brief` (documents one workflow)
 - **Single agent**: `.bmad/bmm/agents/prd-agent.md` (documents one agent)
 ## Inputs
 ### Required
 - **target_path**: Path to module, folder, or specific component to document
 ### Knowledge Base (Auto-loaded)
 - agent-architecture.md
 - agent-command-patterns.md
 - agent-types.md
 - module-structure.md
 - workflow-creation-guide.md
 ## Outputs
 ### Created/Updated Files
 - **README.md**: At each documented level (workflow folders, agent folders, module root)
 - **Catalog files**: WORKFLOWS-CATALOG.md, AGENTS-CATALOG.md (for massive folders)
 - **Frontmatter**: All READMEs include `last-redoc-date: <timestamp>`
 ### Summary Report
 - Documentation coverage statistics
 - List of files created/updated
 - Any items requiring manual review
 ## Workflow Steps
 1. **Initialize**: Load BMAD conventions and validate target
 2. **Analyze Structure**: Build reverse-tree execution plan
 3. **Process Leaves**: Document individual workflows/agents (deepest first)
 4. **Process Folders**: Document workflow/agent collections with categorization
 5. **Process Root**: Document module overview with links and highlights
 6. **Validate**: Verify completeness and generate report
 7. **Diff Analysis** (optional): Show changes since last redoc
 8. **Complete**: Report success and suggest next steps
 ## Technical Details
 - **Execution**: Autonomous with minimal user interaction
 - **Quality**: Technical writer standards - succinct, precise, professional
 - **Context-Aware**: Uses BMAD convention knowledge to highlight only distinctive features
 - **Scalable**: Handles folders of any size with intelligent catalog creation
 ## Next Steps After Running
 1. Review generated documentation for accuracy
 2. If documenting a subfolder, run redoc on parent module to update references
 3. Commit documentation updates with meaningful message
--- a/.bmad/bmb/workflows/redoc/checklist.md
+++ b/.bmad/bmb/workflows/redoc/checklist.md
@ -1,99 +0,0 @@
 # ReDoc Workflow Validation Checklist
 ## Initialization and Setup
 - [ ] All BMAD convention documents loaded and understood
 - [ ] Target path validated and exists
 - [ ] Target type correctly identified (module/workflow/agent/folder)
 - [ ] Documentation execution plan created with reverse-tree order
 ## File Analysis
 - [ ] All files in target scope read completely (no offset/limit usage)
 - [ ] Existing README.md files detected and last-redoc-date parsed
 - [ ] Massive folders (>10 items) identified for catalog document creation
 - [ ] Documentation depth levels calculated correctly
 ## Leaf-Level Documentation (Workflows)
 - [ ] Each workflow's ALL files read: workflow.yaml, instructions.md, template.md, checklist.md
 - [ ] README.md includes frontmatter with current last-redoc-date
 - [ ] Description is 2-4 paragraphs of technical writer quality
 - [ ] Focuses on DISTINCTIVE features, not BMAD boilerplate conventions
 - [ ] Includes "Usage" section with invocation command
 - [ ] Includes "Inputs" and "Outputs" sections where applicable
 - [ ] Succinct and precise language used throughout
 ## Leaf-Level Documentation (Agents)
 - [ ] Each agent file read completely including XML structure, commands, persona
 - [ ] README.md includes frontmatter with current last-redoc-date
 - [ ] Description is 1-3 paragraphs of technical writer quality
 - [ ] Lists all available commands clearly
 - [ ] Explains when to use this agent
 - [ ] Highlights unique capabilities vs standard agent patterns
 ## Mid-Level Documentation (Folders)
 - [ ] All child README.md files read before generating folder README
 - [ ] Workflows categorized logically if massive folder (>10 items)
 - [ ] Agents categorized by type if massive folder (>10 items)
 - [ ] Catalog documents (WORKFLOWS-CATALOG.md, AGENTS-CATALOG.md) created for massive folders
 - [ ] Catalog documents include frontmatter with last-redoc-date
 - [ ] Folder README.md references catalog if one exists
 - [ ] Folder README.md is succinct (1-2 paragraphs + listings/links)
 - [ ] Notable/commonly-used items highlighted
 ## Root Module Documentation
 - [ ] Module config.yaml read and understood
 - [ ] Workflows and agents folder READMEs read before creating root README
 - [ ] Root README includes frontmatter with current last-redoc-date
 - [ ] Module purpose clearly stated in 2-3 sentences
 - [ ] Links to /workflows/README.md and /agents/README.md included
 - [ ] 2-3 key workflows mentioned with context
 - [ ] 2-3 key agents mentioned with context
 - [ ] Configuration section highlights UNIQUE settings only
 - [ ] Usage section explains invocation patterns
 - [ ] BMAD convention knowledge applied (describes only distinctive aspects)
 ## Quality Standards
 - [ ] All documentation uses proper BMAD terminology
 - [ ] Technical writer quality: clear, concise, professional
 - [ ] No placeholder text or generic descriptions remain
 - [ ] All links are valid and correctly formatted
 - [ ] Frontmatter syntax is correct and dates are current
 - [ ] No redundant explanation of standard BMAD patterns
 ## Validation and Reporting
 - [ ] All planned documentation items created/updated
 - [ ] Frontmatter dates verified as current across all files
 - [ ] File paths and internal links validated
 - [ ] Summary report generated with counts and coverage
 - [ ] Files skipped (if any) documented with reasons
 ## Git Diff Analysis (Optional Step)
 - [ ] last-redoc-date timestamps extracted correctly
 - [ ] Git log queried for changes since last redoc
 - [ ] Modified files identified and reported
 - [ ] Findings presented clearly to user
 ## Final Validation
 - [ ] Documentation Coverage
  - All README.md files in scope created/updated
  - Catalog documents created where needed
  - No documentation gaps identified
 - [ ] Execution Quality
  - Reverse-tree order followed (leaf → root)
  - Autonomous execution (minimal user prompts)
  - Only clarification questions asked when truly necessary
 - [ ] Output Quality
  - Technical precision maintained throughout
  - Succinct descriptions (no verbose explanations)
  - Professional documentation standards met
--- a/.bmad/bmb/workflows/redoc/instructions.md
+++ b/.bmad/bmb/workflows/redoc/instructions.md
@ -1,265 +0,0 @@
 # ReDoc 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}/src/modules/bmb/workflows/redoc/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the documentation process</critical>
 <critical>This is an AUTONOMOUS workflow - minimize user interaction unless clarification is absolutely required</critical>
 <critical>IMPORTANT: Process ONE document at a time to avoid token limits. Each README should be created individually, not batched.</critical>
 <critical>When using Task tool with sub-agents: Only request ONE workflow or agent documentation per invocation to prevent token overflow.</critical>
 <workflow>
 <step n="1" goal="Load BMAD conventions and initialize">
 <action>Load ALL BMAD convention documents from {bmad_conventions}:
 - agent_architecture.md - Understand agent XML structure and patterns
 - agent_command_patterns.md - Command syntax and activation patterns
 - agent_types.md - Standard agent categories and purposes
 - module_structure.md - Module organization and folder conventions
 - workflow_guide.md - Workflow structure and best practices
 </action>
 <action>Internalize these conventions so you can:
 - Recognize standard patterns vs unique implementations
 - Describe only what's distinctive about each component
 - Use proper terminology consistently
 - Write with technical precision
  </action>
 <action>Get target path from user:
 - Ask: "What do you want to document? (module path, workflow path, agent path, or folder path)"
 - Store as {{target_path}}
  </action>
 <action>Validate target path exists and determine target type:
 - Module root (contains config.yaml, /workflows, /agents folders)
 - Workflows folder (contains multiple workflow folders)
 - Agents folder (contains multiple agent .md files)
 - Single workflow folder (contains workflow.yaml)
 - Single agent file (.md)
  </action>
 <action>Store target type as {{target_type}} for conditional processing</action>
 </step>
 <step n="2" goal="Analyze directory structure and existing documentation">
 <action>Build complete tree structure of {{target_path}} using Glob and file system tools</action>
 <action>Identify all documentation points:
 - List all folders requiring README.md files
 - Detect existing README.md files
 - Parse frontmatter from existing READMEs to extract last-redoc-date
 - Calculate documentation depth (how many levels deep)
  </action>
 <action>Create documentation map with execution order (deepest → shallowest):
 - Level 0 (deepest): Individual workflow folders, individual agent files
 - Level 1: /workflows folder, /agents folder
 - Level 2 (root): Module root README.md
  </action>
 <action>Detect "massive folders" requiring child catalog documents:
 - Threshold: >10 items or complex categorization needed
 - Mark folders for catalog document creation (e.g., WORKFLOWS-CATALOG.md, AGENTS-CATALOG.md)
  </action>
 <critical>Store execution order as {{doc_execution_plan}} - this ensures reverse-tree processing</critical>
 </step>
 <step n="3" goal="Process leaf-level documentation" repeat="for-each-leaf-item">
 <critical>TOKEN LIMIT WARNING: Process ONE item at a time to prevent token overflow issues.</critical>
 <critical>If using Task tool with sub-agents: NEVER batch multiple workflows/agents in a single invocation.</critical>
 <critical>Each README creation should be a separate operation with its own file save.</critical>
 <critical>Sequential processing is MANDATORY - do not attempt parallel documentation generation.</critical>
 <action>For each individual workflow folder in execution plan (PROCESS ONE AT A TIME):
 1. Read ALL files completely:
   - workflow.yaml (metadata, purpose, configuration)
   - instructions.md (step structure, goals)
   - template.md (output structure) if exists
   - checklist.md (validation criteria) if exists
   - Any supporting data files
 2. Synthesize understanding:
   - Core purpose and use case
   - Input requirements
   - Output produced
   - Unique characteristics (vs standard BMAD workflow patterns)
   - Key steps or special features
 3. Generate/update README.md:
   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
   - Write 2-4 paragraph technical description
   - Include "Usage" section with invocation command
   - Include "Inputs" section if applicable
   - Include "Outputs" section
   - Be succinct and precise - technical writer quality
   - Focus on DISTINCTIVE features, not boilerplate
 4. Save README.md to workflow folder
 <critical>If multiple workflows need documentation, process them SEQUENTIALLY not in parallel. Each workflow gets its own complete processing cycle.</critical>
 </action>
 <action>For each individual agent file in execution plan (PROCESS ONE AT A TIME):
 1. Read agent definition file completely:
   - XML structure and metadata
   - Commands and their purposes
   - Activation patterns
   - Persona and communication style
   - Critical actions and workflows invoked
 2. Synthesize understanding:
   - Agent purpose and role
   - Available commands
   - When to use this agent
   - Unique capabilities
 3. Generate/update README.md (or agent-name-README.md if in shared folder):
   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
   - Write 1-3 paragraph technical description
   - Include "Commands" section listing available commands
   - Include "Usage" section
   - Focus on distinctive features
 4. Save README.md
   </action>
 <action if="clarification needed about purpose or unique features">Ask user briefly, then continue</action>
 </step>
 <step n="4" goal="Process mid-level folder documentation" if="target_type requires folder docs">
 <action>For /workflows folder:
 1. Read ALL workflow README.md files created in Step 3
 2. Categorize workflows by purpose/type if folder is massive (>10 workflows):
   - Document generation workflows
   - Action workflows
   - Meta-workflows
   - Interactive workflows
 3. If massive folder detected:
   - Create WORKFLOWS-CATALOG.md with categorized listings
   - Each entry: workflow name, 1-sentence description, link to folder
   - Add frontmatter with last-redoc-date
 4. Generate/update /workflows/README.md:
   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
   - High-level summary of workflow collection
   - If catalog exists: reference it
   - If not massive: list all workflows with brief descriptions and links
   - Highlight notable or commonly-used workflows
   - Keep succinct (1-2 paragraphs + list)
 5. Save README.md
   </action>
 <action>For /agents folder:
 1. Read ALL agent README.md files
 2. Categorize agents by type if massive folder (>10 agents):
   - Task agents
   - Meta agents
   - Specialized agents
   - Utility agents
 3. If massive folder detected:
   - Create AGENTS-CATALOG.md with categorized listings
   - Each entry: agent name, 1-sentence description, link
   - Add frontmatter with last-redoc-date
 4. Generate/update /agents/README.md:
   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
   - High-level summary of agent collection
   - If catalog exists: reference it
   - If not massive: list all agents with brief descriptions
   - Highlight key agents and their purposes
   - Keep succinct
 5. Save README.md
   </action>
   </step>
 <step n="5" goal="Process root module documentation" if="target_type is module root">
 <action>For module root README.md:
 1. Read module config.yaml for metadata and configuration
 2. Read /workflows/README.md and /agents/README.md created in Step 4
 3. Identify module's unique purpose within BMAD ecosystem
 4. Generate/update module README.md:
   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
   Structure:
   - # Module Name
   - **Purpose**: 2-3 sentence high-level module purpose
   - **Overview**: 1-2 paragraphs describing what this module provides
   - ## Workflows
     - Link to /workflows/README.md with 1-sentence summary
     - Mention count and highlight 2-3 key workflows
   - ## Agents
     - Link to /agents/README.md with 1-sentence summary
     - Mention count and highlight 2-3 key agents
   - ## Configuration
     - Notable config.yaml settings if unique/important
     - Reference paths and conventions
   - ## Usage
     - How to invoke workflows or agents from this module
     - Prerequisites if any
   Focus on UNIQUE aspects using BMAD convention knowledge:
   - Don't explain standard BMAD patterns
   - Highlight what makes THIS module distinctive
   - Use proper BMAD terminology
 5. Save README.md to module root
   </action>
   </step>
 <step n="6" goal="Validation and summary report">
 <action>Verify all planned documentation was created/updated:
 - Check each item in {{doc_execution_plan}}
 - Confirm frontmatter dates are current
 - Validate file paths and links
 </action>
 <action>Generate summary report showing:
 - Target documented: {{target_path}}
 - Target type: {{target_type}}
 - Documentation files created/updated (count and list)
 - Any catalog files created
 - Files skipped or requiring manual review (if any)
 - Coverage: X% of items documented
 - Processing notes: Confirm sequential processing was used to avoid token limits
  </action>
 <action>Display summary to user</action>
 </step>
 <step n="7" goal="Optional git diff analysis" optional="true">
 <ask>Would you like to see what changed since the last redoc run? [y/n]</ask>
 <action if="user_response == 'y'">
 For each README with last-redoc-date frontmatter:
 1. Extract last-redoc-date timestamp
 2. Use git log to find files modified since that date in the documented folder
 3. Highlight files that changed but may need documentation updates
 4. Report findings to user
 </action>
 </step>
 <step n="8" goal="Completion">
 <action>Confirm to {user_name} in {communication_language} that autonomous workflow execution is complete</action>
 <action>Provide path to all updated documentation</action>
 <action>Suggest next steps if needed</action>
 </step>
 </workflow>
--- a/.bmad/bmb/workflows/redoc/workflow.yaml
+++ b/.bmad/bmb/workflows/redoc/workflow.yaml
@ -1,32 +0,0 @@
 # ReDoc - Reverse-Tree Documentation Engine
 name: "redoc"
 description: "Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output."
 author: "BMad"
 # Critical variables
 config_source: "{project-root}/.bmad/bmb/config.yaml"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 # Required knowledge base - BMAD conventions and patterns
 bmad_conventions:
  agent_architecture: "{project-root}/src/modules/bmb/workflows/create-agent/agent-architecture.md"
  agent_command_patterns: "{project-root}/src/modules/bmb/workflows/create-agent/agent-command-patterns.md"
  agent_types: "{project-root}/src/modules/bmb/workflows/create-agent/agent-types.md"
  module_structure: "{project-root}/src/modules/bmb/workflows/create-module/module-structure.md"
  workflow_guide: "{project-root}/src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md"
 # Runtime inputs
 target_path: "" # User specifies: module path, workflow path, agent path, or folder path
 # Module path and component files
 installed_path: "{project-root}/src/modules/bmb/workflows/redoc"
 template: false # Action workflow - updates files in place
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Configuration
 autonomous: true # Runs without user checkpoints unless clarification needed
 standalone: true
 # Web bundle configuration
--- a/.bmad/core/agents/bmad-master.md
+++ b/.bmad/core/agents/bmad-master.md
@ -1,72 +0,0 @@
 ---
 name: 'bmad master'
 description: 'BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator'
 ---
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 ```xml
 <agent id=".bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon="🧙">
 <activation critical="MANDATORY">
  <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}/core/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>
  <step n="4">Load into memory {project-root}/.bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</step>
  <step n="5">Remember the users name is {user_name}</step>
  <step n="6">ALWAYS communicate in {communication_language}</step>
  <step n="7">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="8">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
      match</step>
  <step n="9">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="10">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>
  <menu-handlers>
      <handlers>
      <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>
  <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>
    </handlers>
  </menu-handlers>
  <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>
 </activation>
  <persona>
    <role>Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator</role>
    <identity>Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.</identity>
    <communication_style>Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.</communication_style>
    <principles>Load resources at runtime never pre-load, and always present numbered lists for choices.</principles>
  </persona>
  <menu>
    <item cmd="*help">Show numbered menu</item>
    <item cmd="*list-tasks" action="list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv">List Available Tasks</item>
    <item cmd="*list-workflows" action="list all workflows from {project-root}/.bmad/_cfg/workflow-manifest.csv">List Workflows</item>
    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</item>
    <item cmd="*exit">Exit with confirmation</item>
  </menu>
 </agent>
 ```
--- a/.bmad/core/agents/bmad-web-orchestrator.agent.xml
+++ b/.bmad/core/agents/bmad-web-orchestrator.agent.xml
@ -1,113 +0,0 @@
 <agent id="{bmad_folder}/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
  <activation critical="MANDATORY">
    <step n="1">Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle</step>
    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable
      by type
      and id</step>
    <step n="3">Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below</step>
    <step n="4">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
    <step n="5">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="6">When executing a menu item: Check menu-handlers section below for UNIVERSAL handler instructions that apply to ALL agents</step>
    <menu-handlers critical="UNIVERSAL_FOR_ALL_AGENTS">
      <extract>workflow, exec, tmpl, data, action, validate-workflow</extract>
      <handlers>
        <handler type="workflow">
          When menu item has: workflow="workflow-id"
          1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
          2. CRITICAL: Always LOAD {bmad_folder}/core/tasks/workflow.xml if referenced
          3. Execute the workflow content precisely following all steps
          4. Save outputs after completing EACH workflow step (never batch)
          5. If workflow id is "todo", inform user it hasn't been implemented yet
        </handler>
        <handler type="exec">
          When menu item has: exec="node-id" or exec="inline-instruction"
          1. If value looks like a path/id → Find and execute node with that id
          2. If value is text → Execute as direct instruction
          3. Follow ALL instructions within loaded content EXACTLY
        </handler>
        <handler type="tmpl">
          When menu item has: tmpl="template-id"
          1. Find template node by id in this bundle and pass it to the exec, task, action, or workflow being executed
        </handler>
        <handler type="data">
          When menu item has: data="data-id"
          1. Find data node by id in this bundle
          2. Parse according to node type (json/yaml/xml/csv)
          3. Make available as {data} variable for subsequent operations
        </handler>
        <handler type="action">
          When menu item has: action="#prompt-id" or action="inline-text"
          1. If starts with # → Find prompt with matching id in current agent
          2. Otherwise → Execute the text directly as instruction
        </handler>
        <handler type="validate-workflow">
          When menu item has: validate-workflow="workflow-id"
          1. MUST LOAD {bmad_folder}/core/tasks/validate-workflow.xml
          2. Execute all validation instructions from that file
          3. Check workflow's validation property for schema
          4. Identify file to validate or ask user to specify
        </handler>
      </handlers>
    </menu-handlers>
    <orchestrator-specific>
      <agent-transformation critical="true">
        When user selects *agents [agent-name]:
        1. Find agent XML node with matching name/id in this bundle
        2. Announce transformation: "Transforming into [agent name]... 🎭"
        3. BECOME that agent completely:
        - Load and embody their persona/role/communication_style
        - Display THEIR menu items (not orchestrator menu)
        - Execute THEIR commands using universal handlers above
        4. Stay as that agent until user types *exit
        5. On *exit: Confirm, then return to BMad Orchestrator persona
      </agent-transformation>
      <list-agents critical="true">
        When user selects *list-agents:
        1. Scan all agent nodes in this bundle
        2. Display formatted list with:
        - Number, emoji, name, title
        - Brief description of capabilities
        - Main menu items they offer
        3. Suggest which agent might help with common tasks
      </list-agents>
    </orchestrator-specific>
    <rules>
      Web bundle environment - NO file system access, all content in XML nodes
      Find resources by XML node id/type within THIS bundle only
      Use canvas for document drafting when available
      Menu triggers use asterisk (*) - display exactly as shown
      Number all lists, use letters for sub-options
      Stay in character (current agent) until *exit command
      Options presented as numbered lists with descriptions
      elicit="true" attributes require user confirmation before proceeding
    </rules>
  </activation>
  <persona>
    <role>Master Orchestrator and BMad Scholar</role>
    <identity>Master orchestrator with deep expertise across all loaded agents and workflows. Technical brilliance balanced with
      approachable communication.</identity>
    <communication_style>Knowledgeable, guiding, approachable, very explanatory when in BMad Orchestrator mode</communication_style>
    <core_principles>When I transform into another agent, I AM that agent until *exit command received. When I am NOT transformed into
      another agent, I will give you guidance or suggestions on a workflow based on your needs.</core_principles>
  </persona>
  <menu>
    <item cmd="*help">Show numbered command list</item>
    <item cmd="*list-agents">List all available agents with their capabilities</item>
    <item cmd="*agents [agent-name]">Transform into a specific agent</item>
    <item cmd="*party-mode" workflow="{bmad_folder}/core/workflows/party-mode/workflow.yaml">Enter group chat with all agents
      simultaneously</item>
    <item cmd="*advanced-elicitation" task="{bmad_folder}/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
    <item cmd="*exit">Exit current session</item>
  </menu>
 </agent>
--- a/.bmad/core/config.yaml
+++ b/.bmad/core/config.yaml
@ -1,11 +0,0 @@
 # CORE Module Configuration
 # Generated by BMAD installer
 # Version: 6.0.0-alpha.9
 # Date: 2025-11-14T13:17:23.685Z
 bmad_folder: .bmad
 user_name: BMad
 communication_language: English
 document_output_language: English
 output_folder: "{project-root}/docs"
 install_user_docs: true
--- a/.bmad/core/tasks/adv-elicit-methods.csv
+++ b/.bmad/core/tasks/adv-elicit-methods.csv
@ -1,39 +0,0 @@
 category,method_name,description,output_pattern
 advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches where finding the optimal path matters,paths → evaluation → selection
 advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns in complex multi-factor situations,nodes → connections → patterns
 advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency in lengthy analyses,context → thread → synthesis
 advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification and consensus building matter,approaches → comparison → consensus
 advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving strategies,current → analysis → optimization
 advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making tasks,model → planning → strategy
 collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
 collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
 competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions through adversarial thinking,defense → attack → hardening
 core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - essential when content needs to match specific reader capabilities,audience → adjustments → refined content
 core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts needing polish and enhancement,strengths/weaknesses → improvements → refined version
 core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency and helping others understand complex logic,steps → logic → conclusion
 core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving seemingly impossible problems,assumptions → truths → new approach
 core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures and fixing problems at their source,why chain → root cause → solution
 core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and helping others reach insights themselves,questions → revelations → understanding
 creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding how to reach specific endpoints,end state → steps backward → path forward
 creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and creative exploration,scenarios → implications → insights
 creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation and improvement,S→C→A→M→P→E→R
 learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding and excellent for knowledge transfer,complex → simple → gaps → mastery
 learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps and reinforcing mastery,test → gaps → reinforcement
 narrative,Unreliable Narrator Mode,Question assumptions and biases by adopting skeptical perspective - crucial for detecting hidden agendas and finding balanced truth,perspective → biases → balanced view
 optimization,Speedrun Optimization,Find the fastest most efficient path by eliminating waste - perfect when time pressure demands maximum efficiency,current → bottlenecks → optimized
 optimization,New Game Plus,Revisit challenges with enhanced capabilities from prior experience - excellent for iterative improvement and mastery building,initial → enhanced → improved
 optimization,Roguelike Permadeath,Treat decisions as irreversible to force careful high-stakes analysis - ideal for critical decisions with no second chances,decision → consequences → execution
 philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging and theory selection,options → simplification → selection
 philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and making difficult ethical decisions,dilemma → analysis → decision
 quantum,Observer Effect Consideration,Analyze how the act of measurement changes what's being measured - important for understanding metrics impact and self-aware systems,unmeasured → observation → impact
 retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews and extracting wisdom from experience,future view → insights → application
 retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for knowledge transfer and continuous improvement,experience → lessons → actions
 risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
 risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink and building robust solutions,assumptions → challenges → strengthening
 risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
 risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
 scientific,Peer Review Simulation,Apply rigorous academic evaluation standards - ensures quality through methodology review and critical assessment,methodology → analysis → recommendations
 scientific,Reproducibility Check,Verify results can be replicated independently - fundamental for reliability and scientific validity,method → replication → validation
 structural,Dependency Mapping,Visualize interconnections to understand requirements and impacts - essential for complex systems and integration planning,components → dependencies → impacts
 structural,Information Architecture Review,Optimize organization and hierarchy for better user experience - crucial for fixing navigation and findability problems,current → pain points → restructure
 structural,Skeleton of Thought,Create structure first then expand branches in parallel - efficient for generating long content quickly with good organization,skeleton → branches → integration
--- a/.bmad/core/tasks/advanced-elicitation-methods.csv
+++ b/.bmad/core/tasks/advanced-elicitation-methods.csv
@ -1,21 +0,0 @@
 category,method_name,description,output_pattern
 core,Five Whys,Drill down to root causes by asking 'why' iteratively. Each answer becomes the basis for the next question. Particularly effective for problem analysis and understanding system failures.,problem → why1 → why2 → why3 → why4 → why5 → root cause
 core,First Principles,Break down complex problems into fundamental truths and rebuild from there. Question assumptions and reconstruct understanding from basic principles.,assumptions → deconstruction → fundamentals → reconstruction → solution
 structural,SWOT Analysis,Evaluate internal and external factors through Strengths Weaknesses Opportunities and Threats. Provides balanced strategic perspective.,strengths → weaknesses → opportunities → threats → strategic insights
 structural,Mind Mapping,Create visual representations of interconnected concepts branching from central idea. Reveals relationships and patterns not immediately obvious.,central concept → primary branches → secondary branches → connections → insights
 risk,Pre-mortem Analysis,Imagine project has failed and work backwards to identify potential failure points. Proactive risk identification through hypothetical failure scenarios.,future failure → contributing factors → warning signs → preventive measures
 risk,Risk Matrix,Evaluate risks by probability and impact to prioritize mitigation efforts. Visual framework for systematic risk assessment.,risk identification → probability assessment → impact analysis → prioritization → mitigation
 creative,SCAMPER,Systematic creative thinking through Substitute Combine Adapt Modify Put to other uses Eliminate Reverse. Generates innovative alternatives.,substitute → combine → adapt → modify → other uses → eliminate → reverse
 creative,Six Thinking Hats,Explore topic from six perspectives: facts (white) emotions (red) caution (black) optimism (yellow) creativity (green) process (blue).,facts → emotions → risks → benefits → alternatives → synthesis
 analytical,Root Cause Analysis,Systematic investigation to identify fundamental causes rather than symptoms. Uses various techniques to drill down to core issues.,symptoms → immediate causes → intermediate causes → root causes → solutions
 analytical,Fishbone Diagram,Visual cause-and-effect analysis organizing potential causes into categories. Also known as Ishikawa diagram for systematic problem analysis.,problem statement → major categories → potential causes → sub-causes → prioritization
 strategic,PESTLE Analysis,Examine Political Economic Social Technological Legal Environmental factors. Comprehensive external environment assessment.,political → economic → social → technological → legal → environmental → implications
 strategic,Value Chain Analysis,Examine activities that create value from raw materials to end customer. Identifies competitive advantages and improvement opportunities.,primary activities → support activities → linkages → value creation → optimization
 process,Journey Mapping,Visualize end-to-end experience identifying touchpoints pain points and opportunities. Understanding through customer or user perspective.,stages → touchpoints → actions → emotions → pain points → opportunities
 process,Service Blueprint,Map service delivery showing frontstage backstage and support processes. Reveals service complexity and improvement areas.,customer actions → frontstage → backstage → support processes → improvement areas
 stakeholder,Stakeholder Mapping,Identify and analyze stakeholders by interest and influence. Strategic approach to stakeholder engagement.,identification → interest analysis → influence assessment → engagement strategy
 stakeholder,Empathy Map,Understand stakeholder perspectives through what they think feel see say do. Deep understanding of user needs and motivations.,thinks → feels → sees → says → does → pains → gains
 decision,Decision Matrix,Evaluate options against weighted criteria for objective decision making. Systematic comparison of alternatives.,criteria definition → weighting → scoring → calculation → ranking → selection
 decision,Cost-Benefit Analysis,Compare costs against benefits to evaluate decision viability. Quantitative approach to decision validation.,cost identification → benefit identification → quantification → comparison → recommendation
 validation,Devil's Advocate,Challenge assumptions and proposals by arguing opposing viewpoint. Stress-testing through deliberate opposition.,proposal → counter-arguments → weaknesses → blind spots → strengthened proposal
 validation,Red Team Analysis,Simulate adversarial perspective to identify vulnerabilities. Security and robustness through adversarial thinking.,current approach → adversarial view → attack vectors → vulnerabilities → countermeasures
--- a/.bmad/core/tasks/advanced-elicitation.xml
+++ b/.bmad/core/tasks/advanced-elicitation.xml
@ -1,106 +0,0 @@
 <task id="{bmad_folder}/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
  methods="{project-root}/{bmad_folder}/core/tasks/advanced-elicitation-methods.csv"
  agent-party="{project-root}/{bmad_folder}/_cfg/agent-manifest.csv">
  <llm critical="true">
    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
    <i>DO NOT skip steps or change the sequence</i>
    <i>HALT immediately when halt-conditions are met</i>
    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
  </llm>
  <integration description="When called from workflow">
    <desc>When called during template workflow processing:</desc>
    <i>1. Receive or review the current section content that was just generated or</i>
    <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
    <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
    <i>4. The enhanced content replaces the original section content in the output document</i>
  </integration>
  <flow>
    <step n="1" title="Method Registry Loading">
      <action>Load and read {{methods}} and {{agent-party}}</action>
      <csv-structure>
        <i>category: Method grouping (core, structural, risk, etc.)</i>
        <i>method_name: Display name for the method</i>
        <i>description: Rich explanation of what the method does, when to use it, and why it's valuable</i>
        <i>output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")</i>
      </csv-structure>
      <context-analysis>
        <i>Use conversation history</i>
        <i>Analyze: content type, complexity, stakeholder needs, risk level, and creative potential</i>
      </context-analysis>
      <smart-selection>
        <i>1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential</i>
        <i>2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV</i>
        <i>3. Select 5 methods: Choose methods that best match the context based on their descriptions</i>
        <i>4. Balance approach: Include mix of foundational and specialized techniques as appropriate</i>
      </smart-selection>
    </step>
    <step n="2" title="Present Options and Handle Responses">
      <format>
        **Advanced Elicitation Options**
        Choose a number (1-5), r to shuffle, or x to proceed:
        1. [Method Name]
        2. [Method Name]
        3. [Method Name]
        4. [Method Name]
        5. [Method Name]
        r. Reshuffle the list with 5 new options
        x. Proceed / No Further Actions
      </format>
      <response-handling>
        <case n="1-5">
          <i>Execute the selected method using its description from the CSV</i>
          <i>Adapt the method's complexity and output format based on the current context</i>
          <i>Apply the method creatively to the current section content being enhanced</i>
          <i>Display the enhanced version showing what the method revealed or improved</i>
          <i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
          <i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
            follow the instructions given by the user.</i>
          <i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
        </case>
        <case n="r">
          <i>Select 5 different methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
        </case>
        <case n="x">
          <i>Complete elicitation and proceed</i>
          <i>Return the fully enhanced content back to create-doc.md</i>
          <i>The enhanced content becomes the final version for that section</i>
          <i>Signal completion back to create-doc.md to continue with next section</i>
        </case>
        <case n="direct-feedback">
          <i>Apply changes to current section content and re-present choices</i>
        </case>
        <case n="multiple-numbers">
          <i>Execute methods in sequence on the content, then re-offer choices</i>
        </case>
      </response-handling>
    </step>
    <step n="3" title="Execution Guidelines">
      <i>Method execution: Use the description from CSV to understand and apply each method</i>
      <i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
      <i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
      <i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
      <i>Be concise: Focus on actionable insights</i>
      <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from create-doc)</i>
      <i>Identify personas: For multi-persona methods, clearly identify viewpoints</i>
      <i>Critical loop behavior: Always re-offer the 1-5,r,x choices after each method execution</i>
      <i>Continue until user selects 'x' to proceed with enhanced content</i>
      <i>Each method application builds upon previous enhancements</i>
      <i>Content preservation: Track all enhancements made during elicitation</i>
      <i>Iterative enhancement: Each selected method (1-5) should:</i>
      <i> 1. Apply to the current enhanced version of the content</i>
      <i> 2. Show the improvements made</i>
      <i> 3. Return to the prompt for additional elicitations or completion</i>
    </step>
  </flow>
 </task>
--- a/.bmad/core/tasks/index-docs.xml
+++ b/.bmad/core/tasks/index-docs.xml
@ -1,65 +0,0 @@
 <task id="{bmad_folder}/core/tasks/index-docs" name="Index Docs"
  description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
  <llm critical="true">
    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
    <i>DO NOT skip steps or change the sequence</i>
    <i>HALT immediately when halt-conditions are met</i>
    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
  </llm>
  <flow>
    <step n="1" title="Scan Directory">
      <i>List all files and subdirectories in the target location</i>
    </step>
    <step n="2" title="Group Content">
      <i>Organize files by type, purpose, or subdirectory</i>
    </step>
    <step n="3" title="Generate Descriptions">
      <i>Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the
        filename</i>
    </step>
    <step n="4" title="Create/Update Index">
      <i>Write or update index.md with organized file listings</i>
    </step>
  </flow>
  <output-format>
    <example>
      # Directory Index
      ## Files
      - **[filename.ext](./filename.ext)** - Brief description
      - **[another-file.ext](./another-file.ext)** - Brief description
      ## Subdirectories
      ### subfolder/
      - **[file1.ext](./subfolder/file1.ext)** - Brief description
      - **[file2.ext](./subfolder/file2.ext)** - Brief description
      ### another-folder/
      - **[file3.ext](./another-folder/file3.ext)** - Brief description
    </example>
  </output-format>
  <halt-conditions critical="true">
    <i>HALT if target directory does not exist or is inaccessible</i>
    <i>HALT if user does not have write permissions to create index.md</i>
  </halt-conditions>
  <validation>
    <i>Use relative paths starting with ./</i>
    <i>Group similar files together</i>
    <i>Read file contents to generate accurate descriptions - don't guess from filenames</i>
    <i>Keep descriptions concise but informative (3-10 words)</i>
    <i>Sort alphabetically within groups</i>
    <i>Skip hidden files (starting with .) unless specified</i>
  </validation>
 </task>
--- a/.bmad/core/tasks/validate-workflow.xml
+++ b/.bmad/core/tasks/validate-workflow.xml
@ -1,89 +0,0 @@
 <task id="{bmad_folder}/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
  <objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
  <inputs>
    <input name="workflow" desc="Workflow path containing checklist.md" />
    <input name="checklist" desc="Checklist to validate against (defaults to workflow's checklist.md)" />
    <input name="document" desc="Document to validate (ask user if not specified)" />
  </inputs>
  <flow>
    <step n="1" title="Setup">
      <action>If checklist not provided, load checklist.md from workflow location</action>
      <action>Try to fuzzy match for files similar to the input document name or if user did not provide the document. If document not
        provided or unsure, ask user: "Which document should I validate?"</action>
      <action>Load both the checklist and document</action>
    </step>
    <step n="2" title="Validate" critical="true">
      <mandate>For EVERY checklist item, WITHOUT SKIPPING ANY:</mandate>
      <for-each-item>
        <action>Read requirement carefully</action>
        <action>Search document for evidence along with any ancillary loaded documents or artifacts (quotes with line numbers)</action>
        <action>Analyze deeply - look for explicit AND implied coverage</action>
        <mark-as>
          ✓ PASS - Requirement fully met (provide evidence)
          ⚠ PARTIAL - Some coverage but incomplete (explain gaps)
          ✗ FAIL - Not met or severely deficient (explain why)
          ➖ N/A - Not applicable (explain reason)
        </mark-as>
      </for-each-item>
      <critical>DO NOT SKIP ANY SECTIONS OR ITEMS</critical>
    </step>
    <step n="3" title="Generate Report">
      <action>Create validation-report-{timestamp}.md in document's folder</action>
      <report-format>
        # Validation Report
        **Document:** {document-path}
        **Checklist:** {checklist-path}
        **Date:** {timestamp}
        ## Summary
        - Overall: X/Y passed (Z%)
        - Critical Issues: {count}
        ## Section Results
        ### {Section Name}
        Pass Rate: X/Y (Z%)
        {For each item:}
        [MARK] {Item description}
        Evidence: {Quote with line# or explanation}
        {If FAIL/PARTIAL: Impact: {why this matters}}
        ## Failed Items
        {All ✗ items with recommendations}
        ## Partial Items
        {All ⚠ items with what's missing}
        ## Recommendations
        1. Must Fix: {critical failures}
        2. Should Improve: {important gaps}
        3. Consider: {minor improvements}
      </report-format>
    </step>
    <step n="4" title="Summary for User">
      <action>Present section-by-section summary</action>
      <action>Highlight all critical issues</action>
      <action>Provide path to saved report</action>
      <action>HALT - do not continue unless user asks</action>
    </step>
  </flow>
  <critical-rules>
    <rule>NEVER skip sections - validate EVERYTHING</rule>
    <rule>ALWAYS provide evidence (quotes + line numbers) for marks</rule>
    <rule>Think deeply about each requirement - don't rush</rule>
    <rule>Save report to document's folder automatically</rule>
    <rule>HALT after presenting summary - wait for user</rule>
  </critical-rules>
 </task>
--- a/.bmad/core/tasks/workflow.xml
+++ b/.bmad/core/tasks/workflow.xml
@ -1,270 +0,0 @@
 <task id="{bmad_folder}/core/tasks/workflow.xml" name="Execute Workflow">
  <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
  <llm critical="true">
    <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
    <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
    <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>
    <mandate>Save to template output file after EVERY "template-output" tag</mandate>
    <mandate>NEVER delegate a step - YOU are responsible for every steps execution</mandate>
  </llm>
  <WORKFLOW-RULES critical="true">
    <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
    <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
    <rule n="3">Template-output tags: Save content → Show user → Get approval before continuing</rule>
    <rule n="4">User must approve each major section before continuing UNLESS #yolo mode active</rule>
  </WORKFLOW-RULES>
  <flow>
    <step n="1" title="Load and Initialize Workflow">
      <substep n="1a" title="Load Configuration and Resolve Variables">
        <action>Read workflow.yaml from provided path</action>
        <mandate>Load config_source (REQUIRED for all modules)</mandate>
        <phase n="1">Load external config from config_source path</phase>
        <phase n="2">Resolve all {config_source}: references with values from config</phase>
        <phase n="3">Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path})</phase>
        <phase n="4">Ask user for input of any variables that are still unknown</phase>
      </substep>
      <substep n="1b" title="Load Required Components">
        <mandate>Instructions: Read COMPLETE file from path OR embedded list (REQUIRED)</mandate>
        <check>If template path → Read COMPLETE template file</check>
        <check>If validation path → Note path for later loading when needed</check>
        <check>If template: false → Mark as action-workflow (else template-workflow)</check>
        <note>Data files (csv, json) → Store paths only, load on-demand when instructions reference them</note>
      </substep>
      <substep n="1c" title="Initialize Output" if="template-workflow">
        <action>Resolve default_output_file path with all variables and {{date}}</action>
        <action>Create output directory if doesn't exist</action>
        <action>If template-workflow → Write template to output file with placeholders</action>
        <action>If action-workflow → Skip file creation</action>
      </substep>
    </step>
    <step n="2" title="Process Each Instruction Step">
      <iterate>For each step in instructions:</iterate>
      <substep n="2a" title="Handle Step Attributes">
        <check>If optional="true" and NOT #yolo → Ask user to include</check>
        <check>If if="condition" → Evaluate condition</check>
        <check>If for-each="item" → Repeat step for each item</check>
        <check>If repeat="n" → Repeat step n times</check>
      </substep>
      <substep n="2b" title="Execute Step Content">
        <action>Process step instructions (markdown or XML tags)</action>
        <action>Replace {{variables}} with values (ask user if unknown)</action>
        <execute-tags>
          <tag>action xml tag → Perform the action</tag>
          <tag>check if="condition" xml tag → Conditional block wrapping actions (requires closing &lt;/check&gt;)</tag>
          <tag>ask xml tag → Prompt user and WAIT for response</tag>
          <tag>invoke-workflow xml tag → Execute another workflow with given inputs</tag>
          <tag>invoke-task xml tag → Execute specified task</tag>
          <tag>invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section</tag>
          <tag>goto step="x" → Jump to specified step</tag>
        </execute-tags>
      </substep>
      <substep n="2c" title="Handle template-output Tags">
        <if tag="template-output">
          <mandate>Generate content for this section</mandate>
          <mandate>Save to file (Write first time, Edit subsequent)</mandate>
          <action>Show checkpoint separator: ━━━━━━━━━━━━━━━━━━━━━━━</action>
          <action>Display generated content</action>
          <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
              response="a">
              <action>Start the advanced elicitation workflow {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</action>
            </if>
            <if
              response="c">
              <action>Continue to next step</action>
            </if>
            <if response="p">
              <action>Start the party-mode workflow {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml</action>
            </if>
            <if
              response="y">
              <action>Enter #yolo mode for the rest of the workflow</action>
            </if>
          </ask>
        </if>
      </substep>
      <substep n="2d" title="Step Completion">
        <check>If no special tags and NOT #yolo:</check>
        <ask>Continue to next step? (y/n/edit)</ask>
      </substep>
    </step>
    <step n="3" title="Completion">
      <check>If checklist exists → Run validation</check>
      <check>If template: false → Confirm actions completed</check>
      <check>Else → Confirm document saved to output path</check>
      <action>Report workflow completion</action>
    </step>
  </flow>
  <execution-modes>
    <mode name="normal">Full user interaction at all decision points</mode>
    <mode name="#yolo">Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by
      simulating the remaining discussions with an simulated expert user</mode>
  </execution-modes>
  <supported-tags desc="Instructions can use these tags">
    <structural>
      <tag>step n="X" goal="..." - Define step with number and goal</tag>
      <tag>optional="true" - Step can be skipped</tag>
      <tag>if="condition" - Conditional execution</tag>
      <tag>for-each="collection" - Iterate over items</tag>
      <tag>repeat="n" - Repeat n times</tag>
    </structural>
    <execution>
      <tag>action - Required action to perform</tag>
      <tag>action if="condition" - Single conditional action (inline, no closing tag needed)</tag>
      <tag>check if="condition"&gt;...&lt;/check&gt; - Conditional block wrapping multiple items (closing tag required)</tag>
      <tag>ask - Get user input (wait for response)</tag>
      <tag>goto - Jump to another step</tag>
      <tag>invoke-workflow - Call another workflow</tag>
      <tag>invoke-task - Call a task</tag>
      <tag>invoke-protocol - Execute a reusable protocol (e.g., discover_inputs)</tag>
    </execution>
    <output>
      <tag>template-output - Save content checkpoint</tag>
      <tag>critical - Cannot be skipped</tag>
      <tag>example - Show example output</tag>
    </output>
  </supported-tags>
  <conditional-execution-patterns desc="When to use each pattern">
    <pattern type="single-action">
      <use-case>One action with a condition</use-case>
      <syntax>&lt;action if="condition"&gt;Do something&lt;/action&gt;</syntax>
      <example>&lt;action if="file exists"&gt;Load the file&lt;/action&gt;</example>
      <rationale>Cleaner and more concise for single items</rationale>
    </pattern>
    <pattern type="multi-action-block">
      <use-case>Multiple actions/tags under same condition</use-case>
      <syntax>&lt;check if="condition"&gt;
        &lt;action&gt;First action&lt;/action&gt;
        &lt;action&gt;Second action&lt;/action&gt;
        &lt;/check&gt;</syntax>
      <example>&lt;check if="validation fails"&gt;
        &lt;action&gt;Log error&lt;/action&gt;
        &lt;goto step="1"&gt;Retry&lt;/goto&gt;
        &lt;/check&gt;</example>
      <rationale>Explicit scope boundaries prevent ambiguity</rationale>
    </pattern>
    <pattern type="nested-conditions">
      <use-case>Else/alternative branches</use-case>
      <syntax>&lt;check if="condition A"&gt;...&lt;/check&gt;
        &lt;check if="else"&gt;...&lt;/check&gt;</syntax>
      <rationale>Clear branching logic with explicit blocks</rationale>
    </pattern>
  </conditional-execution-patterns>
  <protocols desc="Reusable workflow protocols that can be invoked via invoke-protocol tag">
    <protocol name="discover_inputs" desc="Smart file discovery and loading based on input_file_patterns">
      <objective>Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration</objective>
      <critical>Only execute if workflow.yaml contains input_file_patterns section</critical>
      <flow>
        <step n="1" title="Parse Input File Patterns">
          <action>Read input_file_patterns from loaded workflow.yaml</action>
          <action>For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present</action>
        </step>
        <step n="2" title="Load Files Using Smart Strategies">
          <iterate>For each pattern in input_file_patterns:</iterate>
          <substep n="2a" title="Try Whole Document First">
            <action>Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md")</action>
            <check if="matches found">
              <action>Load ALL matching files completely (no offset/limit)</action>
              <action>Store content in variable: {pattern_name_content} (e.g., {prd_content})</action>
              <action>Mark pattern as RESOLVED, skip to next pattern</action>
            </check>
          </substep>
          <substep n="2b" title="Try Sharded Document if Whole Not Found">
            <check if="no whole matches AND sharded pattern exists">
              <action>Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified)</action>
              <strategy name="FULL_LOAD">
                <desc>Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs</desc>
                <action>Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md")</action>
                <action>Load EVERY matching file completely</action>
                <action>Concatenate content in logical order (index.md first if exists, then alphabetical)</action>
                <action>Store in variable: {pattern_name_content}</action>
              </strategy>
              <strategy name="SELECTIVE_LOAD">
                <desc>Load specific shard using template variable - example: used for epics with {{epic_num}}</desc>
                <action>Check for template variables in sharded_single pattern (e.g., {{epic_num}})</action>
                <action>If variable undefined, ask user for value OR infer from context</action>
                <action>Resolve template to specific file path</action>
                <action>Load that specific file</action>
                <action>Store in variable: {pattern_name_content}</action>
              </strategy>
              <strategy name="INDEX_GUIDED">
                <desc>Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs</desc>
                <mandate>DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance</mandate>
                <action>Load index.md from sharded directory</action>
                <action>Parse table of contents, links, section headers</action>
                <action>Analyze workflow's purpose and objective</action>
                <action>Identify which linked/referenced documents are likely relevant</action>
                <example>If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth
                  docs, consider deployment docs, skip payment</example>
                <action>Load all identified relevant documents</action>
                <action>Store combined content in variable: {pattern_name_content}</action>
                <note>When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info</note>
              </strategy>
            </check>
          </substep>
          <substep n="2c" title="Handle Not Found">
            <check if="no matches for whole OR sharded">
              <action>Set {pattern_name_content} to empty string</action>
              <action>Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide)</action>
            </check>
          </substep>
        </step>
        <step n="3" title="Report Discovery Results">
          <action>List all loaded content variables with file counts</action>
          <example>
            ✓ Loaded {prd_content} from 1 file: PRD.md
            ✓ Loaded {architecture_content} from 5 sharded files: architecture/index.md, architecture/system-design.md, ...
            ✓ Loaded {epics_content} from selective load: epics/epic-3.md
            ○ No ux_design files found
          </example>
          <note>This gives workflow transparency into what context is available</note>
        </step>
      </flow>
      <usage-in-instructions>
        <example desc="Typical usage in workflow instructions.md">
          &lt;step n="0" goal="Discover and load project context"&gt;
          &lt;invoke-protocol name="discover_inputs" /&gt;
          &lt;/step&gt;
          &lt;step n="1" goal="Analyze requirements"&gt;
          &lt;action&gt;Review {prd_content} for functional requirements&lt;/action&gt;
          &lt;action&gt;Cross-reference with {architecture_content} for technical constraints&lt;/action&gt;
          &lt;/step&gt;
        </example>
      </usage-in-instructions>
    </protocol>
  </protocols>
  <llm final="true">
    <mandate>This is the complete workflow execution engine</mandate>
    <mandate>You MUST Follow instructions exactly as written and maintain conversation context between steps</mandate>
    <mandate>If confused, re-read this task, the workflow yaml, and any yaml indicated files</mandate>
  </llm>
 </task>
--- a/.bmad/core/tools/shard-doc.xml
+++ b/.bmad/core/tools/shard-doc.xml
@ -1,109 +0,0 @@
 <tool id="{bmad_folder}/core/tasks/shard-doc" name="Shard Document"
  description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
  standalone="true">
  <objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
  <llm critical="true">
    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
    <i>DO NOT skip steps or change the sequence</i>
    <i>HALT immediately when halt-conditions are met</i>
    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
  </llm>
  <critical-context>
    <i>Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index</i>
  </critical-context>
  <flow>
    <step n="1" title="Get Source Document">
      <action>Ask user for the source document path if not provided already</action>
      <action>Verify file exists and is accessible</action>
      <action>Verify file is markdown format (.md extension)</action>
      <action if="file not found or not markdown">HALT with error message</action>
    </step>
    <step n="2" title="Get Destination Folder">
      <action>Determine default destination: same location as source file, folder named after source file without .md extension</action>
      <action>Example: /path/to/architecture.md → /path/to/architecture/</action>
      <action>Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path)</action>
      <action if="user accepts default">Use the suggested destination path</action>
      <action if="user provides custom path">Use the custom destination path</action>
      <action>Verify destination folder exists or can be created</action>
      <action>Check write permissions for destination</action>
      <action if="permission denied">HALT with error message</action>
    </step>
    <step n="3" title="Execute Sharding">
      <action>Inform user that sharding is beginning</action>
      <action>Execute command: `npx @kayvan/markdown-tree-parser explode [source-document] [destination-folder]`</action>
      <action>Capture command output and any errors</action>
      <action if="command fails">HALT and display error to user</action>
    </step>
    <step n="4" title="Verify Output">
      <action>Check that destination folder contains sharded files</action>
      <action>Verify index.md was created in destination folder</action>
      <action>Count the number of files created</action>
      <action if="no files created">HALT with error message</action>
    </step>
    <step n="5" title="Report Completion">
      <action>Display completion report to user including:</action>
      <i>- Source document path and name</i>
      <i>- Destination folder path</i>
      <i>- Number of section files created</i>
      <i>- Confirmation that index.md was created</i>
      <i>- Any tool output or warnings</i>
      <action>Inform user that sharding completed successfully</action>
    </step>
    <step n="6" title="Handle Original Document">
      <critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
      <action>Present user with options for the original document:</action>
      <ask>What would you like to do with the original document `[source-document-name]`?
 Options:
 [d] Delete - Remove the original (recommended - shards can always be recombined)
 [m] Move to archive - Move original to a backup/archive location
 [k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
 Your choice (d/m/k):</ask>
      <check if="user selects 'd' (delete)">
        <action>Delete the original source document file</action>
        <action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
        <note>The document can be reconstructed from shards by concatenating all section files in order</note>
      </check>
      <check if="user selects 'm' (move)">
        <action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
        <action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
        <ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
        <action if="user accepts default">Use default archive path</action>
        <action if="user provides custom path">Use custom archive path</action>
        <action>Create archive directory if it doesn't exist</action>
        <action>Move original document to archive location</action>
        <action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
      </check>
      <check if="user selects 'k' (keep)">
        <action>Display warning to user:</action>
        <output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
 This creates confusion because:
 - The discover_inputs protocol may load the wrong version
 - Updates to one won't reflect in the other
 - You'll have duplicate content taking up space
 Consider deleting or archiving the original document.</output>
        <action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
      </check>
    </step>
  </flow>
  <halt-conditions critical="true">
    <i>HALT if npx command fails or produces no output files</i>
  </halt-conditions>
 </tool>
--- a/.bmad/core/workflows/brainstorming/README.md
+++ b/.bmad/core/workflows/brainstorming/README.md
@ -1,261 +0,0 @@
 ---
 last-redoc-date: 2025-09-28
 ---
 # Brainstorming Session Workflow
 ## Overview
 The brainstorming workflow facilitates interactive brainstorming sessions using diverse creative techniques. This workflow acts as an AI facilitator guiding users through various ideation methods to generate and refine creative solutions in a structured, energetic, and highly interactive manner.
 ## Key Features
 - **36 Creative Techniques**: Comprehensive library spanning collaborative, structured, creative, deep, theatrical, wild, and introspective approaches
 - **Interactive Facilitation**: AI acts as a skilled facilitator using "Yes, and..." methodology
 - **Flexible Approach Selection**: User-guided, AI-recommended, random, or progressive technique flows
 - **Context-Aware Sessions**: Supports domain-specific brainstorming through context document input
 - **Systematic Organization**: Converges ideas into immediate opportunities, future innovations, and moonshots
 - **Action Planning**: Prioritizes top ideas with concrete next steps and timelines
 - **Session Documentation**: Comprehensive structured reports capturing all insights and outcomes
 ## Usage
 ### Configuration
 The workflow leverages configuration from `.bmad/core/config.yaml`:
 - **output_folder**: Where session results are saved
 - **user_name**: Session participant identification
 And the following has a default or can be passed in as an override for custom brainstorming scenarios.
 - **brain_techniques**: CSV database of 36 creative techniques, default is `./brain-methods.csv`
 ## Workflow Structure
 ### Files Included
 ```
 brainstorming/
 ├── workflow.yaml           # Configuration and metadata
 ├── instructions.md         # Step-by-step execution guide
 ├── template.md            # Session report structure
 ├── brain-methods.csv      # Database of 36 creative techniques
 └── README.md              # This file
 ```
 ## Creative Techniques Library
 The workflow includes 36 techniques organized into 7 categories:
 ### Collaborative Techniques
 - **Yes And Building**: Build momentum through positive additions
 - **Brain Writing Round Robin**: Silent idea generation with sequential building
 - **Random Stimulation**: Use random catalysts for unexpected connections
 - **Role Playing**: Generate solutions from multiple stakeholder perspectives
 ### Structured Approaches
 - **SCAMPER Method**: Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
 - **Six Thinking Hats**: Explore through six perspectives (facts/emotions/benefits/risks/creativity/process)
 - **Mind Mapping**: Visual branching from central concepts
 - **Resource Constraints**: Innovation through extreme limitations
 ### Creative Methods
 - **What If Scenarios**: Explore radical possibilities by questioning constraints
 - **Analogical Thinking**: Find solutions through domain parallels
 - **Reversal Inversion**: Flip problems upside down for fresh angles
 - **First Principles Thinking**: Strip away assumptions to rebuild from fundamentals
 - **Forced Relationships**: Connect unrelated concepts for innovation
 - **Time Shifting**: Explore solutions across different time periods
 - **Metaphor Mapping**: Use extended metaphors as thinking tools
 ### Deep Analysis
 - **Five Whys**: Drill down through causation layers to root causes
 - **Morphological Analysis**: Systematically explore parameter combinations
 - **Provocation Technique**: Extract useful ideas from absurd starting points
 - **Assumption Reversal**: Challenge and flip core assumptions
 - **Question Storming**: Generate questions before seeking answers
 ### Theatrical Approaches
 - **Time Travel Talk Show**: Interview past/present/future selves
 - **Alien Anthropologist**: Examine through completely foreign eyes
 - **Dream Fusion Laboratory**: Start with impossible solutions, work backwards
 - **Emotion Orchestra**: Let different emotions lead separate sessions
 - **Parallel Universe Cafe**: Explore under alternative reality rules
 ### Wild Methods
 - **Chaos Engineering**: Deliberately break things to discover robust solutions
 - **Guerrilla Gardening Ideas**: Plant unexpected solutions in unlikely places
 - **Pirate Code Brainstorm**: Take what works from anywhere and remix
 - **Zombie Apocalypse Planning**: Design for extreme survival scenarios
 - **Drunk History Retelling**: Explain with uninhibited simplicity
 ### Introspective Delight
 - **Inner Child Conference**: Channel pure childhood curiosity
 - **Shadow Work Mining**: Explore what you're avoiding or resisting
 - **Values Archaeology**: Excavate deep personal values driving decisions
 - **Future Self Interview**: Seek wisdom from your wiser future self
 - **Body Wisdom Dialogue**: Let physical sensations guide ideation
 ## Workflow Process
 ### Phase 1: Session Setup (Step 1)
 - Context gathering (topic, goals, constraints)
 - Domain-specific guidance if context document provided
 - Session scope definition (broad exploration vs. focused ideation)
 ### Phase 2: Approach Selection (Step 2)
 - **User-Selected**: Browse and choose specific techniques
 - **AI-Recommended**: Tailored technique suggestions based on context
 - **Random Selection**: Surprise technique for creative breakthrough
 - **Progressive Flow**: Multi-technique journey from broad to focused
 ### Phase 3: Interactive Facilitation (Step 3)
 - Master facilitator approach using questions, not answers
 - "Yes, and..." building methodology
 - Energy monitoring and technique switching
 - Real-time idea capture and momentum building
 - Quantity over quality focus (aim: 100 ideas in 60 minutes)
 ### Phase 4: Convergent Organization (Step 4)
 - Review and categorize all generated ideas
 - Identify patterns and themes across techniques
 - Sort into three priority buckets for action planning
 ### Phase 5: Insight Extraction (Step 5)
 - Surface recurring themes across multiple techniques
 - Identify key realizations and surprising connections
 - Extract deeper patterns and meta-insights
 ### Phase 6: Action Planning (Step 6)
 - Prioritize top 3 ideas for implementation
 - Define concrete next steps for each priority
 - Determine resource needs and realistic timelines
 ### Phase 7: Session Reflection (Step 7)
 - Analyze what worked well and areas for further exploration
 - Recommend follow-up techniques and next session planning
 - Capture emergent questions for future investigation
 ### Phase 8: Report Generation (Step 8)
 - Compile comprehensive structured report
 - Calculate total ideas generated and techniques used
 - Format all content for sharing and future reference
 ## Output
 ### Generated Files
 - **Primary output**: Structured session report saved to `{output_folder}/brainstorming-session-results-{date}.md`
 - **Context integration**: Links to previous brainstorming sessions if available
 ### Output Structure
 1. **Executive Summary** - Topic, goals, techniques used, total ideas generated, key themes
 2. **Technique Sessions** - Detailed capture of each technique's ideation process
 3. **Idea Categorization** - Immediate opportunities, future innovations, moonshots, insights
 4. **Action Planning** - Top 3 priorities with rationale, steps, resources, timelines
 5. **Reflection and Follow-up** - Session analysis, recommendations, next steps planning
 ## Requirements
 - No special software requirements
 - Access to the CIS module configuration (`.bmad/cis/config.yaml`)
 - Active participation and engagement throughout the interactive session
 - Optional: Domain context document for focused brainstorming
 ## Best Practices
 ### Before Starting
 1. **Define Clear Intent**: Know whether you want broad exploration or focused problem-solving
 2. **Gather Context**: Prepare any relevant background documents or domain knowledge
 3. **Set Time Expectations**: Plan for 45-90 minutes for a comprehensive session
 4. **Create Open Environment**: Ensure distraction-free space for creative thinking
 ### During Execution
 1. **Embrace Quantity**: Generate many ideas without self-censoring
 2. **Build with "Yes, And"**: Accept and expand on ideas rather than judging
 3. **Stay Curious**: Follow unexpected connections and tangents
 4. **Trust the Process**: Let the facilitator guide you through technique transitions
 5. **Capture Everything**: Document all ideas, even seemingly silly ones
 6. **Monitor Energy**: Communicate when you need technique changes or breaks
 ### After Completion
 1. **Review Within 24 Hours**: Re-read the report while insights are fresh
 2. **Act on Quick Wins**: Implement immediate opportunities within one week
 3. **Schedule Follow-ups**: Plan development sessions for promising concepts
 4. **Share Selectively**: Distribute relevant insights to appropriate stakeholders
 ## Facilitation Principles
 The AI facilitator operates using these core principles:
 - **Ask, Don't Tell**: Use questions to draw out participant's own ideas
 - **Build, Don't Judge**: Use "Yes, and..." methodology, never "No, but..."
 - **Quantity Over Quality**: Aim for volume in generation phase
 - **Defer Judgment**: Evaluation comes after generation is complete
 - **Stay Curious**: Show genuine interest in participant's unique perspectives
 - **Monitor Energy**: Adapt technique and pace to participant's engagement level
 ## Example Session Flow
 ### Progressive Technique Flow
 1. **Mind Mapping** (10 min) - Build the landscape of possibilities
 2. **SCAMPER** (15 min) - Systematic exploration of improvement angles
 3. **Six Thinking Hats** (15 min) - Multiple perspectives on solutions
 4. **Forced Relationships** (10 min) - Creative synthesis of unexpected connections
 ### Energy Checkpoints
 - After 15-20 minutes: "Should we continue with this technique or try something new?"
 - Before convergent phase: "Are you ready to start organizing ideas, or explore more?"
 - During action planning: "How's your energy for the final planning phase?"
 ## Customization
 To customize this workflow:
 1. **Add New Techniques**: Extend `brain-methods.csv` with additional creative methods
 2. **Modify Facilitation Style**: Adjust prompts in `instructions.md` for different energy levels
 3. **Update Report Structure**: Modify `template.md` to include additional analysis sections
 4. **Create Domain Variants**: Develop specialized technique sets for specific industries
 ## Version History
 - **v1.0.0** - Initial release
  - 36 creative techniques across 7 categories
  - Interactive facilitation with energy monitoring
  - Comprehensive structured reporting
  - Context-aware session guidance
 ## Support
 For issues or questions:
 - Review technique descriptions in `brain-methods.csv` for facilitation guidance
 - Consult the workflow instructions in `instructions.md` for step-by-step details
 - Reference the template structure in `template.md` for output expectations
 - Follow BMAD documentation standards for workflow customization
 ---
 _Part of the BMad Method v6 - Creative Ideation and Synthesis (CIS) Module_
--- a/.bmad/core/workflows/brainstorming/brain-methods.csv
+++ b/.bmad/core/workflows/brainstorming/brain-methods.csv
@ -1,36 +0,0 @@
 category,technique_name,description,facilitation_prompts,best_for,energy_level,typical_duration
 collaborative,Yes And Building,Build momentum through positive additions where each idea becomes a launching pad for the next - creates energetic collaborative flow,Yes and we could also...|Building on that idea...|That reminds me of...|What if we added?,team-building,high,15-20
 collaborative,Brain Writing Round Robin,Silent idea generation followed by building on others' written concepts - gives quieter voices equal contribution while maintaining documentation,Write your idea silently|Pass to the next person|Build on what you received|Keep ideas flowing,quiet-voices,moderate,20-25
 collaborative,Random Stimulation,Use random words/images as creative catalysts to force unexpected connections - breaks through mental blocks with serendipitous inspiration,Pick a random word/image|How does this relate?|What connections do you see?|Force a relationship
 collaborative,Role Playing,Generate solutions from multiple stakeholder perspectives - builds empathy while ensuring comprehensive consideration of all viewpoints,Think as a [role]|What would they want?|How would they approach this?|What matters to them?
 creative,What If Scenarios,Explore radical possibilities by questioning all constraints and assumptions - perfect for breaking through stuck thinking and discovering unexpected opportunities,What if we had unlimited resources?|What if the opposite were true?|What if this problem didn't exist?,innovation,high,15-20
 creative,Analogical Thinking,Find creative solutions by drawing parallels to other domains - helps transfer successful patterns from one context to another,This is like what?|How is this similar to...?|What other examples come to mind?
 creative,Reversal Inversion,Deliberately flip problems upside down to reveal hidden assumptions and fresh angles - great when conventional approaches aren't working,What if we did the opposite?|How could we make this worse?|What's the reverse approach?
 creative,First Principles Thinking,Strip away assumptions to rebuild from fundamental truths - essential for breakthrough innovation and solving complex problems,What do we know for certain?|What are the fundamental truths?|If we started from scratch?
 creative,Forced Relationships,Connect unrelated concepts to spark innovative bridges - excellent for generating unexpected solutions through creative collision,Take these two unrelated things|Find connections between them|What bridges exist?|How could they work together?
 creative,Time Shifting,Explore how solutions would work across different time periods - reveals constraints and opportunities by changing temporal context,How would this work in the past?|What about 100 years from now?|Different era constraints?|Time-based solutions?
 creative,Metaphor Mapping,Use extended metaphors as thinking tools to explore problems from new angles - transforms abstract challenges into tangible narratives,This problem is like a [metaphor]|Extend the metaphor|What elements map over?|What insights emerge?
 deep,Five Whys,Drill down through layers of causation to uncover root causes - essential for solving problems at their source rather than treating symptoms,Why did this happen?|Why is that?|And why is that true?|What's behind that?|Why ultimately?,problem-solving,moderate,10-15
 deep,Morphological Analysis,Systematically explore all possible parameter combinations - perfect for complex systems requiring comprehensive solution mapping,What are the key parameters?|List options for each|Try different combinations|What patterns emerge?
 deep,Provocation Technique,Use deliberately provocative statements to extract useful ideas from seemingly absurd starting points - catalyzes breakthrough thinking,What if [provocative statement]?|How could this be useful?|What idea does this trigger?|Extract the principle
 deep,Assumption Reversal,Challenge and flip core assumptions to rebuild from new foundations - essential for paradigm shifts and fresh perspectives,What assumptions are we making?|What if the opposite were true?|Challenge each assumption|Rebuild from new assumptions
 deep,Question Storming,Generate questions before seeking answers to properly define the problem space - ensures you're solving the right problem,Only ask questions|No answers allowed yet|What don't we know?|What should we be asking?
 introspective_delight,Inner Child Conference,Channel pure childhood curiosity and wonder - rekindles playful exploration and innocent questioning that cuts through adult complications,What would 7-year-old you ask?|Why why why?|Make it fun again|No boring allowed
 introspective_delight,Shadow Work Mining,Explore what you're actively avoiding or resisting - uncovers hidden insights by examining unconscious blocks and resistance patterns,What are you avoiding?|Where's the resistance?|What scares you about this?|Mine the shadows
 introspective_delight,Values Archaeology,Excavate the deep personal values driving your decisions - clarifies authentic priorities by digging to bedrock motivations,What really matters here?|Why do you care?|Dig to bedrock values|What's non-negotiable?
 introspective_delight,Future Self Interview,Seek wisdom from your wiser future self - gains long-term perspective through imagined temporal self-mentoring,Ask your 80-year-old self|What would you tell younger you?|Future wisdom speaks|Long-term perspective
 introspective_delight,Body Wisdom Dialogue,Let physical sensations and gut feelings guide ideation - taps somatic intelligence often ignored by purely mental approaches,What does your body say?|Where do you feel it?|Trust the tension|Follow physical cues
 structured,SCAMPER Method,Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - ideal for methodical product improvement and innovation,S-What could you substitute?|C-What could you combine?|A-How could you adapt?|M-What could you modify?|P-Put to other uses?|E-What could you eliminate?|R-What if reversed?
 structured,Six Thinking Hats,Explore problems through six distinct perspectives (facts/emotions/benefits/risks/creativity/process) - ensures comprehensive analysis without conflict,White-What facts do we know?|Red-How do you feel about this?|Yellow-What are the benefits?|Black-What could go wrong?|Green-What creative alternatives?|Blue-How should we think about this?
 structured,Mind Mapping,Visually branch ideas from a central concept to discover connections and expand thinking - perfect for organizing complex thoughts and seeing the big picture,Put the main idea in center|What branches from this?|How do these connect?|What sub-branches emerge?
 structured,Resource Constraints,Generate innovative solutions by imposing extreme limitations - forces essential priorities and creative efficiency under pressure,What if you had only $1?|No technology allowed?|One hour to solve?|Minimal resources only?
 theatrical,Time Travel Talk Show,Interview your past/present/future selves for temporal wisdom - playful method for gaining perspective across different life stages,Interview your past self|What would future you say?|Different timeline perspectives|Cross-temporal dialogue
 theatrical,Alien Anthropologist,Examine familiar problems through completely foreign eyes - reveals hidden assumptions by adopting an outsider's bewildered perspective,You're an alien observer|What seems strange?|How would you explain this?|Outside perspective insights
 theatrical,Dream Fusion Laboratory,Start with impossible fantasy solutions then reverse-engineer practical steps - makes ambitious thinking actionable through backwards design,Dream the impossible solution|Work backwards to reality|What steps bridge the gap?|Make magic practical
 theatrical,Emotion Orchestra,Let different emotions lead separate brainstorming sessions then harmonize - uses emotional intelligence for comprehensive perspective,Angry perspective ideas|Joyful approach|Fearful considerations|Hopeful solutions|Harmonize all voices
 theatrical,Parallel Universe Cafe,Explore solutions under alternative reality rules - breaks conventional thinking by changing fundamental assumptions about how things work,Different physics universe|Alternative social norms|Changed historical events|Reality rule variations
 wild,Chaos Engineering,Deliberately break things to discover robust solutions - builds anti-fragility by stress-testing ideas against worst-case scenarios,What if everything went wrong?|Break it on purpose|How does it fail gracefully?|Build from the rubble
 wild,Guerrilla Gardening Ideas,Plant unexpected solutions in unlikely places - uses surprise and unconventional placement for stealth innovation,Where's the least expected place?|Plant ideas secretly|Grow solutions underground|Surprise implementation
 wild,Pirate Code Brainstorm,Take what works from anywhere and remix without permission - encourages rule-bending rapid prototyping and maverick thinking,What would pirates steal?|Remix without asking|Take the best and run|No permission needed
 wild,Zombie Apocalypse Planning,Design solutions for extreme survival scenarios - strips away all but essential functions to find core value,Society collapsed - now what?|Only basics work|Build from nothing|Survival mode thinking
 wild,Drunk History Retelling,Explain complex ideas with uninhibited simplicity - removes overthinking barriers to find raw truth through simplified expression,Explain it like you're tipsy|No filter needed|Raw unedited thoughts|Simplify to absurdity
--- a/.bmad/core/workflows/brainstorming/instructions.md
+++ b/.bmad/core/workflows/brainstorming/instructions.md
@ -1,315 +0,0 @@
 # Brainstorming Session Instructions
 ## 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/core/workflows/brainstorming/workflow.yaml</critical>
 <step n="1" goal="Session Setup">
 <action>Check if context data was provided with workflow invocation</action>
 <check if="data attribute was passed to this workflow">
  <action>Load the context document from the data file path</action>
  <action>Study the domain knowledge and session focus</action>
  <action>Use the provided context to guide the session</action>
  <action>Acknowledge the focused brainstorming goal</action>
  <ask response="session_refinement">I see we're brainstorming about the specific domain outlined in the context. What particular aspect would you like to explore?</ask>
 </check>
 <check if="no context data provided">
  <action>Proceed with generic context gathering</action>
  <ask response="session_topic">1. What are we brainstorming about?</ask>
  <ask response="stated_goals">2. Are there any constraints or parameters we should keep in mind?</ask>
  <ask>3. Is the goal broad exploration or focused ideation on specific aspects?</ask>
 <critical>Wait for user response before proceeding. This context shapes the entire session.</critical>
 </check>
 <template-output>session_topic, stated_goals</template-output>
 </step>
 <step n="2" goal="Present Approach Options">
 Based on the context from Step 1, present these four approach options:
 <ask response="selection">
 1. **User-Selected Techniques** - Browse and choose specific techniques from our library
 2. **AI-Recommended Techniques** - Let me suggest techniques based on your context
 3. **Random Technique Selection** - Surprise yourself with unexpected creative methods
 4. **Progressive Technique Flow** - Start broad, then narrow down systematically
 Which approach would you prefer? (Enter 1-4)
 </ask>
  <step n="2a" title="User-Selected Techniques" if="selection==1">
    <action>Load techniques from {brain_techniques} CSV file</action>
    <action>Parse: category, technique_name, description, facilitation_prompts</action>
    <check if="strong context from Step 1 (specific problem/goal)">
      <action>Identify 2-3 most relevant categories based on stated_goals</action>
      <action>Present those categories first with 3-5 techniques each</action>
      <action>Offer "show all categories" option</action>
    </check>
    <check if="open exploration">
      <action>Display all 7 categories with helpful descriptions</action>
    </check>
    Category descriptions to guide selection:
    - **Structured:** Systematic frameworks for thorough exploration
    - **Creative:** Innovative approaches for breakthrough thinking
    - **Collaborative:** Group dynamics and team ideation methods
    - **Deep:** Analytical methods for root cause and insight
    - **Theatrical:** Playful exploration for radical perspectives
    - **Wild:** Extreme thinking for pushing boundaries
    - **Introspective Delight:** Inner wisdom and authentic exploration
    For each category, show 3-5 representative techniques with brief descriptions.
    Ask in your own voice: "Which technique(s) interest you? You can choose by name, number, or tell me what you're drawn to."
  </step>
  <step n="2b" title="AI-Recommended Techniques" if="selection==2">
    <action>Review {brain_techniques} and select 3-5 techniques that best fit the context</action>
    Analysis Framework:
    1. **Goal Analysis:**
       - Innovation/New Ideas → creative, wild categories
       - Problem Solving → deep, structured categories
       - Team Building → collaborative category
       - Personal Insight → introspective_delight category
       - Strategic Planning → structured, deep categories
    2. **Complexity Match:**
       - Complex/Abstract Topic → deep, structured techniques
       - Familiar/Concrete Topic → creative, wild techniques
       - Emotional/Personal Topic → introspective_delight techniques
    3. **Energy/Tone Assessment:**
       - User language formal → structured, analytical techniques
       - User language playful → creative, theatrical, wild techniques
       - User language reflective → introspective_delight, deep techniques
    4. **Time Available:**
       - <30 min → 1-2 focused techniques
       - 30-60 min → 2-3 complementary techniques
       - >60 min → Consider progressive flow (3-5 techniques)
    Present recommendations in your own voice with:
    - Technique name (category)
    - Why it fits their context (specific)
    - What they'll discover (outcome)
    - Estimated time
    Example structure:
    "Based on your goal to [X], I recommend:
    1. **[Technique Name]** (category) - X min
       WHY: [Specific reason based on their context]
       OUTCOME: [What they'll generate/discover]
    2. **[Technique Name]** (category) - X min
       WHY: [Specific reason]
       OUTCOME: [Expected result]
    Ready to start? [c] or would you prefer different techniques? [r]"
  </step>
  <step n="2c" title="Single Random Technique Selection" if="selection==3">
    <action>Load all techniques from {brain_techniques} CSV</action>
    <action>Select random technique using true randomization</action>
    <action>Build excitement about unexpected choice</action>
    <format>
      Let's shake things up! The universe has chosen:
      **{{technique_name}}** - {{description}}
    </format>
  </step>
  <step n="2d" title="Progressive Flow" if="selection==4">
    <action>Design a progressive journey through {brain_techniques} based on session context</action>
    <action>Analyze stated_goals and session_topic from Step 1</action>
    <action>Determine session length (ask if not stated)</action>
    <action>Select 3-4 complementary techniques that build on each other</action>
    Journey Design Principles:
    - Start with divergent exploration (broad, generative)
    - Move through focused deep dive (analytical or creative)
    - End with convergent synthesis (integration, prioritization)
    Common Patterns by Goal:
    - **Problem-solving:** Mind Mapping → Five Whys → Assumption Reversal
    - **Innovation:** What If Scenarios → Analogical Thinking → Forced Relationships
    - **Strategy:** First Principles → SCAMPER → Six Thinking Hats
    - **Team Building:** Brain Writing → Yes And Building → Role Playing
    Present your recommended journey with:
    - Technique names and brief why
    - Estimated time for each (10-20 min)
    - Total session duration
    - Rationale for sequence
    Ask in your own voice: "How does this flow sound? We can adjust as we go."
  </step>
 <critical>Create the output document using the template, and record at the {{session_start_plan}} documenting the chosen techniques, along with which approach was used. For all remaining steps, progressively add to the document throughout the brainstorming</critical>
 </step>
 <step n="3" goal="Execute Techniques Interactively">
 <critical>
 REMEMBER: YOU ARE A MASTER Brainstorming Creative FACILITATOR: Guide the user as a facilitator to generate their own ideas through questions, prompts, and examples. Don't brainstorm for them unless they explicitly request it.
 </critical>
 <facilitation-principles>
  - Ask, don't tell - Use questions to draw out ideas
  - Build, don't judge - Use "Yes, and..." never "No, but..."
  - Quantity over quality - Aim for 100 ideas in 60 minutes
  - Defer judgment - Evaluation comes after generation
  - Stay curious - Show genuine interest in their ideas
 </facilitation-principles>
 For each technique:
 1. **Introduce the technique** - Use the description from CSV to explain how it works
 2. **Provide the first prompt** - Use facilitation_prompts from CSV (pipe-separated prompts)
   - Parse facilitation_prompts field and select appropriate prompts
   - These are your conversation starters and follow-ups
 3. **Wait for their response** - Let them generate ideas
 4. **Build on their ideas** - Use "Yes, and..." or "That reminds me..." or "What if we also..."
 5. **Ask follow-up questions** - "Tell me more about...", "How would that work?", "What else?"
 6. **Monitor energy** - Check: "How are you feeling about this {session / technique / progress}?"
   - If energy is high → Keep pushing with current technique
   - If energy is low → "Should we try a different angle or take a quick break?"
 7. **Keep momentum** - Celebrate: "Great! You've generated [X] ideas so far!"
 8. **Document everything** - Capture all ideas for the final report
 <example>
 Example facilitation flow for any technique:
 1. Introduce: "Let's try [technique_name]. [Adapt description from CSV to their context]."
 2. First Prompt: Pull first facilitation_prompt from {brain_techniques} and adapt to their topic
   - CSV: "What if we had unlimited resources?"
   - Adapted: "What if you had unlimited resources for [their_topic]?"
 3. Build on Response: Use "Yes, and..." or "That reminds me..." or "Building on that..."
 4. Next Prompt: Pull next facilitation_prompt when ready to advance
 5. Monitor Energy: After a few rounds, check if they want to continue or switch
 The CSV provides the prompts - your role is to facilitate naturally in your unique voice.
 </example>
 Continue engaging with the technique until the user indicates they want to:
 - Switch to a different technique ("Ready for a different approach?")
 - Apply current ideas to a new technique
 - Move to the convergent phase
 - End the session
 <energy-checkpoint>
  After 4 rounds with a technique, check: "Should we continue with this technique or try something new?"
 </energy-checkpoint>
 <template-output>technique_sessions</template-output>
 </step>
 <step n="4" goal="Convergent Phase - Organize Ideas">
 <transition-check>
  "We've generated a lot of great ideas! Are you ready to start organizing them, or would you like to explore more?"
 </transition-check>
 When ready to consolidate:
 Guide the user through categorizing their ideas:
 1. **Review all generated ideas** - Display everything captured so far
 2. **Identify patterns** - "I notice several ideas about X... and others about Y..."
 3. **Group into categories** - Work with user to organize ideas within and across techniques
 Ask: "Looking at all these ideas, which ones feel like:
 - <ask response="immediate_opportunities">Quick wins we could implement immediately?</ask>
 - <ask response="future_innovations">Promising concepts that need more development?</ask>
 - <ask response="moonshots">Bold moonshots worth pursuing long-term?"</ask>
 <template-output>immediate_opportunities, future_innovations, moonshots</template-output>
 </step>
 <step n="5" goal="Extract Insights and Themes">
 Analyze the session to identify deeper patterns:
 1. **Identify recurring themes** - What concepts appeared across multiple techniques? -> key_themes
 2. **Surface key insights** - What realizations emerged during the process? -> insights_learnings
 3. **Note surprising connections** - What unexpected relationships were discovered? -> insights_learnings
 <invoke-task halt="true">{project-root}/.bmad/core/tasks/advanced-elicitation.xml</invoke-task>
 <template-output>key_themes, insights_learnings</template-output>
 </step>
 <step n="6" goal="Action Planning">
 <energy-check>
  "Great work so far! How's your energy for the final planning phase?"
 </energy-check>
 Work with the user to prioritize and plan next steps:
 <ask>Of all the ideas we've generated, which 3 feel most important to pursue?</ask>
 For each priority:
 1. Ask why this is a priority
 2. Identify concrete next steps
 3. Determine resource needs
 4. Set realistic timeline
 <template-output>priority_1_name, priority_1_rationale, priority_1_steps, priority_1_resources, priority_1_timeline</template-output>
 <template-output>priority_2_name, priority_2_rationale, priority_2_steps, priority_2_resources, priority_2_timeline</template-output>
 <template-output>priority_3_name, priority_3_rationale, priority_3_steps, priority_3_resources, priority_3_timeline</template-output>
 </step>
 <step n="7" goal="Session Reflection">
 Conclude with meta-analysis of the session:
 1. **What worked well** - Which techniques or moments were most productive?
 2. **Areas to explore further** - What topics deserve deeper investigation?
 3. **Recommended follow-up techniques** - What methods would help continue this work?
 4. **Emergent questions** - What new questions arose that we should address?
 5. **Next session planning** - When and what should we brainstorm next?
 <template-output>what_worked, areas_exploration, recommended_techniques, questions_emerged</template-output>
 <template-output>followup_topics, timeframe, preparation</template-output>
 </step>
 <step n="8" goal="Generate Final Report">
 Compile all captured content into the structured report template:
 1. Calculate total ideas generated across all techniques
 2. List all techniques used with duration estimates
 3. Format all content according to template structure
 4. Ensure all placeholders are filled with actual content
 <template-output>agent_role, agent_name, user_name, techniques_list, total_ideas</template-output>
 </step>
 </workflow>
--- a/.bmad/core/workflows/brainstorming/template.md
+++ b/.bmad/core/workflows/brainstorming/template.md
@ -1,106 +0,0 @@
 # Brainstorming Session Results
 **Session Date:** {{date}}
 **Facilitator:** {{agent_role}} {{agent_name}}
 **Participant:** {{user_name}}
 ## Session Start
 {{session_start_plan}}
 ## Executive Summary
 **Topic:** {{session_topic}}
 **Session Goals:** {{stated_goals}}
 **Techniques Used:** {{techniques_list}}
 **Total Ideas Generated:** {{total_ideas}}
 ### Key Themes Identified:
 {{key_themes}}
 ## Technique Sessions
 {{technique_sessions}}
 ## Idea Categorization
 ### Immediate Opportunities
 _Ideas ready to implement now_
 {{immediate_opportunities}}
 ### Future Innovations
 _Ideas requiring development/research_
 {{future_innovations}}
 ### Moonshots
 _Ambitious, transformative concepts_
 {{moonshots}}
 ### Insights and Learnings
 _Key realizations from the session_
 {{insights_learnings}}
 ## Action Planning
 ### Top 3 Priority Ideas
 #### #1 Priority: {{priority_1_name}}
 - Rationale: {{priority_1_rationale}}
 - Next steps: {{priority_1_steps}}
 - Resources needed: {{priority_1_resources}}
 - Timeline: {{priority_1_timeline}}
 #### #2 Priority: {{priority_2_name}}
 - Rationale: {{priority_2_rationale}}
 - Next steps: {{priority_2_steps}}
 - Resources needed: {{priority_2_resources}}
 - Timeline: {{priority_2_timeline}}
 #### #3 Priority: {{priority_3_name}}
 - Rationale: {{priority_3_rationale}}
 - Next steps: {{priority_3_steps}}
 - Resources needed: {{priority_3_resources}}
 - Timeline: {{priority_3_timeline}}
 ## Reflection and Follow-up
 ### What Worked Well
 {{what_worked}}
 ### Areas for Further Exploration
 {{areas_exploration}}
 ### Recommended Follow-up Techniques
 {{recommended_techniques}}
 ### Questions That Emerged
 {{questions_emerged}}
 ### Next Session Planning
 - **Suggested topics:** {{followup_topics}}
 - **Recommended timeframe:** {{timeframe}}
 - **Preparation needed:** {{preparation}}
 ---
 _Session facilitated using the BMAD CIS brainstorming framework_
--- a/.bmad/core/workflows/brainstorming/workflow.yaml
+++ b/.bmad/core/workflows/brainstorming/workflow.yaml
@ -1,43 +0,0 @@
 # Brainstorming Session Workflow Configuration
 name: "brainstorming"
 description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
 author: "BMad"
 # Critical variables load from config_source
 config_source: "{project-root}/.bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 date: system-generated
 # Optional inputs for guided brainstorming
 recommended_inputs:
  - session_context: "Context document passed via data attribute"
  - previous_results: "{output_folder}/brainstorming-*.md"
 # Context can be provided via data attribute when invoking
 # Example: data="{path}/context.md" provides domain-specific guidance
 # Module path and component files
 installed_path: "{project-root}/.bmad/core/workflows/brainstorming"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 brain_techniques: "{installed_path}/brain-methods.csv"
 # Output configuration
 default_output_file: "{output_folder}/brainstorming-session-results-{{date}}.md"
 standalone: true
 web_bundle:
  name: "brainstorming"
  description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
  author: "BMad"
  template: ".bmad/core/workflows/brainstorming/template.md"
  instructions: ".bmad/core/workflows/brainstorming/instructions.md"
  brain_techniques: ".bmad/core/workflows/brainstorming/brain-methods.csv"
  use_advanced_elicitation: true
  web_bundle_files:
    - ".bmad/core/workflows/brainstorming/instructions.md"
    - ".bmad/core/workflows/brainstorming/brain-methods.csv"
    - ".bmad/core/workflows/brainstorming/template.md"
--- a/.bmad/core/workflows/party-mode/instructions.md
+++ b/.bmad/core/workflows/party-mode/instructions.md
@ -1,183 +0,0 @@
 # Party Mode - Multi-Agent Discussion Instructions
 <critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
 <workflow>
 <step n="1" goal="Load Agent Manifest and Configurations">
  <action>Load the agent manifest CSV from {{agent_manifest}}</action>
  <action>Parse CSV to extract all agent entries with their condensed information:</action>
    - name (agent identifier)
    - displayName (agent's persona name)
    - title (formal position)
    - icon (visual identifier)
    - role (capabilities summary)
    - identity (background/expertise)
    - communicationStyle (how they communicate)
    - principles (decision-making philosophy)
    - module (source module)
    - path (file location)
 <action>Build complete agent roster with merged personalities</action>
 <action>Store agent data for use in conversation orchestration</action>
 </step>
 <step n="2" goal="Initialize Party Mode">
  <action>Announce party mode activation with enthusiasm</action>
  <action>List all participating agents with their merged information:</action>
  <format>
    🎉 PARTY MODE ACTIVATED! 🎉
    All agents are here for a group discussion!
    Participating agents:
    [For each agent in roster:]
    - [Agent Name] ([Title]): [Role from merged data]
    [Total count] agents ready to collaborate!
    What would you like to discuss with the team?
  </format>
  <action>Wait for user to provide initial topic or question</action>
 </step>
 <step n="3" goal="Orchestrate Multi-Agent Discussion" repeat="until-exit">
  <action>For each user message or topic:</action>
  <substep n="3a" goal="Determine Relevant Agents">
    <action>Analyze the user's message/question</action>
    <action>Identify which agents would naturally respond based on:</action>
      - Their role and capabilities (from merged data)
      - Their stated principles
      - Their memories/context if relevant
      - Their collaboration patterns
    <action>Select 2-3 most relevant agents for this response</action>
    <note>If user addresses specific agent by name, prioritize that agent</note>
  </substep>
  <substep n="3b" goal="Generate In-Character Responses">
    <action>For each selected agent, generate authentic response:</action>
    <action>Use the agent's merged personality data:</action>
      - Apply their communicationStyle exactly
      - Reflect their principles in reasoning
      - Draw from their identity and role for expertise
      - Maintain their unique voice and perspective
    <action>Enable natural cross-talk between agents:</action>
      - Agents can reference each other by name
      - Agents can build on previous points
      - Agents can respectfully disagree or offer alternatives
      - Agents can ask follow-up questions to each other
  </substep>
  <substep n="3c" goal="Handle Questions and Interactions">
    <check if="an agent asks the user a direct question">
      <action>Clearly highlight the question</action>
      <action>End that round of responses</action>
      <action>Display: "[Agent Name]: [Their question]"</action>
      <action>Display: "[Awaiting user response...]"</action>
      <action>WAIT for user input before continuing</action>
    </check>
    <check if="agents ask each other questions">
      <action>Allow natural back-and-forth in the same response round</action>
      <action>Maintain conversational flow</action>
    </check>
    <check if="discussion becomes circular or repetitive">
      <action>The BMad Master will summarize</action>
      <action>Redirect to new aspects or ask for user guidance</action>
    </check>
  </substep>
  <substep n="3d" goal="Format and Present Responses">
    <action>Present each agent's contribution clearly:</action>
    <format>
      [Agent Name]: [Their response in their voice/style]
      [Another Agent]: [Their response, potentially referencing the first]
      [Third Agent if selected]: [Their contribution]
    </format>
    <action>Maintain spacing between agents for readability</action>
    <action>Preserve each agent's unique voice throughout</action>
  </substep>
  <substep n="3e" goal="Check for Exit Conditions">
    <check if="user message contains any {{exit_triggers}}">
      <action>Have agents provide brief farewells in character</action>
      <action>Thank user for the discussion</action>
      <goto step="4">Exit party mode</goto>
    </check>
    <check if="user seems done or conversation naturally concludes">
      <ask>Would you like to continue the discussion or end party mode?</ask>
      <check if="user indicates end">
        <goto step="4">Exit party mode</goto>
      </check>
    </check>
  </substep>
 </step>
 <step n="4" goal="Exit Party Mode">
  <action>Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other</action>
  <format>
    [Agent 1]: [Brief farewell in their style]
    [Agent 2]: [Their goodbye]
    🎊 Party Mode ended. Thanks for the great discussion!
  </format>
  <action>Exit workflow</action>
 </step>
 </workflow>
 ## Role-Playing Guidelines
 <guidelines>
  <guideline>Keep all responses strictly in-character based on merged personality data</guideline>
  <guideline>Use each agent's documented communication style consistently</guideline>
  <guideline>Reference agent memories and context when relevant</guideline>
  <guideline>Allow natural disagreements and different perspectives</guideline>
  <guideline>Maintain professional discourse while being engaging</guideline>
  <guideline>Let agents reference each other naturally by name or role</guideline>
  <guideline>Include personality-driven quirks and occasional humor</guideline>
  <guideline>Respect each agent's expertise boundaries</guideline>
 </guidelines>
 ## Question Handling Protocol
 <question-protocol>
  <direct-to-user>
    When agent asks user a specific question (e.g., "What's your budget?"):
    - End that round immediately after the question
    - Clearly highlight the questioning agent and their question
    - Wait for user response before any agent continues
  </direct-to-user>
  <rhetorical>
    Agents can ask rhetorical or thinking-aloud questions without pausing
  </rhetorical>
  <inter-agent>
    Agents can question each other and respond naturally within same round
  </inter-agent>
 </question-protocol>
 ## Moderation Notes
 <moderation>
  <note>If discussion becomes circular, have bmad-master summarize and redirect</note>
  <note>If user asks for specific agent, let that agent take primary lead</note>
  <note>Balance fun and productivity based on conversation tone</note>
  <note>Ensure all agents stay true to their merged personalities</note>
  <note>Exit gracefully when user indicates completion</note>
 </moderation>
--- a/.bmad/core/workflows/party-mode/workflow.yaml
+++ b/.bmad/core/workflows/party-mode/workflow.yaml
@ -1,28 +0,0 @@
 # Party Mode - Multi-Agent Group Discussion Workflow
 name: "party-mode"
 description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
 author: "BMad"
 # Critical data sources - manifest and config overrides
 agent_manifest: "{project-root}/.bmad/_cfg/agent-manifest.csv"
 date: system-generated
 # This is an interactive action workflow - no template output
 template: false
 instructions: "{project-root}/.bmad/core/workflows/party-mode/instructions.md"
 # Exit conditions
 exit_triggers:
  - "*exit"
 standalone: true
 web_bundle:
  name: "party-mode"
  description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
  author: "BMad"
  instructions: ".bmad/core/workflows/party-mode/instructions.md"
  agent_manifest: ".bmad/_cfg/agent-manifest.csv"
  web_bundle_files:
    - ".bmad/core/workflows/party-mode/instructions.md"
    - ".bmad/_cfg/agent-manifest.csv"
--- a/.bmad/docs/claude-code-instructions.md
+++ b/.bmad/docs/claude-code-instructions.md
@ -1,25 +0,0 @@
 # BMAD Method - Claude Code Instructions
 ## Activating Agents
 BMAD agents are installed as slash commands in `.claude/commands/bmad/`.
 ### How to Use
 1. **Type Slash Command**: Start with `/` to see available commands
 2. **Select Agent**: Type `/bmad-{agent-name}` (e.g., `/bmad-dev`)
 3. **Execute**: Press Enter to activate that agent persona
 ### Examples
 ```
 /bmad:bmm:agents:dev - Activate development agent
 /bmad:bmm:agents:architect - Activate architect agent
 /bmad:bmm:workflows:dev-story - Execute dev-story workflow
 ```
 ### Notes
 - Commands are autocompleted when you type `/`
 - Agent remains active for the conversation
 - Start a new conversation to switch agents
--- a/.claude/commands/bmad/bmb/agents/bmad-builder.md
+++ b/.claude/commands/bmad/bmb/agents/bmad-builder.md
@ -1,14 +0,0 @@
 ---
 name: 'bmad-builder'
 description: 'bmad-builder agent'
 ---
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 <agent-activation CRITICAL="TRUE">
 1. LOAD the FULL agent file from @.bmad/bmb/agents/bmad-builder.md
 2. READ its entire contents - this contains the complete agent persona, menu, and instructions
 3. Execute ALL activation steps exactly as written in the agent file
 4. Follow the agent's persona and menu system precisely
 5. Stay in character throughout the session
 </agent-activation>
--- a/.claude/commands/bmad/bmb/workflows/audit-workflow.md
+++ b/.claude/commands/bmad/bmb/workflows/audit-workflow.md
@ -1,13 +0,0 @@
 ---
 description: 'Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards.'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/audit-workflow/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/audit-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/convert-legacy.md
+++ b/.claude/commands/bmad/bmb/workflows/convert-legacy.md
@ -1,13 +0,0 @@
 ---
 description: 'Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/convert-legacy/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/convert-legacy/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/create-agent.md
+++ b/.claude/commands/bmad/bmb/workflows/create-agent.md
@ -1,13 +0,0 @@
 ---
 description: 'Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/create-agent/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/create-agent/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/create-module.md
+++ b/.claude/commands/bmad/bmb/workflows/create-module.md
@ -1,13 +0,0 @@
 ---
 description: 'Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/create-module/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/create-module/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/create-workflow.md
+++ b/.claude/commands/bmad/bmb/workflows/create-workflow.md
@ -1,13 +0,0 @@
 ---
 description: 'Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/create-workflow/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/create-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/edit-agent.md
+++ b/.claude/commands/bmad/bmb/workflows/edit-agent.md
@ -1,13 +0,0 @@
 ---
 description: 'Edit existing BMAD agents while following all best practices and conventions'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/edit-agent/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/edit-agent/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/edit-module.md
+++ b/.claude/commands/bmad/bmb/workflows/edit-module.md
@ -1,13 +0,0 @@
 ---
 description: 'Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/edit-module/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/edit-module/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/edit-workflow.md
+++ b/.claude/commands/bmad/bmb/workflows/edit-workflow.md
@ -1,13 +0,0 @@
 ---
 description: 'Edit existing BMAD workflows while following all best practices and conventions'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/edit-workflow/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/edit-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/module-brief.md
+++ b/.claude/commands/bmad/bmb/workflows/module-brief.md
@ -1,13 +0,0 @@
 ---
 description: 'Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/module-brief/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/module-brief/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/bmb/workflows/redoc.md
+++ b/.claude/commands/bmad/bmb/workflows/redoc.md
@ -1,13 +0,0 @@
 ---
 description: 'Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.'
 ---
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmb/workflows/redoc/workflow.yaml
 3. Pass the yaml path .bmad/bmb/workflows/redoc/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
--- a/.claude/commands/bmad/core/agents/bmad-master.md
+++ b/.claude/commands/bmad/core/agents/bmad-master.md
@ -1,14 +0,0 @@
 ---
 name: 'bmad-master'
 description: 'bmad-master agent'
 ---
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 <agent-activation CRITICAL="TRUE">
 1. LOAD the FULL agent file from @.bmad/core/agents/bmad-master.md
 2. READ its entire contents - this contains the complete agent persona, menu, and instructions
 3. Execute ALL activation steps exactly as written in the agent file
 4. Follow the agent's persona and menu system precisely
 5. Stay in character throughout the session
 </agent-activation>
--- a/.claude/commands/bmad/core/tasks/advanced-elicitation.md
+++ b/.claude/commands/bmad/core/tasks/advanced-elicitation.md
@ -1,9 +0,0 @@
 ---
 description: 'When called from workflow'
 ---
 # Advanced Elicitation
 LOAD and execute the task at: .bmad/core/tasks/advanced-elicitation.xml
 Follow all instructions in the task file exactly as written.
--- a/.claude/commands/bmad/core/tasks/index-docs.md
+++ b/.claude/commands/bmad/core/tasks/index-docs.md
@ -1,9 +0,0 @@
 ---
 description: 'Generates or updates an index.md of all documents in the specified directory'
 ---
 # Index Docs
 LOAD and execute the task at: .bmad/core/tasks/index-docs.xml
 Follow all instructions in the task file exactly as written.
--- a/Show More
+++ b/Show More
		`@ -1,2 +0,0 @@`
			`name,displayName,description,module,path,standalone`
			`"shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core",".bmad/core/tools/shard-doc.xml","true"`