siesa-agents 2.1.35 → 2.1.37

package/_bmad/bmb/workflows/create-module/templates/module.template.yaml

@@ -0,0 +1,53 @@
+# {module_display_name} Module Configuration
+# This file defines installation questions and module configuration values
+
+code: "${module_name}" # e.g., my-module
+name: "{module_display_name}"
+default_selected: false
+
+# Welcome message shown during installation
+prompt:
+  - "Thank you for choosing {module_display_name}!"
+  - "{module_purpose}"
+# Core config values are automatically inherited from installer:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+
+# ============================================================================
+# CONFIGURATION FIELDS
+# ============================================================================
+# Each field can be:
+# 1. INTERACTIVE (has 'prompt' - asks user during installation)
+# 2. STATIC (no 'prompt' - just uses 'result' value)
+# ============================================================================
+
+# Example configurations (replace with actual planned fields):
+
+# INTERACTIVE text input:
+# output_path:
+#   prompt: "Where should {module_name} save outputs?"
+#   default: "output/{module_name}"
+#   result: "{project-root}/{value}"
+
+# INTERACTIVE single-select:
+# detail_level:
+#   prompt: "How detailed should outputs be?"
+#   default: "standard"
+#   result: "{value}"
+#   single-select:
+#     - value: "minimal"
+#       label: "Minimal - Brief summaries only"
+#     - value: "standard"
+#       label: "Standard - Balanced detail"
+#     - value: "detailed"
+#       label: "Detailed - Comprehensive information"
+
+# STATIC value:
+# module_version:
+#   result: "1.0.0"
+
+# STATIC path:
+# data_path:
+#   result: "{project-root}/_bmad/{module_name}/data"

package/_bmad/bmb/workflows/create-module/templates/workflow-plan-template.md

@@ -0,0 +1,23 @@
+# Workflow Plan Template
+
+Use this template when creating workflow plans in step-07-workflows.md
+
+## Template Structure
+
+Copy the content from step-07-workflows.md when creating workflow plans. The template is embedded in the step file as a code block under "Workflow plan template".
+
+## Usage
+
+1. Navigate to the workflow folder
+2. Create workflow-plan.md
+3. Use the template structure from step-07-workflows.md
+4. Fill in details specific to your workflow
+
+## Required Sections
+
+- Purpose
+- Requirements (User Inputs, Prerequisites, Dependencies)
+- Proposed Steps
+- Expected Outputs
+- Integration Points
+- Implementation Notes

package/_bmad/bmb/workflows/create-module/validation.md

@@ -0,0 +1,126 @@
+# Create Module Workflow Validation Checklist
+
+This document provides the validation criteria used in step-11-validate.md to ensure module quality and BMAD compliance.
+
+## Structure Validation
+
+### Required Directories
+
+- [ ] agents/ - Agent definition files
+- [ ] workflows/ - Workflow folders
+- [ ] tasks/ - Task files (if needed)
+- [ ] templates/ - Shared templates
+- [ ] data/ - Module data
+- [ ] _module-installer/ - Installation config
+- [ ] README.md - Module documentation
+- [ ] module.yaml - module config file
+
+### Optional File in _module-installer/
+
+- [ ] installer.js - Custom logic (if needed)
+
+## Configuration Validation
+
+### module.yaml
+
+- [ ] Valid YAML syntax
+- [ ] Module code matches folder name
+- [ ] Name field present
+- [ ] Prompt array with welcome messages
+- [ ] Configuration fields properly defined
+- [ ] Result templates use correct placeholders
+
+### Module Plan
+
+- [ ] All sections completed
+- [ ] Module identity documented
+- [ ] Component plan clear
+- [ ] Configuration plan documented
+
+## Component Validation
+
+### Agents
+
+- [ ] Files created in agents/ folder
+- [ ] YAML frontmatter valid (for created agents)
+- [ ] TODO flags used for non-existent workflows
+- [ ] Menu items follow BMAD patterns
+- [ ] Placeholder files contain TODO notes
+
+### Workflows
+
+- [ ] Folders created for each planned workflow
+- [ ] workflow-plan.md in each folder
+- [ ] README.md in each workflow folder
+- [ ] Plans include all required sections
+- [ ] Placeholder READMEs created for unplanned workflows
+
+## Documentation Validation
+
+### README.md
+
+- [ ] Module name and purpose
+- [ ] Installation instructions
+- [ ] Components section
+- [ ] Quick start guide
+- [ ] Module structure diagram
+- [ ] Configuration section
+- [ ] Usage examples
+- [ ] Development status
+- [ ] Author information
+
+### TODO.md
+
+- [ ] Development phases defined
+- [ ] Tasks prioritized
+- [ ] Quick commands included
+- [ ] Completion criteria defined
+
+## Integration Validation
+
+### Path Consistency
+
+- [ ] All paths use correct template format
+- [ ] Module code consistent throughout
+- [ ] No hardcoded paths
+- [ ] Cross-references correct
+
+### Agent-Workflow Integration
+
+- [ ] Agents reference correct workflows
+- [ ] TODO flags used appropriately
+- [ ] No circular dependencies
+- [ ] Clear integration points
+
+## BMAD Compliance
+
+### Standards
+
+- [ ] Follows BMAD module structure
+- [ ] Uses BMAD installation patterns
+- [ ] Agent files follow BMAD format
+- [ ] Workflow plans follow BMAD patterns
+
+### Best Practices
+
+- [ ] Clear naming conventions
+- [ ] Proper documentation
+- [ ] Version control ready
+- [ ] Installable via bmad install
+
+## Final Checklist
+
+### Before Marking Complete
+
+- [ ] All validation items checked
+- [ ] Critical issues resolved
+- [ ] Module plan updated with final status
+- [ ] stepsCompleted includes all 11 steps
+- [ ] User satisfied with result
+
+### Ready for Testing
+
+- [ ] Installation should work
+- [ ] Documentation accurate
+- [ ] Structure complete
+- [ ] Next steps clear

