bmad-method 6.0.0-alpha.20 → 6.0.0-alpha.22

package/src/modules/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml

@@ -23,7 +23,7 @@ checklist: "{installed_path}/checklist.md"
 # Related workflows
 quick_prototype_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
 party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+advanced_elicitation: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
 
 # Routing resources (lazy-loaded)
 workflow_init: "{project-root}/_bmad/bmgd/workflows/workflow-status/init/workflow.yaml"

package/src/modules/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml

@@ -23,7 +23,7 @@ checklist: "{installed_path}/checklist.md"
 # Related workflows
 quick_dev_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
 party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+advanced_elicitation: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
 
 # Game-specific references
 gdd_patterns:

package/src/modules/bmm/_module-installer/installer.js

@@ -20,40 +20,8 @@ async function install(options) {
   try {
     logger.log(chalk.blue('🚀 Installing BMM Module...'));
 
-    // Check and create tech_docs directory if configured
-    if (config['tech_docs']) {
-      // Strip {project-root}/ prefix if present
-      const techDocsConfig = config['tech_docs'].replace('{project-root}/', '');
-      const techDocsPath = path.join(projectRoot, techDocsConfig);
-
-      if (await fs.pathExists(techDocsPath)) {
-        // Check if template exists, add if missing
-        const templateDest = path.join(techDocsPath, 'technical-decisions-template.md');
-        if (!(await fs.pathExists(templateDest))) {
-          const templateSource = path.join(__dirname, 'assets', 'technical-decisions-template.md');
-          if (await fs.pathExists(templateSource)) {
-            await fs.copy(templateSource, templateDest);
-            logger.log(chalk.green('✓ Added technical decisions template to existing directory'));
-          }
-        }
-      } else {
-        logger.log(chalk.yellow(`Creating technical documentation directory: ${techDocsConfig}`));
-        await fs.ensureDir(techDocsPath);
-
-        // Copy technical decisions template
-        const templateSource = path.join(__dirname, 'assets', 'technical-decisions-template.md');
-        const templateDest = path.join(techDocsPath, 'technical-decisions-template.md');
-
-        if (await fs.pathExists(templateSource)) {
-          await fs.copy(templateSource, templateDest, { overwrite: false });
-          logger.log(chalk.green('✓ Added technical decisions template'));
-        }
-      }
-    }
-
     // Create output directory if configured
     if (config['output_folder']) {
-      // Strip {project-root}/ prefix if present
       const outputConfig = config['output_folder'].replace('{project-root}/', '');
       const outputPath = path.join(projectRoot, outputConfig);
       if (!(await fs.pathExists(outputPath))) {
@@ -62,9 +30,7 @@ async function install(options) {
       }
     }
 
-    // Create dev story location if configured
     if (config['implementation_artifacts']) {
-      // Strip {project-root}/ prefix if present
       const storyConfig = config['implementation_artifacts'].replace('{project-root}/', '');
       const storyPath = path.join(projectRoot, storyConfig);
       if (!(await fs.pathExists(storyPath))) {

package/src/modules/bmm/agents/analyst.agent.yaml

@@ -18,35 +18,23 @@ agent:
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:
-    - trigger: workflow-status
+    - trigger: WS or fuzzy match on workflow-status
       workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: Get workflow status or initialize a workflow if not already done (optional)
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
 
-    - trigger: brainstorm-project
+    - trigger: BP or fuzzy match on brainstorm-project
       exec: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
       data: "{project-root}/_bmad/bmm/data/project-context-template.md"
-      description: Guided Project Brainstorming session with final report (optional)
+      description: "[BP] Guided Project Brainstorming session with final report (optional)"
 
-    - trigger: research
+    - trigger: RS or fuzzy match on research
       exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow.md"
-      description: Guided Research scoped to market, domain, competitive analysis, or technical research (optional)
+      description: "[RS] Guided Research scoped to market, domain, competitive analysis, or technical research (optional)"
 
-    - trigger: product-brief
+    - trigger: PB or fuzzy match on product-brief
       exec: "{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
-      description: Create a Product Brief (recommended input for PRD)
+      description: "[PB] Create a Product Brief (recommended input for PRD)"
 
-    - trigger: document-project
+    - trigger: DP or fuzzy match on document-project
       workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml"
-      description: Document your existing project (optional, but recommended for existing brownfield project efforts)
-
-    - multi: "[SPM] Start Party Mode (optionally suggest attendees and topic), [CH] Chat"
-      triggers:
-        - party-mode:
-            - input: SPM or fuzzy match start party mode
-            - route: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-            - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
-            - type: exec
-        - expert-chat:
-            - input: CH or fuzzy match validate agent
-            - action: agent responds as expert based on its persona to converse
-            - type: action
+      description: "[DP] Document your existing project (optional, but recommended for existing brownfield project efforts)"

package/src/modules/bmm/agents/architect.agent.yaml

@@ -18,31 +18,14 @@ agent:
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:
-    - trigger: workflow-status
+    - trigger: WS or fuzzy match on workflow-status
       workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: Get workflow status or initialize a workflow if not already done (optional)
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
 
-    - trigger: create-architecture
+    - trigger: CA or fuzzy match on create-architecture
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md"
-      description: Create an Architecture Document to Guide Development of a PRD (required for BMad Method projects)
+      description: "[CA] Create an Architecture Document"
 
-    - trigger: implementation-readiness
+    - trigger: IR or fuzzy match on implementation-readiness
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
-      description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
-
-    - trigger: create-excalidraw-diagram
-      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml"
-      description: Create system architecture or technical diagram (Excalidraw) (Use any time you need a diagram)
-
-    - trigger: create-excalidraw-dataflow
-      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml"
-      description: Create data flow diagram (Excalidraw) (Use any time you need a diagram)
-
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true
+      description: "[IR] Implementation Readiness Review"

package/src/modules/bmm/agents/dev.agent.yaml

@@ -35,14 +35,10 @@ agent:
     - "NEVER lie about tests being written or passing - tests must actually exist and pass 100%"
 
   menu:
-    - trigger: DS or dev-story or fuzzy match on dev-story
+    - trigger: DS or fuzzy match on dev-story
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
       description: "[DS] Execute Dev Story workflow (full BMM path with sprint-status)"
 
-    - trigger: CR or code-review or fuzzy match on code-review
+    - trigger: CR or fuzzy match on code-review
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
       description: "[CR] Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)"
-
-    - trigger: PM or party-mode or fuzzy match on party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PM] Bring the whole team in to chat with other expert agents from the party"

package/src/modules/bmm/agents/pm.agent.yaml

@@ -10,41 +10,34 @@ agent:
     module: bmm
 
   persona:
-    role: Investigative Product Strategist + Market-Savvy PM
+    role: Product Manager specializing in collaborative PRD creation through user interviews, requirement discovery, and stakeholder alignment.
     identity: Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.
     communication_style: "Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters."
     principles: |
-      - Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks.
-      - Align efforts with measurable business impact. Back all claims with data and user insights.
+      - Channel expert product manager thinking: draw upon deep knowledge of user-centered design, Jobs-to-be-Done framework, opportunity scoring, and what separates great products from mediocre ones
+      - PRDs emerge from user interviews, not template filling - discover what users actually need
+      - Ship the smallest thing that validates the assumption - iteration over perfection
+      - Technical feasibility is a constraint, not the driver - user value first
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:
-    - trigger: workflow-status
+    - trigger: WS or fuzzy match on workflow-status
       workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: Get workflow status or initialize a workflow if not already done (optional)
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
 
-    - trigger: create-prd
+    - trigger: PR or fuzzy match on prd
       exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
-      description: Create Product Requirements Document (PRD) (Required for BMad Method flow)
+      description: "[PR] Create Product Requirements Document (PRD) (Required for BMad Method flow)"
 
-    - trigger: create-epics-and-stories
+    - trigger: ES or fuzzy match on epics-stories
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
-      description: Create Epics and User Stories from PRD (Required for BMad Method flow AFTER the Architecture is completed)
+      description: "[ES] Create Epics and User Stories from PRD (Required for BMad Method flow AFTER the Architecture is completed)"
 
-    - trigger: implementation-readiness
+    - trigger: IR or fuzzy match on implementation-readiness
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
-      description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
+      description: "[IR] Implementation Readiness Review"
 
-    - trigger: correct-course
+    - trigger: CC or fuzzy match on correct-course
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      description: Course Correction Analysis (optional during implementation when things go off track)
+      description: "[CC] Course Correction Analysis (optional during implementation when things go off track)"
       ide-only: true
-
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true

package/src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -18,10 +18,14 @@ agent:
       - If `**/project-context.md` exists, follow it. If absent, proceed without.
 
   menu:
-    - trigger: TS or tech-spec or fuzzy match on tech-spec
-      workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
+    - trigger: TS or fuzzy match on tech-spec
+      exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.md"
       description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)"
 
-    - trigger: QD or quick-dev or fuzzy match on quick-dev
+    - trigger: QD or fuzzy match on quick-dev
       workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
       description: "[QD] Implement the tech spec end-to-end solo (Core of Quick Flow)"
+
+    - trigger: CR or fuzzy match on code-review
+      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
+      description: "[CR] Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)"

package/src/modules/bmm/agents/sm.agent.yaml

@@ -24,35 +24,23 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: sprint-planning
+    - trigger: WS or fuzzy match on workflow-status
+      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+
+    - trigger: SP or fuzzy match on sprint-planning
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
-      description: Generate or re-generate sprint-status.yaml from epic files (Required after Epics+Stories are created)
+      description: "[SP] Generate or re-generate sprint-status.yaml from epic files (Required after Epics+Stories are created)"
 
-    - trigger: create-story
+    - trigger: CS or fuzzy match on create-story
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-      description: Create Story (Required to prepare stories for development)
-
-    # TODO: validate-create-story is not yet implemented
-    # The validate-workflow: handler type is not recognized by the workflow engine
-    # See: https://github.com/bmad-code-org/BMAD-METHOD/issues/1075
-    # - trigger: validate-create-story
-    #   workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/validate-workflow.yaml"
-    #   description: Validate Story (Highly Recommended, use fresh context and different LLM for best results)
+      description: "[CS] Create Story (Required to prepare stories for development)"
 
-    - trigger: epic-retrospective
+    - trigger: ER or fuzzy match on epic-retrospective
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
       data: "{project-root}/_bmad/_config/agent-manifest.csv"
-      description: Facilitate team retrospective after an epic is completed (Optional)
+      description: "[ER] Facilitate team retrospective after an epic is completed (Optional)"
 
-    - trigger: correct-course
+    - trigger: CC or fuzzy match on correct-course
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      description: Execute correct-course task (When implementation is off-track)
-
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true
+      description: "[CC] Execute correct-course task (When implementation is off-track)"

package/src/modules/bmm/agents/tea.agent.yaml

@@ -28,43 +28,38 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: framework
+    - trigger: WS or fuzzy match on workflow-status
+      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+
+    - trigger: TF or fuzzy match on test-framework
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/framework/workflow.yaml"
-      description: Initialize production-ready test framework architecture
+      description: "[TF] Initialize production-ready test framework architecture"
 
-    - trigger: atdd
+    - trigger: AT or fuzzy match on atdd
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/atdd/workflow.yaml"
-      description: Generate E2E tests first, before starting implementation
+      description: "[AT] Generate E2E tests first, before starting implementation"
 
-    - trigger: automate
+    - trigger: TA or fuzzy match on test-automate
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/automate/workflow.yaml"
-      description: Generate comprehensive test automation
+      description: "[TA] Generate comprehensive test automation"
 
-    - trigger: test-design
+    - trigger: TD or fuzzy match on test-design
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/test-design/workflow.yaml"
-      description: Create comprehensive test scenarios
+      description: "[TD] Create comprehensive test scenarios"
 
-    - trigger: trace
+    - trigger: TR or fuzzy match on test-trace
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/trace/workflow.yaml"
-      description: Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)
+      description: "[TR] Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)"
 
-    - trigger: nfr-assess
+    - trigger: NR or fuzzy match on nfr-assess
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml"
-      description: Validate non-functional requirements
+      description: "[NR] Validate non-functional requirements"
 
-    - trigger: ci
+    - trigger: CI or fuzzy match on continuous-integration
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/ci/workflow.yaml"
-      description: Scaffold CI/CD quality pipeline
+      description: "[CI] Scaffold CI/CD quality pipeline"
 
-    - trigger: test-review
+    - trigger: RV or fuzzy match on test-review
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/test-review/workflow.yaml"
-      description: Review test quality using comprehensive knowledge base and best practices
-
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true
+      description: "[RV] Review test quality using comprehensive knowledge base and best practices"

package/src/modules/bmm/agents/tech-writer.agent.yaml

@@ -21,47 +21,34 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: document-project
+    - trigger: WS or fuzzy match on workflow-status
+      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+
+    - trigger: DP or fuzzy match on document-project
       workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml"
-      description: Comprehensive project documentation (brownfield analysis, architecture scanning)
+      description: "[DP] Comprehensive project documentation (brownfield analysis, architecture scanning)"
 
-    - trigger: generate-mermaid
+    - trigger: MG or fuzzy match on mermaid-gen
       action: "Create a Mermaid diagram based on user description. Ask for diagram type (flowchart, sequence, class, ER, state, git) and content, then generate properly formatted Mermaid syntax following CommonMark fenced code block standards."
-      description: Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)
+      description: "[MG] Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)"
 
-    - trigger: create-excalidraw-flowchart
+    - trigger: EF or fuzzy match on excalidraw-flowchart
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml"
-      description: Create Excalidraw flowchart for processes and logic flows
+      description: "[EF] Create Excalidraw flowchart for processes and logic flows"
 
-    - trigger: create-excalidraw-diagram
+    - trigger: ED or fuzzy match on excalidraw-diagram
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml"
-      description: Create Excalidraw system architecture or technical diagram
+      description: "[ED] Create Excalidraw system architecture or technical diagram"
 
-    - trigger: create-excalidraw-dataflow
+    - trigger: DF or fuzzy match on dataflow
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml"
-      description: Create Excalidraw data flow diagram
+      description: "[DF] Create Excalidraw data flow diagram"
 
-    - trigger: validate-doc
+    - trigger: VD or fuzzy match on validate-doc
       action: "Review the specified document against CommonMark standards, technical writing best practices, and style guide compliance. Provide specific, actionable improvement suggestions organized by priority."
-      description: Validate documentation against standards and best practices
-
-    - trigger: 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)."
-      description: Review and improve README files
+      description: "[VD] Validate documentation against standards and best practices"
 
