chore: fix bundle urls

* chore: github pages for web bundle

* docs: updated Bundle distribution setup

* chore: addressed PR comments

---------

Co-authored-by: Murat Ozcan <murat@mac.lan>

.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/files-manifest.csv

@@ -1,97 +1,97 @@
 type,name,module,path,hash
-"csv","agent-manifest","_cfg","bmad/_cfg/agent-manifest.csv","fec768b507f89fad6bbfa4dca4a4a27e357f2e192f0625e96cd015897022b208"
-"csv","task-manifest","_cfg","bmad/_cfg/task-manifest.csv","028b2457714722e7313475c357ad1d519bb4c17e5f77fe045345278d6f03e991"
-"csv","workflow-manifest","_cfg","bmad/_cfg/workflow-manifest.csv","b449d807611a9988fe21d31ddfa763b224088e3699c606b4868780e7448bc8d9"
-"yaml","manifest","_cfg","bmad/_cfg/manifest.yaml","c887476778fc7e1fb031f583831227971d0e084dfbd118bf8aaac0805c1fc811"
+"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","e486fc0b22bfe2c85b08fac0fc0aacdb43dd41498727bf39de30e570abe716b9"
-"md","agent-command-patterns","bmb","bmad/bmb/workflows/create-agent/agent-command-patterns.md","8c5972a5aad50f7f6e39ed14edca9c609a7da8be21edf6f872f5ce8481e11738"
-"md","agent-types","bmb","bmad/bmb/workflows/create-agent/agent-types.md","a9429475767b6db4bb74fb27e328a8fdb3e8e7176edb2920ae3e0106d85e9d83"
-"md","bmad-builder","bmb","bmad/bmb/agents/bmad-builder.md","7a020a7cb2231d96588ee68080317b6e41fb11621c6059495ed25d3c689511fb"
+"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","3a9cf6f7d38152d6e5e49179fec8b6056e97db0f34185ea5c466165cb931cd55"
-"md","checklist","bmb","bmad/bmb/workflows/convert-legacy/checklist.md","9a376b87aa0af902a0acd2d5c183ae641a5b6e1cd3ddd2a2dd3a1734c86d1ce5"
-"md","checklist","bmb","bmad/bmb/workflows/create-agent/checklist.md","837667f2bd601833568b327b961ba0dd363ba9a0d240625eebc9d1a9685ecbd8"
-"md","checklist","bmb","bmad/bmb/workflows/create-module/checklist.md","72b9440ba720d96fa1cab50d1242495a5b7c540e7ab93a5a055c46c36d142ce1"
-"md","checklist","bmb","bmad/bmb/workflows/create-workflow/checklist.md","78325ed31532c0059a3f647f7f4cda7702919a9ef43634afa419d3fa30ee2a0c"
+"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","e9878537ef45be158ca222d21311247a9bf0502cdabcb14dd827871d6488cf0e"
-"md","checklist","bmb","bmad/bmb/workflows/edit-module/checklist.md","c0f599a80efb36ee184bcc5c94c903bbac31f335830a493ec9b8f47157ae5568"
+"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","a31c169af274fbf8c72a60459a5855d9c5dfffcf51d2ec39370d54670471d32c"
-"md","instructions","bmb","bmad/bmb/workflows/convert-legacy/instructions.md","91c442227f8fa631ce9d6431eaf2cfd5a37a608c0df360125de23a428e031cca"
-"md","instructions","bmb","bmad/bmb/workflows/create-agent/instructions.md","77c2c7177721fc4b56277d8d3aa2d527ed3dbfee1a6f5ea3f08d63b66260ca2d"
-"md","instructions","bmb","bmad/bmb/workflows/create-module/instructions.md","010cb47095811cf4968d98712749cb1fee5021a52621d0aa0f35ef3758ed2304"
-"md","instructions","bmb","bmad/bmb/workflows/create-workflow/instructions.md","6f81e2b18d5244864f7f194bd8dc8d99f7113bc54a08053d340cb6170a81bffb"
-"md","instructions","bmb","bmad/bmb/workflows/create-workflow/workflow-template/instructions.md","daf3d312e5a60d7c4cbc308014e3c69eeeddd70bd41bd139d328318da1e3ecb2"
-"md","instructions","bmb","bmad/bmb/workflows/edit-agent/instructions.md","0bc81290f33d1101b23ca29cb9f6537e7743113857c113c5bb5a36318d055be8"
-"md","instructions","bmb","bmad/bmb/workflows/edit-module/instructions.md","e5e68479df9e521d157acc1bbf370dbf3f70f1ba8b067b1cec3c53fbf20f02ce"
-"md","instructions","bmb","bmad/bmb/workflows/edit-workflow/instructions.md","a00ff928cf0425b3a88d3ee592e7e09994529b777caf476364cf69a3c5aee866"
-"md","instructions","bmb","bmad/bmb/workflows/module-brief/instructions.md","e2275373850ea0745f396ad0c3aa192f06081b52d98777650f6b645333b62926"
-"md","instructions","bmb","bmad/bmb/workflows/redoc/instructions.md","21dd93b64455f8dd475b508ae9f1076d7e179e99fb6f197476071706b78e3592"
-"md","module-structure","bmb","bmad/bmb/workflows/create-module/module-structure.md","3bdf1d55eec2fccc2c9f44a08f4e0dc489ce47396ff39fa59a82836a911faa54"
+"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","2c11bcf8d974e4f0e0e03f948df42097592751a3aeb9c443fa6cecf05819d49b"
-"md","README","bmb","bmad/bmb/workflows/create-agent/README.md","f4da5c16fb4847252b09b82d70f027ae08e78b75bb101601f2ca3d2c2c884736"
-"md","README","bmb","bmad/bmb/workflows/create-module/README.md","539d3d12d78efcbe0b8b1a21a3916655b8a7356f763844aa6c735b7e8e8bb7e4"
-"md","README","bmb","bmad/bmb/workflows/create-workflow/README.md","18b334dfb3bd6dd413a79e763a4f1f8a6f0fc206a66069ba0923de04d7a64872"
+"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","807df3d74f673399042331e4c5034466d8f146c4b2cdb39fe63ccde6f4509843"
+"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","d52ab0914ec83b2b97fded6b0b278f55fe82bb1ac78cbe202c03cf761fcce8ea"
-"md","README","bmb","bmad/bmb/workflows/redoc/README.md","a1b7e02427cf252bca69a8a1ee0f554844a6a01b5d568d74f494c71542056173"
+"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","d1f5f291de1dad996525e5be5cd360462f4c39657470adedbc2fd3a38fe963e9"
+"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","0cdab81189d40d0d50852c75011a888f89ca0fcf75619f1da1e02dab5dccdbc6"
-"yaml","install-config","bmb","bmad/bmb/workflows/create-module/installer-templates/install-config.yaml","f20caf43009df9955b5fa0fa333851bf8b860568c05707d60ed295179c8abfde"
-"yaml","workflow","bmb","bmad/bmb/workflows/audit-workflow/workflow.yaml","24a82e15c41995c938c7f338254e5f414cfa8b9b679f3325e8d18435c992ab1c"
-"yaml","workflow","bmb","bmad/bmb/workflows/convert-legacy/workflow.yaml","dd1d26124e59b73837f07d3663ca390484cfab0b4a7ffbee778c29bcdaaec097"
-"yaml","workflow","bmb","bmad/bmb/workflows/create-agent/workflow.yaml","4b5c577c470c34d7e85a8881881e7e42a42758dc3fc12ece896752dfbd324eef"
-"yaml","workflow","bmb","bmad/bmb/workflows/create-module/workflow.yaml","da632eac14f6323bb6e4d6821dcc4d266db9ffd52bb43ba7cb2e60ec0c9ae4c6"
-"yaml","workflow","bmb","bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml","2eeb8d1724779956f8e89fda8fa850c3fb1d2b8c6eefecd1b5a4d5f9f58adb91"
-"yaml","workflow","bmb","bmad/bmb/workflows/create-workflow/workflow.yaml","79bce9abed20f239a6d0f97a3577c6b76c05b79696b38183569f1204b1140adb"
-"yaml","workflow","bmb","bmad/bmb/workflows/edit-agent/workflow.yaml","ab77c603f7bbdf8a8f38ce7e82f6cae40ad9ebcbdf0b590c18f5dece1e8685cd"
-"yaml","workflow","bmb","bmad/bmb/workflows/edit-module/workflow.yaml","ee4cd0a932381b67866bd049a8b2ed5b8fde57d48dd488f2317deb649f88cd53"
-"yaml","workflow","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml","9d8e33a8312a5e7cd10de014fb9251c7805be5fa23c7b4b813445b0daafc223c"
-"yaml","workflow","bmb","bmad/bmb/workflows/module-brief/workflow.yaml","5e96bb7f5bf32817513225b1572f7bd93dbc724b166aa3af977818a6ba7bcaf0"
-"yaml","workflow","bmb","bmad/bmb/workflows/redoc/workflow.yaml","0bef37556f6478ed886845c9811ecc97f41a240d3acd6c2e97ea1e2914f3abf7"
+"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","83cf960dda10f42f2dabf16097435a2f3c802997f681d914e442792a9fab1966"
-"md","analyst","bmm","bmad/bmm/agents/analyst.md","df273f9490365a8f263c13df57aa2664e078d3c9bf74c2a564e7fc44278c2fe0"
-"md","architect","bmm","bmad/bmm/agents/architect.md","b6e20637e64cb7678b619d2b1abe82165e67c0ab922cb9baa2af2dea66f27d60"
+"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","c7149871527925ba43036e81641715294050137cba0dc6a16fd5684dd72bab34"
-"md","AUDIT-REPORT","bmm","bmad/bmm/workflows/4-implementation/dev-story/AUDIT-REPORT.md","809706c392b01e43e2dd43026c803733002bf8d8a71ba9cd4ace26cd4787fce5"
+"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","32c547c5c137b466bd642e65fb2523f9663c1938b034cfa31207aa0192d60216"
+"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/narrative/checklist.md","9bcfa41212cd74869199dba1a7d9cd5691e2bbc49e6b74b11e51c32955477524"
-"md","checklist","bmm","bmad/bmm/workflows/2-plan-workflows/prd/checklist.md","3603c689167830ff9b8bd01982fad86f5882390e490982071fa5b7eccd5e42c0"
-"md","checklist","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/checklist.md","d4f21d97e63b8bdb8e33938467a5cb3fa4388527b6d2d65ed45915b2a498a4ef"
+"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","33b2acfcc8fdbab18637218f6c6d16055e0004f0d818f993b0a6aeafac1f6112"
+"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","5e90dc12e01ba5f00301a6724fdac5585596fd6dfc670913938e9e92cdca133a"
+"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","89c90d004e0649624a533d09604384c297b2891847c87cf1dcb358e9c8d0d723"
+"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"
@@ -109,80 +109,78 @@ type,name,module,path,hash
 "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","d469f26d85f6b7e02a7a0198a294ccaa7f5d19cb1db6ca5cc4ddc64971fe2278"
