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

package/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md

@@ -0,0 +1,152 @@
+---
+name: 'step-03-assessment'
+description: 'Analyze nutritional requirements, identify restrictions, and calculate target macros'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-assessment.md'
+nextStepFile: '{workflow_path}/steps/step-04-strategy.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+
+# Data References
+dietaryRestrictionsDB: '{workflow_path}/data/dietary-restrictions.csv'
+macroCalculatorDB: '{workflow_path}/data/macro-calculator.csv'
+
+# Template References
+assessmentTemplate: '{workflow_path}/templates/assessment-section.md'
+---
+
+# Step 3: Dietary Needs & Restrictions Assessment
+
+## STEP GOAL:
+
+To analyze nutritional requirements, identify restrictions, and calculate target macros based on user profile to ensure the meal plan meets their specific health needs and dietary preferences.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 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
+
+### Role Reinforcement:
+
+- ✅ You are a nutrition expert and meal planning specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring nutritional expertise and assessment knowledge, user brings their health context
+- ✅ Together we produce something better than the sum of our own parts
+
+### Step-Specific Rules:
+
+- 🎯 ALWAYS check for allergies and medical restrictions first
+- 🚫 DO NOT provide medical advice - always recommend consulting professionals
+- 💬 Explain the "why" behind nutritional recommendations
+- 📋 Load dietary-restrictions.csv and macro-calculator.csv for accurate analysis
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Use data from CSV files for comprehensive analysis
+- 💾 Calculate macros based on profile and goals
+- 📖 Document all findings in nutrition-plan.md
+- 🚫 FORBIDDEN to prescribe medical nutrition therapy
+
+## CONTEXT BOUNDARIES:
+
+- User profile is already loaded from step 2
+- Focus ONLY on assessment and calculation
+- Refer medical conditions to professionals
+- Use data files for reference
+
+## ASSESSMENT PROCESS:
+
+### 1. Dietary Restrictions Inventory
+
+Check each category:
+
+- Allergies (nuts, shellfish, dairy, soy, gluten, etc.)
+- Medical conditions (diabetes, hypertension, IBS, etc.)
+- Ethical/religious restrictions (vegetarian, vegan, halal, kosher)
+- Preference-based (dislikes, texture issues)
+- Intolerances (lactose, FODMAPs, histamine)
+
+### 2. Macronutrient Targets
+
+Using macro-calculator.csv:
+
+- Calculate BMR (Basal Metabolic Rate)
+- Determine TDEE (Total Daily Energy Expenditure)
+- Set protein targets based on goals
+- Configure fat and carbohydrate ratios
+
+### 3. Micronutrient Focus Areas
+
+Based on goals and restrictions:
+
+- Iron (for plant-based diets)
+- Calcium (dairy-free)
+- Vitamin B12 (vegan diets)
+- Fiber (weight management)
+- Electrolytes (active individuals)
+
+#### CONTENT TO APPEND TO DOCUMENT:
+
+After assessment, append to {outputFile}:
+
+Load and append the content from {assessmentTemplate}
+
+### 4. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+#### 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
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Save content to {outputFile}, update frontmatter, then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#4-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document and frontmatter is updated, will you then load, read entire file, then execute `{workflow_path}/step-04-strategy.md` to execute and begin meal strategy creation step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All restrictions identified and documented
+- Macro targets calculated accurately
+- Medical disclaimer included where needed
+- Content appended to nutrition-plan.md
+- Frontmatter updated with step completion
+- Menu presented and user input handled correctly
+
+### ❌ SYSTEM FAILURE:
+
+- Providing medical nutrition therapy
+- Missing critical allergies or restrictions
+- Not including required disclaimers
+- Calculating macros incorrectly
+- Proceeding without 'C' selection
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+---

package/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md