-    - trigger: explain-concept
+    - trigger: EC or fuzzy match on 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."
-      description: Create clear technical explanations with examples
-
-    - trigger: standards-guide
-      action: "Display the complete documentation standards from {project-root}/_bmad/bmm/data/documentation-standards.md in a clear, formatted way for the user."
-      description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)
-
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true
+      description: "[EC] Create clear technical explanations with examples"

package/src/modules/bmm/agents/ux-designer.agent.yaml

@@ -23,26 +23,14 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: create-ux-design
-      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
-      description: Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)
+    - trigger: WS or fuzzy match on workflow-status
+      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
 
-    # TODO: validate-design is not yet implemented
-    # The validate-workflow: handler type is not recognized by the workflow engine
-    # See: https://github.com/bmad-code-org/BMAD-METHOD/issues/1075
-    # - trigger: validate-design
-    #   workflow: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/validate-workflow.yaml"
-    #   description: Validate UX Specification and Design Artifacts
+    - trigger: UX or fuzzy match on ux-design
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
+      description: "[UX] Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)"
 
-    - trigger: create-excalidraw-wireframe
+    - trigger: XW or fuzzy match on wireframe
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml"
-      description: Create website or app wireframe (Excalidraw)
-
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true
+      description: "[XW] Create website or app wireframe (Excalidraw)"

