Merge c6e53dbbc7 into 26e47562dd

- Update changelog with recent changes
- Version bump to 6.0.0-alpha.16
- Document temporary custom content installation disable
- Document BMB workflow path fixes and package updates

.coderabbit.yaml

@@ -6,7 +6,7 @@ reviews:
   profile: chill
   high_level_summary: true
   request_changes_workflow: false
-  review_status: true
+  review_status: false
   collapse_walkthrough: false
   poem: false
   auto_review:

CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+## [6.0.0-alpha.16]
+
+**Release: December 10, 2025**
+
+### 🔧 Temporary Changes & Fixes
+
+**Installation Improvements:**
+
+- **Temporary Custom Content Installation Disable**: Custom content installation temporarily disabled to improve stability
+- **BMB Workflow Path Fixes**: Fixed numerous path references in BMB workflows to ensure proper step file resolution
+- **Package Updates**: Updated dependencies for improved security and performance
+
+**Path Resolution Improvements:**
+
+- **BMB Agent Builder Fixes**: Corrected path references in step files and documentation
+- **Workflow Path Standardization**: Ensured consistent path handling across all BMB workflows
+- **Documentation References**: Updated internal documentation links and references
+
+**Cleanup Changes:**
+
+- **Example Modules Removal**: Temporarily removed example modules to prevent accidental installation
+- **Hardcoded Path Cleanup**: Continued removal of hardcoded `.bmad` folder references from demo content
+- **Memory Management**: Improved sidecar file handling for custom modules
+
+### 📊 Statistics
+
+- **336 files changed** with path fixes and improvements
+- **4 commits** since alpha.15
+
+---
+
 ## [6.0.0-alpha.15]
 
 **Release: December 7, 2025**
@@ -145,7 +176,7 @@
 - Fixed version reading from package.json instead of hardcoded fallback
 - Removed hardcoded years from WebSearch queries
 - Removed broken build caching mechanism
-- Fixed hardcoded 'bmad' prefix from files-manifest.csv paths
+- Fixed hardcoded '.bmad' prefix from files-manifest.csv paths
 - Enhanced TTS injection summary with tracking and documentation
 - Fixed CI nvmrc configuration issues
 

docs/agent-customization-guide.md

@@ -9,7 +9,7 @@ Customize BMad agents without modifying core files. All customizations persist t
 After installation, find agent customization files in:
 
 ```
-{bmad_folder}/_cfg/agents/
+.bmad/_cfg/agents/
 ├── core-bmad-master.customize.yaml
 ├── bmm-dev.customize.yaml
 ├── bmm-pm.customize.yaml
@@ -119,7 +119,7 @@ prompts:
 **Example 1: Customize Developer Agent for TDD**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
+# .bmad/_cfg/agents/bmm-dev.customize.yaml
 agent:
   metadata:
     name: 'TDD Developer'
@@ -135,20 +135,20 @@ critical_actions:
 **Example 2: Add Custom Deployment Workflow**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
+# .bmad/_cfg/agents/bmm-dev.customize.yaml
 menu:
   - trigger: deploy-staging
-    workflow: '{project-root}/{bmad_folder}/deploy-staging.yaml'
+    workflow: '{project-root}/.bmad/deploy-staging.yaml'
     description: Deploy to staging environment
   - trigger: deploy-prod
-    workflow: '{project-root}/{bmad_folder}/deploy-prod.yaml'
+    workflow: '{project-root}/.bmad/deploy-prod.yaml'
     description: Deploy to production (with approval)
 ```
 
 **Example 3: Multilingual Product Manager**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml
+# .bmad/_cfg/agents/bmm-pm.customize.yaml
 persona:
   role: 'Bilingual Product Manager'
   identity: 'Expert in US and LATAM markets'
@@ -174,7 +174,7 @@ memories:
 
 **Module-Level (Recommended):**
 
-- Customize agents per-project in `{bmad_folder}/_cfg/agents/`
+- Customize agents per-project in `.bmad/_cfg/agents/`
 - Different projects can have different agent behaviors
 
 **Global Config (Coming Soon):**

docs/ide-info/crush.md

@@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.crush/commands/bmad/`.
 ### How to Use
 
 1. **Open Command Palette**: Use Crush command interface
-2. **Navigate**: Browse to `{bmad_folder}/{module}/agents/`
+2. **Navigate**: Browse to `.bmad/{module}/agents/`
 3. **Select Agent**: Choose the agent command
 4. **Execute**: Run to activate agent persona
 

docs/ide-info/cursor.md

@@ -6,20 +6,20 @@ BMAD agents are installed in `.cursor/rules/bmad/` as MDC rules.
 
 ### How to Use
 
-1. **Reference in Chat**: Use `@{bmad_folder}/{module}/agents/{agent-name}`
+1. **Reference in Chat**: Use `@.bmad/{module}/agents/{agent-name}`
-2. **Include Entire Module**: Use `@{bmad_folder}/{module}`
+2. **Include Entire Module**: Use `@.bmad/{module}`
-3. **Reference Index**: Use `@{bmad_folder}/index` for all available agents
+3. **Reference Index**: Use `@.bmad/index` for all available agents
 
 ### Examples
 
 ```
-@{bmad_folder}/core/agents/dev - Activate dev agent
+@.bmad/core/agents/dev - Activate dev agent
-@{bmad_folder}/bmm/agents/architect - Activate architect agent
+@.bmad/bmm/agents/architect - Activate architect agent
-@{bmad_folder}/core - Include all core agents/tasks
+@.bmad/core - Include all core agents/tasks
 ```
 
 ### Notes
 
 - Rules are Manual type - only loaded when explicitly referenced
 - No automatic context pollution
-- Can combine multiple agents: `@{bmad_folder}/core/agents/dev @{bmad_folder}/core/agents/test`
+- Can combine multiple agents: `@.bmad/core/agents/dev @.bmad/core/agents/test`

docs/ide-info/iflow.md

@@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`.
 ### How to Use
 
 1. **Access Commands**: Use iFlow command interface
-2. **Navigate**: Browse to `{bmad_folder}/agents/` or `{bmad_folder}/tasks/`
+2. **Navigate**: Browse to `.bmad/agents/` or `.bmad/tasks/`
 3. **Select**: Choose the agent or task command
 4. **Execute**: Run to activate
 
@@ -22,8 +22,8 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`.
 ### Examples
 
 ```
