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

src/modules/bmm/workflows/2-plan/gdd/instructions-gdd.md

@@ -151,7 +151,7 @@ Your gameplay loop:</ask>
 Define the primary game mechanics.
 
 <template-output>primary_mechanics</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <ask>Describe the control scheme and input method:
 
@@ -176,7 +176,7 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 
 <template-output file="GDD.md">GAME_TYPE_SPECIFIC_SECTIONS</template-output>
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -312,7 +312,7 @@ Asset requirements:</ask>
 - Level 4: 5+ epics with 40+ stories
 
 <template-output>epics</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -336,7 +336,7 @@ Generate all stories with:
 - Technical notes (high-level only)
 
 <template-output file="epics.md">epic\_{{epic_number}}\_details</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </for-each>
 

src/modules/bmm/workflows/2-plan/narrative/instructions-narrative.md

@@ -105,7 +105,7 @@ For 3-Act:
 Describe each act/section for your game:</ask>
 
 <template-output>act_breakdown</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -124,7 +124,7 @@ Format:
 Your story beats:</ask>
 
 <template-output>story_beats</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <ask>Describe the pacing and flow of your narrative.
 
@@ -157,7 +157,7 @@ For each protagonist include:
 Your protagonist(s):</ask>
 
 <template-output>protagonists</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -195,7 +195,7 @@ For each character include:
 Your supporting characters:</ask>
 
 <template-output>supporting_characters</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -243,7 +243,7 @@ Your world:</ask>
 Your history:</ask>
 
 <template-output>history_backstory</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 

src/modules/bmm/workflows/2-plan/prd/instructions-lg.md

@@ -68,7 +68,7 @@ Each goal should be measurable and outcome-focused.
 1-2 paragraphs on problem, current situation, why now.
 
 <template-output>context</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -82,7 +82,7 @@ Each goal should be measurable and outcome-focused.
 Group related features logically.
 
 <template-output>functional_requirements</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -104,7 +104,7 @@ Match NFRs to deployment intent (8-12 NFRs)
 Map complete user flows with decision points.
 
 <template-output>user_journeys</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -126,7 +126,7 @@ Map complete user flows with decision points.
 Each epic delivers significant value.
 
 <template-output>epics</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -150,7 +150,7 @@ Generate all stories with:
 - Technical notes (high-level only)
 
 <template-output file="epics.md">epic\_{{epic_number}}\_details</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </for-each>
 
@@ -205,7 +205,13 @@ Since this is a Level {{project_level}} project, you need architecture before st
 <check if="project has significant UX/UI components (Level 3-4 typically does)">
 
 - [ ] **Run UX specification workflow** (HIGHLY RECOMMENDED for user-facing systems) - Command: `workflow plan-project` then select "UX specification" - Or continue within this workflow if UI-heavy - Input: PRD.md, epics.md, solution-architecture.md (once available) - Output: ux-specification.md - Optional: AI Frontend Prompt for rapid prototyping - Note: Creates comprehensive UX/UI spec including IA, user flows, components
-      </check>
+
+<action>Update workflow status file to mark ux-spec as next step</action>
+<action>In status file, set next_action: "Run UX specification workflow"</action>
+<action>In status file, set next_command: "ux-spec"</action>
+<action>In status file, set next_agent: "PM"</action>
+<action>Add to decisions log: "PRD complete. UX workflow required due to UI components."</action>
+</check>
 
 ### Phase 2: Detailed Planning
 

src/modules/bmm/workflows/2-plan/prd/instructions-med.md

@@ -75,7 +75,7 @@
 **Format**: `FR001: [user capability]`
 
 <template-output>functional_requirements</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -119,7 +119,7 @@ Create simple epic list with story titles.
 Generate epic-stories.md with basic story structure.
 
 <template-output file="epic-stories.md">epic_stories</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -200,7 +200,13 @@ Since this is a Level {{project_level}} project, you need solutioning before imp
 <check if="project has significant UX/UI components (Level 1-2 with UI)">
 
 - [ ] **Run UX specification workflow** (HIGHLY RECOMMENDED for user-facing systems) - Command: `workflow plan-project` then select "UX specification" - Or continue within this workflow if UI-heavy - Input: PRD.md, epic-stories.md, solution-architecture.md (once available) - Output: ux-specification.md - Optional: AI Frontend Prompt for rapid prototyping - Note: Creates comprehensive UX/UI spec including IA, user flows, components
-      </check>
+
+<action>Update workflow status file to mark ux-spec as next step</action>
+<action>In status file, set next_action: "Run UX specification workflow"</action>
+<action>In status file, set next_command: "ux-spec"</action>
+<action>In status file, set next_agent: "PM"</action>
+<action>Add to decisions log: "PRD complete. UX workflow required due to UI components."</action>
+</check>
 
 ### Phase 2: Detailed Planning
 

src/modules/bmm/workflows/2-plan/tech-spec/instructions-sm.md

@@ -76,7 +76,7 @@
 **Deployment Strategy**: How to deploy the change
 <template-output file="tech-spec.md">deployment_strategy</template-output>
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 

src/modules/bmm/workflows/2-plan/ux/instructions-ux.md

@@ -81,7 +81,7 @@ What will guide all design decisions?
 <template-output>usability_goals</template-output>
 <template-output>design_principles</template-output>
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -106,7 +106,7 @@ What will guide all design decisions?
 
 <template-output>navigation_structure</template-output>
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -133,7 +133,7 @@ Create Mermaid diagram showing complete flow.
 
 </for-each>
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -193,7 +193,7 @@ Do you have existing brand guidelines to follow? (y/n)
 
 <template-output>spacing_layout</template-output>
 
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>