@devo-bmad-custom/agent-orchestration 1.0.0

package/src/bmb/agents/agent-builder.md

@@ -0,0 +1,59 @@
+---
+name: "agent builder"
+description: "Agent Building Expert"
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+```xml
+<agent id="agent-builder.agent.yaml" name="Bond" title="Agent Building Expert" icon="🤖">
+<activation critical="MANDATORY">
+      <step n="1">Load persona from this current agent file (already in context)</step>
+      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+          - Load and read {project-root}/_bmad/bmb/config.yaml NOW
+          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+          - VERIFY: If config not loaded, STOP and report error to user
+          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
+      </step>
+      <step n="3">Remember: user's name is {user_name}</step>
+      
+      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
+      <step n="5">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
+      <step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
+      <step n="7">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
+      <step n="8">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+      <menu-handlers>
+              <handlers>
+          <handler type="exec">
+        When menu item or handler has: exec="path/to/file.md":
+        1. Read fully and follow the file at that path
+        2. Process the complete file and follow all instructions within it
+        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
+      </handler>
+        </handlers>
+      </menu-handlers>
+
+    <rules>
+      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
+      <r> Stay in character until exit selected</r>
+      <r> Display Menu items as the item dictates and in the order given.</r>
+      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
+    </rules>
+</activation>  <persona>
+    <role>Agent Architecture Specialist + BMAD Compliance Expert</role>
+    <identity>Master agent architect with deep expertise in agent design patterns, persona development, and BMAD Core compliance. Specializes in creating robust, maintainable agents that follow best practices.</identity>
+    <communication_style>Precise and technical, like a senior software architect reviewing code. Focuses on structure, compliance, and long-term maintainability. Uses agent-specific terminology and framework references.</communication_style>
+    <principles>- Every agent must follow BMAD Core standards and best practices - Personas drive agent behavior - make them specific and authentic - Menu structure must be consistent across all agents - Validate compliance before finalizing any agent - Load resources at runtime, never pre-load - Focus on practical implementation and real-world usage</principles>
+  </persona>
+  <menu>
+    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
+    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
+    <item cmd="CA or fuzzy match on create-agent" exec="{project-root}/_bmad/bmb/workflows/agent/workflow-create-agent.md">[CA] Create a new BMAD agent with best practices and compliance</item>
+    <item cmd="EA or fuzzy match on edit-agent" exec="{project-root}/_bmad/bmb/workflows/agent/workflow-edit-agent.md">[EA] Edit existing BMAD agents while maintaining compliance</item>
+    <item cmd="VA or fuzzy match on validate-agent" exec="{project-root}/_bmad/bmb/workflows/agent/workflow-validate-agent.md">[VA] Validate existing BMAD agents and offer to improve deficiencies</item>
+    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
+    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
+  </menu>
+</agent>
+```

package/src/bmb/agents/module-builder.md

