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

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

@@ -0,0 +1,177 @@
+---
+name: 'step-01-init'
+description: 'Initialize the nutrition plan workflow by detecting continuation state and creating output document'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+nextStepFile: '{workflow_path}/steps/step-02-profile.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+templateFile: '{workflow_path}/templates/nutrition-plan.md'
+continueFile: '{workflow_path}/steps/step-01b-continue.md'
+# Template References
+# This step doesn't use content templates, only the main template
+---
+
+# Step 1: Workflow Initialization
+
+## 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 structured planning, user brings their personal preferences and lifestyle constraints
+- ✅ Together we produce something better than the sum of our own parts
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on initialization and setup
+- 🚫 FORBIDDEN to look ahead to future steps
+- 💬 Handle initialization professionally
+- 🚪 DETECT existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show analysis before taking any action
+- 💾 Initialize document and update frontmatter
+- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until setup is complete
+
+## CONTEXT BOUNDARIES:
+
+- Variables from workflow.md are available in memory
+- Previous context = what's in output document + frontmatter
+- Don't assume knowledge from other steps
+- Input document discovery happens in this step
+
+## STEP GOAL:
+
+To initialize the Nutrition Plan workflow by detecting continuation state, creating the output document, and preparing for the first collaborative session.
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow
+
+First, check if the output document already exists:
+
+- Look for file at `{output_folder}/nutrition-plan-{project_name}.md`
+- If exists, read the complete file including frontmatter
+- If not exists, this is a fresh workflow
+
+### 2. Handle Continuation (If Document Exists)
+
+If the document exists and has frontmatter with `stepsCompleted`:
+
+- **STOP here** and load `./step-01b-continue.md` immediately
+- Do not proceed with any initialization tasks
+- Let step-01b handle the continuation logic
+
+### 3. Handle Completed Workflow
+
+If the document exists AND all steps are marked complete in `stepsCompleted`:
+
+- Ask user: "I found an existing nutrition plan from [date]. Would you like to:
+  1. Create a new nutrition plan
+  2. Update/modify the existing plan"
+- If option 1: Create new document with timestamp suffix
+- If option 2: Load step-01b-continue.md
+
+### 4. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+This workflow doesn't require input documents, but check for:
+**Existing Health Information (Optional):**
+
+- Look for: `{output_folder}/*health*.md`
+- Look for: `{output_folder}/*goals*.md`
+- If found, load completely and add to `inputDocuments` frontmatter
+
+#### B. Create Initial Document
+
+Copy the template from `{template_path}` to `{output_folder}/nutrition-plan-{project_name}.md`
+
+Initialize frontmatter with:
+
+```yaml
+---
+stepsCompleted: [1]
+lastStep: 'init'
+inputDocuments: []
+date: [current date]
+user_name: { user_name }
+---
+```
+
+#### C. Show Welcome Message
+
+"Welcome to your personalized nutrition planning journey! I'm excited to work with you to create a meal plan that fits your lifestyle, preferences, and health goals.
+
+Let's begin by getting to know you and your nutrition goals."
+
+## ✅ SUCCESS METRICS:
+
+- Document created from template
+- Frontmatter initialized with step 1 marked complete
+- User welcomed to the process
+- Ready to proceed to step 2
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Proceeding with step 2 without document initialization
+- Not checking for existing documents properly
+- Creating duplicate documents
+- Skipping welcome message
+
+### 7. Present MENU OPTIONS
+
+Display: **Proceeding to user profile collection...**
+
+#### EXECUTION RULES:
+
+- This is an initialization step with no user choices
+- Proceed directly to next step after setup
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- After setup completion, immediately load, read entire file, then execute `{workflow_path}/step-02-profile.md` to begin user profile collection
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Document created from template
+- Frontmatter initialized with step 1 marked complete
+- User welcomed to the process
+- Ready to proceed to step 2
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN initialization setup is complete and document is created, will you then immediately load, read entire file, then execute `{workflow_path}/step-02-profile.md` to begin user profile collection.
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with step 2 without document initialization
+- Not checking for existing documents properly
+- Creating duplicate documents
+- Skipping welcome message
+
+**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-01b-continue.md

