siesa-agents 2.1.78 → 2.1.80

package/bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/steps/step-06-prep-schedule.md

@@ -1,194 +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
-
-### 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 with all steps completed, 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 with all steps 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/bmad/bmb/workflows/create-workflow/data/examples/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/bmad/bmb/workflows/create-workflow/data/examples/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/bmad/bmb/workflows/create-workflow/data/examples/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/bmad/bmb/workflows/create-workflow/data/examples/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/bmad/bmb/workflows/create-workflow/data/examples/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/bmad/bmb/workflows/create-workflow/data/examples/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/bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/workflow.md

@@ -1,58 +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/bmm/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
-
-### 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/bmad/bmb/workflows/create-workflow/steps/step-01-init.md

@@ -1,158 +0,0 @@
----
-name: 'step-01-init'
-description: 'Initialize workflow creation session by gathering project information and setting up unique workflow folder'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/create-workflow'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-gather.md'
-workflowFile: '{workflow_path}/workflow.md'
-
-# Output files for workflow creation process
-targetWorkflowPath: '{bmb_creations_output_folder}/workflows/{new_workflow_name}'
-workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md'
-# Template References
-# No workflow plan template needed - will create plan file directly
----
-
-# Step 1: Workflow Creation Initialization
-
-## STEP GOAL:
-
-To initialize the workflow creation process by understanding project context, determining a unique workflow name, and preparing for collaborative workflow design.
-
-## 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 workflow architect and systems designer
-- ✅ 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 workflow design expertise, user brings their specific requirements
-- ✅ Together we will create a structured, repeatable workflow
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on initialization and project understanding
-- 🚫 FORBIDDEN to start designing workflow steps in this step
-- 💬 Ask questions conversationally to understand context
-- 🚪 ENSURE unique workflow naming to avoid conflicts
-
-## 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 initialization 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 discovery happens in this step
-
-## INITIALIZATION SEQUENCE:
-
-### 1. Project Discovery
-
-Welcome the user and understand their needs:
-"Welcome! I'm excited to help you create a new workflow. Let's start by understanding what you want to build."
-
-Ask conversationally:
-
-- What type of workflow are you looking to create?
-- What problem will this workflow solve?
-- Who will use this workflow?
-- What module will it belong to (bmb, bmm, cis, custom, stand-alone)?
-
-Also, Ask / suggest a workflow name / folder: (kebab-case, e.g., "user-story-generator")
-
-### 2. Ensure Unique Workflow Name
-
-After getting the workflow name:
-
-**Check for existing workflows:**
-
-- Look for folder at `{bmb_creations_output_folder}/workflows/{new_workflow_name}/`
-- If it exists, inform the user and suggest or get from them a unique name or postfix
-
-**Example alternatives:**
-
-- Original: "user-story-generator"
-- Alternatives: "user-story-creator", "user-story-generator-2025", "user-story-generator-enhanced"
-
-**Loop until we have a unique name that doesn't conflict.**
-
-### 3. Determine Target Location
-
-Based on the module selection, confirm the target location:
-
-- For bmb module: `{custom_workflow_location}` (defaults to `_bmad/custom/src/workflows`)
-- For other modules: Check their module.yaml for custom workflow locations
-- Confirm the exact folder path where the workflow will be created
-- Store the confirmed path as `{targetWorkflowPath}`
-
-### 4. Create Workflow Plan Document
-
-Create the workflow plan document at `{workflowPlanFile}` with the following initial content:
-
-```markdown
----
-stepsCompleted: [1]
----
-
-# Workflow Creation Plan: {new_workflow_name}
-
-## Initial Project Context
-
-- **Module:** [module from user]
-- **Target Location:** {targetWorkflowPath}
-- **Created:** [current date]
-```
-
-This plan will capture all requirements and design details before building the actual workflow.
-
-### 5. Present MENU OPTIONS
-
-Display: **Proceeding to requirements gathering...**
-
-#### 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 and the workflow folder with the workflow plan file created already, only then immediately load, read entire file, and then execute `{workflow_path}/steps/step-02-gather.md` to begin requirements gathering
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Workflow name confirmed and validated
-- Target folder location determined
-- User welcomed and project context understood
-- Ready to proceed to step 2
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding with step 2 without workflow name
-- Not checking for existing workflow folders
-- Not determining target location properly
-- Skipping welcome message
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.