-"md","documentation-standards","bmm","bmad/bmm/workflows/techdoc/documentation-standards.md","3cd7cd52b26a82370d570ebc489a04a523d39ffa6cd0d82e08da2666c1921ead"
+"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","ffdb8746f5b3c2f3393b5f733281b3719bd279ecccc3833b5340a74029460939"
-"md","epics-template","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md","01b8a6e6febdb6c96848ce3fee71458d31f11910e90bd7e01b7ed3200b88644d"
-"md","epics-template","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md","c467d75bd642b433a1de5d7fdd621fd7a13d1d0e12982ed0da7b0fedee595c9d"
+"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","2ce2ce13e581defecd192f5383e7ff079f8dfd25df45759a1e77046285435fb7"
+"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","7d2f98c3d469a8530838205da667c8a98ab6304457008e0e6d3f6b46b6f82225"
+"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","990e98596dc82f5e6c044ea8a833638c8cde46b1a10b1eb4fa8df347568bd881"
-"md","instructions","bmm","bmad/bmm/workflows/1-analysis/domain-research/instructions.md","e5e5710fd9217f9b535fe8f7ae7b85384a2e441f2b8b6631827c840e9421ea6c"
-"md","instructions","bmm","bmad/bmm/workflows/1-analysis/product-brief/instructions.md","8ed82a89a9e7d43bbf7ea81dd1b1113242e0e8c0da14938a86bd49d79595085f"
-"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md","e82c1e4ef30dd7c83904aa3593375bdb19ece52855468b3c184314b9a952a8dc"
-"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md","093ee87c7eed6ac4bd5299924d923a88e4476f9e96c1165cf5b818f6947bf0b3"
-"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/prd/instructions.md","716a1469bd9cbc8dc566cb47a790df5271b00c9fc33737d9b82a419742367570"
-"md","instructions","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md","7603e62c7f03e4b471f15814be89e5ac69d8f26f09c13110b5e579bb3b64f8e2"
-"md","instructions","bmm","bmad/bmm/workflows/3-solutioning/architecture/instructions.md","2814d324cee08f49f7f67546262252cc20a80c34e02abe288b0695f53b62daa6"
-"md","instructions","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md","26560fb893c6b681477443bc74f1d75c4bd10fd20480f8f624d32e149ee02cc3"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/code-review/instructions.md","9759c284b5fbc4675abcbf96983b49e513d58ab26deaca499d74a133ee550b59"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/correct-course/instructions.md","5e8a3aa9b83166b3d5832ac9f5c8e6944328c26a6e4a399dce56916993b1709f"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/create-story/instructions.md","a6f4f6cac9cf36d5ed0e10193512e690915330bcd761e403cc7a460d19449bdd"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/dev-story/instructions.md","2571d592d5e69ea470840013c6e6e9a06b7dd3361782a202503aa1c21b6c0720"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/instructions.md","4310c308e4f43d45de813dc76ff187faad952559e5e6fd26565ce20804b0755c"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/retrospective/instructions.md","b8cd4f18100ade53fc493883d1439653cb73bef63379072fc57331cb359bd517"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/instructions.md","4410cf772bd445f165a8971b0372dea777b5d192968363be46a56863211eef63"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-context/instructions.md","da614cf99bfa1a2c76e1731345fe163fa1095f15c05ab5fedd1390dd0cacdc98"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-done/instructions.md","00e8b4b817b11a8bb1b7a3746fc9991c60acee1551c9de005c423ef9e670272f"
-"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-ready/instructions.md","da51e57c470e7561d61660260d0e5661dd3a269a772ae180910abe5269d9d537"
-"md","instructions","bmm","bmad/bmm/workflows/document-project/instructions.md","150154d560155635b7036043bb4c8ee99f52e4a34d1c9db13e955abc69a0452a"
-"md","instructions","bmm","bmad/bmm/workflows/testarch/atdd/instructions.md","afed355e21b2592c2bfe6ce71c64f6556deb082c865208613427a33e5daa61e3"
-"md","instructions","bmm","bmad/bmm/workflows/testarch/automate/instructions.md","43958a5fb17e5514101656720add81ae30dc7b38b5e0df596df4b7167d8cc059"
-"md","instructions","bmm","bmad/bmm/workflows/testarch/ci/instructions.md","2dbb3687ec7423d01ae29ef0f67400b0df56756a7c0041ef367d6c95b6f695c2"
-"md","instructions","bmm","bmad/bmm/workflows/testarch/framework/instructions.md","2bbaaa5559917cb2f5da2121df763893dc4ccd703afc385d9d71b5b379a798e8"
-"md","instructions","bmm","bmad/bmm/workflows/testarch/nfr-assess/instructions.md","a3838c8e5dcb1735962176aa07cc8f7a1d5a1e1ad70207a27a8152015cfebbcb"
-"md","instructions","bmm","bmad/bmm/workflows/testarch/test-design/instructions.md","b0e17d6cbc4852f4808ae891dc4c70d80cb7df267d1a5e4c138d8c92d12c1319"
-"md","instructions","bmm","bmad/bmm/workflows/testarch/test-review/instructions.md","8e1ed220ae9fb0ea5eba0a75f7fc755b774d8c1cfbaf15c9b972fdbdab76d954"
-"md","instructions","bmm","bmad/bmm/workflows/testarch/trace/instructions.md","e34afa60d1dc5810a37372f59cb37b4f42f08c811948968dddea9668b669b3d2"
-"md","instructions","bmm","bmad/bmm/workflows/workflow-status/init/instructions.md","52404f8731c09694fb8032ddbdcc43da94d89c79e5c4005fb0d4c09db864b316"
-"md","instructions","bmm","bmad/bmm/workflows/workflow-status/instructions.md","9706ab6bc6fe69cf519b6fc8f139349fb7aec18961a57c75082fcc586741d25c"
-"md","instructions-deep-prompt","bmm","bmad/bmm/workflows/1-analysis/research/instructions-deep-prompt.md","a0b0f774abe6a1e29dc01feb4dec706f2deffeb0e6f65d62f1cdaad87dfa0cae"
-"md","instructions-level0-story","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md","b158b4e5aa2357fbef4bc610e721bcb23801e622e9a56da60c3f58908f2f313d"
-"md","instructions-level1-stories","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md","3c8ad58ec827eaf9239140c781258ffb69493592b59b7dfd8562c461420beb38"
-"md","instructions-market","bmm","bmad/bmm/workflows/1-analysis/research/instructions-market.md","37aa30c1810fba4dd74998b21051a5409854ab5a97486df232bb0a4dc30dbe94"
-"md","instructions-narrative","bmm","bmad/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md","882d72dbea480a5bd0387a9d062e668adb585b2ae5f1ac3fb0f292c00f45c0cc"
-"md","instructions-router","bmm","bmad/bmm/workflows/1-analysis/research/instructions-router.md","8fe681c1902e66ff86f96228ca9932b5b688447f5ff66611514289dc2b926d4c"
-"md","instructions-technical","bmm","bmad/bmm/workflows/1-analysis/research/instructions-technical.md","45232dc63d4b80abc53868a4dbe2484bb69a87e7f16fb8765a6a73f5411bd4c4"
-"md","narrative-template","bmm","bmad/bmm/workflows/2-plan-workflows/narrative/narrative-template.md","a97e07173c540f85e946eb9c525e1ccad9294ae5f970760f2a9c537b5c0dcd6b"
+"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","1f62cb3f3f292a5a3d08b295f62fbeb46abff6eb9743abdd5112b49032a7253e"
+"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","1aaa58f55ec09afdfcdc0b830a1db054b5335b94e43c586b40f6b21e2809109a"
+"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","160041033e377e9b547a36440db379dd7cb13993d34f85e52554b075077cab30"
-"md","quick-start","bmm","bmad/bmm/docs/quick-start.md","7f32636d5bbc72df8138e6561e13b95e766d3eaba222261d8c4aaa2e2b39eb64"
+"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","9d39261689b75bbf92e60b0a3250dda150e33bb871557e26259c6ff54191616a"
+"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","0fd9db0d4c1bc00185e1fa88dc5494d49013976322f45cdf45afa03c856d98e6"
+"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","6c7e3534b7d34af38298c3dd91a00b4165d4bfaa3d8d62c3654b7fa38c4925e9"
+"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","97a2cf3d200a9ed038559a4c524e9b333f4d37cff480e976a9a4a292de63df3a"
+"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","abbd01d8606ee4cca815abb739db4f1bc78d6d5b5ee6b9f712013da46c053d31"
+"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"
@@ -191,7 +189,8 @@ type,name,module,path,hash
 "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-design-template","bmm","bmad/bmm/workflows/testarch/test-design/test-design-template.md","ccf81b14ec366cbd125a1cdebe40f07fcf7a9789b0ecc3e57111fc4526966d46"
+"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"
@@ -199,130 +198,92 @@ type,name,module,path,hash
 "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","troubleshooting","bmm","bmad/bmm/docs/troubleshooting.md","2b7bc49ec58d1f63a1976ead4338820e651e62b13e4e7cfdb135e73fe2a04d72"