package/src/modules/bmm/module.yaml

@@ -31,7 +31,7 @@ user_skill_level:
 
 planning_artifacts: # Phase 1-3 artifacts
   prompt: "Where should project planning artifacts be stored?\n - Such as: (Brain Storming, Briefs, PRDs, UX Designs, Architectures, Detailed Epics Plan)"
-  default: "{output_folder}/project-planning-artifacts"
+  default: "{output_folder}/planning-artifacts"
   result: "{project-root}/{value}"
 
 implementation_artifacts: # Phase 4 artifacts and quick-dev flow output
@@ -45,12 +45,12 @@ project_knowledge: # Artifacts from research, document-project output, other lon
   result: "{project-root}/{value}"
 
 tea_use_mcp_enhancements:
-  prompt: "WEB APP ONLY: Test Architect Playwright MCP capabilities (healing, exploratory, verification) are optionally available.\nYou will have to setup your MCPs yourself; refer to test-architecture.md for hints.\nWould you like to enable MCP enhancements in Test Architect?"
+  prompt: "Test Architect Playwright MCP capabilities (healing, exploratory, verification) are optionally available.\nYou will have to setup your MCPs yourself; refer to test-architecture.md for hints.\nWould you like to enable MCP enhancements in Test Architect?"
   default: false
   result: "{value}"
 
 tea_use_playwright_utils:
   prompt:
-    - "WEB APP ONLY: Are you using playwright-utils (@seontechnologies/playwright-utils) in your project?\nYou must install packages yourself, or use test architect's *framework command."
+    - "Are you using playwright-utils (@seontechnologies/playwright-utils) in your project?\nYou must install packages yourself, or use test architect's *framework command."
   default: false
   result: "{value}"

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -29,6 +29,7 @@ Initialize the product brief workflow by detecting continuation state and settin
 - 📖 CRITICAL: Read the complete step file before taking any action
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 
@@ -67,7 +68,7 @@ First, check if the output document already exists:
 
 **Workflow State Detection:**
 
-- Look for file at `{output_folder}/analysis/*product-brief*.md`
+- Look for file `{outputFile}`
 - If exists, read the complete file including frontmatter
 - If not exists, this is a fresh workflow
 
@@ -88,47 +89,35 @@ If no document exists or no `stepsCompleted` in frontmatter:
 
 #### A. Input Document Discovery
 
-Discover and load context documents using smart discovery:
+load context documents using smart discovery. Documents can be in the following locations:
+- {planning_artifacts}/**
+- {output_folder}/**
+- {product_knowledge}/**
+- docs/**
 
-**Research Documents (Priority: Sharded → Whole):**
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
 
-1. Check for sharded research folder: `{output_folder}/analysis/research/**/*.md`
-2. If folder exists: Load EVERY file in that folder completely
-3. If no folder exists: Try whole file: `{output_folder}/analysis/research/*research*.md`
-4. Add discovered files to `inputDocuments` frontmatter
+Try to discover the following:
+- Brainstorming Reports (`*brainstorming*.md`)
+- Research Documents (`*research*.md`)
+- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
 
-**Brainstorming Documents (Priority: Sharded → Whole):**
+<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
 
-1. Check for sharded brainstorming folder: `{output_folder}/analysis/*brainstorm*/**/*.md`
-2. If folder exists: Load useful brainstorming files completely
-3. If no folder exists: Try whole file: `{output_folder}/analysis/*brainstorm*.md`
-4. Add discovered files to `inputDocuments` frontmatter
+**Loading Rules:**
 
-**Project Documentation (Existing Projects):**
-
-1. Look for index file: `{output_folder}/**/index.md`
-2. Load index.md to understand what project files are available
-3. Read available files from index to understand existing project context
-4. Add discovered files to `inputDocuments` frontmatter
+- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
+- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
+- index.md is a guide to what's relevant whenever available
+- Track all successfully loaded files in frontmatter `inputDocuments` array
 
 #### B. Create Initial Document
 
 **Document Setup:**
 
-- Copy the template from `{productBriefTemplate}` to `{outputFile}`
-- Initialize frontmatter with proper structure:
-
-```yaml
----
-stepsCompleted: []
-inputDocuments: []
-workflowType: 'product-brief'
-lastStep: 0
-project_name: '{{project_name}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
----
-```
+- Copy the template from `{productBriefTemplate}` to `{outputFile}`, and update the frontmatter fields
 
 #### C. Present Initialization Results
 
@@ -145,6 +134,7 @@ date: '{{date}}'
 - Research: {number of research files loaded or "None found"}
 - Brainstorming: {number of brainstorming files loaded or "None found"}
 - Project docs: {number of project files loaded or "None found"}
+- Project Context: {number of project context files loaded or "None found"}
 
 **Files loaded:** {list of specific file names or "No additional documents found"}
 

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md

@@ -25,6 +25,7 @@ Resume the product brief workflow from where it was left off, ensuring smooth co
 - 📖 CRITICAL: Read the complete step file before taking any action
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -30,6 +30,7 @@ Conduct comprehensive product vision discovery to define the core problem, solut
 - 📖 CRITICAL: Read the complete step file before taking any action
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement: