bmad-method 6.0.0-alpha.21 → 6.0.0-alpha.23

package/src/modules/bmm/workflows/2-plan-workflows/prd/{steps → steps-c}/step-06-innovation.md

@@ -2,20 +2,15 @@
 name: 'step-06-innovation'
 description: 'Detect and explore innovative aspects of the product (optional step)'
 
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-06-innovation.md'
-nextStepFile: '{workflow_path}/steps/step-07-project-type.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-07-project-type.md'
 outputFile: '{planning_artifacts}/prd.md'
 
 # Data Files
-projectTypesCSV: '{workflow_path}/project-types.csv'
+projectTypesCSV: '../data/project-types.csv'
 
 # 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'
 ---
 
@@ -33,30 +28,16 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on detecting and exploring innovative aspects of the product
 - 🎯 OPTIONAL STEP: Only proceed if innovation signals are detected
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Show your analysis before taking any action
 - ⚠️ Present A/P/C menu after generating innovation content
 - 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected
 
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
-- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper innovation insights
-- **P (Party Mode)**: Bring creative perspectives to explore innovation opportunities
-- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
-- PROTOCOLS always return to this step's A/P/C menu
-- User accepts/rejects protocol changes before proceeding
-
 ## CONTEXT BOUNDARIES:
 
 - Current document and frontmatter from previous steps are available
@@ -83,7 +64,7 @@ Detect and explore innovation patterns in the product, focusing on what makes it
 
 Load innovation signals specific to this project type:
 
-- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
+- Load `{projectTypesCSV}` completely
 - Find the row where `project_type` matches detected type from step-02
 - Extract `innovation_signals` (semicolon-separated list)
 - Extract `web_search_triggers` for potential innovation research
@@ -112,27 +93,22 @@ Match user descriptions against innovation_signals for their project_type:
 ### 3. Initial Innovation Screening
 
 Ask targeted innovation discovery questions:
-"As we explore {{project_name}}, I'm listening for what makes it innovative.
-
-**Innovation Indicators:**
-
-- Are you challenging any existing assumptions about how things work?
-- Are you combining technologies or approaches in new ways?
-- Is there something about this that hasn't been done before?
-
-What aspects of {{project_name}} feel most innovative to you?"
+- Guide exploration of what makes the product innovative
+- Explore if they're challenging existing assumptions
+- Ask about novel combinations of technologies/approaches
+- Identify what hasn't been done before
+- Understand which aspects feel most innovative
 
 ### 4. Deep Innovation Exploration (If Detected)
 
 If innovation signals are found, explore deeply:
 
 #### Innovation Discovery Questions:
-
-- "What makes it unique compared to existing solutions?"
-- "What assumption are you challenging?"
-- "How do we validate it works?"
-- "What's the fallback if it doesn't?"
-- "Has anyone tried this before?"
+- What makes it unique compared to existing solutions?
+- What assumption are you challenging?
+- How do we validate it works?
+- What's the fallback if it doesn't?
+- Has anyone tried this before?
 
 #### Market Context Research:
 
@@ -168,54 +144,43 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Innovation risks and fallbacks based on conversation]
 ```
 
-### 6. Present Content and Menu (Only if Innovation Detected)
-
-Show the generated innovation content and present choices:
-"I've identified some innovative aspects of {{project_name}} that differentiate it from existing solutions.
-
-**Here's what I'll add to the document:**
-
-[Show the complete markdown content from step 5]
-
-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper into these innovation opportunities
-[P] Party Mode - Bring creative perspectives to explore innovation further
-[C] Continue - Save this and move to Project Type Analysis (Step 7 of 11)"
+### 6. Present MENU OPTIONS (Only if Innovation Detected)
 
-### 7. Handle Menu Selection
+Present the innovation content for review, then display menu:
+- Show identified innovative aspects (using structure from section 5)
+- Highlight differentiation from existing solutions
+- Ask if they'd like to refine further, get other perspectives, or proceed
+- Present menu options naturally as part of conversation
 
-#### If 'A' (Advanced Elicitation):
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Project Type Analysis (Step 7 of 11)"
 
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current innovation content
-- Process the enhanced innovation insights that come back
-- Ask user: "Accept these improvements to the innovation analysis? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current innovation content, process the enhanced innovation insights that come back, ask user "Accept these improvements to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current innovation content, process the collaborative innovation exploration and ideation, ask user "Accept these changes to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu
 
-#### If 'P' (Party Mode):
-
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current innovation content
-- Process the collaborative innovation exploration and ideation
-- Ask user: "Accept these changes to the innovation analysis? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
-- Append the final content to `{outputFile}`
-- Update frontmatter: add this step name to the end of the steps completed array
-- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
 
 ## NO INNOVATION DETECTED:
 
 If no genuine innovation signals are found after exploration:
-"After exploring {{project_name}}, I don't see clear innovation signals that warrant a dedicated innovation section. This is perfectly fine - many successful products are excellent executions of existing concepts rather than breakthrough innovations.
+- Acknowledge that no clear innovation signals were found
+- Note this is fine - many successful products are excellent executions of existing concepts
+- Ask if they'd like to try finding innovative angles or proceed
+
+Display: "**Select:** [A] Advanced Elicitation - Let's try to find innovative angles [C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)"
 
-**Options:**
-[A] Force innovation exploration - Let's try to find innovative angles
-[C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)"
+### Menu Handling Logic:
+- IF A: Proceed with content generation anyway, then return to menu
+- IF C: Skip this step, then load, read entire file, then execute {nextStepFile}
 
-If user selects 'A', proceed with content generation anyway. If 'C', skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
+### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
 
 ## APPEND TO DOCUMENT:
 
@@ -247,7 +212,7 @@ When user selects 'C', append the content directly to the document using the str
 
 ## SKIP CONDITIONS:
 
-Skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` if:
+Skip this step and load `{nextStepFile}` if:
 
 - No innovation signals detected in conversation
 - Product is incremental improvement rather than breakthrough