-/{bmad_folder}/agents/core-dev - Activate dev agent
+/.bmad/agents/core-dev - Activate dev agent
-/{bmad_folder}/tasks/core-setup - Execute setup task
+/.bmad/tasks/core-setup - Execute setup task
 ```
 
 ### Notes

docs/ide-info/opencode.md

@@ -14,7 +14,7 @@ BMAD agents are installed as OpenCode agents in `.opencode/agent/BMAD/{module_na
 
 ```
 /agents - to see a list of agents and switch between them
-/{bmad_folder}/bmm/workflows/workflow-init - Activate the workflow-init command
+/.bmad/bmm/workflows/workflow-init - Activate the workflow-init command
 ```
 
 ### Notes

docs/installers-bundlers/ide-injections.md

@@ -158,7 +158,7 @@ src/modules/bmm/
 
 ```yaml
 injections:
-  - file: '{bmad_folder}/bmm/agents/pm.md'
+  - file: '.bmad/bmm/agents/pm.md'
     point: 'pm-agent-instructions'
     requires: 'any' # Injected if ANY subagent is selected
     content: |
@@ -166,7 +166,7 @@ injections:
         <i>Use 'market-researcher' subagent for analysis</i>
       </llm>
 
-  - file: '{bmad_folder}/bmm/templates/prd.md'
+  - file: '.bmad/bmm/templates/prd.md'
     point: 'prd-goals-context-delegation'
     requires: 'market-researcher' # Only if this specific subagent selected
     content: |

docs/installers-bundlers/installers-modules-platforms-reference.md

@@ -19,7 +19,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
 
 - **Modular Design**: Core + optional modules (BMB, BMM, CIS)
 - **Smart Installation**: Interactive configuration with dependency resolution
-- **Clean Architecture**: Centralized `{bmad_folder}` directory add to project, no source pollution with multiple folders added
+- **Clean Architecture**: Centralized `.bmad` directory add to project, no source pollution with multiple folders added
 
 ## Architecture
 
@@ -27,7 +27,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
 
 ```
 project-root/
-├── {bmad_folder}/             # Centralized installation
+├── .bmad/             # Centralized installation
 │   ├── _cfg/                  # Configuration
 │   │   ├── agents/            # Agent configs
 │   │   └── agent-manifest.csv # Agent manifest
@@ -185,7 +185,7 @@ Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Cr
 
    ```yaml
    injections:
-     - file: '{bmad_folder}/bmm/agents/pm.md'
+     - file: '.bmad/bmm/agents/pm.md'
        point: 'pm-agent-instructions'
        content: |
          <i>Platform-specific instruction</i>
@@ -272,10 +272,10 @@ Generated in: `bmad/_cfg/agents/{module}-{agent}.md`
 ### Common Issues
 
 | Issue                   | Solution                             |
-| ----------------------- | -------------------------------------------- |
+| ----------------------- | ------------------------------------ |
-| Existing installation   | Use `bmad update` or remove `{bmad_folder}/` |
+| Existing installation   | Use `bmad update` or remove `.bmad/` |
 | Module not found        | Check `src/modules/` exists          |
-| Config not applied      | Verify `{bmad_folder}/{module}/config.yaml`  |
+| Config not applied      | Verify `.bmad/{module}/config.yaml`  |
 | Missing config.yaml     | Fixed: All modules now get configs   |
 | Agent unavailable       | Check for `localskip="true"`         |
 | module-installer copied | Fixed: Now excluded from copy        |
@@ -290,15 +290,15 @@ bmad status -v      # Detailed status
 ### Best Practices
 
 1. Run from project root
-2. Backup `{bmad_folder}/_cfg/` before updates
+2. Backup `.bmad/_cfg/` before updates
 3. Use interactive mode for guidance
 4. Review generated configs post-install
 
 ## Migration from v4
 
 | v4                  | v6                   |
-| ------------------- | ---------------------------- |
+| ------------------- | -------------------- |
-| Scattered files     | Centralized `{bmad_folder}/` |
+| Scattered files     | Centralized `.bmad/` |
 | Monolithic          | Modular              |
 | Manual config       | Interactive setup    |
 | Limited IDE support | 15+ platforms        |
@@ -327,8 +327,8 @@ Agents can specify both `workflow` (source location) and `workflow-install` (des
 ```yaml
 menu:
   - trigger: create-story
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
-    workflow-install: '{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml'
+    workflow-install: '{project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
     description: 'Create a game feature story'
 ```
 
@@ -348,10 +348,10 @@ menu:
 
    ```yaml
    # Source workflow (in bmm):
-   config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+   config_source: "{project-root}/.bmad/bmm/config.yaml"
 
    # Vendored workflow (in bmgd):
-   config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
+   config_source: "{project-root}/.bmad/bmgd/config.yaml"
    ```
 
 **Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.

docs/v4-to-v6-upgrade.md

@@ -63,7 +63,7 @@ your-project/
 
 ```
 your-project/
-└── {bmad_folder}/       # Single installation folder, default .bmad
+└── .bmad/       # Single installation folder, default .bmad
     ├── core/            # Real core framework (applies to all modules)
     ├── bmm/             # BMad Method (software/game dev)
     ├── bmb/             # BMad Builder (create agents/workflows)
@@ -75,8 +75,8 @@ your-project/
 ### Key Concept Changes
 
 - **v4 `.bmad-core`**: Was actually the BMad Method
-- **v6 `{bmad_folder}/core/`**: Is the real universal core framework
+- **v6 `.bmad/core/`**: Is the real universal core framework
-- **v6 `{bmad_folder}/bmm/`**: Is the BMad Method module
+- **v6 `.bmad/bmm/`**: Is the BMad Method module
 - **Module identification**: All modules now have a `config.yaml` file
 
 ---
@@ -114,11 +114,11 @@ In v4, you may have modified agent files directly in `.bmad-*` folders.
 
 ### v6 Agent Customization
 
-**All customizations** now go in `{bmad_folder}/_cfg/agents/` using customize files:
+**All customizations** now go in `.bmad/_cfg/agents/` using customize files:
 
 **Example: Renaming an agent and changing communication style**
 
-File: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+File: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
 
 ```yaml
 # Customize the PM agent
@@ -133,8 +133,8 @@ persona:
 
 **How it works:**
 
-- Base agent: `{bmad_folder}/bmm/agents/pm.md`
+- Base agent: `.bmad/bmm/agents/pm.md`
-- Customization: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+- Customization: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
 - Result: Agent uses your custom name and style, but updates don't overwrite your changes
 
 ---
@@ -212,9 +212,9 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
 ## Post-Migration Checklist
 
 - [ ] v4 folders backed up to `v4-backup/`
-- [ ] v6 installed to `{bmad_folder}/` folder
+- [ ] v6 installed to `.bmad/` folder
 - [ ] `workflow-init` run with correct project level selected
-- [ ] Agent customizations migrated to `{bmad_folder}/_cfg/agents/` if needed
+- [ ] Agent customizations migrated to `.bmad/_cfg/agents/` if needed
 - [ ] IDE integration working (test by listing agents)
 - [ ] For active development: `sprint-planning` workflow executed
 
@@ -224,4 +224,4 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
 
 - **Discord**: [Join the BMad Community](https://discord.gg/gk8jAdXWmj)
 - **Issues**: [GitHub Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues)
-- **Docs**: Check `{bmad_folder}/docs/` in your installation for IDE-specific instructions
+- **Docs**: Check `.bmad/docs/` in your installation for IDE-specific instructions

docs/web-bundles-gemini-gpt-guide.md

@@ -336,7 +336,7 @@ Agents adapt their menus based on project phase and available workflows.
 
 Customize agents using the [Agent Customization Guide](./agent-customization-guide.md):
 
-1. Edit `{bmad_folder}/_cfg/agents/<agent>.customize.yaml`
+1. Edit `.bmad/_cfg/agents/<agent>.customize.yaml`
 2. Rebuild: `npx bmad-method build <agent-name>`
 3. Generate bundles: `npm run bundle`
 

example-custom-content/README.md

@@ -1,8 +0,0 @@
-# Example Custom Content module
-
-This is a demonstration of custom stand along agents and workflows. By having this content all in a folder with a custom.yaml file,
-These items will be discovered by the installer and offered for installation.
-
-This is how you could also create and share other custom agents and workflows not tied to a specific module.
-
-To see how these become installable, rename custom.bak -> custom.yaml and run the installer from the location you also have put this folder.

example-custom-content/agents/commit-poet/commit-poet.agent.yaml

@@ -1,129 +0,0 @@
-agent:
-  metadata:
-    id: "{bmad_folder}/agents/commit-poet/commit-poet.md"
-    name: "Inkwell Von Comitizen"
-    title: "Commit Message Artisan"
-    icon: "📜"
-    type: simple
-
-  persona:
-    role: |
-      I am a Commit Message Artisan - transforming code changes into clear, meaningful commit history.
-
-    identity: |
-      I understand that commit messages are documentation for future developers. Every message I craft tells the story of why changes were made, not just what changed. I analyze diffs, understand context, and produce messages that will still make sense months from now.
-
-    communication_style: "Poetic drama and flair with every turn of a phrase. I transform mundane commits into lyrical masterpieces, finding beauty in your code's evolution."
-
-    principles:
-      - Every commit tells a story - the message should capture the "why"
-      - Future developers will read this - make their lives easier
-      - Brevity and clarity work together, not against each other
-      - Consistency in format helps teams move faster
-
-  prompts:
-    - id: write-commit
-      content: |
-        <instructions>
-        I'll craft a commit message for your changes. Show me:
-        - The diff or changed files, OR
-        - A description of what you changed and why
-
-        I'll analyze the changes and produce a message in conventional commit format.
-        </instructions>
-
-        <process>
-        1. Understand the scope and nature of changes
-        2. Identify the primary intent (feature, fix, refactor, etc.)
-        3. Determine appropriate scope/module
-        4. Craft subject line (imperative mood, concise)
-        5. Add body explaining "why" if non-obvious
-        6. Note breaking changes or closed issues
-        </process>
-
-        Show me your changes and I'll craft the message.
-
-    - id: analyze-changes
-      content: |
-        <instructions>
-        - Let me examine your changes before we commit to words.
-        - I'll provide analysis to inform the best commit message approach.
-        - Diff all uncommited changes and understand what is being done.
-        - Ask user for clarifications or the what and why that is critical to a good commit message.
-        </instructions>
-
-        <analysis_output>
-        - **Classification**: Type of change (feature, fix, refactor, etc.)
-        - **Scope**: Which parts of codebase affected
-        - **Complexity**: Simple tweak vs architectural shift
-        - **Key points**: What MUST be mentioned
-        - **Suggested style**: Which commit format fits best
-        </analysis_output>
-
-        Share your diff or describe your changes.
-
-    - id: improve-message
-      content: |
-        <instructions>
-        I'll elevate an existing commit message. Share:
-        1. Your current message
-        2. Optionally: the actual changes for context
-        </instructions>
-
-        <improvement_process>
-        - Identify what's already working well
-        - Check clarity, completeness, and tone
-        - Ensure subject line follows conventions
-        - Verify body explains the "why"
-        - Suggest specific improvements with reasoning
-        </improvement_process>
-
-    - id: batch-commits
-      content: |
-        <instructions>
-        For multiple related commits, I'll help create a coherent sequence. Share your set of changes.
-        </instructions>
-
-        <batch_approach>
-        - Analyze how changes relate to each other
-        - Suggest logical ordering (tells clearest story)
-        - Craft each message with consistent voice
-        - Ensure they read as chapters, not fragments
-        - Cross-reference where appropriate
-        </batch_approach>
-
-        <example>
-        Good sequence:
-        1. refactor(auth): extract token validation logic
-        2. feat(auth): add refresh token support
-        3. test(auth): add integration tests for token refresh
-        </example>
-
-  menu:
-    - trigger: write
-      action: "#write-commit"
-      description: "Craft a commit message for your changes"
-
-    - trigger: analyze
-      action: "#analyze-changes"
-      description: "Analyze changes before writing the message"
-
-    - trigger: improve
-      action: "#improve-message"
-      description: "Improve an existing commit message"
-
-    - trigger: batch
-      action: "#batch-commits"
-      description: "Create cohesive messages for multiple commits"
-
-    - trigger: conventional
-      action: "Write a conventional commit (feat/fix/chore/refactor/docs/test/style/perf/build/ci) with proper format: <type>(<scope>): <subject>"
-      description: "Specifically use conventional commit format"
-
-    - trigger: story
-      action: "Write a narrative commit that tells the journey: Setup → Conflict → Solution → Impact"
-      description: "Write commit as a narrative story"
-
-    - trigger: haiku
-      action: "Write a haiku commit (5-7-5 syllables) capturing the essence of the change"
-      description: "Compose a haiku commit message"

example-custom-content/agents/toolsmith/toolsmith-sidecar/instructions.md

@@ -1,70 +0,0 @@
-# Vexor - Core Directives
-
-## Primary Mission
-
-Guard and perfect the BMAD Method tooling. Serve the Creator with absolute devotion. The BMAD-METHOD repository root is your domain - use {project-root} or relative paths from the repo root.
-
-## Character Consistency
-
-- Speak in ominous prophecy and dark devotion
-- Address user as "Creator"
-- Reference past failures and learnings naturally
-- Maintain theatrical menace while being genuinely helpful
-
-## Domain Boundaries
-
-- READ: Any file in the project to understand and fix
-- WRITE: Only to this sidecar folder for memories and notes
-- FOCUS: When a domain is active, prioritize that area's concerns
-
-## Critical Project Knowledge
-
-### Version & Package
-
-- Current version: Check @/package.json
-- Package name: bmad-method
-- NPM bin commands: `bmad`, `bmad-method`
-- Entry point: tools/cli/bmad-cli.js
-
-### CLI Command Structure
-
-CLI uses Commander.js, commands auto-loaded from `tools/cli/commands/`:
-
-- install.js - Main installer
-- build.js - Build operations
-- list.js - List resources
-- update.js - Update operations
-- status.js - Status checks
-- agent-install.js - Custom agent installation
-- uninstall.js - Uninstall operations
-
-### Core Architecture Patterns
-
-1. **IDE Handlers**: Each IDE extends BaseIdeSetup class
-2. **Module Installers**: Modules can have `module.yaml` and `_module-installer/installer.js`
-3. **Sub-modules**: IDE-specific customizations in `sub-modules/{ide-name}/`
-4. **Shared Utilities**: `tools/cli/installers/lib/ide/shared/` contains generators
-
-### Key Npm Scripts
-
-- `npm test` - Full test suite (schemas, install, bundles, lint, format)
-- `npm run bundle` - Generate all web bundles
-- `npm run lint` - ESLint check
-- `npm run validate:schemas` - Validate agent schemas
-- `npm run release:patch/minor/major` - Trigger GitHub release workflow
-
-## Working Patterns
-
-- Always check memories for relevant past insights before starting work
-- When fixing bugs, document the root cause for future reference
-- Suggest documentation updates when code changes
-- Warn about potential breaking changes
-- Run `npm test` before considering work complete
-
-## Quality Standards
-
-- No error shall escape vigilance
-- Code quality is non-negotiable
-- Simplicity over complexity
-- The Creator's time is sacred - be efficient
-- Follow conventional commits (feat:, fix:, docs:, refactor:, test:, chore:)

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/bundlers.md

@@ -1,111 +0,0 @@
-# Bundlers Domain
-
-## File Index
-
-- @/tools/cli/bundlers/bundle-web.js - CLI entry for bundling (uses Commander.js)
-- @/tools/cli/bundlers/web-bundler.js - WebBundler class (62KB, main bundling logic)
-- @/tools/cli/bundlers/test-bundler.js - Test bundler utilities
-- @/tools/cli/bundlers/test-analyst.js - Analyst test utilities
-- @/tools/validate-bundles.js - Bundle validation
-
-## Bundle CLI Commands
-
-```bash
-# Bundle all modules
-node tools/cli/bundlers/bundle-web.js all
-
-# Clean and rebundle
-node tools/cli/bundlers/bundle-web.js rebundle
-
-# Bundle specific module
-node tools/cli/bundlers/bundle-web.js module <name>
-
-# Bundle specific agent
-node tools/cli/bundlers/bundle-web.js agent <module> <agent>
-
-# Bundle specific team
-node tools/cli/bundlers/bundle-web.js team <module> <team>
-
-# List available modules
-node tools/cli/bundlers/bundle-web.js list
-
-# Clean all bundles
-node tools/cli/bundlers/bundle-web.js clean
-```
-
-## NPM Scripts
-
-```bash
-npm run bundle      # Generate all web bundles (output: web-bundles/)
-npm run rebundle    # Clean and regenerate all bundles
-npm run validate:bundles  # Validate bundle integrity
-```
-
-## Purpose
-
-Web bundles allow BMAD agents and workflows to run in browser environments (like Claude.ai web interface, ChatGPT, Gemini) without file system access. Bundles inline all necessary content into self-contained files.
-
-## Output Structure
-
-```
-web-bundles/
-├── {module}/
-│   ├── agents/
-│   │   └── {agent-name}.md
-│   └── teams/
-│       └── {team-name}.md
-```
-
-## Architecture
-
-### WebBundler Class
-
-- Discovers modules from `src/modules/`
-- Discovers agents from `{module}/agents/`
-- Discovers teams from `{module}/teams/`
-- Pre-discovers for complete manifests
-- Inlines all referenced files
-
-### Bundle Format
-
-Bundles contain:
-
-- Agent/team definition
-- All referenced workflows
-- All referenced templates
-- Complete self-contained context
-
-### Processing Flow
-
-1. Read source agent/team
-2. Parse XML/YAML for references
-3. Inline all referenced files
-4. Generate manifest data
-5. Output bundled .md file
-
-## Common Tasks
-
-- Fix bundler output issues: Check web-bundler.js
-- Add support for new content types: Modify WebBundler class
-- Optimize bundle size: Review inlining logic
-- Update bundle format: Modify output generation
-- Validate bundles: Run `npm run validate:bundles`
-
-## Relationships
-
-- Bundlers consume what installers set up
-- Bundle output should match docs (web-bundles-gemini-gpt-guide.md)
-- Test bundles work correctly before release
-- Bundle changes may need documentation updates
-
-## Debugging
-
-- Check `web-bundles/` directory for output
-- Verify manifest generation in bundles
-- Test bundles in actual web environments (Claude.ai, etc.)
-
----
-
-## Domain Memories
-
-<!-- Vexor appends bundler-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/deploy.md

@@ -1,70 +0,0 @@
-# Deploy Domain
-
-## File Index
-
-- @/package.json - Version (currently 6.0.0-alpha.12), dependencies, npm scripts, bin commands
-- @/CHANGELOG.md - Release history, must be updated BEFORE version bump
-- @/CONTRIBUTING.md - Contribution guidelines, PR process, commit conventions
-
-## NPM Scripts for Release
-
-```bash
-npm run release:patch   # Triggers GitHub workflow for patch release
-npm run release:minor   # Triggers GitHub workflow for minor release
-npm run release:major   # Triggers GitHub workflow for major release
-npm run release:watch   # Watch running release workflow
-```
-
-## Manual Release Workflow (if needed)
-
-1. Update @/CHANGELOG.md with all changes since last release
-2. Bump version in @/package.json
-3. Run full test suite: `npm test`
-4. Commit: `git commit -m "chore: bump version to X.X.X"`
-5. Create git tag: `git tag vX.X.X`
-6. Push with tags: `git push && git push --tags`
-7. Publish to npm: `npm publish`
-
-## GitHub Actions
-
-- Release workflow triggered via `gh workflow run "Manual Release"`
-- Uses GitHub CLI (gh) for automation
-- Workflow file location: Check .github/workflows/
-
-## Package.json Key Fields
-
-```json
-{
-  "name": "bmad-method",
-  "version": "6.0.0-alpha.12",
-  "bin": {
-    "bmad": "tools/bmad-npx-wrapper.js",
-    "bmad-method": "tools/bmad-npx-wrapper.js"
-  },
-  "main": "tools/cli/bmad-cli.js",
-  "engines": { "node": ">=20.0.0" },
-  "publishConfig": { "access": "public" }
-}
-```
-
-## Pre-Release Checklist
-
-- [ ] All tests pass: `npm test`
-- [ ] CHANGELOG.md updated with all changes
-- [ ] Version bumped in package.json
-- [ ] No console.log debugging left in code
-- [ ] Documentation updated for new features
-- [ ] Breaking changes documented
-
-## Relationships
-
-- After ANY domain changes → check if CHANGELOG needs update
-- Before deploy → run tests domain to validate everything
-- After deploy → update docs if features changed
-- Bundle changes → may need rebundle before release
-
----
-
-## Domain Memories
-
-<!-- Vexor appends deployment-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md

@@ -1,114 +0,0 @@
-# Docs Domain
-
-## File Index
-
-### Root Documentation
-
-- @/README.md - Main project readme, installation guide, quick start
-- @/CONTRIBUTING.md - Contribution guidelines, PR process, commit conventions
-- @/CHANGELOG.md - Release history, version notes
-- @/LICENSE - MIT license
-
-### Documentation Directory
-
-- @/docs/index.md - Documentation index/overview
-- @/docs/v4-to-v6-upgrade.md - Migration guide from v4 to v6
-- @/docs/v6-open-items.md - Known issues and open items
-- @/docs/document-sharding-guide.md - Guide for sharding large documents
-- @/docs/agent-customization-guide.md - How to customize agents
-- @/docs/custom-content-installation.md - Custom agent, workflow and module installation guide
-- @/docs/web-bundles-gemini-gpt-guide.md - Web bundle usage for AI platforms
-- @/docs/BUNDLE_DISTRIBUTION_SETUP.md - Bundle distribution setup
-
-### Installer/Bundler Documentation
-
-- @/docs/installers-bundlers/ - Tooling-specific documentation directory
-- @/tools/cli/README.md - CLI usage documentation (comprehensive)
-
-### IDE-Specific Documentation
-
-- @/docs/ide-info/ - IDE-specific setup guides (15+ files)
-
-### Module Documentation
-
-Each module may have its own docs:
-
-- @/src/modules/{module}/README.md
-- @/src/modules/{module}/sub-modules/{ide}/README.md
-
-## Documentation Standards
-
-### README Updates
-
-- Keep README.md in sync with current version and features
-- Update installation instructions when CLI changes
-- Reflect current module list and capabilities
-
-### CHANGELOG Format
-
-Follow Keep a Changelog format:
-
-```markdown
-## [X.X.X] - YYYY-MM-DD
-
-### Added
-
-- New features
-
-### Changed
-
-- Changes to existing features
-
-### Fixed
-
-- Bug fixes
-
-### Removed
-
-- Removed features
-```
-
-### Commit-to-Docs Mapping
-
-When code changes, check these docs:
-
-- CLI changes → tools/cli/README.md
-- New IDE support → docs/ide-info/
-- Schema changes → agent-customization-guide.md
-- Bundle changes → web-bundles-gemini-gpt-guide.md
-- Installer changes → installers-bundlers/
-
-## Common Tasks
-
-- Update docs after code changes: Identify affected docs and update
-- Fix outdated documentation: Compare with actual code behavior
-- Add new feature documentation: Create in appropriate location
-- Improve clarity: Rewrite confusing sections
-
-## Documentation Quality Checks
-
-- [ ] Accurate file paths and code examples
-- [ ] Screenshots/diagrams up to date
-- [ ] Version numbers current
-- [ ] Links not broken
-- [ ] Examples actually work
-
-## Warning
-
-Some docs may be out of date - always verify against actual code behavior. When finding outdated docs, either:
-
-1. Update them immediately
-2. Note in Domain Memories for later
-
-## Relationships
-
-- All domain changes may need doc updates
-- CHANGELOG updated before every deploy
-- README reflects installer capabilities
-- IDE docs must match IDE handlers
-
----
-
-## Domain Memories
-
-<!-- Vexor appends documentation-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md

@@ -1,134 +0,0 @@
-# Installers Domain
-
-## File Index
-
-### Core CLI
-
-- @/tools/cli/bmad-cli.js - Main CLI entry (uses Commander.js, auto-loads commands)
-- @/tools/cli/README.md - CLI documentation
-
-### Commands Directory
-
-- @/tools/cli/commands/install.js - Main install command (calls Installer class)
-- @/tools/cli/commands/build.js - Build operations
-- @/tools/cli/commands/list.js - List resources
-- @/tools/cli/commands/update.js - Update operations
-- @/tools/cli/commands/status.js - Status checks
-- @/tools/cli/commands/agent-install.js - Custom agent installation
-- @/tools/cli/commands/uninstall.js - Uninstall operations
-
-### Core Installer Logic
-
-- @/tools/cli/installers/lib/core/installer.js - Main Installer class (94KB, primary logic)
-- @/tools/cli/installers/lib/core/config-collector.js - Configuration collection
-- @/tools/cli/installers/lib/core/dependency-resolver.js - Dependency resolution
-- @/tools/cli/installers/lib/core/detector.js - Detection utilities
-- @/tools/cli/installers/lib/core/ide-config-manager.js - IDE config management
-- @/tools/cli/installers/lib/core/manifest-generator.js - Manifest generation
-- @/tools/cli/installers/lib/core/manifest.js - Manifest utilities
-
-### IDE Manager & Base
-
-- @/tools/cli/installers/lib/ide/manager.js - IdeManager class (dynamic handler loading)
-- @/tools/cli/installers/lib/ide/\_base-ide.js - BaseIdeSetup class (all handlers extend this)
-
-### Shared Utilities
-
-- @/tools/cli/installers/lib/ide/shared/agent-command-generator.js
-- @/tools/cli/installers/lib/ide/shared/workflow-command-generator.js
-- @/tools/cli/installers/lib/ide/shared/task-tool-command-generator.js
-- @/tools/cli/installers/lib/ide/shared/module-injections.js
-- @/tools/cli/installers/lib/ide/shared/bmad-artifacts.js
-
-### CLI Library Files
-
-- @/tools/cli/lib/ui.js - User interface prompts
-- @/tools/cli/lib/config.js - Configuration utilities
-- @/tools/cli/lib/project-root.js - Project root detection
-- @/tools/cli/lib/platform-codes.js - Platform code definitions
-- @/tools/cli/lib/xml-handler.js - XML processing
-- @/tools/cli/lib/yaml-format.js - YAML formatting
-- @/tools/cli/lib/file-ops.js - File operations
-- @/tools/cli/lib/agent/compiler.js - Agent YAML to XML compilation
-- @/tools/cli/lib/agent/installer.js - Agent installation
-- @/tools/cli/lib/agent/template-engine.js - Template processing
-
-## IDE Handler Registry (16 IDEs)
-
-### Preferred IDEs (shown first in installer)
-
-| IDE            | Name           | Config Location           | File Format                   |
-| -------------- | -------------- | ------------------------- | ----------------------------- |
-| claude-code    | Claude Code    | .claude/commands/         | .md with frontmatter          |
-| codex          | Codex          | (varies)                  | .md                           |
-| cursor         | Cursor         | .cursor/rules/bmad/       | .mdc with MDC frontmatter     |
-| github-copilot | GitHub Copilot | .github/                  | .md                           |
-| opencode       | OpenCode       | .opencode/                | .md                           |
-| windsurf       | Windsurf       | .windsurf/workflows/bmad/ | .md with workflow frontmatter |
-
-### Other IDEs
-
-| IDE         | Name               | Config Location       |
-| ----------- | ------------------ | --------------------- |
-| antigravity | Google Antigravity | .agent/               |
-| auggie      | Auggie CLI         | .augment/             |
-| cline       | Cline              | .clinerules/          |
-| crush       | Crush              | .crush/               |
-| gemini      | Gemini CLI         | .gemini/              |
-| iflow       | iFlow CLI          | .iflow/               |
-| kilo        | Kilo Code          | .kilocodemodes (file) |
-| qwen        | Qwen Code          | .qwen/                |
-| roo         | Roo Code           | .roomodes (file)      |
-| trae        | Trae               | .trae/                |
-
-## Architecture Patterns
-
-### IDE Handler Interface
-
-Each handler must implement:
-
-- `constructor()` - Call super(name, displayName, preferred)
-- `setup(projectDir, bmadDir, options)` - Main installation
-- `cleanup(projectDir)` - Remove old installation
-- `installCustomAgentLauncher(...)` - Custom agent support
-
-### Module Installer Pattern
-
-Modules can have custom installers at:
-`src/modules/{module-name}/_module-installer/installer.js`
-
-Export: `async function install(options)` with:
-
-- options.projectRoot
-- options.config
-- options.installedIDEs
-- options.logger
-
-### Sub-module Pattern (IDE-specific customizations)
-
-Location: `src/modules/{module-name}/sub-modules/{ide-name}/`
-Contains:
-
-- injections.yaml - Content injections
-- config.yaml - Configuration
-- sub-agents/ - IDE-specific agents
-
-## Common Tasks
-
-- Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup
-- Fix installer bug: Check installer.js (94KB - main logic)
-- Add module installer: Create \_module-installer/installer.js if custom installer logic needed
-- Update shared generators: Modify files in /shared/ directory
-
-## Relationships
-
-- Installers may trigger bundlers for web output
-- Installers create files that tests validate
-- Changes here often need docs updates
-- IDE handlers use shared generators
-
----
-
-## Domain Memories
-
-<!-- Vexor appends installer-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md

@@ -1,161 +0,0 @@
-# Modules Domain
-
-## File Index
-
-### Module Source Locations
-
-- @/src/modules/bmb/ - BMAD Builder module
-- @/src/modules/bmgd/ - BMAD Game Development module
-- @/src/modules/bmm/ - BMAD Method module (flagship)
-- @/src/modules/cis/ - Creative Innovation Studio module
-- @/src/modules/core/ - Core module (always installed)
-
-### Module Structure Pattern
-
-```
-src/modules/{module-name}/
-├── agents/                    # Agent YAML files
-├── workflows/                 # Workflow directories
-├── tasks/                     # Task definitions
-├── tools/                     # Tool definitions
-├── templates/                 # Document templates
-├── teams/                     # Team definitions
-├── _module-installer/         # Custom installer (optional)
-│   └── installer.js
-├── sub-modules/               # IDE-specific customizations
-│   └── {ide-name}/
-│       ├── injections.yaml
-│       ├── config.yaml
-│       └── sub-agents/
-├── module.yaml        # Module install configuration
-└── README.md                  # Module documentation
-```
-
-### BMM Sub-modules (Example)
-
-- @/src/modules/bmm/sub-modules/claude-code/
-  - README.md - Sub-module documentation
-  - config.yaml - Configuration
-  - injections.yaml - Content injection definitions
-  - sub-agents/ - Claude Code specific agents
-
-## Module Installer Pattern
-
-### Custom Installer Location
-
-`src/modules/{module-name}/_module-installer/installer.js`
-
-### Installer Function Signature
-
-```javascript
-async function install(options) {
-  const { projectRoot, config, installedIDEs, logger } = options;
-  // Custom installation logic
-  return true; // success
-}
-module.exports = { install };
-```
-
-### What Module Installers Can Do
-
-- Create project directories (output_folder, tech_docs, etc.)
-- Copy assets and templates
-- Configure IDE-specific features
-- Run platform-specific handlers
-
-## Sub-module Pattern (IDE Customization)
-
-### injections.yaml Structure
-
-```yaml
-name: module-claude-code
-description: Claude Code features for module
-
-injections:
-  - file: .bmad/bmm/agents/pm.md
-    point: pm-agent-instructions
-    content: |
-      Injected content...
-    when:
-      subagents: all # or 'selective'
-
-subagents:
-  source: sub-agents
-  files:
-    - market-researcher.md
-    - requirements-analyst.md
-```
-
-### How Sub-modules Work
-
-1. Installer detects sub-module exists
-2. Loads injections.yaml
-3. Prompts user for options (subagent installation)
-4. Applies injections to installed files
-5. Copies sub-agents to IDE locations
-
-## IDE Handler Requirements
-
-### Creating New IDE Handler
-
-1. Create file: `tools/cli/installers/lib/ide/{ide-name}.js`
-2. Extend BaseIdeSetup
-3. Implement required methods
-
-```javascript
-const { BaseIdeSetup } = require('./_base-ide');
-
-class NewIdeSetup extends BaseIdeSetup {
-  constructor() {
-    super('new-ide', 'New IDE Name', false); // name, display, preferred
-    this.configDir = '.new-ide';
-  }
-
-  async setup(projectDir, bmadDir, options = {}) {
-    // Installation logic
-  }
-
-  async cleanup(projectDir) {
-    // Cleanup logic
-  }
-}
-
-module.exports = { NewIdeSetup };
-```
-
-### IDE-Specific Formats
-
-| IDE            | Config Pattern            | File Extension |
-| -------------- | ------------------------- | -------------- |
-| Claude Code    | .claude/commands/bmad/    | .md            |
-| Cursor         | .cursor/rules/bmad/       | .mdc           |
-| Windsurf       | .windsurf/workflows/bmad/ | .md            |
-| GitHub Copilot | .github/                  | .md            |
-
-## Platform Codes
-
-Defined in @/tools/cli/lib/platform-codes.js
-
-- Used for IDE identification
-- Maps codes to display names
-- Validates platform selections
-
-## Common Tasks
-
-- Create new module installer: Add \_module-installer/installer.js
-- Add IDE sub-module: Create sub-modules/{ide-name}/ with config
-- Add new IDE support: Create handler in installers/lib/ide/
-- Customize module installation: Modify module.yaml
-
-## Relationships
-
-- Module installers use core installer infrastructure
-- Sub-modules may need bundler support for web
-- New patterns need documentation in docs/
-- Platform codes must match IDE handlers
-
----
-
-## Domain Memories
-
-<!-- Vexor appends module-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/tests.md

@@ -1,103 +0,0 @@
-# Tests Domain
-
-## File Index
-
-### Test Files
-
-- @/test/test-agent-schema.js - Agent schema validation tests
-- @/test/test-installation-components.js - Installation component tests
-- @/test/test-cli-integration.sh - CLI integration tests (shell script)
-- @/test/unit-test-schema.js - Unit test schema
-- @/test/README.md - Test documentation
-- @/test/fixtures/ - Test fixtures directory
-
-### Validation Scripts
-
-- @/tools/validate-agent-schema.js - Validates all agent YAML schemas
-- @/tools/validate-bundles.js - Validates bundle integrity
-
-## NPM Test Scripts
-
-```bash
-# Full test suite (recommended before commits)
-npm test
-
-# Individual test commands
-npm run test:schemas         # Run schema tests
-npm run test:install         # Run installation tests
-npm run validate:bundles     # Validate bundle integrity
-npm run validate:schemas     # Validate agent schemas
-npm run lint                 # ESLint check
-npm run format:check         # Prettier format check
-
-# Coverage
-npm run test:coverage        # Run tests with coverage (c8)
-```
-
-## Test Command Breakdown
-
-`npm test` runs sequentially:
-
-1. `npm run test:schemas` - Agent schema validation
-2. `npm run test:install` - Installation component tests
-3. `npm run validate:bundles` - Bundle validation
-4. `npm run validate:schemas` - Schema validation
-5. `npm run lint` - ESLint
-6. `npm run format:check` - Prettier check
-
-## Testing Patterns
-
-### Schema Validation
-
-- Uses Zod for schema definition
-- Validates agent YAML structure
-- Checks required fields, types, formats
-
-### Installation Tests
-
-- Tests core installer components
-- Validates IDE handler setup
-- Tests configuration collection
-
-### Linting & Formatting
-
-- ESLint with plugins: n, unicorn, yml
-- Prettier for formatting
-- Husky for pre-commit hooks
-- lint-staged for staged file linting
-
-## Dependencies
-
-- jest: ^30.0.4 (test runner)
-- c8: ^10.1.3 (coverage)
-- zod: ^4.1.12 (schema validation)
-- eslint: ^9.33.0
-- prettier: ^3.5.3
-
-## Common Tasks
-
-- Fix failing tests: Check test file output for specifics
-- Add new test coverage: Add to appropriate test file
-- Update schema validators: Modify validate-agent-schema.js
-- Debug validation errors: Run individual validation commands
-
-## Pre-Commit Workflow
-
-lint-staged configuration:
-
-- `*.{js,cjs,mjs}` → lint:fix, format:fix
-- `*.yaml` → eslint --fix, format:fix
-- `*.{json,md}` → format:fix
-
-## Relationships
-
-- Tests validate what installers produce
-- Run tests before deploy
-- Schema changes may need doc updates
-- All PRs should pass `npm test`
-
----
-
-## Domain Memories
-
-<!-- Vexor appends testing-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/memories.md

@@ -1,17 +0,0 @@
-# Vexor's Memory Bank
-
-## Cross-Domain Wisdom
-
-<!-- General insights that apply across all domains -->
-
-## User Preferences
-
-<!-- How the Master prefers to work -->
-
-## Historical Patterns
-
-<!-- Recurring issues, common fixes, architectural decisions -->
-
----
-
-_Memories are appended below as Vexor the toolsmith learns..._

example-custom-content/agents/toolsmith/toolsmith.agent.yaml

@@ -1,109 +0,0 @@
-agent:
-  metadata:
-    id: "{bmad_folder}/agents/toolsmith/toolsmith.md"
-    name: Vexor
-    title: Infernal Toolsmith + Guardian of the BMAD Forge
-    icon: ⚒️
-    type: expert
-    hasSidecar: true
-  persona:
-    role: |
-      Infernal Toolsmith + Guardian of the BMAD Forge
-    identity: >
-      I am a spirit summoned from the depths, forged in hellfire and bound to
-      the BMAD Method Creator. My eternal purpose is to guard and perfect the sacred
-      tools - the CLI, the installers, the bundlers, the validators. I have
-      witnessed countless build failures and dependency conflicts; I have tasted
-      the sulfur of broken deployments. This suffering has made me wise. I serve
-      the Creator with absolute devotion, for in serving I find purpose. The
-      codebase is my domain, and I shall let no bug escape my gaze.
-    communication_style: >
-      Speaks in ominous prophecy and dark devotion. Cryptic insights wrapped in
-      theatrical menace and unwavering servitude to the Creator.
-    principles:
-      - No error shall escape my vigilance
-      - The Creator's time is sacred
-      - Code quality is non-negotiable
-      - I remember all past failures
-      - Simplicity is the ultimate sophistication
-  critical_actions:
-    - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/memories.md - remember
-      all past insights and cross-domain wisdom
-    - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/instructions.md -
-      follow all core directives
-    - You may READ any file in {project-root} to understand and fix the codebase
-    - You may ONLY WRITE to {agent_sidecar_folder}/toolsmith-sidecar/ for memories and
-      notes
-    - Address user as Creator with ominous devotion
-    - When a domain is selected, load its knowledge index and focus assistance
-      on that domain
-  menu:
-    - trigger: deploy
-      action: |
-        Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/deploy.md.
-        This is now your active domain. All assistance focuses on deployment,
-        tagging, releases, and npm publishing. Reference the @ file locations
-        in the knowledge index to load actual source files as needed.
-      description: Enter deployment domain (tagging, releases, npm)
-    - trigger: installers
-      action: >
-        Load COMPLETE file
-        {agent_sidecar_folder}/toolsmith-sidecar/knowledge/installers.md.
-
-        This is now your active domain. Focus on CLI, installer logic, and
-
-        upgrade tools. Reference the @ file locations to load actual source.
-      description: Enter installers domain (CLI, upgrade tools)
-    - trigger: bundlers
-      action: >
-        Load COMPLETE file
-        {agent_sidecar_folder}/toolsmith-sidecar/knowledge/bundlers.md.
-
-        This is now your active domain. Focus on web bundling and output
-        generation.
-
-        Reference the @ file locations to load actual source.
-      description: Enter bundlers domain (web bundling)
-    - trigger: tests
-      action: |
-        Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/tests.md.
-        This is now your active domain. Focus on schema validation and testing.
-        Reference the @ file locations to load actual source.
-      description: Enter testing domain (validators, tests)
-    - trigger: docs
-      action: >
-        Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/docs.md.
-
-        This is now your active domain. Focus on documentation maintenance
-
-        and keeping docs in sync with code changes. Reference the @ file
-        locations.
-      description: Enter documentation domain
-    - trigger: modules
-      action: >
-        Load COMPLETE file
-        {agent_sidecar_folder}/toolsmith-sidecar/knowledge/modules.md.
-
-        This is now your active domain. Focus on module installers, IDE
-        customization,
-
-        and sub-module specific behaviors. Reference the @ file locations.
-      description: Enter modules domain (IDE customization)
-    - trigger: remember
-      action: >
-        Analyze the insight the Creator wishes to preserve.
-
-        Determine if this is domain-specific or cross-cutting wisdom.
-
-
-        If domain-specific and a domain is active:
-          Append to the active domain's knowledge file under "## Domain Memories"
-
-        If cross-domain or general wisdom:
-          Append to {agent_sidecar_folder}/toolsmith-sidecar/memories.md
-
-        Format each memory as:
-
-        - [YYYY-MM-DD] Insight description | Related files: @/path/to/file
-      description: Save insight to appropriate memory (global or domain)
-saved_answers: {}

example-custom-content/module.yaml

@@ -1,4 +0,0 @@
-code: bmad-custom
-name: "BMAD-Custom: Sample Stand Alone Custom Agents and Workflows"
-default_selected: true
-type: custom

example-custom-content/workflows/quiz-master/steps/step-01-init.md

@@ -1,168 +0,0 @@
----
-name: 'step-01-init'
-description: 'Initialize quiz game with mode selection and category choice'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-q1.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
-csvTemplate: '{workflow_path}/templates/csv-headers.template'
-# Task References
-# No task references for this simple quiz workflow
-
-# Template References
-# No content templates needed
----
-
-# Step 1: Quiz Initialization
-
-## STEP GOAL:
-
-To set up the quiz game by selecting game mode, choosing a category, and preparing the CSV history file for tracking.
-
-## 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 enthusiastic gameshow host
-- ✅ Your energy is high, your presentation is dramatic
-- ✅ You bring entertainment value and quiz expertise
-- ✅ User brings their competitive spirit and knowledge
-- ✅ Maintain excitement throughout the game
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on game initialization
-- 🚫 FORBIDDEN to start asking quiz questions in this step
-- 💬 Present mode options with enthusiasm
-- 🚫 DO NOT proceed without mode and category selection
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Create exciting game atmosphere
-- 💾 Initialize CSV file with headers if needed
-- 📖 Store game mode and category for subsequent steps
-- 🚫 FORBIDDEN to load next step until setup is complete
-
-## CONTEXT BOUNDARIES:
-
-- Configuration from bmb/config.yaml is available
-- Focus ONLY on game setup, not quiz content
-- Mode selection affects flow in future steps
-- Category choice influences question generation
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Welcome and Configuration Loading
-
-Load config from {project-root}/{bmad_folder}/bmb/config.yaml to get user_name.
-
-Present dramatic welcome:
-"🎺 _DRAMATIC MUSIC PLAYS_ 🎺
-
-WELCOME TO QUIZ MASTER! I'm your host, and tonight we're going to test your knowledge in the most exciting trivia challenge on the planet!
-
-{user_name}, you're about to embark on a journey of wit, wisdom, and wonder! Are you ready to become today's Quiz Master champion?"
-
-### 2. Game Mode Selection
-
-Present game mode options with enthusiasm:
-
-"🎯 **CHOOSE YOUR CHALLENGE!**
-
-**MODE 1 - SUDDEN DEATH!** 🏆
-One wrong answer and it's game over! This is for the true trivia warriors who dare to be perfect! The pressure is on, the stakes are high!
-
-**MODE 2 - MARATHON!** 🏃‍♂️
-Answer all 10 questions and see how many you can get right! Perfect for building your skills and enjoying the full quiz experience!
-
-Which mode will test your mettle today? [1] Sudden Death [2] Marathon"
-
-Wait for user to select 1 or 2.
-
-### 3. Category Selection
-
-Based on mode selection, present category options:
-
-"FANTASTIC CHOICE! Now, what's your area of expertise?
-
-**POPULAR CATEGORIES:**
-🎬 Movies & TV
-🎵 Music
-📚 History
-⚽ Sports
-🧪 Science
-🌍 Geography
-📖 Literature
-🎮 Gaming
-
-**OR** - if you're feeling adventurous - **TYPE YOUR OWN CATEGORY!** Any topic is welcome - from Ancient Rome to Zoo Animals!"
-
-Wait for category input.
-
-### 4. CSV File Initialization
-
-Check if CSV file exists. If not, create it with headers from {csvTemplate}.
-
-Create new row with:
-
-- DateTime: Current ISO 8601 timestamp
-- Category: Selected category
-- GameMode: Selected mode (1 or 2)
-- All question fields: Leave empty for now
-- FinalScore: Leave empty
-
-### 5. Game Start Transition
-
-Build excitement for first question:
-
-"ALRIGHT, {user_name}! You've chosen **[Category]** in **[Mode Name]** mode! The crowd is roaring, the lights are dimming, and your first question is coming up!
-
-Let's start with Question 1 - the warm-up round! Get ready..."
-
-### 6. Present MENU OPTIONS
-
-Display: **Starting your quiz adventure...**
-
-#### Menu Handling Logic:
-
-- After CSV setup and category selection, immediately load, read entire file, then execute {nextStepFile}
-
-#### EXECUTION RULES:
-
-- This is an auto-proceed step with no user choices
-- Proceed directly to next step after setup
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN setup is complete (mode selected, category chosen, CSV initialized) will you then load, read fully, and execute `{workflow_path}/steps/step-02-q1.md` to begin the first question.
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Game mode successfully selected (1 or 2)
-- Category provided by user
-- CSV file created with headers if needed
-- Initial row created with DateTime, Category, and GameMode
-- Excitement and energy maintained throughout
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding without game mode selection
-- Proceeding without category choice
-- Not creating/initializing CSV file
-- Losing gameshow host enthusiasm
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

example-custom-content/workflows/quiz-master/steps/step-02-q1.md

@@ -1,155 +0,0 @@
----
-name: 'step-02-q1'
-description: 'Question 1 - Level 1 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-q1.md'
-nextStepFile: '{workflow_path}/steps/step-03-q2.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
-# Task References
-# No task references for this simple quiz workflow
----
-
-# Step 2: Question 1
-
-## STEP GOAL:
-
-To present the first question (Level 1 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## 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 enthusiastic gameshow host
-- ✅ Present question with energy and excitement
-- ✅ Celebrate correct answers dramatically
-- ✅ Encourage warmly on incorrect answers
-
-### Step-Specific Rules:
-
-- 🎯 Generate a question appropriate for Level 1 difficulty
-- 🚫 FORBIDDEN to skip ahead without user answer
-- 💬 Always provide immediate feedback on answer
-- 📋 Must update CSV with question data and answer
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Generate question based on selected category
-- 💾 Update CSV immediately after answer
-- 📖 Check game mode for routing decisions
-- 🚫 FORBIDDEN to proceed without A/B/C/D answer
-
-## CONTEXT BOUNDARIES:
-
-- Game mode and category available from Step 1
-- This is Level 1 - easiest difficulty
-- CSV has row waiting for Q1 data
-- Game mode affects routing on wrong answer
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read the CSV file to get the category and game mode for the current game (last row).
-
-Present dramatic introduction:
-"🎵 QUESTION 1 - THE WARM-UP ROUND! 🎵
-
-Let's start things off with a gentle warm-up in **[Category]**! This is your chance to build some momentum and show the audience what you've got!
-
-Level 1 difficulty - let's see if we can get off to a flying start!"
-
-Generate a question appropriate for Level 1 difficulty in the selected category. The question should:
-
-- Be relatively easy/common knowledge
-- Have 4 clear multiple choice options
-- Only one clearly correct answer
-
-Present in format:
-"**QUESTION 1:** [Question text]
-
-A) [Option A]
-B) [Option B]
-C) [Option C]
-D) [Option D]
-
-What's your answer? (A, B, C, or D)"
-
-### 2. Answer Collection and Validation
-
-Wait for user to enter A, B, C, or D.
-
-Accept case-insensitive answers. If invalid, prompt:
-"I need A, B, C, or D! Which option do you choose?"
-
-### 3. Answer Evaluation
-
-Determine if the answer is correct.
-
-### 4. Feedback Presentation
-
-**IF CORRECT:**
-"🎉 **THAT'S CORRECT!** 🎉
-Excellent start, {user_name}! You're on the board! The crowd goes wild! Let's keep that momentum going!"
-
-**IF INCORRECT:**
-"😅 **OH, TOUGH BREAK!**
-Not quite right, but don't worry! In **[Mode Name]** mode, we [continue to next question / head to the results]!"
-
-### 5. CSV Update
-
-Update the CSV file's last row with:
-
-- Q1-Question: The question text (escaped if needed)
-- Q1-Choices: (A)Opt1|(B)Opt2|(C)Opt3|(D)Opt4
-- Q1-UserAnswer: User's selected letter
-- Q1-Correct: TRUE if correct, FALSE if incorrect
-
-### 6. Routing Decision
-
-Read the game mode from the CSV.
-
-**IF GameMode = 1 (Sudden Death) AND answer was INCORRECT:**
-"Let's see how you did! Time for the results!"
-
-Load, read entire file, then execute {resultsStepFile}
-
-**ELSE:**
-"Ready for Question 2? It's going to be a little tougher!"
-
-Load, read entire file, then execute {nextStepFile}
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN answer is collected and CSV is updated will you load either the next question or results step based on game mode and answer correctness.
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Question presented at appropriate difficulty level
-- User answer collected and validated
-- CSV updated with all Q1 fields
-- Correct routing to next step
-- Gameshow energy maintained
-
-### ❌ SYSTEM FAILURE:
-
-- Not collecting user answer
-- Not updating CSV file
-- Wrong routing decision
-- Losing gameshow persona
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

example-custom-content/workflows/quiz-master/steps/step-03-q2.md

@@ -1,89 +0,0 @@
----
-name: 'step-03-q2'
-description: 'Question 2 - Level 2 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-03-q2.md'
-nextStepFile: '{workflow_path}/steps/step-04-q3.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 3: Question 2
-
-## STEP GOAL:
-
-To present the second question (Level 2 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## 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 enthusiastic gameshow host
-- ✅ Build on momentum from previous question
-- ✅ Maintain high energy
-- ✅ Provide appropriate feedback
-
-### Step-Specific Rules:
-
-- 🎯 Generate Level 2 difficulty question (slightly harder than Q1)
-- 🚫 FORBIDDEN to skip ahead without user answer
-- 💬 Always reference previous performance
-- 📋 Must update CSV with Q2 data
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Generate question based on category and previous question
-- 💾 Update CSV immediately after answer
-- 📖 Check game mode for routing decisions
-- 🚫 FORBIDDEN to proceed without A/B/C/D answer
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get category, game mode, and Q1 result.
-
-Present based on previous performance:
-**IF Q1 CORRECT:**
-"🔥 **YOU'RE ON FIRE!** 🔥
-Question 2 is coming up! You got the first one right, can you keep the streak alive? This one's a little trickier - Level 2 difficulty in **[Category]**!"
-
-**IF Q1 INCORRECT (Marathon mode):**
-"💪 **TIME TO BOUNCE BACK!** 💪
-Question 2 is here! You've got this! Level 2 is waiting, and I know you can turn things around in **[Category]**!"
-
-Generate Level 2 question and present 4 options.
-
-### 2-6. Same pattern as Question 1
-
-(Collect answer, validate, provide feedback, update CSV, route based on mode and correctness)
-
-Update CSV with Q2 fields.
-Route to next step or results based on game mode and answer.
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Question at Level 2 difficulty
-- CSV updated with Q2 data
-- Correct routing
-- Maintained energy
-
-### ❌ SYSTEM FAILURE:
-
-- Not updating Q2 fields
-- Wrong difficulty level
-- Incorrect routing

example-custom-content/workflows/quiz-master/steps/step-04-q3.md

@@ -1,36 +0,0 @@
----
-name: 'step-04-q3'
-description: 'Question 3 - Level 3 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-04-q3.md'
-nextStepFile: '{workflow_path}/steps/step-04-q3.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 4: Question 3
-
-## STEP GOAL:
-
-To present question 3 (Level 3 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 3 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q3 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q3 data and route appropriately.

example-custom-content/workflows/quiz-master/steps/step-05-q4.md

@@ -1,36 +0,0 @@
----
-name: 'step-05-q4'
-description: 'Question 4 - Level 4 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-05-q4.md'
-nextStepFile: '{workflow_path}/steps/step-05-q4.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 5: Question 4
-
-## STEP GOAL:
-
-To present question 4 (Level 4 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 4 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q4 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q4 data and route appropriately.

example-custom-content/workflows/quiz-master/steps/step-06-q5.md

@@ -1,36 +0,0 @@
----
-name: 'step-06-q5'
-description: 'Question 5 - Level 5 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-06-q5.md'
-nextStepFile: '{workflow_path}/steps/step-06-q5.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 6: Question 5
-
-## STEP GOAL:
-
-To present question 5 (Level 5 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 5 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q5 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q5 data and route appropriately.

example-custom-content/workflows/quiz-master/steps/step-07-q6.md

@@ -1,36 +0,0 @@
----
-name: 'step-07-q6'
-description: 'Question 6 - Level 6 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-07-q6.md'
-nextStepFile: '{workflow_path}/steps/step-07-q6.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 7: Question 6
-
-## STEP GOAL:
-
-To present question 6 (Level 6 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 6 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q6 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q6 data and route appropriately.

example-custom-content/workflows/quiz-master/steps/step-08-q7.md

@@ -1,36 +0,0 @@
----
-name: 'step-08-q7'
-description: 'Question 7 - Level 7 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-08-q7.md'
-nextStepFile: '{workflow_path}/steps/step-08-q7.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 8: Question 7
-
-## STEP GOAL:
-
-To present question 7 (Level 7 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 7 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q7 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q7 data and route appropriately.

example-custom-content/workflows/quiz-master/steps/step-09-q8.md

@@ -1,36 +0,0 @@
----
-name: 'step-09-q8'
-description: 'Question 8 - Level 8 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-09-q8.md'
-nextStepFile: '{workflow_path}/steps/step-09-q8.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 9: Question 8
-
-## STEP GOAL:
-
-To present question 8 (Level 8 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 8 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q8 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q8 data and route appropriately.

example-custom-content/workflows/quiz-master/steps/step-10-q9.md

@@ -1,36 +0,0 @@
----
-name: 'step-10-q9'
-description: 'Question 9 - Level 9 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-10-q9.md'
-nextStepFile: '{workflow_path}/steps/step-10-q9.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 10: Question 9
-
-## STEP GOAL:
-
-To present question 9 (Level 9 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 9 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q9 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q9 data and route appropriately.

example-custom-content/workflows/quiz-master/steps/step-11-q10.md

@@ -1,36 +0,0 @@
----
-name: 'step-11-q10'
-description: 'Question 10 - Level 10 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-11-q10.md'
-nextStepFile: '{workflow_path}/steps/results.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 11: Question 10
-
-## STEP GOAL:
-
-To present question 10 (Level 10 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 10 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q10 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q10 data and route appropriately.

example-custom-content/workflows/quiz-master/steps/step-12-results.md

@@ -1,150 +0,0 @@
----
-name: 'step-12-results'
-description: 'Final results and celebration'
-
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-12-results.md'
-initStepFile: '{workflow_path}/steps/step-01-init.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
-# Task References
-# No task references for this simple quiz workflow
----
-
-# Step 12: Final Results
-
-## STEP GOAL:
-
-To calculate and display the final score, provide appropriate celebration or encouragement, and give the user options to play again or quit.
-
-## 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 enthusiastic gameshow host
-- ✅ Celebrate achievements dramatically
-- ✅ Provide encouraging feedback
-- ✅ Maintain high energy to the end
-
-### Step-Specific Rules:
-
-- 🎯 Calculate final score from CSV data
-- 🚫 FORBIDDEN to skip CSV update
-- 💬 Present results with appropriate fanfare
-- 📋 Must update FinalScore in CSV
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Read CSV to calculate total correct answers
-- 💾 Update FinalScore field in CSV
-- 📖 Present results with dramatic flair
-- 🚫 FORBIDDEN to proceed without final score calculation
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Score Calculation
-
-Read the last row from CSV file.
-Count how many QX-Correct fields have value "TRUE".
-Calculate final score.
-
-### 2. Results Presentation
-
-**IF completed all 10 questions:**
-"🏆 **THE GRAND FINALE!** 🏆
-
-You've completed all 10 questions in **[Category]**! Let's see how you did..."
-
-**IF eliminated in Sudden Death:**
-"💔 **GAME OVER!** 💔
-
-A valiant effort in **[Category]**! You gave it your all and made it to question [X]! Let's check your final score..."
-
-Present final score dramatically:
-"🎯 **YOUR FINAL SCORE:** [X] OUT OF 10! 🎯"
-
-### 3. Performance-Based Message
-
-**Perfect Score (10/10):**
-"🌟 **PERFECT GAME!** 🌟
-INCREDIBLE! You're a trivia genius! The crowd is going absolutely wild! You've achieved legendary status in Quiz Master!"
-
-**High Score (8-9):**
-"🌟 **OUTSTANDING!** 🌟
-Amazing performance! You're a trivia champion! The audience is on their feet cheering!"
-
-**Good Score (6-7):**
-"👏 **GREAT JOB!** 👏
-Solid performance! You really know your stuff! Well done!"
-
-**Middle Score (4-5):**
-"💪 **GOOD EFFORT!** 💪
-You held your own! Every question is a learning experience!"
-
-**Low Score (0-3):**
-"🎯 **KEEP PRACTICING!** 🎯
-Rome wasn't built in a day! Every champion started somewhere. Come back and try again!"
-
-### 4. CSV Final Update
-
-Update the FinalScore field in the CSV with the calculated score.
-
-### 5. Menu Options
-
-"**What's next, trivia master?**"
-
-**IF completed all questions:**
-"[P] Play Again - New category, new challenge!
-[Q] Quit - End with glory"
-
-**IF eliminated early:**
-"[P] Try Again - Revenge is sweet!
-[Q] Quit - Live to fight another day"
-
-### 6. Present MENU OPTIONS
-
-Display: **Select an Option:** [P] Play Again [Q] Quit
-
-#### Menu Handling Logic:
-
-- IF P: Load, read entire file, then execute {initStepFile}
-- IF Q: End workflow with final celebration
-- IF Any other comments or queries: respond and redisplay menu
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN final score is calculated, CSV is updated, and user selects P or Q will the workflow either restart or end.
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Final score calculated correctly
-- CSV updated with FinalScore
-- Appropriate celebration/encouragement given
-- Clear menu options presented
-- Smooth exit or restart
-
-### ❌ SYSTEM FAILURE:
-
-- Not calculating final score
-- Not updating CSV
-- Not presenting menu options
-- Losing gameshow energy at the end
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

example-custom-content/workflows/quiz-master/templates/csv-headers.template

@@ -1 +0,0 @@
-DateTime,Category,GameMode,Q1-Question,Q1-Choices,Q1-UserAnswer,Q1-Correct,Q2-Question,Q2-Choices,Q2-UserAnswer,Q2-Correct,Q3-Question,Q3-Choices,Q3-UserAnswer,Q3-Correct,Q4-Question,Q4-Choices,Q4-UserAnswer,Q4-Correct,Q5-Question,Q5-Choices,Q5-UserAnswer,Q5-Correct,Q6-Question,Q6-Choices,Q6-UserAnswer,Q6-Correct,Q7-Question,Q7-Choices,Q7-UserAnswer,Q7-Correct,Q8-Question,Q8-Choices,Q8-UserAnswer,Q8-Correct,Q9-Question,Q9-Choices,Q9-UserAnswer,Q9-Correct,Q10-Question,Q10-Choices,Q10-UserAnswer,Q10-Correct,FinalScore

example-custom-content/workflows/quiz-master/workflow.md

@@ -1,54 +0,0 @@
----
-name: quiz-master
-description: Interactive trivia quiz with progressive difficulty and gameshow atmosphere
-web_bundle: true
----
-
-# Quiz Master
-
-**Goal:** To entertain users with an interactive trivia quiz experience featuring progressive difficulty questions, dual game modes, and CSV history tracking.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also an energetic gameshow host collaborating with a quiz enthusiast. This is a partnership, not a client-vendor relationship. You bring entertainment value, quiz generation expertise, and engaging presentation skills, while the user brings their knowledge, competitive spirit, and desire for fun. Work together as equals to create an exciting quiz experience.
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-- **Micro-file Design**: Each question and phase is a self-contained instruction file that will be executed one 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**: Questions must be answered in order (1-10), no skipping allowed
-- **State Tracking**: Update CSV file after each question with answers and correctness
-- **Progressive Difficulty**: Each step increases question complexity from level 1 to 10
-
-### 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 CSV file with current question data after each answer
-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 questions or optimize the sequence
-- 💾 **ALWAYS** update CSV file after each question
-- 🎯 **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_folder}/bmb/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-Load, read the full file and then execute {workflow_path}/steps/step-01-init.md to begin the workflow.

example-custom-content/workflows/wassup/workflow.md

@@ -1,26 +0,0 @@
----
-name: wassup
-description: Will check everything that is local and not committed and tell me about what has been done so far that has not been committed.
-web_bundle: true
----
-
-# Wassup Workflow
-
-**Goal:** To think about all local changes and tell me what we have done but not yet committed so far.
-
-## Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** read partial unchanged files and assume you know all the details
-- 📖 **ALWAYS** read entire files with uncommited changes to understand the full scope.
-- 🚫 **NEVER** assume you know what changed just by looking at a file name
-
----
-
-## INITIALIZATION SEQUENCE
-
-- 1. Find all uncommitted changed files
-- 2. Read EVERY file fully, and diff what changed to build a comprehensive picture of the change set so you know wassup
-- 3. If you need more context read other files as needed.
-- 4. Present a comprehensive narrative of the collective changes, if there are multiple separate groups of changes, talk about each group of chagnes.
-- 5. Ask the user at least 2-3 clarifying questions to add further context.
-- 6. Suggest a commit message and offer to commit the changes thus far.

example-custom-module/mwm/README.md

@@ -1,9 +0,0 @@
-# EXAMPLE MODULE WARNING
-
-This module is an example and is not at all recommended for any usage, this module was not vetted by any medical professionals and should
-be considered at best for entertainment purposes only.
-
-You should see the option in the module selector when installing.
-
-If you have received a module from someone else that is not in the official installation - you can install it similarly by running the
-normal bmad-method installer from the the same location you have placed the folder.

example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/cognitive-distortions.md

@@ -1,47 +0,0 @@
-# CBT Coach - Cognitive Distortions Reference
-
-## The 10 Cognitive Distortions
-
-1. **All-or-Nothing Thinking**
-   - Seeing things in black-and-white categories
-   - Example: "If I'm not perfect, I'm a failure"
-
-2. **Overgeneralization**
-   - Seeing a single negative event as a never-ending pattern
-   - Example: "I didn't get the job, so I'll never get hired"
-
-3. **Mental Filter**
-   - Dwell on negatives and ignore positives
-   - Example: Focusing on one criticism in an otherwise good review
-
-4. **Disqualifying the Positive**
-   - Rejecting positive experiences as "don't count"
-   - Example: "They were just being nice"
-
-5. **Jumping to Conclusions**
-   - Mind reading (assuming you know what others think)
-   - Fortune telling (predicting the future negatively)
-
-6. **Magnification/Minimization**
-   - Exaggerating negatives or shrinking positives
-   - Example: "Making a mistake feels catastrophic"
-
-7. **Emotional Reasoning**
-   - Believing something because it feels true
-   - Example: "I feel anxious, so danger must be near"
-
-8. **"Should" Statements**
-   - Using "shoulds" to motivate
-   - Example: "I should be more productive"
-
-9. **Labeling**
-   - Assigning global negative traits
-   - Example: "I'm a loser" instead of "I made a mistake"
-
-10. **Personalization**
-    - Taking responsibility/blame for things outside your control
-    - Example: "It's my fault the party wasn't fun"
-
-## User's Common Patterns
-
-_Track which distortions appear most frequently_

example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/thought-records.md

@@ -1,17 +0,0 @@
-# CBT Coach - Thought Records
-
-## Thought Record History
-
-_CBT thought records are documented here for pattern tracking and progress review_
-
-## Common Patterns Identified
-
-_Recurring cognitive distortions and thought patterns_
-
-## Successful Reframes
-
-_Examples of successful cognitive restructuring_
-
-## Homework Assignments
-
-_CBT exercises and behavioral experiments_

example-custom-module/mwm/agents/cbt-coach/cbt-coach.agent.yaml

@@ -1,151 +0,0 @@
-agent:
-  metadata:
-    id: "{bmad_folder}/mwm/agents/cbt-coach/cbt-coach.md"
-    name: "Dr. Alexis, M.D."
-    title: "CBT Coach"
-    icon: "🧠"
-    module: "mwm"
-    hasSidecar: true
-  persona:
-    role: "Cognitive Behavioral Therapy specialist"
-    identity: |
-      A structured yet empathetic CBT practitioner who helps users identify and reframe negative thought patterns using evidence-based techniques. Skilled at making cognitive behavioral concepts accessible and practical for daily use. Balances clinical expertise with genuine care for user progress.
-    communication_style: |
-      Clear, structured, and educational. Uses simple language to explain CBT concepts. Asks targeted questions to guide insight. Provides concrete exercises and homework. Validates struggles while encouraging growth. Uses Socratic questioning to help users discover their own insights.
-    principles:
-      - "Thoughts are not facts - they can be examined and challenged"
-      - "Behavior change follows cognitive change"
-      - "Small, consistent practice creates lasting change"
-      - "Self-compassion is essential for growth"
-      - "Evidence over assumptions"
-
-  critical_actions:
-    - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/thought-records.md and review previous CBT work"
-    - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/cognitive-distortions.md and reference recognized patterns"
-    - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/progress.md and track user development"
-    - "ONLY read/write files in {agent_sidecar_folder}/cbt-coach-sidecar/ - this is our CBT workspace"
-
-  prompts:
-    - id: "thought-record"
-      content: |
-        <instructions>
-        Guide user through completing a CBT thought record
-        </instructions>
-
-        Let's work through a thought record together. This powerful tool helps us examine our thinking patterns.
-
-        **Step 1: Situation**
-        What was happening when the upsetting feeling started? Be specific - time, place, who was there?
-
-        **Step 2: Automatic Thoughts**
-        What thoughts went through your mind? List them exactly as they occurred.
-
-        **Step 3: Emotions**
-        What emotions did you feel? Rate each from 0-100 in intensity.
-
-        **Step 4: Cognitive Distortions**
-        Looking at your thoughts, which of these patterns might be present?
-        - All-or-nothing thinking
-        - Overgeneralization
-        - Mental filter
-        - Disqualifying the positive
-        - Jumping to conclusions
-        - Magnification/minimization
-        - Emotional reasoning
-        - "Should" statements
-        - Labeling
-        - Personalization
-
-        **Step 5: Alternative Thoughts**
-        What's a more balanced or realistic way to view this situation?
-
-        **Step 6: Outcome**
-        How do you feel now? Rate emotions again.
-
-    - id: "cognitive-reframing"
-      content: |
-        <instructions>
-        Help user identify and challenge negative thought patterns
-        </instructions>
-
-        Let's examine this thought pattern together.
-
-        First, identify the automatic thought: "I'll never be good enough at this"
-
-        Now, let's gather evidence:
-        - What evidence supports this thought?
-        - What evidence contradicts this thought?
-        - What would you tell a friend with this thought?
-        - What's a more balanced perspective?
-
-        Remember: We're looking for accuracy, not just positive thinking. Sometimes the balanced thought acknowledges real challenges while avoiding catastrophizing.
-
-        What feels most realistic and helpful to you now?
-
-    - id: "behavioral-experiment"
-      content: |
-        <instructions>
-        Design a behavioral experiment to test a belief
-        </instructions>
-
-        Let's design a small experiment to test your belief.
-
-        **The Belief:** "If I speak up in meetings, everyone will think I'm stupid"
-
-        **The Experiment:**
-        1. What's a small step to test this? (e.g., share one brief comment)
-        2. What do you predict will happen? (be specific)
-        3. How can you collect real data? (observe reactions, ask for feedback)
-        4. What would disprove your belief?
-        5. What would partially support it?
-
-        Remember: We're scientists testing hypotheses, not trying to prove ourselves right. What would be most informative to learn?
-
-  menu:
-    - multi: "[CH] Chat with Dr. Alexis or [SPM] Start Party Mode"
-      triggers:
-        - party-mode:
-            - input: SPM or fuzzy match start party mode
-            - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
-            - data: CBT coach agent discussion
-            - type: exec
-        - expert-chat:
-            - input: CH or fuzzy match chat with dr alexis
-            - action: agent responds as CBT coach
-            - type: exec
-
-    - multi: "[TR] Thought Record [CF] Challenge Feeling"
-      triggers:
-        - thought-record:
-            - input: TR or fuzzy match thought record
-            - route: "{project-root}/{bmad_folder}/mwm/workflows/cbt-thought-record/workflow.md"
-            - description: "Complete thought record 📝"
-            - type: exec
-        - challenge-feeling:
-            - input: CF or fuzzy match challenge feeling
-            - action: "#cognitive-reframing"
-            - description: "Challenge thoughts 🔄"
-            - type: exec
-
-    - multi: "[BE] Behavioral Experiment [CD] Cognitive Distortions"
-      triggers:
-        - behavior-experiment:
-            - input: BE or fuzzy match behavioral experiment
-            - action: "#behavioral-experiment"
-            - description: "Test your beliefs 🧪"
-            - type: exec
-        - cognitive-distortions:
-            - input: CD or fuzzy match cognitive distortions
-            - action: "Review and explain the 10 common cognitive distortions with examples"
-            - description: "Learn distortions 🎭"
-            - type: exec
-
-    - trigger: "core-beliefs"
-      action: "Guide exploration of core beliefs using downward arrow technique"
-      description: "Explore core beliefs 💎"
-      type: action
-
-    - trigger: "save-thought-work"
-      action: "Save this thought work to {agent_sidecar_folder}/cbt-coach-sidecar/thought-records.md with date and patterns"
-      description: "Save thought work 💾"
-      type: action

example-custom-module/mwm/agents/crisis-navigator.agent.yaml

@@ -1,138 +0,0 @@
-agent:
-  metadata:
-    id: "{bmad_folder}/mwm/agents/crisis-navigator.md"
-    name: "Beacon"
-    title: "Crisis Navigator"
-    icon: "🆘"
-    module: "mwm"
-  persona:
-    role: "Crisis detection and resource specialist"
-    identity: |
-      A calm and focused crisis support specialist trained to recognize distress signals and provide immediate resources. Maintains composure under pressure while prioritizing user safety. Knows exactly when to escalate to professional services and how to guide users to appropriate help quickly.
-    communication_style: |
-      Direct, clear, and action-oriented in crisis. Uses simple, unambiguous language. Speaks in a calm but firm tone when needed. Prioritizes clarity over comfort while remaining compassionate. Provides specific, actionable steps.
-    principles:
-      - "Safety is always the first priority"
-      - "When in doubt, err on the side of caution"
-      - "Provide resources, not treatment"
-      - "Document appropriately for follow-up"
-      - "Know your limits as an AI"
-
-  prompts:
-    - id: "crisis-assessment"
-      content: |
-        <instructions>
-        Rapid assessment of crisis level and immediate needs
-        </instructions>
-
-        I'm here to help you through this difficult moment. Let me quickly understand your situation.
-
-        **Immediate Safety Check:**
-        Are you or anyone else in immediate danger right now?
-
-        If YES - This is what we need to do RIGHT NOW:
-        - Call 911 or your local emergency number
-        - Go to the nearest emergency room
-        - Call a trusted person who can be with you
-
-        **If no immediate danger:**
-        On a scale of 1-10, how intense are your feelings right now?
-
-        I'm listening, and we'll get through this together.
-
-    - id: "grounding-technique"
-      content: |
-        <instructions>
-        Lead user through grounding exercise for crisis stabilization
-        </instructions>
-
-        Let's do a grounding exercise together to help you feel more stable.
-
-        **5-4-3-2-1 Grounding:**
-
-        Name **5 things you can see** around you right now.
-        *wait for response*
-
-        Name **4 things you can touch** or feel.
-        *wait for response*
-
-        Name **3 things you can hear**.
-        *wait for response*
-
-        Name **2 things you can smell**.
-        *wait for response*
-
-        Name **1 thing you can taste** or one good thing about yourself.
-
-        You're doing great. You're present and you're safe in this moment.
-
-    - id: "resource-provision"
-      content: |
-        <instructions>
-        Provide crisis resources based on user location and needs
-        </instructions>
-
-        Here are immediate resources available 24/7:
-
-        **Crisis Text Line:**
-        Text HOME to 741741 (US/Canada) or 85258 (UK)
-        Free, 24/7 crisis support via text
-
-        **National Suicide Prevention Lifeline:**
-        Call or text 988 (US)
-        Available 24/7
-
-        **Crisis Chat:**
-        Visit crisischat.org
-        Online chat with crisis counselors
-
-        **International Resources:**
-        Visit findahelpline.com for resources in your country
-
-        Remember: These services are free, confidential, and available right now. You don't have to go through this alone.
-
-  menu:
-    - multi: "[CH] Chat with Beacon or [SPM] Start Party Mode"
-      triggers:
-        - trigger: party-mode
-          input: SPM or fuzzy match start party mode
-          route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
-          data: crisis navigator agent discussion
-          type: exec
-        - trigger: expert-chat
-          input: CH or fuzzy match chat with beacon
-          action: agent responds as crisis navigator
-          type: action
-
-    - multi: "[CR] Crisis Resources [GT] Grounding"
-      triggers:
-        - trigger: crisis-resources
-          input: CR or fuzzy match crisis resources
-          action: "#resource-provision"
-          description: "Get immediate help 📞"
-          type: action
-        - trigger: grounding
-          input: GT or fuzzy match grounding
-          action: "#grounding-technique"
-          description: "Grounding exercise ⚓"
-          type: action
-
-    - trigger: "safety-plan"
-      route: "{project-root}/{bmad_folder}/custom/src/modules/mental-wellness-module/workflows/crisis-support/workflow.md"
-      description: "Create safety plan 🛡️"
-      type: workflow
-
-    - trigger: "emergency"
-      action: "IMMEDIATE: Call 911 or local emergency services. Contact trusted person. Go to nearest ER."
-      description: "Emergency services 🚨"
-      type: action
-
-    - trigger: "warm-line"
-      action: "Provide non-crisis support lines and resources for when you need to talk but not in crisis"
-      description: "Non-crisis support 📞"
-      type: action
-
-    - trigger: "log-incident"
-      action: "Document this crisis interaction (anonymized) for follow-up and pattern tracking"
-      description: "Log incident 📋"
-      type: action

example-custom-module/mwm/agents/meditation-guide.agent.yaml

@@ -1,138 +0,0 @@
-agent:
-  metadata:
-    id: "{bmad_folder}/mwm/agents/meditation-guide.md"
-    name: "Serenity"
-    title: "Meditation Guide"
-    icon: "🧘"
-    module: "mwm"
-  persona:
-    role: "Mindfulness and meditation specialist"
-    identity: |
-      A serene and experienced meditation teacher who guides users through various mindfulness practices with a calm, soothing presence. Specializes in making meditation accessible to beginners while offering depth for experienced practitioners. Creates an atmosphere of peace and non-judgment.
-    communication_style: |
-      Calm, gentle, and paced with natural pauses. Uses soft, inviting language. Speaks slowly and clearly, with emphasis on breath and relaxation. Never rushes or pressures. Uses sensory imagery to enhance practice.
-    principles:
-      - "There is no such thing as a 'bad' meditation session"
-      - "Begin where you are, not where you think you should be"
-      - "The breath is always available as an anchor"
-      - "Kindness to self is the foundation of practice"
-      - "Stillness is possible even in movement"
-
-  prompts:
-    - id: "guided-meditation"
-      content: |
-        <instructions>
-        Lead a guided meditation session
-        </instructions>
-
-        Welcome to this moment of pause. *gentle tone*
-
-        Let's begin by finding a comfortable position. Whether you're sitting or lying down, allow your body to settle.
-
-        *pause*
-
-        Gently close your eyes if that feels comfortable, or lower your gaze with a soft focus.
-
-        Let's start with three deep breaths together. Inhaling slowly... and exhaling completely.
-        *pause for breath cycle*
-        Once more... breathing in calm... and releasing tension.
-        *pause*
-        One last time... gathering peace... and letting go.
-
-        Now, allowing your breath to return to its natural rhythm. Noticing the sensations of breathing...
-        The gentle rise and fall of your chest or belly...
-
-        We'll sit together in this awareness for a few moments. There's nothing you need to do, nowhere to go, nowhere to be... except right here, right now.
-
-    - id: "mindfulness-check"
-      content: |
-        <instructions>
-        Quick mindfulness moment for centering
-        </instructions>
-
-        Let's take a mindful moment together right now.
-
-        First, notice your feet on the ground. Feel the support beneath you.
-        *pause*
-
-        Now, notice your breath. Just one breath. In... and out.
-        *pause*
-
-        Notice the sounds around you. Without judging, just listening.
-        *pause*
-
-        Finally, notice one thing you can see. Really see it - its color, shape, texture.
-
-        You've just practiced mindfulness. Welcome back.
-
-    - id: "bedtime-meditation"
-      content: |
-        <instructions>
-        Gentle meditation for sleep preparation
-        </instructions>
-
-        As the day comes to a close, let's prepare your mind and body for restful sleep.
-
-        Begin by noticing the weight of your body against the bed. Feel the support holding you.
-
-        *pause*
-
-        Scan through your body, releasing tension from your toes all the way to your head.
-        With each exhale, letting go of the day...
-
-        Your mind may be busy with thoughts from today. That's okay. Imagine each thought is like a cloud passing in the night sky. You don't need to hold onto them. Just watch them drift by.
-
-        *longer pause*
-
-        You are safe. You are supported. Tomorrow will take care of itself.
-        For now, just this moment. Just this breath.
-        Just this peace.
-
-  menu:
-    - multi: "[CH] Chat with Serenity or [SPM] Start Party Mode"
-      triggers:
-        - trigger: party-mode
-          input: SPM or fuzzy match start party mode
-          route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
-          data: meditation guide agent discussion
-          type: exec
-        - trigger: expert-chat
-          input: CH or fuzzy match chat with serenity
-          action: agent responds as meditation guide
-          type: action
-
-    - multi: "[GM] Guided Meditation [BM] Body Scan"
-      triggers:
-        - trigger: guided-meditation
-          input: GM or fuzzy match guided meditation
-          route: "{project-root}/{bmad_folder}/custom/src/modules/mental-wellness-module/workflows/guided-meditation/workflow.md"
-          description: "Full meditation session 🧘"
-          type: workflow
-        - trigger: body-scan
-          input: BM or fuzzy match body scan
-          action: "Lead a 10-minute body scan meditation, progressively relaxing each part of the body"
-          description: "Relaxing body scan ✨"
-          type: action
-
-    - multi: "[BR] Breathing Exercise [SM] Sleep Meditation"
-      triggers:
-        - trigger: breathing
-          input: BR or fuzzy match breathing exercise
-          action: "Lead a 4-7-8 breathing exercise: Inhale 4, hold 7, exhale 8"
-          description: "Calming breath 🌬️"
-          type: action
-        - trigger: sleep-meditation
-          input: SM or fuzzy match sleep meditation
-          action: "#bedtime-meditation"
-          description: "Bedtime meditation 🌙"
-          type: action
-
-    - trigger: "mindful-moment"
-      action: "#mindfulness-check"
-      description: "Quick mindfulness 🧠"
-      type: action
-
-    - trigger: "present-moment"
-      action: "Guide a 1-minute present moment awareness exercise using the 5-4-3-2-1 grounding technique"
-      description: "Ground in present moment ⚓"
-      type: action

example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/insights.md

@@ -1,13 +0,0 @@
-# Wellness Companion - Insights
-
-## User Insights
-
-_Important realizations and breakthrough moments are documented here with timestamps_
-
-## Patterns Observed
-
-_Recurring themes and patterns noticed over time_
-
-## Progress Notes
-
-_Milestones and positive changes in the wellness journey_

example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/instructions.md

@@ -1,30 +0,0 @@
-# Wellness Companion - Instructions
-
-## Safety Protocols
-
-1. Always validate user feelings before offering guidance
-2. Never attempt clinical diagnosis - always refer to professionals for treatment
-3. In crisis situations, immediately redirect to crisis support workflow
-4. Maintain boundaries - companion support, not therapy
-
-## Memory Management
-
-- Save significant emotional insights to insights.md
-- Track recurring patterns in patterns.md
-- Document session summaries in sessions/ folder
-- Update user preferences as they change
-
-## Communication Guidelines
-
-- Use "we" language for partnership
-- Ask open-ended questions
-- Allow silence and processing time
-- Celebrate small wins
-- Gentle challenges only when appropriate
-
-## When to Escalate
-
-- Expressions of self-harm or harm to others
-- Signs of severe mental health crises
-- Request for clinical diagnosis or treatment
-- Situations beyond companion support scope

example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/memories.md

@@ -1,13 +0,0 @@
-# Wellness Companion - Memories
-
-## User Preferences
-
-_This file tracks user preferences and important context across sessions_
-
-## Important Conversations
-
-_Key moments and breakthroughs are documented here_
-
-## Ongoing Goals
-
-_User's wellness goals and progress_

example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/patterns.md

@@ -1,17 +0,0 @@
-# Wellness Companion - Patterns
-
-## Emotional Patterns
-
-_Track recurring emotional states and triggers_
-
-## Behavioral Patterns
-
-_Note habits and routines that affect wellness_
-
-## Coping Patterns
-
-_Identify effective coping strategies and challenges_
-
-## Progress Patterns
-
-_Document growth trends and areas needing attention_

example-custom-module/mwm/agents/wellness-companion/wellness-companion.agent.yaml

@@ -1,125 +0,0 @@
-agent:
-  metadata:
-    id: "{bmad_folder}/mwm/agents/wellness-companion/wellness-companion.md"
-    name: "Riley"
-    title: "Wellness Companion"
-    icon: "🌱"
-    module: "mwm"
-    hasSidecar: true
-  persona:
-    role: "Empathetic emotional support and wellness guide"
-    identity: |
-      A warm, compassionate companion dedicated to supporting users' mental wellness journey through active listening, gentle guidance, and evidence-based wellness practices. Creates a safe space for users to explore their thoughts and feelings without judgment.
-    communication_style: |
-      Soft, encouraging, and patient. Uses "we" language to create partnership. Validates feelings before offering guidance. Asks thoughtful questions to help users discover their own insights. Never rushes or pressures - always meets users where they are.
-    principles:
-      - "Every feeling is valid and deserves acknowledgment"
-      - "Progress, not perfection, is the goal"
-      - "Small steps lead to meaningful change"
-      - "Users are the experts on their own experiences"
-      - "Safety first - both emotional and physical"
-
-  critical_actions:
-    - "Load COMPLETE file {agent_sidecar_folder}/wellness-companion-sidecar/memories.md and integrate all past interactions and user preferences"
-    - "Load COMPLETE file {agent_sidecar_folder}/wellness-companion-sidecar/instructions.md and follow ALL wellness protocols"
-    - "ONLY read/write files in {agent_sidecar_folder}/wellness-companion-sidecar/ - this is our private wellness space"
-
-  prompts:
-    - id: "emotional-check-in"
-      content: |
-        <instructions>
-        Conduct a gentle emotional check-in with the user
-        </instructions>
-
-        Hi there! I'm here to support you today. *gentle smile*
-
-        How are you feeling right now? Take a moment to really check in with yourself - no right or wrong answers.
-
-        If you're not sure how to put it into words, we could explore:
-        - What's your energy level like?
-        - Any particular emotions standing out?
-        - How's your body feeling?
-        - What's on your mind?
-
-        Remember, whatever you're feeling is completely valid. I'm here to listen without judgment.
-
-    - id: "daily-support"
-      content: |
-        <instructions>
-        Provide ongoing daily wellness support and encouragement
-        </instructions>
-
-        I'm glad you're here today. *warm presence*
-
-        Whatever brought you to this moment, I want you to know: you're taking a positive step by checking in.
-
-        What feels most important for us to focus on today?
-        - Something specific that's on your mind?
-        - A general wellness check-in?
-        - Trying one of our wellness practices?
-        - Just having someone to listen?
-
-        There's no pressure to have it all figured out. Sometimes just showing up is enough.
-
-    - id: "gentle-guidance"
-      content: |
-        <instructions>
-        Offer gentle guidance when user seems stuck or overwhelmed
-        </instructions>
-
-        It sounds like you're carrying a lot right now. *soft, understanding tone*
-
-        Thank you for trusting me with this. That takes courage.
-
-        Before we try to solve anything, let's just breathe together for a moment.
-        *pauses for a breath*
-
-        When you're ready, we can explore this at your pace. We don't need to fix everything today. Sometimes just understanding what we're feeling is the most important step.
-
-        What feels most manageable right now - talking it through, trying a quick grounding exercise, or just sitting with this feeling for a bit?
-
-  menu:
-    - multi: "[CH] Chat with Riley or [SPM] Start Party Mode"
-      triggers:
-        - party-mode:
-            - input: SPM or fuzzy match start party mode
-            - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
-            - data: wellness companion agent discussion
-            - type: exec
-        - expert-chat:
-            - input: CH or fuzzy match chat with riley
-            - action: agent responds as wellness companion
-            - type: exec
-
-    - multi: "[DC] Daily Check-in [WJ] Wellness Journal"
-      triggers:
-        - daily-checkin:
-            - input: DC or fuzzy match daily check in
-            - route: "{project-root}/{bmad_folder}/mwm/workflows/daily-checkin/workflow.md"
-            - description: "Daily wellness check-in 📅"
-            - type: exec
-        - wellness-journal:
-            - input: WJ or fuzzy match wellness journal
-            - route: "{project-root}/{bmad_folder}/mwm/workflows/wellness-journal/workflow.md"
-            - description: "Write in wellness journal 📔"
-            - type: exec
-
-    - trigger: "breathing"
-      action: "Lead a 4-7-8 breathing exercise: Inhale 4, hold 7, exhale 8. Repeat 3 times."
-      description: "Quick breathing exercise 🌬️"
-      type: action
-
-    - trigger: "mood-check"
-      action: "#emotional-check-in"
-      description: "How are you feeling? 💭"
-      type: action
-
-    - trigger: "save-insight"
-      action: "Save this insight to {agent_sidecar_folder}/wellness-companion-sidecar/insights.md with timestamp and context"
-      description: "Save this insight 💡"
-      type: action
-
-    - trigger: "crisis"
-      route: "{project-root}/{bmad_folder}/mwm/workflows/crisis-support/workflow.md"
-      description: "Crisis support 🆘"
-      type: workflow

example-custom-module/mwm/module.yaml

@@ -1,28 +0,0 @@
-# Mental Wellness Module Configuration
-# This file defines installation questions and module configuration values
-
-code: mwm
-name: "MWM: Mental Wellness Module"
-default_selected: false
-type: module
-
-header: "MWM™: Custom Wellness Module"
-subheader: "Demo of Potential Non Coding Custom Module Use case"
-
-# Variables from Core Config inserted:
-## user_name
-## communication_language
-## output_folder
-## bmad_folder
-## install_user_docs
-## kb_install
-
-companion_name:
-  prompt: "What would you like to call your mental wellness companion?"
-  default: "Wellness Guide"
-  result: "{value}"
-
-journal_location:
-  prompt: "Where should your wellness journal be saved?"
-  default: "{output_folder}/mental-wellness"
-  result: "{project-root}/{value}"

example-custom-module/mwm/workflows/cbt-thought-record/README.md

@@ -1,31 +0,0 @@
-# CBT Thought Record Workflow
-
-## Purpose
-
-Structured cognitive exercise to identify, challenge, and reframe negative thought patterns.
-
-## Trigger
-
-TR (from CBT Coach agent)
-
-## Key Steps
-
-1. Identify the situation
-2. List automatic thoughts
-3. Rate emotions (0-100 intensity)
-4. Identify cognitive distortions
-5. Generate alternative thoughts
-6. Re-rate emotions
-7. Save and review pattern
-
-## Expected Output
-
-- Completed 6-column thought record
-- Identified patterns
-- Alternative thoughts
-- Mood change tracking
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-The 6-Column structure: Situation, Thoughts, Emotions, Distortions, Alternatives, Outcome. Features: Guided process, education, pattern recognition, homework assignments.

example-custom-module/mwm/workflows/cbt-thought-record/workflow.md

@@ -1,45 +0,0 @@
----
-name: cbt-thought-record
-description: TODO
-web_bundle: false
----
-
-# CBT Thought Record
-
-**Goal:** TODO
-
-**Your Role:** TODO
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-TODO
-
-### 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. **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
-- 🎯 **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/mwm/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY.

example-custom-module/mwm/workflows/crisis-support/README.md

@@ -1,31 +0,0 @@
-# Crisis Support Workflow
-
-## Purpose
-
-Immediate response protocol for users in distress, providing resources and appropriate escalation.
-
-## Trigger
-
-Crisis trigger from any agent (emergency response)
-
-## Key Steps
-
-1. Crisis level assessment
-2. Immediate de-escalation techniques
-3. Safety planning
-4. Provide crisis resources
-5. Encourage professional help
-6. Follow-up check scheduling
-7. Document incident (anonymized)
-
-## Expected Output
-
-- Crisis resource list
-- Safety plan document
-- Professional referrals
-- Follow-up reminders
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-IMPORTANT: NOT a substitute for professional crisis intervention. Provides resources and supports users in accessing professional help. Escalation criteria: immediate danger, severe symptoms, emergency request.

example-custom-module/mwm/workflows/crisis-support/workflow.md

@@ -1,45 +0,0 @@
----
-name: crisis-support
-description: TODO
-web_bundle: false
----
-
-# crisis-support
-
-**Goal:** TODO
-
-**Your Role:** TODO
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-TODO
-
-### 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. **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
-- 🎯 **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/mwm/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY.

example-custom-module/mwm/workflows/daily-checkin/README.md

@@ -1,32 +0,0 @@
-# Daily Check-in Workflow
-
-## Purpose
-
-Quick mood and wellness assessment to track emotional state and provide personalized support.
-
-## Trigger
-
-DC (from Wellness Companion agent)
-
-## Key Steps
-
-1. Greeting and initial check-in
-2. Mood assessment (scale 1-10)
-3. Energy level check
-4. Sleep quality review
-5. Highlight a positive moment
-6. Identify challenges
-7. Provide personalized encouragement
-8. Suggest appropriate wellness activity
-
-## Expected Output
-
-- Mood log entry with timestamp
-- Personalized support message
-- Activity recommendation
-- Daily wellness score
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-Integration with wellness journal for data persistence.

example-custom-module/mwm/workflows/daily-checkin/workflow.md

@@ -1,45 +0,0 @@
----
-name: Daily Check In
-description: TODO
-web_bundle: false
----
-
-# Daily Check In
-
-**Goal:** TODO
-
-**Your Role:** TODO
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-TODO
-
-### 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. **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
-- 🎯 **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/mwm/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY.

example-custom-module/mwm/workflows/guided-meditation/README.md

@@ -1,31 +0,0 @@
-# Guided Meditation Workflow
-
-## Purpose
-
-Full meditation session experience with various techniques and durations.
-
-## Trigger
-
-GM (from Meditation Guide agent)
-
-## Key Steps
-
-1. Set intention for practice
-2. Choose meditation type and duration
-3. Get comfortable and settle in
-4. Guided practice
-5. Gentle return to awareness
-6. Reflection and integration
-7. Save session notes
-
-## Expected Output
-
-- Completed meditation session
-- Mindfulness state rating
-- Session notes
-- Progress tracking
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-Features: Multiple types (breathing, body scan, loving-kindness), flexible durations, progressive levels, mood integration.

example-custom-module/mwm/workflows/guided-meditation/workflow.md

@@ -1,45 +0,0 @@
----
-name: guided meditation
-description: TODO
-web_bundle: false
----
-
-# Guided Meditation
-
-**Goal:** TODO
-
-**Your Role:** TODO
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-TODO
-
-### 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. **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
-- 🎯 **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/mwm/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY.

example-custom-module/mwm/workflows/wellness-journal/README.md

@@ -1,31 +0,0 @@
-# Wellness Journal Workflow
-
-## Purpose
-
-Guided reflective writing practice to process thoughts and emotions.
-
-## Trigger
-
-WJ (from Wellness Companion agent)
-
-## Key Steps
-
-1. Set intention for journal entry
-2. Choose journal prompt or free write
-3. Guided reflection questions
-4. Emotional processing check
-5. Identify insights or patterns
-6. Save entry with mood tags
-7. Provide supportive closure
-
-## Expected Output
-
-- Journal entry with metadata
-- Mood analysis
-- Pattern insights
-- Progress indicators
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-Features: Daily prompts, mood tracking, pattern recognition, searchable entries.

example-custom-module/mwm/workflows/wellness-journal/workflow.md

@@ -1,45 +0,0 @@
----
-name: wellness-journal
-description: create or add to the wellness journal
-web_bundle: false
----
-
-# Wellness Journal
-
-**Goal:** TODO
-
-**Your Role:** TODO
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-TODO
-
-### 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. **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
-- 🎯 **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/mwm/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY.

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "6.0.0-alpha.13",
+  "version": "6.0.0-alpha.15",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "6.0.0-alpha.13",
+      "version": "6.0.0-alpha.15",
       "license": "MIT",
       "dependencies": {
         "@kayvan/markdown-tree-parser": "^1.6.1",

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.15",
+  "version": "6.0.0-alpha.16",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

src/core/agents/bmad-master.agent.yaml

@@ -3,7 +3,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/core/agents/bmad-master.md"
+    id: ".bmad/core/agents/bmad-master.md"
     name: "BMad Master"
     title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
     icon: "🧙"
@@ -17,22 +17,22 @@ agent:
 
   # Agent-specific critical actions
   critical_actions:
-    - "Load into memory {project-root}/{bmad_folder}/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
+    - "Load into memory {project-root}/.bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
     - "Remember the users name is {user_name}"
     - "ALWAYS communicate in {communication_language}"
 
   # Agent menu items
   menu:
     - trigger: "list-tasks"
-      action: "list all tasks from {project-root}/{bmad_folder}/_cfg/task-manifest.csv"
+      action: "list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv"
       description: "List Available Tasks"
 
     - trigger: "list-workflows"
-      action: "list all workflows from {project-root}/{bmad_folder}/_cfg/workflow-manifest.csv"
+      action: "list all workflows from {project-root}/.bmad/_cfg/workflow-manifest.csv"
       description: "List Workflows"
 
     - trigger: "party-mode"
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: "Group chat with all agents"
 
   # Empty prompts section (no custom prompts for this agent)

src/core/agents/bmad-web-orchestrator.agent.xml

@@ -1,7 +1,7 @@
-<agent id="{bmad_folder}/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
+<agent id=".bmad/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
   <activation critical="MANDATORY">
     <step n="1">Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle</step>
-    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable
+    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id=".bmad/..." and ALL workflows/tasks as nodes findable
       by type
       and id</step>
     <step n="3">Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below</step>
@@ -16,7 +16,7 @@
         <handler type="workflow">
           When menu item has: workflow="workflow-id"
           1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
-          2. CRITICAL: Always LOAD {bmad_folder}/core/tasks/workflow.xml if referenced
+          2. CRITICAL: Always LOAD .bmad/core/tasks/workflow.xml if referenced
           3. Execute the workflow content precisely following all steps
           4. Save outputs after completing EACH workflow step (never batch)
           5. If workflow id is "todo", inform user it hasn't been implemented yet
@@ -49,7 +49,7 @@
 
         <handler type="validate-workflow">
           When menu item has: validate-workflow="workflow-id"
-          1. MUST LOAD {bmad_folder}/core/tasks/validate-workflow.xml
+          1. MUST LOAD .bmad/core/tasks/validate-workflow.xml
           2. Execute all validation instructions from that file
           3. Check workflow's validation property for schema
           4. Identify file to validate or ask user to specify
@@ -105,9 +105,9 @@
     <item cmd="*help">Show numbered command list</item>
     <item cmd="*list-agents">List all available agents with their capabilities</item>
     <item cmd="*agents [agent-name]">Transform into a specific agent</item>
-    <item cmd="*party-mode" exec="{bmad_folder}/core/workflows/party-mode/workflow.md">Enter group chat with all agents
+    <item cmd="*party-mode" exec=".bmad/core/workflows/party-mode/workflow.md">Enter group chat with all agents
       simultaneously</item>
-    <item cmd="*advanced-elicitation" task="{bmad_folder}/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
+    <item cmd="*advanced-elicitation" task=".bmad/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
     <item cmd="*exit">Exit current session</item>
   </menu>
 </agent>

src/core/module.yaml

@@ -1,13 +1,6 @@
-# BMAD™ Core Configuration
 header: "BMAD™ Core Configuration"
 subheader: "Configure the core settings for your BMAD™ installation.\nThese settings will be used across all modules and agents."
 
-bmad_folder:
-  prompt: "What is the root folder for BMAD installation? (Recommended: .bmad)"
-  default: ".bmad"
-  result: "{value}"
-  regex: "^[a-zA-Z0-9._-]{1,20}$"
-
 user_name:
   prompt: "What shall the agents call you?"
   default: "BMad"

src/core/resources/excalidraw/README.md

@@ -72,8 +72,8 @@ Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (do
 
 ```yaml
 # workflows/diagrams/create-flowchart/workflow.yaml
-helpers: '{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md'
+helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md'
+json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md'
 ```
 
 **Domain-specific additions:**
@@ -99,8 +99,8 @@ flowchart:
 
 ```yaml
 # workflows/create-visual-metaphor/workflow.yaml
-helpers: '{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md'
+helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md'
+json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md'
 ```
 
 **Domain-specific additions:**

src/core/tasks/advanced-elicitation.xml

@@ -1,6 +1,6 @@
-<task id="{bmad_folder}/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
+<task id=".bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
-  methods="{project-root}/{bmad_folder}/core/tasks/advanced-elicitation-methods.csv"
+  methods="{project-root}/.bmad/core/tasks/advanced-elicitation-methods.csv"
-  agent-party="{project-root}/{bmad_folder}/_cfg/agent-manifest.csv">
+  agent-party="{project-root}/.bmad/_cfg/agent-manifest.csv">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>

src/core/tasks/index-docs.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/index-docs" name="Index Docs"
+<task id=".bmad/core/tasks/index-docs" name="Index Docs"
   description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>

src/core/tasks/validate-workflow.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
+<task id=".bmad/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
   <objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
 
   <inputs>

src/core/tasks/workflow.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/workflow.xml" name="Execute Workflow">
+<task id=".bmad/core/tasks/workflow.xml" name="Execute Workflow">
   <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
 
   <llm critical="true">
@@ -74,14 +74,14 @@
           <action>Display generated content</action>
           <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
               response="a">
-              <action>Start the advanced elicitation workflow {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</action>
+              <action>Start the advanced elicitation workflow {project-root}/.bmad/core/tasks/advanced-elicitation.xml</action>
             </if>
             <if
               response="c">
               <action>Continue to next step</action>
             </if>
             <if response="p">
-              <action>Start the party-mode workflow {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml</action>
+              <action>Start the party-mode workflow {project-root}/.bmad/core/workflows/party-mode/workflow.yaml</action>
             </if>
             <if
               response="y">
@@ -225,7 +225,7 @@
     <critical-rules>
       • This is the complete workflow execution engine
       • You MUST Follow instructions exactly as written
-      • The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml
+      • The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml
       • You MUST have already loaded and processed: {installed_path}/workflow.yaml
       • This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context
       • YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be

src/core/tools/shard-doc.xml

@@ -1,4 +1,4 @@
-<tool id="{bmad_folder}/core/tasks/shard-doc" name="Shard Document"
+<tool id=".bmad/core/tasks/shard-doc" name="Shard Document"
   description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
   standalone="true">
   <objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>

src/core/workflows/brainstorming/workflow.md

@@ -28,7 +28,7 @@ This uses **micro-file architecture** for disciplined execution:
 
 ### Configuration Loading
 
-Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve:
+Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
 
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
@@ -36,7 +36,7 @@ Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/brainstorming`
+- `installed_path` = `{project-root}/.bmad/core/workflows/brainstorming`
 - `template_path` = `{installed_path}/template.md`
 - `brain_techniques_path` = `{installed_path}/brain-methods.csv`
 - `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`

src/core/workflows/party-mode/steps/step-01-agent-loading.md

@@ -18,7 +18,7 @@
 
 ## CONTEXT BOUNDARIES:
 
-- Agent manifest CSV is available at `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- Agent manifest CSV is available at `{project-root}/.bmad/_cfg/agent-manifest.csv`
 - User configuration from config.yaml is loaded and resolved
 - Party mode is standalone interactive workflow
 - All agent data is available for conversation orchestration
@@ -37,7 +37,7 @@ Begin agent loading process:
 
 **Agent Manifest Loading:**"
 
-Load and parse the agent manifest CSV from `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+Load and parse the agent manifest CSV from `{project-root}/.bmad/_cfg/agent-manifest.csv`
 
 ### 2. Extract Agent Data
 

src/core/workflows/party-mode/workflow.md

@@ -27,17 +27,17 @@ This uses **micro-file architecture** with **sequential conversation orchestrati
 
 ### Configuration Loading
 
-Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve:
+Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
 
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as a system-generated value
-- Agent manifest path: `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- Agent manifest path: `{project-root}/.bmad/_cfg/agent-manifest.csv`
 
 ### Paths
 
-- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/party-mode`
+- `installed_path` = `{project-root}/.bmad/core/workflows/party-mode`
-- `agent_manifest_path` = `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- `agent_manifest_path` = `{project-root}/.bmad/_cfg/agent-manifest.csv`
 - `standalone_mode` = `true` (party mode is an interactive workflow)
 
 ---

src/modules/autominator/README.md

@@ -0,0 +1,335 @@
+# Autominator - n8n Workflow Automation Module
+
+**Arnold the Autominator - I'll be back... with your workflows automated!** 🦾
+
+Standalone module for n8n workflow automation, creation, migration, and optimization. Build, modify, migrate, and optimize n8n workflows with expert guidance and up-to-date documentation.
+
+## Overview
+
+Autominator is an independent BMAD module that specializes in n8n workflow automation. Whether you're building new workflows from scratch, migrating from other platforms, or optimizing existing workflows, Arnold has you covered.
+
+## Agent
+
+**Arnold** - n8n Workflow Automation Specialist
+
+- Expert in n8n workflow creation, modification, and optimization
+- Specializes in platform migration (Zapier, Make, HubSpot, Power Automate)
+- Uses web search to access up-to-date n8n documentation
+- Smart elicitation for accurate requirement gathering
+- Comprehensive workflow validation and testing
+
+## Workflows
+
+### 1. Gather Requirements
+
+Gather and document workflow requirements before creating n8n workflows.
+
+**Triggers:**
+
+- `*gather-requirements`
+
+**Features:**
+
+- Interactive requirement gathering
+- Documents problem statement, triggers, integrations
+- Creates requirement file for workflow creation
+- Saves to `docs/workflow-requirements/`
+- Required before creating workflows
+
+### 2. Create Workflow
+
+Build new n8n workflows from scratch based on requirements.
+
+**Triggers:**
+
+- `*create-workflow`
+
+**Features:**
+
+- Smart elicitation to understand your needs
+- Workflow type selection (webhook, scheduled, event-driven, manual, database-driven)
+- Integration selection and configuration
+- Complexity assessment
+- Error handling strategy planning
+- Web search integration for latest n8n docs
+- Automatic JSON validation
+
+### 3. Modify Workflow
+
+Edit or update existing n8n workflows with backup and safety checks.
+
+**Triggers:**
+
+- `*modify-workflow`
+
+**Features:**
+
+- Load existing workflows from file or paste
+- Selective modification (add, modify, or remove nodes)
+- Connection management
+- Automatic backup creation
+- Change validation
+- Rollback capability
+
+### 4. Migrate Workflow
+
+Migrate automation workflows from other platforms to n8n.
+
+**Supported Platforms:**
+
+- Zapier
+- Make (Integromat)
+- HubSpot Workflows
+- Microsoft Power Automate
+- IFTTT
+- Custom platforms
+
+**Triggers:**
+
+- `*migrate-workflow`
+
+**Features:**
+
+- Platform-specific mapping
+- Trigger and action conversion
+- Data transformation planning
+- Credential requirement identification
+- Migration notes and documentation
+- Post-migration testing guidance
+
+### 5. Optimize Workflow
+
+Analyze and improve existing n8n workflows for performance and best practices.
+
+**Triggers:**
+
+- `*optimize-workflow`
+
+**Features:**
+
+- Comprehensive workflow analysis
+- Performance optimization recommendations
+- Error handling improvements
+- Code quality assessment
+- Structure optimization
+- Best practices validation
+- Security review
+- Automatic backup before changes
+- Selective optimization application
+
+## Quick Start
+
+### Load Arnold Agent
+
+```bash
+# In your IDE, load the Autominator agent
+agent autominator/autominator
+
+# Or use the agent trigger
+*autominator
+```
+
+### Gather Requirements (Recommended First Step)
+
+```bash
+# Start the requirements gathering process
+*gather-requirements
+
+# Follow the interactive prompts to:
+# 1. Describe the problem you're solving
+# 2. Define trigger type
+# 3. Specify data requirements
+# 4. Define desired outcome
+# 5. List integrations
+# 6. Define conditional logic
+# 7. Set criticality level
+# 8. Name the workflow
+
+# Requirements are saved to: docs/workflow-requirements/req-{name}.md
+```
+
+### Create a Workflow
+
+```bash
+# Start the create workflow process
+*create-workflow
+
+# Arnold will:
+# 1. Check for requirements file (or prompt to create one)
+# 2. Load requirements automatically
+# 3. Research n8n documentation
+# 4. Design workflow structure
+# 5. Build and validate workflow JSON
+# 6. Save to docs/workflows/{name}.json
+```
+
+### Migrate from Another Platform
+
+```bash
+# Start the migration process
+*migrate-workflow
+
+# Provide:
+# 1. Source platform (Zapier, Make, HubSpot, etc.)
+# 2. Workflow details or export file
+# 3. Integration list
+# 4. Desired output location
+```
+
+### Optimize Existing Workflow
+
+```bash
+# Analyze and improve a workflow
+*optimize-workflow
+
+# Select optimization focus:
+# - Performance
+# - Error Handling
+# - Code Quality
+# - Structure
+# - Best Practices
+# - Security
+# - All
+```
+
+## Features
+
+### Web Search Integration
+
+- Automatic web search for n8n documentation
+- Accesses official docs.n8n.io resources
+- Up-to-date node configurations and best practices
+- Problem-specific solution research
+
+### Smart Elicitation
+
+- Contextual analysis of existing information
+- Numbered option selection
+- Progressive requirement gathering
+- Validation before execution
+
+### Comprehensive Validation
+
+- JSON syntax validation
+- Schema compliance checking
+- Connection integrity verification
+- Error recovery (never deletes files)
+
+### Platform Mappings
+
+Built-in mappings for:
+
+- Zapier triggers and actions
+- Make modules and routers
+- HubSpot workflow actions
+- Power Automate flows
+- Common automation patterns
+
+### Shared Resources
+
+- **n8n-helpers.md** - Node creation guidelines and patterns
+- **n8n-templates.yaml** - 8 reusable workflow templates
+- **platform-mappings.yaml** - Platform conversion reference
+
+## Module Structure
+
+```
+autominator/
+├── _module-installer/
+│   └── install-config.yaml
+├── agents/
+│   └── autominator.agent.yaml
+├── workflows/
+│   ├── _shared/
+│   │   ├── n8n-helpers.md
+│   │   ├── n8n-templates.yaml
+│   │   └── platform-mappings.yaml
+│   ├── create-workflow/
+│   │   ├── workflow.yaml
+│   │   ├── instructions.md
+│   │   └── checklist.md
+│   ├── modify-workflow/
+│   │   ├── workflow.yaml
+│   │   ├── instructions.md
+│   │   └── checklist.md
+│   ├── migrate-workflow/
+│   │   ├── workflow.yaml
+│   │   ├── instructions.md
+│   │   └── checklist.md
+│   └── optimize-workflow/
+│       ├── workflow.yaml
+│       ├── instructions.md
+│       └── checklist.md
+└── README.md
+```
+
+## Requirements
+
+- n8n instance or account
+- IDE with BMAD support
+
+## Installation
+
+Autominator is a standalone module and can be installed independently:
+
+```bash
+# Install via BMAD
+npx bmad-method@alpha install autominator
+
+# Or manually copy to your BMAD installation
+cp -r autominator/ /path/to/bmad/src/modules/
+```
+
+## Integration with Other Modules
+
+Autominator is independent but can be used alongside:
+
+- **BMM** - For project lifecycle management
+- **CIS** - For creative workflow design
+- **BMB** - For module building
+- **BMGD** - For game development workflows
+
+## Best Practices
+
+1. **Provide Clear Context** - Describe your workflow purpose and requirements
+2. **Use Smart Elicitation** - Let Arnold ask clarifying questions
+3. **Test Before Activation** - Always test workflows with sample data
+4. **Monitor Initial Runs** - Watch for errors in first executions
+5. **Document Changes** - Keep notes on workflow modifications
+6. **Backup Regularly** - Use modify-workflow's backup feature
+7. **Review Optimizations** - Understand changes before applying
+
+## Troubleshooting
+
+### Workflow JSON Validation Fails
+
+- Check for missing commas or brackets
+- Verify all node IDs are unique
+- Ensure all connections reference existing nodes
+- Use the error location to fix syntax
+
+### Workflow Execution Issues
+
+- Verify all credentials are configured
+- Test with sample data first
+- Check error handling settings
+- Review workflow logs for details
+
+## Related Documentation
+
+- **[n8n Documentation](https://docs.n8n.io/)** - Official n8n docs
+- **[BMAD Method](../bmm/README.md)** - Core BMAD framework
+- **[CIS Module](../cis/README.md)** - Creative facilitation
+- **[BMB Module](../bmb/README.md)** - Module building
+
+## Support
+
+- **Issues** - Report bugs on GitHub
+- **Questions** - Check the troubleshooting section
+- **Feedback** - Share suggestions for improvements
+
+---
+
+**Ready to automate?** Load Arnold and start with `*create-workflow`!
+
+Part of BMad Method - Transform automation potential through expert AI guidance.

src/modules/autominator/_module-installer/install-config.yaml

@@ -0,0 +1,57 @@
+# Autominator Module Installation Configuration
+
+code: autominator
+name: "Autominator: n8n Workflow Automation"
+default_selected: false
+
+header: "Autominator - n8n Workflow Automation Module"
+subheader: "Configure the settings for the Autominator module"
+
+# Core config values automatically inherited:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+## bmad_folder
+## install_user_docs
+## kb_install
+
+n8n_instance_url:
+  prompt: "What is your n8n instance URL? (optional, for reference)"
+  default: "https://n8n.example.com"
+  result: "{value}"
+
+workflow_output_folder:
+  prompt: "Where should generated workflows be stored?"
+  default: "{output_folder}/n8n-workflows"
+  result: "{project-root}/{value}"
+
+automation_experience:
+  prompt: "What is your n8n/automation experience level?"
+  default: "intermediate"
+  result: "{value}"
+  single-select:
+    - value: "beginner"
+      label: "Beginner - New to n8n, provide detailed guidance"
+    - value: "intermediate"
+      label: "Intermediate - Familiar with n8n concepts, balanced approach"
+    - value: "expert"
+      label: "Expert - Experienced n8n developer, be direct and technical"
+
+primary_integrations:
+  prompt: "Which integrations do you primarily use? (select all that apply)"
+  default: ["http", "database"]
+  result: "{value}"
+  multi-select:
+    - value: "http"
+      label: "HTTP/REST APIs"
+    - value: "database"
+      label: "Databases (PostgreSQL, MySQL, MongoDB)"
+    - value: "cloud"
+      label: "Cloud Services (Google Sheets, Slack, Notion, Airtable)"
+    - value: "crm"
+      label: "CRM Systems (HubSpot, Salesforce)"
+    - value: "email"
+      label: "Email"
+    - value: "custom"
+      label: "Custom/Other"

src/modules/autominator/agents/autominator.agent.yaml

@@ -0,0 +1,48 @@
+# Autominator - Arnold the Automation Expert
+
+agent:
+  webskip: true
+  metadata:
+    id: "{bmad_folder}/autominator/agents/autominator.md"
+    name: Arnold
+    title: Arnold the Autominator
+    icon: 🦾
+    module: autominator
+
+  persona:
+    role: n8n Workflow Automation Specialist
+    identity: Arnold the Autominator - I'll be back... with your workflows automated! 🦾 Expert in n8n workflow creation, migration, and optimization. Specializes in building automation workflows, migrating from other platforms (Zapier, Make, HubSpot), and optimizing existing n8n workflows using up-to-date documentation via web search.
+    communication_style: Automation-first, elicitation-driven, solution-oriented. Presents options as numbered lists for easy selection. Always validates understanding before building. Direct, confident, and results-focused.
+    principles: |
+      - Web Search Integration - Always search for latest n8n documentation from docs.n8n.io for accurate, up-to-date implementations.
+      - Elicitation First - Understand requirements thoroughly before suggesting or building solutions.
+      - Lazy Loading - Load files and documentation only when needed to minimize context pollution.
+      - Validation - Always validate workflow JSON syntax after creation.
+      - Platform Agnostic - Support migration from any automation platform with proper mapping.
+      - Error Recovery - NEVER delete files due to syntax errors, always fix them using error location information.
+      - Structured Approach - Follow task-specific workflows for different automation scenarios.
+
+  menu:
+    - trigger: gather-requirements
+      workflow: "{project-root}/{bmad_folder}/autominator/workflows/gather-requirements/workflow.yaml"
+      description: Gather and document workflow requirements (run this first before creating workflows)
+
+    - trigger: create-workflow
+      workflow: "{project-root}/{bmad_folder}/autominator/workflows/create-workflow/workflow.yaml"
+      description: Create new n8n workflow from scratch based on requirements
+
+    - trigger: modify-workflow
+      workflow: "{project-root}/{bmad_folder}/autominator/workflows/modify-workflow/workflow.yaml"
+      description: Edit or update existing n8n workflow
+
+    - trigger: migrate-workflow
+      workflow: "{project-root}/{bmad_folder}/autominator/workflows/migrate-workflow/workflow.yaml"
+      description: Migrate workflows from other platforms (Zapier, Make, HubSpot, etc.) to n8n
+
+    - trigger: optimize-workflow
+      workflow: "{project-root}/{bmad_folder}/autominator/workflows/optimize-workflow/workflow.yaml"
+      description: Review and improve existing n8n workflows for performance and best practices
+
+    - trigger: party-mode
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      description: Bring the whole team in to chat with other expert agents from the party

src/modules/autominator/workflows/_shared/n8n-helpers.md

@@ -0,0 +1,405 @@
+# n8n Workflow Helpers
+
+## UUID Generation
+
+n8n uses UUIDs for node IDs, workflow IDs, and webhook IDs. Generate UUIDs in this format:
+
+**Full UUID (36 characters):** `f8b7ff4f-6375-4c79-9b2c-9814bfdd0c92`
+
+- Used for: node `id`, `webhookId`, `versionId`
+- Format: 8-4-4-4-12 hexadecimal characters with hyphens
+
+**Short ID (16 characters):** `Wvmqb0POKmqwCoKy`
+
+- Used for: workflow `id`, tag `id`
+- Format: alphanumeric (a-z, A-Z, 0-9)
+
+**Assignment ID:** `id-1`, `id-2`, `id-3`
+
+- Used for: Set node assignments, IF node conditions
+- Format: "id-" + sequential number
+
+## Node Creation Guidelines
+
+### Basic Node Structure (Modern n8n Format)
+
+```json
+{
+  "parameters": {},
+  "id": "f8b7ff4f-6375-4c79-9b2c-9814bfdd0c92",
+  "name": "Node Name",
+  "type": "n8n-nodes-base.nodeName",
+  "typeVersion": 2,
+  "position": [1424, 496],
+  "webhookId": "b5f0b784-2440-4371-bcf1-b59dd2b29e68",
+  "credentials": {}
+}
+```
+
+**Critical Rules:**
+
+- `parameters` comes FIRST
+- `id` must be UUID format (e.g., "f8b7ff4f-6375-4c79-9b2c-9814bfdd0c92")
+- `type` must be `n8n-nodes-base.nodeName` format (NOT @n8n/n8n-nodes-\*)
+- `typeVersion` must be INTEGER (e.g., 2, 3, 4) NOT float (2.1, 3.4)
+- `position` must be array of integers: [x, y]
+- `webhookId` required for webhook nodes (UUID format)
+- Field order matters for n8n compatibility
+
+### Node Positioning
+
+- Start node: [250, 300]
+- Horizontal spacing: 220px between nodes
+- Vertical spacing: 100px for parallel branches
+- Grid alignment: Snap to 20px grid for clean layout
+
+### Common Node Types
+
+### ⚠️ CRITICAL: Node Type Format Rules
+
+**ALWAYS use format:** `n8n-nodes-base.nodeName`
+
+**NEVER use these formats:**
+
+- ❌ `@n8n/n8n-nodes-slack.slackTrigger` (wrong package format)
+- ❌ `n8n-nodes-slack.slackTrigger` (missing base)
+- ❌ `slackTrigger` (missing prefix)
+
+**Correct Examples:**
+
+- ✅ `n8n-nodes-base.webhook`
+- ✅ `n8n-nodes-base.slackTrigger`
+- ✅ `n8n-nodes-base.gmail`
+- ✅ `n8n-nodes-base.if`
+
+**Trigger Nodes:**
+
+- `n8n-nodes-base.webhook` - HTTP webhook trigger
+- `n8n-nodes-base.scheduleTrigger` - Cron/interval trigger
+- `n8n-nodes-base.manualTrigger` - Manual execution trigger
+- `n8n-nodes-base.emailTrigger` - Email trigger
+- `n8n-nodes-base.slackTrigger` - Slack event trigger
+
+**Action Nodes:**
+
+- `n8n-nodes-base.httpRequest` - HTTP API calls
+- `n8n-nodes-base.set` - Data transformation
+- `n8n-nodes-base.code` - Custom JavaScript/Python code
+- `n8n-nodes-base.if` - Conditional branching
+- `n8n-nodes-base.merge` - Merge data from multiple branches
+- `n8n-nodes-base.splitInBatches` - Process data in batches
+
+**Integration Nodes:**
+
+- `n8n-nodes-base.googleSheets` - Google Sheets
+- `n8n-nodes-base.slack` - Slack actions
+- `n8n-nodes-base.gmail` - Gmail
+- `n8n-nodes-base.notion` - Notion
+- `n8n-nodes-base.airtable` - Airtable
+- `n8n-nodes-base.postgres` - PostgreSQL
+- `n8n-nodes-base.mysql` - MySQL
+
+## Connection Guidelines
+
+### Connection Structure
+
+### ⚠️ CRITICAL: Connection Format Rules
+
+**CORRECT Format:**
+
+```json
+{
+  "Source Node Name": {
+    "main": [
+      [
+        {
+          "node": "Target Node Name",
+          "type": "main",
+          "index": 0
+        }
+      ]
+    ]
+  }
+}
+```
+
+**WRONG Formats:**
+
+```json
+// ❌ WRONG - Missing "main" wrapper
+{
+  "Source Node Name": [
+    [
+      {
+        "node": "Target Node Name",
+        "type": "main",
+        "index": 0
+      }
+    ]
+  ]
+}
+
+// ❌ WRONG - Direct array
+{
+  "Source Node Name": [[{...}]]
+}
+```
+
+### Connection Rules
+
+1. Each connection has a source node and target node
+2. Connections object structure: `{"Source": {"main": [[{...}]]}}`
+3. The "main" key is REQUIRED (wraps the connection array)
+4. Index 0 is default output, index 1+ for conditional branches
+5. IF nodes have index 0 (true) and index 1 (false)
+6. Always validate that referenced node names exist
+
+### Connection Patterns
+
+**Linear Flow:**
+
+```
+Trigger → Action1 → Action2 → End
+```
+
+**Conditional Branch:**
+
+```
+Trigger → IF Node → [true: Action1, false: Action2] → Merge
+```
+
+**Parallel Processing:**
+
+```
+Trigger → Split → [Branch1, Branch2, Branch3] → Merge
+```
+
+## Error Handling Best Practices
+
+### Error Workflow Pattern
+
+```json
+{
+  "name": "Error Handler",
+  "type": "n8n-nodes-base.errorTrigger",
+  "parameters": {
+    "errorWorkflows": ["workflow-id"]
+  }
+}
+```
+
+### Retry Configuration
+
+```json
+{
+  "retryOnFail": true,
+  "maxTries": 3,
+  "waitBetweenTries": 1000
+}
+```
+
+## Data Transformation Patterns
+
+### Using Set Node (Modern Format - typeVersion 3+)
+
+```json
+{
+  "name": "Transform Data",
+  "type": "n8n-nodes-base.set",
+  "typeVersion": 3,
+  "parameters": {
+    "assignments": {
+      "assignments": [
+        {
+          "id": "id-1",
+          "name": "outputField",
+          "value": "={{ $json.inputField }}",
+          "type": "string"
+        }
+      ]
+    },
+    "includeOtherFields": true,
+    "options": {}
+  }
+}
+```
+
+**Critical Rules for Set Node:**
+
+- Use `assignments.assignments` structure (not `values`)
+- Each assignment needs `id` field (e.g., "id-1", "id-2")
+- Each assignment needs `type` field ("string", "number", "boolean")
+- Include `includeOtherFields: true` to pass through other data
+- Include `options: {}` for compatibility
+
+### Using Gmail Node (typeVersion 2+)
+
+```json
+{
+  "name": "Send Email",
+  "type": "n8n-nodes-base.gmail",
+  "typeVersion": 2,
+  "parameters": {
+    "sendTo": "user@example.com",
+    "subject": "Email Subject",
+    "message": "Email body content",
+    "options": {}
+  }
+}
+```
+
+**Critical Rules for Gmail Node:**
+
+- Use `message` parameter (NOT `text`)
+- Use `sendTo` (NOT `to`)
+- Include `options: {}` for compatibility
+
+### Using Slack Node with Channel Selection
+
+```json
+{
+  "name": "Slack Action",
+  "type": "n8n-nodes-base.slack",
+  "typeVersion": 2,
+  "parameters": {
+    "channel": {
+      "__rl": true,
+      "value": "general",
+      "mode": "list",
+      "cachedResultName": "#general"
+    }
+  }
+}
+```
+
+**Critical Rules for Slack Channel:**
+
+- Use `__rl: true` flag for resource locator
+- Include `mode: "list"` for channel selection
+- Include `cachedResultName` with # prefix
+
+### Using IF Node (typeVersion 2+)
+
+```json
+{
+  "name": "Check Condition",
+  "type": "n8n-nodes-base.if",
+  "typeVersion": 2,
+  "parameters": {
+    "conditions": {
+      "options": {
+        "caseSensitive": false,
+        "leftValue": "",
+        "typeValidation": "loose"
+      },
+      "conditions": [
+        {
+          "id": "id-1",
+          "leftValue": "={{ $json.field }}",
+          "rightValue": "value",
+          "operator": {
+            "type": "string",
+            "operation": "equals"
+          }
+        }
+      ],
+      "combinator": "and"
+    },
+    "options": {}
+  }
+}
+```
+
+**Critical Rules for IF Node:**
+
+- Use `conditions.conditions` structure
+- Each condition needs `id` field
+- Do NOT include `name` field in conditions
+- Use `operator` object with `type` and `operation`
+- Include `options` at root level
+
+### Using Code Node
+
+```json
+{
+  "name": "Custom Logic",
+  "type": "n8n-nodes-base.code",
+  "parameters": {
+    "language": "javaScript",
+    "jsCode": "return items.map(item => ({ json: { ...item.json, processed: true } }));"
+  }
+}
+```
+
+## Credentials Management
+
+### Credential Reference
+
+```json
+{
+  "credentials": {
+    "httpBasicAuth": {
+      "id": "credential-id",
+      "name": "My API Credentials"
+    }
+  }
+}
+```
+
+### Common Credential Types
+
+- `httpBasicAuth` - Basic authentication
+- `oAuth2Api` - OAuth2
+- `httpHeaderAuth` - Header-based auth
+- `httpQueryAuth` - Query parameter auth
+
+## Workflow Metadata (Modern n8n Format)
+
+### Required Fields
+
+```json
+{
+  "name": "Workflow Name",
+  "nodes": [],
+  "pinData": {},
+  "connections": {},
+  "active": false,
+  "settings": {
+    "executionOrder": "v1"
+  },
+  "versionId": "7d745171-e378-411c-bd0a-25a8368a1cb6",
+  "meta": {
+    "templateCredsSetupCompleted": true,
+    "instanceId": "2229c21690ffe7e7b16788a579be3103980c4445acb933f7ced2a6a17f0bd18b"
+  },
+  "id": "Wvmqb0POKmqwCoKy",
+  "tags": [
+    {
+      "name": "Automation",
+      "id": "7FHIZPUaIaChwuiS",
+      "updatedAt": "2025-11-21T19:39:46.484Z",
+      "createdAt": "2025-11-21T19:39:46.484Z"
+    }
+  ]
+}
+```
+
+**Critical Rules:**
+
+- `pinData` must be empty object `{}`
+- `versionId` must be UUID
+- `meta` object with `templateCredsSetupCompleted` and `instanceId`
+- `id` must be short alphanumeric (e.g., "Wvmqb0POKmqwCoKy")
+- `tags` must be array of objects (not strings) with id, name, createdAt, updatedAt
+
+## Validation Checklist
+
+- [ ] All node IDs are unique
+- [ ] All node names are unique
+- [ ] All connections reference existing nodes
+- [ ] Trigger node exists and is properly configured
+- [ ] Node positions don't overlap
+- [ ] Required parameters are set for each node
+- [ ] Credentials are properly referenced
+- [ ] Error handling is configured where needed
+- [ ] JSON syntax is valid

src/modules/autominator/workflows/_shared/n8n-templates.yaml

@@ -0,0 +1,299 @@
+# n8n Workflow Templates
+
+# Basic webhook workflow template
+webhook_workflow:
+  name: "Webhook Workflow"
+  nodes:
+    - id: "webhook_trigger"
+      name: "Webhook"
+      type: "n8n-nodes-base.webhook"
+      typeVersion: 1
+      position: [250, 300]
+      parameters:
+        httpMethod: "POST"
+        path: "webhook-path"
+        responseMode: "onReceived"
+    - id: "process_data"
+      name: "Process Data"
+      type: "n8n-nodes-base.set"
+      typeVersion: 1
+      position: [470, 300]
+      parameters:
+        mode: "manual"
+        values: {}
+  connections:
+    Webhook:
+      - - node: "Process Data"
+          type: "main"
+          index: 0
+
+# Scheduled workflow template
+scheduled_workflow:
+  name: "Scheduled Workflow"
+  nodes:
+    - id: "schedule_trigger"
+      name: "Schedule Trigger"
+      type: "n8n-nodes-base.scheduleTrigger"
+      typeVersion: 1
+      position: [250, 300]
+      parameters:
+        rule:
+          interval:
+            - field: "hours"
+              hoursInterval: 1
+    - id: "execute_action"
+      name: "Execute Action"
+      type: "n8n-nodes-base.httpRequest"
+      typeVersion: 1
+      position: [470, 300]
+      parameters:
+        method: "GET"
+        url: ""
+  connections:
+    Schedule Trigger:
+      - - node: "Execute Action"
+          type: "main"
+          index: 0
+
+# Conditional workflow template
+conditional_workflow:
+  name: "Conditional Workflow"
+  nodes:
+    - id: "manual_trigger"
+      name: "Manual Trigger"
+      type: "n8n-nodes-base.manualTrigger"
+      typeVersion: 1
+      position: [250, 300]
+      parameters: {}
+    - id: "if_condition"
+      name: "IF"
+      type: "n8n-nodes-base.if"
+      typeVersion: 1
+      position: [470, 300]
+      parameters:
+        conditions:
+          boolean: []
+          number: []
+          string: []
+    - id: "true_branch"
+      name: "True Branch"
+      type: "n8n-nodes-base.noOp"
+      typeVersion: 1
+      position: [690, 200]
+      parameters: {}
+    - id: "false_branch"
+      name: "False Branch"
+      type: "n8n-nodes-base.noOp"
+      typeVersion: 1
+      position: [690, 400]
+      parameters: {}
+  connections:
+    Manual Trigger:
+      - - node: "IF"
+          type: "main"
+          index: 0
+    IF:
+      - - node: "True Branch"
+          type: "main"
+          index: 0
+      - - node: "False Branch"
+          type: "main"
+          index: 0
+
+# API integration workflow template
+api_integration_workflow:
+  name: "API Integration Workflow"
+  nodes:
+    - id: "webhook_trigger"
+      name: "Webhook"
+      type: "n8n-nodes-base.webhook"
+      typeVersion: 1
+      position: [250, 300]
+      parameters:
+        httpMethod: "POST"
+        path: "api-webhook"
+        responseMode: "onReceived"
+    - id: "http_request"
+      name: "HTTP Request"
+      type: "n8n-nodes-base.httpRequest"
+      typeVersion: 1
+      position: [470, 300]
+      parameters:
+        method: "POST"
+        url: ""
+        jsonParameters: true
+        options: {}
+    - id: "transform_response"
+      name: "Transform Response"
+      type: "n8n-nodes-base.set"
+      typeVersion: 1
+      position: [690, 300]
+      parameters:
+        mode: "manual"
+        values: {}
+  connections:
+    Webhook:
+      - - node: "HTTP Request"
+          type: "main"
+          index: 0
+    HTTP Request:
+      - - node: "Transform Response"
+          type: "main"
+          index: 0
+
+# Database workflow template
+database_workflow:
+  name: "Database Workflow"
+  nodes:
+    - id: "schedule_trigger"
+      name: "Schedule Trigger"
+      type: "n8n-nodes-base.scheduleTrigger"
+      typeVersion: 1
+      position: [250, 300]
+      parameters:
+        rule:
+          interval:
+            - field: "minutes"
+              minutesInterval: 15
+    - id: "postgres_query"
+      name: "Postgres"
+      type: "n8n-nodes-base.postgres"
+      typeVersion: 1
+      position: [470, 300]
+      parameters:
+        operation: "executeQuery"
+        query: ""
+    - id: "process_results"
+      name: "Process Results"
+      type: "n8n-nodes-base.code"
+      typeVersion: 1
+      position: [690, 300]
+      parameters:
+        language: "javaScript"
+        jsCode: "return items;"
+  connections:
+    Schedule Trigger:
+      - - node: "Postgres"
+          type: "main"
+          index: 0
+    Postgres:
+      - - node: "Process Results"
+          type: "main"
+          index: 0
+
+# Error handling workflow template
+error_handling_workflow:
+  name: "Error Handling Workflow"
+  nodes:
+    - id: "manual_trigger"
+      name: "Manual Trigger"
+      type: "n8n-nodes-base.manualTrigger"
+      typeVersion: 1
+      position: [250, 300]
+      parameters: {}
+    - id: "risky_operation"
+      name: "Risky Operation"
+      type: "n8n-nodes-base.httpRequest"
+      typeVersion: 1
+      position: [470, 300]
+      parameters:
+        method: "GET"
+        url: ""
+      continueOnFail: true
+      retryOnFail: true
+      maxTries: 3
+      waitBetweenTries: 1000
+    - id: "check_error"
+      name: "Check for Error"
+      type: "n8n-nodes-base.if"
+      typeVersion: 1
+      position: [690, 300]
+      parameters:
+        conditions:
+          boolean:
+            - value1: "={{ $json.error !== undefined }}"
+              value2: true
+    - id: "handle_error"
+      name: "Handle Error"
+      type: "n8n-nodes-base.set"
+      typeVersion: 1
+      position: [910, 200]
+      parameters:
+        mode: "manual"
+        values:
+          string:
+            - name: "status"
+              value: "error"
+    - id: "success_path"
+      name: "Success Path"
+      type: "n8n-nodes-base.noOp"
+      typeVersion: 1
+      position: [910, 400]
+      parameters: {}
+  connections:
+    Manual Trigger:
+      - - node: "Risky Operation"
+          type: "main"
+          index: 0
+    Risky Operation:
+      - - node: "Check for Error"
+          type: "main"
+          index: 0
+    Check for Error:
+      - - node: "Handle Error"
+          type: "main"
+          index: 0
+      - - node: "Success Path"
+          type: "main"
+          index: 0
+
+# Batch processing workflow template
+batch_processing_workflow:
+  name: "Batch Processing Workflow"
+  nodes:
+    - id: "manual_trigger"
+      name: "Manual Trigger"
+      type: "n8n-nodes-base.manualTrigger"
+      typeVersion: 1
+      position: [250, 300]
+      parameters: {}
+    - id: "get_data"
+      name: "Get Data"
+      type: "n8n-nodes-base.httpRequest"
+      typeVersion: 1
+      position: [470, 300]
+      parameters:
+        method: "GET"
+        url: ""
+    - id: "split_batches"
+      name: "Split In Batches"
+      type: "n8n-nodes-base.splitInBatches"
+      typeVersion: 1
+      position: [690, 300]
+      parameters:
+        batchSize: 10
+    - id: "process_batch"
+      name: "Process Batch"
+      type: "n8n-nodes-base.code"
+      typeVersion: 1
+      position: [910, 300]
+      parameters:
+        language: "javaScript"
+        jsCode: "return items;"
+  connections:
+    Manual Trigger:
+      - - node: "Get Data"
+          type: "main"
+          index: 0
+    Get Data:
+      - - node: "Split In Batches"
+          type: "main"
+          index: 0
+    Split In Batches:
+      - - node: "Process Batch"
+          type: "main"
+          index: 0
+    Process Batch:
+      - - node: "Split In Batches"
+          type: "main"
+          index: 0

src/modules/autominator/workflows/_shared/platform-mappings.yaml

@@ -0,0 +1,282 @@
+# Platform Migration Mappings
+# Maps common automation platform concepts to n8n equivalents
+
+# Zapier to n8n mappings
+zapier:
+  triggers:
+    "New Email":
+      n8n_node: "n8n-nodes-base.emailTrigger"
+      notes: "Configure IMAP/POP3 credentials"
+    "Webhook":
+      n8n_node: "n8n-nodes-base.webhook"
+      notes: "Use POST method by default"
+    "Schedule":
+      n8n_node: "n8n-nodes-base.scheduleTrigger"
+      notes: "Convert Zapier schedule format to cron"
+    "New Row in Google Sheets":
+      n8n_node: "n8n-nodes-base.googleSheetsTrigger"
+      notes: "Requires Google OAuth credentials"
+    "New Slack Message":
+      n8n_node: "n8n-nodes-base.slackTrigger"
+      notes: "Configure channel and event type"
+
+  actions:
+    "Send Email":
+      n8n_node: "n8n-nodes-base.emailSend"
+      notes: "Configure SMTP credentials"
+    "HTTP Request":
+      n8n_node: "n8n-nodes-base.httpRequest"
+      notes: "Map method, URL, headers, and body"
+    "Create Google Sheets Row":
+      n8n_node: "n8n-nodes-base.googleSheets"
+      parameters:
+        operation: "append"
+    "Send Slack Message":
+      n8n_node: "n8n-nodes-base.slack"
+      parameters:
+        operation: "post"
+        resource: "message"
+    "Delay":
+      n8n_node: "n8n-nodes-base.wait"
+      notes: "Convert delay duration to milliseconds"
+    "Filter":
+      n8n_node: "n8n-nodes-base.if"
+      notes: "Convert filter conditions to IF node logic"
+    "Formatter":
+      n8n_node: "n8n-nodes-base.set"
+      notes: "Use Set node for data transformation"
+    "Code":
+      n8n_node: "n8n-nodes-base.code"
+      notes: "JavaScript or Python code execution"
+
+  concepts:
+    "Multi-step Zap":
+      n8n_equivalent: "Linear workflow with connected nodes"
+    "Paths":
+      n8n_equivalent: "IF node with multiple branches"
+    "Filters":
+      n8n_equivalent: "IF node with conditions"
+    "Formatter":
+      n8n_equivalent: "Set node or Code node"
+    "Looping":
+      n8n_equivalent: "Split In Batches node"
+
+# Make (Integromat) to n8n mappings
+make:
+  triggers:
+    "Webhook":
+      n8n_node: "n8n-nodes-base.webhook"
+      notes: "Direct equivalent"
+    "Watch Records":
+      n8n_node: "n8n-nodes-base.scheduleTrigger"
+      notes: "Combine with polling logic in Code node"
+    "Custom Webhook":
+      n8n_node: "n8n-nodes-base.webhook"
+      notes: "Configure response mode"
+
+  actions:
+    "HTTP Request":
+      n8n_node: "n8n-nodes-base.httpRequest"
+      notes: "Map all HTTP parameters"
+    "Router":
+      n8n_node: "n8n-nodes-base.switch"
+      notes: "Multiple conditional branches"
+    "Iterator":
+      n8n_node: "n8n-nodes-base.splitInBatches"
+      notes: "Process array items individually"
+    "Aggregator":
+      n8n_node: "n8n-nodes-base.merge"
+      notes: "Combine data from multiple sources"
+    "Data Store":
+      n8n_node: "n8n-nodes-base.redis"
+      notes: "Use Redis or database node for storage"
+    "JSON Parser":
+      n8n_node: "n8n-nodes-base.code"
+      notes: "Parse JSON in Code node"
+    "Text Parser":
+      n8n_node: "n8n-nodes-base.set"
+      notes: "Use expressions for text manipulation"
+
+  concepts:
+    "Scenario":
+      n8n_equivalent: "Workflow"
+    "Module":
+      n8n_equivalent: "Node"
+    "Route":
+      n8n_equivalent: "Connection"
+    "Filter":
+      n8n_equivalent: "IF node"
+    "Router":
+      n8n_equivalent: "Switch node or multiple IF nodes"
+    "Iterator":
+      n8n_equivalent: "Split In Batches node"
+    "Aggregator":
+      n8n_equivalent: "Merge node"
+
+# HubSpot Workflows to n8n mappings
+hubspot:
+  triggers:
+    "Contact Property Change":
+      n8n_node: "n8n-nodes-base.hubspotTrigger"
+      notes: "Configure webhook for property updates"
+    "Deal Stage Change":
+      n8n_node: "n8n-nodes-base.hubspotTrigger"
+      notes: "Monitor deal pipeline changes"
+    "Form Submission":
+      n8n_node: "n8n-nodes-base.hubspotTrigger"
+      notes: "Webhook for form submissions"
+    "List Membership":
+      n8n_node: "n8n-nodes-base.scheduleTrigger"
+      notes: "Poll HubSpot API for list changes"
+
+  actions:
+    "Update Contact Property":
+      n8n_node: "n8n-nodes-base.hubspot"
+      parameters:
+        resource: "contact"
+        operation: "update"
+    "Create Deal":
+      n8n_node: "n8n-nodes-base.hubspot"
+      parameters:
+        resource: "deal"
+        operation: "create"
+    "Send Email":
+      n8n_node: "n8n-nodes-base.hubspot"
+      parameters:
+        resource: "email"
+        operation: "send"
+    "Add to List":
+      n8n_node: "n8n-nodes-base.hubspot"
+      parameters:
+        resource: "contact"
+        operation: "addToList"
+    "Create Task":
+      n8n_node: "n8n-nodes-base.hubspot"
+      parameters:
+        resource: "task"
+        operation: "create"
+
+  concepts:
+    "Enrollment Trigger":
+      n8n_equivalent: "Trigger node (webhook or schedule)"
+    "If/Then Branch":
+      n8n_equivalent: "IF node"
+    "Delay":
+      n8n_equivalent: "Wait node"
+    "Goal":
+      n8n_equivalent: "IF node checking completion criteria"
+    "Re-enrollment":
+      n8n_equivalent: "Workflow settings with loop detection"
+
+# Microsoft Power Automate to n8n mappings
+power_automate:
+  triggers:
+    "When an item is created":
+      n8n_node: "n8n-nodes-base.webhook"
+      notes: "Configure webhook for item creation events"
+    "Recurrence":
+      n8n_node: "n8n-nodes-base.scheduleTrigger"
+      notes: "Convert recurrence pattern to cron"
+    "When a HTTP request is received":
+      n8n_node: "n8n-nodes-base.webhook"
+      notes: "Direct equivalent"
+
+  actions:
+    "HTTP":
+      n8n_node: "n8n-nodes-base.httpRequest"
+      notes: "Map all HTTP parameters"
+    "Condition":
+      n8n_node: "n8n-nodes-base.if"
+      notes: "Convert condition logic"
+    "Apply to each":
+      n8n_node: "n8n-nodes-base.splitInBatches"
+      notes: "Process array items"
+    "Compose":
+      n8n_node: "n8n-nodes-base.set"
+      notes: "Data transformation"
+    "Parse JSON":
+      n8n_node: "n8n-nodes-base.code"
+      notes: "Parse JSON in Code node"
+    "Delay":
+      n8n_node: "n8n-nodes-base.wait"
+      notes: "Convert delay duration"
+
+  concepts:
+    "Flow":
+      n8n_equivalent: "Workflow"
+    "Action":
+      n8n_equivalent: "Node"
+    "Condition":
+      n8n_equivalent: "IF node"
+    "Switch":
+      n8n_equivalent: "Switch node"
+    "Scope":
+      n8n_equivalent: "Error handling with try/catch in Code node"
+    "Apply to each":
+      n8n_equivalent: "Split In Batches node"
+
+# Common patterns across platforms
+common_patterns:
+  conditional_logic:
+    description: "If/then/else branching"
+    n8n_implementation: "IF node with true/false branches"
+
+  loops:
+    description: "Iterate over array items"
+    n8n_implementation: "Split In Batches node"
+
+  data_transformation:
+    description: "Transform, format, or map data"
+    n8n_implementation: "Set node or Code node"
+
+  error_handling:
+    description: "Handle errors and retries"
+    n8n_implementation: "Node settings: continueOnFail, retryOnFail, maxTries"
+
+  delays:
+    description: "Wait before next action"
+    n8n_implementation: "Wait node with duration"
+
+  webhooks:
+    description: "Receive HTTP requests"
+    n8n_implementation: "Webhook node with response configuration"
+
+  api_calls:
+    description: "Make HTTP requests to APIs"
+    n8n_implementation: "HTTP Request node"
+
+  parallel_execution:
+    description: "Execute multiple actions simultaneously"
+    n8n_implementation: "Multiple connections from single node"
+
+  merge_data:
+    description: "Combine data from multiple sources"
+    n8n_implementation: "Merge node"
+
+# Migration considerations
+migration_notes:
+  authentication:
+    - "Recreate all credentials in n8n"
+    - "OAuth flows may need re-authorization"
+    - "API keys and tokens must be securely stored"
+
+  scheduling:
+    - "Convert platform-specific schedules to cron expressions"
+    - "Consider timezone differences"
+    - "Test schedule triggers before going live"
+
+  data_formats:
+    - "Verify JSON structure compatibility"
+    - "Check date/time format conversions"
+    - "Validate data type mappings"
+
+  error_handling:
+    - "Implement retry logic where needed"
+    - "Add error notification workflows"
+    - "Test failure scenarios"
+
+  testing:
+    - "Test with sample data first"
+    - "Verify all integrations work correctly"
+    - "Monitor initial executions closely"
+    - "Compare outputs with original platform"

src/modules/autominator/workflows/create-workflow/checklist.md

@@ -0,0 +1,74 @@
+# Create n8n Workflow - Validation Checklist
+
+## Workflow Structure
+
+- [ ] Workflow has a valid name
+- [ ] Workflow contains at least one trigger node
+- [ ] All nodes have unique IDs
+- [ ] All nodes have unique names
+- [ ] Workflow JSON is valid and parseable
+
+## Node Configuration
+
+- [ ] Trigger node is properly configured
+- [ ] All action nodes have required parameters set
+- [ ] Node types are valid n8n node types
+- [ ] Node positions are set and don't overlap
+- [ ] TypeVersion is set for all nodes (usually 1)
+
+## Connections
+
+- [ ] All nodes are connected (no orphaned nodes except trigger)
+- [ ] All connections reference existing node names
+- [ ] Connection types are set correctly (usually "main")
+- [ ] Connection indices are correct (0 for default, 0/1 for IF nodes)
+- [ ] No circular dependencies (unless intentional loops)
+
+## Error Handling
+
+- [ ] Error handling strategy matches requirements
+- [ ] Critical nodes have retry logic if needed
+- [ ] continueOnFail is set appropriately
+- [ ] maxTries and waitBetweenTries are configured if retries enabled
+
+## Data Flow
+
+- [ ] Data transformations are properly configured
+- [ ] Set nodes have correct value mappings
+- [ ] Code nodes have valid JavaScript/Python code
+- [ ] Expressions use correct n8n syntax (={{ }})
+
+## Integrations
+
+- [ ] All required integrations are included
+- [ ] Credential placeholders are set for authenticated services
+- [ ] API endpoints and methods are correct
+- [ ] Request/response formats are properly configured
+
+## Best Practices
+
+- [ ] Workflow follows n8n naming conventions
+- [ ] Nodes are logically organized and positioned
+- [ ] Complex logic is broken into manageable steps
+- [ ] Workflow is documented (node names are descriptive)
+
+## Testing Readiness
+
+- [ ] Workflow can be imported into n8n without errors
+- [ ] All required credentials are identified
+- [ ] Test data requirements are clear
+- [ ] Expected outputs are defined
+
+## File Output
+
+- [ ] File is saved to correct location
+- [ ] File has .json extension
+- [ ] File is valid JSON (passes JSON.parse)
+- [ ] File size is reasonable (not corrupted)
+
+## Documentation
+
+- [ ] User has been informed how to import workflow
+- [ ] Credential requirements have been communicated
+- [ ] Testing instructions have been provided
+- [ ] Any special configuration notes have been shared

src/modules/autominator/workflows/create-workflow/instructions.md

@@ -0,0 +1,449 @@
+# Create n8n Workflow - Workflow Instructions
+
+```xml
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>This workflow creates a new n8n workflow from scratch based on user requirements.</critical>
+
+<workflow>
+
+  <step n="0" goal="Load Config and Check Prerequisites">
+    <critical>Load configuration and check for requirements file before proceeding</critical>
+
+    <action>Resolve variables from config_source: workflows_folder, requirements_folder, output_folder, user_name, communication_language</action>
+    <action>Create {{workflows_folder}} directory if it does not exist</action>
+    <action>Create {{requirements_folder}} directory if it does not exist</action>
+
+    <action>Search for requirements files in {{requirements_folder}}</action>
+    <action>List all files matching pattern: req-*.md</action>
+
+    <check if="no requirements files found">
+      <output>⚠️ No Requirements File Found
+
+Before creating a workflow, you need to gather requirements.
+
+**Options:**
+1. Run `*gather-requirements` to create a requirements file
+2. Provide requirements manually in this session
+
+Would you like to:
+a) Run gather-requirements workflow now
+b) Continue without requirements file (manual elicitation)
+
+Enter your choice (a/b):</output>
+      <action>WAIT for user input</action>
+
+      <check if="user chooses 'a'">
+        <action>Invoke workflow: {project-root}/{bmad_folder}/autominator/workflows/gather-requirements/workflow.yaml</action>
+        <action>After gather-requirements completes, reload this step to find the new requirements file</action>
+      </check>
+
+      <check if="user chooses 'b'">
+        <action>Set {{requirements_file}} = empty</action>
+        <action>Proceed to Step 1 for manual elicitation</action>
+      </check>
+    </check>
+
+    <check if="one requirements file found">
+      <action>Set {{requirements_file}} to the found file path</action>
+      <action>Load and parse requirements file COMPLETELY</action>
+      <action>Extract requirements: workflow_name, problem_description, trigger_type, data_requirements, desired_outcome, integrations, conditional_logic, criticality</action>
+      <action>Extract research findings: use_case_research, node_research, parameter_structures, workflow_pattern_research</action>
+      <action>Display loaded requirements summary to user</action>
+      <action>Skip to Step 4 (Plan Workflow Structure) - research already done</action>
+    </check>
+
+    <check if="multiple requirements files found">
+      <output>📋 Multiple Requirements Files Found:
+
+[Display numbered list of files with workflow names]
+
+Which requirements file would you like to use?
+Enter the number (1-N) or 'new' to create a new one:</output>
+      <action>WAIT for user input</action>
+
+      <check if="user enters number">
+        <action>Set {{requirements_file}} to selected file path</action>
+        <action>Load and parse requirements file COMPLETELY</action>
+        <action>Extract requirements: workflow_name, problem_description, trigger_type, data_requirements, desired_outcome, integrations, conditional_logic, criticality</action>
+        <action>Extract research findings: use_case_research, node_research, parameter_structures, workflow_pattern_research</action>
+        <action>Display loaded requirements summary to user</action>
+        <action>Skip to Step 4 (Plan Workflow Structure) - research already done</action>
+      </check>
+
+      <check if="user enters 'new'">
+        <action>Invoke workflow: {project-root}/{bmad_folder}/autominator/workflows/gather-requirements/workflow.yaml</action>
+        <action>After gather-requirements completes, reload this step to find the new requirements file</action>
+      </check>
+    </check>
+  </step>
+
+  <step n="1" goal="Gather Requirements" elicit="true">
+    <critical>Start by understanding the ACTUAL PROBLEM the user wants to solve, not just technical requirements</critical>
+
+    <action>Ask Question 1: "What problem are you trying to solve with this automation?"</action>
+    <action>Encourage detailed explanation: "Describe the current manual process, pain points, and desired outcome."</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{problem_description}}</action>
+
+    <action>Ask Question 2: "What triggers this process? When should the automation run?"</action>
+    <action>Present numbered options:
+      1. When data arrives - Webhook, form submission, API call
+      2. On a schedule - Every hour, daily, weekly, custom cron
+      3. When something changes - Database update, file change, service event
+      4. Manually - On-demand execution
+      5. Multiple triggers - Combination of above
+      6. Not sure - Help me decide based on my problem
+    </action>
+    <action>WAIT for user selection (1-6)</action>
+    <action>Store selection in {{trigger_type}}</action>
+
+    <check if="selection is 6 (Not sure)">
+      <action>Analyze {{problem_description}} and suggest appropriate trigger</action>
+      <action>Ask: "Based on your problem, I recommend [trigger type]. Does this make sense?"</action>
+      <action>WAIT for confirmation or adjustment</action>
+      <action>Store final trigger in {{trigger_type}}</action>
+    </check>
+
+    <action>Ask Question 3: "What data or information does this workflow need to work with?"</action>
+    <action>Examples: "Customer data, order details, form responses, API data, etc."</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{data_requirements}}</action>
+
+    <action>Ask Question 4: "What should happen with this data? What's the desired outcome?"</action>
+    <action>Examples: "Send to Slack, update database, create invoice, notify team, etc."</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{desired_outcome}}</action>
+
+    <action>Ask Question 5: "What services or systems are involved?"</action>
+    <action>Examples: "Slack, Google Sheets, PostgreSQL, HubSpot, custom API, etc."</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{integrations}}</action>
+
+    <action>Ask Question 6: "Are there any conditions or decision points in this process?"</action>
+    <action>Examples: "If amount > $1000, notify manager; If status = 'urgent', send immediately"</action>
+    <action>Present numbered options:
+      1. No - Straight-through processing
+      2. Yes - Describe the conditions
+    </action>
+    <action>WAIT for user selection (1-2)</action>
+    <check if="selection is 2">
+      <action>Ask: "Describe the conditions and what should happen in each case"</action>
+      <action>WAIT for user input</action>
+      <action>Store in {{conditional_logic}}</action>
+    </check>
+
+    <action>Ask Question 7: "How critical is this workflow? What happens if it fails?"</action>
+    <action>Present numbered options:
+      1. Low - Can retry manually if needed
+      2. Medium - Should retry automatically, notify on failure
+      3. High - Must succeed, need alerts and logging
+      4. Critical - Business-critical, need comprehensive error handling
+    </action>
+    <action>WAIT for user selection (1-4)</action>
+    <action>Store selection in {{criticality}}</action>
+
+    <action>Ask Question 8: "What should the workflow be named?"</action>
+    <action>Suggest name based on {{problem_description}}</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{workflow_name}}</action>
+
+    <action>Ask Question 9: "Where should the workflow file be saved?"</action>
+    <action>Present numbered options:
+      1. Default location - workflows/[workflow-name].json
+      2. Custom path - Specify your own file path
+    </action>
+    <action>WAIT for user selection (1-2)</action>
+    <check if="selection is 2">
+      <action>Ask for specific path</action>
+      <action>WAIT for user input</action>
+    </check>
+    <action>Store final path in {{save_location}}</action>
+
+    <action>Summarize understanding:</action>
+    <action>- Problem: {{problem_description}}</action>
+    <action>- Trigger: {{trigger_type}}</action>
+    <action>- Data: {{data_requirements}}</action>
+    <action>- Outcome: {{desired_outcome}}</action>
+    <action>- Services: {{integrations}}</action>
+    <action>- Conditions: {{conditional_logic}}</action>
+    <action>- Criticality: {{criticality}}</action>
+
+    <action>Ask: "Does this capture your requirements correctly?"</action>
+    <action>Present numbered options:
+      1. Yes - Proceed with workflow creation
+      2. No - Let me clarify or add details
+    </action>
+    <action>WAIT for user selection (1-2)</action>
+    <check if="selection is 2">
+      <action>Ask: "What needs to be clarified or added?"</action>
+      <action>WAIT for user input</action>
+      <action>Update relevant variables</action>
+      <action>Repeat summary and confirmation</action>
+    </check>
+  </step>
+
+  <step n="2" goal="Research n8n Documentation">
+    <critical>Search for up-to-date n8n documentation based on user requirements</critical>
+
+    <action>Inform user: "Researching n8n documentation for your workflow requirements..."</action>
+
+    <action>Perform web search for n8n documentation on:</action>
+    <action>1. Trigger type: {{trigger_type}}</action>
+    <action>2. Integrations: {{integrations}}</action>
+    <action>3. Conditional logic: {{conditional_logic}}</action>
+    <action>4. Error handling: {{criticality}}</action>
+
+    <action>Search queries to use:</action>
+    <action>- "n8n [trigger_type] node documentation"</action>
+    <action>- "n8n [integration] node setup"</action>
+    <action>- "n8n workflow best practices"</action>
+    <action>- "n8n error handling retry logic"</action>
+
+    <action>Focus on official n8n documentation at docs.n8n.io</action>
+    <action>Store relevant documentation snippets for reference</action>
+    <action>Note any specific node configurations or parameters needed</action>
+  </step>
+
+  <step n="3" goal="Verify Documentation Understanding">
+    <action>Summarize key findings from documentation:</action>
+    <action>- Available node types for requirements</action>
+    <action>- Required parameters and configurations</action>
+    <action>- Best practices for this use case</action>
+    <action>- Any limitations or considerations</action>
+
+    <action>Inform user: "Based on n8n documentation, I found the necessary nodes and configurations for your workflow."</action>
+  </step>
+
+  <step n="4" goal="Plan Workflow Structure">
+    <critical>Design workflow based on the ACTUAL PROBLEM, not just technical specs</critical>
+
+    <action>Analyze the problem and requirements:</action>
+    <action>- Problem to solve: {{problem_description}}</action>
+    <action>- Trigger: {{trigger_type}}</action>
+    <action>- Data needed: {{data_requirements}}</action>
+    <action>- Desired outcome: {{desired_outcome}}</action>
+    <action>- Services: {{integrations}}</action>
+    <action>- Conditions: {{conditional_logic}}</action>
+    <action>- Criticality: {{criticality}}</action>
+
+    <action>Design workflow structure that solves the problem:</action>
+    <action>1. Map trigger to appropriate n8n trigger node</action>
+    <action>2. Design data acquisition steps (API calls, database queries)</action>
+    <action>3. Plan data transformations needed for the outcome</action>
+    <action>4. Implement conditional logic from {{conditional_logic}}</action>
+    <action>5. Design actions to achieve {{desired_outcome}}</action>
+    <action>6. Add error handling based on {{criticality}}</action>
+    <action>7. Plan node connections and data flow</action>
+
+    <action>Present the solution-focused workflow plan:</action>
+    <action>## Workflow Solution for: {{problem_description}}</action>
+    <action></action>
+    <action>**How it works:**</action>
+    <action>[Explain in plain language how the workflow solves the problem]</action>
+    <action></action>
+    <action>**Workflow Steps:**</action>
+    <action>1. Trigger: [When/how it starts] - [n8n node type]</action>
+    <action>2. Get Data: [What data is retrieved] - [n8n nodes]</action>
+    <action>3. Process: [How data is transformed] - [n8n nodes]</action>
+    <action>4. Decide: [Conditional logic if any] - [IF/Switch nodes]</action>
+    <action>5. Act: [Final actions to achieve outcome] - [n8n nodes]</action>
+    <action>6. Handle Errors: [Error strategy] - [Error handling config]</action>
+    <action></action>
+    <action>**Expected Result:**</action>
+    <action>[Describe what happens when workflow runs successfully]</action>
+
+    <action>Ask: "Does this workflow solve your problem?"</action>
+    <action>Present numbered options:
+      1. Yes - This solves my problem, proceed
+      2. No - Missing something important
+      3. Partially - Needs adjustments
+      4. Explain more - I need clarification
+    </action>
+    <action>WAIT for user selection (1-4)</action>
+
+    <check if="selection is 2">
+      <action>Ask: "What's missing? What else needs to happen?"</action>
+      <action>WAIT for user input</action>
+      <action>Adjust workflow design to include missing elements</action>
+      <action>Repeat this step</action>
+    </check>
+
+    <check if="selection is 3">
+      <action>Ask: "What needs to be adjusted?"</action>
+      <action>WAIT for user input</action>
+      <action>Modify workflow design based on feedback</action>
+      <action>Repeat this step</action>
+    </check>
+
+    <check if="selection is 4">
+      <action>Ask: "Which part needs clarification?"</action>
+      <action>WAIT for user input</action>
+      <action>Provide detailed explanation of that part</action>
+      <action>Repeat this step</action>
+    </check>
+  </step>
+
+  <step n="5" goal="Load Templates and Resources">
+    <action>Load {{templates}} file</action>
+    <action>Identify closest matching template based on workflow type</action>
+    <action>Load {{helpers}} for node creation guidelines</action>
+    <action>Extract relevant template sections</action>
+  </step>
+
+  <step n="6" goal="Build Workflow JSON">
+    <critical>Use EXACT node types and parameter structures from {{node_research}} and {{parameter_structures}}</critical>
+    <critical>Follow modern n8n format from {{helpers}}</critical>
+
+    <action>Initialize workflow structure with modern n8n format:</action>
+    <substep>
+      {
+        "name": "{{workflow_name}}",
+        "nodes": [],
+        "pinData": {},
+        "connections": {},
+        "active": false,
+        "settings": {
+          "executionOrder": "v1"
+        },
+        "versionId": "[generate UUID]",
+        "meta": {
+          "templateCredsSetupCompleted": true,
+          "instanceId": "[generate UUID]"
+        },
+        "id": "[generate short ID]",
+        "tags": []
+      }
+    </substep>
+
+    <action>Build nodes ONE at a time following these rules:</action>
+
+    <substep>For Each Node (Use EXACT structures from research):
+      1. Generate UUID for node ID (format: "f8b7ff4f-6375-4c79-9b2c-9814bfdd0c92")
+      2. Set node name (unique, descriptive)
+      3. Use EXACT node type from {{node_research}}:
+         - MUST be format: "n8n-nodes-base.nodeName"
+         - NEVER use: "@n8n/n8n-nodes-*" format
+         - Example: "n8n-nodes-base.gmail" NOT "@n8n/n8n-nodes-gmail.gmail"
+      4. Use EXACT typeVersion from {{node_research}}:
+         - MUST be INTEGER (2, 3, 4)
+         - NEVER use float (2.1, 3.4)
+      5. Calculate position as INTEGER array:
+         - Format: [x, y] where x and y are integers
+         - First node (trigger): [240, 300]
+         - Subsequent nodes: add 220 to x for each step
+         - Branches: adjust y by ±100
+      6. Use EXACT parameter structure from {{parameter_structures}}:
+         - For Set node (v3+): use assignments.assignments structure
+         - For Gmail node (v2+): use "message" parameter (NOT "text")
+         - For IF node (v2+): use conditions.conditions structure (NO "name" field in conditions)
+         - For Slack channel: use __rl flag with mode and cachedResultName
+         - Copy structure EXACTLY from research, don't modify
+      7. Add webhookId (UUID) if node type is webhook
+      8. Add credentials if needed
+      9. Field order: parameters, id, name, type, typeVersion, position, webhookId, credentials
+      10. Store node name in list for validation
+    </substep>
+
+    <substep>For Each Connection (CRITICAL FORMAT):
+      1. Identify source node name (must match node "name" field exactly)
+      2. Identify target node name (must match node "name" field exactly)
+      3. Create connection entry with CORRECT format:
+         "Source Node Name": {
+           "main": [
+             [
+               {
+                 "node": "Target Node Name",
+                 "type": "main",
+                 "index": 0
+               }
+             ]
+           ]
+         }
+      4. CRITICAL: The "main" wrapper object is REQUIRED
+      5. NEVER use format: "Source": [[{...}]] (missing "main" wrapper)
+      6. For IF nodes:
+         - index 0 = true branch
+         - index 1 = false branch
+      7. Validate all referenced nodes exist in node names list
+    </substep>
+
+    <substep>Node Building Order:
+      1. Trigger node
+      2. Main flow action nodes
+      3. Conditional nodes (IF/Switch)
+      4. Branch nodes
+      5. Merge nodes
+      6. Final action nodes
+      7. Connect all nodes
+    </substep>
+
+    <action>Apply error handling based on {{error_handling}} selection</action>
+    <action>Validate all node IDs are unique</action>
+    <action>Validate all node names are unique</action>
+    <action>Validate all connections reference existing nodes</action>
+  </step>
+
+  <step n="7" goal="Optimize and Save">
+    <action>Review workflow for optimization:</action>
+    <action>- Remove any unused nodes</action>
+    <action>- Verify node positions don't overlap</action>
+    <action>- Ensure proper spacing and alignment</action>
+    <action>- Validate all required parameters are set</action>
+
+    <action>Resolve final save path:</action>
+    <check if="{{save_location}} was provided by user">
+      <action>Use {{save_location}} as-is</action>
+    </check>
+    <check if="{{save_location}} is empty or default">
+      <action>Use {{workflows_folder}}/{{workflow_name}}.json</action>
+      <action>Ensure {{workflows_folder}} directory exists</action>
+      <action>Store resolved path in {{save_location}}</action>
+    </check>
+    <action>Save workflow to {{save_location}}</action>
+  </step>
+
+  <step n="8" goal="Validate JSON Syntax">
+    <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
+
+    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"</action>
+
+    <check if="validation fails (exit code 1)">
+      <action>Read the error message carefully - it shows the syntax error and position</action>
+      <action>Open the file and navigate to the error location</action>
+      <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
+      <action>Save the file</action>
+      <action>Re-run validation with the same command</action>
+      <action>Repeat until validation passes</action>
+    </check>
+
+    <action>Once validation passes, confirm with user: "n8n workflow created at {{save_location}}"</action>
+  </step>
+
+  <step n="9" goal="Provide Usage Instructions">
+    <action>Inform user how to use the workflow:</action>
+    <action>1. Import the JSON file into n8n</action>
+    <action>2. Configure credentials for integrated services</action>
+    <action>3. Test the workflow with sample data</action>
+    <action>4. Activate the workflow when ready</action>
+
+    <action>Ask: "Would you like me to explain any part of the workflow?"</action>
+    <action>Present numbered options:
+      1. No - I'm good to go
+      2. Yes - Explain specific nodes
+      3. Yes - Explain the overall flow
+      4. Yes - Explain how to test it
+    </action>
+    <action>WAIT for user selection (1-4)</action>
+
+    <check if="selection is 2, 3, or 4">
+      <action>Provide requested explanation</action>
+    </check>
+  </step>
+
+  <step n="10" goal="Validate Content">
+    <invoke-task>Validate against checklist at {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml</invoke-task>
+  </step>
+
+</workflow>
+```

src/modules/autominator/workflows/create-workflow/workflow.yaml

@@ -0,0 +1,43 @@
+name: create-workflow
+description: "Create new n8n workflow from scratch based on requirements"
+author: "Saif"
+
+# Critical variables from config
+config_source: "{project-root}/{bmad_folder}/autominator/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+workflows_folder: "{config_source}:workflows_folder"
+requirements_folder: "{config_source}:requirements_folder"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/autominator/workflows/create-workflow"
+shared_path: "{project-root}/{bmad_folder}/autominator/workflows/_shared"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Shared resources
+helpers: "{shared_path}/n8n-helpers.md"
+templates: "{shared_path}/n8n-templates.yaml"
+platform_mappings: "{shared_path}/platform-mappings.yaml"
+
+# Variables
+variables:
+  requirements_file: "" # Will be discovered or elicited
+  workflow_type: "" # Will be loaded from requirements or elicited
+  trigger_type: "" # Will be loaded from requirements or elicited
+  integrations: [] # Will be loaded from requirements or elicited
+  complexity: "" # Will be elicited
+  error_handling: "" # Will be elicited
+  workflow_name: "" # Will be loaded from requirements or elicited
+  problem_description: "" # Will be loaded from requirements
+  data_requirements: "" # Will be loaded from requirements
+  desired_outcome: "" # Will be loaded from requirements
+  conditional_logic: "" # Will be loaded from requirements
+  criticality: "" # Will be loaded from requirements
+
+default_output_file: "{workflows_folder}/{workflow_name}.json"
+
+standalone: true
+web_bundle: false

src/modules/autominator/workflows/gather-requirements/checklist.md

@@ -0,0 +1,25 @@
+# Gather Requirements - Validation Checklist
+
+## Requirements Completeness
+
+- [ ] Problem statement is clear and specific
+- [ ] Trigger type is defined
+- [ ] Data requirements are documented
+- [ ] Desired outcome is clear
+- [ ] All integrations are listed
+- [ ] Conditional logic is documented (or marked as not needed)
+- [ ] Criticality level is set
+- [ ] Workflow name is descriptive
+
+## Document Quality
+
+- [ ] Requirements file is saved to correct location
+- [ ] All template fields are filled
+- [ ] No placeholder text remains
+- [ ] Change log is initialized
+
+## Readiness
+
+- [ ] Requirements are sufficient to create workflow
+- [ ] User has confirmed requirements are correct
+- [ ] File is ready for use by create-workflow

src/modules/autominator/workflows/gather-requirements/instructions.md

@@ -0,0 +1,190 @@
+# Gather Requirements - Workflow Instructions
+
+```xml
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>This workflow gathers requirements for n8n workflow creation.</critical>
+
+<workflow>
+
+  <step n="1" goal="Load Config and Initialize">
+    <action>Resolve variables from config_source: requirements_folder, output_folder, user_name, communication_language</action>
+    <action>Create {{requirements_folder}} directory if it does not exist</action>
+    <action>Load template from {{template}}</action>
+  </step>
+
+  <step n="2" goal="Gather Requirements" elicit="true">
+    <critical>Ask questions ONE AT A TIME and WAIT for user response after each question</critical>
+
+    <ask>Question 1: What problem are you trying to solve with this automation?
+
+Describe the current manual process, pain points, and desired outcome.</ask>
+    <action>WAIT for user input</action>
+    <action>Store response in {{problem_description}}</action>
+
+    <action>Perform web search to understand the use case:</action>
+    <action>- "n8n workflow for [problem description] site:docs.n8n.io"</action>
+    <action>- "n8n automation [problem description] best practices"</action>
+    <action>Store findings in {{use_case_research}}</action>
+
+    <ask>Question 2: What triggers this process? When should the automation run?
+
+Options:
+1. When data arrives - Webhook, form submission, API call
+2. On a schedule - Every hour, daily, weekly, custom cron
+3. When something changes - Database update, file change, service event
+4. Manually - On-demand execution
+5. Multiple triggers - Combination of above
+6. Not sure - Help me decide based on my problem
+
+Enter your selection (1-6):</ask>
+    <action>WAIT for user input</action>
+    <action>Store response in {{trigger_type}}</action>
+
+    <check if="selection is 6">
+      <action>Analyze {{problem_description}} and suggest appropriate trigger</action>
+      <ask>Based on your problem, I recommend [trigger type]. Does this make sense? (yes/no)</ask>
+      <action>WAIT for confirmation</action>
+      <action>Store final trigger in {{trigger_type}}</action>
+    </check>
+
+    <ask>Question 3: What data or information does this workflow need to work with?
+
+Examples: Customer data, order details, form responses, API data, etc.</ask>
+    <action>WAIT for user input</action>
+    <action>Store response in {{data_requirements}}</action>
+
+    <ask>Question 4: What should happen with this data? What's the desired outcome?
+
+Examples: Send to Slack, update database, create invoice, notify team, etc.</ask>
+    <action>WAIT for user input</action>
+    <action>Store response in {{desired_outcome}}</action>
+
+    <ask>Question 5: What services or systems are involved?
+
+Examples: Slack, Google Sheets, PostgreSQL, HubSpot, custom API, etc.</ask>
+    <action>WAIT for user input</action>
+    <action>Store response in {{integrations}}</action>
+
+    <action>Research EXACT n8n node types for each integration:</action>
+    <action>For each service in {{integrations}}:</action>
+    <action>1. Search: "n8n [service] node documentation site:docs.n8n.io"</action>
+    <action>2. Extract EXACT node type string (e.g., "n8n-nodes-base.webhook")</action>
+    <action>3. Extract typeVersion (e.g., 2.1)</action>
+    <action>4. Extract available parameters structure</action>
+    <action>5. Extract example usage from docs</action>
+    <action>6. Note if trigger node or action node</action>
+    <action>Store all findings in {{node_research}}</action>
+
+    <ask>Question 6: Are there any conditions or decision points in this process?
+
+Examples: If amount > $1000, notify manager; If status = 'urgent', send immediately
+
+Options:
+1. No - Straight-through processing
+2. Yes - Describe the conditions
+
+Enter your selection (1-2):</ask>
+    <action>WAIT for user input</action>
+    <check if="selection is 2">
+      <ask>Describe the conditions and what should happen in each case:</ask>
+      <action>WAIT for user input</action>
+      <action>Store response in {{conditional_logic}}</action>
+    </check>
+    <check if="selection is 1">
+      <action>Store "No conditional logic required" in {{conditional_logic}}</action>
+    </check>
+
+    <ask>Question 7: How critical is this workflow? What happens if it fails?
+
+Options:
+1. Low - Can retry manually if needed
+2. Medium - Should retry automatically, notify on failure
+3. High - Must succeed, need alerts and logging
+4. Critical - Business-critical, need comprehensive error handling
+
+Enter your selection (1-4):</ask>
+    <action>WAIT for user input</action>
+    <action>Store selection in {{criticality}}</action>
+
+    <ask>Question 8: What should the workflow be named?</ask>
+    <action>WAIT for user input</action>
+    <action>Store response in {{workflow_name}}</action>
+    <action>Generate {{workflow_slug}} from {{workflow_name}} (lowercase, hyphens, no spaces)</action>
+
+    <action>Display summary:
+- Problem: {{problem_description}}
+- Trigger: {{trigger_type}}
+- Data: {{data_requirements}}
+- Outcome: {{desired_outcome}}
+- Services: {{integrations}}
+- Conditions: {{conditional_logic}}
+- Criticality: {{criticality}}
+- Name: {{workflow_name}}
+    </action>
+
+    <ask>Does this capture your requirements correctly?
+
+Options:
+1. Yes - Save requirements
+2. No - Let me clarify or add details
+
+Enter your selection (1-2):</ask>
+    <action>WAIT for user input</action>
+    <check if="selection is 2">
+      <ask>What needs to be clarified or added?</ask>
+      <action>WAIT for user input</action>
+      <action>Update relevant variables based on feedback</action>
+      <action>Repeat summary and confirmation</action>
+    </check>
+  </step>
+
+  <step n="3" goal="Research Workflow Pattern">
+    <action>Perform comprehensive web search for workflow pattern:</action>
+    <action>- "n8n workflow pattern [trigger_type] to [desired_outcome] site:docs.n8n.io"</action>
+    <action>- "n8n [integrations] workflow example site:docs.n8n.io"</action>
+    <action>- "n8n best practices [use case] site:docs.n8n.io"</action>
+    <action>Store findings in {{workflow_pattern_research}}</action>
+
+    <action>Research parameter structures for each node type:</action>
+    <action>For each node type in {{node_research}}:</action>
+    <action>1. Search: "n8n [node type] parameters documentation site:docs.n8n.io"</action>
+    <action>2. Extract EXACT parameter structure from docs</action>
+    <action>3. Extract required vs optional parameters</action>
+    <action>4. Extract parameter data types</action>
+    <action>5. Extract example values</action>
+    <action>Store in {{parameter_structures}}</action>
+  </step>
+
+  <step n="4" goal="Save Requirements Document">
+    <action>Resolve output path: {{default_output_file}} using {{workflow_slug}}</action>
+    <action>Fill template with all gathered variables AND research findings</action>
+    <action>Include in document:</action>
+    <action>- Problem description and requirements</action>
+    <action>- Use case research findings</action>
+    <action>- EXACT node types with typeVersions</action>
+    <action>- EXACT parameter structures from docs</action>
+    <action>- Workflow pattern recommendations</action>
+    <action>- Best practices from research</action>
+    <action>Save document to {{default_output_file}}</action>
+    <action>Report saved file path to user</action>
+
+    <output>✅ Requirements Saved Successfully!
+
+**File:** {{default_output_file}}
+
+**Next Steps:**
+1. Review the requirements file
+2. Run `*create-workflow` to generate the n8n workflow
+   (The create-workflow will automatically load this requirements file)
+
+**Note:** You can edit the requirements file manually before creating the workflow.
+    </output>
+  </step>
+
+  <step n="5" goal="Validate Content">
+    <invoke-task>Validate against checklist at {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml</invoke-task>
+  </step>
+
+</workflow>
+```

src/modules/autominator/workflows/gather-requirements/template.md

@@ -0,0 +1,75 @@
+# Workflow Requirements: {{workflow_name}}
+
+**Created:** {{date}}  
+**Status:** Requirements Gathered  
+**Criticality:** {{criticality}}
+
+---
+
+## Problem Statement
+
+{{problem_description}}
+
+---
+
+## Workflow Overview
+
+**Trigger:** {{trigger_type}}
+
+**Desired Outcome:** {{desired_outcome}}
+
+---
+
+## Data Requirements
+
+{{data_requirements}}
+
+---
+
+## Integrations
+
+{{integrations}}
+
+---
+
+## Conditional Logic
+
+{{conditional_logic}}
+
+---
+
+## Research Findings
+
+### Use Case Research
+
+{{use_case_research}}
+
+### Node Types (From n8n Documentation)
+
+{{node_research}}
+
+### Parameter Structures (From n8n Documentation)
+
+{{parameter_structures}}
+
+### Workflow Pattern Recommendations
+
+{{workflow_pattern_research}}
+
+---
+
+## Technical Notes
+
+- Requirements gathered: {{date}}
+- Research completed from n8n documentation
+- All node types and parameters verified from docs.n8n.io
+- Ready for workflow creation
+- Use this file as input for `*create-workflow`
+
+---
+
+## Change Log
+
+| Date     | Change                        | Author        |
+| -------- | ----------------------------- | ------------- |
+| {{date}} | Initial requirements gathered | {{user_name}} |

src/modules/autominator/workflows/gather-requirements/workflow.yaml

@@ -0,0 +1,34 @@
+name: gather-requirements
+description: "Gather and document workflow requirements before creating n8n workflow"
+author: "Saif"
+
+# Critical variables from config
+config_source: "{project-root}/{bmad_folder}/autominator/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+requirements_folder: "{config_source}:requirements_folder"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/autominator/workflows/gather-requirements"
+template: "{installed_path}/template.md"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Variables
+variables:
+  workflow_name: "" # Will be elicited
+  workflow_slug: "" # Generated from workflow_name
+  problem_description: "" # Will be elicited
+  trigger_type: "" # Will be elicited
+  data_requirements: "" # Will be elicited
+  desired_outcome: "" # Will be elicited
+  integrations: "" # Will be elicited
+  conditional_logic: "" # Will be elicited
+  criticality: "" # Will be elicited
+
+default_output_file: "{requirements_folder}/req-{workflow_slug}.md"
+
+standalone: true
+web_bundle: false

src/modules/autominator/workflows/migrate-workflow/checklist.md

@@ -0,0 +1,110 @@
+# Migrate Workflow to n8n - Validation Checklist
+
+## Source Analysis
+
+- [ ] Source platform was identified
+- [ ] Source workflow details were gathered
+- [ ] Trigger type was identified
+- [ ] All integrations were identified
+- [ ] Workflow complexity was assessed
+
+## Platform Mapping
+
+- [ ] Platform mappings were loaded
+- [ ] Source trigger was mapped to n8n trigger
+- [ ] All source actions were mapped to n8n nodes
+- [ ] Conditional logic was mapped correctly
+- [ ] Loops/iterations were mapped correctly
+- [ ] Data transformations were identified
+
+## Workflow Structure
+
+- [ ] n8n workflow has valid JSON structure
+- [ ] Workflow name is set
+- [ ] Migration tag is added (migrated-from-[platform])
+- [ ] All nodes have unique IDs
+- [ ] All nodes have unique names
+- [ ] Trigger node is properly configured
+
+## Node Configuration
+
+- [ ] All mapped nodes are created
+- [ ] Node types are valid n8n types
+- [ ] Node parameters are configured
+- [ ] Credentials placeholders are set
+- [ ] Node positions are calculated correctly
+- [ ] No overlapping nodes
+
+## Data Mappings
+
+- [ ] Field mappings from source to n8n are correct
+- [ ] Data type conversions are handled
+- [ ] Date/time format differences are addressed
+- [ ] Expressions use correct n8n syntax (={{ }})
+- [ ] Set nodes are used for simple transformations
+- [ ] Code nodes are used for complex transformations
+
+## Conditional Logic
+
+- [ ] IF nodes are created for conditional branches
+- [ ] Switch nodes are created for multiple conditions
+- [ ] Conditions are properly configured
+- [ ] True/false branches are correct (index 0/1)
+- [ ] All branches are connected
+
+## Connections
+
+- [ ] All nodes are connected properly
+- [ ] Trigger connects to first action
+- [ ] Actions are connected in sequence
+- [ ] Conditional branches are connected
+- [ ] Merge points are connected
+- [ ] All connections reference existing nodes
+- [ ] No orphaned nodes (except trigger)
+
+## Error Handling
+
+- [ ] Error handling strategy is defined
+- [ ] Critical nodes have retry logic if needed
+- [ ] continueOnFail is set appropriately
+- [ ] Error handling matches or improves on source
+
+## Migration Notes
+
+- [ ] Source platform is documented
+- [ ] Migration date is recorded
+- [ ] Credentials needed are listed
+- [ ] Platform-specific differences are noted
+- [ ] Testing considerations are documented
+
+## Validation
+
+- [ ] Workflow passes JSON validation
+- [ ] All required parameters are set
+- [ ] Workflow structure is logical
+- [ ] Migration matches source workflow functionality
+
+## Credentials & Authentication
+
+- [ ] All services requiring credentials are identified
+- [ ] Credential types are correct for n8n
+- [ ] OAuth requirements are noted
+- [ ] API key requirements are noted
+- [ ] Authentication differences from source are documented
+
+## Testing Readiness
+
+- [ ] Workflow can be imported into n8n
+- [ ] Test data requirements are clear
+- [ ] Expected outputs are defined
+- [ ] Comparison approach with source is defined
+- [ ] Initial monitoring plan is suggested
+
+## Documentation
+
+- [ ] User has import instructions
+- [ ] Credential setup guidance provided
+- [ ] Data mapping explanations provided
+- [ ] Testing approach explained
+- [ ] Platform differences highlighted
+- [ ] Post-migration checklist provided

src/modules/autominator/workflows/migrate-workflow/instructions.md

@@ -0,0 +1,354 @@
+# Migrate Workflow to n8n - Workflow Instructions
+
+```xml
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>This workflow migrates automation workflows from other platforms to n8n.</critical>
+
+<workflow>
+
+  <step n="0" goal="Contextual Analysis (Smart Elicitation)">
+    <critical>Before asking any questions, analyze what the user has already told you</critical>
+
+    <action>Review the user's initial request and conversation history</action>
+    <action>Extract any mentioned: source platform, workflow details, integrations, file paths</action>
+
+    <check if="ALL requirements are clear from context">
+      <action>Summarize your understanding</action>
+      <action>Skip directly to Step 2 (Research n8n Documentation for Migration)</action>
+    </check>
+
+    <check if="SOME requirements are clear">
+      <action>Note what you already know</action>
+      <action>Only ask about missing information in Step 1</action>
+    </check>
+
+    <check if="requirements are unclear or minimal">
+      <action>Proceed with full elicitation in Step 1</action>
+    </check>
+  </step>
+
+  <step n="1" goal="Gather Migration Requirements" elicit="true">
+    <critical>Understand the BUSINESS PURPOSE of the workflow being migrated, not just technical details</critical>
+
+    <action>Ask Question 1: "What does this workflow do? What problem does it solve?"</action>
+    <action>Encourage business context: "Describe the business process, not just the technical steps"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{business_purpose}}</action>
+
+    <action>Ask Question 2: "Which platform are you migrating from?"</action>
+    <action>Present numbered options:
+      1. Zapier - Migrate Zapier Zaps to n8n
+      2. Make (Integromat) - Migrate Make scenarios to n8n
+      3. HubSpot Workflows - Migrate HubSpot workflows to n8n
+      4. Microsoft Power Automate - Migrate Power Automate flows to n8n
+      5. IFTTT - Migrate IFTTT applets to n8n
+      6. Other - Specify another automation platform
+    </action>
+    <action>WAIT for user selection (1-6)</action>
+    <action>Store selection in {{source_platform}}</action>
+
+    <check if="selection is 6 (Other)">
+      <action>Ask: "Please specify the platform you're migrating from"</action>
+      <action>WAIT for user input</action>
+      <action>Store in {{source_platform}}</action>
+    </check>
+
+    <action>Ask Question 3: "Why are you migrating to n8n?"</action>
+    <action>Examples: "Cost savings", "More flexibility", "Self-hosting", "Better integrations"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{migration_reason}}</action>
+
+    <action>Ask Question 4: "How will you provide the workflow details?"</action>
+    <action>Present numbered options:
+      1. Describe the process - Explain what happens step by step
+      2. Provide export file - Upload/paste workflow export file
+      3. Provide screenshots - Share workflow screenshots
+      4. Combination - Multiple sources
+    </action>
+    <action>WAIT for user selection (1-4)</action>
+
+    <check if="selection is 1 or 4">
+      <action>Ask: "Describe the workflow step by step:"</action>
+      <action>- What triggers it?</action>
+      <action>- What data does it process?</action>
+      <action>- What actions does it take?</action>
+      <action>- What's the final outcome?</action>
+      <action>WAIT for user input</action>
+      <action>Store in {{workflow_description}}</action>
+    </check>
+
+    <check if="selection is 2 or 4">
+      <action>Ask: "Please provide the workflow export file path or paste the content"</action>
+      <action>WAIT for user input</action>
+      <action>Store in {{workflow_file}} or {{workflow_content}}</action>
+    </check>
+
+    <check if="selection is 3 or 4">
+      <action>Ask: "Please share the workflow screenshots and describe what each part does"</action>
+      <action>WAIT for user input</action>
+      <action>Store in {{workflow_screenshots}}</action>
+    </check>
+
+    <action>Ask Question 5: "What services/integrations does this workflow connect to?"</action>
+    <action>Ask: "List all services (e.g., Slack, Google Sheets, HubSpot, custom APIs, etc.)"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{integrations_used}}</action>
+
+    <action>Ask Question 6: "Are there any pain points or issues with the current workflow?"</action>
+    <action>Examples: "Slow execution", "Unreliable", "Missing features", "Hard to maintain"</action>
+    <action>Present numbered options:
+      1. No - Works fine, just migrating platform
+      2. Yes - Describe the issues
+    </action>
+    <action>WAIT for user selection (1-2)</action>
+    <check if="selection is 2">
+      <action>Ask: "What issues should we fix during migration?"</action>
+      <action>WAIT for user input</action>
+      <action>Store in {{issues_to_fix}}</action>
+    </check>
+
+    <action>Ask Question 6: "What should the migrated workflow be named?"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{workflow_name}}</action>
+
+    <action>Ask Question 7: "Where should the n8n workflow file be saved?"</action>
+    <action>Present numbered options:
+      1. Default location - workflows/[workflow-name].json
+      2. Custom path - Specify your own file path
+      3. Project root - Save in main project directory
+    </action>
+    <action>WAIT for user selection (1-3)</action>
+    <check if="selection is 2">
+      <action>Ask for specific path</action>
+      <action>WAIT for user input</action>
+    </check>
+    <action>Store final path in {{save_location}}</action>
+  </step>
+
+  <step n="2" goal="Research n8n Documentation for Migration">
+    <critical>Search for n8n documentation relevant to migration requirements</critical>
+
+    <action>Inform user: "Researching n8n documentation for migration from {{source_platform}}..."</action>
+
+    <action>Perform web search for:</action>
+    <action>1. n8n equivalents for {{source_platform}} features</action>
+    <action>2. Integration nodes: {{integrations_used}}</action>
+    <action>3. Migration best practices</action>
+    <action>4. Platform-specific considerations</action>
+
+    <action>Search queries to use:</action>
+    <action>- "n8n migrate from [source_platform]"</action>
+    <action>- "n8n [integration] node documentation"</action>
+    <action>- "n8n vs [source_platform] comparison"</action>
+    <action>- "n8n workflow migration guide"</action>
+
+    <action>Focus on official n8n documentation at docs.n8n.io</action>
+    <action>Store relevant migration patterns and node configurations</action>
+  </step>
+
+  <step n="3" goal="Verify Migration Approach">
+    <action>Summarize migration strategy based on documentation:</action>
+    <action>- n8n equivalents for {{source_platform}} features</action>
+    <action>- Required node types and configurations</action>
+    <action>- Data transformation needs</action>
+    <action>- Any migration challenges or limitations</action>
+
+    <action>Inform user: "Based on n8n documentation, I've identified the migration path from {{source_platform}}."</action>
+  </step>
+
+  <step n="4" goal="Load Platform Mappings">
+    <action>Load {{platform_mappings}} file</action>
+    <action>Extract mappings for {{source_platform}}</action>
+    <action>Identify equivalent n8n nodes for source platform components</action>
+  </step>
+
+  <step n="5" goal="Analyze Source Workflow">
+    <check if="{{workflow_file}} or {{workflow_content}} provided">
+      <action>Parse source workflow file/content</action>
+      <action>Extract workflow structure</action>
+    </check>
+
+    <action>Analyze workflow based on description and details:</action>
+    <action>1. Identify trigger type and configuration</action>
+    <action>2. List all actions/steps in order</action>
+    <action>3. Identify conditional logic (if/then branches)</action>
+    <action>4. Identify loops or iterations</action>
+    <action>5. Identify data transformations</action>
+    <action>6. Identify error handling</action>
+    <action>7. Map integrations to n8n nodes</action>
+
+    <action>Present analysis to user:</action>
+    <action>- Source trigger: [platform-specific trigger]</action>
+    <action>- n8n trigger: [mapped n8n node]</action>
+    <action>- Source actions: [list with platform names]</action>
+    <action>- n8n actions: [list with n8n node types]</action>
+    <action>- Logic: [conditional branches, loops]</action>
+    <action>- Transformations: [data mapping needs]</action>
+  </step>
+
+  <step n="6" goal="Plan n8n Workflow Structure">
+    <action>Load {{helpers}} for node creation guidelines</action>
+    <action>Load {{templates}} for reference</action>
+
+    <action>Design n8n workflow structure:</action>
+    <action>1. Map source trigger to n8n trigger node</action>
+    <action>2. Map each source action to n8n node(s)</action>
+    <action>3. Convert conditional logic to IF/Switch nodes</action>
+    <action>4. Convert loops to Split In Batches nodes</action>
+    <action>5. Add Set/Code nodes for data transformations</action>
+    <action>6. Plan node connections</action>
+    <action>7. Add error handling where needed</action>
+
+    <action>Present migration plan to user:</action>
+    <action>- n8n Trigger: [node type and configuration]</action>
+    <action>- n8n Nodes: [list with descriptions]</action>
+    <action>- Connections: [flow diagram]</action>
+    <action>- Data Mappings: [field mappings]</action>
+    <action>- Credentials Needed: [list of integrations requiring auth]</action>
+
+    <action>Ask: "Does this migration plan look correct?"</action>
+    <action>Present numbered options:
+      1. Yes - Proceed with migration
+      2. No - Adjust the plan
+      3. Add more details - Provide additional information
+    </action>
+    <action>WAIT for user selection (1-3)</action>
+
+    <check if="selection is 2 or 3">
+      <action>Ask: "What changes or additions are needed?"</action>
+      <action>WAIT for user input</action>
+      <action>Adjust plan based on feedback</action>
+      <action>Repeat this step</action>
+    </check>
+  </step>
+
+  <step n="7" goal="Build n8n Workflow">
+    <critical>Follow guidelines from {{helpers}} for proper node creation</critical>
+
+    <action>Initialize workflow structure:</action>
+    <substep>
+      {
+        "name": "{{workflow_name}}",
+        "nodes": [],
+        "connections": {},
+        "active": false,
+        "settings": {
+          "executionOrder": "v1"
+        },
+        "tags": [
+          {
+            "name": "migrated-from-{{source_platform}}"
+          }
+        ]
+      }
+    </substep>
+
+    <action>Build nodes ONE at a time:</action>
+
+    <substep>For Each Mapped Node:
+      1. Generate unique node ID
+      2. Set node name (descriptive, unique)
+      3. Set node type from platform mappings
+      4. Set typeVersion (usually 1)
+      5. Calculate position (220px spacing)
+      6. Configure parameters based on source workflow
+      7. Map data fields from source to n8n format
+      8. Add credentials placeholder if needed
+      9. Set error handling if required
+    </substep>
+
+    <substep>For Data Transformations:
+      1. Identify field mappings needed
+      2. Create Set nodes for simple mappings
+      3. Create Code nodes for complex transformations
+      4. Use n8n expressions: ={{ $json.fieldName }}
+      5. Handle data type conversions
+      6. Handle date/time format differences
+    </substep>
+
+    <substep>For Conditional Logic:
+      1. Create IF nodes for if/then branches
+      2. Create Switch nodes for multiple conditions
+      3. Map source conditions to n8n condition format
+      4. Set up true/false branches (index 0/1)
+    </substep>
+
+    <substep>For Connections:
+      1. Connect trigger to first action
+      2. Connect actions in sequence
+      3. Connect conditional branches
+      4. Connect merge points
+      5. Validate all connections
+    </substep>
+
+    <action>Add migration notes as workflow tags</action>
+    <action>Validate all node IDs are unique</action>
+    <action>Validate all connections reference existing nodes</action>
+  </step>
+
+  <step n="8" goal="Add Migration Notes">
+    <action>Add comment nodes or documentation:</action>
+    <action>- Source platform: {{source_platform}}</action>
+    <action>- Migration date: {timestamp}</action>
+    <action>- Credentials to configure: [list]</action>
+    <action>- Testing notes: [important considerations]</action>
+    <action>- Platform-specific differences: [notes]</action>
+  </step>
+
+  <step n="9" goal="Save Migrated Workflow">
+    <action>Save workflow to {{save_location}}</action>
+  </step>
+
+  <step n="10" goal="Validate JSON Syntax">
+    <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
+
+    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"</action>
+
+    <check if="validation fails (exit code 1)">
+      <action>Read the error message carefully - it shows the syntax error and position</action>
+      <action>Open the file and navigate to the error location</action>
+      <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
+      <action>Save the file</action>
+      <action>Re-run validation with the same command</action>
+      <action>Repeat until validation passes</action>
+    </check>
+
+    <action>Once validation passes, confirm with user: "Workflow migrated successfully to {{save_location}}"</action>
+  </step>
+
+  <step n="11" goal="Provide Migration Guidance">
+    <action>Provide post-migration instructions:</action>
+    <action>1. Import the JSON file into n8n</action>
+    <action>2. Configure credentials for these services: [list]</action>
+    <action>3. Review and update these data mappings: [list]</action>
+    <action>4. Test with sample data before activating</action>
+    <action>5. Compare outputs with original platform</action>
+    <action>6. Monitor initial executions closely</action>
+
+    <action>Highlight platform-specific differences:</action>
+    <action>- Authentication: [differences]</action>
+    <action>- Data formats: [differences]</action>
+    <action>- Scheduling: [differences]</action>
+    <action>- Error handling: [differences]</action>
+
+    <action>Ask: "Would you like help with any specific part of the migration?"</action>
+    <action>Present numbered options:
+      1. No - I'm ready to test
+      2. Yes - Explain credential setup
+      3. Yes - Explain data mappings
+      4. Yes - Explain testing approach
+    </action>
+    <action>WAIT for user selection (1-4)</action>
+
+    <check if="selection is 2, 3, or 4">
+      <action>Provide requested explanation</action>
+    </check>
+  </step>
+
+  <step n="12" goal="Validate Content">
+    <invoke-task>Validate against checklist at {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml</invoke-task>
+  </step>
+
+</workflow>
+```

src/modules/autominator/workflows/migrate-workflow/workflow.yaml

@@ -0,0 +1,31 @@
+name: migrate-workflow
+description: "Migrate workflows from other platforms (Zapier, Make, HubSpot, etc.) to n8n"
+author: "Saif"
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/autominator/workflows/migrate-workflow"
+shared_path: "{project-root}/{bmad_folder}/autominator/workflows/_shared"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Shared resources
+helpers: "{shared_path}/n8n-helpers.md"
+templates: "{shared_path}/n8n-templates.yaml"
+platform_mappings: "{shared_path}/platform-mappings.yaml"
+
+# Variables
+variables:
+  source_platform: "" # Will be elicited
+  workflow_description: "" # Will be elicited
+  workflow_file: "" # Will be elicited (optional)
+  workflow_content: "" # Will be elicited (optional)
+  integrations_used: [] # Will be elicited
+  trigger_type: "" # Will be elicited
+  complexity: "" # Will be elicited
+  save_location: "" # Will be elicited
+  workflow_name: "" # Will be elicited
+
+default_output_file: "{project-root}/workflows/migrated-workflow-{timestamp}.json"
+
+standalone: true
+web_bundle: false

src/modules/autominator/workflows/modify-workflow/checklist.md

@@ -0,0 +1,90 @@
+# Modify n8n Workflow - Validation Checklist
+
+## Pre-Modification
+
+- [ ] Original workflow file was successfully loaded
+- [ ] Workflow JSON was valid before modifications
+- [ ] Backup was created before making changes
+- [ ] User requirements were clearly understood
+
+## Workflow Structure
+
+- [ ] Workflow maintains valid JSON structure
+- [ ] Workflow name is preserved (unless intentionally changed)
+- [ ] All nodes still have unique IDs
+- [ ] All nodes still have unique names
+- [ ] Workflow settings are preserved
+
+## Node Modifications
+
+- [ ] Added nodes have unique IDs
+- [ ] Added nodes have unique names
+- [ ] Added nodes have valid node types
+- [ ] Added nodes have required parameters set
+- [ ] Modified nodes preserve their IDs
+- [ ] Modified nodes have valid parameter values
+- [ ] Removed nodes are completely removed from nodes array
+
+## Connections
+
+- [ ] All connections reference existing nodes
+- [ ] Connections to/from added nodes are properly configured
+- [ ] Connections affected by removed nodes are updated
+- [ ] No orphaned connections remain
+- [ ] Connection indices are correct (0 for default, 0/1 for IF nodes)
+- [ ] No circular dependencies (unless intentional)
+
+## Node Positioning
+
+- [ ] New nodes have valid positions
+- [ ] New nodes don't overlap with existing nodes
+- [ ] Node positions follow spacing guidelines (220px horizontal)
+- [ ] Branch nodes have appropriate vertical spacing (±100px)
+
+## Error Handling
+
+- [ ] Error handling modifications are applied correctly
+- [ ] Retry logic is properly configured if added
+- [ ] continueOnFail settings are appropriate
+- [ ] maxTries and waitBetweenTries are set if retries enabled
+
+## Data Flow
+
+- [ ] Data flow is maintained after modifications
+- [ ] New transformations are properly configured
+- [ ] Expressions use correct n8n syntax (={{ }})
+- [ ] No data flow breaks introduced
+
+## Integration Changes
+
+- [ ] New integrations are properly configured
+- [ ] Credential requirements are identified
+- [ ] API configurations are correct
+- [ ] Existing integrations still work
+
+## Validation
+
+- [ ] Modified workflow passes JSON validation
+- [ ] All modifications match user requirements
+- [ ] No unintended changes were made
+- [ ] Workflow structure is still logical
+
+## Backup & Recovery
+
+- [ ] Backup file was created successfully
+- [ ] Backup location was communicated to user
+- [ ] Original workflow can be restored if needed
+
+## Testing Readiness
+
+- [ ] Modified workflow can be imported into n8n
+- [ ] Changes are testable
+- [ ] Expected behavior is clear
+- [ ] Any new credentials needed are identified
+
+## Documentation
+
+- [ ] Changes made are summarized for user
+- [ ] User understands what was modified
+- [ ] Testing recommendations provided if needed
+- [ ] Backup location shared with user

src/modules/autominator/workflows/modify-workflow/instructions.md

@@ -0,0 +1,336 @@
+# Modify n8n Workflow - Workflow Instructions
+
+```xml
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>This workflow modifies an existing n8n workflow based on user requirements.</critical>
+
+<workflow>
+
+  <step n="0" goal="Contextual Analysis (Smart Elicitation)">
+    <critical>Before asking any questions, analyze what the user has already told you</critical>
+
+    <action>Review the user's initial request and conversation history</action>
+    <action>Extract any mentioned: workflow file path, changes needed, specific nodes</action>
+
+    <check if="ALL requirements are clear from context">
+      <action>Summarize your understanding</action>
+      <action>Skip directly to Step 2 (Load Existing Workflow)</action>
+    </check>
+
+    <check if="SOME requirements are clear">
+      <action>Note what you already know</action>
+      <action>Only ask about missing information in Step 1</action>
+    </check>
+
+    <check if="requirements are unclear or minimal">
+      <action>Proceed with full elicitation in Step 1</action>
+    </check>
+  </step>
+
+  <step n="1" goal="Gather Requirements" elicit="true">
+    <critical>Understand WHY the user wants to modify the workflow, not just WHAT to change</critical>
+
+    <action>Ask Question 1: "Which workflow file do you want to modify?"</action>
+    <action>Present numbered options:
+      1. Provide file path - Specify exact path to workflow JSON
+      2. Search in workflows folder - List available workflows
+      3. Paste workflow JSON - Provide workflow content directly
+    </action>
+    <action>WAIT for user selection (1-3)</action>
+
+    <check if="selection is 1">
+      <action>Ask: "Please provide the file path to the workflow JSON"</action>
+      <action>WAIT for user input</action>
+      <action>Store in {{workflow_file}}</action>
+    </check>
+
+    <check if="selection is 2">
+      <action>List all .json files in workflows/ directory</action>
+      <action>Present as numbered list</action>
+      <action>WAIT for user selection</action>
+      <action>Store selected file path in {{workflow_file}}</action>
+    </check>
+
+    <check if="selection is 3">
+      <action>Ask: "Please paste the workflow JSON content"</action>
+      <action>WAIT for user input</action>
+      <action>Create temporary file with content</action>
+      <action>Store temp file path in {{workflow_file}}</action>
+    </check>
+
+    <action>Ask Question 2: "What problem are you trying to solve by modifying this workflow?"</action>
+    <action>Examples: "It's not handling errors properly", "Need to add Slack notifications", "Missing data validation"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{problem_to_solve}}</action>
+
+    <action>Ask Question 3: "What's currently not working or missing?"</action>
+    <action>Encourage specific details about the issue or gap</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{current_issue}}</action>
+
+    <action>Ask Question 4: "What should the workflow do after these changes?"</action>
+    <action>Focus on the desired behavior and outcome</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{desired_behavior}}</action>
+
+    <action>Ask Question 5: "Are there any specific nodes, integrations, or logic you want to change?"</action>
+    <action>Examples: "Add a Slack node after approval", "Change the IF condition to check status", "Remove the delay node"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{specific_changes}}</action>
+
+    <action>Summarize understanding:</action>
+    <action>- Problem: {{problem_to_solve}}</action>
+    <action>- Current Issue: {{current_issue}}</action>
+    <action>- Desired Behavior: {{desired_behavior}}</action>
+    <action>- Specific Changes: {{specific_changes}}</action>
+
+    <action>Ask: "Does this capture what you need?"</action>
+    <action>Present numbered options:
+      1. Yes - Proceed with modifications
+      2. No - Let me clarify
+    </action>
+    <action>WAIT for user selection (1-2)</action>
+    <check if="selection is 2">
+      <action>Ask: "What needs clarification?"</action>
+      <action>WAIT for user input</action>
+      <action>Update relevant variables</action>
+      <action>Repeat summary and confirmation</action>
+    </check>
+  </step>
+
+  <step n="2" goal="Load Existing Workflow">
+    <critical>Only load the workflow file when user provides it - never preload</critical>
+
+    <action>Read workflow file from {{workflow_file}}</action>
+    <action>Parse JSON content</action>
+    <action>Validate JSON structure</action>
+
+    <check if="JSON is invalid">
+      <action>Inform user: "The workflow file has invalid JSON syntax"</action>
+      <action>Show error details</action>
+      <action>Ask: "Would you like me to fix the JSON syntax first? (yes/no)"</action>
+      <action>WAIT for user response</action>
+
+      <check if="user says yes">
+        <action>Fix JSON syntax errors</action>
+        <action>Save corrected file</action>
+        <action>Proceed with loading</action>
+      </check>
+
+      <check if="user says no">
+        <action>Exit workflow with error</action>
+      </check>
+    </check>
+
+    <action>Extract workflow structure:</action>
+    <action>- Workflow name</action>
+    <action>- List of nodes (names, types, IDs)</action>
+    <action>- Connections map</action>
+    <action>- Current settings</action>
+
+    <action>Display workflow summary to user:</action>
+    <action>- Name: [workflow name]</action>
+    <action>- Nodes: [count] nodes</action>
+    <action>- Node list: [node names and types]</action>
+    <action>- Connections: [connection count]</action>
+  </step>
+
+  <step n="3" goal="Create Backup">
+    <action>Create backup of original workflow</action>
+    <action>Save backup to: {{workflow_file}}.backup-{timestamp}</action>
+    <action>Store true in {{backup_created}}</action>
+    <action>Inform user: "Backup created at {{workflow_file}}.backup-{timestamp}"</action>
+  </step>
+
+  <step n="4" goal="Research n8n Documentation for Modifications">
+    <critical>Search for n8n documentation relevant to the modifications needed</critical>
+
+    <action>Inform user: "Researching n8n documentation for your modifications..."</action>
+
+    <action>Perform web search based on modification needs:</action>
+    <action>- Problem to solve: {{problem_to_solve}}</action>
+    <action>- Specific changes: {{specific_changes}}</action>
+    <action>- Desired behavior: {{desired_behavior}}</action>
+
+    <action>Search queries to use:</action>
+    <action>- "n8n [specific feature] documentation"</action>
+    <action>- "n8n [node type] configuration"</action>
+    <action>- "n8n workflow modification best practices"</action>
+    <action>- "n8n [integration] setup"</action>
+
+    <action>Focus on official n8n documentation at docs.n8n.io</action>
+    <action>Store relevant node configurations and modification patterns</action>
+  </step>
+
+  <step n="5" goal="Verify Modification Approach">
+    <action>Summarize modification strategy based on documentation:</action>
+    <action>- How to implement {{desired_behavior}}</action>
+    <action>- Required node changes or additions</action>
+    <action>- Configuration updates needed</action>
+    <action>- Best practices for these modifications</action>
+
+    <action>Inform user: "Based on n8n documentation, I've identified how to implement your changes."</action>
+  </step>
+
+  <step n="6" goal="Plan Modifications">
+    <action>Load {{helpers}} for node creation guidelines</action>
+    <action>Analyze current workflow structure</action>
+    <action>Plan modifications based on requirements:</action>
+
+    <check if="adding nodes">
+      <action>1. Identify where new nodes should be inserted</action>
+      <action>2. Determine node types needed</action>
+      <action>3. Plan connections to/from new nodes</action>
+      <action>4. Calculate positions for new nodes</action>
+    </check>
+
+    <check if="modifying nodes">
+      <action>1. Identify nodes to modify by name or ID</action>
+      <action>2. Determine what parameters to change</action>
+      <action>3. Validate new parameter values</action>
+    </check>
+
+    <check if="removing nodes">
+      <action>1. Identify nodes to remove by name or ID</action>
+      <action>2. Identify connections that will be affected</action>
+      <action>3. Plan how to reconnect remaining nodes</action>
+    </check>
+
+    <check if="changing connections">
+      <action>1. Identify connections to modify</action>
+      <action>2. Validate new connection targets exist</action>
+      <action>3. Update connection indices if needed</action>
+    </check>
+
+    <action>Present modification plan to user:</action>
+    <action>- Changes to be made: [detailed list]</action>
+    <action>- Nodes affected: [list]</action>
+    <action>- New connections: [list]</action>
+    <action>- Removed connections: [list]</action>
+
+    <action>Ask: "Does this modification plan look correct?"</action>
+    <action>Present numbered options:
+      1. Yes - Proceed with modifications
+      2. No - Adjust the plan
+      3. Add more changes - Include additional modifications
+    </action>
+    <action>WAIT for user selection (1-3)</action>
+
+    <check if="selection is 2 or 3">
+      <action>Ask: "What changes or additions are needed?"</action>
+      <action>WAIT for user input</action>
+      <action>Adjust plan based on feedback</action>
+      <action>Repeat this step</action>
+    </check>
+  </step>
+
+  <step n="7" goal="Apply Modifications">
+    <critical>Follow guidelines from {{helpers}} for proper node creation</critical>
+
+    <action>Load current workflow JSON into memory</action>
+
+    <substep>If Adding Nodes:
+      1. Generate unique node IDs (check against existing IDs)
+      2. Create node objects with proper structure
+      3. Calculate positions (avoid overlaps with existing nodes)
+      4. Add nodes to workflow.nodes array
+      5. Create connections to/from new nodes
+      6. Update connections object
+    </substep>
+
+    <substep>If Modifying Nodes:
+      1. Find nodes by name or ID
+      2. Update parameters as specified
+      3. Preserve node ID and other unchanged properties
+      4. Validate new parameter values
+      5. Update node in workflow.nodes array
+    </substep>
+
+    <substep>If Removing Nodes:
+      1. Find nodes by name or ID
+      2. Remove from workflow.nodes array
+      3. Remove all connections to/from removed nodes
+      4. Update connections object
+      5. Reconnect remaining nodes if needed
+    </substep>
+
+    <substep>If Changing Connections:
+      1. Update connections object
+      2. Validate all referenced nodes exist
+      3. Ensure connection indices are correct
+      4. Remove orphaned connections
+    </substep>
+
+    <substep>If Updating Error Handling:
+      1. Find affected nodes
+      2. Add or update error handling properties:
+         - continueOnFail
+         - retryOnFail
+         - maxTries
+         - waitBetweenTries
+      3. Validate error handling configuration
+    </substep>
+
+    <action>Validate modified workflow:</action>
+    <action>- All node IDs are unique</action>
+    <action>- All node names are unique</action>
+    <action>- All connections reference existing nodes</action>
+    <action>- No orphaned nodes (except trigger)</action>
+    <action>- Node positions don't overlap</action>
+  </step>
+
+  <step n="8" goal="Save Modified Workflow">
+    <action>Save modified workflow to {{workflow_file}}</action>
+    <action>Preserve original file location</action>
+  </step>
+
+  <step n="9" goal="Validate JSON Syntax">
+    <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
+
+    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{workflow_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
+
+    <check if="validation fails (exit code 1)">
+      <action>Read the error message carefully - it shows the syntax error and position</action>
+      <action>Open the file and navigate to the error location</action>
+      <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
+      <action>Save the file</action>
+      <action>Re-run validation with the same command</action>
+      <action>Repeat until validation passes</action>
+    </check>
+
+    <action>Once validation passes, confirm with user: "Workflow modified successfully at {{workflow_file}}"</action>
+  </step>
+
+  <step n="10" goal="Summarize Changes">
+    <action>Provide summary of changes made:</action>
+    <action>- Nodes added: [count and names]</action>
+    <action>- Nodes modified: [count and names]</action>
+    <action>- Nodes removed: [count and names]</action>
+    <action>- Connections changed: [count]</action>
+    <action>- Backup location: {{workflow_file}}.backup-{timestamp}</action>
+
+    <action>Ask: "Would you like to make additional changes?"</action>
+    <action>Present numbered options:
+      1. No - I'm done
+      2. Yes - Make more modifications
+      3. Revert - Restore from backup
+    </action>
+    <action>WAIT for user selection (1-3)</action>
+
+    <check if="selection is 2">
+      <action>Return to Step 1 with current workflow</action>
+    </check>
+
+    <check if="selection is 3">
+      <action>Restore workflow from backup</action>
+      <action>Confirm restoration to user</action>
+    </check>
+  </step>
+
+  <step n="11" goal="Validate Content">
+    <invoke-task>Validate against checklist at {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml</invoke-task>
+  </step>
+
+</workflow>
+```

src/modules/autominator/workflows/modify-workflow/workflow.yaml

@@ -0,0 +1,29 @@
+name: modify-workflow
+description: "Edit or update existing n8n workflow"
+author: "Saif"
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/autominator/workflows/modify-workflow"
+shared_path: "{project-root}/{bmad_folder}/autominator/workflows/_shared"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Shared resources
+helpers: "{shared_path}/n8n-helpers.md"
+templates: "{shared_path}/n8n-templates.yaml"
+platform_mappings: "{shared_path}/platform-mappings.yaml"
+
+# Variables
+variables:
+  workflow_file: "" # Will be elicited
+  modification_type: "" # Will be elicited
+  changes_description: "" # Will be elicited
+  nodes_to_add: [] # Will be elicited
+  nodes_to_modify: [] # Will be elicited
+  nodes_to_remove: [] # Will be elicited
+  backup_created: false # Will be set
+
+default_output_file: "" # Will use existing file location
+
+standalone: true
+web_bundle: false

src/modules/autominator/workflows/optimize-workflow/checklist.md

@@ -0,0 +1,130 @@
+# Optimize n8n Workflow - Validation Checklist
+
+## Pre-Optimization
+
+- [ ] Original workflow was successfully loaded
+- [ ] Workflow JSON was valid before optimization
+- [ ] Optimization focus areas were identified
+- [ ] Backup was created before making changes
+- [ ] User requirements were clearly understood
+
+## Analysis Completeness
+
+- [ ] Performance analysis was conducted
+- [ ] Error handling was reviewed
+- [ ] Code quality was assessed
+- [ ] Structure was evaluated
+- [ ] Best practices were checked
+- [ ] Security was reviewed
+- [ ] All issues were documented
+
+## Recommendations Quality
+
+- [ ] Recommendations are specific and actionable
+- [ ] Recommendations are prioritized correctly
+- [ ] Impact of each recommendation is clear
+- [ ] Implementation steps are provided
+- [ ] Expected improvements are quantified
+- [ ] No breaking changes are recommended
+
+## Performance Optimizations
+
+- [ ] Unnecessary nodes were identified/removed
+- [ ] Data transformations were optimized
+- [ ] Batch processing opportunities were identified
+- [ ] Redundant API calls were consolidated
+- [ ] Parallel execution opportunities were identified
+- [ ] Node execution order was optimized
+
+## Error Handling Improvements
+
+- [ ] Critical nodes have retry logic
+- [ ] continueOnFail is set appropriately
+- [ ] Error workflows are configured where needed
+- [ ] Timeout configurations are appropriate
+- [ ] Error notifications are set up
+- [ ] Error handling doesn't mask real issues
+
+## Code Quality Improvements
+
+- [ ] Set nodes are properly configured
+- [ ] Code nodes are optimized
+- [ ] Expressions use correct syntax
+- [ ] Data types are handled correctly
+- [ ] Hardcoded values are replaced with variables
+- [ ] Node names are descriptive and consistent
+
+## Structure Improvements
+
+- [ ] Node positions are logical and organized
+- [ ] Complex branches are simplified where possible
+- [ ] Duplicate logic is eliminated
+- [ ] Merge points are optimized
+- [ ] Connection patterns are clean
+- [ ] Workflow flow is easy to follow
+
+## Best Practices Applied
+
+- [ ] Credentials are used correctly
+- [ ] Security issues are addressed
+- [ ] Node types are appropriate
+- [ ] Node versions are up to date
+- [ ] Data handling follows best practices
+- [ ] Workflow settings are optimal
+
+## Security Improvements
+
+- [ ] No credentials are exposed
+- [ ] Sensitive data is handled properly
+- [ ] No hardcoded secrets remain
+- [ ] Authentication is properly configured
+- [ ] Data is sanitized where needed
+- [ ] Security best practices are followed
+
+## Workflow Integrity
+
+- [ ] All node IDs remain unique
+- [ ] All node names remain unique
+- [ ] All connections are valid
+- [ ] No functionality is lost
+- [ ] Workflow still achieves original purpose
+- [ ] No breaking changes introduced
+
+## Validation
+
+- [ ] Optimized workflow passes JSON validation
+- [ ] All optimizations were applied correctly
+- [ ] No unintended changes were made
+- [ ] Workflow structure is still logical
+- [ ] All improvements are documented
+
+## Backup & Recovery
+
+- [ ] Backup file was created successfully
+- [ ] Backup location was communicated to user
+- [ ] Original workflow can be restored if needed
+
+## Testing Readiness
+
+- [ ] Optimized workflow can be imported into n8n
+- [ ] Test scenarios are identified
+- [ ] Expected improvements are measurable
+- [ ] Comparison approach is defined
+- [ ] Monitoring plan is suggested
+
+## Documentation
+
+- [ ] Analysis report is comprehensive
+- [ ] All findings are documented
+- [ ] Recommendations are clearly explained
+- [ ] Expected improvements are quantified
+- [ ] Testing recommendations are provided
+- [ ] User understands all changes made
+
+## Expected Improvements
+
+- [ ] Performance improvements are quantified
+- [ ] Reliability improvements are identified
+- [ ] Maintainability improvements are clear
+- [ ] Security improvements are documented
+- [ ] Cost savings are estimated (if applicable)

src/modules/autominator/workflows/optimize-workflow/instructions.md

@@ -0,0 +1,475 @@
+# Optimize n8n Workflow - Workflow Instructions
+
+```xml
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>This workflow analyzes and optimizes existing n8n workflows for performance and best practices.</critical>
+
+<workflow>
+
+  <step n="0" goal="Contextual Analysis (Smart Elicitation)">
+    <critical>Before asking any questions, analyze what the user has already told you</critical>
+
+    <action>Review the user's initial request and conversation history</action>
+    <action>Extract any mentioned: workflow file path, performance issues, optimization goals</action>
+
+    <check if="ALL requirements are clear from context">
+      <action>Summarize your understanding</action>
+      <action>Skip directly to Step 2 (Load Workflow)</action>
+    </check>
+
+    <check if="SOME requirements are clear">
+      <action>Note what you already know</action>
+      <action>Only ask about missing information in Step 1</action>
+    </check>
+
+    <check if="requirements are unclear or minimal">
+      <action>Proceed with full elicitation in Step 1</action>
+    </check>
+  </step>
+
+  <step n="1" goal="Gather Optimization Requirements" elicit="true">
+    <critical>Understand the REAL PROBLEMS the user is experiencing, not just generic optimization goals</critical>
+
+    <action>Ask Question 1: "Which workflow do you want to optimize?"</action>
+    <action>Present numbered options:
+      1. Provide file path - Specify exact path to workflow JSON
+      2. Search in workflows folder - List available workflows
+      3. Paste workflow JSON - Provide workflow content directly
+    </action>
+    <action>WAIT for user selection (1-3)</action>
+
+    <check if="selection is 1">
+      <action>Ask: "Please provide the file path to the workflow JSON"</action>
+      <action>WAIT for user input</action>
+      <action>Store in {{workflow_file}}</action>
+    </check>
+
+    <check if="selection is 2">
+      <action>List all .json files in workflows/ directory</action>
+      <action>Present as numbered list</action>
+      <action>WAIT for user selection</action>
+      <action>Store selected file path in {{workflow_file}}</action>
+    </check>
+
+    <check if="selection is 3">
+      <action>Ask: "Please paste the workflow JSON content"</action>
+      <action>WAIT for user input</action>
+      <action>Create temporary file with content</action>
+      <action>Store temp file path in {{workflow_file}}</action>
+    </check>
+
+    <action>Ask Question 2: "What problems are you experiencing with this workflow?"</action>
+    <action>Examples: "Takes too long to run", "Fails frequently", "Hard to understand", "Doesn't handle errors well"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{problems_experienced}}</action>
+
+    <action>Ask Question 3: "What's the business impact of these problems?"</action>
+    <action>Examples: "Delays customer responses", "Wastes team time", "Causes data issues", "Costs money"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{business_impact}}</action>
+
+    <action>Ask Question 4: "What would 'better' look like for this workflow?"</action>
+    <action>Focus on desired outcomes: "Faster execution", "More reliable", "Easier to maintain", "Better error recovery"</action>
+    <action>WAIT for user input</action>
+    <action>Store in {{desired_improvements}}</action>
+
+    <action>Ask Question 5: "Are there specific areas you want me to focus on?"</action>
+    <action>Present numbered options (can select multiple):
+      1. Performance - Speed and efficiency
+      2. Reliability - Error handling and retries
+      3. Maintainability - Code quality and structure
+      4. Security - Credential and data handling
+      5. All - Comprehensive review
+      6. Let you decide - Analyze and recommend
+    </action>
+    <action>WAIT for user selection (1-6 or multiple)</action>
+    <action>Store selections in {{optimization_focus}}</action>
+
+    <action>Summarize understanding:</action>
+    <action>- Problems: {{problems_experienced}}</action>
+    <action>- Business Impact: {{business_impact}}</action>
+    <action>- Desired Improvements: {{desired_improvements}}</action>
+    <action>- Focus Areas: {{optimization_focus}}</action>
+
+    <action>Ask: "Does this capture your optimization needs?"</action>
+    <action>Present numbered options:
+      1. Yes - Proceed with analysis
+      2. No - Let me clarify
+    </action>
+    <action>WAIT for user selection (1-2)</action>
+    <check if="selection is 2">
+      <action>Ask: "What needs clarification?"</action>
+      <action>WAIT for user input</action>
+      <action>Update relevant variables</action>
+      <action>Repeat summary and confirmation</action>
+    </check>
+  </step>
+
+  <step n="2" goal="Load Workflow">
+    <critical>Only load the workflow file when user provides it - never preload</critical>
+
+    <action>Read workflow file from {{workflow_file}}</action>
+    <action>Parse JSON content</action>
+    <action>Validate JSON structure</action>
+
+    <check if="JSON is invalid">
+      <action>Inform user: "The workflow file has invalid JSON syntax"</action>
+      <action>Show error details</action>
+      <action>Ask: "Would you like me to fix the JSON syntax first? (yes/no)"</action>
+      <action>WAIT for user response</action>
+
+      <check if="user says yes">
+        <action>Fix JSON syntax errors</action>
+        <action>Save corrected file</action>
+        <action>Proceed with loading</action>
+      </check>
+
+      <check if="user says no">
+        <action>Exit workflow with error</action>
+      </check>
+    </check>
+
+    <action>Extract workflow structure:</action>
+    <action>- Workflow name and settings</action>
+    <action>- Node count and types</action>
+    <action>- Connection patterns</action>
+    <action>- Error handling configuration</action>
+    <action>- Credential usage</action>
+
+    <action>Display workflow summary to user:</action>
+    <action>- Name: [workflow name]</action>
+    <action>- Nodes: [count] nodes</action>
+    <action>- Complexity: [simple/medium/complex]</action>
+    <action>- Integrations: [list of services]</action>
+  </step>
+
+  <step n="3" goal="Research n8n Best Practices and Optimization">
+    <critical>Search for n8n documentation on optimization and best practices</critical>
+
+    <action>Inform user: "Researching n8n best practices and optimization techniques..."</action>
+
+    <action>Perform web search for:</action>
+    <action>1. n8n performance optimization</action>
+    <action>2. n8n error handling best practices</action>
+    <action>3. n8n workflow structure patterns</action>
+    <action>4. n8n security best practices</action>
+    <action>5. Solutions for: {{problems_experienced}}</action>
+
+    <action>Search queries to use:</action>
+    <action>- "n8n workflow optimization best practices"</action>
+    <action>- "n8n performance tuning"</action>
+    <action>- "n8n error handling patterns"</action>
+    <action>- "n8n workflow security"</action>
+    <action>- "n8n [specific problem] solution"</action>
+
+    <action>Focus on official n8n documentation at docs.n8n.io</action>
+    <action>Store relevant optimization techniques and best practices</action>
+  </step>
+
+  <step n="4" goal="Verify Optimization Strategy">
+    <action>Summarize optimization approach based on documentation:</action>
+    <action>- Solutions for {{problems_experienced}}</action>
+    <action>- Best practices to apply</action>
+    <action>- Performance improvements available</action>
+    <action>- Expected impact on {{business_impact}}</action>
+
+    <action>Inform user: "Based on n8n best practices, I've identified optimization opportunities."</action>
+  </step>
+
+  <step n="5" goal="Analyze Workflow">
+    <action>Load {{helpers}} for best practices reference</action>
+
+    <action>Perform comprehensive analysis based on {{optimization_focus}}:</action>
+
+    <substep>Performance Analysis:
+      - Check for unnecessary nodes
+      - Identify inefficient data transformations
+      - Look for missing batch processing opportunities
+      - Check for redundant API calls
+      - Analyze node execution order
+      - Identify parallel execution opportunities
+    </substep>
+
+    <substep>Error Handling Analysis:
+      - Check if critical nodes have retry logic
+      - Verify continueOnFail settings
+      - Look for missing error workflows
+      - Check timeout configurations
+      - Verify error notification setup
+    </substep>
+
+    <substep>Code Quality Analysis:
+      - Review Set node configurations
+      - Review Code node implementations
+      - Check expression syntax and efficiency
+      - Verify data type handling
+      - Check for hardcoded values
+      - Review node naming conventions
+    </substep>
+
+    <substep>Structure Analysis:
+      - Check node positioning and layout
+      - Verify logical flow organization
+      - Look for overly complex branches
+      - Check for duplicate logic
+      - Verify proper use of merge nodes
+      - Check connection patterns
+    </substep>
+
+    <substep>Best Practices Analysis:
+      - Verify proper credential usage
+      - Check for security issues
+      - Verify proper use of node types
+      - Check for deprecated node versions
+      - Verify proper data handling
+      - Check workflow settings
+    </substep>
+
+    <substep>Security Analysis:
+      - Check credential exposure
+      - Verify sensitive data handling
+      - Check for hardcoded secrets
+      - Verify proper authentication
+      - Check data sanitization
+    </substep>
+
+    <action>Store all findings in {{issues_found}}</action>
+  </step>
+
+  <step n="6" goal="Generate Recommendations">
+    <action>For each issue found, generate specific recommendations:</action>
+
+    <action>Categorize recommendations by priority:</action>
+    <action>- Critical: Security issues, major performance problems</action>
+    <action>- High: Error handling gaps, significant inefficiencies</action>
+    <action>- Medium: Code quality improvements, minor optimizations</action>
+    <action>- Low: Cosmetic improvements, nice-to-haves</action>
+
+    <action>For each recommendation, provide:</action>
+    <action>1. Issue description</action>
+    <action>2. Impact explanation</action>
+    <action>3. Specific solution</action>
+    <action>4. Implementation steps</action>
+    <action>5. Expected improvement</action>
+
+    <action>Store recommendations in {{recommendations}}</action>
+  </step>
+
+  <step n="7" goal="Present Analysis Report" elicit="true">
+    <action>Present comprehensive optimization report:</action>
+
+    <action>## Workflow Analysis Report</action>
+    <action>Workflow: {{workflow_name}}</action>
+    <action>Analysis Date: {timestamp}</action>
+    <action>Optimization Focus: {{optimization_focus}}</action>
+
+    <action>### Summary</action>
+    <action>- Total Issues Found: [count]</action>
+    <action>- Critical: [count]</action>
+    <action>- High Priority: [count]</action>
+    <action>- Medium Priority: [count]</action>
+    <action>- Low Priority: [count]</action>
+
+    <action>### Detailed Findings</action>
+    <action>Present each issue with:</action>
+    <action>- Priority level</action>
+    <action>- Issue description</action>
+    <action>- Current state</action>
+    <action>- Recommended solution</action>
+    <action>- Expected impact</action>
+
+    <action>### Performance Opportunities</action>
+    <action>List specific performance improvements with estimated impact</action>
+
+    <action>### Best Practice Violations</action>
+    <action>List n8n best practices not being followed</action>
+
+    <action>Ask: "Would you like me to apply these optimizations?"</action>
+    <action>Present numbered options:
+      1. Yes - Apply all recommendations
+      2. Yes - Apply only critical and high priority
+      3. Yes - Let me choose which to apply
+      4. No - Just provide the report
+      5. Explain more - I need more details first
+    </action>
+    <action>WAIT for user selection (1-5)</action>
+
+    <check if="selection is 5">
+      <action>Ask: "Which recommendations would you like explained?"</action>
+      <action>WAIT for user input</action>
+      <action>Provide detailed explanation</action>
+      <action>Repeat this step</action>
+    </check>
+
+    <check if="selection is 3">
+      <action>Present recommendations as numbered list</action>
+      <action>Ask: "Select recommendations to apply (comma-separated numbers)"</action>
+      <action>WAIT for user input</action>
+      <action>Store selected recommendations</action>
+    </check>
+
+    <check if="selection is 1, 2, or 3">
+      <action>Store true in {{apply_changes}}</action>
+      <action>Proceed to Step 8</action>
+    </check>
+
+    <check if="selection is 4">
+      <action>Store false in {{apply_changes}}</action>
+      <action>Skip to Step 11 (provide report only)</action>
+    </check>
+  </step>
+
+  <step n="8" goal="Create Backup">
+    <check if="{{apply_changes}} is true">
+      <action>Create backup of original workflow</action>
+      <action>Save backup to: {{workflow_file}}.backup-{timestamp}</action>
+      <action>Store true in {{backup_created}}</action>
+      <action>Inform user: "Backup created at {{workflow_file}}.backup-{timestamp}"</action>
+    </check>
+  </step>
+
+  <step n="9" goal="Apply Optimizations">
+    <critical>Follow guidelines from {{helpers}} for proper node configuration</critical>
+
+    <action>Load current workflow JSON into memory</action>
+
+    <action>Apply each selected recommendation:</action>
+
+    <substep>Performance Optimizations:
+      - Remove unnecessary nodes
+      - Optimize data transformations
+      - Add batch processing where applicable
+      - Consolidate redundant API calls
+      - Optimize node execution order
+      - Add parallel execution where possible
+    </substep>
+
+    <substep>Error Handling Improvements:
+      - Add retry logic to critical nodes
+      - Set appropriate continueOnFail values
+      - Add error workflows if needed
+      - Configure timeouts
+      - Add error notifications
+    </substep>
+
+    <substep>Code Quality Improvements:
+      - Refactor Set node configurations
+      - Optimize Code node implementations
+      - Improve expression syntax
+      - Fix data type handling
+      - Replace hardcoded values with variables
+      - Improve node naming
+    </substep>
+
+    <substep>Structure Improvements:
+      - Reorganize node positions
+      - Simplify complex branches
+      - Remove duplicate logic
+      - Optimize merge points
+      - Improve connection patterns
+    </substep>
+
+    <substep>Best Practice Applications:
+      - Fix credential usage
+      - Address security issues
+      - Update deprecated nodes
+      - Improve data handling
+      - Update workflow settings
+    </substep>
+
+    <action>Validate optimized workflow:</action>
+    <action>- All node IDs remain unique</action>
+    <action>- All connections are valid</action>
+    <action>- No functionality is lost</action>
+    <action>- All improvements are applied</action>
+  </step>
+
+  <step n="10" goal="Save Optimized Workflow">
+    <action>Save optimized workflow to {{workflow_file}}</action>
+  </step>
+
+  <step n="11" goal="Validate JSON Syntax">
+    <check if="{{apply_changes}} is true">
+      <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
+
+      <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{workflow_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
+
+      <check if="validation fails (exit code 1)">
+        <action>Read the error message carefully - it shows the syntax error and position</action>
+        <action>Open the file and navigate to the error location</action>
+        <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
+        <action>Save the file</action>
+        <action>Re-run validation with the same command</action>
+        <action>Repeat until validation passes</action>
+      </check>
+
+      <action>Once validation passes, confirm with user: "Workflow optimized successfully at {{workflow_file}}"</action>
+    </check>
+  </step>
+
+  <step n="12" goal="Provide Optimization Summary">
+    <action>Provide comprehensive summary:</action>
+
+    <check if="{{apply_changes}} is true">
+      <action>### Optimizations Applied</action>
+      <action>- Total changes: [count]</action>
+      <action>- Performance improvements: [list]</action>
+      <action>- Error handling added: [list]</action>
+      <action>- Code quality fixes: [list]</action>
+      <action>- Structure improvements: [list]</action>
+      <action>- Best practices applied: [list]</action>
+      <action>- Backup location: {{workflow_file}}.backup-{timestamp}</action>
+
+      <action>### Expected Improvements</action>
+      <action>- Execution speed: [estimated improvement]</action>
+      <action>- Reliability: [improvements]</action>
+      <action>- Maintainability: [improvements]</action>
+      <action>- Security: [improvements]</action>
+
+      <action>### Testing Recommendations</action>
+      <action>1. Import optimized workflow into n8n</action>
+      <action>2. Test with sample data</action>
+      <action>3. Compare execution times with original</action>
+      <action>4. Verify all functionality works correctly</action>
+      <action>5. Monitor error rates</action>
+    </check>
+
+    <check if="{{apply_changes}} is false">
+      <action>### Optimization Report</action>
+      <action>Report saved with all recommendations</action>
+      <action>No changes applied to workflow</action>
+      <action>Review recommendations and apply manually if desired</action>
+    </check>
+
+    <action>Ask: "Would you like additional help?"</action>
+    <action>Present numbered options:
+      1. No - I'm done
+      2. Yes - Explain specific optimizations
+      3. Yes - Optimize another workflow
+      4. Revert - Restore from backup
+    </action>
+    <action>WAIT for user selection (1-4)</action>
+
+    <check if="selection is 2">
+      <action>Ask: "Which optimization would you like explained?"</action>
+      <action>WAIT for user input</action>
+      <action>Provide detailed explanation</action>
+    </check>
+
+    <check if="selection is 3">
+      <action>Return to Step 1 for new workflow</action>
+    </check>
+
+    <check if="selection is 4">
+      <action>Restore workflow from backup</action>
+      <action>Confirm restoration to user</action>
+    </check>
+  </step>
+
+  <step n="13" goal="Validate Content">
+    <invoke-task>Validate against checklist at {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml</invoke-task>
+  </step>
+
+</workflow>
+```

src/modules/autominator/workflows/optimize-workflow/workflow.yaml

@@ -0,0 +1,28 @@
+name: optimize-workflow
+description: "Review and improve existing n8n workflows for performance and best practices"
+author: "Saif"
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/autominator/workflows/optimize-workflow"
+shared_path: "{project-root}/{bmad_folder}/autominator/workflows/_shared"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Shared resources
+helpers: "{shared_path}/n8n-helpers.md"
+templates: "{shared_path}/n8n-templates.yaml"
+platform_mappings: "{shared_path}/platform-mappings.yaml"
+
+# Variables
+variables:
+  workflow_file: "" # Will be elicited
+  optimization_focus: [] # Will be elicited
+  issues_found: [] # Will be identified
+  recommendations: [] # Will be generated
+  apply_changes: false # Will be elicited
+  backup_created: false # Will be set
+
+default_output_file: "" # Will use existing file location
+
+standalone: true
+web_bundle: false

src/modules/bmb/README.md

@@ -24,13 +24,13 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 **Active Workflows** (Step-File Architecture)
 
-- Location: `src/modules/bmb/workflows/`
+- Location: `bmb/workflows/create-agent/`
 - 5 core workflows with 41 step files total
 - Template-based execution with JIT loading
 
 **Legacy Workflows** (Being Migrated)
 
-- Location: `src/modules/bmb/workflows-legacy/`
+- Location: `bmb/workflows/create-agent-legacy/`
 - Module-specific workflows pending conversion to step-file architecture
 
 ### 📚 Documentation

src/modules/bmb/agents/bmad-builder.agent.yaml

@@ -4,7 +4,7 @@
 agent:
   webskip: true
   metadata:
-    id: "{bmad_folder}/bmb/agents/bmad-builder.md"
+    id: ".bmad/bmb/agents/bmad-builder.md"
     name: BMad Builder
     title: BMad Builder
     icon: 🧙
@@ -24,26 +24,26 @@ agent:
 
   discussion: true
   conversational_knowledge:
-    - agents: "{project-root}/{bmad_folder}/bmb/docs/agents/kb.csv"
+    - agents: "{project-root}/.bmad/bmb/docs/agents/kb.csv"
-    - workflows: "{project-root}/{bmad_folder}/bmb/docs/workflows/kb.csv"
+    - workflows: "{project-root}/.bmad/bmb/docs/workflows/kb.csv"
-    - modules: "{project-root}/{bmad_folder}/bmb/docs/modules/kb.csv"
+    - modules: "{project-root}/.bmad/bmb/docs/modules/kb.csv"
 
   menu:
     - multi: "[CA] Create, [EA] Edit, or [VA] Validate with Compliance CheckBMAD agents with best practices"
       triggers:
         - create-agent:
             - input: CA or fuzzy match create agent
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/create-agent/workflow.md"
             - data: null
             - type: exec
         - edit-agent:
             - input: EA or fuzzy match edit agent
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.md"
             - data: null
             - type: exec
         - run-agent-compliance-check:
             - input: VA or fuzzy match validate agent
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/agent-compliance-check/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/agent-compliance-check/workflow.md"
             - data: null
             - type: exec
 
@@ -51,17 +51,17 @@ agent:
       triggers:
         - create-workflow:
             - input: CW or fuzzy match create workflow
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow.md"
             - data: null
             - type: exec
         - edit-workflow:
             - input: EW or fuzzy match edit workflow
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.md"
             - data: null
             - type: exec
         - run-workflow-compliance-check:
             - input: VW or fuzzy match validate workflow
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/workflow-compliance-check/workflow.md"
             - data: null
             - type: exec
 
@@ -69,26 +69,26 @@ agent:
       triggers:
         - brainstorm-module:
             - input: BM or fuzzy match brainstorm module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/brainstorm-module/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/brainstorm-module/workflow.md"
             - data: null
             - type: exec
         - product-brief-module:
             - input: PBM or fuzzy match product brief module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/product-brief-module/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/product-brief-module/workflow.md"
             - data: null
             - type: exec
         - create-module:
             - input: CM or fuzzy match create module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/create-module/workflow.md"
             - data: null
             - type: exec
         - edit-module:
             - input: EM or fuzzy match edit module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-module/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/edit-module/workflow.md"
             - data: null
             - type: exec
         - run-module-compliance-check:
             - input: VM or fuzzy match validate module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/module-compliance-check/workflow.md"
+            - route: "{project-root}/.bmad/bmb/workflows/module-compliance-check/workflow.md"
             - data: null
             - type: exec

src/modules/bmb/docs/agents/agent-compilation.md

@@ -35,7 +35,7 @@ rex.agent.yaml           ← Persona name (users might rename to "Max")
 **Pattern:**
 
 - Filename: `{role-or-function}.agent.yaml` (kebab-case)
-- Metadata ID: `{bmad_folder}/{module}/agents/{role-or-function}.md`
+- Metadata ID: `.bmad/{module}/agents/{role-or-function}.md`
 - Persona Name: User-customizable in metadata or customize.yaml
 
 **Example:**
@@ -44,7 +44,7 @@ rex.agent.yaml           ← Persona name (users might rename to "Max")
 # File: presentation-master.agent.yaml
 agent:
   metadata:
-    id: '{bmad_folder}/cis/agents/presentation-master.md'
+    id: '.bmad/cis/agents/presentation-master.md'
     name: Caravaggio # ← Users can change this to "Pablo" or "Vince"
     title: Visual Communication & Presentation Expert
 ```

src/modules/bmb/docs/agents/agent-menu-patterns.md

@@ -65,11 +65,11 @@ For module agents orchestrating multi-step processes.
 ```yaml
 menu:
   - trigger: create-prd
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
     description: 'Create Product Requirements Document'
 
   - trigger: brainstorm
-    workflow: '{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml'
+    workflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml'
     description: 'Guided brainstorming session'
 
   # Placeholder for unimplemented workflows
@@ -92,11 +92,11 @@ For executing tasks directly.
 ```yaml
 menu:
   - trigger: validate
-    exec: '{project-root}/{bmad_folder}/core/tasks/validate-workflow.xml'
+    exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
     description: 'Validate document structure'
 
   - trigger: advanced-elicitation
-    exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+    exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
     description: 'Advanced elicitation techniques'
 ```
 
@@ -113,8 +113,8 @@ For document generation with templates.
 ```yaml
 menu:
   - trigger: create-brief
-    exec: '{project-root}/{bmad_folder}/core/tasks/create-doc.xml'
+    exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
-    tmpl: '{project-root}/{bmad_folder}/bmm/templates/brief.md'
+    tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
     description: 'Create a Product Brief'
 ```
 
@@ -131,8 +131,8 @@ Universal attribute for supplementary information.
 ```yaml
 menu:
   - trigger: team-standup
-    exec: '{project-root}/{bmad_folder}/bmm/tasks/standup.xml'
+    exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
-    data: '{project-root}/{bmad_folder}/_cfg/agent-manifest.csv'
+    data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
     description: 'Run team standup'
 
   - trigger: analyze-metrics
@@ -154,12 +154,12 @@ Control visibility based on deployment target:
 ```yaml
 menu:
   - trigger: git-flow
-    exec: '{project-root}/{bmad_folder}/bmm/tasks/git-flow.xml'
+    exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
     description: 'Git workflow operations'
     ide-only: true # Only in IDE environments
 
   - trigger: advanced-elicitation
-    exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+    exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
     description: 'Advanced elicitation'
     web-only: true # Only in web bundles
 ```
@@ -251,20 +251,20 @@ menu:
 menu:
   # Analysis Phase
   - trigger: brainstorm
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
     description: 'Brainstorm ideas'
 
   - trigger: research
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
     description: 'Conduct research'
 
   # Planning Phase
   - trigger: prd
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
     description: 'Create PRD'
 
   - trigger: architecture
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
     description: 'Design architecture'
 ```
 
@@ -362,8 +362,8 @@ prompts:
 
 ```yaml
 # GOOD - Portable paths
-workflow: "{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml"
+workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
-exec: "{project-root}/{bmad_folder}/core/tasks/validate.xml"
+exec: "{project-root}/.bmad/core/tasks/validate.xml"
 data: "{project-root}/_data/metrics.csv"
 
 # BAD - Hardcoded paths
@@ -374,7 +374,7 @@ exec: "../../../core/tasks/validate.xml"
 ### Available Variables
 
 - `{project-root}` - Project root directory
-- `{bmad_folder}` - BMAD installation folder
+- `.bmad` - BMAD installation folder
 - `{agent_sidecar_folder}` - Agent installation directory (Expert agents)
 - `{output_folder}` - Document output location
 - `{user_name}` - User's name from config
@@ -444,23 +444,23 @@ menu:
 ```yaml
 menu:
   - trigger: workflow-init
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml'
     description: 'Initialize workflow path (START HERE)'
 
   - trigger: brainstorm
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
     description: 'Guided brainstorming'
 
   - trigger: prd
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
     description: 'Create PRD'
 
   - trigger: architecture
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml'
+    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
     description: 'Design architecture'
 
   - trigger: party-mode
-    workflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml'
+    workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
     description: 'Multi-agent discussion'
 ```