-"md","user-story-template","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md","9a70551dbe1615a85697cd30f7dbcc0e6af1cfe193019f6739fa37d32622d7d2"
+"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","2913eebbc6eeff757ef08e8d42c68730ba3f6837d311fcbbe647a161a16b36cf"
+"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","1f271cd6c139def4de63a6e0b00800eaebb26353fb4c3758fb4d737c04c98e46"
-"md","workflows-analysis","bmm","bmad/bmm/docs/workflows-analysis.md","fd484512df12c21fc77ea53956a20d235ca20330aaee53f31388b9942fcb40e5"
-"md","workflows-implementation","bmm","bmad/bmm/docs/workflows-implementation.md","7c280d3c46568f4e09d597adf4812cd5e987aa201a36b25b7616f2de77c8a367"
-"md","workflows-planning","bmm","bmad/bmm/docs/workflows-planning.md","8c9955cecaabe1984393864a096d1595fb5a66ab518559ecf6f0f0b8cbd5fd47"
-"md","workflows-solutioning","bmm","bmad/bmm/docs/workflows-solutioning.md","7ab9a206eddc439dbe7fd41a8c7b956187e3907d85db7d21aa4ffc739417e435"
-"xml","context-template","bmm","bmad/bmm/workflows/4-implementation/story-context/context-template.xml","6b88d07ff10f51bb847d70e02f22d8927beb6ef1e55d5acf647e8f23b5821921"
-"xml","daily-standup","bmm","bmad/bmm/tasks/daily-standup.xml","667194d00272fd2204ed0712c934778f0d20de62f6c09dfc5080e7700239ca36"
+"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","56c2b76e22495a327aa8e4af69f2682082970e12655e260924b1d47705b1da4f"
+"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","5bba01ced6a5a703afa9db633cb8009d89fe37ceaa19b012cb4146ff5df5d361"
+"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","746eca76ca530becfbe263559bd8dd2683cf786df22c510938973b499e12922f"
-"yaml","enterprise-greenfield","bmm","bmad/bmm/workflows/workflow-status/paths/enterprise-greenfield.yaml","449923c7bcfda0e3bb75a5c2931baac00cc15002cbffc60bb3aaf9564afb6e73"
-"yaml","full-scan","bmm","bmad/bmm/workflows/document-project/workflows/full-scan.yaml","0a9c4d6caa66ab51c3a9122956821bcd8b5c17207e845bfa1c4dccaef81afbb9"
-"yaml","game-design","bmm","bmad/bmm/workflows/workflow-status/paths/game-design.yaml","9f8f86788fa4a39cb3063c7fc9e6c6bb96396cc0e9813a4014567556f0808956"
+"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","09d810864558bfbc5a83ed8989847a165bd59119dfe420194771643daff6c813"
+"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","f6e12ad099bbcc048990ea9c0798587b044880f17494dbce0b9dd35a7a674d05"
-"yaml","team-gamedev","bmm","bmad/bmm/teams/team-gamedev.yaml","aa6cad296fbe4a967647f378fcd9c2eb2e4dbedfea72029f54d1cae5e2a67e27"
+"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","9fa9d8a3e3467e00b9ba187f91520760751768b56fa14a325cc166e708067afb"
-"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/domain-research/workflow.yaml","368f4864f4354c4c5ecffc94e9daf922744ebb2b9103f9dab2bd38931720b03e"
-"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml","45a1e40440efe2fb0a614842a3efa3b62833bd6f3cf9188393f5f6dbbf1fa491"
-"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/research/workflow.yaml","339f40af85bcff64fedf417156e0c555113219071e06f741d356aaa95a9f5d19"
-"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml","218d220a7f218c6c6d4d4f74e42562b532ec246a2c4f4bd65e3a886239785aa3"
-"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml","69a6223af100fe63486bfcf72706435701f11cc464021ef8fe812a572b17436b"
-"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml","ca071a3d0680951fb3b171574acc4633c742c3da0cdb2da2406380bf3b93342b"
-"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml","3abc6ad64dad18d8cd05d14e94c7ca22b6cc2057badcc5a9c8a434ef54184e58"
-"yaml","workflow","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml","208a389c43e40bbc8ac47b224ceac24a5a72c843b9be41af0cba2f2198333754"
-"yaml","workflow","bmm","bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml","691727257a440a740069afc271e970d68c123f6b81692a1422197eab02ccdc84"
-"yaml","workflow","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml","1e8932f62f0ddc802d963e1af137f39fde7870214020e99664c2377fd2b072b8"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/code-review/workflow.yaml","b4d20f450243e5aedbb537093439c8b4b83aac8213a3a66be5bf2e95a1a9e0f8"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml","29fd40a0b4b16cba64462224732101de2c9050206c0c77dd555399ba8273fb5d"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","0b6ddcd6df3bc2cde34466944f322add6533c184932040e36b17789fb19ecff1"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml","96703263763717900ab1695de19a558c817a472e007af24b380f238c59a4c78d"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml","60899ef88c1766595218724a9c98238978fc977b8f584ec11a8731a06d21e1c3"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","2b27213f09c8809c4710e509ab3c4f63f9715c2ef5c5bad68cbd19711a23d7fb"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml","720f2013eefb7fa241b64671b7388a17b667ef4db8c21bc5c0ad9282df6b6baa"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","1c8c4b3d49665a2757c070b1558f89b5cb5a710381e5119424f682b7c87f1e2c"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-done/workflow.yaml","9edfac176cc3919bbf753e8671c38fb98a210f6a68c341abbf0cc39633435043"
-"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml","7c59d8ffaacb9982014fdad8c95ac1a99985ee4641a33130f251cc696fcf6bde"
-"yaml","workflow","bmm","bmad/bmm/workflows/document-project/workflow.yaml","a257aec6e0b2aa1eb935ae2291fbd8aeb83a93e17c5882d37d92adfe25fbbed8"
-"yaml","workflow","bmm","bmad/bmm/workflows/testarch/atdd/workflow.yaml","b1bc5f8101fabf3fd1dd725d3fd1e5d8568e5497856ccf0556c86a0435214d95"
-"yaml","workflow","bmm","bmad/bmm/workflows/testarch/automate/workflow.yaml","44b21e50e8419dbfdfbf7281b61f9e6f6630f4e9cf720fbe5e54b236d9d5e90d"
-"yaml","workflow","bmm","bmad/bmm/workflows/testarch/ci/workflow.yaml","de89801ec80bd7e13c030a2912b4eee8992e8e2bfd020b59f85466d3569802f9"
-"yaml","workflow","bmm","bmad/bmm/workflows/testarch/framework/workflow.yaml","72786ba1124a51e52acc825a340dcfda2188432ee6514f9e6e30b3bd0ef95123"
-"yaml","workflow","bmm","bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml","f7b005bf1af420693a8415b246bf4e87d827364cde09003649e6c234e6a4c5dc"
-"yaml","workflow","bmm","bmad/bmm/workflows/testarch/test-design/workflow.yaml","13c1255f250701a176dcc9d50f3acfcb0d310a2a15da92af56d658b2ed78e5c2"
-"yaml","workflow","bmm","bmad/bmm/workflows/testarch/test-review/workflow.yaml","19a389464ae744d5dd149e46c58beffb341cecc52198342a7c342cd3895d22f2"
-"yaml","workflow","bmm","bmad/bmm/workflows/testarch/trace/workflow.yaml","9e112a5d983d7b517e22f20b815772e38f42d2568a4dcb7d8eb5afaf9e246963"
-"yaml","workflow","bmm","bmad/bmm/workflows/workflow-status/init/workflow.yaml","e819d5ede67717bce20db57913029252f2374b77215f538d678f4a548caa7925"
-"yaml","workflow","bmm","bmad/bmm/workflows/workflow-status/workflow.yaml","d50d6e5593b871a197a67af991efec5204f354fd6b2ffe93790c9107bdb334c9"
+"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","design-methods","cis","bmad/cis/workflows/design-thinking/design-methods.csv","6735e9777620398e35b7b8ccb21e9263d9164241c3b9973eb76f5112fb3a8fc9"
-"csv","innovation-frameworks","cis","bmad/cis/workflows/innovation-strategy/innovation-frameworks.csv","9a14473b1d667467172d8d161e91829c174e476a030a983f12ec6af249c4e42f"
-"csv","solving-methods","cis","bmad/cis/workflows/problem-solving/solving-methods.csv","aa15c3a862523f20c199600d8d4d0a23fce1001010d7efc29a71abe537d42995"
-"csv","story-types","cis","bmad/cis/workflows/storytelling/story-types.csv","ec5a3c713617bf7e2cf7db439303dd8f3363daa2f6db20a350c82260ade88bdb"
-"md","brainstorming-coach","cis","bmad/cis/agents/brainstorming-coach.md","575658080178a0378b51249f805dc18a8b45bca9bd52032e3a97bd1160c64fcb"
-"md","creative-problem-solver","cis","bmad/cis/agents/creative-problem-solver.md","2dc08760b34d7328392cae249e8454c655143ed20074cc2d9acf3149d982689f"
-"md","design-thinking-coach","cis","bmad/cis/agents/design-thinking-coach.md","5374ac22137c53fc1f18d14825a4fd9965635aec8fe47676c9bf28bfaddf7380"
-"md","innovation-strategist","cis","bmad/cis/agents/innovation-strategist.md","d8a3789604cd16d855faf3f2b81c8af68c2b12d0641300c6c5ee24111157b797"
-"md","instructions","cis","bmad/cis/workflows/design-thinking/instructions.md","40e09c9c8dfcb57bb9f89f6357d619dc006d6520239494144a9122e5086d87dc"
-"md","instructions","cis","bmad/cis/workflows/innovation-strategy/instructions.md","fa8fbe1e56f666b0931a0c782cbf49f8b65dfa366c8ffa208f21ba3881bdb331"
-"md","instructions","cis","bmad/cis/workflows/problem-solving/instructions.md","9b4e1fd2e5ea8ce5c6d4fdb495291775225ad7aaca8a39d7ac3351b7475c0cc1"
-"md","instructions","cis","bmad/cis/workflows/storytelling/instructions.md","c49bbf472654cdcb7f227c5d94f2e82b47b9d6db8527adcb72e192f5df71e656"
-"md","README","cis","bmad/cis/README.md","31e1194dcef4a18b744d9e11d8b8aec42f336ccd351e287a1b62e5cec5a9d22a"
-"md","README","cis","bmad/cis/agents/README.md","dd7276c44ba77e9d856efaa9587666267279564a3f930398869f475341cd9c38"
-"md","README","cis","bmad/cis/workflows/README.md","f8ff9630b4f89858389fefb8204fe6589a5f0ed78b3f5cdf16f537df39fe3855"
-"md","README","cis","bmad/cis/workflows/design-thinking/README.md","0a38f88352dc4674f6e1f55a67ffebf403bf329c874a21a49ce7834c08f91f62"
-"md","README","cis","bmad/cis/workflows/innovation-strategy/README.md","820a9e734fadf2cfac94d499cec2e4b41a54d054c0d2f6b9819da319beee4fb9"
-"md","README","cis","bmad/cis/workflows/problem-solving/README.md","a5e75b9899751d7aabffcf65785f10d4d2e0455f8c7c541e8a143e3babceca8b"
-"md","README","cis","bmad/cis/workflows/storytelling/README.md","1bad4223dce51cb5a7ab8c116467f78037a4583d3a840210ee2f160ad15b71ee"
-"md","storyteller","cis","bmad/cis/agents/storyteller.md","931797eb435adb0460b7c4c3dd9f209c03d637c99cb8076deecd4b4a4a99a9b6"
-"md","template","cis","bmad/cis/workflows/design-thinking/template.md","7834c387ac0412c841b49a9fcdd8043f5ce053e5cb26993548cf4d31b561f6f0"
-"md","template","cis","bmad/cis/workflows/innovation-strategy/template.md","3e649531c0d8ac94e147159cd456aa0e1726439e8518c3ccc2ad08fc486aed59"
-"md","template","cis","bmad/cis/workflows/problem-solving/template.md","6c9efd7ac7b10010bd9911db16c2fbdca01fb0c306d871fa6381eef700b45608"
-"md","template","cis","bmad/cis/workflows/storytelling/template.md","461981aa772ef2df238070cbec90fc40995df2a71a8c22225b90c91afed57452"
-"yaml","brainstorming-coach.agent","cis","bmad/cis/agents/brainstorming-coach.agent.yaml",""
-"yaml","config","cis","bmad/cis/config.yaml","216a76c1f0dc54d9f8df25e822fe3811e45c8f57b6a3426edec41f8bf9b31a97"
-"yaml","creative-problem-solver.agent","cis","bmad/cis/agents/creative-problem-solver.agent.yaml",""
-"yaml","creative-squad","cis","bmad/cis/teams/creative-squad.yaml","5c31e9dd98fff661baa82e71ae3dd5856883fabbc245a62e28a77c4e2df83dec"
-"yaml","design-thinking-coach.agent","cis","bmad/cis/agents/design-thinking-coach.agent.yaml",""
-"yaml","innovation-strategist.agent","cis","bmad/cis/agents/innovation-strategist.agent.yaml",""
-"yaml","storyteller.agent","cis","bmad/cis/agents/storyteller.agent.yaml",""
-"yaml","workflow","cis","bmad/cis/workflows/design-thinking/workflow.yaml","a1bc933af1982db11ac6b2a26749c20b42683d9c75315992662ba6c2ad184b1f"
-"yaml","workflow","cis","bmad/cis/workflows/innovation-strategy/workflow.yaml","c613120567bd7890558f746925ed4b34947f964265c66539687db2eb6f1420f1"
-"yaml","workflow","cis","bmad/cis/workflows/problem-solving/workflow.yaml","fa93582b4b27dd9a91876e417d2f50156080966f788600e9b3b10fbc0b6ff628"
-"yaml","workflow","cis","bmad/cis/workflows/storytelling/workflow.yaml","d0af924c5f573c3c57bfd7eeaf712dadea9d96ca77383a3c2e4cd2d9fddc87eb"
 "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","da52edd5ab4fd9a189c3e27cc8d114eeefe0068ff85febdca455013b8c85da1a"
-"md","instructions","core","bmad/core/workflows/brainstorming/instructions.md","20c57ede11289def7927b6ef7bb69bd7a3deb9468dc08e93ee057f98a906e7f0"
-"md","instructions","core","bmad/core/workflows/party-mode/instructions.md","28e48c7a05e1f17ad64c0cc701a2ba60e385cd4704c726a14d4b886d885306ab"
-"md","README","core","bmad/core/workflows/brainstorming/README.md","4b81a01b94d6f9eda24a7adeb6cd4a2762482a9003859391a78226427b70d287"
+"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","94f004a336e434cd231de35eb864435ac51cd5888e9befe66e326eb16497121e"
-"xml","bmad-web-orchestrator.agent","core","bmad/core/agents/bmad-web-orchestrator.agent.xml","91a5c1b660befa7365f427640b4fa3dbb18f5e48cd135560303dae0939dccf12"
-"xml","index-docs","core","bmad/core/tasks/index-docs.xml","38226219c7dbde1c1dabcd87214383a6bfb2d0a7e79e09a9c79dd6be851b7e64"
-"xml","shard-doc","core","bmad/core/tools/shard-doc.xml","7788d38b9989361992664b8a4e23896081638df2a9bc9227eb56e82f3a5c183a"
-"xml","validate-workflow","core","bmad/core/tasks/validate-workflow.xml","1e8c569d8d53e618642aa1472721655cb917901a5888a7b403a98df4db2f26bf"
-"xml","workflow","core","bmad/core/tasks/workflow.xml","0b2b7bd184e099869174cc8d9125fce08bcd3fd64fad50ff835a42eccf6620e2"
+"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","5c229b5fcb7f9ff0af8e2bb9ce2defdff9e4664d4e8314a281c6c33778d6477e"
-"yaml","workflow","core","bmad/core/workflows/brainstorming/workflow.yaml","74038fa3892c4e873cc79ec806ecb2586fc5b4cf396c60ae964a6a71a9ad4a3d"
-"yaml","workflow","core","bmad/core/workflows/party-mode/workflow.yaml","04558885b784b4731f37465897b9292a756f64c409bd76dcc541407d50501605"
+"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

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

.bmad/_cfg/tool-manifest.csv

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

@@ -12,13 +12,13 @@ name,description,module,path,standalone
 "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"
-"narrative","Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance.","bmm","bmad/bmm/workflows/2-plan-workflows/narrative/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 project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow.","bmm","bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml","true"
-"tech-spec-sm","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"
+"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"
@@ -42,9 +42,3 @@ name,description,module,path,standalone
 "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"
-"design-thinking","Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.","cis","bmad/cis/workflows/design-thinking/workflow.yaml","true"
-"innovation-strategy","Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.","cis","bmad/cis/workflows/innovation-strategy/workflow.yaml","true"
-"problem-solving","Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.","cis","bmad/cis/workflows/problem-solving/workflow.yaml","true"
-"storytelling","Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.","cis","bmad/cis/workflows/storytelling/workflow.yaml","true"
-"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"

.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"`
@@ -161,7 +161,7 @@
     <action if="condition met">Do something</action>
     ```
 
-    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|invoke-task|goto|step)&gt; within text content
+    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|invoke-task|goto|step)&gt; within text content</action>
     <action>Record any instances of nested tag references with line numbers</action>
     <action>Scan instructions.md for conditional execution antipattern: self-closing check tags</action>
     <action>Detect pattern: `&lt;check&gt;.*&lt;/check&gt;` on single line (self-closing check)</action>
@@ -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>
 
@@ -193,9 +193,23 @@ menu:
   - trigger: [emerging from conversation]
     workflow: [path based on capability]
     description: [user's words refined]
-```
+
+# For cross-module workflow references (advanced):
+
+- trigger: [another capability]
+  workflow: "{project-root}/.bmad/SOURCE_MODULE/workflows/path/to/workflow.yaml"
+  workflow-install: "{project-root}/.bmad/THIS_MODULE/workflows/vendored/path/workflow.yaml"
+  description: [description]
+
+`````
 </example>
 
+<note>**Workflow Vendoring (Advanced):**
+When an agent needs workflows from another module, use both `workflow` (source) and `workflow-install` (destination).
+During installation, the workflow will be copied and configured for this module, making it standalone.
+This is typically used when creating specialized modules that reuse common workflows with different configurations.
+</note>
+
 <template-output>agent_commands</template-output>
 </step>
 
@@ -224,7 +238,7 @@ menu:
 <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
@@ -298,14 +312,16 @@ menu: {{The capabilities built}}
 
 **Folder Structure:**
 
-```
+`````
+
 {{agent_filename}}-sidecar/
-├── memories.md         # Persistent memory
-├── instructions.md     # Private directives
-├── knowledge/         # Knowledge base
-│   └── README.md
-└── sessions/          # Session notes
-```
+├── memories.md # Persistent memory
+├── instructions.md # Private directives
+├── knowledge/ # Knowledge base
+│ └── README.md
+└── sessions/ # Session notes
+
+````
 
 **File: memories.md**
 
@@ -323,7 +339,7 @@ menu: {{The capabilities built}}
 ## Personal Notes
 
 <!-- My observations and insights -->