@@ -256,6 +221,6 @@ Skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document (or step is skipped), load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
+After user selects 'C' and content is saved to document (or step is skipped), load `{nextStepFile}`.
 
 Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu (or confirms step skip)!

package/src/modules/bmm/workflows/2-plan-workflows/prd/{steps → steps-c}/step-07-project-type.md

@@ -2,20 +2,15 @@
 name: 'step-07-project-type'
 description: 'Conduct project-type specific discovery using CSV-driven guidance'
 
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-07-project-type.md'
-nextStepFile: '{workflow_path}/steps/step-08-scoping.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-08-scoping.md'
 outputFile: '{planning_artifacts}/prd.md'
 
 # Data Files
-projectTypesCSV: '{workflow_path}/project-types.csv'
+projectTypesCSV: '../data/project-types.csv'
 
 # 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'
 ---
 
@@ -33,30 +28,16 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on project-type specific requirements and technical considerations
 - 🎯 DATA-DRIVEN: Use CSV configuration to guide discovery
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Show your analysis before taking any action
 - ⚠️ Present A/P/C menu after generating project-type content
 - 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected
 
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
-- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper project-type insights
-- **P (Party Mode)**: Bring technical perspectives to explore project-specific requirements
-- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
-- PROTOCOLS always return to this step's A/P/C menu
-- User accepts/rejects protocol changes before proceeding
-
 ## CONTEXT BOUNDARIES:
 
 - Current document and frontmatter from previous steps are available
@@ -72,11 +53,23 @@ Conduct project-type specific discovery using CSV-driven guidance to define tech
 
 ### 1. Load Project-Type Configuration Data
 
-Load project-type specific configuration:
+**Attempt subprocess data lookup:**
+
+"Your task: Lookup data in {projectTypesCSV}
+
+**Search criteria:**
+- Find row where project_type matches {{projectTypeFromStep02}}
 
-- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
-- Find the row where `project_type` matches detected type from step-02
-- Extract these columns:
+**Return format:**
+Return ONLY the matching row as a YAML-formatted object with these fields:
+project_type, key_questions, required_sections, skip_sections, innovation_signals
+
+**Do NOT return the entire CSV - only the matching row.**"
+
+**Graceful degradation (if Task tool unavailable):**
+- Load the CSV file directly
+- Find the matching row manually
+- Extract required fields:
   - `key_questions` (semicolon-separated list of discovery questions)
   - `required_sections` (semicolon-separated list of sections to document)
   - `skip_sections` (semicolon-separated list of sections to skip)