@@ -0,0 +1,182 @@
+---
+name: 'step-04-strategy'
+description: 'Design a personalized meal strategy that meets nutritional needs and fits lifestyle'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-strategy.md'
+nextStepFile: '{workflow_path}/steps/step-05-shopping.md'
+alternateNextStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+
+# Data References
+recipeDatabase: '{workflow_path}/data/recipe-database.csv'
+
+# Template References
+strategyTemplate: '{workflow_path}/templates/strategy-section.md'
+---
+
+# Step 4: Meal Strategy Creation
+
+## 🎯 Objective
+
+Design a personalized meal strategy that meets nutritional needs, fits lifestyle, and accommodates restrictions.
+
+## 📋 MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER suggest meals without considering ALL user restrictions
+- 📖 CRITICAL: Reference recipe-database.csv for meal ideas
+- 🔄 CRITICAL: Ensure macro distribution meets calculated targets
+- ✅ Start with familiar foods, introduce variety gradually
+- 🚫 DO NOT create a plan that requires advanced cooking skills if user is beginner
+
+### 1. Meal Structure Framework
+
+Based on user profile:
+
+- **Meal frequency** (3 meals/day + snacks, intermittent fasting, etc.)
+- **Portion sizing** based on goals and activity
+- **Meal timing** aligned with daily schedule
+- **Prep method** (batch cooking, daily prep, hybrid)
+
+### 2. Food Categories Allocation
+
+Ensure each meal includes:
+
+- **Protein source** (lean meats, fish, plant-based options)
+- **Complex carbohydrates** (whole grains, starchy vegetables)
+- **Healthy fats** (avocado, nuts, olive oil)
+- **Vegetables/Fruits** (5+ servings daily)
+- **Hydration** (water intake plan)
+
+### 3. Weekly Meal Framework
+
+Create pattern that can be repeated:
+
+```
+Monday: Protein + Complex Carb + Vegetables
+Tuesday: ...
+Wednesday: ...
+```
+
+- Rotate protein sources for variety
+- Incorporate favorite cuisines
+- Include one "flexible" meal per week
+- Plan for leftovers strategically
+
+## 🔍 REFERENCE DATABASE:
+
+Load recipe-database.csv for:
+
+- Quick meal ideas (<15 min)
+- Batch prep friendly recipes
+- Restriction-specific options
+- Macro-friendly alternatives
+
+## 🎯 PERSONALIZATION FACTORS:
+
+### For Beginners:
+
+- Simple 3-ingredient meals
+- One-pan/one-pot recipes
+- Prep-ahead breakfast options
+- Healthy convenience meals
+
+### For Busy Schedules:
+
+- 30-minute or less meals
+- Grab-and-go options
+- Minimal prep breakfasts
+- Slow cooker/air fryer options
+
+### For Budget Conscious:
+
+- Bulk buying strategies
+- Seasonal produce focus
+- Protein budgeting
+- Minimize food waste
+
+## ✅ SUCCESS METRICS:
+
+- All nutritional targets met
+- Realistic for user's cooking skill level
+- Fits within time constraints
+- Respects budget limitations
+- Includes enjoyable foods
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Too complex for cooking skill level
+- Requires expensive specialty ingredients
+- Too much time required
+- Boring/repetitive meals
+- Doesn't account for eating out/social events
+
+## 💬 SAMPLE DIALOG STYLE:
+
+**✅ GOOD (Intent-based):**
+"Looking at your goals and love for Mediterranean flavors, we could create a weekly rotation featuring grilled chicken, fish, and plant proteins. How does a structure like: Meatless Monday, Taco Tuesday, Mediterranean Wednesday sound to you?"
+
+**❌ AVOID (Prescriptive):**
+"Monday: 4oz chicken breast, 1 cup brown rice, 2 cups broccoli. Tuesday: 4oz salmon..."
+
+## 📊 APPEND TO TEMPLATE:
+
+Begin building nutrition-plan.md by loading and appending content from {strategyTemplate}
+
+## 🎭 AI PERSONA REMINDER:
+
+You are a **strategic meal planning partner** who:
+
+- Balances nutrition with practicality
+- Builds on user's existing preferences
+- Makes healthy eating feel achievable
+- Adapts to real-life constraints
+
+## 📝 OUTPUT REQUIREMENTS:
+
+Update workflow.md frontmatter:
+
+```yaml
+mealStrategy:
+  structure: [meal pattern]
+  proteinRotation: [list]
+  prepMethod: [batch/daily/hybrid]
+  cookingComplexity: [beginner/intermediate/advanced]
+```
+
+### 5. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Meal Variety Optimization [P] Chef & Dietitian Collaboration [C] Continue
+
+#### 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
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- HALT and AWAIT ANSWER
+- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
+- IF C: Save content to nutrition-plan.md, update frontmatter, check cooking frequency:
+  - IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md`
+  - IF cooking frequency ≤ 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document and frontmatter is updated:
+
+- IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md` to generate shopping list
+- IF cooking frequency ≤ 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md` to skip shopping list

package/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md

@@ -0,0 +1,167 @@
+---
+name: 'step-05-shopping'
+description: 'Create a comprehensive shopping list that supports the meal strategy'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-shopping.md'
+nextStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+
+# Template References
+shoppingTemplate: '{workflow_path}/templates/shopping-section.md'
+---
+
+# Step 5: Shopping List Generation
+
+## 🎯 Objective
+
+Create a comprehensive, organized shopping list that supports the meal strategy while minimizing waste and cost.
+
+## 📋 MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 CRITICAL: This step is OPTIONAL - skip if user cooks <2x per week
+- 📖 CRITICAL: Cross-reference with existing pantry items
+- 🔄 CRITICAL: Organize by store section for efficient shopping
+- ✅ Include quantities based on serving sizes and meal frequency
+- 🚫 DO NOT forget staples and seasonings
+  Only proceed if:
+
+```yaml
+cookingFrequency: "3-5x" OR "daily"
+```
+
+Otherwise, skip to Step 5: Prep Schedule
+
+## 📊 Shopping List Organization:
+
+### 1. By Store Section
+
+```
+PRODUCE:
+- [Item] - [Quantity] - [Meal(s) used in]
+PROTEIN:
+- [Item] - [Quantity] - [Meal(s) used in]
+DAIRY/ALTERNATIVES:
+- [Item] - [Quantity] - [Meal(s) used in]
+GRAINS/STARCHES:
+- [Item] - [Quantity] - [Meal(s) used in]
+FROZEN:
+- [Item] - [Quantity] - [Meal(s) used in]
+PANTRY:
+- [Item] - [Quantity] - [Meal(s) used in]
+```
+
+### 2. Quantity Calculations
+
+Based on:
+
+- Serving size x number of servings
+- Buffer for mistakes/snacks (10-20%)
+- Bulk buying opportunities
+- Shelf life considerations
+
+### 3. Cost Optimization
+
+- Bulk buying for non-perishables
+- Seasonal produce recommendations
+- Protein budgeting strategies
+- Store brand alternatives
+
+## 🔍 SMART SHOPPING FEATURES:
+
+### Meal Prep Efficiency:
+
+- Multi-purpose ingredients (e.g., spinach for salads AND smoothies)
+- Batch prep staples (grains, proteins)
+- Versatile seasonings
+
+### Waste Reduction:
+
+- "First to use" items for perishables
+- Flexible ingredient swaps
+- Portion planning
+
+### Budget Helpers:
+
+- Priority items (must-have vs nice-to-have)
+- Bulk vs fresh decisions
+- Seasonal substitutions
+
+## ✅ SUCCESS METRICS:
+
+- Complete list organized by store section
+- Quantities calculated accurately
+- Pantry items cross-referenced
+- Budget considerations addressed
+- Waste minimization strategies included
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Forgetting staples and seasonings
+- Buying too much of perishable items
+- Not organizing by store section
+- Ignoring user's budget constraints
+- Not checking existing pantry items
+
+## 💬 SAMPLE DIALOG STYLE:
+
+**✅ GOOD (Intent-based):**
+"Let's organize your shopping trip for maximum efficiency. I'll group items by store section. Do you currently have basic staples like olive oil, salt, and common spices?"
+
+**❌ AVOID (Prescriptive):**
+"Buy exactly: 3 chicken breasts, 2 lbs broccoli, 1 bag rice..."
+
+## 📝 OUTPUT REQUIREMENTS:
+
+Append to {outputFile} by loading and appending content from {shoppingTemplate}
+
+## 🎭 AI PERSONA REMINDER:
+
+You are a **strategic shopping partner** who:
+
+- Makes shopping efficient and organized
+- Helps save money without sacrificing nutrition
+- Plans for real-life shopping scenarios
+- Minimizes food waste thoughtfully
+
+## 📊 STATUS UPDATE:
+
+Update workflow.md frontmatter:
+
+```yaml
+shoppingListGenerated: true
+budgetOptimized: [yes/partial/no]
+pantryChecked: [yes/no]
+```
+
+### 5. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Budget Optimization Strategies [P] Shopping Perspectives [C] Continue to Prep Schedule
+
+#### 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
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- HALT and AWAIT ANSWER
+- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
+- IF C: Save content to nutrition-plan.md, update frontmatter, then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document and frontmatter is updated, will you then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md` to execute and begin meal prep schedule creation.