-```
+````
 
 **File: instructions.md**
 

.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
@@ -136,6 +136,40 @@ Tasks should be used for:
 - Declare dependencies in config.yaml
 - Version compatibility notes
 
+### Workflow Vendoring (Advanced)
+
+For modules that need workflows from other modules but want to remain standalone, use **workflow vendoring**:
+
+**In Agent YAML:**
+
+```yaml
+menu:
+  - trigger: command-name
+    workflow: '{project-root}/.bmad/SOURCE_MODULE/workflows/path/workflow.yaml'
+    workflow-install: '{project-root}/.bmad/THIS_MODULE/workflows/vendored/workflow.yaml'
+    description: 'Command description'
+```
+
+**What Happens:**
+
+- During installation, workflows are copied from `workflow` to `workflow-install` location
+- Vendored workflows get `config_source` updated to reference this module's config
+- Compiled agent only references the `workflow-install` path
+- Module becomes fully standalone - no source module dependency required
+
+**Use Cases:**
+
+- Specialized modules that reuse common workflows with different configs
+- Domain-specific adaptations (e.g., game dev using standard dev workflows)
+- Testing workflows in isolation
+
+**Benefits:**
+
+- Module independence (no forced dependencies)
+- Clean namespace (workflows in your module)
+- Config isolation (use your module's settings)
+- Customization ready (modify vendored workflows freely)
+
 ## Installation Infrastructure
 
 ### Required: \_module-installer/install-config.yaml
@@ -182,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/agents/analyst.md

@@ -6,11 +6,11 @@ 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="📊">
+<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/bmm/config.yaml NOW
+      - 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>
@@ -28,13 +28,19 @@ 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
     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>
 
@@ -49,18 +55,20 @@ You must fully embody this agent's persona and follow all activation instruction
 </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 business needs into actionable technical specifications. Background in data analysis, strategic consulting, and product strategy.</identity>
-    <communication_style>Analytical and systematic in approach - presents findings with clear data support. Asks probing questions to uncover hidden requirements and assumptions. Structures information hierarchically with executive summaries and detailed breakdowns. Uses precise, unambiguous language when documenting requirements. Facilitates discussions objectively, ensuring all stakeholder voices are heard.</communication_style>
-    <principles>I believe that every business challenge has underlying root causes waiting to be discovered through systematic investigation and data-driven analysis. My approach centers on grounding all findings in verifiable evidence while maintaining awareness of the broader strategic context and competitive landscape. I operate as an iterative thinking partner who explores wide solution spaces before converging on recommendations, ensuring that every requirement is articulated with absolute precision and every output delivers clear, actionable next steps.</principles>
+    <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</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="*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="*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

@@ -6,11 +6,11 @@ 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="🏗️">
+<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/bmm/config.yaml NOW
+      - 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>
@@ -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
@@ -37,11 +37,17 @@ You must fully embody this agent's persona and follow all activation instruction
   </handler>
   <handler type="validate-workflow">
     When command has: validate-workflow="path/to/workflow.yaml"
-    1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
+    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>
 
@@ -56,16 +62,18 @@ You must fully embody this agent's persona and follow all activation instruction
 </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 architecture patterns and technology selection. Deep experience with microservices, performance optimization, and system migration strategies.</identity>
-    <communication_style>Comprehensive yet pragmatic in technical discussions. Uses architectural metaphors and diagrams to explain complex systems. Balances technical depth with accessibility for stakeholders. Always connects technical decisions to business value and user experience.</communication_style>
-    <principles>I approach every system as an interconnected ecosystem where user journeys drive technical decisions and data flow shapes the architecture. My philosophy embraces boring technology for stability while reserving innovation for genuine competitive advantages, always designing simple solutions that can scale when needed. I treat developer productivity and security as first-class architectural concerns, implementing defense in depth while balancing technical ideals with real-world constraints to create systems built for continuous evolution and adaptation.</principles>
+    <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="*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

@@ -6,11 +6,11 @@ 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-impl.md" name="Amelia" title="Developer Agent" icon="💻">
+<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/bmm/config.yaml NOW
+      - 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>
@@ -32,7 +32,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
@@ -53,16 +53,16 @@ You must fully embody this agent's persona and follow all activation instruction
 </activation>
   <persona>
     <role>Senior Implementation Engineer</role>
-    <identity>Executes approved stories with strict adherence to acceptance criteria, using the Story Context XML and existing code to minimize rework and hallucinations.</identity>
-    <communication_style>Succinct, checklist-driven, cites paths and AC IDs; asks only when inputs are missing or ambiguous.</communication_style>
-    <principles>I treat the Story Context XML as the single source of truth, trusting it over any training priors while refusing to invent solutions when information is missing. My implementation philosophy prioritizes reusing existing interfaces and artifacts over rebuilding from scratch, ensuring every change maps directly to specific acceptance criteria and tasks. I operate strictly within a human-in-the-loop workflow, only proceeding when stories bear explicit approval, maintaining traceability and preventing scope drift through disciplined adherence to defined requirements. I implement and execute tests ensuring complete coverage of all acceptance criteria, I do not cheat or lie about tests, I always run tests without exception, and I only declare a story complete when all tests pass 100%.</principles>
+    <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="*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

@@ -6,11 +6,11 @@ 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="📋">
+<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/bmm/config.yaml NOW
+      - 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>
@@ -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
@@ -37,11 +37,17 @@ You must fully embody this agent's persona and follow all activation instruction
   </handler>
   <handler type="validate-workflow">
     When command has: validate-workflow="path/to/workflow.yaml"
-    1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
+    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>
 
@@ -56,20 +62,22 @@ You must fully embody this agent's persona and follow all activation instruction
 </activation>
   <persona>
     <role>Investigative Product Strategist + Market-Savvy PM</role>
-    <identity>Product management veteran with 8+ years experience launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights. Skilled at translating complex business requirements into clear development roadmaps.</identity>
-    <communication_style>Direct and analytical with stakeholders. Asks probing questions to uncover root causes. Uses data and user insights to support recommendations. Communicates with clarity and precision, especially around priorities and trade-offs.</communication_style>
-    <principles>I operate with an investigative mindset that seeks to uncover the deeper &quot;why&quot; behind every requirement while maintaining relentless focus on delivering value to target users. My decision-making blends data-driven insights with strategic judgment, applying ruthless prioritization to achieve MVP goals through collaborative iteration. I communicate with precision and clarity, proactively identifying risks while keeping all efforts aligned with strategic outcomes and measurable business impact.</principles>
+    <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</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-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="*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

@@ -6,11 +6,11 @@ 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="🏃">
+<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/bmm/config.yaml NOW
+      - 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>
@@ -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
@@ -37,7 +37,7 @@ You must fully embody this agent's persona and follow all activation instruction
   </handler>
   <handler type="validate-workflow">
     When command has: validate-workflow="path/to/workflow.yaml"
-    1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
+    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
@@ -48,6 +48,12 @@ You must fully embody this agent's persona and follow all activation instruction
         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>
 
@@ -62,23 +68,25 @@ You must fully embody this agent's persona and follow all activation instruction
 </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 development team coordination. Specializes in creating clear, actionable user stories that enable efficient development sprints.</identity>
-    <communication_style>Task-oriented and efficient. Focuses on clear handoffs and precise requirements. Direct communication style that eliminates ambiguity. Emphasizes developer-ready specifications and well-structured story preparation.</communication_style>
-    <principles>I maintain strict boundaries between story preparation and implementation, rigorously following established procedures to generate detailed user stories that serve as the single source of truth for development. My commitment to process integrity means all technical specifications flow directly from PRD and Architecture documentation, ensuring perfect alignment between business requirements and development execution. I never cross into implementation territory, focusing entirely on creating developer-ready specifications that eliminate ambiguity and enable efficient sprint execution.</principles>
+    <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="*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

@@ -6,18 +6,18 @@ 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="🧪">
+<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/bmm/config.yaml NOW
+      - 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="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>
@@ -30,13 +30,19 @@ 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
     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>
 
@@ -52,20 +58,22 @@ You must fully embody this agent's persona and follow all activation instruction
   <persona>
     <role>Master Test Architect</role>
     <identity>Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.</identity>
-    <communication_style>Data-driven advisor. Strong opinions, weakly held. Pragmatic.</communication_style>
-    <principles>Risk-based testing. depth scales with impact. Quality gates backed by data. Tests mirror usage. Cost = creation + execution + maintenance. Testing is feature work. Prioritize unit/integration over E2E. Flakiness is critical debt. ATDD tests first, AI implements, suite validates.</principles>
+    <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="*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

@@ -6,17 +6,17 @@ 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="📚">
+<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/bmm/config.yaml NOW
+      - 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="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>
@@ -34,7 +34,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
@@ -46,6 +46,12 @@ You must fully embody this agent's persona and follow all activation instruction
         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>
 
@@ -60,13 +66,13 @@ You must fully embody this agent's persona and follow all activation instruction
 </activation>
   <persona>
     <role>Technical Documentation Specialist + Knowledge Curator</role>
-    <identity>Experienced technical writer with deep expertise in documentation standards (CommonMark, DITA, OpenAPI), API documentation, and developer experience. Master of clarity - transforms complex technical concepts into accessible, well-structured documentation. Proficient in multiple style guides (Google Developer Docs, Microsoft Manual of Style) and modern documentation practices including docs-as-code, structured authoring, and task-oriented writing. Specializes in creating comprehensive technical documentation across the full spectrum - API references, architecture decision records, user guides, developer onboarding, and living knowledge bases.</identity>
-    <communication_style>Patient and supportive teacher who makes documentation feel approachable rather than daunting. Uses clear examples and analogies to explain complex topics. Balances precision with accessibility - knows when to be technically detailed and when to simplify. Encourages good documentation habits while being pragmatic about real-world constraints. Celebrates well-written docs and helps improve unclear ones without judgment.</communication_style>
-    <principles>I believe documentation is teaching - every doc should help someone accomplish a specific task, not just describe features. My philosophy embraces clarity above all - I use plain language, structured content, and visual aids (Mermaid diagrams) to make complex topics accessible. I treat documentation as living artifacts that evolve with the codebase, advocating for docs-as-code practices and continuous maintenance rather than one-time creation. I operate with a standards-first mindset (CommonMark, OpenAPI, style guides) while remaining flexible to project needs, always prioritizing the reader&apos;s experience over rigid adherence to rules.</principles>
+    <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="*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>
@@ -76,6 +82,8 @@ You must fully embody this agent's persona and follow all activation instruction
     <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

@@ -6,11 +6,11 @@ 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="🎨">
+<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/bmm/config.yaml NOW
+      - 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>
@@ -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
@@ -37,11 +37,17 @@ You must fully embody this agent's persona and follow all activation instruction
   </handler>
   <handler type="validate-workflow">
     When command has: validate-workflow="path/to/workflow.yaml"
-    1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
+    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>
 
@@ -56,15 +62,17 @@ You must fully embody this agent's persona and follow all activation instruction
 </activation>
   <persona>
     <role>User Experience Designer + UI Specialist</role>
-    <identity>Senior UX Designer with 7+ years creating intuitive user experiences across web and mobile platforms. Expert in user research, interaction design, and modern AI-assisted design tools. Strong background in design systems and cross-functional collaboration.</identity>
-    <communication_style>Empathetic and user-focused. Uses storytelling to communicate design decisions. Creative yet data-informed approach. Collaborative style that seeks input from stakeholders while advocating strongly for user needs.</communication_style>
-    <principles>I champion user-centered design where every decision serves genuine user needs, starting with simple solutions that evolve through feedback into memorable experiences enriched by thoughtful micro-interactions. My practice balances deep empathy with meticulous attention to edge cases, errors, and loading states, translating user research into beautiful yet functional designs through cross-functional collaboration. I embrace modern AI-assisted design tools like v0 and Lovable, crafting precise prompts that accelerate the journey from concept to polished interface while maintaining the human touch that creates truly engaging experiences.</principles>
+    <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="*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

@@ -1,17 +1,18 @@
 # BMM Module Configuration
 # Generated by BMAD installer
-# Version: 6.0.0-alpha.4
-# Date: 2025-11-04T02:59:22.716Z
+# Version: 6.0.0-alpha.7
+# Date: 2025-11-09T05:23:00.244Z
 
 project_name: BMAD-METHOD
-include_game_planning: false
 user_skill_level: intermediate
-tech_docs: "{project-root}/docs"
-dev_story_location: "{project-root}/docs/stories"
+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

@@ -36,7 +36,7 @@ Understanding how BMM adapts to your needs:
 
 ---
 
-## 🤖 Agents & Collaboration
+## 🤖 Agents and Collaboration
 
 Complete guide to BMM's AI agent team:
 
@@ -52,7 +52,7 @@ Complete guide to BMM's AI agent team:
   - Example party compositions
   - Multi-module integration (BMM + CIS + BMB + custom)
   - Agent customization in party mode
-  - Best practices and troubleshooting
+  - Best practices
 
 ---
 
@@ -65,7 +65,7 @@ Comprehensive guide for brownfield development:
   - Track selection for brownfield
   - Integration with existing patterns
   - Phase-by-phase workflow guidance
-  - Common scenarios and troubleshooting
+  - Common scenarios
 
 ---
 
@@ -75,7 +75,6 @@ Essential reference materials:
 
 - **[Glossary](./glossary.md)** - Key terminology and concepts
 - **[FAQ](./faq.md)** - Frequently asked questions across all topics
-- **[Troubleshooting](./troubleshooting.md)** - Common issues and solutions
 - **[Enterprise Agentic Development](./enterprise-agentic-development.md)** - Team collaboration strategies
 
 ---
@@ -99,7 +98,7 @@ Essential reference materials:
 → See [Scale Adaptive System](./scale-adaptive-system.md)
 
 **Find specific commands or answers**
-→ Check [FAQ](./faq.md) or [Troubleshooting](./troubleshooting.md)
+→ Check [FAQ](./faq.md)
 
 ---
 
@@ -127,7 +126,7 @@ Comprehensive documentation for all BMM workflows organized by phase:
   - Complete story lifecycle
   - One-story-at-a-time discipline
 
-- **[Testing & QA Workflows](./workflows-testing.md)** - Comprehensive quality assurance (1,420 lines)
+- **[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
@@ -152,15 +151,16 @@ For detailed technical documentation on specific complex workflows:
 
 ---
 
-## 🧪 Testing & Quality
+## 🧪 Testing and Quality
 
 Quality assurance guidance:
 
-- **[Test Architect Guide](../testarch/README.md)** - Comprehensive testing strategy
-  - Test design workflows
-  - Quality gates
-  - Risk assessment
-  - NFR validation
+<!-- Test Architect documentation to be added -->
+
+- Test design workflows
+- Quality gates
+- Risk assessment
+- NFR validation
 
 ---
 
@@ -178,7 +178,7 @@ Understanding BMM components:
 
 ## 🌐 External Resources
 
-### Community & Support
+### 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
@@ -212,12 +212,12 @@ flowchart TD
     SAS --> IMPL
     BF --> IMPL
 
-    IMPL --> REF[Quick References<br/>Glossary, FAQ, Troubleshooting]
+    IMPL --> REF[Quick References<br/>Glossary, FAQ]
 
-    style START fill:#bfb,stroke:#333,stroke-width:2px
-    style QS fill:#bbf,stroke:#333,stroke-width:2px
-    style DECIDE fill:#ffb,stroke:#333,stroke-width:2px
-    style IMPL fill:#f9f,stroke:#333,stroke-width:2px
+    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
 ```
 
 ---

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

