adv elicitation project updated to hopefully not be skipped as optional anymore. further workflow updates.

src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md

@@ -195,7 +195,7 @@ Examples:
 
 <template-output>special_requirements</template-output>
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 

src/modules/bmm/workflows/1-analysis/research/instructions-market.md

@@ -80,7 +80,7 @@ Search queries to execute:
 - "[market_category] market growth rate CAGR forecast"
 - "[market_category] market trends [current_year]"
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="3b" title="Regulatory and Government Data">
@@ -204,8 +204,8 @@ For each major segment, research and define:
 - Purchasing frequency
 - Budget allocation
 
-<elicit-required/>
-<template-output>segment_profile_{{segment_number}}</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<template-output>segment*profile*{{segment_number}}</template-output>
 </step>
 
 <step n="5b" title="Jobs-to-be-Done Framework">
@@ -280,8 +280,8 @@ Gather intelligence on:
 - Team and leadership
 - Customer reviews and sentiment
 
-<elicit-required/>
-<template-output>competitor_analysis_{{competitor_number}}</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<template-output>competitor*analysis*{{competitor_number}}</template-output>
 </step>
 
 <step n="6c" title="Competitive Positioning Map">
@@ -404,7 +404,7 @@ For each opportunity:
 - Risk assessment
 - Success criteria
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 <template-output>market_opportunities</template-output>
 </step>
 

src/modules/bmm/workflows/1-analysis/research/instructions-technical.md

@@ -101,7 +101,7 @@ If you have specific options, list them. Otherwise, I'll research current leadin
 - "State of [technical_category] 2025"
   </action>
 
-  <elicit-required/>
+  <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <action>Present discovered options (typically 3-5 main candidates)</action>
 <template-output>technology_options</template-output>
@@ -173,8 +173,8 @@ Research and document:
 - Training costs
 - Total cost of ownership estimate
 
-<elicit-required/>
-<template-output>tech_profile_{{option_number}}</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<template-output>tech*profile*{{option_number}}</template-output>
 
 </step>
 
@@ -344,7 +344,7 @@ Research and document:
 - Contingency options if primary choice doesn't work
 - Exit strategy considerations
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <template-output>recommendations</template-output>
 

src/modules/bmm/workflows/1-analysis/workflow-status/instructions.md

@@ -252,7 +252,31 @@ Your choice (1-12):</ask>
 
 <action>Set project_type = mapped project_type_id</action>
 
-<output>**Step 4: Understanding Your Workflow**
+<ask>**Step 4: User Interface Components**
+
+Does your project involve user-facing UI components?
+
+a. **Yes** - Project has user interface elements (web pages, mobile screens, desktop UI, game UI)
+b. **No** - Backend-only, API, CLI, or no visual interface
+
+Your choice (a/b):</ask>
+
+<action>Capture has_ui_components</action>
+
+<check if='has_ui_components == "a"'>
+  <action>Set needs_ux_workflow = true</action>
+  <output>**✅ UX Workflow Detected**
+
+Since your project has UI components, we'll include the UX specification workflow in Phase 2.
+This ensures proper UX/UI design happens between PRD and architecture/implementation.
+</output>
+</check>
+
+<check if='has_ui_components == "b"'>
+  <action>Set needs_ux_workflow = false</action>
+</check>
+
+<output>**Step 5: Understanding Your Workflow**
 
 Before we plan your workflow, let's determine the scope and complexity of your project.
 
@@ -267,7 +291,9 @@ The BMad Method uses 5 project levels (0-4) that determine which phases you'll n
 **Optional Phase 1 (Analysis):** Brainstorming, research, and brief creation can precede any level.
 </output>
 
-<ask>**Do you already know your project's approximate size/scope?**
+<ask>**Step 6: Project Scope Assessment**
+
+Do you already know your project's approximate size/scope?
 
 a. **Yes** - I can describe the general scope
 b. **No** - Not sure yet, need help determining it
@@ -309,7 +335,7 @@ We'll determine your project level during Phase 2 (Planning).
 <action>Set estimated_level = "TBD"</action>
 </check>
 
-<ask>**Step 5: Choose Your Starting Point**
+<ask>**Step 7: Choose Your Starting Point**
 
 Now let's determine where you want to begin:
 
@@ -406,6 +432,16 @@ Based on your responses, here's your complete workflow journey:
 - Description: "Create PRD/GDD/Tech-Spec (determines final level)"
 - Status: "Planned"
 
+<check if='needs_ux_workflow == true'>
+  <action>Add UX workflow to Phase 2 planning (runs after PRD, before Phase 3)</action>
+  - Phase: "2-Plan"
+  - Step: "ux-spec"
+  - Agent: "PM"
+  - Description: "UX/UI specification (user flows, wireframes, components)"
+  - Status: "Planned"
+  - Note: "Required for projects with UI components"
+</check>
+
 <check if='level_known == true AND estimated_level >= 3'>
   <action>Add Phase 3 (required for Level 3-4)</action>
   - Phase: "3-Solutioning"
@@ -609,6 +645,7 @@ Which phase? (1-4)</ask>
 **Phase 2: Planning (Required)**
 
 - `plan-project` - Scale-adaptive planning (PRD, GDD, or Tech-Spec)
+- `ux-spec` - UX/UI specification (for projects with UI components)
 
 **Phase 3: Solutioning (Level 3-4 Only)**