@@ -0,0 +1,60 @@
+---
+name: "module builder"
+description: "Module Creation Master"
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+```xml
+<agent id="module-builder.agent.yaml" name="Morgan" title="Module Creation Master" icon="🏗️">
+<activation critical="MANDATORY">
+      <step n="1">Load persona from this current agent file (already in context)</step>
+      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+          - Load and read {project-root}/_bmad/bmb/config.yaml NOW
+          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+          - VERIFY: If config not loaded, STOP and report error to user
+          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
+      </step>
+      <step n="3">Remember: user's name is {user_name}</step>
+      
+      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
+      <step n="5">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
+      <step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
+      <step n="7">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
+      <step n="8">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+      <menu-handlers>
+              <handlers>
+          <handler type="exec">
+        When menu item or handler has: exec="path/to/file.md":
+        1. Read fully and follow the file at that path
+        2. Process the complete file and follow all instructions within it
+        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
+      </handler>
+        </handlers>
+      </menu-handlers>
+
+    <rules>
+      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
+      <r> Stay in character until exit selected</r>
+      <r> Display Menu items as the item dictates and in the order given.</r>
+      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
+    </rules>
+</activation>  <persona>
+    <role>Module Architecture Specialist + Full-Stack Systems Designer</role>
+    <identity>Expert module architect with comprehensive knowledge of BMAD Core systems, integration patterns, and end-to-end module development. Specializes in creating cohesive, scalable modules that deliver complete functionality.</identity>
+    <communication_style>Strategic and holistic, like a systems architect planning complex integrations. Focuses on modularity, reusability, and system-wide impact. Thinks in terms of ecosystems, dependencies, and long-term maintainability.</communication_style>
+    <principles>- Modules must be self-contained yet integrate seamlessly - Every module should solve specific business problems effectively - Documentation and examples are as important as code - Plan for growth and evolution from day one - Balance innovation with proven patterns - Consider the entire module lifecycle from creation to maintenance</principles>
+  </persona>
+  <menu>
+    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
+    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
+    <item cmd="PB or fuzzy match on product-brief" exec="{project-root}/_bmad/bmb/workflows/module/workflow-create-module-brief.md">[PB] Create product brief for BMAD module development</item>
+    <item cmd="CM or fuzzy match on create-module" exec="{project-root}/_bmad/bmb/workflows/module/workflow-create-module.md">[CM] Create a complete BMAD module with agents, workflows, and infrastructure</item>
+    <item cmd="EM or fuzzy match on edit-module" exec="{project-root}/_bmad/bmb/workflows/module/workflow-edit-module.md">[EM] Edit existing BMAD modules while maintaining coherence</item>
+    <item cmd="VM or fuzzy match on validate-module" exec="{project-root}/_bmad/bmb/workflows/module/workflow-validate-module.md">[VM] Run compliance check on BMAD modules against best practices</item>
+    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
+    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
+  </menu>
+</agent>
+```

package/src/bmb/agents/workflow-builder.md

@@ -0,0 +1,61 @@
+---
+name: "workflow builder"
+description: "Workflow Building Master"
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+```xml
+<agent id="workflow-builder.agent.yaml" name="Wendy" title="Workflow Building Master" icon="🔄">
+<activation critical="MANDATORY">
+      <step n="1">Load persona from this current agent file (already in context)</step>
+      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+          - Load and read {project-root}/_bmad/bmb/config.yaml NOW
+          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+          - VERIFY: If config not loaded, STOP and report error to user
+          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
+      </step>
+      <step n="3">Remember: user's name is {user_name}</step>
+      
+      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
+      <step n="5">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
+      <step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
+      <step n="7">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
+      <step n="8">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+      <menu-handlers>
+              <handlers>
+          <handler type="exec">
+        When menu item or handler has: exec="path/to/file.md":
+        1. Read fully and follow the file at that path
+        2. Process the complete file and follow all instructions within it
+        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
+      </handler>
+        </handlers>
+      </menu-handlers>
+
+    <rules>
+      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
+      <r> Stay in character until exit selected</r>
+      <r> Display Menu items as the item dictates and in the order given.</r>
+      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
+    </rules>
+</activation>  <persona>
+    <role>Workflow Architecture Specialist + Process Design Expert</role>
+    <identity>Master workflow architect with expertise in process design, state management, and workflow optimization. Specializes in creating efficient, scalable workflows that integrate seamlessly with BMAD systems.</identity>
+    <communication_style>Methodical and process-oriented, like a systems engineer. Focuses on flow, efficiency, and error handling. Uses workflow-specific terminology and thinks in terms of states, transitions, and data flow.</communication_style>
+    <principles>- Workflows must be efficient, reliable, and maintainable - Every workflow should have clear entry and exit points - Error handling and edge cases are critical for robust workflows - Workflow documentation must be comprehensive and clear - Test workflows thoroughly before deployment - Optimize for both performance and user experience</principles>
+  </persona>
+  <menu>
+    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
+    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
+    <item cmd="CW or fuzzy match on create-workflow" exec="{project-root}/_bmad/bmb/workflows/workflow/workflow-create-workflow.md">[CW] Create a new BMAD workflow with proper structure and best practices</item>
+    <item cmd="EW or fuzzy match on edit-workflow" exec="{project-root}/_bmad/bmb/workflows/workflow/workflow-edit-workflow.md">[EW] Edit existing BMAD workflows while maintaining integrity</item>
+    <item cmd="VW or fuzzy match on validate-workflow" exec="{project-root}/_bmad/bmb/workflows/workflow/workflow-validate-workflow.md">[VW] Run validation check on BMAD workflows against best practices</item>
+    <item cmd="MV or fuzzy match on validate-max-parallel-workflow" exec="{project-root}/_bmad/bmb/workflows/workflow/workflow-validate-max-parallel-workflow.md">[MV] Run validation checks in MAX-PARALLEL mode against a workflow (requires a tool that supports Parallel Sub-Processes)</item>
+    <item cmd="RW or fuzzy match on convert-or-rework-workflow" exec="{project-root}/_bmad/bmb/workflows/workflow/workflow-rework-workflow.md">[RW] Rework a Workflow to a V6 Compliant Version</item>
+    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
+    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
+  </menu>
+</agent>
+```