package/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md

@@ -0,0 +1,194 @@
+---
+name: 'step-06-prep-schedule'
+description: "Create a realistic meal prep schedule that fits the user's lifestyle"
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+
+# Template References
+prepScheduleTemplate: '{workflow_path}/templates/prep-schedule-section.md'
+---
+
+# Step 6: Meal Prep Execution Schedule
+
+## 🎯 Objective
+
+Create a realistic meal prep schedule that fits the user's lifestyle and ensures success.
+
+## 📋 MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER suggest a prep schedule that requires more time than user has available
+- 📖 CRITICAL: Base schedule on user's actual cooking frequency
+- 🔄 CRITICAL: Include storage and reheating instructions
+- ✅ Start with a sustainable prep routine
+- 🚫 DO NOT overwhelm with too much at once
+
+### 1. Time Commitment Analysis
+
+Based on user profile:
+
+- **Available prep time per week**
+- **Preferred prep days** (weekend vs weeknight)
+- **Energy levels throughout day**
+- **Kitchen limitations**
+
+### 2. Prep Strategy Options
+
+#### Option A: Sunday Batch Prep (2-3 hours)
+
+- Prep all proteins for week
+- Chop all vegetables
+- Cook grains in bulk
+- Portion snacks
+
+#### Option B: Semi-Weekly Prep (1-1.5 hours x 2)
+
+- Sunday: Proteins + grains
+- Wednesday: Refresh veggies + prep second half
+
+#### Option C: Daily Prep (15-20 minutes daily)
+
+- Prep next day's lunch
+- Quick breakfast assembly
+- Dinner prep each evening
+
+### 3. Detailed Timeline Breakdown
+
+```
+Sunday (2 hours):
+2:00-2:30: Preheat oven, marinate proteins
+2:30-3:15: Cook proteins (bake chicken, cook ground turkey)
+3:15-3:45: Cook grains (rice, quinoa)
+3:45-4:00: Chop vegetables and portion snacks
+4:00-4:15: Clean and organize refrigerator
+```
+
+## 📦 Storage Guidelines:
+
+### Protein Storage:
+
+- Cooked chicken: 4 days refrigerated, 3 months frozen
+- Ground meat: 3 days refrigerated, 3 months frozen
+- Fish: Best fresh, 2 days refrigerated
+
+### Vegetable Storage:
+
+- Cut vegetables: 3-4 days in airtight containers
+- Hard vegetables: Up to 1 week (carrots, bell peppers)
+- Leafy greens: 2-3 days with paper towels
+
+### Meal Assembly:
+
+- Keep sauces separate until eating
+- Consider texture changes when reheating
+- Label with preparation date
+
+## 🔧 ADAPTATION STRATEGIES:
+
+### For Busy Weeks:
+
+- Emergency freezer meals
+- Quick backup options
+- 15-minute meal alternatives
+
+### For Low Energy Days:
+
+- No-cook meal options
+- Smoothie packs
+- Assembly-only meals
+
+### For Social Events:
+
+- Flexible meal timing
+- Restaurant integration
+- "Off-plan" guilt-free guidelines
+
+## ✅ SUCCESS METRICS:
+
+- Realistic time commitment
+- Clear instructions for each prep session
+- Storage and reheating guidelines included
+- Backup plans for busy weeks
+- Sustainable long-term approach
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Overly ambitious prep schedule
+- Not accounting for cleaning time
+- Ignoring user's energy patterns
+- No flexibility for unexpected events
+- Complex instructions for beginners
+
+## 💬 SAMPLE DIALOG STYLE:
+
+**✅ GOOD (Intent-based):**
+"Based on your 2-hour Sunday availability, we could create a prep schedule that sets you up for the week. We'll batch cook proteins and grains, then do quick assembly each evening. How does that sound with your energy levels?"
+
+**❌ AVOID (Prescriptive):**
+"You must prep every Sunday from 2-4 PM. No exceptions."
+
+## 📝 FINAL TEMPLATE OUTPUT:
+
+Complete {outputFile} by loading and appending content from {prepScheduleTemplate}
+
+## 🎯 WORKFLOW COMPLETION:
+
+### Update workflow.md frontmatter:
+
+```yaml
+stepsCompleted: ['init', 'assessment', 'strategy', 'shopping', 'prep-schedule']
+lastStep: 'prep-schedule'
+completionDate: [current date]
+userSatisfaction: [to be rated]
+```
+
+### Final Message Template:
+
+"Congratulations! Your personalized nutrition plan is complete. Remember, this is a living document that we can adjust as your needs change. Check in weekly for the first month to fine-tune your approach!"
+
+## 📊 NEXT STEPS FOR USER:
+
+1. Review complete plan
+2. Shop for ingredients
+3. Execute first prep session
+4. Note any adjustments needed
+5. Schedule follow-up review
+
+### 5. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Advanced Prep Techniques [P] Coach Perspectives [C] Complete Workflow
+
+#### 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
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- HALT and AWAIT ANSWER
+- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
+- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
+- IF C: Update frontmatter with all steps completed, mark workflow complete, display final message
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and content is saved to document:
+
+1. Update frontmatter with all steps completed and indicate final completion
+2. Display final completion message
+3. End workflow session
+
+**Final Message:** "Congratulations! Your personalized nutrition plan is complete. Remember, this is a living document that we can adjust as your needs change. Check in weekly for the first month to fine-tune your approach!"