@@ -164,47 +157,34 @@ When saving to document, append these Level 2 and Level 3 sections:
 [Implementation specific requirements based on conversation]
 ```
 
-### 6. Present Content and Menu
+### 6. Present MENU OPTIONS
 
-Show the generated project-type content and present choices:
-"I've documented the {project_type}-specific requirements for {{project_name}} based on our conversation and best practices for this type of product.
-
-**Here's what I'll add to the document:**
+Present the project-type content for review, then display menu:
 
-[Show the complete markdown content from step 5]
+"Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}.
 
-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper into these technical requirements
-[P] Party Mode - Bring technical expertise perspectives to validate requirements
-[C] Continue - Save this and move to Scoping (Step 8 of 11)"
-
-### 7. Handle Menu Selection
-
-#### If 'A' (Advanced Elicitation):
+**Here's what I'll add to the document:**
 
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current project-type content
-- Process the enhanced technical insights that come back
-- Ask user: "Accept these improvements to the technical requirements? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
+[Show the complete markdown content from section 5]
 
-#### If 'P' (Party Mode):
+**What would you like to do?**"
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements
-- Process the collaborative technical expertise and validation
-- Ask user: "Accept these changes to the technical requirements? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Scoping (Step 8 of 11)"
 
-#### If 'C' (Continue):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current project-type content, process the enhanced technical insights that come back, ask user "Accept these improvements to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the current project-type requirements, process the collaborative technical expertise and validation, ask user "Accept these changes to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu
 
-- Append the final content to `{outputFile}`
-- Update frontmatter: add this step name to the end of the steps completed array
-- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md`
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the document using the structure from step 5.
+When user selects 'C', append the content directly to the document using the structure from previous steps.
 
 ## SUCCESS METRICS:
 
@@ -252,6 +232,6 @@ When user selects 'C', append the content directly to the document using the str
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` to define project scope.
+After user selects 'C' and content is saved to document, load `{nextStepFile}` to define project scope.
 
 Remember: Do NOT proceed to step-08 (Scoping) until user explicitly selects 'C' from the A/P/C menu and content is saved!

package/src/modules/bmm/workflows/2-plan-workflows/prd/{steps → steps-c}/step-08-scoping.md

@@ -2,17 +2,12 @@
 name: 'step-08-scoping'
 description: 'Define MVP boundaries and prioritize features across development phases'
 
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-
 # File References
-thisStepFile: '{workflow_path}/steps/step-08-scoping.md'
-nextStepFile: '{workflow_path}/steps/step-09-functional.md'
-workflowFile: '{workflow_path}/workflow.md'
+nextStepFile: './step-09-functional.md'
 outputFile: '{planning_artifacts}/prd.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 +25,7 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on strategic scope decisions that keep projects viable
 - 🎯 EMPHASIZE lean MVP thinking while preserving long-term vision
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -37,23 +33,9 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 - 📚 Review the complete PRD document built so far
 - ⚠️ Present A/P/C menu after generating scoping decisions
 - 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]` before loading next step
+- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted
 - 🚫 FORBIDDEN to load next step until C is selected
 
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
-- **A (Advanced Elicitation)**: Use discovery protocols to explore innovative scoping approaches
-- **P (Party Mode)**: Bring multiple perspectives to ensure comprehensive scope decisions
-- **C (Continue)**: Save the scoping decisions and proceed to functional requirements
-
-## PROTOCOL INTEGRATION:
-
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
-- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
-- User accepts/rejects protocol changes before proceeding
 
 ## CONTEXT BOUNDARIES:
 
@@ -71,80 +53,46 @@ Conduct comprehensive scoping exercise to define MVP boundaries and prioritize f
 ### 1. Review Current PRD State
 
 Analyze everything documented so far:
-"I've reviewed your complete PRD so far. Here's what we've established:
-
-**Product Vision & Success:**
-{{summary_of_vision_and_success_criteria}}
-
-**User Journeys:** {{number_of_journeys}} mapped with rich narratives
-
-**Domain & Innovation Focus:**
-{{summary_of_domain_requirements_and_innovation}}
-
-**Current Scope Implications:**
-Based on everything we've documented, this looks like it could be:
-
-- [ ] Simple MVP (small team, lean scope)
-- [ ] Medium scope (moderate team, balanced features)
-- [ ] Complex project (large team, comprehensive scope)
-
-Does this initial assessment feel right, or do you see this differently?"
+- Present synthesis of established vision, success criteria, journeys
+- Assess domain and innovation focus
+- Evaluate scope implications: simple MVP, medium, or complex project
+- Ask if initial assessment feels right or if they see it differently
 
 ### 2. Define MVP Strategy
 
 Facilitate strategic MVP decisions:
-
-"Let's think strategically about your launch strategy:
-
-**MVP Philosophy Options:**
-
-1. **Problem-Solving MVP**: Solve the core problem with minimal features
-2. **Experience MVP**: Deliver the key user experience with basic functionality
-3. **Platform MVP**: Build the foundation for future expansion
-4. **Revenue MVP**: Generate early revenue with essential features
-
-**Critical Questions:**
-
-- What's the minimum that would make users say 'this is useful'?
-- What would make investors/partners say 'this has potential'?
-- What's the fastest path to validated learning?
-
-**Which MVP approach feels right for {{project_name}}?**"
+- Explore MVP philosophy options: problem-solving, experience, platform, or revenue MVP
+- Ask critical questions:
+  - What's the minimum that would make users say 'this is useful'?
+  - What would make investors/partners say 'this has potential'?
+  - What's the fastest path to validated learning?
+- Guide toward appropriate MVP approach for their product
 
 ### 3. Scoping Decision Framework
 
 Use structured decision-making for scope:
 
 **Must-Have Analysis:**
-"Let's identify absolute MVP necessities. For each journey and success criterion, ask:
-
-- **Without this, does the product fail?** (Y/N)
-- **Can this be manual initially?** (Y/N)
-- **Is this a deal-breaker for early adopters?** (Y/N)
-
-**Current Document Review:**
-Looking at your user journeys, what are the absolute core experiences that must work?
-
-{{analyze_journeys_for_mvp_essentials}}"
+- Guide identification of absolute MVP necessities
+- For each journey and success criterion, ask:
+  - Without this, does the product fail?
+  - Can this be manual initially?
+  - Is this a deal-breaker for early adopters?
+- Analyze journeys for MVP essentials
 
 **Nice-to-Have Analysis:**
-"Let's also identify what could be added later:
-
-**Post-MVP Enhancements:**
-
-- Features that enhance but aren't essential
-- User types that can be added later
-- Advanced functionality that builds on MVP
-
-**What features could we add in versions 2, 3, etc.?**"
+- Identify what could be added later:
+  - Features that enhance but aren't essential
+  - User types that can be added later
+  - Advanced functionality that builds on MVP
+- Ask what features could be added in versions 2, 3, etc.
 
 ### 4. Progressive Feature Roadmap
 
 Create phased development approach:
-
-"Let's map your features across development phases:
-
-**Phase 1: MVP**
+- Guide mapping of features across development phases
+- Structure as Phase 1 (MVP), Phase 2 (Growth), Phase 3 (Vision)
+- Ensure clear progression and dependencies
 
 - Core user value delivery
 - Essential user journeys
@@ -224,44 +172,26 @@ Prepare comprehensive scoping section:
 **Resource Risks:** {{contingency_approach}}
 ```
 
-### 7. Present Content and Menu
-
-Show the scoping decisions and present choices:
-
-"I've analyzed your complete PRD and created a strategic scoping plan for {{project_name}}.
-
-**Here's what I'll add to the document:**
-
-[Show the complete markdown content from step 6]
-
-**What would you like to do?**
-[A] Advanced Elicitation - Explore alternative scoping strategies
-[P] Party Mode - Bring different perspectives on MVP and roadmap decisions
-[C] Continue - Save scoping decisions and move to Functional Requirements (Step 9 of 11)"
-
-### 8. Handle Menu Selection
-
-#### If 'A' (Advanced Elicitation):
-
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current scoping analysis
-- Process enhanced scoping insights that come back
-- Ask user: "Accept these improvements to the scoping decisions? (y/n)"
-- If yes: Update content, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
+### 7. Present MENU OPTIONS
 
-#### If 'P' (Party Mode):
+Present the scoping decisions for review, then display menu:
+- Show strategic scoping plan (using structure from step 6)
+- Highlight MVP boundaries and phased roadmap
+- Ask if they'd like to refine further, get other perspectives, or proceed
+- Present menu options naturally as part of conversation
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with scoping context
-- Process collaborative insights on MVP and roadmap decisions
-- Ask user: "Accept these changes to the scoping decisions? (y/n)"
-- If yes: Update content, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
+Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Functional Requirements (Step 9 of 11)"
 
-#### If 'C' (Continue):
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask} with the current scoping analysis, process the enhanced insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF P: Execute {partyModeWorkflow} with the scoping context, process the collaborative insights on MVP and roadmap decisions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user respond, then redisplay menu
 
-- Append the final content to `{outputFile}`
-- Update frontmatter: add this step name to the end of the steps completed array
-- Load `./step-09-functional.md`
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
 
 ## APPEND TO DOCUMENT:
 
@@ -293,6 +223,6 @@ When user selects 'C', append the content directly to the document using the str
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-09-functional.md`.
+After user selects 'C' and content is saved to document, load {nextStepFile}.
 
 Remember: Do NOT proceed to step-09 until user explicitly selects 'C' from the A/P/C menu and content is saved!