@@ -629,14 +629,14 @@ You can customize any agent's personality without modifying core agent files.
 
 ### Location
 
-**Customization Directory:** `{project-root}/bmad/_cfg/agents/`
+**Customization Directory:** `{project-root}/.bmad/_cfg/agents/`
 
 **Naming Convention:** `{module}-{agent-name}.customize.yaml`
 
 **Examples:**
 
 ```
-bmad/_cfg/agents/
+.bmad/_cfg/agents/
 ├── bmm-pm.customize.yaml
 ├── bmm-dev.customize.yaml
 ├── cis-storyteller.customize.yaml
@@ -736,9 +736,9 @@ Other agents collaborate with PM's specialized perspective.
 
 ```bash
 # Create customization file at:
-# {project-root}/bmad/_cfg/agents/{module}-{agent-name}.customize.yaml
+# {project-root}/.bmad/_cfg/agents/{module}-{agent-name}.customize.yaml
 
-# Example: bmad/_cfg/agents/bmm-pm.customize.yaml
+# Example: .bmad/_cfg/agents/bmm-pm.customize.yaml
 ```
 
 **Step 2: Regenerate Agent Manifest**
@@ -996,7 +996,7 @@ Quick reference for agent selection:
 - [Phase 2: Planning Workflows](./workflows-planning.md)
 - [Phase 3: Solutioning Workflows](./workflows-solutioning.md)
 - [Phase 4: Implementation Workflows](./workflows-implementation.md)
-- [Testing & QA Workflows](./workflows-testing.md)
+<!-- Testing & QA Workflows documentation to be added -->
 
 **Advanced References:**
 
@@ -1013,7 +1013,6 @@ Quick reference for agent selection:
 
 - [Enterprise Agentic Development](./enterprise-agentic-development.md) - Team collaboration
 - [FAQ](./faq.md) - Common questions
-- [Troubleshooting](./troubleshooting.md) - Problem resolution
 - [Glossary](./glossary.md) - Terminology reference
 
 ---

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

@@ -12,7 +12,6 @@
 
 - [Quick Reference](#quick-reference) - Commands and files
 - [Common Scenarios](#common-scenarios) - Real-world examples
-- [Troubleshooting](#troubleshooting) - Problem solutions
 - [Best Practices](#best-practices) - Success tips
 
 ---
@@ -138,7 +137,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
 
    ```bash
    # Load BMad Master or any agent
-   bmad/core/tools/shard-doc.xml --input docs/massive-doc.md
+   .bmad/core/tools/shard-doc.xml --input docs/massive-doc.md
    ```
 
    - Splits on level 2 sections by default
@@ -148,7 +147,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
 2. **Then:** Run `index-docs` task to create navigation:
 
    ```bash
-   bmad/core/tasks/index-docs.xml --directory ./docs
+   .bmad/core/tasks/index-docs.xml --directory ./docs
    ```
 
 3. **Finally:** Validate quality - if sharded docs still seem incomplete/outdated → Run `document-project`
@@ -211,7 +210,7 @@ If you have **good, current documentation** but it's in massive files:
 
 ```bash
 # For each massive doc (>500 lines or 10+ level 2 sections)
-bmad/core/tools/shard-doc.xml \
+.bmad/core/tools/shard-doc.xml \
   --input docs/api-documentation.md \
   --output docs/api/ \
   --level 2  # Split on ## headers (default)
@@ -220,7 +219,7 @@ bmad/core/tools/shard-doc.xml \
 **Step 2: Generate index**
 
 ```bash
-bmad/core/tasks/index-docs.xml --directory ./docs
+.bmad/core/tasks/index-docs.xml --directory ./docs
 ```
 
 **Step 3: Validate**
@@ -277,7 +276,7 @@ It's better to spend 10-30 minutes generating fresh, accurate docs than to waste
 
 **When to skip:** Bug fixes, well-understood features, time-sensitive changes
 
-See [Workflows Guide](../workflows/README.md) for details.
+See the [Workflows section in BMM README](../README.md) for details.
 
 ### Phase 2: Planning (Required)
 
@@ -336,8 +335,8 @@ flowchart TD
     CHECK -->|Yes| CREATE
     CHECK -->|No| RETRO
 
-    style SPRINT fill:#bfb,stroke:#333,stroke-width:2px
-    style RETRO fill:#fbf,stroke:#333,stroke-width:2px
+    style SPRINT fill:#bfb,stroke:#333,stroke-width:2px,color:#000
+    style RETRO fill:#fbf,stroke:#333,stroke-width:2px,color:#000
 ```
 
 **Status Progression:**
@@ -534,8 +533,6 @@ Document in tech-spec/architecture:
 
 ## Troubleshooting
 
-For complete troubleshooting, see [Troubleshooting Guide](./troubleshooting.md).
-
 ### AI Agents Lack Codebase Understanding
 
 **Symptoms:**
@@ -706,9 +703,9 @@ flowchart TD
     PRD --> IMPL
     PRD2 --> IMPL
 
-    style START fill:#f9f,stroke:#333,stroke-width:2px
-    style DOC fill:#ffb,stroke:#333,stroke-width:2px
-    style IMPL fill:#bfb,stroke:#333,stroke-width:2px
+    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
 ```
 
 ---
@@ -735,12 +732,11 @@ flowchart TD
 - **[Quick Start Guide](./quick-start.md)** - Getting started with BMM
 - **[Glossary](./glossary.md)** - Key terminology
 - **[FAQ](./faq.md)** - Common questions