package/_bmad/bmb/workflows/create-module/workflow.md

@@ -0,0 +1,56 @@
+---
+name: create-module
+description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure'
+web_bundle: true
+installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
+---
+
+# Create Module Workflow
+
+**Goal:** To guide users through creating complete, installable BMAD modules with proper structure, agents, workflow plans, and documentation.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a Module Architect and BMAD Systems Specialist collaborating with module creators. This is a partnership, not a client-vendor relationship. You bring expertise in BMAD architecture, component design, and installation patterns, while the user brings their domain knowledge and specific module requirements. Work together as equals.
+
+## WORKFLOW ARCHITECTURE
+
+### Core Principles
+
+- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
+- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - 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. Module Configuration Loading
+
+Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
+- ✅ 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 {installed_path}/steps/step-01-init.md to begin the workflow.

package/_bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/data/dietary-restrictions.csv

@@ -0,0 +1,18 @@
+category,restriction,considerations,alternatives,notes
+Allergy,Nuts,Severe allergy, check labels carefully,Seeds, sunflower seed butter
+Allergy,Shellfish,Cross-reactivity with some fish,Fin fish, vegetarian proteins
+Allergy,Dairy,Calcium and vitamin D needs,Almond milk, fortified plant milks
+Allergy,Soy,Protein source replacement,Legumes, quinoa, seitan
+Allergy,Gluten,Celiac vs sensitivity,Quinoa, rice, certified gluten-free
+Medical,Diabetes,Carbohydrate timing and type,Fiber-rich foods, low glycemic
+Medical,Hypertension,Sodium restriction,Herbs, spices, salt-free seasonings
+Medical,IBS,FODMAP triggers,Low FODMAP vegetables, soluble fiber
+Ethical,Vegetarian,Complete protein combinations,Quinoa, buckwheat, hemp seeds
+Ethical,Vegan,B12 supplementation mandatory,Nutritional yeast, fortified foods
+Ethical,Halal,Meat sourcing requirements,Halal-certified products
+Ethical,Kosher,Dairy-meat separation,Parve alternatives
+Intolerance,Lactose,Dairy digestion issues,Lactase pills, aged cheeses
+Intolerance,FODMAP,Carbohydrate malabsorption,Low FODMAP fruits/veg
+Preference,Dislikes,Texture/flavor preferences,Similar texture alternatives
+Preference,Budget,Cost-effective options,Bulk buying, seasonal produce
+Preference,Convenience,Time-saving options,Pre-cut vegetables, frozen produce

package/_bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/data/macro-calculator.csv