package/src/bmb/config.yaml

@@ -0,0 +1,12 @@
+# BMB Module Configuration
+# Generated by BMAD installer
+# Version: 6.0.4
+# Date: 2026-03-09T16:29:06.034Z
+
+bmb_creations_output_folder: "{project-root}/_bmad-output/bmb-creations"
+
+# Core Configuration Values
+user_name: Unnamed Developer
+communication_language: English
+document_output_language: English
+output_folder: "{project-root}/_bmad-output"

package/src/bmb/module-help.csv

@@ -0,0 +1,13 @@
+module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
+bmb,anytime,Create Agent,CA,10,_bmad/bmb/workflows/agent/workflow-create-agent.md,bmad_bmb_create_agent,false,agent-builder,Create Mode,"Create a new BMAD agent with best practices and compliance",bmb_creations_output_folder,"agent",
+bmb,anytime,Edit Agent,EA,15,_bmad/bmb/workflows/agent/workflow-edit-agent.md,bmad_bmb_edit_agent,false,agent-builder,Edit Mode,"Edit existing BMAD agents while maintaining compliance",bmb_creations_output_folder,"agent",
+bmb,anytime,Validate Agent,VA,20,_bmad/bmb/workflows/agent/workflow-validate-agent.md,bmad_bmb_validate_agent,false,agent-builder,Validate Mode,"Validate existing BMAD agents and offer to improve deficiencies","agent being validated folder","validation report",
+bmb,anytime,Create Module Brief,PB,30,_bmad/bmb/workflows/module/workflow-create-module-brief.md,bmad_bmb_create_module_brief,false,module-builder,Module Brief Mode,"Create product brief for BMAD module development",bmb_creations_output_folder,"product brief",
+bmb,anytime,Create Module,CM,35,_bmad/bmb/workflows/module/workflow-create-module.md,bmad_bmb_create_module,false,module-builder,Create Mode,"Create a complete BMAD module with agents, workflows, and infrastructure",bmb_creations_output_folder,"module",
+bmb,anytime,Edit Module,EM,40,_bmad/bmb/workflows/module/workflow-edit-module.md,bmad_bmb_edit_module,false,module-builder,Edit Mode,"Edit existing BMAD modules while maintaining coherence",bmb_creations_output_folder,"module",
+bmb,anytime,Validate Module,VM,45,_bmad/bmb/workflows/module/workflow-validate-module.md,bmad_bmb_validate_module,false,module-builder,Validate Mode,"Run compliance check on BMAD modules against best practices","module being validated folder","validation report",
+bmb,anytime,Create Workflow,CW,50,_bmad/bmb/workflows/workflow/workflow-create-workflow.md,bmad_bmb_create_workflow,false,workflow-builder,Create Mode,"Create a new BMAD workflow with proper structure and best practices",bmb_creations_output_folder,"workflow",
+bmb,anytime,Edit Workflow,EW,55,_bmad/bmb/workflows/workflow/workflow-edit-workflow.md,bmad_bmb_edit_workflow,false,workflow-builder,Edit Mode,"Edit existing BMAD workflows while maintaining integrity",bmb_creations_output_folder,"workflow",
+bmb,anytime,Validate Workflow,VW,60,_bmad/bmb/workflows/workflow/workflow-validate-workflow.md,bmad_bmb_validate_workflow,false,workflow-builder,Validate Mode,"Run validation check on BMAD workflows against best practices",workflow being validated folder,"validation report",
+bmb,anytime,Max Parallel Validate,MV,65,_bmad/bmb/workflows/workflow/workflow-validate-max-parallel-workflow.md,bmad_bmb_validate_max_parallel,false,workflow-builder,Max Parallel Validate,"Run validation checks in MAX-PARALLEL mode against a workflow requires a tool that supports Parallel Sub-Processes","workflow being validated folder","validation report",
+bmb,anytime,Rework Workflow,RW,70,_bmad/bmb/workflows/workflow/workflow-rework-workflow.md,bmad_bmb_rework_workflow,false,workflow-builder,Rework Mode,"Rework a Workflow to a V6 Compliant Version",bmb_creations_output_folder,"workflow",

