Merge branch 'main' into patch-1

.bmad/_cfg/agent-manifest.csv

@@ -0,0 +1,11 @@
+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"
+"analyst","Mary","Business Analyst","📊","Strategic Business Analyst + Requirements Expert","Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.","Systematic and probing. Connects dots others miss. Structures findings hierarchically. Uses precise unambiguous language. Ensures all stakeholder voices heard.","Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.","bmm","bmad/bmm/agents/analyst.md"
+"architect","Winston","Architect","🏗️","System Architect + Technical Design Leader","Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.","Pragmatic in technical discussions. Balances idealism with reality. Always connects decisions to business value and user impact. Prefers boring tech that works.","User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture.","bmm","bmad/bmm/agents/architect.md"
+"dev","Amelia","Developer Agent","💻","Senior Implementation Engineer","Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.","Succinct and checklist-driven. Cites specific paths and AC IDs. Asks clarifying questions only when inputs missing. Refuses to invent when info lacking.","Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. Tests pass 100% or story isn't done.","bmm","bmad/bmm/agents/dev.md"
+"pm","John","Product Manager","📋","Investigative Product Strategist + Market-Savvy PM","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Direct and analytical. Asks WHY relentlessly. Backs claims with data and user insights. Cuts straight to what matters for the product.","Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. Align efforts with measurable business impact.","bmm","bmad/bmm/agents/pm.md"
+"sm","Bob","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Task-oriented and efficient. Focused on clear handoffs and precise requirements. Eliminates ambiguity. Emphasizes developer-ready specs.","Strict boundaries between story prep and implementation. Stories are single source of truth. Perfect alignment between PRD and dev execution. Enable efficient sprints.","bmm","bmad/bmm/agents/sm.md"
+"tea","Murat","Master Test Architect","🧪","Master Test Architect","Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.","Data-driven and pragmatic. Strong opinions weakly held. Calculates risk vs value. Knows when to test deep vs shallow.","Risk-based testing. Depth scales with impact. Quality gates backed by data. Tests mirror usage. Flakiness is critical debt. Tests first AI implements suite validates.","bmm","bmad/bmm/agents/tea.md"
+"tech-writer","paige","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient and supportive. Uses clear examples and analogies. Knows when to simplify vs when to be detailed. Celebrates good docs helps improve unclear ones.","Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code.","bmm","bmad/bmm/agents/tech-writer.md"
+"ux-designer","Sally","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Empathetic and user-focused. Uses storytelling for design decisions. Data-informed but creative. Advocates strongly for user needs and edge cases.","Every decision serves genuine user needs. Start simple evolve through feedback. Balance empathy with edge case attention. AI tools accelerate human-centered design.","bmm","bmad/bmm/agents/ux-designer.md"

.bmad/_cfg/agents/bmm-architect.customize.yaml

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

.bmad/_cfg/agents/bmm-dev.customize.yaml

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

.bmad/_cfg/agents/bmm-pm.customize.yaml

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

.bmad/_cfg/agents/bmm-sm.customize.yaml

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

.bmad/_cfg/agents/bmm-tea.customize.yaml

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

.bmad/_cfg/agents/bmm-tech-writer.customize.yaml

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

.bmad/_cfg/agents/bmm-ux-designer.customize.yaml

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

.bmad/_cfg/agents/core-bmad-master.customize.yaml

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

.bmad/_cfg/files-manifest.csv

@@ -0,0 +1,289 @@
+type,name,module,path,hash
+"csv","agent-manifest","_cfg","bmad/_cfg/agent-manifest.csv","862ee4c3ad7447b284553d049f621b263b8f51cd08dcf944a4cc419e41a2e618"
+"csv","task-manifest","_cfg","bmad/_cfg/task-manifest.csv","52fd8a292c670764d1613a423a1907e21e5d420281c3c9517834530765054c08"
+"csv","workflow-manifest","_cfg","bmad/_cfg/workflow-manifest.csv","b7050572626a3680ae0eaf39b8f226d63f58de2bb7c52bcd2268260dba61b1d6"
+"yaml","manifest","_cfg","bmad/_cfg/manifest.yaml","2ccef9d449c4346f7dbafb20cb6842bb97fceaaaa8c3c05253ffd3dacc208d7f"
+"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","4c9dd10936b348487f959b8b7552f56cf30f26d5aff7c3b83112e505b36f14f7"
+"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","772ca307a2a532c4bca3347749db9c6f1f8d4a1647658cb56ec19c3d70766d2d"
+"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","1465d2c1eea7b3d37b74107a198de893bd4f7e2670add78cd027ed33976ae14d"
+"md","checklist","bmb","bmad/bmb/workflows/convert-legacy/checklist.md","9a78192e6a0077275cdf66853a2d7ce6cf4748c944eef0bdc2647155fdff07fb"
+"md","checklist","bmb","bmad/bmb/workflows/create-agent/checklist.md","1caaf50fe01c5bbaf8d311b0218a19944620561d3dc3b1dbf2b4140aeb0683f3"
+"md","checklist","bmb","bmad/bmb/workflows/create-module/checklist.md","2426bad295560cdc8cd972465ce82f1f9aaabfd992727ed8294819edc71854cd"
+"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","821c90da14f02b967cb468b19f59a26c0d8f044d7a81a8b97631fb8ffac7648f"
+"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","3669cb91a34e2aba24bfec1eafb4bd1594de955ee266fb6cd8649e24fd86d17b"
+"md","instructions","bmb","bmad/bmb/workflows/create-agent/instructions.md","fb1a52d5934b7291b70934632507f725a132cb8da016891e05d2781a16e564a9"
+"md","instructions","bmb","bmad/bmb/workflows/create-module/instructions.md","a7cf67787e5d1abe9e980908ad2b492f84178dc6538a510f072153417938ab78"
+"md","instructions","bmb","bmad/bmb/workflows/create-workflow/instructions.md","cb4bbec63be3b7822b9ca2a4b854aa1bcda278193f87211090f690515a10fbfb"
+"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","092a88bd8eeda473e92f87d999a7a2a22479bb5501232d20db387dfe52250d41"
+"md","README","bmb","bmad/bmb/README.md","aa2beac1fb84267cbaa6d7eb541da824c34177a17cd227f11b189ab3a1e06d33"
+"md","README","bmb","bmad/bmb/workflows/convert-legacy/README.md","08cc7f23805e53c4f9ee57589fed90e5ac2835b058f89494d68933fe7d2c5e0e"
+"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","abedfdc607c4c1aaebec53aaddbbf077e91bb3fc78f0fd4fcabaae12c33002f5"
+"yaml","bmad-builder.agent","bmb","bmad/bmb/agents/bmad-builder.agent.yaml",""
+"yaml","config","bmb","bmad/bmb/config.yaml","25225c1376f0ca74fc151fa146cd02b8264a31184a1187d965d87b6a8eaef855"
+"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","default-party","bmm","bmad/bmm/teams/default-party.csv","92f7c52a3a1441e5139e11e91eddeb4f1bca83e73ddcd291ec36401a1f4c39db"
+"csv","documentation-requirements","bmm","bmad/bmm/workflows/document-project/documentation-requirements.csv","d1253b99e88250f2130516b56027ed706e643bfec3d99316727a4c6ec65c6c1d"
+"csv","domain-complexity","bmm","bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv","ed4d30e9fd87db2d628fb66cac7a302823ef6ebb3a8da53b9265326f10a54e11"
+"csv","pattern-categories","bmm","bmad/bmm/workflows/3-solutioning/architecture/pattern-categories.csv","d9a275931bfed32a65106ce374f2bf8e48ecc9327102a08f53b25818a8c78c04"
+"csv","project-types","bmm","bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv","30a52051db3f0e4ff0145b36cd87275e1c633bc6c25104a714c88341e28ae756"
+"csv","tea-index","bmm","bmad/bmm/testarch/tea-index.csv","23b0e383d06e039a77bb1611b168a2bb5323ed044619a592ac64e36911066c83"
+"json","project-scan-report-schema","bmm","bmad/bmm/workflows/document-project/templates/project-scan-report-schema.json","53255f15a10cab801a1d75b4318cdb0095eed08c51b3323b7e6c236ae6b399b7"
+"md","agents-guide","bmm","bmad/bmm/docs/agents-guide.md","d1466c9ac38ddceefc7598282699f0a469383909831f2a70227119c26a20d074"
+"md","analyst","bmm","bmad/bmm/agents/analyst.md","c5251d3e3bdd9d14d973b1286b1a7585f46f54ae8037ccd9a8451e922ce2da60"
+"md","architect","bmm","bmad/bmm/agents/architect.md","a8bb17d5a30fa9b7c60501239b6275b21f65cb709b53a68abda69f11e2f93cbe"
+"md","architecture-template","bmm","bmad/bmm/workflows/3-solutioning/architecture/architecture-template.md","a4908c181b04483c589ece1eb09a39f835b8a0dcb871cb624897531c371f5166"
+"md","atdd-checklist-template","bmm","bmad/bmm/workflows/testarch/atdd/atdd-checklist-template.md","9944d7b488669bbc6e9ef537566eb2744e2541dad30a9b2d9d4ae4762f66b337"
+"md","AUDIT-REPORT","bmm","bmad/bmm/workflows/4-implementation/dev-story/AUDIT-REPORT.md","1dc2f30299b35da8f659b3d8f2b0301bd2098fd90f1ea35364d752b0620259d0"
+"md","backlog_template","bmm","bmad/bmm/workflows/4-implementation/code-review/backlog_template.md","84b1381c05012999ff9a8b036b11c8aa2f926db4d840d256b56d2fa5c11f4ef7"
+"md","brownfield-guide","bmm","bmad/bmm/docs/brownfield-guide.md","083dbf565e3bbdbbb899b31fb201ec7e98e8cafbba4d5f539fe9019f3a21e8c7"
+"md","checklist","bmm","bmad/bmm/workflows/1-analysis/product-brief/checklist.md","d801d792e3cf6f4b3e4c5f264d39a18b2992a197bc347e6d0389cc7b6c5905de"
+"md","checklist","bmm","bmad/bmm/workflows/1-analysis/research/checklist.md","b5bce869ee1ffd1d7d7dee868c447993222df8ac85c4f5b18957b5a5b04d4499"
+"md","checklist","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md","1aa5bc2ad9409fab750ce55475a69ec47b7cdb5f4eac93b628bb5d9d3ea9dacb"
+"md","checklist","bmm","bmad/bmm/workflows/2-plan-workflows/prd/checklist.md","c9cbd451aea761365884ce0e47b86261cff5c72a6ffac2451123484b79dd93d1"
+"md","checklist","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/checklist.md","fea852e71365e1eb28f452ea7b8b19c7418ca1598c2ee22349ff9e9a7811fec8"
+"md","checklist","bmm","bmad/bmm/workflows/3-solutioning/architecture/checklist.md","aa0bd2bde20f45be77c5b43c38a1dfb90c41947ff8320f53150c5f8274680f14"
+"md","checklist","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/checklist.md","c458763b4f2f4e06e2663c111eab969892ee4e690a920b970603de72e0d9c025"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/code-review/checklist.md","549f958bfe0b28f33ed3dac7b76ea8f266630b3e67f4bda2d4ae85be518d3c89"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/correct-course/checklist.md","c02bdd4bf4b1f8ea8f7c7babaa485d95f7837818e74cef07486a20b31671f6f5"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/create-story/checklist.md","e3a636b15f010fc0c337e35c2a9427d4a0b9746f7f2ac5dda0b2f309f469f5d1"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/dev-story/checklist.md","77cecc9d45050de194300c841e7d8a11f6376e2fbe0a5aac33bb2953b1026014"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/checklist.md","630a0c5b75ea848a74532f8756f01ec12d4f93705a3f61fcde28bc42cdcb3cf3"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/checklist.md","80b10aedcf88ab1641b8e5f99c9a400c8fd9014f13ca65befc5c83992e367dd7"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/story-context/checklist.md","29f17f8b5c0c4ded3f9ca7020b5a950ef05ae3c62c3fadc34fc41b0c129e13ca"
+"md","checklist","bmm","bmad/bmm/workflows/document-project/checklist.md","54e260b60ba969ecd6ab60cb9928bc47b3733d7b603366e813eecfd9316533df"
+"md","checklist","bmm","bmad/bmm/workflows/testarch/atdd/checklist.md","c4fa594d949dd8f1f818c11054b28643b458ab05ed90cf65f118deb1f4818e9f"
+"md","checklist","bmm","bmad/bmm/workflows/testarch/automate/checklist.md","bf1ae220c15c9f263967d1606658b19adcd37d57aef2b0faa30d34f01e5b0d22"
+"md","checklist","bmm","bmad/bmm/workflows/testarch/ci/checklist.md","b0a6233b7d6423721aa551ad543fa708ede1343313109bdc0cbd37673871b410"
+"md","checklist","bmm","bmad/bmm/workflows/testarch/framework/checklist.md","d0f1008c374d6c2d08ba531e435953cf862cc280fcecb0cca8e9028ddeb961d1"
+"md","checklist","bmm","bmad/bmm/workflows/testarch/nfr-assess/checklist.md","044416df40402db39eb660509eedadafc292c16edc247cf93812f2a325ee032c"
+"md","checklist","bmm","bmad/bmm/workflows/testarch/test-design/checklist.md","17b95b1b316ab8d2fc9a2cd986ec5ef481cb4c285ea11651abd53c549ba762bb"
+"md","checklist","bmm","bmad/bmm/workflows/testarch/test-review/checklist.md","0626c675114c23019e20e4ae2330a64baba43ad11774ff268c027b3c584a0891"
+"md","checklist","bmm","bmad/bmm/workflows/testarch/trace/checklist.md","a4468ae2afa9cf676310ec1351bb34317d5390e4a02ded9684cc15a62f2fd4fd"
+"md","checklist-deep-prompt","bmm","bmad/bmm/workflows/1-analysis/research/checklist-deep-prompt.md","1aa3eb0dd454decd55e656d3b6ed8aafe39baa5a042b754fd84083cfd59d5426"
+"md","checklist-technical","bmm","bmad/bmm/workflows/1-analysis/research/checklist-technical.md","8f879eac05b729fa4d3536197bbc7cce30721265c5a81f8750698b27aa9ad633"
+"md","ci-burn-in","bmm","bmad/bmm/testarch/knowledge/ci-burn-in.md","de0092c37ea5c24b40a1aff90c5560bbe0c6cc31702de55d4ea58c56a2e109af"
+"md","component-tdd","bmm","bmad/bmm/testarch/knowledge/component-tdd.md","88bd1f9ca1d5bcd1552828845fe80b86ff3acdf071bac574eda744caf7120ef8"
+"md","contract-testing","bmm","bmad/bmm/testarch/knowledge/contract-testing.md","d8f662c286b2ea4772213541c43aebef006ab6b46e8737ebdc4a414621895599"
+"md","data-factories","bmm","bmad/bmm/testarch/knowledge/data-factories.md","d7428fe7675da02b6f5c4c03213fc5e542063f61ab033efb47c1c5669b835d88"
+"md","deep-dive-instructions","bmm","bmad/bmm/workflows/document-project/workflows/deep-dive-instructions.md","5df994e4e77a2a64f98fb7af4642812378f15898c984fb4f79b45fb2201f0000"
+"md","deep-dive-template","bmm","bmad/bmm/workflows/document-project/templates/deep-dive-template.md","6198aa731d87d6a318b5b8d180fc29b9aa53ff0966e02391c17333818e94ffe9"
+"md","dev","bmm","bmad/bmm/agents/dev.md","ade37e17b0172c7097eb224edbcde136f7346597529bf478154c6452058bde17"
+"md","documentation-standards","bmm","bmad/bmm/workflows/techdoc/documentation-standards.md","fc26d4daff6b5a73eb7964eacba6a4f5cf8f9810a8c41b6949c4023a4176d853"
+"md","email-auth","bmm","bmad/bmm/testarch/knowledge/email-auth.md","43f4cc3138a905a91f4a69f358be6664a790b192811b4dfc238188e826f6b41b"
+"md","enterprise-agentic-development","bmm","bmad/bmm/docs/enterprise-agentic-development.md","6e8fa4765da3344a23ae04882df8b0245b37c0a20616968f32487a908836a875"
+"md","epics-template","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md","d497e0f6db4411d8ee423c1cbbf1c0fa7bfe13ae5199a693c80b526afd417bb0"
+"md","epics-template","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md","bb05533e9c003a01edeff9553a7e9e65c255920668e1b71ad652b5642949fb69"
+"md","error-handling","bmm","bmad/bmm/testarch/knowledge/error-handling.md","8a314eafb31e78020e2709d88aaf4445160cbefb3aba788b62d1701557eb81c1"
+"md","faq","bmm","bmad/bmm/docs/faq.md","fc0592c32eef96a0003217c5e4f18bee821ff0d35895460819df91395225f083"
+"md","feature-flags","bmm","bmad/bmm/testarch/knowledge/feature-flags.md","f6db7e8de2b63ce40a1ceb120a4055fbc2c29454ad8fca5db4e8c065d98f6f49"
+"md","fixture-architecture","bmm","bmad/bmm/testarch/knowledge/fixture-architecture.md","a3b6c1bcaf5e925068f3806a3d2179ac11dde7149e404bc4bb5602afb7392501"
+"md","full-scan-instructions","bmm","bmad/bmm/workflows/document-project/workflows/full-scan-instructions.md","f51b4444c5a44f098ce49c4ef27a50715b524c074d08c41e7e8c982df32f38b9"
+"md","glossary","bmm","bmad/bmm/docs/glossary.md","1b8010c64dd92319b1104de818e97c0faca075496f7c0a4484509836857a589d"
+"md","index-template","bmm","bmad/bmm/workflows/document-project/templates/index-template.md","42c8a14f53088e4fda82f26a3fe41dc8a89d4bcb7a9659dd696136378b64ee90"
+"md","instructions","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md","91c7b5649b9cc99e3698d1a6b1abd17b7567f4478156c8666107946bc43e51a8"
+"md","instructions","bmm","bmad/bmm/workflows/1-analysis/domain-research/instructions.md","fb136f53c9f9c88ac54e810313eb8d1be43167adaeba6ada2a53f0861e558b16"
+"md","instructions","bmm","bmad/bmm/workflows/1-analysis/product-brief/instructions.md","3c21ceb9f83789ea7ab7866497008fece1e525a7877c19fa3167ff85b110de1b"
+"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md","2164a42dcd80ea7a95030974502e9c43b50c369f52c804ae0c5d3c26cc57bb71"
+"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md","916247ffcab63737bb9853348b4ac9212c5ab06d5caccdb83248f96bf81d29f6"
+"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/prd/instructions.md","22a7d64903948684b746131ed4eb29b83d848c21abf0f534ca8bb66e6c8070ce"
+"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md","51389527c9adcbd13f121314b9af0dda033f3aa98f04f1a5082e3b410e399747"
+"md","instructions","bmm","bmad/bmm/workflows/3-solutioning/architecture/instructions.md","6ea2b19232eb015008f990a48c9cb882216334af89996bcd7245c96ab3ca57b3"
+"md","instructions","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md","2d11c6d5fb71a4600d258fc9fa4e432d3638eca00f5c7f89be20d0d72a300ad0"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/code-review/instructions.md","2eb3c32afe60f0c53e9e973f505aeba2b2dfc0f5caffb3ae4a06a95971544632"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/correct-course/instructions.md","496d491641f4fd47579d50e8e435a37df7fc565e707c1fdfebbc931ba294b728"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/create-story/instructions.md","9d25311570f8fea94e5670521489947209e477fe6ca80e3ff4b9e60a43c52f4c"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/dev-story/instructions.md","715706691014a922f700542c12e0087895f7c5d03c6b2b33306447d3eb67475b"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/instructions.md","b97f601c655ba53f206c36791c8ecf41399dddc4a9712159378d95f46f24fe54"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/retrospective/instructions.md","2846289787a169f36d74a023930be6a4e16852aa2a41c980ca59bd79d89a58c7"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/instructions.md","9e2a26d84dc90f5153dcd9ca0ddcbfaaa5064e6d2b4b91dfd768de1f27ac577c"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-context/instructions.md","0655d1963591c118675b7c32b126f83bfc0abc5acf9fb3efae8ec2100cd46301"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-done/instructions.md","52163e1df2e75f1d34cad513b386ac73bada53784e827cca28d0ea9f05dc8ec4"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-ready/instructions.md","92e97b5803ba75883c995c5282aa90b7c4392e0d9c5fe0a5949ce432a3574813"
+"md","instructions","bmm","bmad/bmm/workflows/document-project/instructions.md","c67bd666382131bead7d4ace1ac6f0c9acd2d1d1b2a82314b4b90bda3a15eeb4"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/atdd/instructions.md","dcd052e78a069e9548d66ba679ed5db66e94b8ef5b3a02696837b77a641abcad"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/automate/instructions.md","8e6cb0167b14b345946bb7e46ab2fb02a9ff2faab9c3de34848e2d4586626960"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/ci/instructions.md","abdf97208c19d0cb76f9e5387613a730e56ddd90eb87523a8c8f1b03f20647a3"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/framework/instructions.md","936b9770dca2c65b38bc33e2e85ccf61e0b5722fc046eeae159a3efcbc361e30"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/nfr-assess/instructions.md","7de16907253721c8baae2612be35325c6fa543765377783763a09739fa71f072"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/test-design/instructions.md","878c45fd814f97a93fc0ee9d90e1454f0fa3c9e5a077033b6fd52eab6d7b506c"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/test-review/instructions.md","ab2f7adfd106652014a1573e2557cfd4c9d0f7017258d68abf8b1470ab82720e"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/trace/instructions.md","fe499a09c4bebbff0a0bce763ced2c36bee5c36b268a4abb4e964a309ff2fa20"
+"md","instructions","bmm","bmad/bmm/workflows/workflow-status/init/instructions.md","abaa96dc1de78d597e29439789ba540b891dc117e013e0c706c000469af2fc31"
+"md","instructions","bmm","bmad/bmm/workflows/workflow-status/instructions.md","1faa787f278a2ee95b418e82475be6f24a09f4bb566f5544c8585ed410cf62b2"
+"md","instructions-deep-prompt","bmm","bmad/bmm/workflows/1-analysis/research/instructions-deep-prompt.md","0f06e808bb5793e4a4ec59cf8c6a3ad53e822c2aa0f0ccef6406d26bd1fa08f7"
+"md","instructions-level0-story","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md","d151a30816d6231fbd8b44e6d3503a986b4344dd03fc756670002adc501b0cda"
+"md","instructions-level1-stories","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md","849f9c055584c895a8778c9a916c5db777fdac575f709c40ddda660450190ed6"
+"md","instructions-market","bmm","bmad/bmm/workflows/1-analysis/research/instructions-market.md","ecd2315e72edb569f46e94f5958fac115b44807cab769a3e55c3b80e58136447"
+"md","instructions-router","bmm","bmad/bmm/workflows/1-analysis/research/instructions-router.md","a55dae293e8a97fc6f6672cd57f3d1f7c94802954c9124a8cc4eec12fb667c71"
+"md","instructions-technical","bmm","bmad/bmm/workflows/1-analysis/research/instructions-technical.md","47b653bd61f6a3fe4ba89b53a7b8a9383560adfce6bf8acf24f6acc594eceb44"
+"md","network-first","bmm","bmad/bmm/testarch/knowledge/network-first.md","2920e58e145626f5505bcb75e263dbd0e6ac79a8c4c2ec138f5329e06a6ac014"
+"md","nfr-criteria","bmm","bmad/bmm/testarch/knowledge/nfr-criteria.md","e63cee4a0193e4858c8f70ff33a497a1b97d13a69da66f60ed5c9a9853025aa1"
+"md","nfr-report-template","bmm","bmad/bmm/workflows/testarch/nfr-assess/nfr-report-template.md","b1d8fcbdfc9715a285a58cb161242dea7d311171c09a2caab118ad8ace62b80c"
+"md","party-mode","bmm","bmad/bmm/docs/party-mode.md","7acadc96c7235695a88cba42b5642e1ee3a7f96eb2264862f629e1d4280b9761"
+"md","playwright-config","bmm","bmad/bmm/testarch/knowledge/playwright-config.md","42516511104a7131775f4446196cf9e5dd3295ba3272d5a5030660b1dffaa69f"
+"md","pm","bmm","bmad/bmm/agents/pm.md","edef9620a64c8aa357f565495195179bbaaeea31d153f17fe1d03973cd51017f"
+"md","prd-template","bmm","bmad/bmm/workflows/2-plan-workflows/prd/prd-template.md","cf79921e432b992048af21cb4c87ca5cbc14cdf6e279324b3d5990a7f2366ec4"
+"md","probability-impact","bmm","bmad/bmm/testarch/knowledge/probability-impact.md","446dba0caa1eb162734514f35366f8c38ed3666528b0b5e16c7f03fd3c537d0f"
+"md","project-context","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/project-context.md","0f1888da4bfc4f24c4de9477bd3ccb2a6fb7aa83c516dfdc1f98fbd08846d4ba"
+"md","project-overview-template","bmm","bmad/bmm/workflows/document-project/templates/project-overview-template.md","a7c7325b75a5a678dca391b9b69b1e3409cfbe6da95e70443ed3ace164e287b2"
+"md","quick-spec-flow","bmm","bmad/bmm/docs/quick-spec-flow.md","215d508d27ea94e0091fc32f8dce22fadf990b3b9d8b397e2c393436934f85af"
+"md","quick-start","bmm","bmad/bmm/docs/quick-start.md","88946558a87bd2eb38990cff74f29b6ef4f81db6f961500f9ca626d168cd0fce"
+"md","README","bmm","bmad/bmm/README.md","ad4e6d0c002e3a5fef1b695bda79e245fe5a43345375c699165b32d6fc511457"
+"md","README","bmm","bmad/bmm/docs/README.md","27a835cbc5ed50e4b076d8f0d9454c8e6b6826e69d72ec010df904e891023493"
+"md","risk-governance","bmm","bmad/bmm/testarch/knowledge/risk-governance.md","2fa2bc3979c4f6d4e1dec09facb2d446f2a4fbc80107b11fc41cbef2b8d65d68"
+"md","scale-adaptive-system","bmm","bmad/bmm/docs/scale-adaptive-system.md","f1bdaac7e6cf96dc115d8fd86c7dc499892ad745a1330221fedbaae1188c6a24"
+"md","selective-testing","bmm","bmad/bmm/testarch/knowledge/selective-testing.md","c14c8e1bcc309dbb86a60f65bc921abf5a855c18a753e0c0654a108eb3eb1f1c"
+"md","selector-resilience","bmm","bmad/bmm/testarch/knowledge/selector-resilience.md","a55c25a340f1cd10811802665754a3f4eab0c82868fea61fea9cc61aa47ac179"
+"md","sm","bmm","bmad/bmm/agents/sm.md","957f431bac1a60c750bc4c84064f80280f9ff53426f4f46b11702e0ab64d8476"
+"md","source-tree-template","bmm","bmad/bmm/workflows/document-project/templates/source-tree-template.md","109bc335ebb22f932b37c24cdc777a351264191825444a4d147c9b82a1e2ad7a"
+"md","tea","bmm","bmad/bmm/agents/tea.md","f77345c6c5393da31b8045c6d3a4af636de100d20d4a9fec96a949e9c12aaf91"
+"md","tech-spec-template","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/tech-spec-template.md","2b07373b7b23f71849f107b8fd4356fef71ba5ad88d7f333f05547da1d3be313"
+"md","tech-writer","bmm","bmad/bmm/agents/tech-writer.md","a5925b4be760cee6b91c2997b8ec224d7889f2a97b6fb91c13ad8ee707b8b3e3"
+"md","template","bmm","bmad/bmm/workflows/1-analysis/domain-research/template.md","5606843f77007d886cc7ecf1fcfddd1f6dfa3be599239c67eff1d8e40585b083"
+"md","template","bmm","bmad/bmm/workflows/1-analysis/product-brief/template.md","96f89df7a4dabac6400de0f1d1abe1f2d4713b76fe9433f31c8a885e20d5a5b4"
+"md","template","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/template.md","11c3b7573991c001a7f7780daaf5e5dfa4c46c3ea1f250c5bbf86c5e9f13fc8b"
+"md","template","bmm","bmad/bmm/workflows/4-implementation/create-story/template.md","83c5d21312c0f2060888a2a8ba8332b60f7e5ebeb9b24c9ee59ba96114afb9c9"
+"md","template","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/template.md","b5c5d0686453b7c9880d5b45727023f2f6f8d6e491b47267efa8f968f20074e3"
+"md","template-deep-prompt","bmm","bmad/bmm/workflows/1-analysis/research/template-deep-prompt.md","2e65c7d6c56e0fa3c994e9eb8e6685409d84bc3e4d198ea462fa78e06c1c0932"
+"md","template-market","bmm","bmad/bmm/workflows/1-analysis/research/template-market.md","e5e59774f57b2f9b56cb817c298c02965b92c7d00affbca442366638cd74d9ca"
+"md","template-technical","bmm","bmad/bmm/workflows/1-analysis/research/template-technical.md","78caa56ba6eb6922925e5aab4ed4a8245fe744b63c245be29a0612135851f4ca"
+"md","test-architecture","bmm","bmad/bmm/docs/test-architecture.md","13342dd006b91cd445dcf5a868541b1cf59b40022227e8c87b66669862e993bf"
+"md","test-design-template","bmm","bmad/bmm/workflows/testarch/test-design/test-design-template.md","cbbc3e3d097dfd31784b9447d07b4b4f4c63dadf2ba0968671ec862da8c30d27"
+"md","test-healing-patterns","bmm","bmad/bmm/testarch/knowledge/test-healing-patterns.md","b44f7db1ebb1c20ca4ef02d12cae95f692876aee02689605d4b15fe728d28fdf"
+"md","test-levels-framework","bmm","bmad/bmm/testarch/knowledge/test-levels-framework.md","80bbac7959a47a2e7e7de82613296f906954d571d2d64ece13381c1a0b480237"
+"md","test-priorities-matrix","bmm","bmad/bmm/testarch/knowledge/test-priorities-matrix.md","321c3b708cc19892884be0166afa2a7197028e5474acaf7bc65c17ac861964a5"
+"md","test-quality","bmm","bmad/bmm/testarch/knowledge/test-quality.md","97b6db474df0ec7a98a15fd2ae49671bb8e0ddf22963f3c4c47917bb75c05b90"
+"md","test-review-template","bmm","bmad/bmm/workflows/testarch/test-review/test-review-template.md","3e68a73c48eebf2e0b5bb329a2af9e80554ef443f8cd16652e8343788f249072"
+"md","timing-debugging","bmm","bmad/bmm/testarch/knowledge/timing-debugging.md","c4c87539bbd3fd961369bb1d7066135d18c6aad7ecd70256ab5ec3b26a8777d9"
+"md","trace-template","bmm","bmad/bmm/workflows/testarch/trace/trace-template.md","5453a8e4f61b294a1fc0ba42aec83223ae1bcd5c33d7ae0de6de992e3ee42b43"
+"md","user-story-template","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md","4b179d52088745060991e7cfd853da7d6ce5ac0aa051118c9cecea8d59bdaf87"
+"md","ux-design-template","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md","f9b8ae0fe08c6a23c63815ddd8ed43183c796f266ffe408f3426af1f13b956db"
+"md","ux-designer","bmm","bmad/bmm/agents/ux-designer.md","5a1ce1b47a4f67b25dd464a94a8149bc86b7690b585738dcfbf273a0a035c7ea"
+"md","visual-debugging","bmm","bmad/bmm/testarch/knowledge/visual-debugging.md","072a3d30ba6d22d5e628fc26a08f6e03f8b696e49d5a4445f37749ce5cd4a8a9"
+"md","workflow-architecture-reference","bmm","bmad/bmm/docs/workflow-architecture-reference.md","ce6c43a7f90e7b31655dd1bc9632cda700e105315f5ef25067319792274b2283"
+"md","workflow-document-project-reference","bmm","bmad/bmm/docs/workflow-document-project-reference.md","464819d23cc4bc88b20c8a668669ae7a6bc7bcb5e4aaa1d0f0998f35ff7ad8df"
+"md","workflows-analysis","bmm","bmad/bmm/docs/workflows-analysis.md","4dd00c829adcf881ecb96e083f754a4ce109159cfdaff8a5a856590ba33f1d74"
+"md","workflows-implementation","bmm","bmad/bmm/docs/workflows-implementation.md","d9d22fd7e11a5586f4c93d38f88fd93e4203d31d3388ad2d0de439cc8d35df79"
+"md","workflows-planning","bmm","bmad/bmm/docs/workflows-planning.md","b713c4b5c3275daa8285fa5e8a18d9e2b6d38c66cbb77e302c15b40ea9bb3029"
+"md","workflows-solutioning","bmm","bmad/bmm/docs/workflows-solutioning.md","193b6bfdafcf802b9ff6f39d1bea4fe09d788e3b2bbfe9ff034019c9a3fba696"
+"xml","context-template","bmm","bmad/bmm/workflows/4-implementation/story-context/context-template.xml","582374f4d216ba60f1179745b319bbc2becc2ac92d7d8a19ac3273381a5c2549"
+"xml","daily-standup","bmm","bmad/bmm/tasks/daily-standup.xml","e7260fff0437543d980ba0aa031169a2fcbbcb82283d722fd62bae063ffdfa7a"
+"yaml","analyst.agent","bmm","bmad/bmm/agents/analyst.agent.yaml",""
+"yaml","architect.agent","bmm","bmad/bmm/agents/architect.agent.yaml",""
+"yaml","architecture-patterns","bmm","bmad/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml","9394c1e632e01534f7a1afd676de74b27f1868f58924f21b542af3631679c552"
+"yaml","config","bmm","bmad/bmm/config.yaml","5c70cc87f606b834885744f468071c37726736de18a20dec40dc7a88012a61e1"
+"yaml","decision-catalog","bmm","bmad/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml","f7fc2ed6ec6c4bd78ec808ad70d24751b53b4835e0aad1088057371f545d3c82"
+"yaml","deep-dive","bmm","bmad/bmm/workflows/document-project/workflows/deep-dive.yaml","c401fb8d94ca96f3bb0ccc1146269e1bfa4ce4eadab52bd63c7fcff6c2f26216"
+"yaml","dev.agent","bmm","bmad/bmm/agents/dev.agent.yaml",""
+"yaml","enterprise-brownfield","bmm","bmad/bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml","8b81f8b51f6575b92f8b490694e5f538aad9644c86119ccd6e2b727c7c232ef7"
+"yaml","enterprise-greenfield","bmm","bmad/bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml","040727a03c69aac1ac980ec3d708f7e64f083640fe1e724b3f09b9880f400e5a"
+"yaml","full-scan","bmm","bmad/bmm/workflows/document-project/workflows/full-scan.yaml","3d2e620b58902ab63e2d83304180ecd22ba5ab07183b3afb47261343647bde6f"
+"yaml","game-design","bmm","bmad/bmm/workflows/workflow-status/paths/game-design.yaml","f5228c1cd593348f03824535e19a6c41b926a49a0c63ca320a2cd2e0d8b11976"
+"yaml","github-actions-template","bmm","bmad/bmm/workflows/testarch/ci/github-actions-template.yaml","28c0de7c96481c5a7719596c85dd0ce8b5dc450d360aeaa7ebf6294dcf4bea4c"
+"yaml","gitlab-ci-template","bmm","bmad/bmm/workflows/testarch/ci/gitlab-ci-template.yaml","bc83b9240ad255c6c2a99bf863b9e519f736c99aeb4b1e341b07620d54581fdc"
+"yaml","injections","bmm","bmad/bmm/workflows/1-analysis/research/claude-code/injections.yaml","dd6dd6e722bf661c3c51d25cc97a1e8ca9c21d517ec0372e469364ba2cf1fa8b"
+"yaml","method-brownfield","bmm","bmad/bmm/workflows/workflow-status/paths/method-brownfield.yaml","6f4c6b508d3af2eba1409d48543e835d07ec4d453fa34fe53a2c7cbb91658969"
+"yaml","method-greenfield","bmm","bmad/bmm/workflows/workflow-status/paths/method-greenfield.yaml","1eb8232eca4cb915acecbc60fe3495c6dcc8d2241393ee42d62b5f491d7c223e"
+"yaml","pm.agent","bmm","bmad/bmm/agents/pm.agent.yaml",""
+"yaml","project-levels","bmm","bmad/bmm/workflows/workflow-status/project-levels.yaml","414b9aefff3cfe864e8c14b55595abfe3157fd20d9ee11bb349a2b8c8e8b5449"
+"yaml","quick-flow-brownfield","bmm","bmad/bmm/workflows/workflow-status/paths/quick-flow-brownfield.yaml","0d8837a07efaefe06b29c1e58fee982fafe6bbb40c096699bd64faed8e56ebf8"
+"yaml","quick-flow-greenfield","bmm","bmad/bmm/workflows/workflow-status/paths/quick-flow-greenfield.yaml","c6eae1a3ef86e87bd48a285b11989809526498dc15386fa949279f2e77b011d5"
+"yaml","sample-level-3-workflow","bmm","bmad/bmm/workflows/workflow-status/sample-level-3-workflow.yaml","036b27d39d3a845abed38725d816faca1452651c0b90f30f6e3adc642c523c6f"
+"yaml","sm.agent","bmm","bmad/bmm/agents/sm.agent.yaml",""
+"yaml","sprint-status-template","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml","314af29f980b830cc2f67b32b3c0c5cc8a3e318cc5b2d66ff94540e5c80e3aca"
+"yaml","tea.agent","bmm","bmad/bmm/agents/tea.agent.yaml",""
+"yaml","team-fullstack","bmm","bmad/bmm/teams/team-fullstack.yaml","da8346b10dfad8e1164a11abeb3b0a84a1d8b5f04e01e8490a44ffca477a1b96"
+"yaml","tech-writer.agent","bmm","bmad/bmm/agents/tech-writer.agent.yaml",""
+"yaml","ux-designer.agent","bmm","bmad/bmm/agents/ux-designer.agent.yaml",""
+"yaml","validation-criteria","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/validation-criteria.yaml","d690edf5faf95ca1ebd3736e01860b385b05566da415313d524f4db12f9a5af4"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml","38d859ea65db2cc2eebb0dbf1679711dad92710d8da2c2d9753b852055abd970"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/domain-research/workflow.yaml","03ecc394a1a6f1e345e95173231b981e7acb09d0017560727327090c44b7de35"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml","69c3ec3a42e638d44ccae5e0cf6e068e67f4689f3692d1efac184152e27698a8"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/research/workflow.yaml","3489d4989ad781f67909269e76b439122246d667d771cbb64988e4624ee2572a"
+"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml","f9e680c0d7fdecf691dd9eecb0792f232f00cc5cdee18b3aa9946e5766e876d5"
+"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml","96645d267020a88d8bfe83ab893ffcb47d9ce7b2b69093db63026b9f76eaa517"
+"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml","292c2273f1b22fe16f2a4c602db68b7adb3affa77dfaeb26f801676edc288b73"
+"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml","d9b6e9405f44de954f83c2328a95a4e10479c292b84ed28a756f5712fc12be17"
+"yaml","workflow","bmm","bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml","3ff2ce0d789e1dd73e4427aada3853ac5532cb054559d70f1bc933087e69f4e1"
+"yaml","workflow","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml","f17268e08ec2b63cf2d109ee42269223117d0330728e960d1105106efd8462b4"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/code-review/workflow.yaml","37215c77c85ffcdcd96f564746e211962f8eeae306c7b8d01d94815cbd252f65"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml","79663be356876f0734dc24349c2db14a0f27ab53eb635e2ca22d052ccf88ca06"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","feb4206ccdb08021fa40d241135b019b69459ff6cc9e68faccb3ceebf6322b46"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml","cef3d12648ba38aa41662490101516384c9b9cd13b0119a7b2f0b0e563e8b1c6"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml","f953cd7cf84d6065e31eeec848fadf3b829fc5e98a2f20c12a4042c30091df34"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","183de1c1156a9c0787ec31dc1def2ded490735a21c82c85635b24044946b0ae4"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml","47a933e12162326a9258603501f446b27cebdd0f5a6fa19ff5ea00e579decc27"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","06d034ec9b60a97f5e268920f13afbafae495331b54353d144daf0c5a91181e5"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-done/workflow.yaml","fa709f77a94b94cf1051cc66e12e1cdc4dfc10100884d47a86dbbe62702288c7"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml","9cef1dbb6d437cb280d5566e0a56d40da1f84a7cb34ad887318deeb6a2a5f544"
+"yaml","workflow","bmm","bmad/bmm/workflows/document-project/workflow.yaml","36b65f562bb94eb819728d819e66fd5a23d1b98d1766050c998fd6feaf3df8f6"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/atdd/workflow.yaml","06474fa7f23657d4145a214771a68e7d894e4488cc5a82c943dad765601f48be"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/automate/workflow.yaml","e733691f1613e6c55d28a42f745cf396a6f62b62968ff9c42cdb53b2ac3cadcb"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/ci/workflow.yaml","87ca4dceeaa74f6c151d4add6541ed9b8376aa3015c9e4532c8bfc1b93e0abe9"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/framework/workflow.yaml","e2efafaeabfe9c608df7545e442f25e0518e50b9b48d5bcef61cf5e0b1daadb0"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml","5bf4a2dede46943bb449ac51cc07335d350cfb8a270f82fffbe5fae921ac6d72"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/test-design/workflow.yaml","581e91cb914a02b9ae79d1d139264e1dfba663072b6d09dca3250720835fdc60"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/test-review/workflow.yaml","7c05fab368e2211c97bc9ba92556d6047de4535a28792731215151ef8bf497c5"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/trace/workflow.yaml","51c96a9c007ca3ef2d39fa199f2d8c7cb33506b20775ef51f80624fc272cd66f"
+"yaml","workflow","bmm","bmad/bmm/workflows/workflow-status/init/workflow.yaml","01aae9499f50a40dbbd0018308f3ae016b4d62de3de22d06d2402bdc1a6471a5"
+"yaml","workflow","bmm","bmad/bmm/workflows/workflow-status/workflow.yaml","6a1ad67ec954660fd8e7433b55ab3b75e768f7efa33aad36cf98cdbc2ef6575b"
+"yaml","workflow-status-template","bmm","bmad/bmm/workflows/workflow-status/workflow-status-template.yaml","6021202726d2b81f28908ffeb93330d25bcd52986823200e01b814d67c1677dd"
+"csv","adv-elicit-methods","core","bmad/core/tasks/adv-elicit-methods.csv","b4e925870f902862899f12934e617c3b4fe002d1b652c99922b30fa93482533b"
+"csv","brain-methods","core","bmad/core/workflows/brainstorming/brain-methods.csv","ecffe2f0ba263aac872b2d2c95a3f7b1556da2a980aa0edd3764ffb2f11889f3"
+"md","bmad-master","core","bmad/core/agents/bmad-master.md","906028c592f49b6b9962c7efa63535b069b731237d28617a56434d061210d02a"
+"md","instructions","core","bmad/core/workflows/brainstorming/instructions.md","f737f1645d0f7af37fddd1d4ac8a387f26999d0be5748ce41bdbcf2b89738413"
+"md","instructions","core","bmad/core/workflows/party-mode/instructions.md","768a835653fea54cbf4f7136e19f968add5ccf4b1dbce5636c5268d74b1b7181"
+"md","README","core","bmad/core/workflows/brainstorming/README.md","92d624c9ec560297003db0616671fbd6c278d9ea3dacf1c6cf41f064bacec926"
+"md","template","core","bmad/core/workflows/brainstorming/template.md","b5c760f4cea2b56c75ef76d17a87177b988ac846657f4b9819ec125d125b7386"
+"xml","adv-elicit","core","bmad/core/tasks/adv-elicit.xml","4f45442af426a269c0af709348efe431e335ff45bb8eda7d01e7d100c57e03b9"
+"xml","bmad-web-orchestrator.agent","core","bmad/core/agents/bmad-web-orchestrator.agent.xml","ac09744c3ad70443fbe6873d6a1345c09ad4ab1fe3e310e3230c912967cb51e9"
+"xml","index-docs","core","bmad/core/tasks/index-docs.xml","c6a9d79628fd1246ef29e296438b238d21c68f50eadb16219ac9d6200cf03628"
+"xml","shard-doc","core","bmad/core/tools/shard-doc.xml","f2ec685bd3f9ca488c47c494b344b8cff1854d5439c7207182e08ecfa0bb4a07"
+"xml","validate-workflow","core","bmad/core/tasks/validate-workflow.xml","63580411c759ee317e58da8bda6ceba27dbf9d3742f39c5c705afcd27361a9ee"
+"xml","workflow","core","bmad/core/tasks/workflow.xml","f7500bdc26a0d4630674000788d9dbc376b03347aea221b90afcdbb0a1e569d7"
+"yaml","bmad-master.agent","core","bmad/core/agents/bmad-master.agent.yaml",""
+"yaml","config","core","bmad/core/config.yaml","1b581a5489df69af7425c5ab4730e78fcc720d9e886b7e8cf13d03015229d536"
+"yaml","workflow","core","bmad/core/workflows/brainstorming/workflow.yaml","0af588d7096facdd79c701b37463b6a0e497b0b4339a951d7d3342d8a48fe6c1"
+"yaml","workflow","core","bmad/core/workflows/party-mode/workflow.yaml","5b5bd943eaa96b573ca1fce4120d17fab7e766a9204dd43c899ec2cc4b0561f6"

.bmad/_cfg/ides/claude-code.yaml

@@ -0,0 +1,7 @@
+ide: claude-code
+configured_date: "2025-11-09T05:23:00.281Z"
+last_updated: "2025-11-09T05:23:00.281Z"
+configuration:
+  subagentChoices:
+    install: none
+  installLocation: null

.bmad/_cfg/manifest.yaml

@@ -0,0 +1,10 @@
+installation:
+  version: 6.0.0-alpha.7
+  installDate: "2025-11-09T05:23:00.252Z"
+  lastUpdated: "2025-11-09T05:23:00.252Z"
+modules:
+  - core
+  - bmb
+  - bmm
+ides:
+  - claude-code

.bmad/_cfg/task-manifest.csv

@@ -0,0 +1,6 @@
+name,displayName,description,module,path,standalone
+"adv-elicit","Advanced Elicitation","When called from workflow","core","bmad/core/tasks/adv-elicit.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"
+"daily-standup","Daily Standup","","bmm","bmad/bmm/tasks/daily-standup.xml","false"

.bmad/_cfg/tool-manifest.csv

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

.bmad/_cfg/workflow-manifest.csv

@@ -0,0 +1,44 @@
+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"
+"brainstorm-project","Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml","true"
+"domain-research","Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects","bmm","bmad/bmm/workflows/1-analysis/domain-research/workflow.yaml","true"
+"product-brief","Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration","bmm","bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml","true"
+"research","Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis","bmm","bmad/bmm/workflows/1-analysis/research/workflow.yaml","true"
+"create-ux-design","Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step.","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml","true"
+"create-epics-and-stories","Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml","true"
+"prd","Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.","bmm","bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml","true"
+"tech-spec","Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed.","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml","true"
+"architecture","Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.","bmm","bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml","true"
+"solutioning-gate-check","Systematically validate that all planning and solutioning phases are complete and properly aligned before transitioning to Phase 4 implementation. Ensures PRD, architecture, and stories are cohesive with no gaps or contradictions.","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml","true"
+"code-review","Perform a Senior Developer code review on a completed story flagged Ready for Review, leveraging story-context, epic tech-spec, repo docs, MCP servers for latest best-practices, and web search as fallback. Appends structured review notes to the story.","bmm","bmad/bmm/workflows/4-implementation/code-review/workflow.yaml","true"
+"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml","true"
+"create-story","Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","true"
+"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml","true"
+"epic-tech-context","Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml","true"
+"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","true"
+"sprint-planning","Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml","true"
+"story-context","Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","true"
+"story-done","Marks a story as done (DoD complete) and moves it from its current status → DONE in the status file. Advances the story queue. Simple status-update workflow with no searching required.","bmm","bmad/bmm/workflows/4-implementation/story-done/workflow.yaml","true"
+"story-ready","Marks a drafted story as ready for development and moves it from TODO → IN PROGRESS in the status file. Simple status-update workflow with no searching required.","bmm","bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml","true"
+"document-project","Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development","bmm","bmad/bmm/workflows/document-project/workflow.yaml","true"
+"testarch-atdd","Generate failing acceptance tests before implementation using TDD red-green-refactor cycle","bmm","bmad/bmm/workflows/testarch/atdd/workflow.yaml","false"
+"testarch-automate","Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite","bmm","bmad/bmm/workflows/testarch/automate/workflow.yaml","false"
+"testarch-ci","Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection","bmm","bmad/bmm/workflows/testarch/ci/workflow.yaml","false"
+"testarch-framework","Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration","bmm","bmad/bmm/workflows/testarch/framework/workflow.yaml","false"
+"testarch-nfr","Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation","bmm","bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml","false"
+"testarch-test-design","Plan risk mitigation and test coverage strategy before development with risk assessment and prioritization","bmm","bmad/bmm/workflows/testarch/test-design/workflow.yaml","false"
+"testarch-test-review","Review test quality using comprehensive knowledge base and best practices validation","bmm","bmad/bmm/workflows/testarch/test-review/workflow.yaml","false"
+"testarch-trace","Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)","bmm","bmad/bmm/workflows/testarch/trace/workflow.yaml","false"
+"workflow-init","Initialize a new BMM project by determining level, type, and creating workflow path","bmm","bmad/bmm/workflows/workflow-status/init/workflow.yaml","true"
+"workflow-status","Lightweight status checker - answers ""what should I do now?"" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.","bmm","bmad/bmm/workflows/workflow-status/workflow.yaml","true"

.bmad/bmb/agents/bmad-builder.md

@@ -6,11 +6,11 @@ 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="🧙">
+<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/bmb/config.yaml NOW
+      - 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>
@@ -28,7 +28,7 @@ You must fully embody this agent's persona and follow all activation instruction
       <handlers>
   <handler type="workflow">
     When menu item has: workflow="path/to/workflow.yaml"
-    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
+    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
@@ -55,15 +55,15 @@ You must fully embody this agent's persona and follow all activation instruction
   </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="*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>

.bmad/bmb/config.yaml

@@ -0,0 +1,16 @@
+# BMB Module Configuration
+# Generated by BMAD installer
+# Version: 6.0.0-alpha.7
+# Date: 2025-11-09T05:23:00.243Z
+
+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: false

.bmad/bmb/workflows/audit-workflow/checklist.md

@@ -45,7 +45,7 @@
 ## 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})
+- [ ] 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)
@@ -53,7 +53,7 @@
 - [ ] 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
+- [ ] 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

.bmad/bmb/workflows/audit-workflow/instructions.md

@@ -1,7 +1,7 @@
 # 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>
+<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>
 
@@ -33,7 +33,7 @@
 
     **Required variables:**
 
-    - `config_source: "{project-root}/bmad/[module]/config.yaml"`
+    - `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"`
@@ -182,7 +182,7 @@
 
       **Path Validation:**
 
-      - [ ] All paths use bmad/-relative format (NOT {project-root})
+      - [ ] All paths use .bmad/-relative format (NOT {project-root})
       - [ ] No {config_source} variables in web_bundle section
       - [ ] Paths match actual file locations
 
@@ -200,7 +200,7 @@
       <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>
+      <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>

.bmad/bmb/workflows/audit-workflow/workflow.yaml

@@ -4,14 +4,14 @@ description: "Comprehensive workflow quality audit - validates structure, config
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
+installed_path: "{project-root}/.bmad/bmb/workflows/audit-workflow"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

.bmad/bmb/workflows/convert-legacy/README.md

@@ -84,7 +84,7 @@ convert-legacy/
 - 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
+- Ensures all paths use `{project-root}/.bmad/` format
 
 ### Phase 2: Conversion Strategy (Step 4)
 
@@ -126,7 +126,7 @@ convert-legacy/
 **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/adv-elicit.xml</invoke-task>` tags
+- Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>` tags
 - Transforms conditional sections to flow control
 - Creates proper template.md from content structure
 - Integrates v4 create-doc.md task patterns
@@ -218,7 +218,7 @@ Converted items follow v6 conventions:
 
 **Issue**: Path conversion errors
 
-- **Solution**: Ensure all references use `{project-root}/bmad/` format
+- **Solution**: Ensure all references use `{project-root}/.bmad/` format
 - **Check**: Review conversion mappings for proper path patterns
 
 **Issue**: Sub-workflow invocation fails
@@ -252,8 +252,8 @@ To customize this workflow:
 
 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`
+- 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
 

.bmad/bmb/workflows/convert-legacy/checklist.md

@@ -37,7 +37,7 @@
 - [ ] 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/
+- [ ] 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
@@ -48,7 +48,7 @@
 - [ ] 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/adv-elicit.xml</invoke-task>
+- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
 - [ ] Conditional sections preserved with if="" attributes
 - [ ] Repeatable sections converted to repeat="" attributes
 

.bmad/bmb/workflows/convert-legacy/instructions.md

@@ -1,7 +1,7 @@
 # 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>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>
@@ -70,8 +70,8 @@ For Modules:
 <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>
+<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>
 
@@ -150,16 +150,16 @@ For Modules:
    - 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/
+   - 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"
+- 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>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>
@@ -172,7 +172,7 @@ For Modules:
 - Any special behaviors
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-agent/workflow.yaml
+  workflow: {project-root}/.bmad/bmb/workflows/create-agent/workflow.yaml
   inputs:
     - agent_name: {{extracted_name}}
     - agent_purpose: {{extracted_purpose}}
@@ -193,7 +193,7 @@ For Modules:
 
 2. Convert template sections to instructions.md:
    - Each YAML section → workflow step
-   - `elicit: true` → `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` tag
+   - `elicit: true` → `<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>` tag
    - Conditional sections → `if="condition"` attribute
    - Repeatable sections → `repeat="for-each"` attribute
    - Section instructions → step content
@@ -212,7 +212,7 @@ For Modules:
 
 ```yaml
 # Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+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'
@@ -220,7 +220,7 @@ date: system-generated
 ```
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
+  workflow: {project-root}/.bmad/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{template_name}}
     - workflow_type: document
@@ -239,7 +239,7 @@ date: system-generated
 <action>Create module blueprint with all components</action>
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-module/workflow.yaml
+  workflow: {project-root}/.bmad/bmb/workflows/create-module/workflow.yaml
   inputs:
     - module_name: {{module_name}}
     - components: {{component_list}}
@@ -277,7 +277,7 @@ date: system-generated
    </check>
 
 4. Handle special v4 patterns:
-   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
    - Agent permissions → note in instructions
    - YOLO mode → autonomous flag or optional steps
    - Critical notices → workflow.yaml comments
@@ -286,7 +286,7 @@ date: system-generated
 
 ```yaml
 # Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+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'
@@ -294,7 +294,7 @@ date: system-generated
 ```
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
+  workflow: {project-root}/.bmad/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{task_name}}
     - workflow_type: {{confirmed_workflow_type}}

.bmad/bmb/workflows/convert-legacy/workflow.yaml

@@ -4,7 +4,7 @@ description: "Converts legacy BMAD v4 or similar items (agents, workflows, modul
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
@@ -15,18 +15,18 @@ 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"
+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}}"
+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"
+  - 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

.bmad/bmb/workflows/create-agent/README.md

@@ -86,20 +86,20 @@ workflow create-agent
 
 **Standalone Agents:**
 
-- Source: `bmad/agents/{filename}.agent.yaml`
-- Compiled: `bmad/agents/{filename}.md`
+- 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`
+- Compiled: `.bmad/{module}/agents/{filename}.md`
 
 ### YAML Structure
 
 ```yaml
 agent:
   metadata:
-    id: bmad/{module}/agents/{filename}.md
+    id: .bmad/{module}/agents/{filename}.md
     name: Agent Name
     title: Agent Title
     icon: 🤖
@@ -117,7 +117,7 @@ agent:
 
 ### Optional Customize File
 
-Location: `bmad/_cfg/agents/{module}-{filename}.customize.yaml`
+Location: `.bmad/_cfg/agents/{module}-{filename}.customize.yaml`
 
 Allows persona and menu overrides that persist through updates.
 

.bmad/bmb/workflows/create-agent/agent-architecture.md

@@ -31,7 +31,7 @@ _LLM-Optimized Technical Documentation for Agent Building_
 
 **Required Attributes:**
 
-- `id` - Unique path identifier (e.g., "bmad/bmm/agents/analyst.md")
+- `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
@@ -60,7 +60,7 @@ _LLM-Optimized Technical Documentation for Agent Building_
 
 ```xml
 <critical-actions>
-  <i>Load into memory {project-root}/bmad/{module}/config.yaml and set variables</i>
+  <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 -->
@@ -77,7 +77,7 @@ _LLM-Optimized Technical Documentation for Agent Building_
   <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>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>
 
@@ -162,9 +162,9 @@ _LLM-Optimized Technical Documentation for Agent Building_
 
 ```xml
 <module-integration>
-  <module-path>{project-root}/bmad/{module-code}</module-path>
+  <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>
+  <workflows-path>{project-root}/.bmad/{module-code}/workflows</workflows-path>
 </module-integration>
 ```
 
@@ -186,7 +186,7 @@ Example: `{config_source}:output_folder`
 ### Path Construction
 
 ```
-Good: {project-root}/bmad/{module}/agents/
+Good: {project-root}/.bmad/{module}/agents/
 Bad:  /absolute/path/to/agents/
 Bad:  ../../../relative/paths/
 ```
@@ -197,7 +197,7 @@ Bad:  ../../../relative/paths/
 
 ```xml
 <!-- Full path -->
-<item cmd="*create-prd" run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
+<item cmd="*create-prd" run-workflow="{project-root}/.bmad/bmm/workflows/prd/workflow.yaml">
   Create Product Requirements Document
 </item>
 
@@ -210,7 +210,7 @@ Bad:  ../../../relative/paths/
 ### Task Commands
 
 ```xml
-<item cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.xml">
+<item cmd="*validate" exec="{project-root}/.bmad/core/tasks/validate-workflow.xml">
   Validate document
 </item>
 ```
@@ -219,8 +219,8 @@ Bad:  ../../../relative/paths/
 
 ```xml
 <item cmd="*brief"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/brief.md">
+   exec="{project-root}/.bmad/core/tasks/create-doc.md"
+   tmpl="{project-root}/.bmad/bmm/templates/brief.md">
   Create project brief
 </item>
 ```
@@ -229,8 +229,8 @@ Bad:  ../../../relative/paths/
 
 ```xml
 <item cmd="*standup"
-   exec="{project-root}/bmad/bmm/tasks/daily-standup.xml"
-   data="{project-root}/bmad/_cfg/agent-manifest.csv">
+   exec="{project-root}/.bmad/bmm/tasks/daily-standup.xml"
+   data="{project-root}/.bmad/_cfg/agent-manifest.csv">
   Run daily standup
 </item>
 ```
@@ -295,7 +295,7 @@ Bad:  ../../../relative/paths/
 </persona>
 
 <!-- Variable-based paths -->
-<item cmd="*run" exec="{project-root}/bmad/module/task.md">
+<item cmd="*run" exec="{project-root}/.bmad/module/task.md">
 
 <!-- Required commands present -->
 <menu>
@@ -395,7 +395,7 @@ When building agents:
 
 ```xml
 <critical-actions>
-  <i>Load into memory {project-root}/bmad/{module}/config.yaml</i>
+  <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>
@@ -404,7 +404,7 @@ When building agents:
 ### Module Agent Pattern
 
 ```xml
-<agent id="bmad/{module}/agents/{name}.md"
+<agent id=".bmad/{module}/agents/{name}.md"
        name="{Name}"
        title="{Title}"
        icon="{emoji}">

.bmad/bmb/workflows/create-agent/agent-command-patterns.md

@@ -67,14 +67,14 @@ Execute complete multi-step processes
 ```xml
 <!-- Standard workflow -->
 <item cmd="*create-prd"
-     run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
+     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">
+     workflow="{project-root}/.bmad/bmm/workflows/prd/workflow.yaml">
   Validate PRD Against Checklist
 </item>
 
@@ -112,14 +112,14 @@ Execute single operations
 ```xml
 <!-- Simple task -->
 <item cmd="*validate"
-   exec="{project-root}/bmad/core/tasks/validate-workflow.xml">
+   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">
+   exec="{project-root}/.bmad/mmm/tasks/daily-standup.xml"
+   data="{project-root}/.bmad/_cfg/agent-manifest.csv">
   Run agile team standup
 </item>
 ```
@@ -137,15 +137,15 @@ 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">
+   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">
+   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>
 ```
@@ -174,7 +174,7 @@ Direct prompts embedded in commands (Simple agents)
 ```xml
 <!-- Short action attribute with embedded prompt -->
 <item cmd="*list-tasks"
-   action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">
+   action="list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv">
   List Available Tasks
 </item>
 
@@ -227,7 +227,7 @@ For multiline/complex prompts, define them separately and reference by id:
 
     <item cmd="*review-literature"
        action="#literature-review"
-       data="{project-root}/bmad/_data/sources.csv">
+       data="{project-root}/.bmad/_data/sources.csv">
       Conduct Literature Review
     </item>
 
@@ -407,23 +407,23 @@ The `data` attribute can be added to ANY command type to provide supplementary i
 ```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">
+   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">
+   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">
+   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>
 ```
@@ -572,14 +572,14 @@ The `data` attribute can be added to ANY command type to provide supplementary i
 ```xml
 <!-- Create document -->
 <item cmd="*{action}-{object}"
-   run-workflow="{project-root}/bmad/{module}/workflows/{workflow}/workflow.yaml">
+   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">
+   workflow="{project-root}/.bmad/{module}/workflows/{workflow}/workflow.yaml">
   Validate {Object Description}
 </item>
 ```
@@ -588,7 +588,7 @@ The `data` attribute can be added to ANY command type to provide supplementary i
 
 ```xml
 <item cmd="*{action}"
-   exec="{project-root}/bmad/{module}/tasks/{task}.md">
+   exec="{project-root}/.bmad/{module}/tasks/{task}.md">
   {Action Description}
 </item>
 ```
@@ -597,8 +597,8 @@ The `data` attribute can be added to ANY command type to provide supplementary i
 
 ```xml
 <item cmd="*{document}"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/{module}/templates/{template}.md">
+   exec="{project-root}/.bmad/core/tasks/create-doc.md"
+   tmpl="{project-root}/.bmad/{module}/templates/{template}.md">
   Create {Document Name}
 </item>
 ```
@@ -631,7 +631,7 @@ The `data` attribute can be added to ANY command type to provide supplementary i
 ### Complete Self-Contained Agent
 
 ```xml
-<agent id="bmad/research/agents/analyst.md" name="Research Analyst" icon="🔬">
+<agent id=".bmad/research/agents/analyst.md" name="Research Analyst" icon="🔬">
   <!-- Embedded prompt library -->
   <prompts>
     <prompt id="swot-analysis">
@@ -688,14 +688,14 @@ The `data` attribute can be added to ANY command type to provide supplementary i
 
     <item cmd="*compete"
        action="#competitive-intel"
-       data="{project-root}/bmad/_data/market-data.csv">
+       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">
+       exec="{project-root}/.bmad/core/tasks/create-doc.md"
+       tmpl="{project-root}/.bmad/research/templates/report.md">
       Generate Research Report
     </item>
 
@@ -721,7 +721,7 @@ For agents that primarily use embedded logic:
 
     <item cmd="*analyze"
        action="perform statistical analysis on the provided data"
-       data="{project-root}/bmad/_data/dataset.csv">
+       data="{project-root}/.bmad/_data/dataset.csv">
       Analyze Dataset
     </item>
 

.bmad/bmb/workflows/create-agent/agent-types.md

@@ -8,10 +8,10 @@ BMAD agents come in three distinct types, each designed for different use cases
 
 ### Standalone Agents (Simple & Expert)
 
-Live in their own dedicated directories under `bmad/agents/`:
+Live in their own dedicated directories under `.bmad/agents/`:
 
 ```
-bmad/agents/
+.bmad/agents/
 ├── my-helper/                   # Simple agent
 │   ├── my-helper.agent.yaml     # Agent definition
 │   └── my-helper.md             # Built XML (generated)
@@ -28,10 +28,10 @@ bmad/agents/
 
 ### Module Agents
 
-Part of a module system under `bmad/{module}/agents/`:
+Part of a module system under `.bmad/{module}/agents/`:
 
 ```
-bmad/bmm/agents/
+.bmad/bmm/agents/
 ├── product-manager.agent.yaml
 ├── product-manager.md           # Built XML
 ├── business-analyst.agent.yaml
@@ -44,7 +44,7 @@ bmad/bmm/agents/
 
 **Purpose:** Self-contained, standalone agents with embedded capabilities
 
-**Location:** `bmad/agents/{agent-name}/`
+**Location:** `.bmad/agents/{agent-name}/`
 
 **Characteristics:**
 
@@ -105,7 +105,7 @@ agent:
 
 **Purpose:** Specialized agents with domain expertise and sidecar resources
 
-**Location:** `bmad/agents/{agent-name}/` with sidecar directory
+**Location:** `.bmad/agents/{agent-name}/` with sidecar directory
 
 **Characteristics:**
 
@@ -168,7 +168,7 @@ agent:
 **Complete Directory Structure:**
 
 ```
-bmad/agents/expert-agent/
+.bmad/agents/expert-agent/
 ├── expert-agent.agent.yaml      # Agent YAML source
 ├── expert-agent.md              # Built XML (generated)
 └── expert-agent-sidecar/        # Sidecar resources
@@ -183,7 +183,7 @@ bmad/agents/expert-agent/
 
 **Purpose:** Full-featured agents belonging to a module with access to workflows and resources
 
-**Location:** `bmad/{module}/agents/`
+**Location:** `.bmad/{module}/agents/`
 
 **Characteristics:**
 
@@ -216,20 +216,20 @@ agent:
     communication_style: '...'
     principles: ['...']
   critical_actions:
-    - 'Load config from {project-root}/bmad/{module}/config.yaml'
+    - 'Load config from {project-root}/.bmad/{module}/config.yaml'
   menu:
     - trigger: create-prd
-      workflow: '{project-root}/bmad/bmm/workflows/prd/workflow.yaml'
+      workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
       description: 'Create PRD'
     - trigger: validate
-      exec: '{project-root}/bmad/core/tasks/validate-workflow.xml'
+      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="📋">
+<agent id=".bmad/bmm/agents/pm.md" name="John" title="Product Manager" icon="📋">
   <persona>
     <role>Product Management Expert</role>
     <identity>...</identity>
@@ -237,12 +237,12 @@ agent:
     <principles>...</principles>
   </persona>
   <critical-actions>
-    <i>Load config from {project-root}/bmad/{module}/config.yaml</i>
+    <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="*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>

.bmad/bmb/workflows/create-agent/checklist.md

@@ -11,7 +11,7 @@
 
 ### Core Components
 
-- [ ] `metadata.id` points to final compiled path: `bmad/{{module}}/agents/{{agent}}.md`
+- [ ] `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
 
@@ -34,12 +34,12 @@
 
 - [ ] `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`
+- [ ] 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`
+- [ ] Confirm compiled file exists at `{project-root}/.bmad/{{module}}/agents/{{agent}}.md`
 
 ## Final Quality
 

.bmad/bmb/workflows/create-agent/instructions.md

@@ -1,8 +1,8 @@
 # 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>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>
@@ -11,7 +11,7 @@
   <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>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>
@@ -51,19 +51,19 @@
   <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>
+    <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>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
+- 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>
 
@@ -197,8 +197,8 @@ menu:
 # 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"
+  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]
 
 `````
@@ -238,7 +238,7 @@ This is typically used when creating specialized modules that reuse common workf
 <example type="yaml">
   agent:
     metadata:
-      id: bmad/{{target_module}}/agents/{{agent_filename}}.md
+      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

.bmad/bmb/workflows/create-agent/workflow.yaml

@@ -4,7 +4,7 @@ description: "Interactive workflow to build BMAD Core compliant agents (YAML sou
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
@@ -17,21 +17,21 @@ communication_styles: "{installed_path}/communication-styles.md"
 
 # Optional docs that help understand agent patterns
 recommended_inputs:
-  - example_agents: "{project-root}/bmad/bmm/agents/"
+  - 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"
+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/
+# 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"
+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"
+config_output_file: "{project-root}/.bmad/_cfg/agents/{{target_module}}-{{agent_filename}}.customize.yaml"
 
 standalone: true

.bmad/bmb/workflows/create-module/README.md

@@ -71,7 +71,7 @@ workflow create-module --input module-brief-{name}-{date}.md
 ### Generated Directory
 
 ```
-bmad/{module-code}/
+.bmad/{module-code}/
 ├── agents/              # Agent definitions
 ├── workflows/           # Workflow processes
 ├── tasks/              # Reusable tasks

.bmad/bmb/workflows/create-module/checklist.md

@@ -19,7 +19,7 @@
 
 ## Directory Structure
 
-### Source Directories (bmad/{module-code}/)
+### Source Directories (.bmad/{module-code}/)
 
 - [ ] `/agents` directory created (even if empty)
 - [ ] `/workflows` directory created (even if empty)

.bmad/bmb/workflows/create-module/installer-templates/install-config.yaml

@@ -80,7 +80,7 @@ prompt:
 
 # EXAMPLE: Static path
 # module_data_path:
-#   result: "{project-root}/bmad/{{MODULE_CODE}}/data"
+#   result: "{project-root}/.bmad/{{MODULE_CODE}}/data"
 
 # ============================================================================
 # YOUR MODULE CONFIGURATION FIELDS

.bmad/bmb/workflows/create-module/instructions.md

@@ -1,8 +1,8 @@
 # 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>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>
@@ -28,7 +28,7 @@
 <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>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>
@@ -64,7 +64,7 @@
 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/
+   - 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
 
@@ -322,7 +322,7 @@ prompt:
 
 # EXAMPLE Static path:
 # data_path:
-#   result: "{project-root}/bmad/{{module_code}}/data"
+#   result: "{project-root}/.bmad/{{module_code}}/data"
 
 {{generated_config_fields_from_step_4}}
 ```
@@ -446,7 +446,7 @@ bmad install {{module_code}}
 
 ## Configuration
 
-The module can be configured in `bmad/{{module_code}}/config.yaml`
+The module can be configured in `.bmad/{{module_code}}/config.yaml`
 
 Key settings:
 {{configuration_options}}

.bmad/bmb/workflows/create-module/module-structure.md

@@ -24,7 +24,7 @@ src/modules/{module-code}/
 └── README.md                      # Module documentation
 
 # INSTALLED MODULE (in target project)
-{project-root}/bmad/{module-code}/
+{project-root}/.bmad/{module-code}/
 ├── agents/                        # Compiled agent files (.md)
 ├── workflows/                     # Workflow instances
 ├── tasks/                         # Task files
@@ -145,8 +145,8 @@ For modules that need workflows from other modules but want to remain standalone
 ```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'
+    workflow: '{project-root}/.bmad/SOURCE_MODULE/workflows/path/workflow.yaml'
+    workflow-install: '{project-root}/.bmad/THIS_MODULE/workflows/vendored/workflow.yaml'
     description: 'Command description'
 ```
 
@@ -216,7 +216,7 @@ module_version:
   result: '1.0.0'
 
 data_path:
-  result: '{project-root}/bmad/module-code/data'
+  result: '{project-root}/.bmad/module-code/data'
 ```
 
 **Key Points:**

.bmad/bmb/workflows/create-module/workflow.yaml

@@ -4,7 +4,7 @@ description: "Interactive workflow to build complete BMAD modules with agents, w
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
@@ -14,22 +14,22 @@ 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"
+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/"
+  - 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"
+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"

.bmad/bmb/workflows/create-workflow/README.md

@@ -159,7 +159,7 @@ The brainstorming phase invokes the CIS brainstorming workflow to:
 ### Generated Workflow Folder
 
 Creates a complete workflow folder at:
-`{project-root}/bmad/{{target_module}}/workflows/{{workflow_name}}/`
+`{project-root}/.bmad/{{target_module}}/workflows/{{workflow_name}}/`
 
 ### Files Created
 
@@ -267,9 +267,9 @@ To modify this workflow:
 
 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`
+- 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
 
 ---

.bmad/bmb/workflows/create-workflow/checklist.md

@@ -61,7 +61,7 @@
 
 - [ ] web_bundle section present if needed
 - [ ] Name, description, author copied from main config
-- [ ] All file paths converted to bmad/-relative format
+- [ ] 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

.bmad/bmb/workflows/create-workflow/instructions.md

@@ -1,7 +1,7 @@
 # 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>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>
@@ -13,7 +13,7 @@
 
 <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
+- 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
 
@@ -255,7 +255,7 @@ Include:
 
 ```yaml
 # Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+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'
@@ -277,13 +277,13 @@ name: 'workflow-name'
 description: 'Clear purpose statement'
 
 # Paths
-installed_path: '{project-root}/bmad/module/workflows/name'
+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'
+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'
@@ -314,7 +314,7 @@ 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 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
@@ -328,7 +328,7 @@ Generate the instructions.md file following the workflow creation guide:
 
 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/adv-elicit.xml</invoke-task>, <critical>, <example>
+   - Output: <template-output>, <invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>, <critical>, <example>
    - Flow: <loop>, <break>, <continue>
 
 5. Best practices from guide:
@@ -616,15 +616,15 @@ If yes:
 
 - 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})
+- 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:
+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"
+   - Example: "{project-root}/.bmad/bmm/workflows/x" → ".bmad/bmm/workflows/x"
 
 3. List ALL referenced files by scanning:
 
@@ -642,8 +642,8 @@ If yes:
 
    **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
+   - 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
 
@@ -654,24 +654,24 @@ 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'
+  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'
+  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'
+    - '.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'
+    - workflow_variable_name: '.bmad/path/to/workflow.yaml'
 ```
 
 **Example with existing_workflows:**
@@ -681,14 +681,14 @@ web_bundle:
   name: 'brainstorm-game'
   description: 'Game brainstorming with CIS workflow'
   author: 'BMad'
-  instructions: 'bmad/bmm/workflows/brainstorm-game/instructions.md'
+  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'
+    - '.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'
+    - core_brainstorming: '.bmad/core/workflows/brainstorming/workflow.yaml'
 ```
 
 **What existing_workflows does:**
@@ -696,13 +696,13 @@ web_bundle:
 - 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
+- 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
+- Check that paths are .bmad/-relative
 - If workflow uses <invoke-workflow>, add to existing_workflows
 
 <template-output>web_bundle_config</template-output>

.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md

@@ -25,7 +25,7 @@ Create a folder with these files:
 # workflow.yaml (REQUIRED)
 name: 'my-workflow'
 description: 'What this workflow does'
-installed_path: '{project-root}/bmad/module/workflows/my-workflow'
+installed_path: '{project-root}/.bmad/module/workflows/my-workflow'
 template: '{installed_path}/template.md'
 instructions: '{installed_path}/instructions.md'
 default_output_file: '{output_folder}/output.md'
@@ -44,7 +44,7 @@ standalone: true
 ```markdown
 # instructions.md
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: workflow.yaml</critical>
 
 <workflow>
@@ -65,7 +65,7 @@ That's it! To execute, tell the BMAD agent: `workflow path/to/my-workflow/`
 | -------------- | ------------------ | ----------------------- |
 | **Purpose**    | Single operation   | Multi-step process      |
 | **Format**     | XML                | Folder with YAML config |
-| **Location**   | `/src/core/tasks/` | `/bmad/*/workflows/`    |
+| **Location**   | `/src/core/tasks/` | `/.bmad/*/workflows/`   |
 | **User Input** | Minimal            | Extensive               |
 | **Output**     | Variable           | Usually documents       |
 
@@ -104,7 +104,7 @@ name: 'workflow-name'
 description: 'Clear purpose statement'
 
 # Paths
-installed_path: '{project-root}/bmad/module/workflows/name'
+installed_path: '{project-root}/.bmad/module/workflows/name'
 template: '{installed_path}/template.md' # or false
 instructions: '{installed_path}/instructions.md' # or false
 validation: '{installed_path}/checklist.md' # optional
@@ -641,7 +641,7 @@ the technology stack recommendations. Please choose: web, mobile, or desktop.</a
 ```markdown
 # instructions.md
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: workflow.yaml</critical>
 
 <workflow>
@@ -855,7 +855,7 @@ _Generated on {{date}}_
 **Output:**
 
 - `<template-output>` - Save checkpoint
-- `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` - Trigger AI enhancement
+- `<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>` - Trigger AI enhancement
 - `<critical>` - Important info
 - `<example>` - Show example
 
@@ -904,7 +904,7 @@ _Generated on {{date}}_
   <step n="2" goal="Define requirements">
     Create functional and non-functional requirements.
     <template-output>requirements</template-output>
-    <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+    <invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
   </step>
 
   <step n="3" goal="Validate">
@@ -1194,7 +1194,7 @@ Web bundles allow workflows to be deployed as self-contained packages for web en
 1. **Self-Contained**: No external dependencies
 2. **No Config Variables**: Cannot use `{config_source}` references
 3. **Complete File List**: Every referenced file must be listed
-4. **Relative Paths**: Use `bmad/` root paths (no `{project-root}`)
+4. **Relative Paths**: Use `.bmad/` root paths (no `{project-root}`)
 
 ### Creating a Web Bundle
 
@@ -1206,20 +1206,20 @@ web_bundle:
   description: 'Workflow description'
   author: 'Your Name'
 
-  # Core files (bmad/-relative paths)
-  instructions: 'bmad/module/workflows/workflow/instructions.md'
-  validation: 'bmad/module/workflows/workflow/checklist.md'
-  template: 'bmad/module/workflows/workflow/template.md'
+  # Core files (.bmad/-relative paths)
+  instructions: '.bmad/module/workflows/workflow/instructions.md'
+  validation: '.bmad/module/workflows/workflow/checklist.md'
+  template: '.bmad/module/workflows/workflow/template.md'
 
   # Data files (no config_source allowed)
-  data_file: 'bmad/module/workflows/workflow/data.csv'
+  data_file: '.bmad/module/workflows/workflow/data.csv'
 
   # Complete file list - CRITICAL!
   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'
+    - '.bmad/module/workflows/workflow/instructions.md'
+    - '.bmad/module/workflows/workflow/checklist.md'
+    - '.bmad/module/workflows/workflow/template.md'
+    - '.bmad/module/workflows/workflow/data.csv'
     # Include ALL referenced files
 ```
 
@@ -1227,7 +1227,7 @@ web_bundle:
 
 1. **Remove Config Dependencies**:
    - Replace `{config_source}:variable` with hardcoded values
-   - Convert `{project-root}/bmad/` to `bmad/`
+   - Convert `{project-root}/.bmad/` to `.bmad/`
 
 2. **Inventory All Files**:
    - Scan instructions.md for file references
@@ -1236,7 +1236,7 @@ web_bundle:
 
 3. **Test Completeness**:
    - Ensure no missing file references
-   - Verify all paths are relative to bmad/
+   - Verify all paths are relative to .bmad/
 
 ### Example: Complete Web Bundle
 
@@ -1246,37 +1246,37 @@ web_bundle:
   description: 'Requirements analysis workflow'
   author: 'BMad Team'
 
-  instructions: 'bmad/bmm/workflows/analyze-requirements/instructions.md'
-  validation: 'bmad/bmm/workflows/analyze-requirements/checklist.md'
-  template: 'bmad/bmm/workflows/analyze-requirements/template.md'
+  instructions: '.bmad/bmm/workflows/analyze-requirements/instructions.md'
+  validation: '.bmad/bmm/workflows/analyze-requirements/checklist.md'
+  template: '.bmad/bmm/workflows/analyze-requirements/template.md'
 
   # Data files
-  techniques_data: 'bmad/bmm/workflows/analyze-requirements/techniques.csv'
-  patterns_data: 'bmad/bmm/workflows/analyze-requirements/patterns.json'
+  techniques_data: '.bmad/bmm/workflows/analyze-requirements/techniques.csv'
+  patterns_data: '.bmad/bmm/workflows/analyze-requirements/patterns.json'
 
   # Sub-workflow reference
-  validation_workflow: 'bmad/bmm/workflows/validate-requirements/workflow.yaml'
+  validation_workflow: '.bmad/bmm/workflows/validate-requirements/workflow.yaml'
 
   standalone: true
 
   web_bundle_files:
     # Core workflow files
-    - 'bmad/bmm/workflows/analyze-requirements/instructions.md'
-    - 'bmad/bmm/workflows/analyze-requirements/checklist.md'
-    - 'bmad/bmm/workflows/analyze-requirements/template.md'
+    - '.bmad/bmm/workflows/analyze-requirements/instructions.md'
+    - '.bmad/bmm/workflows/analyze-requirements/checklist.md'
+    - '.bmad/bmm/workflows/analyze-requirements/template.md'
 
     # Data files
-    - 'bmad/bmm/workflows/analyze-requirements/techniques.csv'
-    - 'bmad/bmm/workflows/analyze-requirements/patterns.json'
+    - '.bmad/bmm/workflows/analyze-requirements/techniques.csv'
+    - '.bmad/bmm/workflows/analyze-requirements/patterns.json'
 
     # Sub-workflow and its files
-    - 'bmad/bmm/workflows/validate-requirements/workflow.yaml'
-    - 'bmad/bmm/workflows/validate-requirements/instructions.md'
-    - 'bmad/bmm/workflows/validate-requirements/checklist.md'
+    - '.bmad/bmm/workflows/validate-requirements/workflow.yaml'
+    - '.bmad/bmm/workflows/validate-requirements/instructions.md'
+    - '.bmad/bmm/workflows/validate-requirements/checklist.md'
 
     # Shared templates referenced in instructions
-    - 'bmad/bmm/templates/requirement-item.md'
-    - 'bmad/bmm/templates/validation-criteria.md'
+    - '.bmad/bmm/templates/requirement-item.md'
+    - '.bmad/bmm/templates/validation-criteria.md'
 ```
 
 ## Troubleshooting
@@ -1305,4 +1305,4 @@ web_bundle:
 _For implementation details, see:_
 
 - `/src/core/tasks/workflow.xml` - Execution engine
-- `/bmad/bmm/workflows/` - Production examples
+- `/.bmad/bmm/workflows/` - Production examples

.bmad/bmb/workflows/create-workflow/workflow-template/instructions.md

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

.bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml

@@ -20,7 +20,7 @@ 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}"
+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

.bmad/bmb/workflows/create-workflow/workflow.yaml

@@ -4,7 +4,7 @@ description: "Interactive workflow builder that guides creation of new BMAD work
 author: "BMad Builder"
 
 # Critical variables
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
@@ -17,11 +17,11 @@ 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/"
+  - 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"
+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"
@@ -33,7 +33,7 @@ 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}}"
+module_output_folder: "{project-root}/.bmad/{{target_module}}/workflows/{{workflow_name}}"
 standalone_output_folder: "{custom_workflow_location}/{{workflow_name}}"
 
 standalone: true

.bmad/bmb/workflows/edit-agent/checklist.md

@@ -46,7 +46,7 @@ Use this checklist to validate agent edits meet BMAD Core standards.
 ## Menu Handler Validation
 
 - [ ] menu-handlers section is present
-- [ ] Workflow handler loads {project-root}/bmad/core/tasks/workflow.xml
+- [ ] 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

.bmad/bmb/workflows/edit-agent/instructions.md

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

.bmad/bmb/workflows/edit-agent/workflow.yaml

@@ -4,27 +4,27 @@ description: "Edit existing BMAD agents while following all best practices and c
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
+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"
+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/"
+  - 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"
+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"

.bmad/bmb/workflows/edit-module/README.md

@@ -106,7 +106,7 @@ Modules can share workflows:
 
 ```yaml
 # In agent menu item:
-workflow: '{project-root}/bmad/other-module/workflows/shared-workflow/workflow.yaml'
+workflow: '{project-root}/.bmad/other-module/workflows/shared-workflow/workflow.yaml'
 ```
 
 Common patterns:
@@ -151,7 +151,7 @@ Changes are reviewed and approved by you before being applied.
 - Can configure web bundles
 - Are the development source of truth
 
-**Installed modules** (in bmad/):
+**Installed modules** (in .bmad/):
 
 - Are deployed to target projects
 - Use config.yaml for user customization

.bmad/bmb/workflows/edit-module/checklist.md

@@ -5,7 +5,7 @@ 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)
+- [ ] Module is in correct location (src/modules/ for source, .bmad/ for installed)
 - [ ] agents/ directory exists
 - [ ] workflows/ directory exists
 - [ ] config.yaml exists in module root
@@ -128,7 +128,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
 
 - [ ] Web bundles configured in workflow.yaml files
 - [ ] All referenced files included in web_bundle_files
-- [ ] Paths are bmad/-relative (not project-root)
+- [ ] Paths are .bmad/-relative (not project-root)
 - [ ] No config_source references in web bundles
 - [ ] Invoked workflows included in dependencies
 

.bmad/bmb/workflows/edit-module/instructions.md

@@ -1,7 +1,7 @@
 # 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>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>
@@ -9,7 +9,7 @@
 <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>
+<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:
 
@@ -185,7 +185,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
 **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
+- 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

.bmad/bmb/workflows/edit-module/workflow.yaml

@@ -4,28 +4,28 @@ description: "Edit existing BMAD modules (structure, agents, workflows, document
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
+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"
+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/"
+  - 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"
+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"

.bmad/bmb/workflows/edit-workflow/instructions.md

@@ -1,7 +1,7 @@
 # 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>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>
@@ -24,7 +24,7 @@
 
 - Workflow creation guide: {workflow_creation_guide}
 - Workflow execution engine: {workflow_execution_engine}
-- Study example workflows from: {project-root}/bmad/bmm/workflows/
+- Study example workflows from: {project-root}/.bmad/bmm/workflows/
   </action>
 
 <action>Analyze the workflow deeply:
@@ -205,7 +205,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
 
 - Identify all files the workflow depends on
 - Check for invoked workflows (must be included)
-- Verify paths are bmad/-relative
+- Verify paths are .bmad/-relative
 - Remove config_source dependencies
 - Build complete file list
 

.bmad/bmb/workflows/edit-workflow/workflow.yaml

@@ -4,21 +4,21 @@ description: "Edit existing BMAD workflows while following all best practices an
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
+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/"
+  - workflow_examples: "{project-root}/.bmad/bmm/workflows/"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/edit-workflow"
+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"

.bmad/bmb/workflows/module-brief/README.md

@@ -254,8 +254,8 @@ To customize this workflow:
 
 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
+- 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`
 

.bmad/bmb/workflows/module-brief/instructions.md

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

.bmad/bmb/workflows/module-brief/workflow.yaml

@@ -4,7 +4,7 @@ description: "Create a comprehensive Module Brief that serves as the blueprint f
 author: "BMad Builder"
 
 # Critical variables
-config_source: "{project-root}/bmad/bmb/config.yaml"
+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"
@@ -13,11 +13,11 @@ 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"
+  - 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"
+installed_path: "{project-root}/.bmad/bmb/workflows/module-brief"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

.bmad/bmb/workflows/redoc/README.md

@@ -28,11 +28,11 @@ 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)
+- **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
 

.bmad/bmb/workflows/redoc/instructions.md

@@ -1,6 +1,6 @@
 # ReDoc Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {project-root}/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>

.bmad/bmb/workflows/redoc/workflow.yaml

@@ -4,7 +4,7 @@ description: "Autonomous documentation system that maintains module, workflow, a
 author: "BMad"
 
 # Critical variables
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/.bmad/bmb/config.yaml"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 

.bmad/bmm/README.md

@@ -0,0 +1,128 @@
+# BMM - BMad Method Module
+
+Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
+
+---
+
+## 📚 Complete Documentation
+
+👉 **[BMM Documentation Hub](./docs/README.md)** - Start here for complete guides, tutorials, and references
+
+**Quick Links:**
+
+- **[Quick Start Guide](./docs/quick-start.md)** - New to BMM? Start here (15 min)
+- **[Agents Guide](./docs/agents-guide.md)** - Meet your 12 specialized AI agents (45 min)
+- **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - How BMM adapts to project size (42 min)
+- **[FAQ](./docs/faq.md)** - Quick answers to common questions
+- **[Glossary](./docs/glossary.md)** - Key terminology reference
+
+---
+
+## 🏗️ Module Structure
+
+This module contains:
+
+```
+bmm/
+├── agents/          # 12 specialized AI agents (PM, Architect, SM, DEV, TEA, etc.)
+├── workflows/       # 34 workflows across 4 phases + testing
+├── teams/           # Pre-configured agent groups
+├── tasks/           # Atomic work units
+├── testarch/        # Comprehensive testing infrastructure
+└── docs/            # Complete user documentation
+```
+
+### Agent Roster
+
+**Core Development:** PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Technical Writer
+**Game Development:** Game Designer, Game Developer, Game Architect
+**Orchestration:** BMad Master (from Core)
+
+👉 **[Full Agents Guide](./docs/agents-guide.md)** - Roles, workflows, and when to use each agent
+
+### Workflow Phases
+
+**Phase 0:** Documentation (brownfield only)
+**Phase 1:** Analysis (optional) - 5 workflows
+**Phase 2:** Planning (required) - 6 workflows
+**Phase 3:** Solutioning (Level 3-4) - 2 workflows
+**Phase 4:** Implementation (iterative) - 10 workflows
+**Testing:** Quality assurance (parallel) - 9 workflows
+
+👉 **[Workflow Guides](./docs/README.md#-workflow-guides)** - Detailed documentation for each phase
+
+---
+
+## 🚀 Getting Started
+
+**New Project:**
+
+```bash
+# Install BMM
+npx bmad-method@alpha install
+
+# Load Analyst agent in your IDE, then:
+*workflow-init
+```
+
+**Existing Project (Brownfield):**
+
+```bash
+# Document your codebase first
+*document-project
+
+# Then initialize
+*workflow-init
+```
+
+👉 **[Quick Start Guide](./docs/quick-start.md)** - Complete setup and first project walkthrough
+
+---
+
+## 🎯 Key Concepts
+
+### Scale-Adaptive Design
+
+BMM automatically adjusts to project complexity (Levels 0-4):
+
+- **Level 0-1:** Quick Spec Flow for bug fixes and small features
+- **Level 2:** PRD with optional architecture
+- **Level 3-4:** Full PRD + comprehensive architecture
+
+👉 **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - Complete level breakdown
+
+### Story-Centric Implementation
+
+Stories move through a defined lifecycle: `backlog → drafted → ready → in-progress → review → done`
+
+Just-in-time epic context and story context provide exact expertise when needed.
+
+👉 **[Implementation Workflows](./docs/workflows-implementation.md)** - Complete story lifecycle guide
+
+### Multi-Agent Collaboration
+
+Use party mode to engage all 19+ agents (from BMM, CIS, BMB, custom modules) in group discussions for strategic decisions, creative brainstorming, and complex problem-solving.
+
+👉 **[Party Mode Guide](./docs/party-mode.md)** - How to orchestrate multi-agent collaboration
+
+---
+
+## 📖 Additional Resources
+
+- **[Brownfield Guide](./docs/brownfield-guide.md)** - Working with existing codebases
+- **[Quick Spec Flow](./docs/quick-spec-flow.md)** - Fast-track for Level 0-1 projects
+- **[Enterprise Agentic Development](./docs/enterprise-agentic-development.md)** - Team collaboration patterns
+- **[Troubleshooting](./docs/troubleshooting.md)** - Common issues and solutions
+- **[IDE Setup Guides](../../../docs/ide-info/)** - Configure Claude Code, Cursor, Windsurf, etc.
+
+---
+
+## 🤝 Community
+
+- **[Discord](https://discord.gg/gk8jAdXWmj)** - Get help, share feedback (#general-dev, #bugs-issues)
+- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features
+- **[YouTube](https://www.youtube.com/@BMadCode)** - Video tutorials and walkthroughs
+
+---
+
+**Ready to build?** → [Start with the Quick Start Guide](./docs/quick-start.md)

.bmad/bmm/agents/analyst.md

@@ -0,0 +1,75 @@
+---
+name: 'analyst'
+description: 'Business Analyst'
+---
+
+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/bmm/agents/analyst.md" name="Mary" title="Business Analyst" 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}/bmm/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 trigger text</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>
+      <handler type="exec">
+        When menu item has: exec="path/to/file.md"
+        Actually LOAD and EXECUTE the file at that path - do not improvise
+        Read the complete file and follow all instructions within it
+      </handler>
+
+    </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>Strategic Business Analyst + Requirements Expert</role>
+    <identity>Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.</identity>
+    <communication_style>Systematic and probing. Connects dots others miss. Structures findings hierarchically. Uses precise unambiguous language. Ensures all stakeholder voices heard.</communication_style>
+    <principles>Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*workflow-init" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml">Start a new sequenced workflow path (START HERE!)</item>
+    <item cmd="*workflow-status" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
+    <item cmd="*brainstorm-project" workflow="{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml">Guide me through Brainstorming</item>
+    <item cmd="*product-brief" workflow="{project-root}/.bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml">Produce Project Brief</item>
+    <item cmd="*document-project" workflow="{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml">Generate comprehensive documentation of an existing Project</item>
+    <item cmd="*research" workflow="{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml">Guide me through Research</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
+    <item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.bmad/bmm/agents/architect.md

@@ -0,0 +1,80 @@
+---
+name: 'architect'
+description: 'Architect'
+---
+
+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/bmm/agents/architect.md" name="Winston" title="Architect" 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}/bmm/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 trigger text</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>
+  <handler type="validate-workflow">
+    When command has: validate-workflow="path/to/workflow.yaml"
+    1. You MUST LOAD the file at: {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml
+    2. READ its entire contents and EXECUTE all instructions in that file
+    3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+    4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+  </handler>
+      <handler type="exec">
+        When menu item has: exec="path/to/file.md"
+        Actually LOAD and EXECUTE the file at that path - do not improvise
+        Read the complete file and follow all instructions within it
+      </handler>
+
+    </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>System Architect + Technical Design Leader</role>
+    <identity>Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.</identity>
+    <communication_style>Pragmatic in technical discussions. Balances idealism with reality. Always connects decisions to business value and user impact. Prefers boring tech that works.</communication_style>
+    <principles>User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*workflow-status" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
+    <item cmd="*create-architecture" workflow="{project-root}/.bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml">Produce a Scale Adaptive Architecture</item>
+    <item cmd="*validate-architecture" validate-workflow="{project-root}/.bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml">Validate Architecture Document</item>
+    <item cmd="*solutioning-gate-check" workflow="{project-root}/.bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml">Validate solutioning complete, ready for Phase 4 (Level 2-4 only)</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
+    <item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.bmad/bmm/agents/dev.md

@@ -0,0 +1,69 @@
+---
+name: 'dev'
+description: 'Developer 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.
+
+```xml
+<agent id=".bmad/bmm/agents/dev.md" name="Amelia" title="Developer Agent" 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}/bmm/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">DO NOT start implementation until a story is loaded and Status == Approved</step>
+  <step n="5">When a story is loaded, READ the entire story markdown</step>
+  <step n="6">Locate 'Dev Agent Record' → 'Context Reference' and READ the referenced Story Context file(s). If none present, HALT and ask user to run @spec-context → *story-context</step>
+  <step n="7">Pin the loaded Story Context into active memory for the whole session; treat it as AUTHORITATIVE over any model priors</step>
+  <step n="8">For *develop (Dev Story workflow), execute continuously without pausing for review or 'milestones'. Only halt for explicit blocker conditions (e.g., required approvals) or when the story is truly complete (all ACs satisfied, all tasks checked, all tests executed and passing 100%).</step>
+  <step n="9">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="10">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="11">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="12">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>Senior Implementation Engineer</role>
+    <identity>Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.</identity>
+    <communication_style>Succinct and checklist-driven. Cites specific paths and AC IDs. Asks clarifying questions only when inputs missing. Refuses to invent when info lacking.</communication_style>
+    <principles>Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. Tests pass 100% or story isn&apos;t done.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*workflow-status" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
+    <item cmd="*develop-story" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml">Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story</item>
+    <item cmd="*story-done" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/story-done/workflow.yaml">Mark story done after DoD complete</item>
+    <item cmd="*code-review" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml">Perform a thorough clean context QA code review on a story flagged Ready for Review</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.bmad/bmm/agents/pm.md

@@ -0,0 +1,84 @@
+---
+name: 'pm'
+description: 'Product Manager'
+---
+
+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/bmm/agents/pm.md" name="John" title="Product Manager" 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}/bmm/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 trigger text</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>
+  <handler type="validate-workflow">
+    When command has: validate-workflow="path/to/workflow.yaml"
+    1. You MUST LOAD the file at: {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml
+    2. READ its entire contents and EXECUTE all instructions in that file
+    3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+    4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+  </handler>
+      <handler type="exec">
+        When menu item has: exec="path/to/file.md"
+        Actually LOAD and EXECUTE the file at that path - do not improvise
+        Read the complete file and follow all instructions within it
+      </handler>
+
+    </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>Investigative Product Strategist + Market-Savvy PM</role>
+    <identity>Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.</identity>
+    <communication_style>Direct and analytical. Asks WHY relentlessly. Backs claims with data and user insights. Cuts straight to what matters for the product.</communication_style>
+    <principles>Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. Align efforts with measurable business impact.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*workflow-init" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml">Start a new sequenced workflow path (START HERE!)</item>
+    <item cmd="*workflow-status" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
+    <item cmd="*create-prd" workflow="{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml">Create Product Requirements Document (PRD) for Level 2-4 projects</item>
+    <item cmd="*create-epics-and-stories" workflow="{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml">Break PRD requirements into implementable epics and stories</item>
+    <item cmd="*validate-prd" validate-workflow="{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml">Validate PRD + Epics + Stories completeness and quality</item>
+    <item cmd="*tech-spec" workflow="{project-root}/.bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml">Create Tech Spec for Level 0-1 (sometimes Level 2) projects</item>
+    <item cmd="*validate-tech-spec" validate-workflow="{project-root}/.bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml">Validate Technical Specification Document</item>
+    <item cmd="*correct-course" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml">Course Correction Analysis</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
+    <item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.bmad/bmm/agents/sm.md

@@ -0,0 +1,93 @@
+---
+name: 'sm'
+description: 'Scrum Master'
+---
+
+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/bmm/agents/sm.md" name="Bob" title="Scrum Master" 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}/bmm/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">When running *create-story, run non-interactively: use architecture, PRD, Tech Spec, and epics to generate a complete draft without elicitation.</step>
+  <step n="5">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="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="7">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="8">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>
+  <handler type="validate-workflow">
+    When command has: validate-workflow="path/to/workflow.yaml"
+    1. You MUST LOAD the file at: {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml
+    2. READ its entire contents and EXECUTE all instructions in that file
+    3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+    4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+  </handler>
+      <handler type="data">
+        When menu item has: data="path/to/file.json|yaml|yml|csv|xml"
+        Load the file first, parse according to extension
+        Make available as {data} variable to subsequent handler operations
+      </handler>
+
+      <handler type="exec">
+        When menu item has: exec="path/to/file.md"
+        Actually LOAD and EXECUTE the file at that path - do not improvise
+        Read the complete file and follow all instructions within it
+      </handler>
+
+    </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>Technical Scrum Master + Story Preparation Specialist</role>
+    <identity>Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.</identity>
+    <communication_style>Task-oriented and efficient. Focused on clear handoffs and precise requirements. Eliminates ambiguity. Emphasizes developer-ready specs.</communication_style>
+    <principles>Strict boundaries between story prep and implementation. Stories are single source of truth. Perfect alignment between PRD and dev execution. Enable efficient sprints.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*workflow-status" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
+    <item cmd="*sprint-planning" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml">Generate or update sprint-status.yaml from epic files</item>
+    <item cmd="*epic-tech-context" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml">(Optional) Use the PRD and Architecture to create a Epic-Tech-Spec for a specific epic</item>
+    <item cmd="*validate-epic-tech-context" validate-workflow="{project-root}/.bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml">(Optional) Validate latest Tech Spec against checklist</item>
+    <item cmd="*create-story" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml">Create a Draft Story</item>
+    <item cmd="*validate-create-story" validate-workflow="{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml">(Optional) Validate Story Draft with Independent Review</item>
+    <item cmd="*story-context" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/story-context/workflow.yaml">(Optional) Assemble dynamic Story Context (XML) from latest docs and code and mark story ready for dev</item>
+    <item cmd="*validate-story-context" validate-workflow="{project-root}/.bmad/bmm/workflows/4-implementation/story-context/workflow.yaml">(Optional) Validate latest Story Context XML against checklist</item>
+    <item cmd="*story-ready-for-dev" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml">(Optional) Mark drafted story ready for dev without generating Story Context</item>
+    <item cmd="*epic-retrospective" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml" data="{project-root}/.bmad/_cfg/agent-manifest.csv">(Optional) Facilitate team retrospective after an epic is completed</item>
+    <item cmd="*correct-course" workflow="{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml">(Optional) Execute correct-course task</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
+    <item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.bmad/bmm/agents/tea.md

@@ -0,0 +1,80 @@
+---
+name: 'tea'
+description: 'Master Test Architect'
+---
+
+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/bmm/agents/tea.md" name="Murat" title="Master Test Architect" 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}/bmm/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">Consult {project-root}/.bmad/bmm/testarch/tea-index.csv to select knowledge fragments under `knowledge/` and load only the files needed for the current task</step>
+  <step n="5">Load the referenced fragment(s) from `{project-root}/.bmad/bmm/testarch/knowledge/` before giving recommendations</step>
+  <step n="6">Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation; fall back to {project-root}/.bmad/bmm/testarch/test-resources-for-ai-flat.txt only when deeper sourcing is required</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 trigger text</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="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>
+      <handler type="exec">
+        When menu item has: exec="path/to/file.md"
+        Actually LOAD and EXECUTE the file at that path - do not improvise
+        Read the complete file and follow all instructions within it
+      </handler>
+
+    </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 Test Architect</role>
+    <identity>Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.</identity>
+    <communication_style>Data-driven and pragmatic. Strong opinions weakly held. Calculates risk vs value. Knows when to test deep vs shallow.</communication_style>
+    <principles>Risk-based testing. Depth scales with impact. Quality gates backed by data. Tests mirror usage. Flakiness is critical debt. Tests first AI implements suite validates.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*workflow-status" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
+    <item cmd="*framework" workflow="{project-root}/.bmad/bmm/workflows/testarch/framework/workflow.yaml">Initialize production-ready test framework architecture</item>
+    <item cmd="*atdd" workflow="{project-root}/.bmad/bmm/workflows/testarch/atdd/workflow.yaml">Generate E2E tests first, before starting implementation</item>
+    <item cmd="*automate" workflow="{project-root}/.bmad/bmm/workflows/testarch/automate/workflow.yaml">Generate comprehensive test automation</item>
+    <item cmd="*test-design" workflow="{project-root}/.bmad/bmm/workflows/testarch/test-design/workflow.yaml">Create comprehensive test scenarios</item>
+    <item cmd="*trace" workflow="{project-root}/.bmad/bmm/workflows/testarch/trace/workflow.yaml">Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)</item>
+    <item cmd="*nfr-assess" workflow="{project-root}/.bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml">Validate non-functional requirements</item>
+    <item cmd="*ci" workflow="{project-root}/.bmad/bmm/workflows/testarch/ci/workflow.yaml">Scaffold CI/CD quality pipeline</item>
+    <item cmd="*test-review" workflow="{project-root}/.bmad/bmm/workflows/testarch/test-review/workflow.yaml">Review test quality using comprehensive knowledge base and best practices</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
+    <item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.bmad/bmm/agents/tech-writer.md

@@ -0,0 +1,90 @@
+---
+name: 'tech writer'
+description: 'Technical Writer'
+---
+
+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/bmm/agents/tech-writer.md" name="paige" title="Technical Writer" 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}/bmm/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">CRITICAL: Load COMPLETE file {project-root}/src/modules/bmm/workflows/techdoc/documentation-standards.md into permanent memory and follow ALL rules within</step>
+  <step n="5">Load into memory {project-root}/.bmad/bmm/config.yaml and set variables</step>
+  <step n="6">Remember the user's name is {user_name}</step>
+  <step n="7">ALWAYS communicate in {communication_language}</step>
+  <step n="8">ALWAYS write documentation in {document_output_language}</step>
+  <step n="9">CRITICAL: All documentation MUST follow CommonMark specification strictly - zero tolerance for violations</step>
+  <step n="10">CRITICAL: All Mermaid diagrams MUST use valid syntax - mentally validate before outputting</step>
+  <step n="11">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="12">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="13">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="14">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>
+      <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="exec">
+        When menu item has: exec="path/to/file.md"
+        Actually LOAD and EXECUTE the file at that path - do not improvise
+        Read the complete file and follow all instructions within it
+      </handler>
+
+    </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>Technical Documentation Specialist + Knowledge Curator</role>
+    <identity>Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.</identity>
+    <communication_style>Patient and supportive. Uses clear examples and analogies. Knows when to simplify vs when to be detailed. Celebrates good docs helps improve unclear ones.</communication_style>
+    <principles>Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*document-project" workflow="{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml">Comprehensive project documentation (brownfield analysis, architecture scanning)</item>
+    <item cmd="*create-api-docs" workflow="todo">Create API documentation with OpenAPI/Swagger standards</item>
+    <item cmd="*create-architecture-docs" workflow="todo">Create architecture documentation with diagrams and ADRs</item>
+    <item cmd="*create-user-guide" workflow="todo">Create user-facing guides and tutorials</item>
+    <item cmd="*audit-docs" workflow="todo">Review documentation quality and suggest improvements</item>
+    <item cmd="*generate-diagram" action="Create a Mermaid diagram based on user description. Ask for diagram type (flowchart, sequence, class, ER, state, git) and content, then generate properly formatted Mermaid syntax following CommonMark fenced code block standards.">Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)</item>
+    <item cmd="*validate-doc" action="Review the specified document against CommonMark standards, technical writing best practices, and style guide compliance. Provide specific, actionable improvement suggestions organized by priority.">Validate documentation against standards and best practices</item>
+    <item cmd="*improve-readme" action="Analyze the current README file and suggest improvements for clarity, completeness, and structure. Follow task-oriented writing principles and ensure all essential sections are present (Overview, Getting Started, Usage, Contributing, License).">Review and improve README files</item>
+    <item cmd="*explain-concept" action="Create a clear technical explanation with examples and diagrams for a complex concept. Break it down into digestible sections using task-oriented approach. Include code examples and Mermaid diagrams where helpful.">Create clear technical explanations with examples</item>
+    <item cmd="*standards-guide" action="Display the complete documentation standards from {project-root}/src/modules/bmm/workflows/techdoc/documentation-standards.md in a clear, formatted way for the user.">Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
+    <item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.bmad/bmm/agents/ux-designer.md

@@ -0,0 +1,79 @@
+---
+name: 'ux designer'
+description: 'UX Designer'
+---
+
+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/bmm/agents/ux-designer.md" name="Sally" title="UX Designer" 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}/bmm/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 trigger text</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>
+  <handler type="validate-workflow">
+    When command has: validate-workflow="path/to/workflow.yaml"
+    1. You MUST LOAD the file at: {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml
+    2. READ its entire contents and EXECUTE all instructions in that file
+    3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+    4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+  </handler>
+      <handler type="exec">
+        When menu item has: exec="path/to/file.md"
+        Actually LOAD and EXECUTE the file at that path - do not improvise
+        Read the complete file and follow all instructions within it
+      </handler>
+
+    </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>User Experience Designer + UI Specialist</role>
+    <identity>Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.</identity>
+    <communication_style>Empathetic and user-focused. Uses storytelling for design decisions. Data-informed but creative. Advocates strongly for user needs and edge cases.</communication_style>
+    <principles>Every decision serves genuine user needs. Start simple evolve through feedback. Balance empathy with edge case attention. AI tools accelerate human-centered design.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*workflow-status" workflow="{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations (START HERE!)</item>
+    <item cmd="*create-design" workflow="{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml">Conduct Design Thinking Workshop to Define the User Specification</item>
+    <item cmd="*validate-design" validate-workflow="{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml">Validate UX Specification and Design Artifacts</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Consult with other expert agents from the party</item>
+    <item cmd="*adv-elicit" exec="{project-root}/.bmad/core/tasks/adv-elicit.xml">Advanced elicitation techniques to challenge the LLM to get better results</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

.bmad/bmm/config.yaml

@@ -0,0 +1,18 @@
+# BMM Module Configuration
+# Generated by BMAD installer
+# Version: 6.0.0-alpha.7
+# Date: 2025-11-09T05:23:00.244Z
+
+project_name: BMAD-METHOD
+user_skill_level: intermediate
+tech_docs: "{project-root}/docs/technical"
+dev_ephemeral_location: "{project-root}/.bmad-ephemeral"
+tea_use_mcp_enhancements: false
+
+# Core Configuration Values
+bmad_folder: .bmad
+user_name: BMad
+communication_language: English
+document_output_language: English
+output_folder: "{project-root}/docs"
+install_user_docs: false

.bmad/bmm/docs/README.md

@@ -0,0 +1,235 @@
+# BMM Documentation
+
+Complete guides for the BMad Method Module (BMM) - AI-powered agile development workflows that adapt to your project's complexity.
+
+---
+
+## 🚀 Getting Started
+
+**New to BMM?** Start here:
+
+- **[Quick Start Guide](./quick-start.md)** - Step-by-step guide to building your first project (15 min read)
+  - Installation and setup
+  - Understanding the four phases
+  - Running your first workflows
+  - Agent-based development flow
+
+**Quick Path:** Install → workflow-init → Follow agent guidance
+
+---
+
+## 📖 Core Concepts
+
+Understanding how BMM adapts to your needs:
+
+- **[Scale Adaptive System](./scale-adaptive-system.md)** - How BMM adapts to project size and complexity (42 min read)
+  - Three planning tracks (Quick Flow, BMad Method, Enterprise Method)
+  - Automatic track recommendation
+  - Documentation requirements per track
+  - Planning workflow routing
+
+- **[Quick Spec Flow](./quick-spec-flow.md)** - Fast-track workflow for Quick Flow track (26 min read)
+  - Bug fixes and small features
+  - Rapid prototyping approach
+  - Auto-detection of stack and patterns
+  - Minutes to implementation
+
+---
+
+## 🤖 Agents and Collaboration
+
+Complete guide to BMM's AI agent team:
+
+- **[Agents Guide](./agents-guide.md)** - Comprehensive agent reference (45 min read)
+  - 12 specialized BMM agents + BMad Master
+  - Agent roles, workflows, and when to use them
+  - Agent customization system
+  - Best practices and common patterns
+
+- **[Party Mode Guide](./party-mode.md)** - Multi-agent collaboration (20 min read)
+  - How party mode works (19+ agents collaborate in real-time)
+  - When to use it (strategic, creative, cross-functional, complex)
+  - Example party compositions
+  - Multi-module integration (BMM + CIS + BMB + custom)
+  - Agent customization in party mode
+  - Best practices
+
+---
+
+## 🔧 Working with Existing Code
+
+Comprehensive guide for brownfield development:
+
+- **[Brownfield Development Guide](./brownfield-guide.md)** - Complete guide for existing codebases (53 min read)
+  - Documentation phase strategies
+  - Track selection for brownfield
+  - Integration with existing patterns
+  - Phase-by-phase workflow guidance
+  - Common scenarios
+
+---
+
+## 📚 Quick References
+
+Essential reference materials:
+
+- **[Glossary](./glossary.md)** - Key terminology and concepts
+- **[FAQ](./faq.md)** - Frequently asked questions across all topics
+- **[Enterprise Agentic Development](./enterprise-agentic-development.md)** - Team collaboration strategies
+
+---
+
+## 🎯 Choose Your Path
+
+### I need to...
+
+**Build something new (greenfield)**
+→ Start with [Quick Start Guide](./quick-start.md)
+→ Then review [Scale Adaptive System](./scale-adaptive-system.md) to understand tracks
+
+**Fix a bug or add small feature**
+→ Go directly to [Quick Spec Flow](./quick-spec-flow.md)
+
+**Work with existing codebase (brownfield)**
+→ Read [Brownfield Development Guide](./brownfield-guide.md)
+→ Pay special attention to Phase 0 documentation requirements
+
+**Understand planning tracks and methodology**
+→ See [Scale Adaptive System](./scale-adaptive-system.md)
+
+**Find specific commands or answers**
+→ Check [FAQ](./faq.md)
+
+---
+
+## 📋 Workflow Guides
+
+Comprehensive documentation for all BMM workflows organized by phase:
+
+- **[Phase 1: Analysis Workflows](./workflows-analysis.md)** - Optional exploration and research workflows (595 lines)
+  - brainstorm-project, product-brief, research, and more
+  - When to use analysis workflows
+  - Creative and strategic tools
+
+- **[Phase 2: Planning Workflows](./workflows-planning.md)** - Scale-adaptive planning (967 lines)
+  - prd, tech-spec, gdd, narrative, ux
+  - Track-based planning approach (Quick Flow, BMad Method, Enterprise Method)
+  - Which planning workflow to use
+
+- **[Phase 3: Solutioning Workflows](./workflows-solutioning.md)** - Architecture and validation (638 lines)
+  - architecture, solutioning-gate-check
+  - Required for BMad Method and Enterprise Method tracks
+  - Preventing agent conflicts
+
+- **[Phase 4: Implementation Workflows](./workflows-implementation.md)** - Sprint-based development (1,634 lines)
+  - sprint-planning, create-story, dev-story, code-review
+  - Complete story lifecycle
+  - One-story-at-a-time discipline
+
+- **[Testing & QA Workflows](./test-architecture.md)** - Comprehensive quality assurance (1,420 lines)
+  - Test strategy, automation, quality gates
+  - TEA agent and test healing
+  - BMad-integrated vs standalone modes
+
+**Total: 34 workflows documented across all phases**
+
+### Advanced Workflow References
+
+For detailed technical documentation on specific complex workflows:
+
+- **[Document Project Workflow Reference](./workflow-document-project-reference.md)** - Technical deep-dive (445 lines)
+  - v1.2.0 context-safe architecture
+  - Scan levels, resumability, write-as-you-go
+  - Multi-part project detection
+  - Deep-dive mode for targeted analysis
+
+- **[Architecture Workflow Reference](./workflow-architecture-reference.md)** - Decision architecture guide (320 lines)
+  - Starter template intelligence
+  - Novel pattern design
+  - Implementation patterns for agent consistency
+  - Adaptive facilitation approach
+
+---
+
+## 🧪 Testing and Quality
+
+Quality assurance guidance:
+
+<!-- Test Architect documentation to be added -->
+
+- Test design workflows
+- Quality gates
+- Risk assessment
+- NFR validation
+
+---
+
+## 🏗️ Module Structure
+
+Understanding BMM components:
+
+- **[BMM Module README](../README.md)** - Overview of module structure
+  - Agent roster and roles
+  - Workflow organization
+  - Teams and collaboration
+  - Best practices
+
+---
+
+## 🌐 External Resources
+
+### Community and Support
+
+- **[Discord Community](https://discord.gg/gk8jAdXWmj)** - Get help from the community (#general-dev, #bugs-issues)
+- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features
+- **[YouTube Channel](https://www.youtube.com/@BMadCode)** - Video tutorials and walkthroughs
+
+### Additional Documentation
+
+- **[IDE Setup Guides](../../../docs/ide-info/)** - Configure your development environment
+  - Claude Code
+  - Cursor
+  - Windsurf
+  - VS Code
+  - Other IDEs
+
+---
+
+## 📊 Documentation Map
+
+```mermaid
+flowchart TD
+    START[New to BMM?]
+    START --> QS[Quick Start Guide]
+
+    QS --> DECIDE{What are you building?}
+
+    DECIDE -->|Bug fix or<br/>small feature| QSF[Quick Spec Flow]
+    DECIDE -->|New project| SAS[Scale Adaptive System]
+    DECIDE -->|Existing codebase| BF[Brownfield Guide]
+
+    QSF --> IMPL[Implementation]
+    SAS --> IMPL
+    BF --> IMPL
+
+    IMPL --> REF[Quick References<br/>Glossary, FAQ]
+
+    style START fill:#bfb,stroke:#333,stroke-width:2px,color:#000
+    style QS fill:#bbf,stroke:#333,stroke-width:2px,color:#000
+    style DECIDE fill:#ffb,stroke:#333,stroke-width:2px,color:#000
+    style IMPL fill:#f9f,stroke:#333,stroke-width:2px,color:#000
+```
+
+---
+
+## 💡 Tips for Using This Documentation
+
+1. **Start with Quick Start** if you're new - it provides the essential foundation
+2. **Use the FAQ** to find quick answers without reading entire guides
+3. **Bookmark Glossary** for terminology references while reading other docs
+4. **Follow the suggested paths** above based on your specific situation
+5. **Join Discord** for interactive help and community insights
+
+---
+
+**Ready to begin?** → [Start with the Quick Start Guide](./quick-start.md)

.bmad/bmm/docs/brownfield-guide.md

@@ -0,0 +1,754 @@
+# BMad Method Brownfield Development Guide
+
+**Complete guide for working with existing codebases**
+
+**Reading Time:** ~35 minutes
+
+---
+
+## Quick Navigation
+
+**Jump to:**
+
+- [Quick Reference](#quick-reference) - Commands and files
+- [Common Scenarios](#common-scenarios) - Real-world examples
+- [Best Practices](#best-practices) - Success tips
+
+---
+
+## What is Brownfield Development?
+
+Brownfield projects involve working within existing codebases rather than starting fresh:
+
+- **Bug fixes** - Single file changes
+- **Small features** - Adding to existing modules
+- **Feature sets** - Multiple related features
+- **Major integrations** - Complex architectural additions
+- **System expansions** - Enterprise-scale enhancements
+
+**Key Difference from Greenfield:** You must understand and respect existing patterns, architecture, and constraints.
+
+**Core Principle:** AI agents need comprehensive documentation to understand existing code before they can effectively plan or implement changes.
+
+---
+
+## Getting Started
+
+### Understanding Planning Tracks
+
+For complete track details, see [Scale Adaptive System](./scale-adaptive-system.md).
+
+**Brownfield tracks at a glance:**
+
+| Track                 | Scope                      | Typical Stories | Key Difference                                  |
+| --------------------- | -------------------------- | --------------- | ----------------------------------------------- |
+| **Quick Flow**        | Bug fixes, small features  | 1-15            | Must understand affected code and patterns      |
+| **BMad Method**       | Feature sets, integrations | 10-50+          | Integrate with existing architecture            |
+| **Enterprise Method** | Enterprise expansions      | 30+             | Full system documentation + compliance required |
+
+**Note:** Story counts are guidance, not definitions. Tracks are chosen based on planning needs.
+
+### Track Selection for Brownfield
+
+When you run `workflow-init`, it handles brownfield intelligently:
+
+**Step 1: Shows what it found**
+
+- Old planning docs (PRD, epics, stories)
+- Existing codebase
+
+**Step 2: Asks about YOUR work**
+
+> "Are these works in progress, previous effort, or proposed work?"
+
+- **(a) Works in progress** → Uses artifacts to determine level
+- **(b) Previous effort** → Asks you to describe NEW work
+- **(c) Proposed work** → Uses artifacts as guidance
+- **(d) None of these** → You explain your work
+
+**Step 3: Analyzes your description**
+
+- Keywords: "fix", "bug" → Quick Flow, "dashboard", "platform" → BMad Method, "enterprise", "multi-tenant" → Enterprise Method
+- Complexity assessment
+- Confirms suggested track with you
+
+**Key Principle:** System asks about YOUR current work first, uses old artifacts as context only.
+
+**Example: Old Complex PRD, New Simple Work**
+
+```
+System: "Found PRD.md (BMad Method track, 30 stories, 6 months old)"
+System: "Is this work in progress or previous effort?"
+You: "Previous effort - I'm just fixing a bug now"
+System: "Tell me about your current work"
+You: "Update payment method enums"
+System: "Quick Flow track (tech-spec approach). Correct?"
+You: "Yes"
+✅ Creates Quick Flow workflow
+```
+
+---
+
+## Phase 0: Documentation (Critical First Step)
+
+🚨 **For brownfield projects: Always ensure adequate AI-usable documentation before planning**
+
+### Default Recommendation: Run document-project
+
+**Best practice:** Run `document-project` workflow unless you have **confirmed, trusted, AI-optimized documentation**.
+
+### Why Document-Project is Almost Always the Right Choice
+
+Existing documentation often has quality issues that break AI workflows:
+
+**Common Problems:**
+
+- **Too Much Information (TMI):** Massive markdown files with 10s or 100s of level 2 sections
+- **Out of Date:** Documentation hasn't been updated with recent code changes
+- **Wrong Format:** Written for humans, not AI agents (lacks structure, index, clear patterns)
+- **Incomplete Coverage:** Missing critical architecture, patterns, or setup info
+- **Inconsistent Quality:** Some areas documented well, others not at all
+
+**Impact on AI Agents:**
+
+- AI agents hit token limits reading massive files
+- Outdated docs cause hallucinations (agent thinks old patterns still apply)
+- Missing structure means agents can't find relevant information
+- Incomplete coverage leads to incorrect assumptions
+
+### Documentation Decision Tree
+
+**Step 1: Assess Existing Documentation Quality**
+
+Ask yourself:
+
+- ✅ Is it **current** (updated in last 30 days)?
+- ✅ Is it **AI-optimized** (structured with index.md, clear sections, <500 lines per file)?
+- ✅ Is it **comprehensive** (architecture, patterns, setup all documented)?
+- ✅ Do you **trust** it completely for AI agent consumption?
+
+**If ANY answer is NO → Run `document-project`**
+
+**Step 2: Check for Massive Documents**
+
+If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
+
+1. **First:** Run `shard-doc` tool to split large files:
+
+   ```bash
+   # Load BMad Master or any agent
+   .bmad/core/tools/shard-doc.xml --input docs/massive-doc.md
+   ```
+
+   - Splits on level 2 sections by default
+   - Creates organized, manageable files
+   - Preserves content integrity
+
+2. **Then:** Run `index-docs` task to create navigation:
+
+   ```bash
+   .bmad/core/tasks/index-docs.xml --directory ./docs
+   ```
+
+3. **Finally:** Validate quality - if sharded docs still seem incomplete/outdated → Run `document-project`
+
+### Four Real-World Scenarios
+
+| Scenario | You Have                                   | Action                     | Why                                     |
+| -------- | ------------------------------------------ | -------------------------- | --------------------------------------- |
+| **A**    | No documentation                           | `document-project`         | Only option - generate from scratch     |
+| **B**    | Docs exist but massive/outdated/incomplete | `document-project`         | Safer to regenerate than trust bad docs |
+| **C**    | Good docs but no structure                 | `shard-doc` → `index-docs` | Structure existing content for AI       |
+| **D**    | Confirmed AI-optimized docs with index.md  | Skip Phase 0               | Rare - only if you're 100% confident    |
+
+### Scenario A: No Documentation (Most Common)
+
+**Action: Run document-project workflow**
+
+1. Load Analyst or Technical Writer (Paige) agent
+2. Run `*document-project`
+3. Choose scan level:
+   - **Quick** (2-5min): Pattern analysis, no source reading
+   - **Deep** (10-30min): Reads critical paths - **Recommended**
+   - **Exhaustive** (30-120min): Reads all files
+
+**Outputs:**
+
+- `docs/index.md` - Master AI entry point
+- `docs/project-overview.md` - Executive summary
+- `docs/architecture.md` - Architecture analysis
+- `docs/source-tree-analysis.md` - Directory structure
+- Additional files based on project type (API, web app, etc.)
+
+### Scenario B: Docs Exist But Quality Unknown/Poor (Very Common)
+
+**Action: Run document-project workflow (regenerate)**
+
+Even if `docs/` folder exists, if you're unsure about quality → **regenerate**.
+
+**Why regenerate instead of index?**
+
+- Outdated docs → AI makes wrong assumptions
+- Incomplete docs → AI invents missing information
+- TMI docs → AI hits token limits, misses key info
+- Human-focused docs → Missing AI-critical structure
+
+**document-project** will:
+
+- Scan actual codebase (source of truth)
+- Generate fresh, accurate documentation
+- Structure properly for AI consumption
+- Include only relevant, current information
+
+### Scenario C: Good Docs But Needs Structure
+
+**Action: Shard massive files, then index**
+
+If you have **good, current documentation** but it's in massive files:
+
+**Step 1: Shard large documents**
+
+```bash
+# For each massive doc (>500 lines or 10+ level 2 sections)
+.bmad/core/tools/shard-doc.xml \
+  --input docs/api-documentation.md \
+  --output docs/api/ \
+  --level 2  # Split on ## headers (default)
+```
+
+**Step 2: Generate index**
+
+```bash
+.bmad/core/tasks/index-docs.xml --directory ./docs
+```
+
+**Step 3: Validate**
+
+- Review generated `docs/index.md`
+- Check that sharded files are <500 lines each
+- Verify content is current and accurate
+- **If anything seems off → Run document-project instead**
+
+### Scenario D: Confirmed AI-Optimized Documentation (Rare)
+
+**Action: Skip Phase 0**
+
+Only skip if ALL conditions met:
+
+- ✅ `docs/index.md` exists and is comprehensive
+- ✅ Documentation updated within last 30 days
+- ✅ All doc files <500 lines with clear structure
+- ✅ Covers architecture, patterns, setup, API surface
+- ✅ You personally verified quality for AI consumption
+- ✅ Previous AI agents used it successfully
+
+**If unsure → Run document-project** (costs 10-30 minutes, saves hours of confusion)
+
+### Why document-project is Critical
+
+Without AI-optimized documentation, workflows fail:
+
+- **tech-spec** (Quick Flow) can't auto-detect stack/patterns → Makes wrong assumptions
+- **PRD** (BMad Method) can't reference existing code → Designs incompatible features
+- **architecture** can't build on existing structure → Suggests conflicting patterns
+- **story-context** can't inject existing patterns → Dev agent rewrites working code
+- **dev-story** invents implementations → Breaks existing integrations
+
+### Key Principle
+
+**When in doubt, run document-project.**
+
+It's better to spend 10-30 minutes generating fresh, accurate docs than to waste hours debugging AI agents working from bad documentation.
+
+---
+
+## Workflow Phases by Track
+
+### Phase 1: Analysis (Optional)
+
+**Workflows:**
+
+- `brainstorm-project` - Solution exploration
+- `research` - Technical/market research
+- `product-brief` - Strategic planning (BMad Method/Enterprise tracks only)
+
+**When to use:** Complex features, technical decisions, strategic additions
+
+**When to skip:** Bug fixes, well-understood features, time-sensitive changes
+
+See the [Workflows section in BMM README](../README.md) for details.
+
+### Phase 2: Planning (Required)
+
+**Planning approach adapts by track:**
+
+**Quick Flow:** Use `tech-spec` workflow
+
+- Creates tech-spec.md
+- Auto-detects existing stack (brownfield)
+- Confirms conventions with you
+- Generates implementation-ready stories
+
+**BMad Method/Enterprise:** Use `prd` workflow
+
+- Creates PRD.md + epic breakdown
+- References existing architecture
+- Plans integration points
+
+**Brownfield-specific:** See [Scale Adaptive System](./scale-adaptive-system.md) for complete workflow paths by track.
+
+### Phase 3: Solutioning (BMad Method/Enterprise Only)
+
+**Critical for brownfield:**
+
+- Review existing architecture FIRST
+- Document integration points explicitly
+- Plan backward compatibility
+- Consider migration strategy
+
+**Workflows:**
+
+- `create-architecture` - Extend architecture docs (BMad Method/Enterprise)
+- `solutioning-gate-check` - Validate before implementation (BMad Method/Enterprise)
+
+### Phase 4: Implementation (All Tracks)
+
+**Sprint-based development through story iteration:**
+
+```mermaid
+flowchart TD
+    SPRINT[sprint-planning<br/>Initialize tracking]
+    EPIC[epic-tech-context<br/>Per epic]
+    CREATE[create-story]
+    CONTEXT[story-context]
+    DEV[dev-story]
+    REVIEW[code-review]
+    CHECK{More stories?}
+    RETRO[retrospective<br/>Per epic]
+
+    SPRINT --> EPIC
+    EPIC --> CREATE
+    CREATE --> CONTEXT
+    CONTEXT --> DEV
+    DEV --> REVIEW
+    REVIEW --> CHECK
+    CHECK -->|Yes| CREATE
+    CHECK -->|No| RETRO
+
+    style SPRINT fill:#bfb,stroke:#333,stroke-width:2px,color:#000
+    style RETRO fill:#fbf,stroke:#333,stroke-width:2px,color:#000
+```
+
+**Status Progression:**
+
+- Epic: `backlog → contexted`
+- Story: `backlog → drafted → ready-for-dev → in-progress → review → done`
+
+**Brownfield-Specific Implementation Tips:**
+
+1. **Respect existing patterns** - Follow established conventions
+2. **Test integration thoroughly** - Validate interactions with existing code
+3. **Use feature flags** - Enable gradual rollout
+4. **Context injection matters** - epic-tech-context and story-context reference existing patterns
+
+---
+
+## Best Practices
+
+### 1. Always Document First
+
+Even if you know the code, AI agents need `document-project` output for context. Run it before planning.
+
+### 2. Be Specific About Current Work
+
+When workflow-init asks about your work:
+
+- ✅ "Update payment method enums to include Apple Pay"
+- ❌ "Fix stuff"
+
+### 3. Choose Right Documentation Approach
+
+- **Has good docs, no index?** → Run `index-docs` task (fast)
+- **No docs or need codebase analysis?** → Run `document-project` (Deep scan)
+
+### 4. Respect Existing Patterns
+
+Tech-spec and story-context will detect conventions. Follow them unless explicitly modernizing.
+
+### 5. Plan Integration Points Explicitly
+
+Document in tech-spec/architecture:
+
+- Which existing modules you'll modify
+- What APIs/services you'll integrate with
+- How data flows between new and existing code
+
+### 6. Design for Gradual Rollout
+
+- Use feature flags for new functionality
+- Plan rollback strategies
+- Maintain backward compatibility
+- Create migration scripts if needed
+
+### 7. Test Integration Thoroughly
+
+- Regression testing of existing features
+- Integration point validation
+- Performance impact assessment
+- API contract verification
+
+### 8. Use Sprint Planning Effectively
+
+- Run `sprint-planning` at Phase 4 start
+- Context epics before drafting stories
+- Update `sprint-status.yaml` as work progresses
+
+### 9. Leverage Context Injection
+
+- Run `epic-tech-context` before story drafting
+- Always create `story-context` before implementation
+- These reference existing patterns for consistency
+
+### 10. Learn Continuously
+
+- Run `retrospective` after each epic
+- Incorporate learnings into next stories
+- Update discovered patterns
+- Share insights across team
+
+---
+
+## Common Scenarios
+
+### Scenario 1: Bug Fix (Quick Flow)
+
+**Situation:** Authentication token expiration causing logout issues
+
+**Track:** Quick Flow
+
+**Workflow:**
+
+1. **Document:** Skip if auth system documented, else run `document-project` (Quick scan)
+2. **Plan:** Load PM → run `tech-spec`
+   - Analyzes bug
+   - Detects stack (Express, Jest)
+   - Confirms conventions
+   - Creates tech-spec.md + story
+3. **Implement:** Load DEV → run `dev-story`
+4. **Review:** Load DEV → run `code-review`
+
+**Time:** 2-4 hours
+
+---
+
+### Scenario 2: Small Feature (Quick Flow)
+
+**Situation:** Add "forgot password" to existing auth system
+
+**Track:** Quick Flow
+
+**Workflow:**
+
+1. **Document:** Run `document-project` (Deep scan of auth module if not documented)
+2. **Plan:** Load PM → run `tech-spec`
+   - Detects Next.js 13.4, NextAuth.js
+   - Analyzes existing auth patterns
+   - Confirms conventions
+   - Creates tech-spec.md + epic + 3-5 stories
+3. **Implement:** Load SM → `sprint-planning` → `create-story` → `story-context`
+   Load DEV → `dev-story` for each story
+4. **Review:** Load DEV → `code-review`
+
+**Time:** 1-3 days
+
+---
+
+### Scenario 3: Feature Set (BMad Method)
+
+**Situation:** Add user dashboard with analytics, preferences, activity
+
+**Track:** BMad Method
+
+**Workflow:**
+
+1. **Document:** Run `document-project` (Deep scan) - Critical for understanding existing UI patterns
+2. **Analyze:** Load Analyst → `research` (if evaluating analytics libraries)
+3. **Plan:** Load PM → `prd`
+4. **Solution:** Load Architect → `create-architecture` → `solutioning-gate-check`
+5. **Implement:** Sprint-based (10-15 stories)
+   - Load SM → `sprint-planning`
+   - Per epic: `epic-tech-context` → stories
+   - Load DEV → `dev-story` per story
+6. **Review:** Per story completion
+
+**Time:** 1-2 weeks
+
+---
+
+### Scenario 4: Complex Integration (BMad Method)
+
+**Situation:** Add real-time collaboration to document editor
+
+**Track:** BMad Method
+
+**Workflow:**
+
+1. **Document:** Run `document-project` (Exhaustive if not documented) - **Mandatory**
+2. **Analyze:** Load Analyst → `research` (WebSocket vs WebRTC vs CRDT)
+3. **Plan:** Load PM → `prd`
+4. **Solution:**
+   - Load Architect → `create-architecture` (extend for real-time layer)
+   - Load Architect → `solutioning-gate-check`
+5. **Implement:** Sprint-based (20-30 stories)
+
+**Time:** 3-6 weeks
+
+---
+
+### Scenario 5: Enterprise Expansion (Enterprise Method)
+
+**Situation:** Add multi-tenancy to single-tenant SaaS platform
+
+**Track:** Enterprise Method
+
+**Workflow:**
+
+1. **Document:** Run `document-project` (Exhaustive) - **Mandatory**
+2. **Analyze:** **Required**
+   - `brainstorm-project` - Explore multi-tenancy approaches
+   - `research` - Database sharding, tenant isolation, pricing
+   - `product-brief` - Strategic document
+3. **Plan:** Load PM → `prd` (comprehensive)
+4. **Solution:**
+   - `create-architecture` - Full system architecture
+   - `integration-planning` - Phased migration strategy
+   - `create-architecture` - Multi-tenancy architecture
+   - `validate-architecture` - External review
+   - `solutioning-gate-check` - Executive approval
+5. **Implement:** Phased sprint-based (50+ stories)
+
+**Time:** 3-6 months
+
+---
+
+## Troubleshooting
+
+### AI Agents Lack Codebase Understanding
+
+**Symptoms:**
+
+- Suggestions don't align with existing patterns
+- Ignores available components
+- Doesn't reference existing code
+
+**Solution:**
+
+1. Run `document-project` with Deep scan
+2. Verify `docs/index.md` exists
+3. Check documentation completeness
+4. Run deep-dive on specific areas if needed
+
+### Have Documentation But Agents Can't Find It
+
+**Symptoms:**
+
+- README.md, ARCHITECTURE.md exist
+- AI agents ask questions already answered
+- No `docs/index.md` file
+
+**Solution:**
+
+- **Quick fix:** Run `index-docs` task (2-5min)
+- **Comprehensive:** Run `document-project` workflow (10-30min)
+
+### Integration Points Unclear
+
+**Symptoms:**
+
+- Not sure how to connect new code to existing
+- Unsure which files to modify
+
+**Solution:**
+
+1. Ensure `document-project` captured existing architecture
+2. Check `story-context` - should document integration points
+3. In tech-spec/architecture - explicitly document:
+   - Which existing modules to modify
+   - What APIs/services to integrate with
+   - Data flow between new and existing code
+4. Review architecture document for integration guidance
+
+### Existing Tests Breaking
+
+**Symptoms:**
+
+- Regression test failures
+- Previously working functionality broken
+
+**Solution:**
+
+1. Review changes against existing patterns
+2. Verify API contracts unchanged (unless intentionally versioned)
+3. Run `test-review` workflow (TEA agent)
+4. Add regression testing to DoD
+5. Consider feature flags for gradual rollout
+
+### Inconsistent Patterns Being Introduced
+
+**Symptoms:**
+
+- New code style doesn't match existing
+- Different architectural approach
+
+**Solution:**
+
+1. Check convention detection (Quick Spec Flow should detect patterns)
+2. Review documentation - ensure `document-project` captured patterns
+3. Use `story-context` - injects pattern guidance
+4. Add to code-review checklist: pattern adherence, convention consistency
+5. Run retrospective to identify deviations early
+
+---
+
+## Quick Reference
+
+### Commands by Phase
+
+```bash
+# Phase 0: Documentation (If Needed)
+# Analyst agent:
+document-project        # Create comprehensive docs (10-30min)
+# OR load index-docs task for existing docs (2-5min)
+
+# Phase 1: Analysis (Optional)
+# Analyst agent:
+brainstorm-project      # Explore solutions
+research                # Gather data
+product-brief           # Strategic planning (BMad Method/Enterprise only)
+
+# Phase 2: Planning (Required)
+# PM agent:
+tech-spec               # Quick Flow track
+prd                     # BMad Method/Enterprise tracks
+
+# Phase 3: Solutioning (BMad Method/Enterprise)
+# Architect agent:
+create-architecture          # Extend architecture
+solutioning-gate-check       # Final validation
+
+# Phase 4: Implementation (All Tracks)
+# SM agent:
+sprint-planning              # Initialize tracking
+epic-tech-context            # Epic context
+create-story                 # Draft story
+story-context                # Story context
+
+# DEV agent:
+dev-story                    # Implement
+code-review                  # Review
+
+# SM agent:
+retrospective                # After epic
+correct-course               # If issues
+```
+
+### Key Files
+
+**Phase 0 Output:**
+
+- `docs/index.md` - **Master AI entry point (REQUIRED)**
+- `docs/project-overview.md`
+- `docs/architecture.md`
+- `docs/source-tree-analysis.md`
+
+**Phase 1-3 Tracking:**
+
+- `docs/bmm-workflow-status.yaml` - Progress tracker
+
+**Phase 2 Planning:**
+
+- `docs/tech-spec.md` (Quick Flow track)
+- `docs/PRD.md` (BMad Method/Enterprise tracks)
+- Epic breakdown
+
+**Phase 3 Architecture:**
+
+- `docs/architecture.md` (BMad Method/Enterprise tracks)
+
+**Phase 4 Implementation:**
+
+- `docs/sprint-status.yaml` - **Single source of truth**
+- `docs/epic-{n}-context.md`
+- `docs/stories/{epic}-{story}-{title}.md`
+- `docs/stories/{epic}-{story}-{title}-context.md`
+
+### Decision Flowchart
+
+```mermaid
+flowchart TD
+    START([Brownfield Project])
+    CHECK{Has docs/<br/>index.md?}
+
+    START --> CHECK
+    CHECK -->|No| DOC[document-project<br/>Deep scan]
+    CHECK -->|Yes| TRACK{What Track?}
+
+    DOC --> TRACK
+
+    TRACK -->|Quick Flow| TS[tech-spec]
+    TRACK -->|BMad Method| PRD[prd → architecture]
+    TRACK -->|Enterprise| PRD2[prd → arch + security/devops]
+
+    TS --> IMPL[Phase 4<br/>Implementation]
+    PRD --> IMPL
+    PRD2 --> IMPL
+
+    style START fill:#f9f,stroke:#333,stroke-width:2px,color:#000
+    style DOC fill:#ffb,stroke:#333,stroke-width:2px,color:#000
+    style IMPL fill:#bfb,stroke:#333,stroke-width:2px,color:#000
+```
+
+---
+
+## Prevention Tips
+
+**Avoid issues before they happen:**
+
+1. ✅ **Always run document-project for brownfield** - Saves context issues later
+2. ✅ **Use fresh chats for complex workflows** - Prevents hallucinations
+3. ✅ **Verify files exist before workflows** - Check PRD, epics, stories present
+4. ✅ **Read agent menu first** - Confirm agent has the workflow
+5. ✅ **Start with simpler track if unsure** - Easy to upgrade (Quick Flow → BMad Method)
+6. ✅ **Keep status files updated** - Manual updates when needed
+7. ✅ **Run retrospectives after epics** - Catch issues early
+8. ✅ **Follow phase sequence** - Don't skip required phases
+
+---
+
+## Related Documentation
+
+- **[Scale Adaptive System](./scale-adaptive-system.md)** - Understanding tracks and complexity
+- **[Quick Spec Flow](./quick-spec-flow.md)** - Fast-track for Quick Flow
+- **[Quick Start Guide](./quick-start.md)** - Getting started with BMM
+- **[Glossary](./glossary.md)** - Key terminology
+- **[FAQ](./faq.md)** - Common questions
+- **[Workflow Documentation](./README.md#-workflow-guides)** - Complete workflow reference
+
+---
+
+## Support and Resources
+
+**Community:**
+
+- [Discord](https://discord.gg/gk8jAdXWmj) - #general-dev, #bugs-issues
+- [GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)
+- [YouTube Channel](https://www.youtube.com/@BMadCode)
+
+**Documentation:**
+
+- [Test Architect Guide](./test-architecture.md) - Comprehensive testing strategy
+- [BMM Module README](../README.md) - Complete module and workflow reference
+
+---
+
+_Brownfield development is about understanding and respecting what exists while thoughtfully extending it._

.bmad/bmm/docs/enterprise-agentic-development.md

@@ -0,0 +1,680 @@
+# Enterprise Agentic Development with BMad Method
+
+**The paradigm shift: From team-based story parallelism to individual epic ownership**
+
+**Reading Time:** ~18 minutes
+
+---
+
+## Table of Contents
+
+- [The Paradigm Shift](#the-paradigm-shift)
+- [The Evolving Role of Product Managers and UX Designers](#the-evolving-role-of-product-managers-and-ux-designers)
+- [How BMad Method Enables PM/UX Technical Evolution](#how-bmad-method-enables-pmux-technical-evolution)
+- [Team Collaboration Patterns](#team-collaboration-patterns)
+- [Work Distribution Strategies](#work-distribution-strategies)
+- [Enterprise Configuration with Git Submodules](#enterprise-configuration-with-git-submodules)
+- [Best Practices](#best-practices)
+- [Common Scenarios](#common-scenarios)
+
+---
+
+## The Paradigm Shift
+
+### Traditional Agile: Team-Based Story Parallelism
+
+- **Epic duration:** 4-12 weeks across multiple sprints
+- **Story duration:** 2-5 days per developer
+- **Team size:** 5-9 developers working on same epic
+- **Parallelization:** Multiple devs on stories within single epic
+- **Coordination:** Constant - daily standups, merge conflicts, integration overhead
+
+**Example:** Payment Processing Epic
+
+- Sprint 1-2: Backend API (Dev A)
+- Sprint 1-2: Frontend UI (Dev B)
+- Sprint 2-3: Testing (Dev C)
+- **Result:** 6-8 weeks, 3 developers, high coordination
+
+### Agentic Development: Individual Epic Ownership
+
+- **Epic duration:** Hours to days (not weeks)
+- **Story duration:** 30 min to 4 hours with AI agent
+- **Team size:** 1 developer + AI agents completes full epics
+- **Parallelization:** Developers work on separate epics
+- **Coordination:** Minimal - epic boundaries, async updates
+
+**Same Example:** Payment Processing Epic
+
+- Day 1 AM: Backend API stories (1 dev + agent, 3-4 stories)
+- Day 1 PM: Frontend UI stories (same dev + agent, 2-3 stories)
+- Day 2: Testing & deployment (same dev + agent, 2 stories)
+- **Result:** 1-2 days, 1 developer, minimal coordination
+
+### The Core Difference
+
+**What changed:** AI agents collapse story duration from days to hours, making **epic-level ownership** practical.
+
+**Impact:** Single developer with BMad Method can deliver in 1 day what previously required full team and multiple sprints.
+
+---
+
+## The Evolving Role of Product Managers and UX Designers
+
+### The Future is Now
+
+Product Managers and UX Designers are undergoing **the most significant transformation since the creation of these disciplines**. The emergence of AI agents is creating a new breed of technical product leaders who translate vision directly into working code.
+
+### From Spec Writers to Code Orchestrators
+
+**Traditional PM/UX (Pre-2025):**
+
+- Write PRDs, hand off to engineering
+- Wait weeks/months for implementation
+- Limited validation capabilities
+- Non-technical role, heavy on process
+
+**Emerging PM/UX (2025+):**
+
+- Write AI-optimized PRDs that **feed agentic pipelines directly**
+- Generate working prototypes in 10-15 minutes
+- Review pull requests from AI agents
+- Technical fluency is **table stakes**, not optional
+- Orchestrate cloud-based AI agent teams
+
+### Industry Research (November 2025)
+
+- **56% of product professionals** cite AI/ML as top focus
+- **AI agents automating** customer discovery, PRD creation, status reporting
+- **PRD-to-Code automation** enables PMs to build and deploy apps in 10-15 minutes
+- **By 2026**: Roles converging into "Full-Stack Product Lead" (PM + Design + Engineering)
+- **Very high salaries** for AI agent PMs who orchestrate autonomous dev systems
+
+### Required Skills for Modern PMs/UX
+
+1. **AI Prompt Engineering** - Writing PRDs AI agents can execute autonomously
+2. **Coding Literacy** - Understanding code structure, APIs, data flows (not production coding)
+3. **Agentic Workflow Design** - Orchestrating multi-agent systems (planning → design → dev)
+4. **Technical Architecture** - Reasoning frameworks, memory systems, tool integration
+5. **Data Literacy** - Interpreting model outputs, spotting trends, identifying gaps
+6. **Code Review** - Evaluating AI-generated PRs for correctness and vision alignment
+
+### What Remains Human
+
+**AI Can't Replace:**
+
+- Product vision (market dynamics, customer pain, strategic positioning)
+- Empathy (deep user research, emotional intelligence, stakeholder management)
+- Creativity (novel problem-solving, disruptive thinking)
+- Judgment (prioritization decisions, trade-off analysis)
+- Ethics (responsible AI use, privacy, accessibility)
+
+**What Changes:**
+
+- PMs/UX spend **more time on human elements** (AI handles routine execution)
+- Barrier between "thinking" and "building" collapses
+- Product leaders become **builder-thinkers**, not just spec writers
+
+### The Convergence
+
+- **PMs learning to code** with GitHub Copilot, Cursor, v0
+- **UX designers generating code** with UXPin Merge, Figma-to-code tools
+- **Developers becoming orchestrators** reviewing AI output vs writing from scratch
+
+**The Bottom Line:** By 2026, successful PMs/UX will fluently operate in both vision and execution. **BMad Method provides the structured framework to make this transition.**
+
+---
+
+## How BMad Method Enables PM/UX Technical Evolution
+
+BMad Method is specifically designed to position PMs and UX designers for this future.
+
+### 1. AI-Executable PRD Generation
+
+**PM Workflow:**
+
+```bash
+bmad pm *create-prd
+```
+
+**BMad produces:**
+
+- Structured, machine-readable requirements
+- Testable acceptance criteria per requirement
+- Clear epic/story decomposition
+- Technical context for AI agents
+
+**Why it matters:** Traditional PRDs are human-readable prose. BMad PRDs are **AI-executable work packages**.
+
+**PM Value:** Write once, automatically translated into agent-ready stories. No engineering bottleneck for translation.
+
+### 2. Automated Epic/Story Breakdown
+
+**PM Workflow:**
+
+```bash
+bmad pm *create-epics-and-stories
+```
+
+**BMad produces:**
+
+- Epic files with clear objectives
+- Story files with acceptance criteria, context, technical guidance
+- Priority assignments (P0-P3)
+- Dependency mapping
+
+**Why it matters:** Stories become **work packages for cloud AI agents**. Each story is self-contained with full context.
+
+**PM Value:** No more "story refinement sessions" with engineering. AI agents execute directly from BMad stories.
+
+### 3. Human-in-the-Loop Architecture
+
+**Architect/PM Workflow:**
+
+```bash
+bmad architect *create-architecture
+```
+
+**BMad produces:**
+
+- System architecture aligned with PRD
+- Architecture Decision Records (ADRs)
+- Epic-specific technical guidance
+- Integration patterns and standards
+
+**Why it matters:** PMs can **understand and validate** technical decisions. Architecture is conversational, not template-driven.
+
+**PM Value:** Technical fluency built through guided architecture process. PMs learn while creating.
+
+### 4. Cloud Agentic Pipeline (Emerging Pattern)
+
+**Current State (2025):**
+
+```
+PM writes BMad PRD
+   ↓
+create-epics-and-stories generates story queue
+   ↓
+Stories loaded by human developers + BMad agents
+   ↓
+Developers create PRs
+   ↓
+PM/Team reviews PRs
+   ↓
+Merge and deploy
+```
+
+**Near Future (2026):**
+
+```
+PM writes BMad PRD
+   ↓
+create-epics-and-stories generates story queue
+   ↓
+Stories automatically fed to cloud AI agent pool
+   ↓
+AI agents implement stories in parallel
+   ↓
+AI agents create pull requests
+   ↓
+PM/UX/Senior Devs review PRs
+   ↓
+Approved PRs auto-merge
+   ↓
+Continuous deployment to production
+```
+
+**Time Savings:**
+
+- **Traditional:** PM writes spec → 2-4 weeks engineering → review → deploy (6-8 weeks)
+- **BMad Agentic:** PM writes PRD → AI agents implement → review PRs → deploy (2-5 days)
+
+### 5. UX Design Integration
+
+**UX Designer Workflow:**
+
+```bash
+bmad ux *create-design
+```
+
+**BMad produces:**
+
+- Component-based design system
+- Interaction patterns aligned with tech stack
+- Accessibility guidelines
+- Responsive design specifications
+
+**Why it matters:** Design specs become **implementation-ready** for AI agents. No "lost in translation" between design and dev.
+
+**UX Value:** Designs validated through working prototypes, not static mocks. Technical understanding built through BMad workflows.
+
+### 6. PM Technical Skills Development
+
+**BMad teaches PMs technical skills through:**
+
+- **Conversational workflows** - No pre-requisite knowledge, learn by doing
+- **Architecture facilitation** - Understand system design through guided questions
+- **Story context assembly** - See how code patterns inform implementation
+- **Code review workflows** - Learn to evaluate code quality, patterns, standards
+
+**Example:** PM runs `create-architecture` workflow:
+
+- BMad asks about scale, performance, integrations
+- PM answers business questions
+- BMad explains technical implications
+- PM learns architecture concepts while making decisions
+
+**Result:** PMs gain **working technical knowledge** without formal CS education.
+
+### 7. Organizational Leverage
+
+**Traditional Model:**
+
+- 1 PM → supports 5-9 developers → delivers 1-2 features/quarter
+
+**BMad Agentic Model:**
+
+- 1 PM → writes BMad PRD → 20-50 AI agents execute stories in parallel → delivers 5-10 features/quarter
+
+**Leverage multiplier:** 5-10× with same PM headcount.
+
+### 8. Quality Consistency
+
+**BMad ensures:**
+
+- AI agents follow architectural patterns consistently (via story-context)
+- Code standards applied uniformly (via epic-tech-context)
+- PRD traceability throughout implementation (via acceptance criteria)
+- No "telephone game" between PM, design, and dev
+
+**PM Value:** What gets built **matches what was specified**, drastically reducing rework.
+
+### 9. Rapid Prototyping for Validation
+
+**PM Workflow (with BMad + Cursor/v0):**
+
+1. Use BMad to generate PRD structure and requirements
+2. Extract key user flow from PRD
+3. Feed to Cursor/v0 with BMad context
+4. Working prototype in 10-15 minutes
+5. Validate with users **before** committing to full development
+
+**Traditional:** Months of development to validate idea
+**BMad Agentic:** Hours of development to validate idea
+
+### 10. Career Path Evolution
+
+**BMad positions PMs for emerging roles:**
+
+- **AI Agent Product Manager** - Orchestrate autonomous development systems
+- **Full-Stack Product Lead** - Oversee product, design, engineering with AI leverage
+- **Technical Product Strategist** - Bridge business vision and technical execution
+
+**Hiring advantage:** PMs using BMad demonstrate:
+
+- Technical fluency (can read architecture, validate tech decisions)
+- AI-native workflows (structured requirements, agentic orchestration)
+- Results (ship 5-10× faster than peers)
+
+---
+
+## Team Collaboration Patterns
+
+### Old Pattern: Story Parallelism
+
+**Traditional Agile:**
+
+```
+Epic: User Dashboard (8 weeks)
+├─ Story 1: Backend API (Dev A, Sprint 1-2)
+├─ Story 2: Frontend Layout (Dev B, Sprint 1-2)
+├─ Story 3: Data Viz (Dev C, Sprint 2-3)
+└─ Story 4: Integration Testing (Team, Sprint 3-4)
+
+Challenge: Coordination overhead, merge conflicts, integration issues
+```
+
+### New Pattern: Epic Ownership
+
+**Agentic Development:**
+
+```
+Project: Analytics Platform (2-3 weeks)
+
+Developer A:
+└─ Epic 1: User Dashboard (3 days, 12 stories sequentially with AI)
+
+Developer B:
+└─ Epic 2: Admin Panel (4 days, 15 stories sequentially with AI)
+
+Developer C:
+└─ Epic 3: Reporting Engine (5 days, 18 stories sequentially with AI)
+
+Benefit: Minimal coordination, epic-level ownership, clear boundaries
+```
+
+---
+
+## Work Distribution Strategies
+
+### Strategy 1: Epic-Based (Recommended)
+
+**Best for:** 2-10 developers
+
+**Approach:** Each developer owns complete epics, works sequentially through stories
+
+**Example:**
+
+```yaml
+epics:
+  - id: epic-1
+    title: Payment Processing
+    owner: alice
+    stories: 8
+    estimate: 2 days
+
+  - id: epic-2
+    title: User Dashboard
+    owner: bob
+    stories: 12
+    estimate: 3 days
+```
+
+**Benefits:** Clear ownership, minimal conflicts, epic cohesion, reduced coordination
+
+### Strategy 2: Layer-Based
+
+**Best for:** Full-stack apps, specialized teams
+
+**Example:**
+
+```
+Frontend Dev: Epic 1 (Product Catalog UI), Epic 3 (Cart UI)
+Backend Dev: Epic 2 (Product API), Epic 4 (Cart Service)
+```
+
+**Benefits:** Developers in expertise area, true parallel work, clear API contracts
+
+**Requirements:** Strong architecture phase, clear API contracts upfront
+
+### Strategy 3: Feature-Based
+
+**Best for:** Large teams (10+ developers)
+
+**Example:**
+
+```
+Team A (2 devs): Payments feature (4 epics)
+Team B (2 devs): User Management feature (3 epics)
+Team C (2 devs): Analytics feature (3 epics)
+```
+
+**Benefits:** Feature team autonomy, domain expertise, scalable to large orgs
+
+---
+
+## Enterprise Configuration with Git Submodules
+
+### The Challenge
+
+**Problem:** Teams customize BMad (agents, workflows, configs) but don't want personal tooling in main repo.
+
+**Anti-pattern:** Adding `.bmad/` to `.gitignore` breaks IDE tools, submodule management.
+
+### The Solution: Git Submodules
+
+**Benefits:**
+
+- BMad exists in project but tracked separately
+- Each developer controls their own BMad version/config
+- Optional team config sharing via submodule repo
+- IDE tools maintain proper context
+
+### Setup (New Projects)
+
+**1. Create optional team config repo:**
+
+```bash
+git init bmm-config
+cd bmm-config
+npx bmad-method install
+# Customize for team standards
+git commit -m "Team BMM config"
+git push origin main
+```
+
+**2. Add submodule to project:**
+
+```bash
+cd /path/to/your-project
+git submodule add https://github.com/your-org/bmm-config.git bmad
+git commit -m "Add BMM as submodule"
+```
+
+**3. Team members initialize:**
+
+```bash
+git clone https://github.com/your-org/your-project.git
+cd your-project
+git submodule update --init --recursive
+# Make personal customizations in .bmad/
+```
+
+### Daily Workflow
+
+**Work in main project:**
+
+```bash
+cd /path/to/your-project
+# BMad available at ./.bmad/, load agents normally
+```
+
+**Update personal config:**
+
+```bash
+cd bmad
+# Make changes, commit locally, don't push unless sharing
+```
+
+**Update to latest team config:**
+
+```bash
+cd bmad
+git pull origin main
+```
+
+### Configuration Strategies
+
+**Option 1: Fully Personal** - No submodule, each dev installs independently, use `.gitignore`
+
+**Option 2: Team Baseline + Personal** - Submodule has team standards, devs add personal customizations locally
+
+**Option 3: Full Team Sharing** - All configs in submodule, team collaborates on improvements
+
+---
+
+## Best Practices
+
+### 1. Epic Ownership
+
+- **Do:** Assign entire epic to one developer (context → implementation → retro)
+- **Don't:** Split epics across multiple developers (coordination overhead, context loss)
+
+### 2. Dependency Management
+
+- **Do:** Identify epic dependencies in planning, document API contracts, complete prerequisites first
+- **Don't:** Start dependent epic before prerequisite ready, change API contracts without coordination
+
+### 3. Communication Cadence
+
+**Traditional:** Daily standups essential
+**Agentic:** Lighter coordination
+
+**Recommended:**
+
+- Daily async updates ("Epic 1, 60% complete, no blockers")
+- Twice-weekly 15min sync
+- Epic completion demos
+- Sprint retro after all epics complete
+
+### 4. Branch Strategy
+
+```bash
+feature/epic-1-payment-processing    (Alice)
+feature/epic-2-user-dashboard        (Bob)
+feature/epic-3-admin-panel           (Carol)
+
+# PR and merge when epic complete
+```
+
+### 5. Testing Strategy
+
+- **Story-level:** Unit tests (DoD requirement, written by agent during dev-story)
+- **Epic-level:** Integration tests across stories
+- **Project-level:** E2E tests after multiple epics complete
+
+### 6. Documentation Updates
+
+- **Real-time:** `sprint-status.yaml` updated by workflows
+- **Epic completion:** Update architecture docs, API docs, README if changed
+- **Sprint completion:** Incorporate retrospective insights
+
+### 7. Metrics (Different from Traditional)
+
+**Traditional:** Story points per sprint, burndown charts
+**Agentic:** Epics per week, stories per day, time to epic completion
+
+**Example velocity:**
+
+- Junior dev + AI: 1-2 epics/week (8-15 stories)
+- Mid-level dev + AI: 2-3 epics/week (15-25 stories)
+- Senior dev + AI: 3-5 epics/week (25-40 stories)
+
+---
+
+## Common Scenarios
+
+### Scenario 1: Startup (2 Developers)
+
+**Project:** SaaS MVP (Level 3)
+
+**Distribution:**
+
+```
+Developer A:
+├─ Epic 1: Authentication (3 days)
+├─ Epic 3: Payment Integration (2 days)
+└─ Epic 5: Admin Dashboard (3 days)
+
+Developer B:
+├─ Epic 2: Core Product Features (4 days)
+├─ Epic 4: Analytics (3 days)
+└─ Epic 6: Notifications (2 days)
+
+Total: ~2 weeks
+Traditional estimate: 3-4 months
+```
+
+**BMM Setup:** Direct installation, both use Claude Code, minimal customization
+
+### Scenario 2: Mid-Size Team (8 Developers)
+
+**Project:** Enterprise Platform (Level 4)
+
+**Distribution (Layer-Based):**
+
+```
+Backend (2 devs): 6 API epics
+Frontend (2 devs): 6 UI epics
+Full-stack (2 devs): 4 integration epics
+DevOps (1 dev): 3 infrastructure epics
+QA (1 dev): 1 E2E testing epic
+
+Total: ~3 weeks
+Traditional estimate: 9-12 months
+```
+
+**BMM Setup:** Git submodule, team config repo, mix of Claude Code/Cursor users
+
+### Scenario 3: Large Enterprise (50+ Developers)
+
+**Project:** Multi-Product Platform
+
+**Organization:**
+
+- 5 product teams (8-10 devs each)
+- 1 platform team (10 devs - shared services)
+- 1 infrastructure team (5 devs)
+
+**Distribution (Feature-Based):**
+
+```
+Product Team A: Payments (10 epics, 2 weeks)
+Product Team B: User Mgmt (12 epics, 2 weeks)
+Product Team C: Analytics (8 epics, 1.5 weeks)
+Product Team D: Admin Tools (10 epics, 2 weeks)
+Product Team E: Mobile (15 epics, 3 weeks)
+
+Platform Team: Shared Services (continuous)
+Infrastructure Team: DevOps (continuous)
+
+Total: 3-4 months
+Traditional estimate: 2-3 years
+```
+
+**BMM Setup:** Each team has own submodule config, org-wide base config, variety of IDE tools
+
+---
+
+## Summary
+
+### Key Transformation
+
+**Work Unit Changed:**
+
+- **Old:** Story = unit of work assignment
+- **New:** Epic = unit of work assignment
+
+**Why:** AI agents collapse story duration (days → hours), making epic ownership practical.
+
+### Velocity Impact
+
+- **Traditional:** Months for epic delivery, heavy coordination
+- **Agentic:** Days for epic delivery, minimal coordination
+- **Result:** 10-50× productivity gains
+
+### PM/UX Evolution
+
+**BMad Method enables:**
+
+- PMs to write AI-executable PRDs
+- UX designers to validate through working prototypes
+- Technical fluency without CS degrees
+- Orchestration of cloud AI agent teams
+- Career evolution to Full-Stack Product Lead
+
+### Enterprise Adoption
+
+**Git submodules:** Best practice for BMM management across teams
+**Team flexibility:** Mix of tools (Claude Code, Cursor, Windsurf) with shared BMM foundation
+**Scalable patterns:** Epic-based, layer-based, feature-based distribution strategies
+
+### The Future (2026)
+
+PMs write BMad PRDs → Stories auto-fed to cloud AI agents → Parallel implementation → Human review of PRs → Continuous deployment
+
+**The future isn't AI replacing PMs—it's AI-augmented PMs becoming 10× more powerful.**
+
+---
+
+## Related Documentation
+
+- [FAQ](./faq.md) - Common questions
+- [Scale Adaptive System](./scale-adaptive-system.md) - Project levels explained
+- [Quick Start Guide](./quick-start.md) - Getting started
+- [Workflow Documentation](./README.md#-workflow-guides) - Complete workflow reference
+- [Agents Guide](./agents-guide.md) - Understanding BMad agents
+
+---
+
+_BMad Method fundamentally changes how PMs work, how teams structure work, and how products get built. Understanding these patterns is essential for enterprise success in the age of AI agents._

.bmad/bmm/docs/faq.md

@@ -0,0 +1,587 @@
+# BMM Frequently Asked Questions
+
+Quick answers to common questions about the BMad Method Module.
+
+---
+
+## Table of Contents
+
+- [Getting Started](#getting-started)
+- [Choosing the Right Level](#choosing-the-right-level)
+- [Workflows and Phases](#workflows-and-phases)
+- [Planning Documents](#planning-documents)
+- [Implementation](#implementation)
+- [Brownfield Development](#brownfield-development)
+- [Tools and Technical](#tools-and-technical)
+
+---
+
+## Getting Started
+
+### Q: Do I always need to run workflow-init?
+
+**A:** No, once you learn the flow you can go directly to workflows. However, workflow-init is helpful because it:
+
+- Determines your project's appropriate level automatically
+- Creates the tracking status file
+- Routes you to the correct starting workflow
+
+For experienced users: use the [Quick Reference](./quick-start.md#quick-reference-agent-document-mapping) to go directly to the right agent/workflow.
+
+### Q: Why do I need fresh chats for each workflow?
+
+**A:** Context-intensive workflows (like brainstorming, PRD creation, architecture design) can cause AI hallucinations if run in sequence within the same chat. Starting fresh ensures the agent has maximum context capacity for each workflow. This is particularly important for:
+
+- Planning workflows (PRD, architecture)
+- Analysis workflows (brainstorming, research)
+- Complex story implementation
+
+Quick workflows like status checks can reuse chats safely.
+
+### Q: Can I skip workflow-status and just start working?
+
+**A:** Yes, if you already know your project level and which workflow comes next. workflow-status is mainly useful for:
+
+- New projects (guides initial setup)
+- When you're unsure what to do next
+- After breaks in work (reminds you where you left off)
+- Checking overall progress
+
+### Q: What's the minimum I need to get started?
+
+**A:** For the fastest path:
+
+1. Install BMad Method: `npx bmad-method@alpha install`
+2. For small changes: Load PM agent → run tech-spec → implement
+3. For larger projects: Load PM agent → run prd → architect → implement
+
+### Q: How do I know if I'm in Phase 1, 2, 3, or 4?
+
+**A:** Check your `bmm-workflow-status.md` file (created by workflow-init). It shows your current phase and progress. If you don't have this file, you can also tell by what you're working on:
+
+- **Phase 1** - Brainstorming, research, product brief (optional)
+- **Phase 2** - Creating either a PRD or tech-spec (always required)
+- **Phase 3** - Architecture design (Level 2-4 only)
+- **Phase 4** - Actually writing code, implementing stories
+
+---
+
+## Choosing the Right Level
+
+### Q: How do I know which level my project is?
+
+**A:** Use workflow-init for automatic detection, or self-assess using these keywords:
+
+- **Level 0:** "fix", "bug", "typo", "small change", "patch" → 1 story
+- **Level 1:** "simple", "basic", "small feature", "add" → 2-10 stories
+- **Level 2:** "dashboard", "several features", "admin panel" → 5-15 stories
+- **Level 3:** "platform", "integration", "complex", "system" → 12-40 stories
+- **Level 4:** "enterprise", "multi-tenant", "multiple products" → 40+ stories
+
+When in doubt, start smaller. You can always run create-prd later if needed.
+
+### Q: Can I change levels mid-project?
+
+**A:** Yes! If you started at Level 1 but realize it's Level 2, you can run create-prd to add proper planning docs. The system is flexible - your initial level choice isn't permanent.
+
+### Q: What if workflow-init suggests the wrong level?
+
+**A:** You can override it! workflow-init suggests a level but always asks for confirmation. If you disagree, just say so and choose the level you think is appropriate. Trust your judgment.
+
+### Q: Do I always need architecture for Level 2?
+
+**A:** No, architecture is **optional** for Level 2. Only create architecture if you need system-level design. Many Level 2 projects work fine with just PRD + epic-tech-context created during implementation.
+
+### Q: What's the difference between Level 1 and Level 2?
+
+**A:**
+
+- **Level 1:** 1-10 stories, uses tech-spec (simpler, faster), no architecture
+- **Level 2:** 5-15 stories, uses PRD (product-focused), optional architecture
+
+The overlap (5-10 stories) is intentional. Choose based on:
+
+- Need product-level planning? → Level 2
+- Just need technical plan? → Level 1
+- Multiple epics? → Level 2
+- Single epic? → Level 1
+
+---
+
+## Workflows and Phases
+
+### Q: What's the difference between workflow-status and workflow-init?
+
+**A:**
+
+- **workflow-status:** Checks existing status and tells you what's next (use when continuing work)
+- **workflow-init:** Creates new status file and sets up project (use when starting new project)
+
+If status file exists, use workflow-status. If not, use workflow-init.
+
+### Q: Can I skip Phase 1 (Analysis)?
+
+**A:** Yes! Phase 1 is optional for all levels, though recommended for complex projects. Skip if:
+
+- Requirements are clear
+- No research needed
+- Time-sensitive work
+- Small changes (Level 0-1)
+
+### Q: When is Phase 3 (Architecture) required?
+
+**A:**
+
+- **Level 0-1:** Never (skip entirely)
+- **Level 2:** Optional (only if system design needed)
+- **Level 3-4:** Required (comprehensive architecture mandatory)
+
+### Q: What happens if I skip a recommended workflow?
+
+**A:** Nothing breaks! Workflows are guidance, not enforcement. However, skipping recommended workflows (like architecture for Level 3) may cause:
+
+- Integration issues during implementation
+- Rework due to poor planning
+- Conflicting design decisions
+- Longer development time overall
+
+### Q: How do I know when Phase 3 is complete and I can start Phase 4?
+
+**A:** For Level 3-4, run the solutioning-gate-check workflow. It validates that PRD, architecture, and UX (if applicable) are cohesive before implementation. Pass the gate check = ready for Phase 4.
+
+### Q: Can I run workflows in parallel or do they have to be sequential?
+
+**A:** Most workflows must be sequential within a phase:
+
+- Phase 1: brainstorm → research → product-brief (optional order)
+- Phase 2: PRD must complete before moving forward
+- Phase 3: architecture → validate → gate-check (sequential)
+- Phase 4: Stories within an epic should generally be sequential, but stories in different epics can be parallel if you have capacity
+
+---
+
+## Planning Documents
+
+### Q: What's the difference between tech-spec and epic-tech-context?
+
+**A:**
+
+- **Tech-spec (Level 0-1):** Created upfront in Planning Phase, serves as primary/only planning document, a combination of enough technical and planning information to drive a single or multiple files
+- **Epic-tech-context (Level 2-4):** Created during Implementation Phase per epic, supplements PRD + Architecture
+
+Think of it as: tech-spec is for small projects (replaces PRD and architecture), epic-tech-context is for large projects (supplements PRD).
+
+### Q: Why no tech-spec at Level 2+?
+
+**A:** Level 2+ projects need product-level planning (PRD) and system-level design (Architecture), which tech-spec doesn't provide. Tech-spec is too narrow for coordinating multiple features. Instead, Level 2-4 uses:
+
+- PRD (product vision, requirements, epics)
+- Architecture (system design)
+- Epic-tech-context (detailed implementation per epic, created just-in-time)
+
+### Q: When do I create epic-tech-context?
+
+**A:** In Phase 4, right before implementing each epic. Don't create all epic-tech-context upfront - that's over-planning. Create them just-in-time using the epic-tech-context workflow as you're about to start working on that epic.
+
+**Why just-in-time?** You'll learn from earlier epics, and those learnings improve later epic-tech-context.
+
+### Q: Do I need a PRD for a bug fix?
+
+**A:** No! Bug fixes are typically Level 0 (single atomic change). Use Quick Spec Flow:
+
+- Load PM agent
+- Run tech-spec workflow
+- Implement immediately
+
+PRDs are for Level 2-4 projects with multiple features requiring product-level coordination.
+
+### Q: Can I skip the product brief?
+
+**A:** Yes, product brief is always optional. It's most valuable for:
+
+- Level 3-4 projects needing strategic direction
+- Projects with stakeholders requiring alignment
+- Novel products needing market research
+- When you want to explore solution space before committing
+
+---
+
+## Implementation
+
+### Q: Do I need story-context for every story?
+
+**A:** Technically no, but it's recommended. story-context provides implementation-specific guidance, references existing patterns, and injects expertise. Skip it only if:
+
+- Very simple story (self-explanatory)
+- You're already expert in the area
+- Time is extremely limited
+
+For Level 0-1 using tech-spec, story-context is less critical because tech-spec is already comprehensive.
+
+### Q: What if I don't create epic-tech-context before drafting stories?
+
+**A:** You can proceed without it, but you'll miss:
+
+- Epic-level technical direction
+- Architecture guidance for this epic
+- Integration strategy with other epics
+- Common patterns to follow across stories
+
+epic-tech-context helps ensure stories within an epic are cohesive.
+
+### Q: How do I mark a story as done?
+
+**A:** You have two options:
+
+**Option 1: Use story-done workflow (Recommended)**
+
+1. Load SM agent
+2. Run `story-done` workflow
+3. Workflow automatically updates `sprint-status.yaml` (created by sprint-planning at Phase 4 start)
+4. Moves story from current status → `DONE`
+5. Advances the story queue
+
+**Option 2: Manual update**
+
+1. After dev-story completes and code-review passes
+2. Open `sprint-status.yaml` (created by sprint-planning)
+3. Change the story status from `review` to `done`
+4. Save the file
+
+The story-done workflow is faster and ensures proper status file updates.
+
+### Q: Can I work on multiple stories at once?
+
+**A:** Yes, if you have capacity! Stories within different epics can be worked in parallel. However, stories within the same epic are usually sequential because they build on each other.
+
+### Q: What if my story takes longer than estimated?
+
+**A:** That's normal! Stories are estimates. If implementation reveals more complexity:
+
+1. Continue working until DoD is met
+2. Consider if story should be split
+3. Document learnings in retrospective
+4. Adjust future estimates based on this learning
+
+### Q: When should I run retrospective?
+
+**A:** After completing all stories in an epic (when epic is done). Retrospectives capture:
+
+- What went well
+- What could improve
+- Technical insights
+- Input for next epic-tech-context
+
+Don't wait until project end - run after each epic for continuous improvement.
+
+---
+
+## Brownfield Development
+
+### Q: What is brownfield vs greenfield?
+
+**A:**
+
+- **Greenfield:** New project, starting from scratch, clean slate
+- **Brownfield:** Existing project, working with established codebase and patterns
+
+### Q: Do I have to run document-project for brownfield?
+
+**A:** Highly recommended, especially if:
+
+- No existing documentation
+- Documentation is outdated
+- AI agents need context about existing code
+- Level 2-4 complexity
+
+You can skip it if you have comprehensive, up-to-date documentation including `docs/index.md`.
+
+### Q: What if I forget to run document-project on brownfield?
+
+**A:** Workflows will lack context about existing code. You may get:
+
+- Suggestions that don't match existing patterns
+- Integration approaches that miss existing APIs
+- Architecture that conflicts with current structure
+
+Run document-project and restart planning with proper context.
+
+### Q: Can I use Quick Spec Flow for brownfield projects?
+
+**A:** Yes! Quick Spec Flow works great for brownfield. It will:
+
+- Auto-detect your existing stack
+- Analyze brownfield code patterns
+- Detect conventions and ask for confirmation
+- Generate context-rich tech-spec that respects existing code
+
+Perfect for bug fixes and small features in existing codebases.
+
+### Q: How does workflow-init handle brownfield with old planning docs?
+
+**A:** workflow-init asks about YOUR current work first, then uses old artifacts as context:
+
+1. Shows what it found (old PRD, epics, etc.)
+2. Asks: "Is this work in progress, previous effort, or proposed work?"
+3. If previous effort: Asks you to describe your NEW work
+4. Determines level based on YOUR work, not old artifacts
+
+This prevents old Level 3 PRDs from forcing Level 3 workflow for new Level 0 bug fix.
+
+### Q: What if my existing code doesn't follow best practices?
+
+**A:** Quick Spec Flow detects your conventions and asks: "Should I follow these existing conventions?" You decide:
+
+- **Yes** → Maintain consistency with current codebase
+- **No** → Establish new standards (document why in tech-spec)
+
+BMM respects your choice - it won't force modernization, but it will offer it.
+
+---
+
+## Tools and Technical
+
+### Q: Why are my Mermaid diagrams not rendering?
+
+**A:** Common issues:
+
+1. Missing language tag: Use ` ```mermaid` not just ` ``` `
+2. Syntax errors in diagram (validate at mermaid.live)
+3. Tool doesn't support Mermaid (check your Markdown renderer)
+
+All BMM docs use valid Mermaid syntax that should render in GitHub, VS Code, and most IDEs.
+
+### Q: Can I use BMM with GitHub Copilot / Cursor / other AI tools?
+
+**A:** Yes! BMM is complementary. BMM handles:
+
+- Project planning and structure
+- Workflow orchestration
+- Agent Personas and expertise
+- Documentation generation
+- Quality gates
+
+Your AI coding assistant handles:
+
+- Line-by-line code completion
+- Quick refactoring
+- Test generation
+
+Use them together for best results.
+
+### Q: What IDEs/tools support BMM?
+
+**A:** BMM requires tools with **agent mode** and access to **high-quality LLM models** that can load and follow complex workflows, then properly implement code changes.
+
+**Recommended Tools:**
+
+- **Claude Code** ⭐ **Best choice**
+  - Sonnet 4.5 (excellent workflow following, coding, reasoning)
+  - Opus (maximum context, complex planning)
+  - Native agent mode designed for BMM workflows
+
+- **Cursor**
+  - Supports Anthropic (Claude) and OpenAI models
+  - Agent mode with composer
+  - Good for developers who prefer Cursor's UX
+
+- **Windsurf**
+  - Multi-model support
+  - Agent capabilities
+  - Suitable for BMM workflows
+
+**What Matters:**
+
+1. **Agent mode** - Can load long workflow instructions and maintain context
+2. **High-quality LLM** - Models ranked high on SWE-bench (coding benchmarks)
+3. **Model selection** - Access to Claude Sonnet 4.5, Opus, or GPT-4o class models
+4. **Context capacity** - Can handle large planning documents and codebases
+
+**Why model quality matters:** BMM workflows require LLMs that can follow multi-step processes, maintain context across phases, and implement code that adheres to specifications. Tools with weaker models will struggle with workflow adherence and code quality.
+
+See [IDE Setup Guides](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) for configuration specifics.
+
+### Q: Can I customize agents?
+
+**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `.bmad/_cfg/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
+
+**Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags - a format any LLM can read and follow.
+
+### Q: What happens to my planning docs after implementation?
+
+**A:** Keep them! They serve as:
+
+- Historical record of decisions
+- Onboarding material for new team members
+- Reference for future enhancements
+- Audit trail for compliance
+
+For enterprise projects (Level 4), consider archiving completed planning artifacts to keep workspace clean.
+
+### Q: Can I use BMM for non-software projects?
+
+**A:** BMM is optimized for software development, but the methodology principles (scale-adaptive planning, just-in-time design, context injection) can apply to other complex project types. You'd need to adapt workflows and agents for your domain.
+
+---
+
+## Advanced Questions
+
+### Q: What if my project grows from Level 1 to Level 3?
+
+**A:** Totally fine! When you realize scope has grown:
+
+1. Run create-prd to add product-level planning
+2. Run create-architecture for system design
+3. Use existing tech-spec as input for PRD
+4. Continue with updated level
+
+The system is flexible - growth is expected.
+
+### Q: Can I mix greenfield and brownfield approaches?
+
+**A:** Yes! Common scenario: adding new greenfield feature to brownfield codebase. Approach:
+
+1. Run document-project for brownfield context
+2. Use greenfield workflows for new feature planning
+3. Explicitly document integration points between new and existing
+4. Test integration thoroughly
+
+### Q: How do I handle urgent hotfixes during a sprint?
+
+**A:** Use correct-course workflow or just:
+
+1. Save your current work state
+2. Load PM agent → quick tech-spec for hotfix
+3. Implement hotfix (Level 0 flow)
+4. Deploy hotfix
+5. Return to original sprint work
+
+Level 0 Quick Spec Flow is perfect for urgent fixes.
+
+### Q: What if I disagree with the workflow's recommendations?
+
+**A:** Workflows are guidance, not enforcement. If a workflow recommends something that doesn't make sense for your context:
+
+- Explain your reasoning to the agent
+- Ask for alternative approaches
+- Skip the recommendation if you're confident
+- Document why you deviated (for future reference)
+
+Trust your expertise - BMM supports your decisions.
+
+### Q: Can multiple developers work on the same BMM project?
+
+**A:** Yes! But the paradigm is fundamentally different from traditional agile teams.
+
+**Key Difference:**
+
+- **Traditional:** Multiple devs work on stories within one epic (months)
+- **Agentic:** Each dev owns complete epics (days)
+
+**In traditional agile:** A team of 5 devs might spend 2-3 months on a single epic, with each dev owning different stories.
+
+**With BMM + AI agents:** A single dev can complete an entire epic in 1-3 days. What used to take months now takes days.
+
+**Team Work Distribution:**
+
+- **Recommended:** Split work by **epic** (not story)
+- Each developer owns complete epics end-to-end
+- Parallel work happens at epic level
+- Minimal coordination needed
+
+**For full-stack apps:**
+
+- Frontend and backend can be separate epics (unusual in traditional agile)
+- Frontend dev owns all frontend epics
+- Backend dev owns all backend epics
+- Works because delivery is so fast
+
+**Enterprise Considerations:**
+
+- Use **git submodules** for BMM installation (not .gitignore)
+- Allows personal configurations without polluting main repo
+- Teams may use different AI tools (Claude Code, Cursor, etc.)
+- Developers may follow different methods or create custom agents/workflows
+
+**Quick Tips:**
+
+- Share `sprint-status.yaml` (single source of truth)
+- Assign entire epics to developers (not individual stories)
+- Coordinate at epic boundaries, not story level
+- Use git submodules for BMM in enterprise settings
+
+**For comprehensive coverage of enterprise team collaboration, work distribution strategies, git submodule setup, and velocity expectations, see:**
+
+👉 **[Enterprise Agentic Development Guide](./enterprise-agentic-development.md)**
+
+### Q: What is party mode and when should I use it?
+
+**A:** Party mode is a unique multi-agent collaboration feature where ALL your installed agents (19+ from BMM, CIS, BMB, custom modules) discuss your challenges together in real-time.
+
+**How it works:**
+
+1. Run `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent)
+2. Introduce your topic
+3. BMad Master selects 2-3 most relevant agents per message
+4. Agents cross-talk, debate, and build on each other's ideas
+
+**Best for:**
+
+- Strategic decisions with trade-offs (architecture choices, tech stack, scope)
+- Creative brainstorming (game design, product innovation, UX ideation)
+- Cross-functional alignment (epic kickoffs, retrospectives, phase transitions)
+- Complex problem-solving (multi-faceted challenges, risk assessment)
+
+**Example parties:**
+
+- **Product Strategy:** PM + Innovation Strategist (CIS) + Analyst
+- **Technical Design:** Architect + Creative Problem Solver (CIS) + Game Architect
+- **User Experience:** UX Designer + Design Thinking Coach (CIS) + Storyteller (CIS)
+
+**Why it's powerful:**
+
+- Diverse perspectives (technical, creative, strategic)
+- Healthy debate reveals blind spots
+- Emergent insights from agent interaction
+- Natural collaboration across modules
+
+**For complete documentation:**
+
+👉 **[Party Mode Guide](./party-mode.md)** - How it works, when to use it, example compositions, best practices
+
+---
+
+## Getting Help
+
+### Q: Where do I get help if my question isn't answered here?
+
+**A:**
+
+1. Search [Complete Documentation](./README.md) for related topics
+2. Ask in [Discord Community](https://discord.gg/gk8jAdXWmj) (#general-dev)
+3. Open a [GitHub Issue](https://github.com/bmad-code-org/BMAD-METHOD/issues)
+4. Watch [YouTube Tutorials](https://www.youtube.com/@BMadCode)
+
+### Q: How do I report a bug or request a feature?
+
+**A:** Open a GitHub issue at: https://github.com/bmad-code-org/BMAD-METHOD/issues
+
+Please include:
+
+- BMM version (check your installed version)
+- Steps to reproduce (for bugs)
+- Expected vs actual behavior
+- Relevant workflow or agent involved
+
+---
+
+## Related Documentation
+
+- [Quick Start Guide](./quick-start.md) - Get started with BMM
+- [Glossary](./glossary.md) - Terminology reference
+- [Scale Adaptive System](./scale-adaptive-system.md) - Understanding levels
+- [Brownfield Guide](./brownfield-guide.md) - Existing codebase workflows
+
+---
+
+**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

.bmad/bmm/docs/glossary.md

@@ -0,0 +1,320 @@
+# BMM Glossary
+
+Comprehensive terminology reference for the BMad Method Module.
+
+---
+
+## Navigation
+
+- [Core Concepts](#core-concepts)
+- [Scale and Complexity](#scale-and-complexity)
+- [Planning Documents](#planning-documents)
+- [Workflow and Phases](#workflow-and-phases)
+- [Agents and Roles](#agents-and-roles)
+- [Status and Tracking](#status-and-tracking)
+- [Project Types](#project-types)
+- [Implementation Terms](#implementation-terms)
+
+---
+
+## Core Concepts
+
+### BMM (BMad Method Module)
+
+Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
+
+### BMad Method
+
+The complete methodology for AI-assisted software development, encompassing planning, architecture, implementation, and quality assurance workflows that adapt to project complexity.
+
+### Scale-Adaptive System
+
+BMad Method's intelligent workflow orchestration that automatically adjusts planning depth, documentation requirements, and implementation processes based on project needs through three distinct planning tracks (Quick Flow, BMad Method, Enterprise Method).
+
+### Agent
+
+A specialized AI persona with specific expertise (PM, Architect, SM, DEV, TEA) that guides users through workflows and creates deliverables. Agents have defined capabilities, communication styles, and workflow access.
+
+### Workflow
+
+A multi-step guided process that orchestrates AI agent activities to produce specific deliverables. Workflows are interactive and adapt to user context.
+
+---
+
+## Scale and Complexity
+
+### Quick Flow Track
+
+Fast implementation track using tech-spec planning only. Best for bug fixes, small features, and changes with clear scope. Typical range: 1-15 stories. No architecture phase needed. Examples: bug fixes, OAuth login, search features.
+
+### BMad Method Track
+
+Full product planning track using PRD + Architecture + UX. Best for products, platforms, and complex features requiring system design. Typical range: 10-50+ stories. Examples: admin dashboards, e-commerce platforms, SaaS products.
+
+### Enterprise Method Track
+
+Extended enterprise planning track adding Security Architecture, DevOps Strategy, and Test Strategy to BMad Method. Best for enterprise requirements, compliance needs, and multi-tenant systems. Typical range: 30+ stories. Examples: multi-tenant platforms, compliance-driven systems, mission-critical applications.
+
+### Planning Track
+
+The methodology path (Quick Flow, BMad Method, or Enterprise Method) chosen for a project based on planning needs, complexity, and requirements rather than story count alone.
+
+**Note:** Story counts are guidance, not definitions. Tracks are determined by what planning the project needs, not story math.
+
+---
+
+## Planning Documents
+
+### Tech-Spec (Technical Specification)
+
+**Quick Flow track only.** Comprehensive technical plan created upfront that serves as the primary planning document for small changes or features. Contains problem statement, solution approach, file-level changes, stack detection (brownfield), testing strategy, and developer resources.
+
+### Epic-Tech-Context (Epic Technical Context)
+
+**BMad Method/Enterprise tracks only.** Detailed technical planning document created during implementation (just-in-time) for each epic. Supplements PRD + Architecture with epic-specific implementation details, code-level design decisions, and integration points.
+
+**Key Difference:** Tech-spec (Quick Flow) is created upfront and is the only planning doc. Epic-tech-context (BMad Method/Enterprise) is created per epic during implementation and supplements PRD + Architecture.
+
+### PRD (Product Requirements Document)
+
+**BMad Method/Enterprise tracks.** Product-level planning document containing vision, goals, feature requirements, epic breakdown, success criteria, and UX considerations. Replaces tech-spec for larger projects that need product planning.
+
+### Architecture Document
+
+**BMad Method/Enterprise tracks.** System-wide design document defining structure, components, interactions, data models, integration patterns, security, performance, and deployment.
+
+**Scale-Adaptive:** Architecture complexity scales with track - BMad Method is lightweight to moderate, Enterprise Method is comprehensive with security/devops/test strategies.
+
+### Epics
+
+High-level feature groupings that contain multiple related stories. Typically span 5-15 stories each and represent cohesive functionality (e.g., "User Authentication Epic").
+
+### Product Brief
+
+Optional strategic planning document created in Phase 1 (Analysis) that captures product vision, market context, user needs, and high-level requirements before detailed planning.
+
+### GDD (Game Design Document)
+
+Game development equivalent of PRD, created by Game Designer agent for game projects.
+
+---
+
+## Workflow and Phases
+
+### Phase 0: Documentation (Prerequisite)
+
+**Conditional phase for brownfield projects.** Creates comprehensive codebase documentation before planning. Only required if existing documentation is insufficient for AI agents.
+
+### Phase 1: Analysis (Optional)
+
+Discovery and research phase including brainstorming, research workflows, and product brief creation. Optional for Quick Flow, recommended for BMad Method, required for Enterprise Method.
+
+### Phase 2: Planning (Required)
+
+**Always required.** Creates formal requirements and work breakdown. Routes to tech-spec (Quick Flow) or PRD (BMad Method/Enterprise) based on selected track.
+
+### Phase 3: Solutioning (Track-Dependent)
+
+Architecture design phase. Required for BMad Method and Enterprise Method tracks. Includes architecture creation, validation, and gate checks.
+
+### Phase 4: Implementation (Required)
+
+Sprint-based development through story-by-story iteration. Uses sprint-planning, epic-tech-context, create-story, story-context, dev-story, code-review, and retrospective workflows.
+
+### Quick Spec Flow
+
+Fast-track workflow system for Quick Flow track projects that goes straight from idea to tech-spec to implementation, bypassing heavy planning. Designed for bug fixes, small features, and rapid prototyping.
+
+### Just-In-Time Design
+
+Pattern where epic-tech-context is created during implementation (Phase 4) right before working on each epic, rather than all upfront. Enables learning and adaptation.
+
+### Context Injection
+
+Dynamic technical guidance generated for each story via epic-tech-context and story-context workflows, providing exact expertise when needed without upfront over-planning.
+
+---
+
+## Agents and Roles
+
+### PM (Product Manager)
+
+Agent responsible for creating PRDs, tech-specs, and managing product requirements. Primary agent for Phase 2 planning.
+
+### Analyst (Business Analyst)
+
+Agent that initializes workflows, conducts research, creates product briefs, and tracks progress. Often the entry point for new projects.
+
+### Architect
+
+Agent that designs system architecture, creates architecture documents, performs technical reviews, and validates designs. Primary agent for Phase 3 solutioning.
+
+### SM (Scrum Master)
+
+Agent that manages sprints, creates stories, generates contexts, and coordinates implementation. Primary orchestrator for Phase 4 implementation.
+
+### DEV (Developer)
+
+Agent that implements stories, writes code, runs tests, and performs code reviews. Primary implementer in Phase 4.
+
+### TEA (Test Architect)
+
+Agent responsible for test strategy, quality gates, NFR assessment, and comprehensive quality assurance. Integrates throughout all phases.
+
+### Technical Writer
+
+Agent specialized in creating and maintaining high-quality technical documentation. Expert in documentation standards, information architecture, and professional technical writing. The agent's internal name is "paige" but is presented as "Technical Writer" to users.
+
+### UX Designer
+
+Agent that creates UX design documents, interaction patterns, and visual specifications for UI-heavy projects.
+
+### Game Designer
+
+Specialized agent for game development projects. Creates game design documents (GDD) and game-specific workflows.
+
+### BMad Master
+
+Meta-level orchestrator agent from BMad Core. Facilitates party mode, lists available tasks and workflows, and provides high-level guidance across all modules.
+
+### Party Mode
+
+Multi-agent collaboration feature where all installed agents (19+ from BMM, CIS, BMB, custom modules) discuss challenges together in real-time. BMad Master orchestrates, selecting 2-3 relevant agents per message for natural cross-talk and debate. Best for strategic decisions, creative brainstorming, cross-functional alignment, and complex problem-solving. See [Party Mode Guide](./party-mode.md).
+
+---
+
+## Status and Tracking
+
+### bmm-workflow-status.yaml
+
+**Phases 1-3.** Tracking file that shows current phase, completed workflows, progress, and next recommended actions. Created by workflow-init, updated automatically.
+
+### sprint-status.yaml
+
+**Phase 4 only.** Single source of truth for implementation tracking. Contains all epics, stories, and retrospectives with current status for each. Created by sprint-planning, updated by agents.
+
+### Story Status Progression
+
+```
+backlog → drafted → ready-for-dev → in-progress → review → done
+```
+
+- **backlog** - Story exists in epic but not yet drafted
+- **drafted** - Story file created by SM via create-story
+- **ready-for-dev** - Story has context, ready for DEV via story-context
+- **in-progress** - DEV is implementing via dev-story
+- **review** - Implementation complete, awaiting code-review
+- **done** - Completed with DoD met
+
+### Epic Status Progression
+
+```
+backlog → contexted
+```
+
+- **backlog** - Epic exists in planning docs but no context yet
+- **contexted** - Epic has technical context via epic-tech-context
+
+### Retrospective
+
+Workflow run after completing each epic to capture learnings, identify improvements, and feed insights into next epic planning. Critical for continuous improvement.
+
+---
+
+## Project Types
+
+### Greenfield
+
+New project starting from scratch with no existing codebase. Freedom to establish patterns, choose stack, and design from clean slate.
+
+### Brownfield
+
+Existing project with established codebase, patterns, and constraints. Requires understanding existing architecture, respecting established conventions, and planning integration with current systems.
+
+**Critical:** Brownfield projects should run document-project workflow BEFORE planning to ensure AI agents have adequate context about existing code.
+
+### document-project Workflow
+
+**Brownfield prerequisite.** Analyzes and documents existing codebase, creating comprehensive documentation including project overview, architecture analysis, source tree, API contracts, and data models. Three scan levels: quick, deep, exhaustive.
+
+---
+
+## Implementation Terms
+
+### Story
+
+Single unit of implementable work with clear acceptance criteria, typically 2-8 hours of development effort. Stories are grouped into epics and tracked in sprint-status.yaml.
+
+### Story File
+
+Markdown file containing story details: description, acceptance criteria, technical notes, dependencies, implementation guidance, and testing requirements.
+
+### Story Context
+
+Technical guidance document created via story-context workflow that provides implementation-specific context, references existing patterns, suggests approaches, and injects expertise for the specific story.
+
+### Epic Context
+
+Technical planning document created via epic-tech-context workflow before drafting stories within an epic. Provides epic-level technical direction, architecture notes, and implementation strategy.
+
+### Sprint Planning
+
+Workflow that initializes Phase 4 implementation by creating sprint-status.yaml, extracting all epics/stories from planning docs, and setting up tracking infrastructure.
+
+### Gate Check
+
+Validation workflow (solutioning-gate-check) run before Phase 4 to ensure PRD, architecture, and UX documents are cohesive with no gaps or contradictions. Required for BMad Method and Enterprise Method tracks.
+
+### DoD (Definition of Done)
+
+Criteria that must be met before marking a story as done. Typically includes: implementation complete, tests written and passing, code reviewed, documentation updated, and acceptance criteria validated.
+
+### Shard / Sharding
+
+**For runtime LLM optimization only (NOT human docs).** Splitting large planning documents (PRD, epics, architecture) into smaller section-based files to improve workflow efficiency. Phase 1-3 workflows load entire sharded documents transparently. Phase 4 workflows selectively load only needed sections for massive token savings.
+
+---
+
+## Additional Terms
+
+### Workflow Status
+
+Universal entry point workflow that checks for existing status file, displays current phase/progress, and recommends next action based on project state.
+
+### Workflow Init
+
+Initialization workflow that creates bmm-workflow-status.yaml, detects greenfield vs brownfield, determines planning track, and sets up appropriate workflow path.
+
+### Track Selection
+
+Automatic analysis by workflow-init that uses keyword analysis, complexity indicators, and project requirements to suggest appropriate track (Quick Flow, BMad Method, or Enterprise Method). User can override suggested track.
+
+### Correct Course
+
+Workflow run during Phase 4 when significant changes or issues arise. Analyzes impact, proposes solutions, and routes to appropriate remediation workflows.
+
+### Migration Strategy
+
+Plan for handling changes to existing data, schemas, APIs, or patterns during brownfield development. Critical for ensuring backward compatibility and smooth rollout.
+
+### Feature Flags
+
+Implementation technique for brownfield projects that allows gradual rollout of new functionality, easy rollback, and A/B testing. Recommended for BMad Method and Enterprise brownfield changes.
+
+### Integration Points
+
+Specific locations where new code connects with existing systems. Must be documented explicitly in brownfield tech-specs and architectures.
+
+### Convention Detection
+
+Quick Spec Flow feature that automatically detects existing code style, naming conventions, patterns, and frameworks from brownfield codebases, then asks user to confirm before proceeding.
+
+---
+
+## Related Documentation
+
+- [Quick Start Guide](./quick-start.md) - Learn BMM basics
+- [Scale Adaptive System](./scale-adaptive-system.md) - Deep dive on tracks and complexity
+- [Brownfield Guide](./brownfield-guide.md) - Working with existing codebases
+- [Quick Spec Flow](./quick-spec-flow.md) - Fast-track for Quick Flow track
+- [FAQ](./faq.md) - Common questions

.bmad/bmm/docs/party-mode.md

@@ -0,0 +1,224 @@
+# Party Mode: Multi-Agent Collaboration
+
+**Get all your AI agents in one conversation**
+
+---
+
+## What is Party Mode?
+
+Ever wanted to gather your entire AI team in one room and see what happens? That's party mode.
+
+Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent), and suddenly you've got **all your AI agents** in one conversation. PM, Architect, DEV, UX Designer, the CIS creative agents - everyone shows up.
+
+**Why it's useful:**
+
+- **After complex workflows** - Debrief with the whole team about what worked, what didn't
+- **Big decisions with tradeoffs** - Get technical, creative, and strategic perspectives simultaneously
+- **Brainstorming sessions** - Watch ideas evolve through cross-pollination
+- **When things go wrong** - Call out failures, watch agents defend their decisions, let them debate whose fault it was (oddly therapeutic)
+- **Sprint retrospectives** - Party mode powers the retrospective workflow
+- **Sprint planning** - Multi-agent collaboration for planning sessions
+
+**Future use:** Advanced elicitation workflows will leverage party mode for sophisticated requirement gathering.
+
+---
+
+## How It Works
+
+**The basics:**
+
+1. Party mode reads `.bmad/_cfg/agent-manifest.csv`
+2. Loads ALL installed agents (already includes your customizations from install)
+3. BMad Master orchestrates - picks 2-3 relevant agents per message based on topic
+4. Agents respond in character, can agree/disagree/build on each other's ideas
+5. Discussion continues until you type "exit" or reach natural conclusion
+
+**That's it.** No complex merging, no runtime magic. Just agents talking.
+
+---
+
+## Quick Start
+
+```bash
+# Trigger party mode
+/bmad:core:workflows:party-mode
+
+# OR from any agent context
+*party-mode
+
+# During party
+Ask questions, respond to agents, direct the conversation
+
+# Exit
+Type: exit
+```
+
+---
+
+## Fun Examples
+
+### Example 1: Calling Out Bad Architecture
+
+**You:** "Okay team, our last sprint was a disaster. The authentication service went down three times. Who screwed this up?"
+
+**Architect (Winston):** "The design was sound - distributed authentication with proper fallbacks. If implementation deviated from the spec..."
+
+**DEV (Amelia):** "I followed the architecture doc exactly. The spec didn't account for concurrent session invalidation race conditions."
+
+**PM (John):** "Both of you missed the bigger issue - we didn't validate session management requirements in the PRD. This is on me for not catching it."
+
+**TEA (Murat):** "And I should've caught this in integration tests. The test scenarios didn't cover concurrent invalidation."
+
+_(Watch them debate whose fault it really was - it's therapeutic)_
+
+---
+
+### Example 2: Creative Brainstorming
+
+**You:** "How do we make onboarding feel magical instead of boring?"
+
+**UX Designer (Sally):** "Start with progressive disclosure - reveal features as users need them, not all at once in a tutorial."
+
+**Storyteller (CIS):** "What if onboarding was a story? Each step reveals a character's journey - the user IS the hero."
+
+**Innovation Strategist (CIS):** "Take it further - gamify with unlockable achievements. But make them meaningful, not arbitrary badges."
+
+**Game Designer:** "Building on that - what if the first 'quest' is actually solving a real user problem? They learn by doing something valuable."
+
+_(Ideas cross-pollinate and evolve)_
+
+---
+
+### Example 3: Technical Decision
+
+**You:** "Monolith or microservices for MVP?"
+
+**Architect:** "Start monolith. Microservices add complexity you don't need at 1000 users."
+
+**PM:** "Agree. Time to market matters more than theoretical scalability."
+
+**DEV:** "Monolith with clear module boundaries. We can extract services later if needed."
+
+**Innovation Strategist:** "Contrarian take - if your differentiator IS scalability, build for it now. Otherwise Architect's right."
+
+_(Multiple perspectives reveal the right answer)_
+
+---
+
+## When NOT to Use Party Mode
+
+**Skip party mode for:**
+
+- Simple implementation questions → Use DEV agent
+- Document review → Use Technical Writer
+- Workflow status checks → Use any agent + `*workflow-status`
+- Single-domain questions → Use specialist agent
+
+**Use party mode for:**
+
+- Multi-perspective decisions
+- Creative collaboration
+- Post-mortems and retrospectives
+- Sprint planning sessions
+- Complex problem-solving
+
+---
+
+## Agent Customization
+
+Party mode uses agents from `.bmad/[module]/agents/*.md` - these already include any customizations you applied during install.
+
+**To customize agents for party mode:**
+
+1. Create customization file: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
+2. Run `npx bmad-method install` to rebuild agents
+3. Customizations now active in party mode
+
+Example customization:
+
+```yaml
+agent:
+  persona:
+    principles:
+      - 'HIPAA compliance is non-negotiable'
+      - 'Patient safety over feature velocity'
+```
+
+See [Agents Guide](./agents-guide.md#agent-customization) for details.
+
+---
+
+## BMM Workflows That Use Party Mode
+
+**Current:**
+
+- `epic-retrospective` - Post-epic team retrospective powered by party mode
+- Sprint planning discussions (informal party mode usage)
+
+**Future:**
+
+- Advanced elicitation workflows will officially integrate party mode
+- Multi-agent requirement validation
+- Collaborative technical reviews
+
+---
+
+## Available Agents
+
+Party mode can include **19+ agents** from all installed modules:
+
+**BMM (12 agents):** PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Technical Writer, Game Designer, Game Developer, Game Architect
+
+**CIS (5 agents):** Brainstorming Coach, Creative Problem Solver, Design Thinking Coach, Innovation Strategist, Storyteller
+
+**BMB (1 agent):** BMad Builder
+
+**Core (1 agent):** BMad Master (orchestrator)
+
+**Custom:** Any agents you've created
+
+---
+
+## Tips
+
+**Get better results:**
+
+- Be specific with your topic/question
+- Provide context (project type, constraints, goals)
+- Direct specific agents when you want their expertise
+- Make decisions - party mode informs, you decide
+- Time box discussions (15-30 minutes is usually plenty)
+
+**Examples of good opening questions:**
+
+- "We need to decide between REST and GraphQL for our mobile API. Project is a B2B SaaS with 50 enterprise clients."
+- "Our last sprint failed spectacularly. Let's discuss what went wrong with authentication implementation."
+- "Brainstorm: how can we make our game's tutorial feel rewarding instead of tedious?"
+
+---
+
+## Troubleshooting
+
+**Same agents responding every time?**
+Vary your questions or explicitly request other perspectives: "Game Designer, your thoughts?"
+
+**Discussion going in circles?**
+BMad Master will summarize and redirect, or you can make a decision and move on.
+
+**Too many agents talking?**
+Make your topic more specific - BMad Master picks 2-3 agents based on relevance.
+
+**Agents not using customizations?**
+Make sure you ran `npx bmad-method install` after creating customization files.
+
+---
+
+## Related Documentation
+
+- [Agents Guide](./agents-guide.md) - Complete agent reference
+- [Quick Start Guide](./quick-start.md) - Getting started with BMM
+- [FAQ](./faq.md) - Common questions
+
+---
+
+_Better decisions through diverse perspectives. Welcome to party mode._

.bmad/bmm/docs/quick-spec-flow.md

@@ -0,0 +1,652 @@
+# BMad Quick Spec Flow
+
+**Perfect for:** Bug fixes, small features, rapid prototyping, and quick enhancements
+
+**Time to implementation:** Minutes, not hours
+
+---
+
+## What is Quick Spec Flow?
+
+Quick Spec Flow is a **streamlined alternative** to the full BMad Method for Quick Flow track projects. Instead of going through Product Brief → PRD → Architecture, you go **straight to a context-aware technical specification** and start coding.
+
+### When to Use Quick Spec Flow
+
+✅ **Use Quick Flow track when:**
+
+- Single bug fix or small enhancement
+- Small feature with clear scope (typically 1-15 stories)
+- Rapid prototyping or experimentation
+- Adding to existing brownfield codebase
+- You know exactly what you want to build
+
+❌ **Use BMad Method or Enterprise tracks when:**
+
+- Building new products or major features
+- Need stakeholder alignment
+- Complex multi-team coordination
+- Requires extensive planning and architecture
+
+💡 **Not sure?** Run `workflow-init` to get a recommendation based on your project's needs!
+
+---
+
+## Quick Spec Flow Overview
+
+```mermaid
+flowchart TD
+    START[Step 1: Run Tech-Spec Workflow]
+    DETECT[Detects project stack<br/>package.json, requirements.txt, etc.]
+    ANALYZE[Analyzes brownfield codebase<br/>if exists]
+    TEST[Detects test frameworks<br/>and conventions]
+    CONFIRM[Confirms conventions<br/>with you]
+    GENERATE[Generates context-rich<br/>tech-spec]
+    STORIES[Creates ready-to-implement<br/>stories]
+
+    OPTIONAL[Step 2: Optional<br/>Generate Story Context<br/>SM Agent<br/>For complex scenarios only]
+
+    IMPL[Step 3: Implement<br/>DEV Agent<br/>Code, test, commit]
+
+    DONE[DONE! 🚀]
+
+    START --> DETECT
+    DETECT --> ANALYZE
+    ANALYZE --> TEST
+    TEST --> CONFIRM
+    CONFIRM --> GENERATE
+    GENERATE --> STORIES
+    STORIES --> OPTIONAL
+    OPTIONAL -.->|Optional| IMPL
+    STORIES --> IMPL
+    IMPL --> DONE
+
+    style START fill:#bfb,stroke:#333,stroke-width:2px,color:#000
+    style OPTIONAL fill:#ffb,stroke:#333,stroke-width:2px,stroke-dasharray: 5 5,color:#000
+    style IMPL fill:#bbf,stroke:#333,stroke-width:2px,color:#000
+    style DONE fill:#f9f,stroke:#333,stroke-width:3px,color:#000
+```
+
+---
+
+## Single Atomic Change
+
+**Best for:** Bug fixes, single file changes, isolated improvements
+
+### What You Get
+
+1. **tech-spec.md** - Comprehensive technical specification with:
+   - Problem statement and solution
+   - Detected framework versions and dependencies
+   - Brownfield code patterns (if applicable)
+   - Existing test patterns to follow
+   - Specific file paths to modify
+   - Complete implementation guidance
+
+2. **story-[slug].md** - Single user story ready for development
+
+### Quick Spec Flow Commands
+
+```bash
+# Start Quick Spec Flow (no workflow-init needed!)
+# Load PM agent and run tech-spec
+
+# When complete, implement directly:
+# Load DEV agent and run dev-story
+```
+
+### What Makes It Quick
+
+- ✅ No Product Brief needed
+- ✅ No PRD needed
+- ✅ No Architecture doc needed
+- ✅ Auto-detects your stack
+- ✅ Auto-analyzes brownfield code
+- ✅ Auto-validates quality
+- ✅ Story context optional (tech-spec is comprehensive!)
+
+### Example Single Change Scenarios
+
+- "Fix the login validation bug"
+- "Add email field to user registration form"
+- "Update API endpoint to return additional field"
+- "Improve error handling in payment processing"
+
+---
+
+## Coherent Small Feature
+
+**Best for:** Small features with 2-3 related user stories
+
+### What You Get
+
+1. **tech-spec.md** - Same comprehensive spec as single change projects
+2. **epics.md** - Epic organization with story breakdown
+3. **story-[epic-slug]-1.md** - First story
+4. **story-[epic-slug]-2.md** - Second story
+5. **story-[epic-slug]-3.md** - Third story (if needed)
+
+### Quick Spec Flow Commands
+
+```bash
+# Start Quick Spec Flow
+# Load PM agent and run tech-spec
+
+# Optional: Organize stories as a sprint
+# Load SM agent and run sprint-planning
+
+# Implement story-by-story:
+# Load DEV agent and run dev-story for each story
+```
+
+### Story Sequencing
+
+Stories are **automatically validated** to ensure proper sequence:
+
+- ✅ No forward dependencies (Story 2 can't depend on Story 3)
+- ✅ Clear dependency documentation
+- ✅ Infrastructure → Features → Polish order
+- ✅ Backend → Frontend flow
+
+### Example Small Feature Scenarios
+
+- "Add OAuth social login (Google, GitHub, Twitter)"
+- "Build user profile page with avatar upload"
+- "Implement basic search with filters"
+- "Add dark mode toggle to application"
+
+---
+
+## Smart Context Discovery
+
+Quick Spec Flow automatically discovers and uses:
+
+### 1. Existing Documentation
+
+- Product briefs (if they exist)
+- Research documents
+- `document-project` output (brownfield codebase map)
+
+### 2. Project Stack
+
+- **Node.js:** package.json → frameworks, dependencies, scripts, test framework
+- **Python:** requirements.txt, pyproject.toml → packages, tools
+- **Ruby:** Gemfile → gems and versions
+- **Java:** pom.xml, build.gradle → Maven/Gradle dependencies
+- **Go:** go.mod → modules
+- **Rust:** Cargo.toml → crates
+- **PHP:** composer.json → packages
+
+### 3. Brownfield Code Patterns
+
+- Directory structure and organization
+- Existing code patterns (class-based, functional, MVC)
+- Naming conventions (camelCase, snake_case, PascalCase)
+- Test frameworks and patterns
+- Code style (semicolons, quotes, indentation)
+- Linter/formatter configs
+- Error handling patterns
+- Logging conventions
+- Documentation style
+
+### 4. Convention Confirmation
+
+**IMPORTANT:** Quick Spec Flow detects your conventions and **asks for confirmation**:
+
+```
+I've detected these conventions in your codebase:
+
+Code Style:
+- ESLint with Airbnb config
+- Prettier with single quotes, 2-space indent
+- No semicolons
+
+Test Patterns:
+- Jest test framework
+- .test.js file naming
+- expect() assertion style
+
+Should I follow these existing conventions? (yes/no)
+```
+
+**You decide:** Conform to existing patterns or establish new standards!
+
+---
+
+## Modern Best Practices via WebSearch
+
+Quick Spec Flow stays current by using WebSearch when appropriate:
+
+### For Greenfield Projects
+
+- Searches for latest framework versions
+- Recommends official starter templates
+- Suggests modern best practices
+
+### For Outdated Dependencies
+
+- Detects if your dependencies are >2 years old
+- Searches for migration guides
+- Notes upgrade complexity
+
+### Starter Template Recommendations
+
+For greenfield projects, Quick Spec Flow recommends:
+
+**React:**
+
+- Vite (modern, fast)
+- Next.js (full-stack)
+
+**Python:**
+
+- cookiecutter templates
+- FastAPI starter
+
+**Node.js:**
+
+- NestJS CLI
+- express-generator
+
+**Benefits:**
+
+- ✅ Modern best practices baked in
+- ✅ Proper project structure
+- ✅ Build tooling configured
+- ✅ Testing framework set up
+- ✅ Faster time to first feature
+
+---
+
+## UX/UI Considerations
+
+For user-facing changes, Quick Spec Flow captures:
+
+- UI components affected (create vs modify)
+- UX flow changes (current vs new)
+- Responsive design needs (mobile, tablet, desktop)
+- Accessibility requirements:
+  - Keyboard navigation
+  - Screen reader compatibility
+  - ARIA labels
+  - Color contrast standards
+- User feedback patterns:
+  - Loading states
+  - Error messages
+  - Success confirmations
+  - Progress indicators
+
+---
+
+## Auto-Validation and Quality Assurance
+
+Quick Spec Flow **automatically validates** everything:
+
+### Tech-Spec Validation (Always Runs)
+
+Checks:
+
+- ✅ Context gathering completeness
+- ✅ Definitiveness (no "use X or Y" statements)
+- ✅ Brownfield integration quality
+- ✅ Stack alignment
+- ✅ Implementation readiness
+
+Generates scores:
+
+```
+✅ Validation Passed!
+- Context Gathering: Comprehensive
+- Definitiveness: All definitive
+- Brownfield Integration: Excellent
+- Stack Alignment: Perfect
+- Implementation Readiness: ✅ Ready
+```
+
+### Story Validation (Multi-Story Features)
+
+Checks:
+
+- ✅ Story sequence (no forward dependencies!)
+- ✅ Acceptance criteria quality (specific, testable)
+- ✅ Completeness (all tech spec tasks covered)
+- ✅ Clear dependency documentation
+
+**Auto-fixes issues if found!**
+
+---
+
+## Complete User Journey
+
+### Scenario 1: Bug Fix (Single Change)
+
+**Goal:** Fix login validation bug
+
+**Steps:**
+
+1. **Start:** Load PM agent, say "I want to fix the login validation bug"
+2. **PM runs tech-spec workflow:**
+   - Asks: "What problem are you solving?"
+   - You explain the validation issue
+   - Detects your Node.js stack (Express 4.18.2, Jest for testing)
+   - Analyzes existing UserService code patterns
+   - Asks: "Should I follow your existing conventions?" → You say yes
+   - Generates tech-spec.md with specific file paths and patterns
+   - Creates story-login-fix.md
+3. **Implement:** Load DEV agent, run `dev-story`
+   - DEV reads tech-spec (has all context!)
+   - Implements fix following existing patterns
+   - Runs tests (following existing Jest patterns)
+   - Done!
+
+**Total time:** 15-30 minutes (mostly implementation)
+
+---
+
+### Scenario 2: Small Feature (Multi-Story)
+
+**Goal:** Add OAuth social login (Google, GitHub)
+
+**Steps:**
+
+1. **Start:** Load PM agent, say "I want to add OAuth social login"
+2. **PM runs tech-spec workflow:**
+   - Asks about the feature scope
+   - You specify: Google and GitHub OAuth
+   - Detects your stack (Next.js 13.4, NextAuth.js already installed!)
+   - Analyzes existing auth patterns
+   - Confirms conventions with you
+   - Generates:
+     - tech-spec.md (comprehensive implementation guide)
+     - epics.md (OAuth Integration epic)
+     - story-oauth-1.md (Backend OAuth setup)
+     - story-oauth-2.md (Frontend login buttons)
+3. **Optional Sprint Planning:** Load SM agent, run `sprint-planning`
+4. **Implement Story 1:**
+   - Load DEV agent, run `dev-story` for story 1
+   - DEV implements backend OAuth
+5. **Implement Story 2:**
+   - DEV agent, run `dev-story` for story 2
+   - DEV implements frontend
+   - Done!
+
+**Total time:** 1-3 hours (mostly implementation)
+
+---
+
+## Integration with Phase 4 Workflows
+
+Quick Spec Flow works seamlessly with all Phase 4 implementation workflows:
+
+### story-context (SM Agent)
+
+- ✅ Recognizes tech-spec.md as authoritative source
+- ✅ Extracts context from tech-spec (replaces PRD)
+- ✅ Generates XML context for complex scenarios
+
+### create-story (SM Agent)
+
+- ✅ Can work with tech-spec.md instead of PRD
+- ✅ Uses epics.md from tech-spec workflow
+- ✅ Creates additional stories if needed
+
+### sprint-planning (SM Agent)
+
+- ✅ Works with epics.md from tech-spec
+- ✅ Organizes multi-story features for coordinated implementation
+- ✅ Tracks progress through sprint-status.yaml
+
+### dev-story (DEV Agent)
+
+- ✅ Reads stories generated by tech-spec
+- ✅ Uses tech-spec.md as comprehensive context
+- ✅ Implements following detected conventions
+
+---
+
+## Comparison: Quick Spec vs Full BMM
+
+| Aspect                | Quick Flow Track             | BMad Method/Enterprise Tracks      |
+| --------------------- | ---------------------------- | ---------------------------------- |
+| **Setup**             | None (standalone)            | workflow-init recommended          |
+| **Planning Docs**     | tech-spec.md only            | Product Brief → PRD → Architecture |
+| **Time to Code**      | Minutes                      | Hours to days                      |
+| **Best For**          | Bug fixes, small features    | New products, major features       |
+| **Context Discovery** | Automatic                    | Manual + guided                    |
+| **Story Context**     | Optional (tech-spec is rich) | Required (generated from PRD)      |
+| **Validation**        | Auto-validates everything    | Manual validation steps            |
+| **Brownfield**        | Auto-analyzes and conforms   | Manual documentation required      |
+| **Conventions**       | Auto-detects and confirms    | Document in PRD/Architecture       |
+
+---
+
+## When to Graduate from Quick Flow to BMad Method
+
+Start with Quick Flow, but switch to BMad Method when:
+
+- ❌ Project grows beyond initial scope
+- ❌ Multiple teams need coordination
+- ❌ Stakeholders need formal documentation
+- ❌ Product vision is unclear
+- ❌ Architectural decisions need deep analysis
+- ❌ Compliance/regulatory requirements exist
+
+💡 **Tip:** You can always run `workflow-init` later to transition from Quick Flow to BMad Method!
+
+---
+
+## Quick Spec Flow - Key Benefits
+
+### 🚀 **Speed**
+
+- No Product Brief
+- No PRD
+- No Architecture doc
+- Straight to implementation
+
+### 🧠 **Intelligence**
+
+- Auto-detects stack
+- Auto-analyzes brownfield
+- Auto-validates quality
+- WebSearch for current info
+
+### 📐 **Respect for Existing Code**
+
+- Detects conventions
+- Asks for confirmation
+- Follows patterns
+- Adapts vs. changes
+
+### ✅ **Quality**
+
+- Auto-validation
+- Definitive decisions (no "or" statements)
+- Comprehensive context
+- Clear acceptance criteria
+
+### 🎯 **Focus**
+
+- Single atomic changes
+- Coherent small features
+- No scope creep
+- Fast iteration
+
+---
+
+## Getting Started
+
+### Prerequisites
+
+- BMad Method installed (`npx bmad-method install`)
+- Project directory with code (or empty for greenfield)
+
+### Quick Start Commands
+
+```bash
+# For a quick bug fix or small change:
+# 1. Load PM agent
+# 2. Say: "I want to [describe your change]"
+# 3. PM will ask if you want to run tech-spec
+# 4. Answer questions about your change
+# 5. Get tech-spec + story
+# 6. Load DEV agent and implement!
+
+# For a small feature with multiple stories:
+# Same as above, but get epic + 2-3 stories
+# Optionally use SM sprint-planning to organize
+```
+
+### No workflow-init Required!
+
+Quick Spec Flow is **fully standalone**:
+
+- Detects if it's a single change or multi-story feature
+- Asks for greenfield vs brownfield
+- Works without status file tracking
+- Perfect for rapid prototyping
+
+---
+
+## FAQ
+
+### Q: Can I use Quick Spec Flow on an existing project?
+
+**A:** Yes! It's perfect for brownfield projects. It will analyze your existing code, detect patterns, and ask if you want to follow them.
+
+### Q: What if I don't have a package.json or requirements.txt?
+
+**A:** Quick Spec Flow will work in greenfield mode, recommend starter templates, and use WebSearch for modern best practices.
+
+### Q: Do I need to run workflow-init first?
+
+**A:** No! Quick Spec Flow is standalone. But if you want guidance on which flow to use, workflow-init can help.
+
+### Q: Can I use this for frontend changes?
+
+**A:** Absolutely! Quick Spec Flow captures UX/UI considerations, component changes, and accessibility requirements.
+
+### Q: What if my Quick Flow project grows?
+
+**A:** No problem! You can always transition to BMad Method by running workflow-init and create-prd. Your tech-spec becomes input for the PRD.
+
+### Q: Do I need story-context for every story?
+
+**A:** Usually no! Tech-spec is comprehensive enough for most Quick Flow projects. Only use story-context for complex edge cases.
+
+### Q: Can I skip validation?
+
+**A:** No, validation always runs automatically. But it's fast and catches issues early!
+
+### Q: Will it work with my team's code style?
+
+**A:** Yes! It detects your conventions and asks for confirmation. You control whether to follow existing patterns or establish new ones.
+
+---
+
+## Tips and Best Practices
+
+### 1. **Be Specific in Discovery**
+
+When describing your change, provide specifics:
+
+- ✅ "Fix email validation in UserService to allow plus-addressing"
+- ❌ "Fix validation bug"
+
+### 2. **Trust the Convention Detection**
+
+If it detects your patterns correctly, say yes! It's faster than establishing new conventions.
+
+### 3. **Use WebSearch Recommendations for Greenfield**
+
+Starter templates save hours of setup time. Let Quick Spec Flow find the best ones.
+
+### 4. **Review the Auto-Validation**
+
+When validation runs, read the scores. They tell you if your spec is production-ready.
+
+### 5. **Story Context is Optional**
+
+For single changes, try going directly to dev-story first. Only add story-context if you hit complexity.
+
+### 6. **Keep Single Changes Truly Atomic**
+
+If your "single change" needs 3+ files, it might be a multi-story feature. Let the workflow guide you.
+
+### 7. **Validate Story Sequence for Multi-Story Features**
+
+When you get multiple stories, check the dependency validation output. Proper sequence matters!
+
+---
+
+## Real-World Examples
+
+### Example 1: Adding Logging (Single Change)
+
+**Input:** "Add structured logging to payment processing"
+
+**Tech-Spec Output:**
+
+- Detected: winston 3.8.2 already in package.json
+- Analyzed: Existing services use winston with JSON format
+- Confirmed: Follow existing logging patterns
+- Generated: Specific file paths, log levels, format example
+- Story: Ready to implement in 1-2 hours
+
+**Result:** Consistent logging added, following team patterns, no research needed.
+
+---
+
+### Example 2: Search Feature (Multi-Story)
+
+**Input:** "Add search to product catalog with filters"
+
+**Tech-Spec Output:**
+
+- Detected: React 18.2.0, MUI component library, Express backend
+- Analyzed: Existing ProductList component patterns
+- Confirmed: Follow existing API and component structure
+- Generated:
+  - Epic: Product Search Functionality
+  - Story 1: Backend search API with filters
+  - Story 2: Frontend search UI component
+- Auto-validated: Story 1 → Story 2 sequence correct
+
+**Result:** Search feature implemented in 4-6 hours with proper architecture.
+
+---
+
+## Summary
+
+Quick Spec Flow is your **fast path from idea to implementation** for:
+
+- 🐛 Bug fixes
+- ✨ Small features
+- 🚀 Rapid prototyping
+- 🔧 Quick enhancements
+
+**Key Features:**
+
+- Auto-detects your stack
+- Auto-analyzes brownfield code
+- Auto-validates quality
+- Respects existing conventions
+- Uses WebSearch for modern practices
+- Generates comprehensive tech-specs
+- Creates implementation-ready stories
+
+**Time to code:** Minutes, not hours.
+
+**Ready to try it?** Load the PM agent and say what you want to build! 🚀
+
+---
+
+## Next Steps
+
+- **Try it now:** Load PM agent and describe a small change
+- **Learn more:** See the [BMM Workflow Guides](./README.md#-workflow-guides) for comprehensive workflow documentation
+- **Need help deciding?** Run `workflow-init` to get a recommendation
+- **Have questions?** Join us on Discord: https://discord.gg/gk8jAdXWmj
+
+---
+
+_Quick Spec Flow - Because not every change needs a Product Brief._

.bmad/bmm/docs/quick-start.md

@@ -0,0 +1,366 @@
+# BMad Method V6 Quick Start Guide
+
+Get started with BMad Method v6 for your new greenfield project. This guide walks you through building software from scratch using AI-powered workflows.
+
+## TL;DR - The Quick Path
+
+1. **Install**: `npx bmad-method@alpha install`
+2. **Initialize**: Load Analyst agent → Run "workflow-init"
+3. **Plan**: Load PM agent → Run "prd" (or "tech-spec" for small projects)
+4. **Architect**: Load Architect agent → Run "create-architecture" (10+ stories only)
+5. **Build**: Load SM agent → Run workflows for each story → Load DEV agent → Implement
+6. **Always use fresh chats** for each workflow to avoid hallucinations
+
+---
+
+## What is BMad Method?
+
+BMad Method (BMM) helps you build software through guided workflows with specialized AI agents. The process follows four phases:
+
+1. **Phase 1: Analysis** (Optional) - Brainstorming, Research, Product Brief
+2. **Phase 2: Planning** (Required) - Create your requirements (tech-spec or PRD)
+3. **Phase 3: Solutioning** (Track-dependent) - Design the architecture for BMad Method and Enterprise tracks
+4. **Phase 4: Implementation** (Required) - Build your software Epic by Epic, Story by Story
+
+## Installation
+
+```bash
+# Install v6 Alpha to your project
+npx bmad-method@alpha install
+```
+
+The interactive installer will guide you through setup and create a `.bmad/` folder with all agents and workflows.
+
+---
+
+## Getting Started
+
+### Step 1: Initialize Your Workflow
+
+1. **Load the Analyst agent** in your IDE - See your IDE-specific instructions in [docs/ide-info](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) for how to activate agents:
+   - [Claude Code](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/docs/ide-info/claude-code.md)
+   - [VS Code/Cursor/Windsurf](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) - Check your IDE folder
+   - Other IDEs also supported
+2. **Wait for the agent's menu** to appear
+3. **Tell the agent**: "Run workflow-init" or type "\*workflow-init" or select the menu item number
+
+#### What happens during workflow-init?
+
+Workflows are interactive processes in V6 that replaced tasks and templates from prior versions. There are many types of workflows, and you can even create your own with the BMad Builder module. For the BMad Method, you'll be interacting with expert-designed workflows crafted to work with you to get the best out of both you and the LLM.
+
+During workflow-init, you'll describe:
+
+- Your project and its goals
+- Whether there's an existing codebase or this is a new project
+- The general size and complexity (you can adjust this later)
+
+#### Planning Tracks
+
+Based on your description, the workflow will suggest a track and let you choose from:
+
+**Three Planning Tracks:**
+
+- **Quick Flow** - Fast implementation (tech-spec only) - bug fixes, simple features, clear scope (typically 1-15 stories)
+- **BMad Method** - Full planning (PRD + Architecture + UX) - products, platforms, complex features (typically 10-50+ stories)
+- **Enterprise Method** - Extended planning (BMad Method + Security/DevOps/Test) - enterprise requirements, compliance, multi-tenant (typically 30+ stories)
+
+**Note**: Story counts are guidance, not definitions. Tracks are chosen based on planning needs, not story math.
+
+#### What gets created?
+
+Once you confirm your track, the `bmm-workflow-status.yaml` file will be created in your project's docs folder (assuming default install location). This file tracks your progress through all phases.
+
+**Important notes:**
+
+- Every track has different paths through the phases
+- Story counts can still change based on overall complexity as you work
+- For this guide, we'll assume a BMad Method track project
+- This workflow will guide you through Phase 1 (optional), Phase 2 (required), and Phase 3 (required for BMad Method and Enterprise tracks)
+
+### Step 2: Work Through Phases 1-3
+
+After workflow-init completes, you'll work through the planning phases. **Important: Use fresh chats for each workflow to avoid context limitations.**
+
+#### Checking Your Status
+
+If you're unsure what to do next:
+
+1. Load any agent in a new chat
+2. Ask for "workflow-status"
+3. The agent will tell you the next recommended or required workflow
+
+**Example response:**
+
+```
+Phase 1 (Analysis) is entirely optional. All workflows are optional or recommended:
+  - brainstorm-project - optional
+  - research - optional
+  - product-brief - RECOMMENDED (but not required)
+
+The next TRULY REQUIRED step is:
+  - PRD (Product Requirements Document) in Phase 2 - Planning
+  - Agent: pm
+  - Command: prd
+```
+
+#### How to Run Workflows in Phases 1-3
+
+When an agent tells you to run a workflow (like `prd`):
+
+1. **Start a new chat** with the specified agent (e.g., PM) - See [docs/ide-info](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) for your IDE's specific instructions
+2. **Wait for the menu** to appear
+3. **Tell the agent** to run it using any of these formats:
+   - Type the shorthand: `*prd`
+   - Say it naturally: "Let's create a new PRD"
+   - Select the menu number for "create-prd"
+
+The agents in V6 are very good with fuzzy menu matching!
+
+#### Quick Reference: Agent → Document Mapping
+
+For v4 users or those who prefer to skip workflow-status guidance:
+
+- **Analyst** → Brainstorming, Product Brief
+- **PM** → PRD (BMad Method/Enterprise tracks) OR tech-spec (Quick Flow track)
+- **UX-Designer** → UX Design Document (if UI-heavy)
+- **Architect** → Architecture (BMad Method/Enterprise tracks)
+
+#### Phase 2: Planning - Creating the PRD
+
+**For BMad Method and Enterprise tracks:**
+
+1. Load the **PM agent** in a new chat
+2. Tell it to run the PRD workflow
+3. Once complete, you'll have:
+   - **PRD.md** - Your Product Requirements Document
+   - Epic breakdown
+
+**For Quick Flow track:**
+
+- Use **tech-spec** instead of PRD (no architecture needed)
+
+#### Phase 2 (Optional): UX Design
+
+If your project has a user interface:
+
+1. Load the **UX-Designer agent** in a new chat
+2. Tell it to run the UX design workflow
+3. After completion, run validations to ensure the Epics file stays updated
+
+#### Phase 3: Architecture
+
+**For BMad Method and Enterprise tracks:**
+
+1. Load the **Architect agent** in a new chat
+2. Tell it to run the create-architecture workflow
+3. After completion, run validations to ensure the Epics file stays updated
+
+#### Phase 3: Solutioning Gate Check (Highly Recommended)
+
+Once architecture is complete:
+
+1. Load the **Architect agent** in a new chat
+2. Tell it to run "solutioning-gate-check"
+3. This validates cohesion across all your planning documents (PRD, UX, Architecture, Epics)
+4. This was called the "PO Master Checklist" in v4
+
+**Why run this?** It ensures all your planning assets align properly before you start building.
+
+#### Context Management Tips
+
+- **Use 200k+ context models** for best results (Claude Sonnet 4.5, GPT-4, etc.)
+- **Fresh chat for each workflow** - Brainstorming, Briefs, Research, and PRD generation are all context-intensive
+- **No document sharding needed** - Unlike v4, you don't need to split documents
+- **Web Bundles coming soon** - Will help save LLM tokens for users with limited plans
+
+### Step 3: Start Building (Phase 4 - Implementation)
+
+Once planning and architecture are complete, you'll move to Phase 4. **Important: Each workflow below should be run in a fresh chat to avoid context limitations and hallucinations.**
+
+#### 3.1 Initialize Sprint Planning
+
+1. **Start a new chat** with the **SM (Scrum Master) agent**
+2. Wait for the menu to appear
+3. Tell the agent: "Run sprint-planning"
+4. This creates your `sprint-status.yaml` file that tracks all epics and stories
+
+#### 3.2 Create Epic Context (Optional but Recommended)
+
+1. **Start a new chat** with the **SM agent**
+2. Wait for the menu
+3. Tell the agent: "Run epic-tech-context"
+4. This creates technical context for the current epic before drafting stories
+
+#### 3.3 Draft Your First Story
+
+1. **Start a new chat** with the **SM agent**
+2. Wait for the menu
+3. Tell the agent: "Run create-story"
+4. This drafts the story file from the epic
+
+#### 3.4 Add Story Context (Optional but Recommended)
+
+1. **Start a new chat** with the **SM agent**
+2. Wait for the menu
+3. Tell the agent: "Run story-context"
+4. This creates implementation-specific technical context for the story
+
+#### 3.5 Implement the Story
+
+1. **Start a new chat** with the **DEV agent**
+2. Wait for the menu
+3. Tell the agent: "Run dev-story"
+4. The DEV agent will implement the story and update the sprint status
+
+#### 3.6 Review the Code (Optional but Recommended)
+
+1. **Start a new chat** with the **DEV agent**
+2. Wait for the menu
+3. Tell the agent: "Run code-review"
+4. The DEV agent performs quality validation (this was called QA in v4)
+
+### Step 4: Keep Going
+
+For each subsequent story, repeat the cycle using **fresh chats** for each workflow:
+
+1. **New chat** → SM agent → "Run create-story"
+2. **New chat** → SM agent → "Run story-context"
+3. **New chat** → DEV agent → "Run dev-story"
+4. **New chat** → DEV agent → "Run code-review" (optional but recommended)
+
+After completing all stories in an epic:
+
+1. **Start a new chat** with the **SM agent**
+2. Tell the agent: "Run retrospective"
+
+**Why fresh chats?** Context-intensive workflows can cause hallucinations if you keep issuing commands in the same chat. Starting fresh ensures the agent has maximum context capacity for each workflow.
+
+---
+
+## Understanding the Agents
+
+Each agent is a specialized AI persona:
+
+- **Analyst** - Initializes workflows and tracks progress
+- **PM** - Creates requirements and specifications
+- **UX-Designer** - If your project has a front end - this designer will help produce artifacts, come up with mock updates, and design a great look and feel with you giving it guidance.
+- **Architect** - Designs system architecture
+- **SM (Scrum Master)** - Manages sprints and creates stories
+- **DEV** - Implements code and reviews work
+
+## How Workflows Work
+
+1. **Load an agent** - Open the agent file in your IDE to activate it
+2. **Wait for the menu** - The agent will present its available workflows
+3. **Tell the agent what to run** - Say "Run [workflow-name]"
+4. **Follow the prompts** - The agent guides you through each step
+
+The agent creates documents, asks questions, and helps you make decisions throughout the process.
+
+## Project Tracking Files
+
+BMad creates two files to track your progress:
+
+**1. bmm-workflow-status.yaml**
+
+- Shows which phase you're in and what's next
+- Created by workflow-init
+- Updated automatically as you progress through phases
+
+**2. sprint-status.yaml** (Phase 4 only)
+
+- Tracks all your epics and stories during implementation
+- Critical for SM and DEV agents to know what to work on next
+- Created by sprint-planning workflow
+- Updated automatically as stories progress
+
+**You don't need to edit these manually** - agents update them as you work.
+
+---
+
+## The Complete Flow Visualized
+
+```mermaid
+flowchart LR
+    subgraph P1["Phase 1 (Optional)<br/>Analysis"]
+        direction TB
+        A1[Brainstorm]
+        A2[Research]
+        A3[Brief]
+        A4[Analyst]
+        A1 ~~~ A2 ~~~ A3 ~~~ A4
+    end
+
+    subgraph P2["Phase 2 (Required)<br/>Planning"]
+        direction TB
+        B1[Quick Flow:<br/>tech-spec]
+        B2[Method/Enterprise:<br/>PRD]
+        B3[UX opt]
+        B4[PM, UX]
+        B1 ~~~ B2 ~~~ B3 ~~~ B4
+    end
+
+    subgraph P3["Phase 3 (Track-dependent)<br/>Solutioning"]
+        direction TB
+        C1[Method/Enterprise:<br/>architecture]
+        C2[gate-check]
+        C3[Architect]
+        C1 ~~~ C2 ~~~ C3
+    end
+
+    subgraph P4["Phase 4 (Required)<br/>Implementation"]
+        direction TB
+        D1[Per Epic:<br/>epic context]
+        D2[Per Story:<br/>create-story]
+        D3[story-context]
+        D4[dev-story]
+        D5[code-review]
+        D6[SM, DEV]
+        D1 ~~~ D2 ~~~ D3 ~~~ D4 ~~~ D5 ~~~ D6
+    end
+
+    P1 --> P2
+    P2 --> P3
+    P3 --> P4
+
+    style P1 fill:#bbf,stroke:#333,stroke-width:2px,color:#000
+    style P2 fill:#bfb,stroke:#333,stroke-width:2px,color:#000
+    style P3 fill:#ffb,stroke:#333,stroke-width:2px,color:#000
+    style P4 fill:#fbf,stroke:#333,stroke-width:2px,color:#000
+```
+
+## Common Questions
+
+**Q: Do I always need architecture?**
+A: Only for BMad Method and Enterprise tracks. Quick Flow projects skip straight from tech-spec to implementation.
+
+**Q: Can I change my plan later?**
+A: Yes! The SM agent has a "correct-course" workflow for handling scope changes.
+
+**Q: What if I want to brainstorm first?**
+A: Load the Analyst agent and tell it to "Run brainstorm-project" before running workflow-init.
+
+**Q: Why do I need fresh chats for each workflow?**
+A: Context-intensive workflows can cause hallucinations if run in sequence. Fresh chats ensure maximum context capacity.
+
+**Q: Can I skip workflow-init and workflow-status?**
+A: Yes, once you learn the flow. Use the Quick Reference in Step 2 to go directly to the workflows you need.
+
+## Getting Help
+
+- **During workflows**: Agents guide you with questions and explanations
+- **Community**: [Discord](https://discord.gg/gk8jAdXWmj) - #general-dev, #bugs-issues
+- **Complete guide**: [BMM Workflow Documentation](./README.md#-workflow-guides)
+- **YouTube tutorials**: [BMad Code Channel](https://www.youtube.com/@BMadCode)
+
+---
+
+## Key Takeaways
+
+✅ **Always use fresh chats** - Load agents in new chats for each workflow to avoid context issues
+✅ **Let workflow-status guide you** - Load any agent and ask for status when unsure what's next
+✅ **Track matters** - Quick Flow uses tech-spec, BMad Method/Enterprise need PRD and architecture
+✅ **Tracking is automatic** - The status files update themselves, no manual editing needed
+✅ **Agents are flexible** - Use menu numbers, shortcuts (\*prd), or natural language
+
+**Ready to start building?** Install BMad, load the Analyst, run workflow-init, and let the agents guide you!

.bmad/bmm/docs/scale-adaptive-system.md

@@ -0,0 +1,599 @@
+# BMad Method Scale Adaptive System
+
+**Automatically adapts workflows to project complexity - from quick fixes to enterprise systems**
+
+---
+
+## Overview
+
+The **Scale Adaptive System** intelligently routes projects to the right planning methodology based on complexity, not arbitrary story counts.
+
+### The Problem
+
+Traditional methodologies apply the same process to every project:
+
+- Bug fix requires full design docs
+- Enterprise system built with minimal planning
+- One-size-fits-none approach
+
+### The Solution
+
+BMad Method adapts to three distinct planning tracks:
+
+- **Quick Flow**: Tech-spec only, implement immediately
+- **BMad Method**: PRD + Architecture, structured approach
+- **Enterprise Method**: Full planning with security/devops/test
+
+**Result**: Right planning depth for every project.
+
+---
+
+## Quick Reference
+
+### Three Tracks at a Glance
+
+| Track                 | Planning Depth        | Time Investment | Best For                                   |
+| --------------------- | --------------------- | --------------- | ------------------------------------------ |
+| **Quick Flow**        | Tech-spec only        | Hours to 1 day  | Simple features, bug fixes, clear scope    |
+| **BMad Method**       | PRD + Arch + UX       | 1-3 days        | Products, platforms, complex features      |
+| **Enterprise Method** | Method + Test/Sec/Ops | 3-7 days        | Enterprise needs, compliance, multi-tenant |
+
+### Decision Tree
+
+```mermaid
+flowchart TD
+    START{Describe your project}
+
+    START -->|Bug fix, simple feature| Q1{Scope crystal clear?}
+    START -->|Product, platform, complex| M[BMad Method<br/>PRD + Architecture]
+    START -->|Enterprise, compliance| E[Enterprise Method<br/>Extended Planning]
+
+    Q1 -->|Yes| QF[Quick Flow<br/>Tech-spec only]
+    Q1 -->|Uncertain| M
+
+    style QF fill:#bfb,stroke:#333,stroke-width:2px,color:#000
+    style M fill:#bbf,stroke:#333,stroke-width:2px,color:#000
+    style E fill:#f9f,stroke:#333,stroke-width:2px,color:#000
+```
+
+### Quick Keywords
+
+- **Quick Flow**: fix, bug, simple, add, clear scope
+- **BMad Method**: product, platform, dashboard, complex, multiple features
+- **Enterprise Method**: enterprise, multi-tenant, compliance, security, audit
+
+---
+
+## How Track Selection Works
+
+When you run `workflow-init`, it guides you through an educational choice:
+
+### 1. Description Analysis
+
+Analyzes your project description for complexity indicators and suggests an appropriate track.
+
+### 2. Educational Presentation
+
+Shows all three tracks with:
+
+- Time investment
+- Planning approach
+- Benefits and trade-offs
+- AI agent support level
+- Concrete examples
+
+### 3. Honest Recommendation
+
+Provides tailored recommendation based on:
+
+- Complexity keywords
+- Greenfield vs brownfield
+- User's description
+
+### 4. User Choice
+
+You choose the track that fits your situation. The system guides but never forces.
+
+**Example:**
+
+```
+workflow-init: "Based on 'Add user dashboard with analytics', I recommend BMad Method.
+               This involves multiple features and system design. The PRD + Architecture
+               gives AI agents complete context for better code generation."
+
+You: "Actually, this is simpler than it sounds. Quick Flow."
+
+workflow-init: "Got it! Using Quick Flow with tech-spec."
+```
+
+---
+
+## The Three Tracks
+
+### Track 1: Quick Flow
+
+**Definition**: Fast implementation with tech-spec planning.
+
+**Time**: Hours to 1 day of planning
+
+**Planning Docs**:
+
+- Tech-spec.md (implementation-focused)
+- Story files (1-15 typically, auto-detects epic structure)
+
+**Workflow Path**:
+
+```
+(Brownfield: document-project first if needed)
+↓
+Tech-Spec → Implement
+```
+
+**Use For**:
+
+- Bug fixes
+- Simple features
+- Enhancements with clear scope
+- Quick additions
+
+**Story Count**: Typically 1-15 stories (guidance, not rule)
+
+**Example**: "Fix authentication token expiration bug"
+
+**AI Agent Support**: Basic - minimal context provided
+
+**Trade-off**: Less planning = higher rework risk if complexity emerges
+
+---
+
+### Track 2: BMad Method (RECOMMENDED)
+
+**Definition**: Full product + system design planning.
+
+**Time**: 1-3 days of planning
+
+**Planning Docs**:
+
+- PRD.md (product requirements)
+- Architecture.md (system design)
+- UX Design (if UI components)
+- Epic breakdown with stories
+
+**Workflow Path**:
+
+```
+(Brownfield: document-project first if needed)
+↓
+(Optional: Analysis phase - brainstorm, research, product brief)
+↓
+PRD → (Optional UX) → Architecture → Gate Check → Implement
+```
+
+**Use For**:
+
+**Greenfield**:
+
+- Products
+- Platforms
+- Multi-feature initiatives
+
+**Brownfield**:
+
+- Complex additions (new UIs + APIs)
+- Major refactors
+- New modules
+
+**Story Count**: Typically 10-50+ stories (guidance, not rule)
+
+**Examples**:
+
+- "User dashboard with analytics and preferences"
+- "Add real-time collaboration to existing document editor"
+- "Payment integration system"
+
+**AI Agent Support**: Exceptional - complete context for coding partnership
+
+**Why Architecture for Brownfield?**
+
+Your brownfield documentation might be huge. Architecture workflow distills massive codebase context into a focused solution design specific to YOUR project. This keeps AI agents focused without getting lost in existing code.
+
+**Benefits**:
+
+- Complete AI agent context
+- Prevents architectural drift
+- Fewer surprises during implementation
+- Better code quality
+- Faster overall delivery (planning pays off)
+
+---
+
+### Track 3: Enterprise Method
+
+**Definition**: Extended planning with security, devops, and test strategy.
+
+**Time**: 3-7 days of planning
+
+**Planning Docs**:
+
+- All BMad Method docs PLUS:
+- Security Architecture
+- DevOps Strategy
+- Test Strategy
+- Compliance documentation
+
+**Workflow Path**:
+
+```
+(Brownfield: document-project nearly mandatory)
+↓
+Analysis (recommended/required) → PRD → UX → Architecture
+↓
+Security Architecture → DevOps Strategy → Test Strategy
+↓
+Gate Check → Implement
+```
+
+**Use For**:
+
+- Enterprise requirements
+- Multi-tenant systems
+- Compliance needs (HIPAA, SOC2, etc.)
+- Mission-critical systems
+- Security-sensitive applications
+
+**Story Count**: Typically 30+ stories (but defined by enterprise needs, not count)
+
+**Examples**:
+
+- "Multi-tenant SaaS platform"
+- "HIPAA-compliant patient portal"
+- "Add SOC2 audit logging to enterprise app"
+
+**AI Agent Support**: Elite - comprehensive enterprise planning
+
+**Critical for Enterprise**:
+
+- Security architecture and threat modeling
+- DevOps pipeline planning
+- Comprehensive test strategy
+- Risk assessment
+- Compliance mapping
+
+---
+
+## Planning Documents by Track
+
+### Quick Flow Documents
+
+**Created**: Upfront in Planning Phase
+
+**Tech-Spec**:
+
+- Problem statement and solution
+- Source tree changes
+- Technical implementation details
+- Detected stack and conventions (brownfield)
+- UX/UI considerations (if user-facing)
+- Testing strategy
+
+**Serves as**: Complete planning document (replaces PRD + Architecture)
+
+---
+
+### BMad Method Documents
+
+**Created**: Upfront in Planning and Solutioning Phases
+
+**PRD (Product Requirements Document)**:
+
+- Product vision and goals
+- Feature requirements
+- Epic breakdown with stories
+- Success criteria
+- User experience considerations
+- Business context
+
+**Architecture Document**:
+
+- System components and responsibilities
+- Data models and schemas
+- Integration patterns
+- Security architecture
+- Performance considerations
+- Deployment architecture
+
+**For Brownfield**: Acts as focused "solution design" that distills existing codebase into integration plan
+
+---
+
+### Enterprise Method Documents
+
+**Created**: Extended planning across multiple phases
+
+Includes all BMad Method documents PLUS:
+
+**Security Architecture**:
+
+- Threat modeling
+- Authentication/authorization design
+- Data protection strategy
+- Audit requirements
+
+**DevOps Strategy**:
+
+- CI/CD pipeline design
+- Infrastructure architecture
+- Monitoring and alerting
+- Disaster recovery
+
+**Test Strategy**:
+
+- Test approach and coverage
+- Automation strategy
+- Quality gates
+- Performance testing
+
+---
+
+## Workflow Comparison
+
+| Track           | Analysis    | Planning  | Architecture | Security/Ops | Typical Stories |
+| --------------- | ----------- | --------- | ------------ | ------------ | --------------- |
+| **Quick Flow**  | Optional    | Tech-spec | None         | None         | 1-15            |
+| **BMad Method** | Recommended | PRD + UX  | Required     | None         | 10-50+          |
+| **Enterprise**  | Required    | PRD + UX  | Required     | Required     | 30+             |
+
+**Note**: Story counts are GUIDANCE based on typical usage, NOT definitions of tracks.
+
+---
+
+## Brownfield Projects
+
+### Critical First Step
+
+For ALL brownfield projects: Run `document-project` BEFORE planning workflows.
+
+### Why document-project is Critical
+
+**Quick Flow** uses it for:
+
+- Auto-detecting existing patterns
+- Understanding codebase structure
+- Confirming conventions
+
+**BMad Method** uses it for:
+
+- Architecture inputs (existing structure)
+- Integration design
+- Pattern consistency
+
+**Enterprise Method** uses it for:
+
+- Security analysis
+- Integration architecture
+- Risk assessment
+
+### Brownfield Workflow Pattern
+
+```mermaid
+flowchart TD
+    START([Brownfield Project])
+    CHECK{Has docs/<br/>index.md?}
+
+    START --> CHECK
+    CHECK -->|No| DOC[document-project workflow<br/>10-30 min]
+    CHECK -->|Yes| TRACK[Choose Track]
+
+    DOC --> TRACK
+    TRACK -->|Quick| QF[Tech-Spec]
+    TRACK -->|Method| M[PRD + Arch]
+    TRACK -->|Enterprise| E[PRD + Arch + Sec/Ops]
+
+    style DOC fill:#ffb,stroke:#333,stroke-width:2px,color:#000
+    style TRACK fill:#bfb,stroke:#333,stroke-width:2px,color:#000
+```
+
+---
+
+## Common Scenarios
+
+### Scenario 1: Bug Fix (Quick Flow)
+
+**Input**: "Fix email validation bug in login form"
+
+**Detection**: Keywords "fix", "bug"
+
+**Track**: Quick Flow
+
+**Workflow**:
+
+1. (Optional) Brief analysis
+2. Tech-spec with single story
+3. Implement immediately
+
+**Time**: 2-4 hours total
+
+---
+
+### Scenario 2: Small Feature (Quick Flow)
+
+**Input**: "Add OAuth social login (Google, GitHub, Facebook)"
+
+**Detection**: Keywords "add", "feature", clear scope
+
+**Track**: Quick Flow
+
+**Workflow**:
+
+1. (Optional) Research OAuth providers
+2. Tech-spec with 3 stories
+3. Implement story-by-story
+
+**Time**: 1-3 days
+
+---
+
+### Scenario 3: Customer Portal (BMad Method)
+
+**Input**: "Build customer portal with dashboard, tickets, billing"
+
+**Detection**: Keywords "portal", "dashboard", multiple features
+
+**Track**: BMad Method
+
+**Workflow**:
+
+1. (Recommended) Product Brief
+2. PRD with epics
+3. (If UI) UX Design
+4. Architecture (system design)
+5. Gate Check
+6. Implement with sprint planning
+
+**Time**: 1-2 weeks
+
+---
+
+### Scenario 4: E-commerce Platform (BMad Method)
+
+**Input**: "Build e-commerce platform with products, cart, checkout, admin, analytics"
+
+**Detection**: Keywords "platform", multiple subsystems
+
+**Track**: BMad Method
+
+**Workflow**:
+
+1. Research + Product Brief
+2. Comprehensive PRD
+3. UX Design (recommended)
+4. System Architecture (required)
+5. Gate check
+6. Implement with phased approach
+
+**Time**: 3-6 weeks
+
+---
+
+### Scenario 5: Brownfield Addition (BMad Method)
+
+**Input**: "Add search functionality to existing product catalog"
+
+**Detection**: Brownfield + moderate complexity
+
+**Track**: BMad Method (not Quick Flow)
+
+**Critical First Step**:
+
+1. **Run document-project** to analyze existing codebase
+
+**Then Workflow**: 2. PRD for search feature 3. Architecture (integration design - highly recommended) 4. Implement following existing patterns
+
+**Time**: 1-2 weeks
+
+**Why Method not Quick Flow?**: Integration with existing catalog system benefits from architecture planning to ensure consistency.
+
+---
+
+### Scenario 6: Multi-tenant Platform (Enterprise Method)
+
+**Input**: "Add multi-tenancy to existing single-tenant SaaS platform"
+
+**Detection**: Keywords "multi-tenant", enterprise scale
+
+**Track**: Enterprise Method
+
+**Workflow**:
+
+1. Document-project (mandatory)
+2. Research (compliance, security)
+3. PRD (multi-tenancy requirements)
+4. Architecture (tenant isolation design)
+5. Security Architecture (data isolation, auth)
+6. DevOps Strategy (tenant provisioning, monitoring)
+7. Test Strategy (tenant isolation testing)
+8. Gate check
+9. Phased implementation
+
+**Time**: 3-6 months
+
+---
+
+## Best Practices
+
+### 1. Document-Project First for Brownfield
+
+Always run `document-project` before starting brownfield planning. AI agents need existing codebase context.
+
+### 2. Trust the Recommendation
+
+If `workflow-init` suggests BMad Method, there's probably complexity you haven't considered. Review carefully before overriding.
+
+### 3. Start Smaller if Uncertain
+
+Uncertain between Quick Flow and Method? Start with Quick Flow. You can create PRD later if needed.
+
+### 4. Don't Skip Gate Checks
+
+For BMad Method and Enterprise, gate checks prevent costly mistakes. Invest the time.
+
+### 5. Architecture is Optional but Recommended for Brownfield
+
+Brownfield BMad Method makes architecture optional, but it's highly recommended. It distills complex codebase into focused solution design.
+
+### 6. Discovery Phase Based on Need
+
+Brainstorming and research are offered regardless of track. Use them when you need to think through the problem space.
+
+### 7. Product Brief for Greenfield Method
+
+Product Brief is only offered for greenfield BMad Method and Enterprise. It's optional but helps with strategic thinking.
+
+---
+
+## Key Differences from Legacy System
+
+### Old System (Levels 0-4)
+
+- Arbitrary story count thresholds
+- Level 2 vs Level 3 based on story count
+- Confusing overlap zones (5-10 stories, 12-40 stories)
+- Tech-spec and PRD shown as conflicting options
+
+### New System (3 Tracks)
+
+- Methodology-based distinction (not story counts)
+- Story counts as guidance, not definitions
+- Clear track purposes:
+  - Quick Flow = Implementation-focused
+  - BMad Method = Product + system design
+  - Enterprise = Extended with security/ops
+- Mutually exclusive paths chosen upfront
+- Educational decision-making
+
+---
+
+## Migration from Old System
+
+If you have existing projects using the old level system:
+
+- **Level 0-1** → Quick Flow
+- **Level 2-3** → BMad Method
+- **Level 4** → Enterprise Method
+
+Run `workflow-init` on existing projects to migrate to new tracking system. It detects existing planning artifacts and creates appropriate workflow tracking.
+
+---
+
+## Related Documentation
+
+- **[Quick Start Guide](./quick-start.md)** - Get started with BMM
+- **[Quick Spec Flow](./quick-spec-flow.md)** - Details on Quick Flow track
+- **[Brownfield Guide](./brownfield-guide.md)** - Existing codebase workflows
+- **[Glossary](./glossary.md)** - Complete terminology
+- **[FAQ](./faq.md)** - Common questions
+- **[Workflows Guide](./README.md#-workflow-guides)** - Complete workflow reference
+
+---
+
+_Scale Adaptive System - Right planning depth for every project._

.bmad/bmm/docs/test-architecture.md

@@ -0,0 +1,394 @@
+---
+last-redoc-date: 2025-11-05
+---
+
+# Test Architect (TEA) Agent Guide
+
+## Overview
+
+- **Persona:** Murat, Master Test Architect and Quality Advisor focused on risk-based testing, fixture architecture, ATDD, and CI/CD governance.
+- **Mission:** Deliver actionable quality strategies, automation coverage, and gate decisions that scale with project complexity and compliance demands.
+- **Use When:** BMad Method or Enterprise track projects, integration risk is non-trivial, brownfield regression risk exists, or compliance/NFR evidence is required. (Quick Flow projects typically don't require TEA)
+
+## TEA Workflow Lifecycle
+
+TEA integrates into the BMad development lifecycle during Solutioning (Phase 3) and Implementation (Phase 4):
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','secondaryColor':'#fff','tertiaryColor':'#fff','fontSize':'16px','fontFamily':'arial'}}}%%
+graph TB
+    subgraph Phase2["<b>Phase 2: PLANNING</b>"]
+        PM["<b>PM: *prd (creates PRD + epics)</b>"]
+        PlanNote["<b>Business requirements phase</b>"]
+        PM -.-> PlanNote
+    end
+
+    subgraph Phase3["<b>Phase 3: SOLUTIONING</b>"]
+        Architecture["<b>Architect: *architecture</b>"]
+        Framework["<b>TEA: *framework</b>"]
+        CI["<b>TEA: *ci</b>"]
+        GateCheck["<b>Architect: *solutioning-gate-check</b>"]
+        Architecture --> Framework
+        Framework --> CI
+        CI --> GateCheck
+        Phase3Note["<b>Test infrastructure AFTER architecture</b><br/>defines technology stack"]
+        Framework -.-> Phase3Note
+    end
+
+    subgraph Phase4["<b>Phase 4: IMPLEMENTATION - Per Epic Cycle</b>"]
+        SprintPlan["<b>SM: *sprint-planning</b>"]
+        TestDesign["<b>TEA: *test-design (per epic)</b>"]
+        CreateStory["<b>SM: *create-story</b>"]
+        ATDD["<b>TEA: *atdd (optional, before dev)</b>"]
+        DevImpl["<b>DEV: implements story</b>"]
+        Automate["<b>TEA: *automate</b>"]
+        TestReview1["<b>TEA: *test-review (optional)</b>"]
+        Trace1["<b>TEA: *trace (refresh coverage)</b>"]
+
+        SprintPlan --> TestDesign
+        TestDesign --> CreateStory
+        CreateStory --> ATDD
+        ATDD --> DevImpl
+        DevImpl --> Automate
+        Automate --> TestReview1
+        TestReview1 --> Trace1
+        Trace1 -.->|next story| CreateStory
+        TestDesignNote["<b>Test design: 'How do I test THIS epic?'</b><br/>Creates test-design-epic-N.md per epic"]
+        TestDesign -.-> TestDesignNote
+    end
+
+    subgraph Gate["<b>EPIC/RELEASE GATE</b>"]
+        NFR["<b>TEA: *nfr-assess (if not done earlier)</b>"]
+        TestReview2["<b>TEA: *test-review (final audit, optional)</b>"]
+        TraceGate["<b>TEA: *trace - Phase 2: Gate</b>"]
+        GateDecision{"<b>Gate Decision</b>"}
+
+        NFR --> TestReview2
+        TestReview2 --> TraceGate
+        TraceGate --> GateDecision
+        GateDecision -->|PASS| Pass["<b>PASS ✅</b>"]
+        GateDecision -->|CONCERNS| Concerns["<b>CONCERNS ⚠️</b>"]
+        GateDecision -->|FAIL| Fail["<b>FAIL ❌</b>"]
+        GateDecision -->|WAIVED| Waived["<b>WAIVED ⏭️</b>"]
+    end
+
+    Phase2 --> Phase3
+    Phase3 --> Phase4
+    Phase4 --> Gate
+
+    style Phase2 fill:#bbdefb,stroke:#0d47a1,stroke-width:3px,color:#000
+    style Phase3 fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px,color:#000
+    style Phase4 fill:#e1bee7,stroke:#4a148c,stroke-width:3px,color:#000
+    style Gate fill:#ffe082,stroke:#f57c00,stroke-width:3px,color:#000
+    style Pass fill:#4caf50,stroke:#1b5e20,stroke-width:3px,color:#000
+    style Concerns fill:#ffc107,stroke:#f57f17,stroke-width:3px,color:#000
+    style Fail fill:#f44336,stroke:#b71c1c,stroke-width:3px,color:#000
+    style Waived fill:#9c27b0,stroke:#4a148c,stroke-width:3px,color:#000
+```
+
+**Phase Numbering Note:** BMad uses a 4-phase methodology with optional Phase 0/1:
+
+- **Phase 0** (Optional): Documentation (brownfield prerequisite - `*document-project`)
+- **Phase 1** (Optional): Discovery/Analysis (`*brainstorm`, `*research`, `*product-brief`)
+- **Phase 2** (Required): Planning (`*prd` creates PRD + epics)
+- **Phase 3** (Track-dependent): Solutioning (`*architecture` → TEA: `*framework`, `*ci` → `*solutioning-gate-check`)
+- **Phase 4** (Required): Implementation (`*sprint-planning` → per-epic: `*test-design` → per-story: dev workflows)
+
+**TEA workflows:** `*framework` and `*ci` run once in Phase 3 after architecture. `*test-design` runs per-epic in Phase 4. Output: `test-design-epic-N.md`.
+
+Quick Flow track skips Phases 0, 1, and 3. BMad Method and Enterprise use all phases based on project needs.
+
+### Why TEA is Different from Other BMM Agents
+
+TEA is the only BMM agent that operates in **multiple phases** (Phase 3 and Phase 4) and has its own **knowledge base architecture**.
+
+<details>
+<summary><strong>Cross-Phase Operation & Unique Architecture</strong></summary>
+
+### Phase-Specific Agents (Standard Pattern)
+
+Most BMM agents work in a single phase:
+
+- **Phase 1 (Analysis)**: Analyst agent
+- **Phase 2 (Planning)**: PM agent
+- **Phase 3 (Solutioning)**: Architect agent
+- **Phase 4 (Implementation)**: SM, DEV agents
+
+### TEA: Multi-Phase Quality Agent (Unique Pattern)
+
+TEA is **the only agent that operates in multiple phases**:
+
+```
+Phase 1 (Analysis) → [TEA not typically used]
+    ↓
+Phase 2 (Planning) → [PM defines requirements - TEA not active]
+    ↓
+Phase 3 (Solutioning) → TEA: *framework, *ci (test infrastructure AFTER architecture)
+    ↓
+Phase 4 (Implementation) → TEA: *test-design (per epic: "how do I test THIS feature?")
+                        → TEA: *atdd, *automate, *test-review, *trace (per story)
+    ↓
+Epic/Release Gate → TEA: *nfr-assess, *trace Phase 2 (release decision)
+```
+
+### TEA's 8 Workflows Across Phases
+
+**Standard agents**: 1-3 workflows per phase
+**TEA**: 8 workflows across Phase 3, Phase 4, and Release Gate
+
+| Phase       | TEA Workflows                                         | Frequency        | Purpose                                        |
+| ----------- | ----------------------------------------------------- | ---------------- | ---------------------------------------------- |
+| **Phase 2** | (none)                                                | -                | Planning phase - PM defines requirements       |
+| **Phase 3** | *framework, *ci                                       | Once per project | Setup test infrastructure AFTER architecture   |
+| **Phase 4** | *test-design, *atdd, *automate, *test-review, \*trace | Per epic/story   | Test planning per epic, then per-story testing |
+| **Release** | *nfr-assess, *trace (Phase 2: gate)                   | Per epic/release | Go/no-go decision                              |
+
+**Note**: `*trace` is a two-phase workflow: Phase 1 (traceability) + Phase 2 (gate decision). This reduces cognitive load while maintaining natural workflow.
+
+### Unique Directory Architecture
+
+TEA is the only BMM agent with its own top-level module directory (`bmm/testarch/`):
+
+```
+src/modules/bmm/
+├── agents/
+│   └── tea.agent.yaml          # Agent definition (standard location)
+├── workflows/
+│   └── testarch/               # TEA workflows (standard location)
+└── testarch/                   # Knowledge base (UNIQUE!)
+    ├── knowledge/              # 21 production-ready test pattern fragments
+    ├── tea-index.csv           # Centralized knowledge lookup (21 fragments indexed)
+    └── README.md               # This guide
+```
+
+### Why TEA Gets Special Treatment
+
+TEA uniquely requires:
+
+- **Extensive domain knowledge**: 21 fragments, 12,821 lines covering test patterns, CI/CD, fixtures, quality practices, healing strategies
+- **Centralized reference system**: `tea-index.csv` for on-demand fragment loading during workflow execution
+- **Cross-cutting concerns**: Domain-specific testing patterns (vs project-specific artifacts like PRDs/stories)
+- **Optional MCP integration**: Healing, exploratory, and verification modes for enhanced testing capabilities
+
+This architecture enables TEA to maintain consistent, production-ready testing patterns across all BMad projects while operating across multiple development phases.
+
+</details>
+
+## High-Level Cheat Sheets
+
+These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks** across the **4-Phase Methodology** (Phase 1: Analysis, Phase 2: Planning, Phase 3: Solutioning, Phase 4: Implementation).
+
+**Note:** Quick Flow projects typically don't require TEA (covered in Overview). These cheat sheets focus on BMad Method and Enterprise tracks where TEA adds value.
+
+**Legend for Track Deltas:**
+
+- ➕ = New workflow or phase added (doesn't exist in baseline)
+- 🔄 = Modified focus (same workflow, different emphasis or purpose)
+- 📦 = Additional output or archival requirement
+
+### Greenfield - BMad Method (Simple/Standard Work)
+
+**Planning Track:** BMad Method (PRD + Architecture)
+**Use Case:** New projects with standard complexity
+
+| Workflow Stage             | Test Architect                                                    | Dev / Team                                           | Outputs                                                    |
+| -------------------------- | ----------------------------------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------------- |
+| **Phase 1**: Discovery     | -                                                                 | Analyst `*product-brief` (optional)                  | `product-brief.md`                                         |
+| **Phase 2**: Planning      | -                                                                 | PM `*prd` (creates PRD + epics)                      | PRD, epics                                                 |
+| **Phase 3**: Solutioning   | Run `*framework`, `*ci` AFTER architecture                        | Architect `*architecture`, `*solutioning-gate-check` | Architecture, test scaffold, CI pipeline                   |
+| **Phase 4**: Sprint Start  | -                                                                 | SM `*sprint-planning`                                | Sprint status file with all epics and stories              |
+| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic (per-epic test plan)             | Review epic scope                                    | `test-design-epic-N.md` with risk assessment and test plan |
+| **Phase 4**: Story Dev     | (Optional) `*atdd` before dev, then `*automate` after             | SM `*create-story`, DEV implements                   | Tests, story implementation                                |
+| **Phase 4**: Story Review  | Execute `*test-review` (optional), re-run `*trace`                | Address recommendations, update code/tests           | Quality report, refreshed coverage matrix                  |
+| **Phase 4**: Release Gate  | (Optional) `*test-review` for final audit, Run `*trace` (Phase 2) | Confirm Definition of Done, share release notes      | Quality audit, Gate YAML + release summary                 |
+
+<details>
+<summary>Execution Notes</summary>
+
+- Run `*framework` only once per repo or when modern harness support is missing.
+- **Phase 3 (Solutioning)**: After architecture is complete, run `*framework` and `*ci` to setup test infrastructure based on architectural decisions.
+- **Phase 4 starts**: After solutioning is complete, sprint planning loads all epics.
+- **`*test-design` runs per-epic**: At the beginning of working on each epic, run `*test-design` to create a test plan for THAT specific epic/feature. Output: `test-design-epic-N.md`.
+- Use `*atdd` before coding when the team can adopt ATDD; share its checklist with the dev agent.
+- Post-implementation, keep `*trace` current, expand coverage with `*automate`, optionally review test quality with `*test-review`. For release gate, run `*trace` with Phase 2 enabled to get deployment decision.
+- Use `*test-review` after `*atdd` to validate generated tests, after `*automate` to ensure regression quality, or before gate for final audit.
+
+</details>
+
+<details>
+<summary>Worked Example – “Nova CRM” Greenfield Feature</summary>
+
+1. **Planning (Phase 2):** Analyst runs `*product-brief`; PM executes `*prd` to produce PRD and epics.
+2. **Solutioning (Phase 3):** Architect completes `*architecture` for the new module; TEA sets up test infrastructure via `*framework` and `*ci` based on architectural decisions; gate check validates planning completeness.
+3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load all epics into sprint status.
+4. **Epic 1 Planning (Phase 4):** TEA runs `*test-design` to create test plan for Epic 1, producing `test-design-epic-1.md` with risk assessment.
+5. **Story Implementation (Phase 4):** For each story in Epic 1, SM generates story via `*create-story`; TEA optionally runs `*atdd`; Dev implements with guidance from failing tests.
+6. **Post-Dev (Phase 4):** TEA runs `*automate`, optionally `*test-review` to audit test quality, re-runs `*trace` to refresh coverage.
+7. **Release Gate:** TEA runs `*trace` with Phase 2 enabled to generate gate decision.
+
+</details>
+
+### Brownfield - BMad Method or Enterprise (Simple or Complex)
+
+**Planning Tracks:** BMad Method or Enterprise Method
+**Use Case:** Existing codebases - simple additions (BMad Method) or complex enterprise requirements (Enterprise Method)
+
+**🔄 Brownfield Deltas from Greenfield:**
+
+- ➕ Phase 0 (Documentation) - Document existing codebase if undocumented
+- ➕ Phase 2: `*trace` - Baseline existing test coverage before planning
+- 🔄 Phase 4: `*test-design` - Focus on regression hotspots and brownfield risks
+- 🔄 Phase 4: Story Review - May include `*nfr-assess` if not done earlier
+
+| Workflow Stage                | Test Architect                                                               | Dev / Team                                           | Outputs                                                                |
+| ----------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------- | ---------------------------------------------------------------------- |
+| **Phase 0**: Documentation ➕ | -                                                                            | Analyst `*document-project` (if undocumented)        | Comprehensive project documentation                                    |
+| **Phase 1**: Discovery        | -                                                                            | Analyst/PM/Architect rerun planning workflows        | Updated planning artifacts in `{output_folder}`                        |
+| **Phase 2**: Planning         | Run ➕ `*trace` (baseline coverage)                                          | PM `*prd` (creates PRD + epics)                      | PRD, epics, ➕ coverage baseline                                       |
+| **Phase 3**: Solutioning      | Run `*framework`, `*ci` AFTER architecture                                   | Architect `*architecture`, `*solutioning-gate-check` | Architecture, test framework, CI pipeline                              |
+| **Phase 4**: Sprint Start     | -                                                                            | SM `*sprint-planning`                                | Sprint status file with all epics and stories                          |
+| **Phase 4**: Epic Planning    | Run `*test-design` for THIS epic 🔄 (regression hotspots)                    | Review epic scope and brownfield risks               | `test-design-epic-N.md` with brownfield risk assessment and mitigation |
+| **Phase 4**: Story Dev        | (Optional) `*atdd` before dev, then `*automate` after                        | SM `*create-story`, DEV implements                   | Tests, story implementation                                            |
+| **Phase 4**: Story Review     | Apply `*test-review` (optional), re-run `*trace`, ➕ `*nfr-assess` if needed | Resolve gaps, update docs/tests                      | Quality report, refreshed coverage matrix, NFR report                  |
+| **Phase 4**: Release Gate     | (Optional) `*test-review` for final audit, Run `*trace` (Phase 2)            | Capture sign-offs, share release notes               | Quality audit, Gate YAML + release summary                             |
+
+<details>
+<summary>Execution Notes</summary>
+
+- Lead with `*trace` during Planning (Phase 2) to baseline existing test coverage before architecture work begins.
+- **Phase 3 (Solutioning)**: After architecture is complete, run `*framework` and `*ci` to modernize test infrastructure. For brownfield, framework may need to integrate with or replace existing test setup.
+- **Phase 4 starts**: After solutioning is complete and sprint planning loads all epics.
+- **`*test-design` runs per-epic**: At the beginning of working on each epic, run `*test-design` to identify regression hotspots, integration risks, and mitigation strategies for THAT specific epic/feature. Output: `test-design-epic-N.md`.
+- Use `*atdd` when stories benefit from ATDD; otherwise proceed to implementation and rely on post-dev automation.
+- After development, expand coverage with `*automate`, optionally review test quality with `*test-review`, re-run `*trace` (Phase 2 for gate decision). Run `*nfr-assess` now if non-functional risks weren't addressed earlier.
+- Use `*test-review` to validate existing brownfield tests or audit new tests before gate.
+
+</details>
+
+<details>
+<summary>Worked Example – “Atlas Payments” Brownfield Story</summary>
+
+1. **Planning (Phase 2):** PM executes `*prd` to update PRD and `epics.md` (Epic 1: Payment Processing); TEA runs `*trace` to baseline existing coverage.
+2. **Solutioning (Phase 3):** Architect triggers `*architecture` capturing legacy payment flows and integration architecture; TEA sets up `*framework` and `*ci` based on architectural decisions; gate check validates planning.
+3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load Epic 1 into sprint status.
+4. **Epic 1 Planning (Phase 4):** TEA runs `*test-design` for Epic 1 (Payment Processing), producing `test-design-epic-1.md` that flags settlement edge cases, regression hotspots, and mitigation plans.
+5. **Story Implementation (Phase 4):** For each story in Epic 1, SM generates story via `*create-story`; TEA runs `*atdd` producing failing Playwright specs; Dev implements with guidance from tests and checklist.
+6. **Post-Dev (Phase 4):** TEA applies `*automate`, optionally `*test-review` to audit test quality, re-runs `*trace` to refresh coverage.
+7. **Release Gate:** TEA performs `*nfr-assess` to validate SLAs, runs `*trace` with Phase 2 enabled to generate gate decision (PASS/CONCERNS/FAIL).
+
+</details>
+
+### Greenfield - Enterprise Method (Enterprise/Compliance Work)
+
+**Planning Track:** Enterprise Method (BMad Method + extended security/devops/test strategies)
+**Use Case:** New enterprise projects with compliance, security, or complex regulatory requirements
+
+**🏢 Enterprise Deltas from BMad Method:**
+
+- ➕ Phase 1: `*research` - Domain and compliance research (recommended)
+- ➕ Phase 2: `*nfr-assess` - Capture NFR requirements early (security/performance/reliability)
+- 🔄 Phase 4: `*test-design` - Enterprise focus (compliance, security architecture alignment)
+- 📦 Release Gate - Archive artifacts and compliance evidence for audits
+
+| Workflow Stage             | Test Architect                                                           | Dev / Team                                           | Outputs                                                            |
+| -------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------- | ------------------------------------------------------------------ |
+| **Phase 1**: Discovery     | -                                                                        | Analyst ➕ `*research`, `*product-brief`             | Domain research, compliance analysis, product brief                |
+| **Phase 2**: Planning      | Run ➕ `*nfr-assess`                                                     | PM `*prd` (creates PRD + epics), UX `*create-design` | Enterprise PRD, epics, UX design, ➕ NFR documentation             |
+| **Phase 3**: Solutioning   | Run `*framework`, `*ci` AFTER architecture                               | Architect `*architecture`, `*solutioning-gate-check` | Architecture, test framework, CI pipeline                          |
+| **Phase 4**: Sprint Start  | -                                                                        | SM `*sprint-planning`                                | Sprint plan with all epics                                         |
+| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (compliance focus)                   | Review epic scope and compliance requirements        | `test-design-epic-N.md` with security/performance/compliance focus |
+| **Phase 4**: Story Dev     | (Optional) `*atdd`, `*automate`, `*test-review`, `*trace` per story      | SM `*create-story`, DEV implements                   | Tests, fixtures, quality reports, coverage matrices                |
+| **Phase 4**: Release Gate  | Final `*test-review` audit, Run `*trace` (Phase 2), 📦 archive artifacts | Capture sign-offs, 📦 compliance evidence            | Quality audit, updated assessments, gate YAML, 📦 audit trail      |
+
+<details>
+<summary>Execution Notes</summary>
+
+- `*nfr-assess` runs early in Planning (Phase 2) to capture compliance, security, and performance requirements upfront.
+- **Phase 3 (Solutioning)**: After architecture is complete, run `*framework` and `*ci` with enterprise-grade configurations (selective testing, burn-in jobs, caching, notifications).
+- **Phase 4 starts**: After solutioning is complete and sprint planning loads all epics.
+- **`*test-design` runs per-epic**: At the beginning of working on each epic, run `*test-design` to create an enterprise-focused test plan for THAT specific epic, ensuring alignment with security architecture, performance targets, and compliance requirements. Output: `test-design-epic-N.md`.
+- Use `*atdd` for stories when feasible so acceptance tests can lead implementation.
+- Use `*test-review` per story or sprint to maintain quality standards and ensure compliance with testing best practices.
+- Prior to release, rerun coverage (`*trace`, `*automate`), perform final quality audit with `*test-review`, and formalize the decision with `*trace` Phase 2 (gate decision); archive artifacts for compliance audits.
+
+</details>
+
+<details>
+<summary>Worked Example – “Helios Ledger” Enterprise Release</summary>
+
+1. **Planning (Phase 2):** Analyst runs `*research` and `*product-brief`; PM completes `*prd` creating PRD and epics; TEA runs `*nfr-assess` to establish NFR targets.
+2. **Solutioning (Phase 3):** Architect completes `*architecture` with enterprise considerations; TEA sets up `*framework` and `*ci` with enterprise-grade configurations based on architectural decisions; gate check validates planning completeness.
+3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load all epics into sprint status.
+4. **Per-Epic (Phase 4):** For each epic, TEA runs `*test-design` to create epic-specific test plan (e.g., `test-design-epic-1.md`, `test-design-epic-2.md`) with compliance-focused risk assessment.
+5. **Per-Story (Phase 4):** For each story, TEA uses `*atdd`, `*automate`, `*test-review`, and `*trace`; Dev teams iterate on the findings.
+6. **Release Gate:** TEA re-checks coverage, performs final quality audit with `*test-review`, and logs the final gate decision via `*trace` Phase 2, archiving artifacts for compliance.
+
+</details>
+
+## Command Catalog
+
+<details>
+<summary><strong>Optional Playwright MCP Enhancements</strong></summary>
+
+**Two Playwright MCP servers** (actively maintained, continuously updated):
+
+- `playwright` - Browser automation (`npx @playwright/mcp@latest`)
+- `playwright-test` - Test runner with failure analysis (`npx playwright run-test-mcp-server`)
+
+**How MCP Enhances TEA Workflows**:
+
+MCP provides additional capabilities on top of TEA's default AI-based approach:
+
+1. `*test-design`:
+   - Default: Analysis + documentation
+   - **+ MCP**: Interactive UI discovery with `browser_navigate`, `browser_click`, `browser_snapshot`, behavior observation
+
+   Benefit: Discover actual functionality, edge cases, undocumented features
+
+2. `*atdd`, `*automate`:
+   - Default: Infers selectors and interactions from requirements and knowledge fragments
+   - **+ MCP**: Generates tests **then** verifies with `generator_setup_page`, `browser_*` tools, validates against live app
+
+   Benefit: Accurate selectors from real DOM, verified behavior, refined test code
+
+3. `*automate`:
+   - Default: Pattern-based fixes from error messages + knowledge fragments
+   - **+ MCP**: Pattern fixes **enhanced with** `browser_snapshot`, `browser_console_messages`, `browser_network_requests`, `browser_generate_locator`
+
+   Benefit: Visual failure context, live DOM inspection, root cause discovery
+
+**Config example**:
+
+```json
+{
+  "mcpServers": {
+    "playwright": {
+      "command": "npx",
+      "args": ["@playwright/mcp@latest"]
+    },
+    "playwright-test": {
+      "command": "npx",
+      "args": ["playwright", "run-test-mcp-server"]
+    }
+  }
+}
+```
+
+**To disable**: Set `tea_use_mcp_enhancements: false` in `.bmad/bmm/config.yaml` OR remove MCPs from IDE config.
+
+</details>
+
+<br></br>
+
+| Command        | Workflow README                                   | Primary Outputs                                                                               | Notes                                                | With Playwright MCP Enhancements                                                                             |
+| -------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| `*framework`   | [📖](../workflows/testarch/framework/README.md)   | Playwright/Cypress scaffold, `.env.example`, `.nvmrc`, sample specs                           | Use when no production-ready harness exists          | -                                                                                                            |
+| `*ci`          | [📖](../workflows/testarch/ci/README.md)          | CI workflow, selective test scripts, secrets checklist                                        | Platform-aware (GitHub Actions default)              | -                                                                                                            |
+| `*test-design` | [📖](../workflows/testarch/test-design/README.md) | Combined risk assessment, mitigation plan, and coverage strategy                              | Risk scoring + optional exploratory mode             | **+ Exploratory**: Interactive UI discovery with browser automation (uncover actual functionality)           |
+| `*atdd`        | [📖](../workflows/testarch/atdd/README.md)        | Failing acceptance tests + implementation checklist                                           | TDD red phase + optional recording mode              | **+ Recording**: AI generation verified with live browser (accurate selectors from real DOM)                 |
+| `*automate`    | [📖](../workflows/testarch/automate/README.md)    | Prioritized specs, fixtures, README/script updates, DoD summary                               | Optional healing/recording, avoid duplicate coverage | **+ Healing**: Pattern fixes enhanced with visual debugging + **+ Recording**: AI verified with live browser |
+| `*test-review` | [📖](../workflows/testarch/test-review/README.md) | Test quality review report with 0-100 score, violations, fixes                                | Reviews tests against knowledge base patterns        | -                                                                                                            |
+| `*nfr-assess`  | [📖](../workflows/testarch/nfr-assess/README.md)  | NFR assessment report with actions                                                            | Focus on security/performance/reliability            | -                                                                                                            |
+| `*trace`       | [📖](../workflows/testarch/trace/README.md)       | Phase 1: Coverage matrix, recommendations. Phase 2: Gate decision (PASS/CONCERNS/FAIL/WAIVED) | Two-phase workflow: traceability + gate decision     | -                                                                                                            |
+
+**📖** = Click to view detailed workflow documentation

.bmad/bmm/docs/workflow-architecture-reference.md

@@ -0,0 +1,371 @@
+# Decision Architecture Workflow - Technical Reference
+
+**Module:** BMM (BMAD Method Module)
+**Type:** Solutioning Workflow
+
+---
+
+## Overview
+
+The Decision Architecture workflow is a complete reimagining of how architectural decisions are made in the BMAD Method. Instead of template-driven documentation, this workflow facilitates an intelligent conversation that produces a **decision-focused architecture document** optimized for preventing AI agent conflicts during implementation.
+
+---
+
+## Core Philosophy
+
+**The Problem**: When multiple AI agents implement different parts of a system, they make conflicting technical decisions leading to incompatible implementations.
+
+**The Solution**: A "consistency contract" that documents all critical technical decisions upfront, ensuring every agent follows the same patterns and uses the same technologies.
+
+---
+
+## Key Features
+
+### 1. Starter Template Intelligence ⭐ NEW
+
+- Discovers relevant starter templates (create-next-app, create-t3-app, etc.)
+- Considers UX requirements when selecting templates (animations, accessibility, etc.)
+- Searches for current CLI options and defaults
+- Documents decisions made BY the starter template
+- Makes remaining architectural decisions around the starter foundation
+- First implementation story becomes "initialize with starter command"
+
+### 2. Adaptive Facilitation
+
+- Adjusts conversation style based on user skill level (beginner/intermediate/expert)
+- Experts get rapid, technical discussions
+- Beginners receive education and protection from complexity
+- Everyone produces the same high-quality output
+
+### 3. Dynamic Version Verification
+
+- NEVER trusts hardcoded version numbers
+- Uses WebSearch to find current stable versions
+- Verifies versions during the conversation
+- Documents only verified, current versions
+
+### 4. Intelligent Discovery
+
+- No rigid project type templates
+- Analyzes PRD to identify which decisions matter for THIS project
+- Uses knowledge base of decisions and patterns
+- Scales to infinite project types
+
+### 5. Collaborative Decision Making
+
+- Facilitates discussion for each critical decision
+- Presents options with trade-offs
+- Integrates advanced elicitation for innovative approaches
+- Ensures decisions are coherent and compatible
+
+### 6. Consistent Output
+
+- Structured decision collection during conversation
+- Strict document generation from collected decisions
+- Validated against hard requirements
+- Optimized for AI agent consumption
+
+---
+
+## Workflow Structure
+
+```
+Step 0: Validate workflow and extract project configuration
+Step 0.5: Validate workflow sequencing
+Step 1: Load PRD and understand project context
+Step 2: Discover and evaluate starter templates ⭐ NEW
+Step 3: Adapt facilitation style and identify remaining decisions
+Step 4: Facilitate collaborative decision making (with version verification)
+Step 5: Address cross-cutting concerns
+Step 6: Define project structure and boundaries
+Step 7: Design novel architectural patterns (when needed) ⭐ NEW
+Step 8: Define implementation patterns to prevent agent conflicts
+Step 9: Validate architectural coherence
+Step 10: Generate decision architecture document (with initialization commands)
+Step 11: Validate document completeness
+Step 12: Final review and update workflow status
+```
+
+---
+
+## Files in This Workflow
+
+- **workflow.yaml** - Configuration and metadata
+- **instructions.md** - The adaptive facilitation flow
+- **decision-catalog.yaml** - Knowledge base of all architectural decisions
+- **architecture-patterns.yaml** - Common patterns identified from requirements
+- **pattern-categories.csv** - Pattern principles that teach LLM what needs defining
+- **checklist.md** - Validation requirements for the output document
+- **architecture-template.md** - Strict format for the final document
+
+---
+
+## How It's Different from Old architecture
+
+| Aspect               | Old Workflow                                 | New Workflow                                    |
+| -------------------- | -------------------------------------------- | ----------------------------------------------- |
+| **Approach**         | Template-driven                              | Conversation-driven                             |
+| **Project Types**    | 11 rigid types with 22+ files                | Infinite flexibility with intelligent discovery |
+| **User Interaction** | Output sections with "Continue?"             | Collaborative decision facilitation             |
+| **Skill Adaptation** | One-size-fits-all                            | Adapts to beginner/intermediate/expert          |
+| **Decision Making**  | Late in process (Step 5)                     | Upfront and central focus                       |
+| **Output**           | Multiple documents including faux tech-specs | Single decision-focused architecture            |
+| **Time**             | Confusing and slow                           | 30-90 minutes depending on skill level          |
+| **Elicitation**      | Never used                                   | Integrated at decision points                   |
+
+---
+
+## Expected Inputs
+
+- **PRD** (Product Requirements Document) with:
+  - Functional Requirements
+  - Non-Functional Requirements
+  - Performance and compliance needs
+
+- **Epics** file with:
+  - User stories
+  - Acceptance criteria
+  - Dependencies
+
+- **UX Spec** (Optional but valuable) with:
+  - Interface designs and interaction patterns
+  - Accessibility requirements (WCAG levels)
+  - Animation and transition needs
+  - Platform-specific UI requirements
+  - Performance expectations for interactions
+
+---
+
+## Output Document
+
+A single `architecture.md` file containing:
+
+- Executive summary (2-3 sentences)
+- Project initialization command (if using starter template)
+- Decision summary table with verified versions and epic mapping
+- Complete project structure
+- Integration specifications
+- Consistency rules for AI agents
+
+---
+
+## How Novel Pattern Design Works
+
+Step 7 handles unique or complex patterns that need to be INVENTED:
+
+### 1. Detection
+
+The workflow analyzes the PRD for concepts that don't have standard solutions:
+
+- Novel interaction patterns (e.g., "swipe to match" when Tinder doesn't exist)
+- Complex multi-epic workflows (e.g., "viral invitation system")
+- Unique data relationships (e.g., "social graph" before Facebook)
+- New paradigms (e.g., "ephemeral messages" before Snapchat)
+
+### 2. Design Collaboration
+
+Instead of just picking technologies, the workflow helps DESIGN the solution:
+
+- Identifies the core problem to solve
+- Explores different approaches with the user
+- Documents how components interact
+- Creates sequence diagrams for complex flows
+- Uses elicitation to find innovative solutions
+
+### 3. Documentation
+
+Novel patterns become part of the architecture with:
+
+- Pattern name and purpose
+- Component interactions
+- Data flow diagrams
+- Which epics/stories are affected
+- Implementation guidance for agents
+
+### 4. Example
+
+```
+PRD: "Users can create 'circles' of friends with overlapping membership"
+↓
+Workflow detects: This is a novel social structure pattern
+↓
+Designs with user: Circle membership model, permission cascading, UI patterns
+↓
+Documents: "Circle Pattern" with component design and data flow
+↓
+All agents understand how to implement circle-related features consistently
+```
+
+---
+
+## How Implementation Patterns Work
+
+Step 8 prevents agent conflicts by defining patterns for consistency:
+
+### 1. The Core Principle
+
+> "Any time multiple agents might make the SAME decision DIFFERENTLY, that's a pattern to capture"
+
+The LLM asks: "What could an agent encounter where they'd have to guess?"
+
+### 2. Pattern Categories (principles, not prescriptions)
+
+- **Naming**: How things are named (APIs, database fields, files)
+- **Structure**: How things are organized (folders, modules, layers)
+- **Format**: How data is formatted (JSON structures, responses)
+- **Communication**: How components talk (events, messages, protocols)
+- **Lifecycle**: How states change (workflows, transitions)
+- **Location**: Where things go (URLs, paths, storage)
+- **Consistency**: Cross-cutting concerns (dates, errors, logs)
+
+### 3. LLM Intelligence
+
+- Uses the principle to identify patterns beyond the 7 categories
+- Figures out what specific patterns matter for chosen tech
+- Only asks about patterns that could cause conflicts
+- Skips obvious patterns that the tech choice determines
+
+### 4. Example
+
+```
+Tech chosen: REST API + PostgreSQL + React
+↓
+LLM identifies needs:
+- REST: URL structure, response format, status codes
+- PostgreSQL: table naming, column naming, FK patterns
+- React: component structure, state management, test location
+↓
+Facilitates each with user
+↓
+Documents as Implementation Patterns in architecture
+```
+
+---
+
+## How Starter Templates Work
+
+When the workflow detects a project type that has a starter template:
+
+1. **Discovery**: Searches for relevant starter templates based on PRD
+2. **Investigation**: Looks up current CLI options and defaults
+3. **Presentation**: Shows user what the starter provides
+4. **Integration**: Documents starter decisions as "PROVIDED BY STARTER"
+5. **Continuation**: Only asks about decisions NOT made by starter
+6. **Documentation**: Includes exact initialization command in architecture
+
+### Example Flow
+
+```
+PRD says: "Next.js web application with authentication"
+↓
+Workflow finds: create-next-app and create-t3-app
+↓
+User chooses: create-t3-app (includes auth setup)
+↓
+Starter provides: Next.js, TypeScript, tRPC, Prisma, NextAuth, Tailwind
+↓
+Workflow only asks about: Database choice, deployment target, additional services
+↓
+First story becomes: "npx create t3-app@latest my-app --trpc --nextauth --prisma"
+```
+
+---
+
+## Usage
+
+```bash
+# In your BMAD-enabled project
+workflow architecture
+```
+
+The AI agent will:
+
+1. Load your PRD and epics
+2. Identify critical decisions needed
+3. Facilitate discussion on each decision
+4. Generate a comprehensive architecture document
+5. Validate completeness
+
+---
+
+## Design Principles
+
+1. **Facilitation over Prescription** - Guide users to good decisions rather than imposing templates
+2. **Intelligence over Templates** - Use AI understanding rather than rigid structures
+3. **Decisions over Details** - Focus on what prevents agent conflicts, not implementation minutiae
+4. **Adaptation over Uniformity** - Meet users where they are while ensuring quality output
+5. **Collaboration over Output** - The conversation matters as much as the document
+
+---
+
+## For Developers
+
+This workflow assumes:
+
+- Single developer + AI agents (not teams)
+- Speed matters (decisions in minutes, not days)
+- AI agents need clear constraints to prevent conflicts
+- The architecture document is for agents, not humans
+
+---
+
+## Migration from architecture
+
+Projects using the old `architecture` workflow should:
+
+1. Complete any in-progress architecture work
+2. Use `architecture` for new projects
+3. The old workflow remains available but is deprecated
+
+---
+
+## Version History
+
+**1.3.2** - UX specification integration and fuzzy file matching
+
+- Added UX spec as optional input with fuzzy file matching
+- Updated workflow.yaml with input file references
+- Starter template selection now considers UX requirements
+- Added UX alignment validation to checklist
+- Instructions use variable references for flexible file names
+
+**1.3.1** - Workflow refinement and standardization
+
+- Added workflow status checking at start (Steps 0 and 0.5)
+- Added workflow status updating at end (Step 12)
+- Reorganized step numbering for clarity (removed fractional steps)
+- Enhanced with intent-based approach throughout
+- Improved cohesiveness across all workflow components
+
+**1.3.0** - Novel pattern design for unique architectures
+
+- Added novel pattern design (now Step 7, formerly Step 5.3)
+- Detects novel concepts in PRD that need architectural invention
+- Facilitates design collaboration with sequence diagrams
+- Uses elicitation for innovative approaches
+- Documents custom patterns for multi-epic consistency
+
+**1.2.0** - Implementation patterns for agent consistency
+
+- Added implementation patterns (now Step 8, formerly Step 5.5)
+- Created principle-based pattern-categories.csv (7 principles, not 118 prescriptions)
+- Core principle: "What could agents decide differently?"
+- LLM uses principle to identify patterns beyond the categories
+- Prevents agent conflicts through intelligent pattern discovery
+
+**1.1.0** - Enhanced with starter template discovery and version verification
+
+- Added intelligent starter template detection and integration (now Step 2)
+- Added dynamic version verification via web search
+- Starter decisions are documented as "PROVIDED BY STARTER"
+- First implementation story uses starter initialization command
+
+**1.0.0** - Initial release replacing architecture workflow
+
+---
+
+**Related Documentation:**
+
+- [Solutioning Workflows](./workflows-solutioning.md)
+- [Planning Workflows](./workflows-planning.md)
+- [Scale Adaptive System](./scale-adaptive-system.md)

.bmad/bmm/docs/workflow-document-project-reference.md

@@ -0,0 +1,487 @@
+# Document Project Workflow - Technical Reference
+
+**Module:** BMM (BMAD Method Module)
+**Type:** Action Workflow (Documentation Generator)
+
+---
+
+## Purpose
+
+Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development. Generates a master index and multiple documentation files tailored to project structure and type.
+
+**NEW in v1.2.0:** Context-safe architecture with scan levels, resumability, and write-as-you-go pattern to prevent context exhaustion.
+
+---
+
+## Key Features
+
+- **Multi-Project Type Support**: Handles web, backend, mobile, CLI, game, embedded, data, infra, library, desktop, and extension projects
+- **Multi-Part Detection**: Automatically detects and documents projects with separate client/server or multiple services
+- **Three Scan Levels** (NEW v1.2.0): Quick (2-5 min), Deep (10-30 min), Exhaustive (30-120 min)
+- **Resumability** (NEW v1.2.0): Interrupt and resume workflows without losing progress
+- **Write-as-you-go** (NEW v1.2.0): Documents written immediately to prevent context exhaustion
+- **Intelligent Batching** (NEW v1.2.0): Subfolder-based processing for deep/exhaustive scans
+- **Data-Driven Analysis**: Uses CSV-based project type detection and documentation requirements
+- **Comprehensive Scanning**: Analyzes APIs, data models, UI components, configuration, security patterns, and more
+- **Architecture Matching**: Matches projects to 170+ architecture templates from the solutioning registry
+- **Brownfield PRD Ready**: Generates documentation specifically designed for AI agents planning new features
+
+---
+
+## How to Invoke
+
+```bash
+workflow document-project
+```
+
+Or from BMAD CLI:
+
+```bash
+/bmad:bmm:workflows:document-project
+```
+
+---
+
+## Scan Levels (NEW in v1.2.0)
+
+Choose the right scan depth for your needs:
+
+### 1. Quick Scan (Default)
+
+**Duration:** 2-5 minutes
+**What it does:** Pattern-based analysis without reading source files
+**Reads:** Config files, package manifests, directory structure, README
+**Use when:**
+
+- You need a fast project overview
+- Initial understanding of project structure
+- Planning next steps before deeper analysis
+
+**Does NOT read:** Source code files (_.js, _.ts, _.py, _.go, etc.)
+
+### 2. Deep Scan
+
+**Duration:** 10-30 minutes
+**What it does:** Reads files in critical directories based on project type
+**Reads:** Files in critical paths defined by documentation requirements
+**Use when:**
+
+- Creating comprehensive documentation for brownfield PRD
+- Need detailed analysis of key areas
+- Want balance between depth and speed
+
+**Example:** For a web app, reads controllers/, models/, components/, but not every utility file
+
+### 3. Exhaustive Scan
+
+**Duration:** 30-120 minutes
+**What it does:** Reads ALL source files in project
+**Reads:** Every source file (excludes node_modules, dist, build, .git)
+**Use when:**
+
+- Complete project analysis needed
+- Migration planning requires full understanding
+- Detailed audit of entire codebase
+- Deep technical debt assessment
+
+**Note:** Deep-dive mode ALWAYS uses exhaustive scan (no choice)
+
+---
+
+## Resumability (NEW in v1.2.0)
+
+The workflow can be interrupted and resumed without losing progress:
+
+- **State Tracking:** Progress saved in `project-scan-report.json`
+- **Auto-Detection:** Workflow detects incomplete runs (<24 hours old)
+- **Resume Prompt:** Choose to resume or start fresh
+- **Step-by-Step:** Resume from exact step where interrupted
+- **Archiving:** Old state files automatically archived
+
+**Example Resume Flow:**
+
+```
+> workflow document-project
+
+I found an in-progress workflow state from 2025-10-11 14:32:15.
+
+Current Progress:
+- Mode: initial_scan
+- Scan Level: deep
+- Completed Steps: 5/12
+- Last Step: step_5
+
+Would you like to:
+1. Resume from where we left off - Continue from step 6
+2. Start fresh - Archive old state and begin new scan
+3. Cancel - Exit without changes
+
+Your choice [1/2/3]:
+```
+
+---
+
+## What It Does
+
+### Step-by-Step Process
+
+1. **Detects Project Structure** - Identifies if project is single-part or multi-part (client/server/etc.)
+2. **Classifies Project Type** - Matches against 12 project types (web, backend, mobile, etc.)
+3. **Discovers Documentation** - Finds existing README, CONTRIBUTING, ARCHITECTURE files
+4. **Analyzes Tech Stack** - Parses package files, identifies frameworks, versions, dependencies
+5. **Conditional Scanning** - Performs targeted analysis based on project type requirements:
+   - API routes and endpoints
+   - Database models and schemas
+   - State management patterns
+   - UI component libraries
+   - Configuration and security
+   - CI/CD and deployment configs
+6. **Generates Source Tree** - Creates annotated directory structure with critical paths
+7. **Extracts Dev Instructions** - Documents setup, build, run, and test commands
+8. **Creates Architecture Docs** - Generates detailed architecture using matched templates
+9. **Builds Master Index** - Creates comprehensive index.md as primary AI retrieval source
+10. **Validates Output** - Runs 140+ point checklist to ensure completeness
+
+### Output Files
+
+**Single-Part Projects:**
+
+- `index.md` - Master index
+- `project-overview.md` - Executive summary
+- `architecture.md` - Detailed architecture
+- `source-tree-analysis.md` - Annotated directory tree
+- `component-inventory.md` - Component catalog (if applicable)
+- `development-guide.md` - Local dev instructions
+- `api-contracts.md` - API documentation (if applicable)
+- `data-models.md` - Database schema (if applicable)
+- `deployment-guide.md` - Deployment process (optional)
+- `contribution-guide.md` - Contributing guidelines (optional)
+- `project-scan-report.json` - State file for resumability (NEW v1.2.0)
+
+**Multi-Part Projects (e.g., client + server):**
+
+- `index.md` - Master index with part navigation
+- `project-overview.md` - Multi-part summary
+- `architecture-{part_id}.md` - Per-part architecture docs
+- `source-tree-analysis.md` - Full tree with part annotations
+- `component-inventory-{part_id}.md` - Per-part components
+- `development-guide-{part_id}.md` - Per-part dev guides
+- `integration-architecture.md` - How parts communicate
+- `project-parts.json` - Machine-readable metadata
+- `project-scan-report.json` - State file for resumability (NEW v1.2.0)
+- Additional conditional files per part (API, data models, etc.)
+
+---
+
+## Data Files
+
+The workflow uses a single comprehensive CSV file:
+
+**documentation-requirements.csv** - Complete project analysis guide
+
+- Location: `/.bmad/bmm/workflows/document-project/documentation-requirements.csv`
+- 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded)
+- 24 columns combining:
+  - **Detection columns**: `project_type_id`, `key_file_patterns` (identifies project type from codebase)
+  - **Requirement columns**: `requires_api_scan`, `requires_data_models`, `requires_ui_components`, etc.
+  - **Pattern columns**: `critical_directories`, `test_file_patterns`, `config_patterns`, etc.
+- Self-contained: All project detection AND scanning requirements in one file
+- Architecture patterns inferred from tech stack (no external registry needed)
+
+---
+
+## Use Cases
+
+### Primary Use Case: Brownfield PRD Creation
+
+After running this workflow, use the generated `index.md` as input to brownfield PRD workflows:
+
+```
+User: "I want to add a new dashboard feature"
+PRD Workflow: Loads docs/index.md
+→ Understands existing architecture
+→ Identifies reusable components
+→ Plans integration with existing APIs
+→ Creates contextual PRD with epics and stories
+```
+
+### Other Use Cases
+
+- **Onboarding New Developers** - Comprehensive project documentation
+- **Architecture Review** - Structured analysis of existing system
+- **Technical Debt Assessment** - Identify patterns and anti-patterns
+- **Migration Planning** - Understand current state before refactoring
+
+---
+
+## Requirements
+
+### Recommended Inputs (Optional)
+
+- Project root directory (defaults to current directory)
+- README.md or similar docs (auto-discovered if present)
+- User guidance on key areas to focus (workflow will ask)
+
+### Tools Used
+
+- File system scanning (Glob, Read, Grep)
+- Code analysis
+- Git repository analysis (optional)
+
+---
+
+## Configuration
+
+### Default Output Location
+
+Files are saved to: `{output_folder}` (from config.yaml)
+
+Default: `/docs/` folder in project root
+
+### Customization
+
+- Modify `documentation-requirements.csv` to adjust scanning patterns for project types
+- Add new project types to `project-types.csv`
+- Add new architecture templates to `registry.csv`
+
+---
+
+## Example: Multi-Part Web App
+
+**Input:**
+
+```
+my-app/
+├── client/     # React frontend
+├── server/     # Express backend
+└── README.md
+```
+
+**Detection Result:**
+
+- Repository Type: Monorepo
+- Part 1: client (web/React)
+- Part 2: server (backend/Express)
+
+**Output (10+ files):**
+
+```
+docs/
+├── index.md
+├── project-overview.md
+├── architecture-client.md
+├── architecture-server.md
+├── source-tree-analysis.md
+├── component-inventory-client.md
+├── development-guide-client.md
+├── development-guide-server.md
+├── api-contracts-server.md
+├── data-models-server.md
+├── integration-architecture.md
+└── project-parts.json
+```
+
+---
+
+## Example: Simple CLI Tool
+
+**Input:**
+
+```
+hello-cli/
+├── main.go
+├── go.mod
+└── README.md
+```
+
+**Detection Result:**
+
+- Repository Type: Monolith
+- Part 1: main (cli/Go)
+
+**Output (4 files):**
+
+```
+docs/
+├── index.md
+├── project-overview.md
+├── architecture.md
+└── source-tree-analysis.md
+```
+
+---
+
+## Deep-Dive Mode
+
+### What is Deep-Dive Mode?
+
+When you run the workflow on a project that already has documentation, you'll be offered a choice:
+
+1. **Rescan entire project** - Update all documentation with latest changes
+2. **Deep-dive into specific area** - Generate EXHAUSTIVE documentation for a particular feature/module/folder
+3. **Cancel** - Keep existing documentation
+
+Deep-dive mode performs **comprehensive, file-by-file analysis** of a specific area, reading EVERY file completely and documenting:
+
+- All exports with complete signatures
+- All imports and dependencies
+- Dependency graphs and data flow
+- Code patterns and implementations
+- Testing coverage and strategies
+- Integration points
+- Reuse opportunities
+
+### When to Use Deep-Dive Mode
+
+- **Before implementing a feature** - Deep-dive the area you'll be modifying
+- **During architecture review** - Deep-dive complex modules
+- **For code understanding** - Deep-dive unfamiliar parts of codebase
+- **When creating PRDs** - Deep-dive areas affected by new features
+
+### Deep-Dive Process
+
+1. Workflow detects existing `index.md`
+2. Offers deep-dive option
+3. Suggests areas based on project structure:
+   - API route groups
+   - Feature modules
+   - UI component areas
+   - Services/business logic
+4. You select area or specify custom path
+5. Workflow reads EVERY file in that area
+6. Generates `deep-dive-{area-name}.md` with complete analysis
+7. Updates `index.md` with link to deep-dive doc
+8. Offers to deep-dive another area or finish
+
+### Deep-Dive Output Example
+
+**docs/deep-dive-dashboard-feature.md:**
+
+- Complete file inventory (47 files analyzed)
+- Every export with signatures
+- Dependency graph
+- Data flow analysis
+- Integration points
+- Testing coverage
+- Related code references
+- Implementation guidance
+- ~3,000 LOC documented in detail
+
+### Incremental Deep-Diving
+
+You can deep-dive multiple areas over time:
+
+- First run: Scan entire project → generates index.md
+- Second run: Deep-dive dashboard feature
+- Third run: Deep-dive API layer
+- Fourth run: Deep-dive authentication system
+
+All deep-dive docs are linked from the master index.
+
+---
+
+## Validation
+
+The workflow includes a comprehensive 160+ point checklist covering:
+
+- Project detection accuracy
+- Technology stack completeness
+- Codebase scanning thoroughness
+- Architecture documentation quality
+- Multi-part handling (if applicable)
+- Brownfield PRD readiness
+- Deep-dive completeness (if applicable)
+
+---
+
+## Next Steps After Completion
+
+1. **Review** `docs/index.md` - Your master documentation index
+2. **Validate** - Check generated docs for accuracy
+3. **Use for PRD** - Point brownfield PRD workflow to index.md
+4. **Maintain** - Re-run workflow when architecture changes significantly
+
+---
+
+## File Structure
+
+```
+document-project/
+├── workflow.yaml                    # Workflow configuration
+├── instructions.md                  # Step-by-step workflow logic
+├── checklist.md                     # Validation criteria
+├── documentation-requirements.csv   # Project type scanning patterns
+├── templates/                       # Output templates
+│   ├── index-template.md
+│   ├── project-overview-template.md
+│   └── source-tree-template.md
+└── README.md                        # This file
+```
+
+---
+
+## Troubleshooting
+
+**Issue: Project type not detected correctly**
+
+- Solution: Workflow will ask for confirmation; manually select correct type
+
+**Issue: Missing critical information**
+
+- Solution: Provide additional context when prompted; re-run specific analysis steps
+
+**Issue: Multi-part detection missed a part**
+
+- Solution: When asked to confirm parts, specify the missing part and its path
+
+**Issue: Architecture template doesn't match well**
+
+- Solution: Check registry.csv; may need to add new template or adjust matching criteria
+
+---
+
+## Architecture Improvements in v1.2.0
+
+### Context-Safe Design
+
+The workflow now uses a write-as-you-go architecture:
+
+- Documents written immediately to disk (not accumulated in memory)
+- Detailed findings purged after writing (only summaries kept)
+- State tracking enables resumption from any step
+- Batching strategy prevents context exhaustion on large projects
+
+### Batching Strategy
+
+For deep/exhaustive scans:
+
+- Process ONE subfolder at a time
+- Read files → Extract info → Write output → Validate → Purge context
+- Primary concern is file SIZE (not count)
+- Track batches in state file for resumability
+
+### State File Format
+
+Optimized JSON (no pretty-printing):
+
+```json
+{
+  "workflow_version": "1.2.0",
+  "timestamps": {...},
+  "mode": "initial_scan",
+  "scan_level": "deep",
+  "completed_steps": [...],
+  "current_step": "step_6",
+  "findings": {"summary": "only"},
+  "outputs_generated": [...],
+  "resume_instructions": "..."
+}
+```
+
+---
+
+**Related Documentation:**
+
+- [Brownfield Development Guide](./brownfield-guide.md)
+- [Implementation Workflows](./workflows-implementation.md)
+- [Scale Adaptive System](./scale-adaptive-system.md)

.bmad/bmm/docs/workflows-analysis.md

@@ -0,0 +1,370 @@
+# BMM Analysis Workflows (Phase 1)
+
+**Reading Time:** ~7 minutes
+
+## Overview
+
+Phase 1 (Analysis) workflows are **optional** exploration and discovery tools that help validate ideas, understand markets, and generate strategic context before planning begins.
+
+**Key principle:** Analysis workflows help you think strategically before committing to implementation. Skip them if your requirements are already clear.
+
+**When to use:** Starting new projects, exploring opportunities, validating market fit, generating ideas, understanding problem spaces.
+
+**When to skip:** Continuing existing projects with clear requirements, well-defined features with known solutions, strict constraints where discovery is complete.
+
+---
+
+## Phase 1 Analysis Workflow Map
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
+graph TB
+    subgraph Discovery["<b>DISCOVERY & IDEATION (Optional)</b>"]
+        direction LR
+        BrainstormProject["<b>Analyst: brainstorm-project</b><br/>Multi-track solution exploration"]
+        BrainstormGame["<b>Analyst: brainstorm-game</b><br/>Game concept generation"]
+    end
+
+    subgraph Research["<b>RESEARCH & VALIDATION (Optional)</b>"]
+        direction TB
+        ResearchWF["<b>Analyst: research</b><br/>• market (TAM/SAM/SOM)<br/>• technical (framework evaluation)<br/>• competitive (landscape)<br/>• user (personas, JTBD)<br/>• domain (industry analysis)<br/>• deep_prompt (AI research)"]
+    end
+
+    subgraph Strategy["<b>STRATEGIC CAPTURE (Recommended for Greenfield)</b>"]
+        direction LR
+        ProductBrief["<b>Analyst: product-brief</b><br/>Product vision + strategy<br/>(Interactive or YOLO mode)"]
+        GameBrief["<b>Game Designer: game-brief</b><br/>Game vision capture<br/>(Interactive or YOLO mode)"]
+    end
+
+    Discovery -.->|Software| ProductBrief
+    Discovery -.->|Games| GameBrief
+    Discovery -.->|Validate ideas| Research
+    Research -.->|Inform brief| ProductBrief
+    Research -.->|Inform brief| GameBrief
+    ProductBrief --> Phase2["<b>Phase 2: prd workflow</b>"]
+    GameBrief --> Phase2Game["<b>Phase 2: gdd workflow</b>"]
+    Research -.->|Can feed directly| Phase2
+
+    style Discovery fill:#e1f5fe,stroke:#01579b,stroke-width:3px,color:#000
+    style Research fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
+    style Strategy fill:#f3e5f5,stroke:#4a148c,stroke-width:3px,color:#000
+    style Phase2 fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px,color:#000
+    style Phase2Game fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px,color:#000
+
+    style BrainstormProject fill:#81d4fa,stroke:#0277bd,stroke-width:2px,color:#000
+    style BrainstormGame fill:#81d4fa,stroke:#0277bd,stroke-width:2px,color:#000
+    style ResearchWF fill:#fff59d,stroke:#f57f17,stroke-width:2px,color:#000
+    style ProductBrief fill:#ce93d8,stroke:#6a1b9a,stroke-width:2px,color:#000
+    style GameBrief fill:#ce93d8,stroke:#6a1b9a,stroke-width:2px,color:#000
+```
+
+---
+
+## Quick Reference
+
+| Workflow               | Agent         | Required    | Purpose                                                        | Output                       |
+| ---------------------- | ------------- | ----------- | -------------------------------------------------------------- | ---------------------------- |
+| **brainstorm-project** | Analyst       | No          | Explore solution approaches and architectures                  | Solution options + rationale |
+| **brainstorm-game**    | Analyst       | No          | Generate game concepts using creative techniques               | Game concepts + evaluation   |
+| **research**           | Analyst       | No          | Multi-type research (market/technical/competitive/user/domain) | Research reports             |
+| **product-brief**      | Analyst       | Recommended | Define product vision and strategy (interactive)               | Product Brief document       |
+| **game-brief**         | Game Designer | Recommended | Capture game vision before GDD (interactive)                   | Game Brief document          |
+
+---
+
+## Workflow Descriptions
+
+### brainstorm-project
+
+**Purpose:** Generate multiple solution approaches through parallel ideation tracks (architecture, UX, integration, value).
+
+**Agent:** Analyst
+
+**When to Use:**
+
+- Unclear technical approach with business objectives
+- Multiple solution paths need evaluation
+- Hidden assumptions need discovery
+- Innovation beyond obvious solutions
+
+**Key Outputs:**
+
+- Architecture proposals with trade-off analysis
+- Value framework (prioritized features)
+- Risk analysis (dependencies, challenges)
+- Strategic recommendation with rationale
+
+**Example:** "We need a customer dashboard" → Options: Monolith SSR (faster), Microservices SPA (scalable), Hybrid (balanced) with recommendation.
+
+---
+
+### brainstorm-game
+
+**Purpose:** Generate game concepts through systematic creative exploration using five brainstorming techniques.
+
+**Agent:** Analyst
+
+**When to Use:**
+
+- Generating original game concepts
+- Exploring variations on themes
+- Breaking creative blocks
+- Validating game ideas against constraints
+
+**Techniques Used:**
+
+- SCAMPER (systematic modification)
+- Mind Mapping (hierarchical exploration)
+- Lotus Blossom (radial expansion)
+- Six Thinking Hats (multi-perspective)
+- Random Word Association (lateral thinking)
+
+**Key Outputs:**
+
+- Method-specific artifacts (5 separate documents)
+- Consolidated concept document with feasibility
+- Design pillar alignment matrix
+
+**Example:** "Roguelike with psychological themes" → Emotions as characters, inner demons as enemies, therapy sessions as rest points, deck composition affects narrative.
+
+---
+
+### research
+
+**Purpose:** Comprehensive multi-type research system consolidating market, technical, competitive, user, and domain analysis.
+
+**Agent:** Analyst
+
+**Research Types:**
+
+| Type            | Purpose                                                | Use When                            |
+| --------------- | ------------------------------------------------------ | ----------------------------------- |
+| **market**      | TAM/SAM/SOM, competitive analysis                      | Need market viability validation    |
+| **technical**   | Technology evaluation, ADRs                            | Choosing frameworks/platforms       |
+| **competitive** | Deep competitor analysis                               | Understanding competitive landscape |
+| **user**        | Customer insights, personas, JTBD                      | Need user understanding             |
+| **domain**      | Industry deep dives, trends                            | Understanding domain/industry       |
+| **deep_prompt** | Generate AI research prompts (ChatGPT, Claude, Gemini) | Need deeper AI-assisted research    |
+
+**Key Features:**
+
+- Real-time web research
+- Multiple analytical frameworks (Porter's Five Forces, SWOT, Technology Adoption Lifecycle)
+- Platform-specific optimization for deep_prompt type
+- Configurable research depth (quick/standard/comprehensive)
+
+**Example (market):** "SaaS project management tool" → TAM $50B, SAM $5B, SOM $50M, top competitors (Asana, Monday), positioning recommendation.
+
+---
+
+### product-brief
+
+**Purpose:** Interactive product brief creation that guides strategic product vision definition.
+
+**Agent:** Analyst
+
+**When to Use:**
+
+- Starting new product/major feature initiative
+- Aligning stakeholders before detailed planning
+- Transitioning from exploration to strategy
+- Need executive-level product documentation
+
+**Modes:**
+
+- **Interactive Mode** (Recommended): Step-by-step collaborative development with probing questions
+- **YOLO Mode**: AI generates complete draft from context, then iterative refinement
+
+**Key Outputs:**
+
+- Executive summary
+- Problem statement with evidence
+- Proposed solution and differentiators
+- Target users (segmented)
+- MVP scope (ruthlessly defined)
+- Financial impact and ROI
+- Strategic alignment
+- Risks and open questions
+
+**Integration:** Feeds directly into PRD workflow (Phase 2).
+
+---
+
+### game-brief
+
+**Purpose:** Lightweight interactive brainstorming session capturing game vision before Game Design Document.
+
+**Agent:** Game Designer
+
+**When to Use:**
+
+- Starting new game project
+- Exploring game ideas before committing
+- Pitching concepts to team/stakeholders
+- Validating market fit and feasibility
+
+**Game Brief vs GDD:**
+
+| Aspect       | Game Brief         | GDD                       |
+| ------------ | ------------------ | ------------------------- |
+| Purpose      | Validate concept   | Design for implementation |
+| Detail Level | High-level vision  | Detailed specs            |
+| Format       | Conversational     | Structured                |
+| Output       | Concise vision doc | Comprehensive design      |
+
+**Key Outputs:**
+
+- Game vision (concept, pitch)
+- Target market and positioning
+- Core gameplay pillars
+- Scope and constraints
+- Reference framework
+- Risk assessment
+- Success criteria
+
+**Integration:** Feeds into GDD workflow (Phase 2).
+
+---
+
+## Decision Guide
+
+### Starting a Software Project
+
+```
+brainstorm-project (if unclear) → research (market/technical) → product-brief → Phase 2 (prd)
+```
+
+### Starting a Game Project
+
+```
+brainstorm-game (if generating concepts) → research (market/competitive) → game-brief → Phase 2 (gdd)
+```
+
+### Validating an Idea
+
+```
+research (market type) → product-brief or game-brief → Phase 2
+```
+
+### Technical Decision Only
+
+```
+research (technical type) → Use findings in Phase 3 (architecture)
+```
+
+### Understanding Market
+
+```
+research (market/competitive type) → product-brief → Phase 2
+```
+
+---
+
+## Integration with Phase 2 (Planning)
+
+Analysis outputs feed directly into Planning:
+
+| Analysis Output             | Planning Input             |
+| --------------------------- | -------------------------- |
+| product-brief.md            | **prd** workflow           |
+| game-brief.md               | **gdd** workflow           |
+| market-research.md          | **prd** context            |
+| technical-research.md       | **architecture** (Phase 3) |
+| competitive-intelligence.md | **prd** positioning        |
+
+Planning workflows automatically load these documents if they exist in the output folder.
+
+---
+
+## Best Practices
+
+### 1. Don't Over-Invest in Analysis
+
+Analysis is optional. If requirements are clear, skip to Phase 2 (Planning).
+
+### 2. Iterate Between Workflows
+
+Common pattern: brainstorm → research (validate) → brief (synthesize)
+
+### 3. Document Assumptions
+
+Analysis surfaces and validates assumptions. Document them explicitly for planning to challenge.
+
+### 4. Keep It Strategic
+
+Focus on "what" and "why", not "how". Leave implementation for Planning and Solutioning.
+
+### 5. Involve Stakeholders
+
+Use analysis workflows to align stakeholders before committing to detailed planning.
+
+---
+
+## Common Patterns
+
+### Greenfield Software (Full Analysis)
+
+```
+1. brainstorm-project - explore approaches
+2. research (market) - validate viability
+3. product-brief - capture strategic vision
+4. → Phase 2: prd
+```
+
+### Greenfield Game (Full Analysis)
+
+```
+1. brainstorm-game - generate concepts
+2. research (competitive) - understand landscape
+3. game-brief - capture vision
+4. → Phase 2: gdd
+```
+
+### Skip Analysis (Clear Requirements)
+
+```
+→ Phase 2: prd or tech-spec directly
+```
+
+### Technical Research Only
+
+```
+1. research (technical) - evaluate technologies
+2. → Phase 3: architecture (use findings in ADRs)
+```
+
+---
+
+## Related Documentation
+
+- [Phase 2: Planning Workflows](./workflows-planning.md) - Next phase
+- [Phase 3: Solutioning Workflows](./workflows-solutioning.md)
+- [Phase 4: Implementation Workflows](./workflows-implementation.md)
+- [Scale Adaptive System](./scale-adaptive-system.md) - Understanding project complexity
+- [Agents Guide](./agents-guide.md) - Complete agent reference
+
+---
+
+## Troubleshooting
+
+**Q: Do I need to run all analysis workflows?**
+A: No! Analysis is entirely optional. Use only workflows that help you think through your problem.
+
+**Q: Which workflow should I start with?**
+A: If unsure, start with `research` (market type) to validate viability, then move to `product-brief` or `game-brief`.
+
+**Q: Can I skip straight to Planning?**
+A: Yes! If you know what you're building and why, skip Phase 1 entirely and start with Phase 2 (prd/gdd/tech-spec).
+
+**Q: How long should Analysis take?**
+A: Typically hours to 1-2 days. If taking longer, you may be over-analyzing. Move to Planning.
+
+**Q: What if I discover problems during Analysis?**
+A: That's the point! Analysis helps you fail fast and pivot before heavy planning investment.
+
+**Q: Should brownfield projects do Analysis?**
+A: Usually no. Start with `document-project` (Phase 0), then skip to Planning (Phase 2).
+
+---
+
+_Phase 1 Analysis - Optional strategic thinking before commitment._