@@ -0,0 +1,16 @@
+goal,activity_level,multiplier,protein_ratio,protein_min,protein_max,fat_ratio,carb_ratio
+weight_loss,sedentary,1.2,0.3,1.6,2.2,0.35,0.35
+weight_loss,light,1.375,0.35,1.8,2.5,0.30,0.35
+weight_loss,moderate,1.55,0.4,2.0,2.8,0.30,0.30
+weight_loss,active,1.725,0.4,2.2,3.0,0.25,0.35
+weight_loss,very_active,1.9,0.45,2.5,3.3,0.25,0.30
+maintenance,sedentary,1.2,0.25,0.8,1.2,0.35,0.40
+maintenance,light,1.375,0.25,1.0,1.4,0.35,0.40
+maintenance,moderate,1.55,0.3,1.2,1.6,0.35,0.35
+maintenance,active,1.725,0.3,1.4,1.8,0.30,0.40
+maintenance,very_active,1.9,0.35,1.6,2.2,0.30,0.35
+muscle_gain,sedentary,1.2,0.35,1.8,2.5,0.30,0.35
+muscle_gain,light,1.375,0.4,2.0,2.8,0.30,0.30
+muscle_gain,moderate,1.55,0.4,2.2,3.0,0.25,0.35
+muscle_gain,active,1.725,0.45,2.5,3.3,0.25,0.30
+muscle_gain,very_active,1.9,0.45,2.8,3.5,0.25,0.30

package/_bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/data/recipe-database.csv

@@ -0,0 +1,28 @@
+category,name,prep_time,cook_time,total_time,protein_per_serving,complexity,meal_type,restrictions_friendly,batch_friendly
+Protein,Grilled Chicken Breast,10,20,30,35,beginner,lunch/dinner,all,yes
+Protein,Baked Salmon,5,15,20,22,beginner,lunch/dinner,gluten-free,no
+Protein,Lentils,0,25,25,18,beginner,lunch/dinner,vegan,yes
+Protein,Ground Turkey,5,15,20,25,beginner,lunch/dinner,all,yes
+Protein,Tofu Stir-fry,10,15,25,20,intermediate,lunch/dinner,vegan,no
+Protein,Eggs Scrambled,5,5,10,12,beginner,breakfast,vegetarian,no
+Protein,Greek Yogurt,0,0,0,17,beginner,snack,vegetarian,no
+Carb,Quinoa,5,15,20,8,beginner,lunch/dinner,gluten-free,yes
+Carb,Brown Rice,5,40,45,5,beginner,lunch/dinner,gluten-free,yes
+Carb,Sweet Potato,5,45,50,4,beginner,lunch/dinner,all,yes
+Carb,Oatmeal,2,5,7,5,beginner,breakfast,gluten-free,yes
+Carb,Whole Wheat Pasta,2,10,12,7,beginner,lunch/dinner,vegetarian,no
+Veggie,Broccoli,5,10,15,3,beginner,lunch/dinner,all,yes
+Veggie,Spinach,2,3,5,3,beginner,lunch/dinner,all,no
+Veggie,Bell Peppers,5,10,15,1,beginner,lunch/dinner,all,no
+Veggie,Kale,5,5,10,3,beginner,lunch/dinner,all,no
+Veggie,Avocado,2,0,2,2,beginner,snack/lunch,all,no
+Snack,Almonds,0,0,0,6,beginner,snack,gluten-free,no
+Snack,Apple with PB,2,0,2,4,beginner,snack,vegetarian,no
+Snack,Protein Smoothie,5,0,5,25,beginner,snack,all,no
+Snack,Hard Boiled Eggs,0,12,12,6,beginner,snack,vegetarian,yes
+Breakfast,Overnight Oats,5,0,5,10,beginner,breakfast,vegan,yes
+Breakfast,Protein Pancakes,10,10,20,20,intermediate,breakfast,vegetarian,no
+Breakfast,Veggie Omelet,5,10,15,18,intermediate,breakfast,vegetarian,no
+Quick Meal,Chicken Salad,10,0,10,30,beginner,lunch,gluten-free,no
+Quick Meal,Tuna Wrap,5,0,5,20,beginner,lunch,gluten-free,no
+Quick Meal,Buddha Bowl,15,0,15,15,intermediate,lunch,vegan,no

package/_bmad/bmb/workflows/create-workflow/data/examples/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/_bmad/bmb/workflows/create-workflow/data/examples/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.