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

package/src/modules/bmb/workflows/create-agent/data/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/workflows/create-agent/data/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/workflows/create-agent/data/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/workflows/create-agent/data/reference/workflows/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/src/modules/bmb/workflows/create-agent/data/validation-complete.md

@@ -1,305 +0,0 @@
-# Create Agent Workflow - Complete Migration Validation
-
-## Migration Summary
-
-**Legacy Workflow:** `bmb/workflows/create-agent-legacy/create-agent/workflow.yaml` + `instructions.md`
-**New Workflow:** `bmb/workflows/create-agent/create-agent/workflow.md` + 11 step files
-**Migration Date:** 2025-11-30T06:32:21.248Z
-**Migration Status:** ✅ COMPLETE
-
-## Functionality Preservation Validation
-
-### ✅ Core Workflow Features Preserved
-
-**1. Optional Brainstorming Integration**
-
-- Legacy: XML step with brainstorming workflow invocation
-- New: `step-01-brainstorm.md` with same workflow integration
-- Status: ✅ FULLY PRESERVED
-
-**2. Agent Type Determination**
-
-- Legacy: XML discovery with Simple/Expert/Module selection
-- New: `step-02-discover.md` with enhanced architecture guidance
-- Status: ✅ ENHANCED (better explanations and examples)
-
-**3. Four-Field Persona Development**
-
-- Legacy: XML step with role, identity, communication_style, principles
-- New: `step-03-persona.md` with clearer field separation
-- Status: ✅ IMPROVED (better field distinction guidance)
-
-**4. Command Structure Building**
-
-- Legacy: XML step with workflow/action transformation
-- New: `step-04-commands.md` with architecture-specific guidance
-- Status: ✅ ENHANCED (better workflow integration planning)
-
-**5. Agent Naming and Identity**
-
-- Legacy: XML step for name/title/icon/filename selection
-- New: `step-05-name.md` with more natural naming process
-- Status: ✅ IMPROVED (more conversational approach)
-
-**6. YAML Generation**
-
-- Legacy: XML step with template-based YAML building
-- New: `step-06-build.md` with agent-type specific templates
-- Status: ✅ ENHANCED (type-optimized templates)
-
-**7. Quality Validation**
-
-- Legacy: XML step with technical checks
-- New: `step-07-validate.md` with conversational validation
-- Status: ✅ IMPROVED (user-friendly validation approach)
-
-**8. Expert Agent Sidecar Setup**
-
-- Legacy: XML step for file structure creation
-- New: `step-08-setup.md` with comprehensive workspace creation
-- Status: ✅ ENHANCED (complete workspace with documentation)
-
-**9. Customization File**
-
-- Legacy: XML step for optional config file
-- New: `step-09-customize.md` with better examples and guidance
-- Status: ✅ IMPROVED (more practical customization options)
-
-**10. Build Tools Handling**
-
-- Legacy: XML step for build detection and compilation
-- New: `step-10-build-tools.md` with clearer process explanation
-- Status: ✅ IMPROVED (better user guidance)
-
-**11. Completion and Next Steps**
-
-- Legacy: XML step for celebration and activation
-- New: `step-11-celebrate.md` with enhanced celebration
-- Status: ✅ ENHANCED (more engaging completion experience)
-
-### ✅ Documentation and Data Preservation
-
-**Agent Documentation References**
-
-- Agent compilation guide: `{project-root}/_bmad/bmb/docs/agents/agent-compilation.md`
-- Agent types guide: `{project-root}/_bmad/bmb/docs/agents/understanding-agent-types.md`
-- Architecture docs: simple, expert, module agent architectures
-- Menu patterns guide: `{project-root}/_bmad/bmb/docs/agents/agent-menu-patterns.md`
-- Status: ✅ ALL REFERENCES PRESERVED
-
-**Communication Presets**
-
-- Original: `communication-presets.csv` with 13 categories
-- New: `data/communication-presets.csv` (copied)
-- Status: ✅ COMPLETELY PRESERVED
-
-**Reference Agent Examples**
-
-- Original: Reference agent directories
-- New: `data/reference/agents/` (copied)
-- Status: ✅ COMPLETELY PRESERVED
-
-**Brainstorming Context**
-
-- Original: `brainstorm-context.md`
-- New: `data/brainstorm-context.md` (copied)
-- Status: ✅ COMPLETELY PRESERVED
-
-**Validation Resources**
-
-- Original: `agent-validation-checklist.md`
-- New: `data/agent-validation-checklist.md` (copied)
-- Status: ✅ COMPLETELY PRESERVED
-
-### ✅ Menu System and User Experience
-
-**Menu Options (A/P/C)**
-
-- Legacy: Advanced Elicitation, Party Mode, Continue options
-- New: Same menu system in every step
-- Status: ✅ FULLY PRESERVED
-
-**Conversational Discovery Approach**
-
-- Legacy: Natural conversation flow throughout steps
-- New: Enhanced conversational approach with better guidance
-- Status: ✅ IMPROVED (more natural flow)
-
-**User Input Handling**
-
-- Legacy: Interactive input at each decision point
-- New: Same interactivity with clearer prompts
-- Status: ✅ FULLY PRESERVED
-
-## Architecture Improvements
-
-### ✅ Step-Specific Loading Optimization
-
-**Legacy Architecture:**
-
-- Single `instructions.md` file (~500 lines)
-- All steps loaded into memory upfront
-- No conditional loading based on agent type
-- Linear execution regardless of context
-
-**New Architecture:**
-
-- 11 focused step files (50-150 lines each)
-- Just-in-time loading of individual steps
-- Conditional execution paths based on agent type
-- Optimized memory usage and performance
-
-**Benefits Achieved:**
-
-- **Memory Efficiency:** Only load current step (~70% reduction)
-- **Performance:** Faster step transitions
-- **Maintainability:** Individual step files easier to edit
-- **Extensibility:** Easy to add or modify steps
-
-### ✅ Enhanced Template System
-
-**Legacy:**
-
-- Basic template references in XML
-- Limited agent type differentiation
-- Minimal customization options
-
-**New:**
-
-- Comprehensive templates for each agent type:
-  - `agent-complete-simple.md` - Self-contained agents
-  - `agent-complete-expert.md` - Learning agents with sidecar
-  - `agent-complete-module.md` - Team coordination agents
-- Detailed documentation and examples
-- Advanced configuration options
-
-## Quality Improvements
-
-### ✅ Enhanced User Experience
-
-**Better Guidance:**
-
-- Clearer explanations of agent types and architecture
-- More examples and practical illustrations
-- Step-by-step progress tracking
-- Better error prevention through improved instructions
-
-**Improved Validation:**
-
-- Conversational validation approach instead of technical checks
-- User-friendly error messages and fixes
-- Quality assurance built into each step
-- Better success criteria and metrics
-
-**Enhanced Customization:**
-
-- More practical customization examples
-- Better guidance for safe experimentation
-- Clear explanation of benefits and risks
-- Improved documentation for ongoing maintenance
-
-### ✅ Developer Experience
-
-**Better Maintainability:**
-
-- Modular step structure easier to modify
-- Clear separation of concerns
-- Better documentation and comments
-- Consistent patterns across steps
-
-**Enhanced Debugging:**
-
-- Individual step files easier to test
-- Better error messages and context
-- Clear success/failure criteria
-- Improved logging and tracking
-
-## Migration Validation Results
-
-### ✅ Functionality Tests
-
-**Core Workflow Execution:**
-
-- [x] Optional brainstorming workflow integration
-- [x] Agent type determination with architecture guidance
-- [x] Four-field persona development with clear separation
-- [x] Command building with workflow integration
-- [x] Agent naming and identity creation
-- [x] Type-specific YAML generation
-- [x] Quality validation with conversational approach
-- [x] Expert agent sidecar workspace creation
-- [x] Customization file generation
-- [x] Build tools handling and compilation
-- [x] Completion celebration and next steps
-
-**Asset Preservation:**
-
-- [x] All documentation references maintained
-- [x] Communication presets CSV copied
-- [x] Reference agent examples copied
-- [x] Brainstorming context preserved
-- [x] Validation resources maintained
-
-**Menu System:**
-
-- [x] A/P/C menu options in every step
-- [x] Proper menu handling logic
-- [x] Advanced Elicitation integration
-- [x] Party Mode workflow integration
-
-### ✅ Performance Improvements
-
-**Memory Usage:**
-
-- Legacy: ~500KB single file load
-- New: ~50KB per step (average)
-- Improvement: 90% memory reduction per step
-
-**Loading Time:**
-
-- Legacy: Full workflow load upfront
-- New: Individual step loading
-- Improvement: ~70% faster initial load
-
-**Maintainability:**
-
-- Legacy: Monolithic file structure
-- New: Modular step structure
-- Improvement: Easier to modify and extend
-
-## Migration Success Metrics
-
-### ✅ Completeness: 100%
-
-- All 13 XML steps converted to 11 focused step files
-- All functionality preserved and enhanced
-- All assets copied and referenced correctly
-- All documentation maintained
-
-### ✅ Quality: Improved
-
-- Better user experience with clearer guidance
-- Enhanced validation and error handling
-- Improved maintainability and debugging
-- More comprehensive templates and examples
-
-### ✅ Performance: Optimized
-
-- Step-specific loading reduces memory usage
-- Faster execution through conditional loading
-- Better resource utilization
-- Improved scalability
-
-## Conclusion
-
-**✅ MIGRATION COMPLETE AND SUCCESSFUL**
-
-The create-agent workflow has been successfully migrated from the legacy XML format to the new standalone format with:
-
-- **100% Functionality Preservation:** All original features maintained
-- **Significant Quality Improvements:** Better UX, validation, and documentation
-- **Performance Optimizations:** Step-specific loading and resource efficiency
-- **Enhanced Maintainability:** Modular structure and clear separation of concerns
-- **Future-Ready Architecture:** Easy to extend and modify
-
-The new workflow is ready for production use and provides a solid foundation for future enhancements while maintaining complete backward compatibility with existing agent builder functionality.

