siesa-agents 2.1.40 → 2.1.41

package/bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/steps/step-01b-continue.md

@@ -1,150 +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.
+---
+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/bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/steps/step-02-profile.md

@@ -1,164 +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/workflows/advanced-elicitation/workflow.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.
+---
+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/workflows/advanced-elicitation/workflow.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.