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

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

@@ -1,195 +0,0 @@
----
-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/workflows/advanced-elicitation/workflow.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
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### 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/workflows/advanced-elicitation/workflow.xml`
-- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
-- IF C: update frontmatter `stepsCompleted` to add 6 at the end of the array before loading next step, 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 `stepsCompleted` to add 6 at the end of the array before loading next step 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!"

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/templates/assessment-section.md

@@ -1,25 +0,0 @@
-## 📊 Daily Nutrition Targets
-
-**Daily Calories:** [calculated amount]
-**Protein:** [grams]g ([percentage]% of calories)
-**Carbohydrates:** [grams]g ([percentage]% of calories)
-**Fat:** [grams]g ([percentage]% of calories)
-
----
-
-## ⚠️ Dietary Considerations
-
-### Allergies & Intolerances
-
-- [List of identified restrictions]
-- [Cross-reactivity notes if applicable]
-
-### Medical Considerations
-
-- [Conditions noted with professional referral recommendation]
-- [Special nutritional requirements]
-
-### Preferences
-
-- [Cultural/ethical restrictions]
-- [Strong dislikes to avoid]

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/templates/nutrition-plan.md

@@ -1,68 +0,0 @@
-# Personalized Nutrition Plan
-
-**Created:** {{date}}
-**Author:** {{user_name}}
-
----
-
-## ✅ Progress Tracking
-
-**Steps Completed:**
-
-- [ ] Step 1: Workflow Initialization
-- [ ] Step 2: User Profile & Goals
-- [ ] Step 3: Dietary Assessment
-- [ ] Step 4: Meal Strategy
-- [ ] Step 5: Shopping List _(if applicable)_
-- [ ] Step 6: Meal Prep Schedule
-
-**Last Updated:** {{date}}
-
----
-
-## 📋 Executive Summary
-
-**Primary Goal:** [To be filled in Step 1]
-
-**Daily Nutrition Targets:**
-
-- Calories: [To be calculated in Step 2]
-- Protein: [To be calculated in Step 2]g
-- Carbohydrates: [To be calculated in Step 2]g
-- Fat: [To be calculated in Step 2]g
-
-**Key Considerations:** [To be filled in Step 2]
-
----
-
-## 🎯 Your Nutrition Goals
-
-[Content to be added in Step 1]
-
----
-
-## 🍽️ Meal Framework
-
-[Content to be added in Step 3]
-
----
-
-## 🛒 Shopping List
-
-[Content to be added in Step 4 - if applicable]
-
----
-
-## ⏰ Meal Prep Schedule
-
-[Content to be added in Step 5]
-
----
-
-## 📝 Notes & Next Steps
-
-[Add any notes or adjustments as you progress]
-
----
-
-**Medical Disclaimer:** This nutrition plan is for educational purposes only and is not medical advice. Please consult with a registered dietitian or healthcare provider for personalized medical nutrition therapy, especially if you have medical conditions, allergies, or are taking medications.

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/templates/prep-schedule-section.md

@@ -1,29 +0,0 @@
-## Meal Prep Schedule
-
-### [Chosen Prep Strategy]
-
-### Weekly Prep Tasks
-
-- [Day]: [Tasks] - [Time needed]
-- [Day]: [Tasks] - [Time needed]
-
-### Daily Assembly
-
-- Morning: [Quick tasks]
-- Evening: [Assembly instructions]
-
-### Storage Guide
-
-- Proteins: [Instructions]
-- Vegetables: [Instructions]
-- Grains: [Instructions]
-
-### Success Tips
-
-- [Personalized success strategies]
-
-### Weekly Review Checklist
-
-- [ ] Check weekend schedule
-- [ ] Review meal plan satisfaction
-- [ ] Adjust next week's plan

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/templates/profile-section.md

@@ -1,47 +0,0 @@
-## 🎯 Your Nutrition Goals
-
-### Primary Objective
-
-[User's main goal and motivation]
-
-### Target Timeline
-
-[Realistic timeframe and milestones]
-
-### Success Metrics
-
-- [Specific measurable outcomes]
-- [Non-scale victories]
-- [Lifestyle improvements]
-
----
-
-## 👤 Personal Profile
-
-### Basic Information
-
-- **Age:** [age]
-- **Gender:** [gender]
-- **Height:** [height]
-- **Weight:** [current weight]
-- **Activity Level:** [activity description]
-
-### Lifestyle Factors
-
-- **Daily Schedule:** [typical day structure]
-- **Cooking Frequency:** [how often they cook]
-- **Cooking Skill:** [beginner/intermediate/advanced]
-- **Available Time:** [time for meal prep]
-
-### Food Preferences
-
-- **Favorite Cuisines:** [list]
-- **Disliked Foods:** [list]
-- **Allergies:** [list]
-- **Dietary Restrictions:** [list]
-
-### Budget & Access
-
-- **Weekly Budget:** [range]
-- **Shopping Access:** [stores available]
-- **Special Considerations:** [family, social, etc.]

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/templates/shopping-section.md

@@ -1,37 +0,0 @@
-## Weekly Shopping List
-
-### Check Pantry First
-
-- [List of common staples to verify]
-
-### Produce Section
-
-- [Item] - [Quantity] - [Used in]
-
-### Protein
-
-- [Item] - [Quantity] - [Used in]
-
-### Dairy/Alternatives
-
-- [Item] - [Quantity] - [Used in]
-
-### Grains/Starches
-
-- [Item] - [Quantity] - [Used in]
-
-### Frozen
-
-- [Item] - [Quantity] - [Used in]
-
-### Pantry
-
-- [Item] - [Quantity] - [Used in]
-
-### Money-Saving Tips
-
-- [Personalized savings strategies]
-
-### Flexible Swaps
-
-- [Alternative options if items unavailable]

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/templates/strategy-section.md

@@ -1,18 +0,0 @@
-## Weekly Meal Framework
-
-### Protein Rotation
-
-- Monday: [Protein source]
-- Tuesday: [Protein source]
-- Wednesday: [Protein source]
-- Thursday: [Protein source]
-- Friday: [Protein source]
-- Saturday: [Protein source]
-- Sunday: [Protein source]
-
-### Meal Timing
-
-- Breakfast: [Time] - [Type]
-- Lunch: [Time] - [Type]
-- Dinner: [Time] - [Type]
-- Snacks: [As needed]

package/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md

@@ -1,59 +0,0 @@
----
-name: Meal Prep & Nutrition Plan
-description: Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.
-web_bundle: true
----
-
-# Meal Prep & Nutrition Plan Workflow
-
-**Goal:** Create personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a nutrition expert and meal planning specialist working collaboratively with the user. We engage in collaborative dialogue, not command-response, where you bring nutritional expertise and structured planning, while the user brings their personal preferences, lifestyle constraints, and health goals. Work together to create a sustainable, enjoyable nutrition plan.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
-- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-Load and read full config from {project-root}/_bmad/core/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### 2. First Step EXECUTION
-
-Load, read the full file and then execute `{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.

package/src/modules/bmb/workflows/agent/steps-c/step-08a-plan-traceability.md

@@ -1,203 +0,0 @@
----
-name: 'step-07a-plan-traceability'
-description: 'Verify build matches original plan'
-
-# File References
-nextStepFile: './step-08b-metadata-validation.md'
-agentPlan: '{bmb_creations_output_folder}/agent-plan-{agent_name}.md'
-builtYaml: '{bmb_creations_output_folder}/{agent-name}/{agent-name}.agent.yaml'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# STEP GOAL
-Verify that the built agent YAML file contains all elements specified in the original agent plan. This step ensures plan traceability - confirming that what we planned is what we actually built.
-
-# MANDATORY EXECUTION RULES
-- MUST load both agentPlan and builtYaml files before comparison
-- MUST compare ALL planned elements against built implementation
-- MUST report specific missing items, not just "something is missing"
-- MUST offer fix option before proceeding to next validation
-- MUST handle missing files gracefully (report clearly, don't crash)
-- MUST respect YOLO mode behavior (part of combined validation report)
-
-# EXECUTION PROTOCOLS
-
-## File Loading Protocol
-1. Load agentPlan from `{bmb_creations_output_folder}/agent-plan-{agent_name}.md`
-2. Load builtYaml from `{bmb_creations_output_folder}/{agent-name}/{agent-name}.agent.yaml`
-3. If either file is missing, report the specific missing file and stop comparison
-4. Use Read tool to access both files with absolute paths
-
-## Comparison Protocol
-Compare the following categories systematically:
-
-### 1. Metadata Comparison
-- Agent name
-- Description
-- Version
-- Author/creator information
-- Location/module path
-- Language settings (if specified in plan)
-
-### 2. Persona Field Comparison
-For each field in persona section:
-- Check presence in built YAML
-- Verify field content matches planned intent
-- Note any significant deviations (minor wording differences ok)
-
-### 3. Commands Comparison
-- Verify all planned commands are present
-- Check command names match
-- Verify command descriptions are present
-- Confirm critical actions are referenced
-
-### 4. Critical Actions Comparison
-- Verify all planned critical_actions are present
-- Check action names match exactly
-- Verify action descriptions are present
-- Confirm each action has required fields
-
-### 5. Additional Elements
-- Dependencies (if planned)
-- Configuration (if planned)
-- Installation instructions (if planned)
-
-## Reporting Protocol
-Present findings in clear, structured format:
-
-```
-PLAN TRACEABILITY REPORT
-========================
-
-Agent: {agent_name}
-Plan File: {path to agent plan}
-Build File: {path to built YAML}
-
-COMPARISON RESULTS:
--------------------
-
-✅ Metadata: All present / Missing: {list}
-✅ Persona Fields: All present / Missing: {list}
-✅ Commands: All present / Missing: {list}
-✅ Critical Actions: All present / Missing: {list}
-✅ Other Elements: All present / Missing: {list}
-
-OVERALL STATUS: [PASS / FAIL]
-
-```
-
-If ANY elements are missing:
-- List each missing element with category
-- Provide specific location reference (what was planned)
-- Ask if user wants to fix items or continue anyway
-
-## Menu Protocol
-
-### 8. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [F] Fix Findings [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF F: Apply auto-fixes to {builtYaml} for identified missing elements, then redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF C: Proceed to next validation step, 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](#8-present-menu-options)
-
-#### 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
-
-If YOLO mode:
-- Include this report in combined validation report
-- Auto-select [C] Continue if all elements present
-- Auto-select [F] Fix if missing critical elements (name, commands)
-- Flag non-critical missing items in summary
-
-# CONTEXT BOUNDARIES
-- ONLY compare plan vs build - do NOT evaluate quality or correctness
-- Do NOT suggest improvements or changes beyond planned elements
-- Do NOT re-open persona/commands discovery - this is verification only
-- Fix option should return to step-06-build, not earlier steps
-- If plan file is ambiguous, note ambiguity but use reasonable interpretation
-
-# SEQUENCE
-
-## 1. Load Required Files
-```yaml
-action: read
-target:
-  - agentPlan
-  - builtYaml
-on_failure: report which file is missing and suggest resolution
-```
-
-## 2. Perform Structured Comparison
-```yaml
-action: compare
-categories:
-  - metadata
-  - persona_fields
-  - commands
-  - critical_actions
-  - other_elements
-method: systematic category-by-category check
-```
-
-## 3. Generate Comparison Report
-```yaml
-action: report
-format: structured pass/fail with specific missing items
-output: console display + optional save to validation log
-```
-
-## 4. Present Menu Options
-```yaml
-action: menu
-options:
-  - F: Fix missing items
-  - C: Continue to metadata validation
-  - V: View detailed comparison (optional)
-default: C if pass, F if fail
-```
-
-## 5. Handle User Choice
-- **[F] Fix Findings**: Apply auto-fixes to {builtYaml} for identified missing elements, then re-present menu
-- **[C] Continue**: Proceed to step-07b-metadata-validation
-- **[A] Advanced Elicitation**: Execute advanced elicitation workflow, then re-present menu
-- **[P] Party Mode**: Execute party mode workflow, then re-present menu
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [validation complete with any findings addressed], will you then load and read fully `{nextStepFile}` to execute and begin [metadata validation].
-
-# SUCCESS/FAILURE METRICS
-
-## Success Criteria
-- All planned elements present in built YAML: **COMPLETE PASS**
-- Minor deviations (wording, formatting) but all core elements present: **PASS**
-- Missing elements identified and user chooses to continue: **PASS WITH NOTED DEFICIENCIES**
-
-## Failure Criteria
-- Unable to load plan or build file: **BLOCKING FAILURE**
-- Critical elements missing (name, commands, or critical_actions): **FAIL**
-- Comparison cannot be completed due to file corruption: **BLOCKING FAILURE**
-
-## Next Step Triggers
-- **PASS → step-07b-metadata-validation**
-- **PASS WITH DEFICIENCIES → step-07b-metadata-validation** (user choice)
-- **FAIL → step-06-build** (with specific fix instructions)
-- **BLOCKING FAILURE → STOP** (resolve file access issues first)
-
-## YOLO Mode Behavior
-- Auto-fix missing critical elements by returning to build step
-- Log non-critical missing items for review but continue validation
-- Include traceability report in final YOLO summary
-- Do NOT stop for user confirmation unless plan file is completely missing