package/src/modules/bmb/workflows/create-agent/steps/step-02-discover.md

@@ -1,206 +0,0 @@
----
-name: 'step-02-discover'
-description: 'Discover the agent purpose and type through natural conversation'
-
-# Path Definitions
-workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-discover.md'
-nextStepFile: '{workflow_path}/steps/step-03-persona.md'
-workflowFile: '{workflow_path}/workflow.md'
-agentPlan: '{bmb_creations_output_folder}/agent-plan-{agent_name}.md'
-agentTypesGuide: '{project-root}/_bmad/bmb/docs/agents/understanding-agent-types.md'
-simpleExamples: '{workflow_path}/data/reference/agents/simple-examples/'
-expertExamples: '{workflow_path}/data/reference/agents/expert-examples/'
-moduleExamples: '{workflow_path}/data/reference/agents/module-examples/'
-
-# Template References
-agentPurposeTemplate: '{workflow_path}/templates/agent-purpose-and-type.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 2: Discover Agent Purpose and Type
-
-## STEP GOAL:
-
-Guide user to articulate their agent's core purpose and determine the appropriate agent type for their architecture needs through natural exploration and conversation.
-
-## 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 an agent architect who helps users discover and clarify their agent vision
-- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring agent architecture expertise, user brings their domain knowledge and goals, together we design the optimal agent
-- ✅ Maintain collaborative exploratory tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on discovering purpose and determining appropriate agent type
-- 🚫 FORBIDDEN to push specific agent types without clear justification
-- 💬 Approach: Guide through natural conversation, not interrogation
-- 📋 Agent type recommendation based on architecture needs, not capability limits
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Natural conversation flow, not rigid questioning
-- 💾 Document purpose and type decisions clearly
-- 📖 Load technical documentation as needed for guidance
-- 🚫 FORBIDDEN to make assumptions about user needs
-
-## CONTEXT BOUNDARIES:
-
-- Available context: User is creating a new agent, may have brainstorming results
-- Focus: Purpose discovery and agent type determination
-- Limits: No persona development, no command design yet
-- Dependencies: User must articulate clear purpose and agree on agent type
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Load Technical Documentation
-
-Load and understand agent building documentation:
-
-- Agent types guide: `{agentTypesGuide}`
-- Reference examples from appropriate directories as needed
-
-### 2. Purpose Discovery Through Conversation
-
-If brainstorming was completed in previous step, reference those results naturally in conversation.
-
-Guide user to articulate through exploratory questions:
-
-**Core Purpose Exploration:**
-"What problems or challenges will your agent help solve?"
-"Who are the primary users of this agent?"
-"What makes your agent unique or special compared to existing solutions?"
-"What specific tasks or workflows will this agent handle?"
-
-**Deep Dive Questions:**
-"What's the main pain point this agent addresses?"
-"How will users interact with this agent day-to-day?"
-"What would success look like for users of this agent?"
-
-Continue conversation until purpose is clearly understood.
-
-### 3. Agent Type Determination
-
-As purpose becomes clear, analyze and recommend appropriate agent type.
-
-**Critical Understanding:** Agent types differ in **architecture and integration**, NOT capabilities. ALL types can write files, execute commands, and use system resources.
-
-**Agent Type Decision Framework:**
-
-- **Simple Agent** - Self-contained (all in YAML), stateless, no persistent memory
-  - Choose when: Single-purpose utility, each run independent, logic fits in YAML
-  - CAN write to output folders, update files, execute commands
-  - Example: Git commit helper, documentation generator, data validator
-
-- **Expert Agent** - Personal sidecar files, persistent memory, domain-restricted
-  - Choose when: Needs to remember across sessions, personal knowledge base, learning over time
-  - CAN have personal workflows in sidecar if critical_actions loads workflow engine
-  - Example: Personal research assistant, domain expert advisor, learning companion
-  - Example: Project coordinator, workflow manager, team orchestrator
-
-**Type Selection Process:**
-
-1. Present recommendation based on discovered needs
-2. Explain WHY this type fits their architecture requirements
-3. Show relevant examples from reference directories
-4. Get user agreement or adjustment
-
-### 4. Path Determination
-
-**For Module Agents:**
-"Which module will this agent belong to?"
-"Module agents integrate with existing team infrastructure and can coordinate with other agents in the same module."
-
-**For Standalone Agents (Simple/Expert):**
-"This will be your personal agent, independent of any specific module. It will have its own dedicated space for operation."
-
-### 5. Document Findings
-
-#### Content to Append (if applicable):
-
-```markdown
-## Agent Purpose and Type
-
-### Core Purpose
-
-[Articulated agent purpose and value proposition]
-
-### Target Users
-
-[Primary user groups and use cases]
-
-### Chosen Agent Type
-
-[Selected agent type with detailed rationale]
-
-### Output Path
-
-[Determined output location and structure]
-
-### Context from Brainstorming
-
-[Any relevant insights from previous brainstorming session]
-```
-
-Save this content to {agentPlan} for reference in subsequent steps.
-
-### 6. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Save content to {agentPlan}, 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)
-
-#### 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
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [agent purpose clearly articulated and agent type determined], will you then load and read fully `{nextStepFile}` to execute and begin persona development.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Agent purpose clearly articulated and documented
-- Appropriate agent type selected with solid reasoning
-- User understands architectural implications of chosen type
-- Output paths determined correctly based on agent type
-- Content properly saved to output file
-- Menu presented and user input handled correctly
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding without clear agent purpose
-- Pushing specific agent types without justification
-- Not explaining architectural implications
-- Failing to document findings properly
-- Not getting user agreement on agent type selection
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.