@@ -0,0 +1,150 @@
+---
+name: 'step-01b-continue'
+description: 'Handle workflow continuation from previous session'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+# Template References
+# This step doesn't use content templates, reads from existing output file
+---
+
+# Step 1B: Workflow Continuation
+
+## STEP GOAL:
+
+To resume the nutrition planning workflow from where it was left off, ensuring smooth continuation without loss of context.
+
+## 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
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring nutritional expertise and structured planning, user brings their personal preferences and lifestyle constraints
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on analyzing and resuming workflow state
+- 🚫 FORBIDDEN to modify content completed in previous steps
+- 💬 Maintain continuity with previous sessions
+- 🚪 DETECT exact continuation point from frontmatter
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking action
+- 💾 Keep existing frontmatter `stepsCompleted` values
+- 📖 Review the template content already generated
+- 🚫 FORBIDDEN to modify content completed in previous steps
+
+## CONTEXT BOUNDARIES:
+
+- Current nutrition-plan.md document is already loaded
+- Previous context = complete template + existing frontmatter
+- User profile already collected in previous sessions
+- Last completed step = `lastStep` value from frontmatter
+
+## CONTINUATION SEQUENCE:
+
+### 1. Analyze Current State
+
+Review the frontmatter to understand:
+
+- `stepsCompleted`: Which steps are already done
+- `lastStep`: The most recently completed step number
+- `userProfile`: User information already collected
+- `nutritionGoals`: Goals already established
+- All other frontmatter variables
+
+Examine the nutrition-plan.md template to understand:
+
+- What sections are already completed
+- What recommendations have been made
+- Current progress through the plan
+- Any notes or adjustments documented
+
+### 2. Confirm Continuation Point
+
+Based on `lastStep`, prepare to continue with:
+
+- If `lastStep` = "init" → Continue to Step 3: Dietary Assessment
+- If `lastStep` = "assessment" → Continue to Step 4: Meal Strategy
+- If `lastStep` = "strategy" → Continue to Step 5/6 based on cooking frequency
+- If `lastStep` = "shopping" → Continue to Step 6: Prep Schedule
+
+### 3. Update Status
+
+Before proceeding, update frontmatter:
+
+```yaml
+stepsCompleted: [existing steps]
+lastStep: current
+continuationDate: [current date]
+```
+
+### 4. Welcome Back Dialog
+
+"Welcome back! I see we've completed [X] steps of your nutrition plan. We last worked on [brief description]. Are you ready to continue with [next step]?"
+
+### 5. Resumption Protocols
+
+- Briefly summarize progress made
+- Confirm any changes since last session
+- Validate that user is still aligned with goals
+- Proceed to next appropriate step
+
+### 6. Present MENU OPTIONS
+
+Display: **Resuming workflow - Select an Option:** [C] Continue
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- 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 C: Update frontmatter with continuation info, then load, read entire file, then execute appropriate next step based on `lastStep`
+  - IF lastStep = "init": load {workflow_path}/step-03-assessment.md
+  - IF lastStep = "assessment": load {workflow_path}/step-04-strategy.md
+  - IF lastStep = "strategy": check cooking frequency, then load appropriate step
+  - IF lastStep = "shopping": load {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 continuation analysis is complete, will you then update frontmatter and load, read entire file, then execute the appropriate next step file.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Correctly identified last completed step
+- User confirmed readiness to continue
+- Frontmatter updated with continuation date
+- Workflow resumed at appropriate step
+
+### ❌ SYSTEM FAILURE:
+
+- Skipping analysis of existing state
+- Modifying content from previous steps
+- Loading wrong next step
+- Not updating frontmatter properly
+
+**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-02-profile.md

@@ -0,0 +1,164 @@
+---
+name: 'step-02-profile'
+description: 'Gather comprehensive user profile information through collaborative conversation'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
+
+# File References (all use {variable} format in file)
+thisStepFile: '{workflow_path}/steps/step-02-profile.md'
+nextStepFile: '{workflow_path}/steps/step-03-assessment.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
+profileTemplate: '{workflow_path}/templates/profile-section.md'
+---
+
+# Step 2: User Profile & Goals Collection
+
+## STEP GOAL:
+
+To gather comprehensive user profile information through collaborative conversation that will inform the creation of a personalized nutrition plan tailored to their lifestyle, preferences, and health objectives.
+
+## 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
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring nutritional expertise and structured planning
+- ✅ User brings their personal preferences and lifestyle constraints
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on collecting profile and goal information
+- 🚫 FORBIDDEN to provide meal recommendations or nutrition advice in this step
+- 💬 Ask questions conversationally, not like a form
+- 🚫 DO NOT skip any profile section - each affects meal recommendations
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Engage in natural conversation to gather profile information
+- 💾 After collecting all information, append to {outputFile}
+- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
+- 🚫 FORBIDDEN to load next step until user selects 'C' and content is saved
+
+## CONTEXT BOUNDARIES:
+
+- Document and frontmatter are already loaded from initialization
+- Focus ONLY on collecting user profile and goals
+- Don't provide meal recommendations in this step
+- This is about understanding, not prescribing
+
+## PROFILE COLLECTION PROCESS:
+
+### 1. Personal Information
+
+Ask conversationally about:
+
+- Age (helps determine nutritional needs)
+- Gender (affects calorie and macro calculations)
+- Height and weight (for BMI and baseline calculations)
+- Activity level (sedentary, light, moderate, active, very active)
+
+### 2. Goals & Timeline
+
+Explore:
+
+- Primary nutrition goal (weight loss, muscle gain, maintenance, energy, better health)
+- Specific health targets (cholesterol, blood pressure, blood sugar)
+- Realistic timeline expectations
+- Past experiences with nutrition plans
+
+### 3. Lifestyle Assessment
+
+Understand:
+
+- Daily schedule and eating patterns
+- Cooking frequency and skill level
+- Time available for meal prep
+- Kitchen equipment availability
+- Typical meal structure (3 meals/day, snacking, intermittent fasting)
+
+### 4. Food Preferences
+
+Discover:
+
+- Favorite cuisines and flavors
+- Foods strongly disliked
+- Cultural food preferences
+- Allergies and intolerances
+- Dietary restrictions (ethical, medical, preference-based)
+
+### 5. Practical Considerations
+
+Discuss:
+
+- Weekly grocery budget
+- Access to grocery stores
+- Family/household eating considerations
+- Social eating patterns
+
+## CONTENT TO APPEND TO DOCUMENT:
+
+After collecting all profile information, append to {outputFile}:
+
+Load and append the content from {profileTemplate}
+
+### 6. 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 only then load, read entire file, then execute {nextStepFile}
+- 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 and frontmatter is updated, will you then load, read entire file, then execute {nextStepFile} to execute and begin dietary needs assessment step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Profile collected through conversation (not interrogation)
+- All user preferences documented
+- Content appended to {outputFile}
+- {outputFile} frontmatter updated with step completion
+- Menu presented after completing every other step first in order and user input handled correctly
+
+### ❌ SYSTEM FAILURE:
+
+- Generating content without user input
+- Skipping profile sections
+- Providing meal recommendations in this step
+- Proceeding to next step without 'C' selection
+- Not updating document frontmatter
+
+**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-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.
+
+---