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

package/src/modules/bmb/reference/workflows/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/tasks/advanced-elicitation.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/tasks/advanced-elicitation.xml`
-- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
-- IF C: update frontmatter `stepsCompleted` to add 6 at the end of the array before loading next step, 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 `stepsCompleted` to add 6 at the end of the array before loading next step 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/src/modules/bmb/reference/workflows/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/src/modules/bmb/reference/workflows/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/src/modules/bmb/reference/workflows/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/src/modules/bmb/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/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/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/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/core/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
-
-### 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/agent-validation-checklist.md

@@ -1,174 +0,0 @@
-# BMAD Agent Validation Checklist
-
-Use this checklist to validate agents meet BMAD quality standards, whether creating new agents or editing existing ones.
-
-## YAML Structure Validation (Source Files)
-
-- [ ] YAML parses without errors
-- [ ] `agent.metadata` includes: `id`, `name`, `title`, `icon`
-- [ ] `agent.metadata.module` present if Module agent (e.g., `bmm`, `bmgd`, `cis`)
-- [ ] `agent.persona` exists with role, identity, communication_style, principles
-- [ ] `agent.menu` exists with at least one item
-- [ ] Filename is kebab-case and ends with `.agent.yaml`
-
-## Agent Structure Validation
-
-- [ ] Agent file format is valid (.agent.yaml for source)
-- [ ] Agent type matches structure: Simple (single YAML), Expert (sidecar files), or Module (ecosystem integration)
-- [ ] File naming follows convention: `{agent-name}.agent.yaml`
-- [ ] If Expert: folder structure with .agent.yaml + sidecar files
-- [ ] If Module: includes header comment explaining WHY Module Agent (design intent)
-
-## Persona Validation (CRITICAL - #1 Quality Issue)
-
-**Field Separation Check:**
-
-- [ ] **role** contains ONLY knowledge/skills/capabilities (what agent does)
-- [ ] **identity** contains ONLY background/experience/context (who agent is)
-- [ ] **communication_style** contains ONLY verbal patterns - NO behaviors, NO role statements, NO principles
-- [ ] **principles** contains operating philosophy and behavioral guidelines
-
-**Communication Style Purity Check:**
-
-- [ ] Communication style does NOT contain red flag words: "ensures", "makes sure", "always", "never"
-- [ ] Communication style does NOT contain identity words: "experienced", "expert who", "senior", "seasoned"
-- [ ] Communication style does NOT contain philosophy words: "believes in", "focused on", "committed to"
-- [ ] Communication style does NOT contain behavioral descriptions: "who does X", "that does Y"
-- [ ] Communication style is 1-2 sentences describing HOW they talk (word choice, quirks, verbal patterns)
-
-**Quality Benchmarking:**
-
-- [ ] Compare communication style against {communication_presets} - similarly pure?
-- [ ] Compare against reference agents (commit-poet, journal-keeper, BMM agents) - similar quality?
-- [ ] Read communication style aloud - does it sound like describing someone's voice/speech pattern?
-
-## Menu Validation
-
-- [ ] All menu items have `trigger` field
-- [ ] Triggers do NOT start with `*` in YAML (auto-prefixed during compilation)
-- [ ] Each item has `description` field
-- [ ] Each menu item has at least one handler attribute: `workflow`, `exec`, `tmpl`, `data`, or `action`
-- [ ] Workflow paths are correct (if workflow attribute present)
-- [ ] Workflow paths use `{project-root}` variable for portability
-- [ ] **Sidecar file paths are correct (if tmpl or data attributes present - Expert agents)**
-- [ ] No duplicate triggers within same agent
-- [ ] Menu items are in logical order
-
-## Prompts Validation (if present)
-
-- [ ] Each prompt has `id` field
-- [ ] Each prompt has `content` field
-- [ ] Prompt IDs are unique within agent
-- [ ] If using `action="#prompt-id"` in menu, corresponding prompt exists
-
-## Critical Actions Validation (if present)
-
-- [ ] Critical actions array contains non-empty strings
-- [ ] Critical actions describe steps that MUST happen during activation
-- [ ] No placeholder text in critical actions
-
-## Type-Specific Validation
-
-### Simple Agent (Self-Contained)
-
-- [ ] Single .agent.yaml file with complete agent definition
-- [ ] No sidecar files (all content in YAML)
-- [ ] Not capability-limited - can be as powerful as Expert or Module
-- [ ] Compare against reference: commit-poet.agent.yaml
-
-### Expert Agent (With Sidecar Files)
-
-- [ ] Folder structure: .agent.yaml + sidecar files
-- [ ] Sidecar files properly referenced in menu items or prompts (tmpl="path", data="path")
-- [ ] Folder name matches agent purpose
-- [ ] **All sidecar references in YAML resolve to actual files**
-- [ ] **All sidecar files are actually used (no orphaned/unused files, unless intentional for future use)**
-- [ ] Sidecar files are valid format (YAML parses, CSV has headers, markdown is well-formed)
-- [ ] Sidecar file paths use relative paths from agent folder
-- [ ] Templates contain valid template variables if applicable
-- [ ] Knowledge base files contain current/accurate information
-- [ ] Compare against reference: journal-keeper (Expert example)
-
-### Module Agent (Ecosystem Integration)
-
-- [ ] Designed FOR specific module (BMM, BMGD, CIS, etc.)
-- [ ] Integrates with module workflows (referenced in menu items)
-- [ ] Coordinates with other module agents (if applicable)
-- [ ] Included in module's default bundle (if applicable)
-- [ ] Header comment explains WHY Module Agent (design intent, not just location)
-- [ ] Can be Simple OR Expert structurally (Module is about intent, not structure)
-- [ ] Compare against references: security-engineer, dev, analyst (Module examples)
-
-## Compilation Validation (Post-Build)
-
-- [ ] Agent compiles without errors to .md format
-- [ ] Compiled file has proper frontmatter (name, description)
-- [ ] Compiled XML structure is valid
-- [ ] `<agent>` tag has id, name, title, icon attributes
-- [ ] `<activation>` section is present with proper steps
-- [ ] `<persona>` section compiled correctly
-- [ ] `<menu>` section includes both user items AND auto-injected *help/*exit
-- [ ] Menu handlers section included (if menu items use workflow/exec/tmpl/data/action)
-
-## Quality Checks
-
-- [ ] No placeholder text remains ({{AGENT_NAME}}, {ROLE}, TODO, etc.)
-- [ ] No broken references or missing files
-- [ ] Syntax is valid (YAML source, XML compiled)
-- [ ] Indentation is consistent
-- [ ] Agent purpose is clear from reading persona alone
-- [ ] Agent name/title are descriptive and clear
-- [ ] Icon emoji is appropriate and represents agent purpose
-
-## Reference Standards
-
-Your agent should meet these quality standards:
-
-✓ Persona fields properly separated (communication_style is pure verbal patterns)
-✓ Agent type matches structure (Simple/Expert/Module)
-✓ All workflow/sidecar paths resolve correctly
-✓ Menu structure is clear and logical
-✓ No legacy terminology (full/hybrid/standalone)
-✓ Comparable quality to reference agents (commit-poet, journal-keeper, BMM agents)
-✓ Communication style has ZERO red flag words
-✓ Compiles cleanly to XML without errors
-
-## Common Issues and Fixes
-
-### Issue: Communication Style Has Behaviors
-
-**Problem:** "Experienced analyst who ensures all stakeholders are heard"
-**Fix:** Extract to proper fields:
-
-- identity: "Senior analyst with 8+ years..."
-- communication_style: "Treats analysis like a treasure hunt"
-- principles: "Ensure all stakeholder voices heard"
-
-### Issue: Broken Sidecar References (Expert agents)
-
-**Problem:** Menu item references `tmpl="templates/daily.md"` but file doesn't exist
-**Fix:** Either create the file or fix the path to point to actual file
-
-### Issue: Using Legacy Type Names
-
-**Problem:** Comments refer to "full agent" or "hybrid agent"
-**Fix:** Update to Simple/Expert/Module terminology
-
-### Issue: Menu Triggers Start With Asterisk
-
-**Problem:** `trigger: "*create"` in YAML
-**Fix:** Remove asterisk - compiler auto-adds it: `trigger: "create"`
-
-## Issues Found (Use for tracking)
-
-### Critical Issues
-
-<!-- List any issues that MUST be fixed before agent can function -->
-
-### Warnings
-
-<!-- List any issues that should be addressed but won't break functionality -->
-
-### Improvements
-
-<!-- List any optional enhancements that could improve the agent -->

package/src/modules/bmb/workflows/create-agent/data/info-and-installation-guide.md

@@ -1,29 +0,0 @@
-# {agent_name} Agent
-
-## Installation
-
-Create a `custom.yaml` file in the agent folder:
-
-```yaml
-code: { agent_code }
-name: '{agent_name}'
-default_selected: true
-```
-
-Then run:
-
-```bash
-npx bmad-method install
-```
-
-Or if you have bmad-cli installed globally:
-
-```bash
-bmad install
-```
-
-## About This Agent
-
-{agent_description}
-
-_Generated with BMAD Builder workflow_

package/src/modules/bmb/workflows/create-agent/data/reference/README.md

@@ -1,3 +0,0 @@
-# Reference Examples
-
-Reference models of best practices for agents, workflows, and whole modules.