siesa-agents 2.1.40 → 2.1.42

package/bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md

@@ -1,177 +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
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### 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
-- update frontmatter `stepsCompleted` to add 4 at the end of the array before loading next step
-- Frontmatter initialized with `stepsCompleted: [1]`
-- 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.
+---
+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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 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
+- update frontmatter `stepsCompleted` to add 4 at the end of the array before loading next step
+- Frontmatter initialized with `stepsCompleted: [1]`
+- 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/bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md

@@ -1,121 +1,121 @@
----
-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'
-outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
----
-
-# 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
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### 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 during this step
-- 💬 Maintain continuity with previous sessions
-- 🚪 DETECT exact continuation point from frontmatter of incomplete file {outputFile}
-
-## 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 of {outputFile} to understand:
-
-- `stepsCompleted`: Which steps are already done, the rightmost value of the array is the last step completed. For example stepsCompleted: [1, 2, 3] would mean that steps 1, then 2, and then 3 were finished.
-
-### 2. Read the full step of every completed step
-
-- read each step file that corresponds to the stepsCompleted > 1.
-
-EXAMPLE: In the example `stepsCompleted: [1, 2, 3]` your would find the step 2 file by file name (step-02-profile.md) and step 3 file (step-03-assessment.md). the last file in the array is the last one completed, so you will follow the instruction to know what the next step to start processing is. reading that file would for example show that the next file is `steps/step-04-strategy.md`.
-
-### 3. Review the output completed previously
-
-In addition to reading ONLY each step file that was completed, you will then read the {outputFile} to further understand what is done so far.
-
-### 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
-
-### 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: follow the suggestion of the last completed step reviewed to continue as it suggested
-- 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'
+outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
+---
+
+# 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 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 during this step
+- 💬 Maintain continuity with previous sessions
+- 🚪 DETECT exact continuation point from frontmatter of incomplete file {outputFile}
+
+## 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 of {outputFile} to understand:
+
+- `stepsCompleted`: Which steps are already done, the rightmost value of the array is the last step completed. For example stepsCompleted: [1, 2, 3] would mean that steps 1, then 2, and then 3 were finished.
+
+### 2. Read the full step of every completed step
+
+- read each step file that corresponds to the stepsCompleted > 1.
+
+EXAMPLE: In the example `stepsCompleted: [1, 2, 3]` your would find the step 2 file by file name (step-02-profile.md) and step 3 file (step-03-assessment.md). the last file in the array is the last one completed, so you will follow the instruction to know what the next step to start processing is. reading that file would for example show that the next file is `steps/step-04-strategy.md`.
+
+### 3. Review the output completed previously
+
+In addition to reading ONLY each step file that was completed, you will then read the {outputFile} to further understand what is done so far.
+
+### 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
+
+### 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: follow the suggestion of the last completed step reviewed to continue as it suggested
+- 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.