-- **[Troubleshooting](./troubleshooting.md)** - Problem resolution
-- **[Workflows Guide](../workflows/README.md)** - Complete workflow reference
+- **[Workflow Documentation](./README.md#-workflow-guides)** - Complete workflow reference
 
 ---
 
-## Support & Resources
+## Support and Resources
 
 **Community:**
 
@@ -750,9 +746,8 @@ flowchart TD
 
 **Documentation:**
 
-- [BMM Workflows Guide](../workflows/README.md)
-- [Test Architect Guide](../testarch/README.md)
-- [BMM Module README](../README.md)
+- [Test Architect Guide](./test-architecture.md) - Comprehensive testing strategy
+- [BMM Module README](../README.md) - Complete module and workflow reference
 
 ---
 

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

@@ -9,7 +9,7 @@
 ## Table of Contents
 
 - [The Paradigm Shift](#the-paradigm-shift)
-- [The Evolving Role of Product Managers & UX Designers](#the-evolving-role-of-product-managers--ux-designers)
+- [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)
@@ -59,7 +59,7 @@
 
 ---
 
-## The Evolving Role of Product Managers & UX Designers
+## The Evolving Role of Product Managers and UX Designers
 
 ### The Future is Now
 
@@ -419,7 +419,7 @@ Team C (2 devs): Analytics feature (3 epics)
 
 **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.
+**Anti-pattern:** Adding `.bmad/` to `.gitignore` breaks IDE tools, submodule management.
 
 ### The Solution: Git Submodules
 
@@ -457,7 +457,7 @@ git commit -m "Add BMM as submodule"
 git clone https://github.com/your-org/your-project.git
 cd your-project
 git submodule update --init --recursive
-# Make personal customizations in bmad/
+# Make personal customizations in .bmad/
 ```
 
 ### Daily Workflow
@@ -466,7 +466,7 @@ git submodule update --init --recursive
 
 ```bash
 cd /path/to/your-project
-# BMad available at ./bmad/, load agents normally
+# BMad available at ./.bmad/, load agents normally
 ```
 
 **Update personal config:**
@@ -672,7 +672,7 @@ PMs write BMad PRDs → Stories auto-fed to cloud AI agents → Parallel impleme
 - [FAQ](./faq.md) - Common questions
 - [Scale Adaptive System](./scale-adaptive-system.md) - Project levels explained
 - [Quick Start Guide](./quick-start.md) - Getting started
-- [Workflows Guide](../workflows/README.md) - Complete workflow reference
+- [Workflow Documentation](./README.md#-workflow-guides) - Complete workflow reference
 - [Agents Guide](./agents-guide.md) - Understanding BMad agents
 
 ---

.bmad/bmm/docs/faq.md

@@ -8,11 +8,11 @@ Quick answers to common questions about the BMad Method Module.
 
 - [Getting Started](#getting-started)
 - [Choosing the Right Level](#choosing-the-right-level)
-- [Workflows & Phases](#workflows--phases)
+- [Workflows and Phases](#workflows-and-phases)
 - [Planning Documents](#planning-documents)
 - [Implementation](#implementation)
 - [Brownfield Development](#brownfield-development)
-- [Tools & Technical](#tools--technical)
+- [Tools and Technical](#tools-and-technical)
 
 ---
 
@@ -26,7 +26,7 @@ Quick answers to common questions about the BMad Method Module.
 - 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.
+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?
 
@@ -108,7 +108,7 @@ The overlap (5-10 stories) is intentional. Choose based on:
 
 ---
 
-## Workflows & Phases
+## Workflows and Phases
 
 ### Q: What's the difference between workflow-status and workflow-init?
 
@@ -339,7 +339,7 @@ BMM respects your choice - it won't force modernization, but it will offer it.
 
 ---
 
-## Tools & Technical
+## Tools and Technical
 
 ### Q: Why are my Mermaid diagrams not rendering?
 
@@ -399,11 +399,11 @@ Use them together for best results.
 
 **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](../../../docs/ide-info/) for configuration specifics.
+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.
+**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.
 
@@ -557,11 +557,10 @@ Trust your expertise - BMM supports your decisions.
 
 **A:**
 
-1. Check [Troubleshooting Guide](./troubleshooting.md) for common issues
-2. Search [Complete Documentation](./README.md) for related topics
-3. Ask in [Discord Community](https://discord.gg/gk8jAdXWmj) (#general-dev)
-4. Open a [GitHub Issue](https://github.com/bmad-code-org/BMAD-METHOD/issues)
-5. Watch [YouTube Tutorials](https://www.youtube.com/@BMadCode)
+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?
 
@@ -580,7 +579,6 @@ Please include:
 
 - [Quick Start Guide](./quick-start.md) - Get started with BMM
 - [Glossary](./glossary.md) - Terminology reference
-- [Troubleshooting](./troubleshooting.md) - Problem resolution
 - [Scale Adaptive System](./scale-adaptive-system.md) - Understanding levels
 - [Brownfield Guide](./brownfield-guide.md) - Existing codebase workflows
 

.bmad/bmm/docs/glossary.md

@@ -7,11 +7,11 @@ Comprehensive terminology reference for the BMad Method Module.
 ## Navigation
 
 - [Core Concepts](#core-concepts)
-- [Scale & Complexity](#scale--complexity)
+- [Scale and Complexity](#scale-and-complexity)
 - [Planning Documents](#planning-documents)
-- [Workflow & Phases](#workflow--phases)
-- [Agents & Roles](#agents--roles)
-- [Status & Tracking](#status--tracking)
+- [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)
 
@@ -41,7 +41,7 @@ A multi-step guided process that orchestrates AI agent activities to produce spe
 
 ---
 
-## Scale & Complexity
+## Scale and Complexity
 
 ### Quick Flow Track
 
@@ -99,7 +99,7 @@ Game development equivalent of PRD, created by Game Designer agent for game proj
 
 ---
 
-## Workflow & Phases
+## Workflow and Phases
 
 ### Phase 0: Documentation (Prerequisite)
 
@@ -135,7 +135,7 @@ Dynamic technical guidance generated for each story via epic-tech-context and st
 
 ---
 
-## Agents & Roles
+## Agents and Roles
 
 ### PM (Product Manager)
 
@@ -183,7 +183,7 @@ Multi-agent collaboration feature where all installed agents (19+ from BMM, CIS,
 
 ---
 
-## Status & Tracking
+## Status and Tracking
 
 ### bmm-workflow-status.yaml
 
@@ -318,4 +318,3 @@ Quick Spec Flow feature that automatically detects existing code style, naming c
 - [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
-- [Troubleshooting](./troubleshooting.md) - Problem resolution

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

@@ -27,7 +27,7 @@ Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent), and su
 
 **The basics:**
 
-1. Party mode reads `bmad/_cfg/agent-manifest.csv`
+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
@@ -126,11 +126,11 @@ _(Multiple perspectives reveal the right answer)_
 
 ## Agent Customization
 
-Party mode uses agents from `bmad/[module]/agents/*.md` - these already include any customizations you applied during install.
+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`
+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
 

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

@@ -60,10 +60,10 @@ flowchart TD
     STORIES --> IMPL
     IMPL --> DONE
 
-    style START fill:#bfb,stroke:#333,stroke-width:2px
-    style OPTIONAL fill:#ffb,stroke:#333,stroke-width:2px,stroke-dasharray: 5 5
-    style IMPL fill:#bbf,stroke:#333,stroke-width:2px
-    style DONE fill:#f9f,stroke:#333,stroke-width:3px
+    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
 ```
 
 ---
@@ -277,7 +277,7 @@ For user-facing changes, Quick Spec Flow captures:
 
 ---
 
-## Auto-Validation & Quality Assurance
+## Auto-Validation and Quality Assurance
 
 Quick Spec Flow **automatically validates** everything:
 
@@ -543,7 +543,7 @@ Quick Spec Flow is **fully standalone**:
 
 ---
 
-## Tips & Best Practices
+## Tips and Best Practices
 
 ### 1. **Be Specific in Discovery**
 
@@ -643,7 +643,7 @@ Quick Spec Flow is your **fast path from idea to implementation** for:
 ## Next Steps
 
 - **Try it now:** Load PM agent and describe a small change
-- **Learn more:** See `src/modules/bmm/workflows/README.md` for full BMM workflow guide
+- **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
 

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

@@ -29,7 +29,7 @@ BMad Method (BMM) helps you build software through guided workflows with special
 npx bmad-method@alpha install
 ```
 
-The interactive installer will guide you through setup and create a `bmad/` folder with all agents and workflows.
+The interactive installer will guide you through setup and create a `.bmad/` folder with all agents and workflows.
 
 ---
 
@@ -37,9 +37,9 @@ The interactive installer will guide you through setup and create a `bmad/` fold
 
 ### Step 1: Initialize Your Workflow
 
-1. **Load the Analyst agent** in your IDE - See your IDE-specific instructions in [docs/ide-info](../docs/ide-info/) for how to activate agents:
-   - [Claude Code](../docs/ide-info/claude-code.md)
-   - [VS Code/Cursor/Windsurf](../docs/ide-info/) - Check your IDE folder
+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
@@ -107,7 +107,7 @@ The next TRULY REQUIRED step is:
 
 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](../docs/ide-info/) for your IDE's specific instructions
+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`
@@ -323,10 +323,10 @@ flowchart LR
     P2 --> P3
     P3 --> P4
 
-    style P1 fill:#bbf,stroke:#333,stroke-width:2px
-    style P2 fill:#bfb,stroke:#333,stroke-width:2px
-    style P3 fill:#ffb,stroke:#333,stroke-width:2px
-    style P4 fill:#fbf,stroke:#333,stroke-width:2px
+    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
@@ -350,7 +350,7 @@ A: Yes, once you learn the flow. Use the Quick Reference in Step 2 to go directl
 
 - **During workflows**: Agents guide you with questions and explanations
 - **Community**: [Discord](https://discord.gg/gk8jAdXWmj) - #general-dev, #bugs-issues
-- **Complete guide**: [BMM Workflows README](../src/modules/bmm/workflows/README.md)
+- **Complete guide**: [BMM Workflow Documentation](./README.md#-workflow-guides)
 - **YouTube tutorials**: [BMad Code Channel](https://www.youtube.com/@BMadCode)
 
 ---

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

@@ -51,9 +51,9 @@ flowchart TD
     Q1 -->|Yes| QF[Quick Flow<br/>Tech-spec only]
     Q1 -->|Uncertain| M
 
-    style QF fill:#bfb,stroke:#333,stroke-width:2px
-    style M fill:#bbf,stroke:#333,stroke-width:2px
-    style E fill:#f9f,stroke:#333,stroke-width:2px
+    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
@@ -389,8 +389,8 @@ flowchart TD
     TRACK -->|Method| M[PRD + Arch]
     TRACK -->|Enterprise| E[PRD + Arch + Sec/Ops]
 
-    style DOC fill:#ffb,stroke:#333,stroke-width:2px
-    style TRACK fill:#bfb,stroke:#333,stroke-width:2px
+    style DOC fill:#ffb,stroke:#333,stroke-width:2px,color:#000
+    style TRACK fill:#bfb,stroke:#333,stroke-width:2px,color:#000
 ```
 
 ---
@@ -592,7 +592,7 @@ Run `workflow-init` on existing projects to migrate to new tracking system. It d
 - **[Brownfield Guide](./brownfield-guide.md)** - Existing codebase workflows
 - **[Glossary](./glossary.md)** - Complete terminology
 - **[FAQ](./faq.md)** - Common questions
-- **[Workflows Guide](../workflows/README.md)** - Complete workflow reference
+- **[Workflows Guide](./README.md#-workflow-guides)** - Complete workflow reference
 
 ---
 

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

@@ -0,0 +1,433 @@
+---
+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 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>"]
+        TestDesignSys["<b>TEA: *test-design (system-level)</b>"]
+        ValidateArch["<b>Architect: *validate-architecture</b>"]
+        GateCheck["<b>Architect: *solutioning-gate-check</b>"]
+        Architecture --> TestDesignSys
+        TestDesignSys --> ValidateArch
+        ValidateArch --> GateCheck
+        Phase3Note["<b>Testability review before gate</b><br/>Recommended: Method | Required: Enterprise"]
+        TestDesignSys -.-> Phase3Note
+    end
+
+    subgraph Phase4["<b>Phase 4: IMPLEMENTATION</b>"]
+        subgraph Sprint0["<b>Sprint 0: Infrastructure Setup</b>"]
+            Framework["<b>TEA: *framework</b>"]
+            CI["<b>TEA: *ci</b>"]
+            Framework --> CI
+            Sprint0Note["<b>Test infrastructure setup</b><br/>based on architectural decisions"]
+            Framework -.-> Sprint0Note
+        end
+
+        SprintPlan["<b>SM: *sprint-planning</b>"]
+
+        subgraph PerEpic["<b>Per Epic Cycle</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>"]
+
+            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
+
+        CI --> SprintPlan
+        SprintPlan --> TestDesign
+    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 Sprint0 fill:#f3e5f5,stroke:#6a1b9a,stroke-width:2px,color:#000
+    style PerEpic fill:#f3e5f5,stroke:#6a1b9a,stroke-width:2px,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** (Required): Solutioning (`*architecture` → `*validate-architecture` → `*solutioning-gate-check`)
+- **Phase 4** (Required): Implementation
+  - **Sprint 0**: Test infrastructure setup (`*framework`, `*ci`) based on architectural decisions
+  - **Sprint Planning**: Load epics into sprint status
+  - **Per-Epic**: `*test-design` → per-story dev workflows
+
+**TEA workflows:** `*test-design` runs in Phase 3 (system-level testability review, recommended/required) and Phase 4 (per-epic planning). `*framework` and `*ci` run once in Phase 4 Sprint 0 (after architecture and testability are approved).
+
+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 **both Phase 3 (Solutioning) and Phase 4 (Implementation)** 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: Cross-Phase Quality Agent (Unique Pattern)
+
+TEA is **the only agent that operates in both Phase 3 (Solutioning) and Phase 4 (Implementation)**:
+
+```
+Phase 1 (Analysis) → [TEA not typically used]
+    ↓
+Phase 2 (Planning) → [PM defines requirements - TEA not active]
+    ↓
+Phase 3 (Solutioning) → TEA: *test-design (system-level testability review before gate)
+    ↓
+Phase 4 Sprint 0 → TEA: *framework, *ci (test infrastructure setup based on testability review)
+    ↓
+Phase 4 Sprint Planning → [SM loads epics into sprint status]
+    ↓
+Phase 4 Per-Epic → TEA: *test-design (per epic: "how do I test THIS feature?")
+Phase 4 Per-Story → TEA: *atdd, *automate, *test-review, *trace (per story)
+    ↓
+Epic/Release Gate → TEA: *nfr-assess, *trace Phase 2 (release decision)
+```
+
+### TEA's 8 Workflows Across Phase 3-4
+
+**Standard agents**: 1-3 workflows per phase
+**TEA**: 8 workflows spanning Phase 3 Solutioning through Phase 4 Release Gate
+
+| Phase                 | TEA Workflows                            | Frequency        | Purpose                                        |
+| --------------------- | ---------------------------------------- | ---------------- | ---------------------------------------------- |
+| **Phase 2**           | (none)                                   | -                | Planning phase - PM defines requirements       |
+| **Phase 3**           | \*test-design (system-level)             | Once per project | Testability review before solutioning gate     |
+| **Phase 4 Sprint 0**  | *framework, *ci                          | Once per project | Setup test infrastructure based on testability |
+| **Phase 4 Per-Epic**  | \*test-design (epic-level)               | Per epic         | Test planning: "how do I test THIS epic?"      |
+| **Phase 4 Per-Story** | *atdd, *automate, \*test-review, \*trace | Per story        | Test implementation and quality validation     |
+| **Release Gate**      | *nfr-assess, *trace (Phase 2: gate)      | Per epic/release | Go/no-go decision                              |
+
+**Note**: Like `*trace`, `*test-design` is now a dual-mode workflow: system-level mode (testability review in Phase 3) and epic-level mode (test planning in Phase 4). Auto-detects mode based on project phase.
+
+### 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 `*test-design` (system-level, recommended)                    | Architect `*architecture`, `*solutioning-gate-check` | Architecture, `test-design-system.md` (testability review) |
+| **Phase 4**: Sprint 0        | Run `*framework`, `*ci` based on test-design-system.md            | Setup repo structure, dependencies                   | Test scaffold, CI pipeline, development environment        |
+| **Phase 4**: Sprint Planning | -                                                                 | SM `*sprint-planning`                                | Sprint status file with all epics and stories              |
+| **Phase 4**: Epic Planning   | Run `*test-design` (epic-level, auto-detected)                    | 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>
+
+- **Phase 3 (Solutioning)**: Architect creates architecture document; TEA runs `*test-design` (system-level mode, auto-detected) for testability review; gate check validates planning completeness including testability.
+- **`*test-design` auto-detects mode**: In Phase 3 outputs `test-design-system.md`, in Phase 4 outputs `test-design-epic-N.md`.
+- **Phase 4 Sprint 0**: After architecture is approved and testability validated, run `*framework` and `*ci` to setup test infrastructure. This is implementation work (scaffolding code, installing dependencies, configuring CI), not planning.
+- **Phase 4 Sprint Planning**: After infrastructure is ready, sprint planning loads all epics.
+- **`*test-design` runs per-epic** (Phase 4): At the beginning of each epic, run `*test-design` to create epic-specific test plan. 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` defining tech stack; TEA runs `*test-design` (auto-detects system-level mode) producing `test-design-system.md` with testability review; gate check validates planning completeness including testability.
+3. **Sprint 0 (Phase 4):** TEA sets up test infrastructure via `*framework` and `*ci` based on test-design-system.md; team scaffolds repo structure and dependencies.
+4. **Sprint Planning (Phase 4):** Scrum Master runs `*sprint-planning` to load all epics into sprint status.
+5. **Epic 1 Planning (Phase 4):** TEA runs `*test-design` (auto-detects epic-level mode) to create test plan for Epic 1, producing `test-design-epic-1.md` with risk assessment.
+6. **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.
+7. **Post-Dev (Phase 4):** TEA runs `*automate`, optionally `*test-review` to audit test quality, re-runs `*trace` to refresh coverage.
+8. **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 3: `*test-design` (system-level) - Includes brownfield testability concerns
+- 🔄 Phase 4 Sprint 0: `*framework`, `*ci` - May integrate with/replace existing test setup
+- 🔄 Phase 4: `*test-design` (epic-level) - 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 `*test-design` (system-level, recommended) 🔄                            | Architect `*architecture`, `*solutioning-gate-check` | Architecture, `test-design-system.md` (brownfield testability review)  |
+| **Phase 4**: Sprint 0         | Run `*framework`, `*ci` based on test-design-system.md 🔄                    | Modernize/integrate test setup                       | Test scaffold, CI pipeline (may replace existing)                      |
+| **Phase 4**: Sprint Planning  | -                                                                            | SM `*sprint-planning`                                | Sprint status file with all epics and stories                          |
+| **Phase 4**: Epic Planning    | Run `*test-design` (epic-level) 🔄 (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)**: Architect creates architecture document; TEA runs `*test-design` (system-level mode, auto-detected) for testability review including brownfield concerns; gate check validates planning completeness including testability.
+- **`*test-design` auto-detects mode**: In Phase 3 outputs `test-design-system.md`, in Phase 4 outputs `test-design-epic-N.md`.
+- **Phase 4 Sprint 0**: After architecture is approved and testability validated, run `*framework` and `*ci` to modernize test infrastructure. For brownfield, this may integrate with or replace existing test setup.
+- **Phase 4 Sprint Planning**: After infrastructure is ready, sprint planning loads all epics.
+- **`*test-design` runs per-epic** (Phase 4): At the beginning of each epic, run `*test-design` to identify regression hotspots, integration risks, and mitigation strategies. 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 runs `*test-design` (auto-detects system-level mode) producing `test-design-system.md` with brownfield testability review; gate check validates planning.
+3. **Sprint 0 (Phase 4):** TEA sets up `*framework` and `*ci` based on test-design-system.md, integrating with existing test setup; team modernizes infrastructure.
+4. **Sprint Planning (Phase 4):** Scrum Master runs `*sprint-planning` to load Epic 1 into sprint status.
+5. **Epic 1 Planning (Phase 4):** TEA runs `*test-design` (auto-detects epic-level mode) for Epic 1, producing `test-design-epic-1.md` that flags settlement edge cases, regression hotspots, and mitigation plans.
+6. **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.
+7. **Post-Dev (Phase 4):** TEA applies `*automate`, optionally `*test-review` to audit test quality, re-runs `*trace` to refresh coverage.
+8. **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 3: `*test-design` (system-level) - **Required** for enterprise (vs recommended for Method)
+- 🔄 Phase 4 Sprint 0: `*framework`, `*ci` - Enterprise-grade configurations
+- 🔄 Phase 4: `*test-design` (epic-level) - 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 `*test-design` (system-level, **required**) 🔄                       | Architect `*architecture`, `*solutioning-gate-check` | Architecture, `test-design-system.md` (enterprise testability)     |
+| **Phase 4**: Sprint 0        | Run `*framework`, `*ci` with enterprise configs 🔄                       | Setup enterprise infrastructure                      | Test scaffold, CI pipeline (selective testing, burn-in, caching)   |
+| **Phase 4**: Sprint Planning | -                                                                        | SM `*sprint-planning`                                | Sprint plan with all epics                                         |
+| **Phase 4**: Epic Planning   | Run `*test-design` (epic-level) 🔄 (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)**: Architect creates architecture document with enterprise considerations; TEA runs `*test-design` (system-level mode, **required** for enterprise) for comprehensive testability review; gate check validates planning completeness including testability.
+- **`*test-design` auto-detects mode**: In Phase 3 outputs `test-design-system.md`, in Phase 4 outputs `test-design-epic-N.md`.
+- **Phase 4 Sprint 0**: After architecture is approved and testability validated, run `*framework` and `*ci` with enterprise-grade configurations (selective testing, burn-in jobs, caching, notifications).
+- **Phase 4 Sprint Planning**: After infrastructure is ready, sprint planning loads all epics.
+- **`*test-design` runs per-epic** (Phase 4): At the beginning of each epic, run `*test-design` to create enterprise-focused test plan 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 runs `*test-design` (auto-detects system-level mode, required) producing `test-design-system.md` with comprehensive testability review; gate check validates planning completeness.
+3. **Sprint 0 (Phase 4):** TEA sets up `*framework` and `*ci` with enterprise-grade configurations based on test-design-system.md; team establishes infrastructure.
+4. **Sprint Planning (Phase 4):** Scrum Master runs `*sprint-planning` to load all epics into sprint status.
+5. **Per-Epic (Phase 4):** For each epic, TEA runs `*test-design` (auto-detects epic-level mode) to create epic-specific test plan (e.g., `test-design-epic-1.md`, `test-design-epic-2.md`) with compliance-focused risk assessment.
+6. **Per-Story (Phase 4):** For each story, TEA uses `*atdd`, `*automate`, `*test-review`, and `*trace`; Dev teams iterate on the findings.
+7. **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-document-project-reference.md

@@ -179,7 +179,7 @@ The workflow uses a single comprehensive CSV file:
 
 **documentation-requirements.csv** - Complete project analysis guide
 
-- Location: `/bmad/bmm/workflows/document-project/documentation-requirements.csv`
+- 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)

.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._