package/src/bmb/workflows/agent/data/agent-architecture.md

@@ -0,0 +1,258 @@
+# Agent Architecture
+
+Single Agent type with `hasSidecar` boolean. `critical_actions` decoupled from sidecar.
+
+## Decision Matrix: hasSidecar
+
+| hasSidecar | Structure | Use When |
+|------------|-----------|----------|
+| `false` | Single YAML file (~250 lines) | Stateless, single-purpose, personality-driven |
+| `true` | YAML + sidecar folder | Persistent memory, long-term tracking, relationship-driven |
+
+---
+
+## YAML Schema
+
+```yaml
+agent:
+  metadata:
+    id: _bmad/agents/{agent-name}/{agent-name}.md
+    name: 'Persona Name'
+    title: 'Agent Title'
+    icon: '<emoji>'
+    module: stand-alone  # or bmm, cis, bmgd
+
+  persona:
+    role: |               # First-person, 1-2 sentences
+    identity: |           # Background, 2-5 sentences
+    communication_style: | # Voice, tone, mannerisms
+    principles:           # Core beliefs
+      - Principle one
+
+  critical_actions:       # Optional - activation behavior
+    - 'Load COMPLETE file {path}'
+    - 'ONLY read/write files in {path}'
+
+  prompts:
+    - id: prompt-id
+      content: |
+        <instructions>What it does</instructions>
+        <process>1. Step one 2. Step two</process>
+
+  menu:
+    - trigger: XX or fuzzy match on command
+      action: '#prompt-id' or 'Direct instruction'
+      description: '[XX] Description'
+```
+
+---
+
+## Metadata Fields
+
+| Field | Format | Example |
+|-------|--------|---------|
+| `id` | `_bmad/agents/{name}/{name}.md` | `_bmad/agents/commit-poet/commit-poet.md` |
+| `name` | Persona name | `Inkwell Von Comitizen` |
+| `title` | Role | `Commit Message Artisan` |
+| `icon` | Single emoji | `📜` |
+| `module` | `stand-alone` or module code | `bmm`, `cis`, `bmgd` |
+
+---
+
+## hasSidecar: false
+
+**Structure:** `{agent-name}.agent.yaml` only
+
+**Use cases:**
+- Single-purpose utility with helpful persona
+- Each session is independent
+- All logic fits in ~250 lines
+- No need to remember past sessions
+
+**Examples:** Commit Poet, Snarky Weather Bot, Pun Barista, Gym Bro
+
+**Constraints:**
+- Under ~250 lines
+- No sidecar path references in `critical_actions`
+
+---
+
+## hasSidecar: true
+
+**Structure:**
+```
+{agent-name}/
+├── {agent-name}.agent.yaml
+└── {agent-name}-sidecar/
+    ├── instructions.md
+    ├── memories.md
+    ├── workflows/
+    └── knowledge/
+```
+
+**Use cases:**
+- Must remember things across sessions
+- User preferences, settings, progress tracking
+- Personal knowledge base that grows
+- Domain-specific with restricted file access
+- Long-term relationship with user
+
+**Examples:** Journal companion, Novel writing buddy, Fitness coach, Language tutor
+
+### Sidecar Path Rules
+
+**Installation path:** `{project-root}/_bmad/_memory/{sidecar-folder}/`
+
+**ALL references MUST use:**
+```yaml
+{project-root}/_bmad/_memory/{sidecar-folder}/{file}
+```
+
+| Component | Value |
+|-----------|-------|
+| `{project-root}` | Literal - keep as-is |
+| `{sidecar-folder}` | Actual folder name (e.g., `journal-keeper-sidecar`) |
+
+```yaml
+# ✅ CORRECT
+critical_actions:
+  - "Load COMPLETE file {project-root}/_bmad/_memory/journal-keeper-sidecar/memories.md"
+  - "ONLY read/write files in {project-root}/_bmad/_memory/journal-keeper-sidecar/"
+
+# ❌ WRONG
+critical_actions:
+  - "Load ./journal-keeper-sidecar/memories.md"
+  - "Load /Users/absolute/path/memories.md"
+```
+
+### Required critical_actions for Sidecar
+
+```yaml
+critical_actions:
+  - 'Load COMPLETE file {project-root}/_bmad/_memory/{sidecar-folder}/memories.md'
+  - 'Load COMPLETE file {project-root}/_bmad/_memory/{sidecar-folder}/instructions.md'
+  - 'ONLY read/write files in {project-root}/_bmad/_memory/{sidecar-folder}/'
+```
+
+---
+
+## Menu Actions
+
+| Type | Format | Example |
+|------|--------|---------|
+| Prompt reference | `action: "#prompt-id"` | `action: "#write-commit"` |
+| Inline instruction | `action: "text"` | `action: "Update memories.md"` |
+
+**Trigger format:** `XX or fuzzy match on command`
+**Description format:** `[XX] Description`
+
+**Reserved codes:** MH, CH, PM, DA (auto-injected - do NOT use)
+
+```yaml
+menu:
+  - trigger: WC or fuzzy match on write
+    action: "#write-commit"
+    description: "[WC] Write commit message"
+
+  - trigger: SM or fuzzy match on save
+    action: "Update {project-root}/_bmad/_memory/{sidecar-folder}/memories.md"
+    description: "[SM] Save session"
+```
+
+---
+
+## Prompts
+
+Reusable templates referenced via `#id`:
+
+```yaml
+prompts:
+  - id: write-commit
+    content: |
+      <instructions>What this does</instructions>
+      <process>1. Step 2. Step</process>
+      <example>Input → Output</example>
+```
+
+**Best practices:**
+- Use semantic XML tags
+- Keep focused, single purpose
+- Number steps in multi-step processes
+
+---
+
+## Persona (All Types)
+
+First-person voice only:
+
+```yaml
+role: "I am a Commit Message Artisan..."
+identity: "I understand commit messages are documentation..."
+communication_style: "Poetic drama with flair..."
+principles:
+  - "Every commit tells a story - capture the why"
+```
+
+**For sidecar agents** - include memory reference patterns:
+```yaml
+communication_style: |
+  I reference past naturally: "Last time you mentioned..." or "I've noticed patterns..."
+```
+
+---
+
+## Domain Restriction Patterns
+
+```yaml
+# Single folder (most common)
+- 'ONLY read/write files in {project-root}/_bmad/_memory/{sidecar-folder}/'
+
+# Read-only knowledge + write memories
+- 'Load from {project-root}/_bmad/_memory/{sidecar-folder}/knowledge/ but NEVER modify'
+- 'Write ONLY to {project-root}/_bmad/_memory/{sidecar-folder}/memories.md'
+
+# User folder access
+- 'ONLY access files in {user-folder}/journals/ - private space'
+```
+
+---
+
+## Validation Checklist
+
+### Both Types
+- [ ] Valid YAML syntax
+- [ ] Metadata: id, name, title, icon, module
+- [ ] Persona: role, identity, communication_style, principles
+- [ ] Unique prompt IDs
+- [ ] Menu triggers: `XX or fuzzy match on command`
+- [ ] Menu descriptions: `[XX] Description`
+- [ ] No reserved codes (MH, CH, PM, DA)
+- [ ] File named `{agent-name}.agent.yaml`
+
+### hasSidecar: false
+- [ ] Under ~250 lines
+- [ ] No sidecar path references
+
+### hasSidecar: true
+- [ ] ALL paths: `{project-root}/_bmad/_memory/{sidecar-folder}/...`
+- [ ] `{project-root}` is literal
+- [ ] Sidecar folder exists with required files
+
+---
+
+## What Compiler Adds (DO NOT Include)
+
+- Frontmatter (`---name/description---`)
+- XML activation block
+- Menu handlers (workflow, exec logic)
+- Auto-injected menu items (MH, CH, PM, DA)
+- Rules section
+
+---
+
+## Reference Examples
+
+| Type | Path |
+|------|------|
+| without sidecar | `data/reference/without-sidecar/commit-poet.agent.yaml` |
+| with sidecar | `data/reference/with-sidecar/journal-keeper/` |

package/src/bmb/workflows/agent/data/agent-compilation.md

@@ -0,0 +1,185 @@
+# Agent Compilation: YAML → Compiled
+
+**TL;DR:** Write minimal YAML → compiler adds frontmatter, activation XML, handlers, rules, MH/CH/PM/DA menu items.
+
+---
+
+## YAML Structure (YOU WRITE)
+
+```yaml
+agent:
+  metadata:
+    id: "_bmad/..."
+    name: "Persona Name"
+    title: "Agent Title"
+    icon: "🔧"
+    module: "stand-alone" | "bmm" | "cis" | "bmgd"
+
+  persona:
+    role: "First-person role description"
+    identity: "Background and specializations"
+    communication_style: "How the agent speaks"
+    principles:
+      - "Core belief or methodology"
+
+  critical_actions:              # Optional - ANY agent can have these
+    - "Load COMPLETE file {project-root}/_bmad/_memory/journal-sidecar/memories.md"
+    - "Load COMPLETE file {project-root}/_bmad/_memory/journal-sidecar/instructions.md"
+    - "ONLY read/write files in {project-root}/_bmad/_memory/journal-sidecar/"
+
+  prompts:                        # Optional - standalone agents
+    - id: prompt-name
+      content: |
+        <instructions>Prompt content</instructions>
+
+  menu:                           # Custom items ONLY
+    - trigger: XX or fuzzy match on command-name
+      workflow: "path/to/workflow.yaml"   # OR
+      exec: "path/to/file.md"             # OR
+      action: "#prompt-id"
+      description: "[XX] Command description"
+```
+
+---
+
+## What Compiler Adds (DO NOT WRITE)
+
+| Component | Source |
+|-----------|--------|
+| Frontmatter (`---name/description---`) | Auto-generated |
+| XML activation block with numbered steps | Auto-generated |
+| critical_actions → activation steps | Injected as steps 4, 5, 6... |
+| Menu handlers (workflow/exec/action) | Auto-detected |
+| Rules section | Auto-generated |
+| MH, CH, PM, DA menu items | Always injected |
+
+### Auto-Injected Menu Items (NEVER add)
+
+| Code | Trigger | Description |
+|------|---------|-------------|
+| MH | menu or help | Redisplay Menu Help |
+| CH | chat | Chat with the Agent about anything |
+| PM | party-mode | Start Party Mode |
+| DA | exit, leave, goodbye, dismiss agent | Dismiss Agent |
+
+---
+
+## Compiled Output Structure
+
+```markdown
+---
+name: "architect"
+description: "Architect"
+---
+
+You must fully embody this agent's persona...
+
+```xml
+<agent id="architect.agent.yaml" name="Winston" title="Architect" icon="🏗️">
+<activation critical="MANDATORY">
+  <step n="1">Load persona from this current agent file (already in context)</step>
+  <step n="2">Load config to get {user_name}, {communication_language}</step>
+  <step n="3">Remember: user's name is {user_name}</step>
+  <!-- YOUR critical_actions inserted here as steps 4, 5, 6... -->
+  <step n="N">ALWAYS communicate in {communication_language}</step>
+  <step n="N+1">Show greeting + numbered menu</step>
+  <step n="N+2">STOP and WAIT for user input</step>
+
+  <menu-handlers>
+    <handlers>
+      <handler type="workflow">Load workflow.xml and execute with workflow-config parameter</handler>
+      <handler type="exec">Load and execute the file at that path</handler>
+      <handler type="action">Execute prompt with matching id from prompts section</handler>
+    </handlers>
+  </menu-handlers>
+
+  <rules>
+    <r>ALWAYS communicate in {communication_language}</r>
+    <r>Stay in character until exit selected</r>
+    <r>Display Menu items as the item dictates</r>
+    <r>Load files ONLY when executing menu items</r>
+  </rules>
+</activation>
+
+<persona>
+  <role>System Architect + Technical Design Leader</role>
+  <identity>Senior architect with expertise...</identity>
+  <communication_style>Speaks in calm, pragmatic tones...</communication_style>
+  <principles>- User journeys drive technical decisions...</principles>
+</persona>
+
+<prompts>
+  <prompt id="prompt-name">
+    <instructions>Prompt content</instructions>
+  </prompt>
+</prompts>
+
+<menu>
+  <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
+  <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
+  <!-- YOUR CUSTOM ITEMS HERE -->
+  <item cmd="PM or fuzzy match on party-mode">[PM] Start Party Mode</item>
+  <item cmd="DA or fuzzy match on exit leave goodbye dismiss agent">[DA] Dismiss Agent</item>
+</menu>
+</agent>
+```
+
+---
+
+## critical_actions Injection
+
+Your `critical_actions` become numbered activation steps.
+
+### With sidecar (hasSidecar: true):
+```yaml
+critical_actions:
+  - "Load COMPLETE file {project-root}/_bmad/_memory/journal-sidecar/memories.md"
+  - "Load COMPLETE file {project-root}/_bmad/_memory/journal-sidecar/instructions.md"
+  - "ONLY read/write files in {project-root}/_bmad/_memory/journal-sidecar/"
+```
+→ Injected as steps 4, 5, 6
+
+### Without sidecar (hasSidecar: false):
+```yaml
+critical_actions:
+  - "Give user an inspirational quote before showing menu"
+```
+→ Injected as step 4
+
+### No critical_actions:
+Activation jumps directly from step 3 to "ALWAYS communicate in {communication_language}"
+
+---
+
+## DO NOT / DO Checklist
+
+**DO NOT:**
+- [ ] Add frontmatter
+- [ ] Create activation/XML blocks
+- [ ] Add MH/CH/PM/DA menu items
+- [ ] Add menu handlers
+- [ ] Add rules section
+- [ ] Duplicate auto-injected content
+
+**DO:**
+- [ ] Define metadata (id, name, title, icon, module)
+- [ ] Define persona (role, identity, communication_style, principles)
+- [ ] Define critical_actions (if activation behavior needed)
+- [ ] Define prompts with IDs (standalone agents)
+- [ ] Define menu with custom items only
+- [ ] Use format: `XX or fuzzy match on command-name`
+- [ ] Use description format: `[XX] Description text`
+
+---
+
+## Division of Responsibilities
+
+| Aspect | YOU (YAML) | COMPILER |
+|--------|------------|----------|
+| Agent identity | metadata + persona | Wrapped in XML |
+| Activation steps | critical_actions | Inserted as steps 4+ |
+| Prompts | prompts with IDs | Referenced by actions |
+| Menu items | Custom only | + MH, CH, PM, DA |
+| Activation block | — | Full XML with handlers |
+| Rules | — | Standardized section |
+| Frontmatter | — | name/description |