bmad-method 6.0.0-alpha.1 → 6.0.0-alpha.11

package/src/modules/bmb/workflows/audit-workflow/checklist.md

@@ -45,7 +45,7 @@
 ## Web Bundle Validation (if applicable)
 
 - [ ] web_bundle section present if workflow needs deployment
-- [ ] All paths in web_bundle use bmad/-relative format (NOT {project-root})
+- [ ] All paths in web_bundle use {bmad_folder}/-relative format (NOT {project-root})
 - [ ] No {config_source} variables in web_bundle section
 - [ ] instructions file listed in web_bundle_files array
 - [ ] template file listed in web_bundle_files (if document workflow)
@@ -53,7 +53,7 @@
 - [ ] All data files (CSV, JSON, YAML) listed in web_bundle_files
 - [ ] All <invoke-workflow> called workflows have their .yaml files in web_bundle_files
 - [ ] **CRITICAL**: If workflow invokes other workflows, existing_workflows field is present
-- [ ] existing_workflows maps workflow variables to bmad/-relative paths correctly
+- [ ] existing_workflows maps workflow variables to {bmad_folder}/-relative paths correctly
 - [ ] All files referenced in instructions <action> tags listed in web_bundle_files
 - [ ] No files listed in web_bundle_files that don't exist
 - [ ] Web bundle metadata (name, description, author) matches top-level metadata
@@ -125,10 +125,9 @@ _List any cleanup recommendations:_
 
 ## Audit Summary
 
-**Total Checks:** 72
-**Passed:** **\_** / 72
-**Failed:** **\_** / 72
-**Pass Rate:** **\_**%
+**Total Checks:**
+**Passed:** {total}
+**Failed:** {total}
 
 **Recommendation:**
 

package/src/modules/bmb/workflows/audit-workflow/instructions.md

@@ -1,7 +1,7 @@
 # Audit Workflow - Workflow Quality Audit Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/audit-workflow/workflow.yaml</critical>
+<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: {project-root}/{bmad_folder}/bmb/workflows/audit-workflow/workflow.yaml</critical>
 
 <workflow>
 
@@ -33,7 +33,7 @@
 
     **Required variables:**
 
-    - `config_source: "{project-root}/bmad/[module]/config.yaml"`
+    - `config_source: "{project-root}/{bmad_folder}/[module]/config.yaml"`
     - `output_folder: "{config_source}:output_folder"`
     - `user_name: "{config_source}:user_name"`
     - `communication_language: "{config_source}:communication_language"`
@@ -161,7 +161,7 @@
     <action if="condition met">Do something</action>
     ```
 
-    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|goto|step|elicit-required)&gt; within text content</action>
+    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|invoke-task|goto|step)&gt; within text content</action>
     <action>Record any instances of nested tag references with line numbers</action>
     <action>Scan instructions.md for conditional execution antipattern: self-closing check tags</action>
     <action>Detect pattern: `&lt;check&gt;.*&lt;/check&gt;` on single line (self-closing check)</action>
@@ -182,7 +182,7 @@
 
       **Path Validation:**
 
-      - [ ] All paths use bmad/-relative format (NOT {project-root})
+      - [ ] All paths use {bmad_folder}/-relative format (NOT {project-root})
       - [ ] No {config_source} variables in web_bundle section
       - [ ] Paths match actual file locations
 
@@ -200,7 +200,7 @@
       <action>Verify each called workflow.yaml is in web_bundle_files</action>
       <action>**CRITICAL**: Check if existing_workflows field is present when workflows are invoked</action>
       <action>If invoke-workflow calls exist, existing_workflows MUST map workflow variables to paths</action>
-      <action>Example: If instructions use {core_brainstorming}, web_bundle needs: existing_workflows: - core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"</action>
+      <action>Example: If instructions use {core_brainstorming}, web_bundle needs: existing_workflows: - core_brainstorming: "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"</action>
 
       **File Reference Scan:**
       <action>Scan instructions.md for file references in action tags</action>

package/src/modules/bmb/workflows/audit-workflow/workflow.yaml

@@ -4,14 +4,14 @@ description: "Comprehensive workflow quality audit - validates structure, config
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/audit-workflow"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/audit-workflow"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/src/modules/bmb/workflows/convert-legacy/README.md

@@ -84,7 +84,7 @@ convert-legacy/
 - Prompts for target module (bmm, bmb, cis, custom)
 - Determines proper installation paths using v6 conventions
 - Shows target location for user confirmation
-- Ensures all paths use `{project-root}/bmad/` format
+- Ensures all paths use `{project-root}/{bmad_folder}/` format
 
 ### Phase 2: Conversion Strategy (Step 4)
 
@@ -126,7 +126,7 @@ convert-legacy/
 **Template-to-Workflow Conversion (5c)**
 
 - Converts YAML template sections to workflow steps
-- Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` tags
+- Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>` tags
 - Transforms conditional sections to flow control
 - Creates proper template.md from content structure
 - Integrates v4 create-doc.md task patterns
@@ -218,7 +218,7 @@ Converted items follow v6 conventions:
 
 **Issue**: Path conversion errors
 
-- **Solution**: Ensure all references use `{project-root}/bmad/` format
+- **Solution**: Ensure all references use `{project-root}/{bmad_folder}/` format
 - **Check**: Review conversion mappings for proper path patterns
 
 **Issue**: Sub-workflow invocation fails
@@ -252,8 +252,8 @@ To customize this workflow:
 
 For issues or questions:
 
-- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Check conversion mappings at `/bmad/bmb/data/v4-to-v6-mappings.yaml`
+- Review the workflow creation guide at `/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Check conversion mappings at `/{bmad_folder}/bmb/data/v4-to-v6-mappings.yaml`
 - Validate output using `checklist.md`
 - Consult BMAD v6 documentation for proper conventions
 

package/src/modules/bmb/workflows/convert-legacy/checklist.md

@@ -37,7 +37,7 @@
 - [ ] File paths use {project-root} variables
 - [ ] Config values use {config_source}: pattern
 - [ ] Agent follows naming conventions (kebab-case for files)
-- [ ] ALL paths reference {project-root}/bmad/{{module}}/ locations, NOT src/
+- [ ] ALL paths reference {project-root}/{bmad_folder}/{{module}}/ locations, NOT src/
 - [ ] exec, data, run-workflow commands point to final BMAD installation paths
 
 ### For Template/Workflow Conversions
@@ -48,7 +48,7 @@
 - [ ] All sections converted to workflow steps
 - [ ] Section hierarchy maintained in instructions
 - [ ] Variables ({{var}}) preserved in template.md
-- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
 - [ ] Conditional sections preserved with if="" attributes
 - [ ] Repeatable sections converted to repeat="" attributes
 

package/src/modules/bmb/workflows/convert-legacy/instructions.md

@@ -1,7 +1,7 @@
 # Convert Legacy - v4 to v6 Conversion Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<parameter name="You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<parameter name="You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/convert-legacy/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the conversion process</critical>
 
 <workflow>
@@ -70,8 +70,8 @@ For Modules:
 <action if="custom module"><ask>Enter custom module code (kebab-case):</ask></action>
 <action>Determine installation path based on type and module</action>
 <critical>IMPORTANT: All paths must use final BMAD installation locations, not src paths!</critical>
-<action>Show user the target location: {project-root}/bmad/{{target_module}}/{{item_type}}/{{item_name}}</action>
-<action>Note: Files will be created in bmad/ but all internal paths will reference {project-root}/bmad/ locations</action>
+<action>Show user the target location: {project-root}/{bmad_folder}/{{target_module}}/{{item_type}}/{{item_name}}</action>
+<action>Note: Files will be created in {bmad_folder}/ but all internal paths will reference {project-root}/{bmad_folder}/ locations</action>
 <ask>Proceed with this location? (y/n)</ask>
 </step>
 
@@ -150,16 +150,16 @@ For Modules:
    - Convert task dependencies to workflow references
    - Map template dependencies to v6 workflows
    - Preserve checklist and data file references
-   - CRITICAL: All paths must use {project-root}/bmad/{{module}}/ NOT src/
+   - CRITICAL: All paths must use {project-root}/{bmad_folder}/{{module}}/ NOT src/
 
 <action>Generate the converted v6 agent YAML file (.agent.yaml)</action>
 <action>Example path conversions:
 
-- exec="{project-root}/bmad/{{target_module}}/tasks/task-name.md"
-- run-workflow="{project-root}/bmad/{{target_module}}/workflows/workflow-name/workflow.yaml"
-- data="{project-root}/bmad/{{target_module}}/data/data-file.yaml"
+- exec="{project-root}/{bmad_folder}/{{target_module}}/tasks/task-name.md"
+- run-workflow="{project-root}/{bmad_folder}/{{target_module}}/workflows/workflow-name/workflow.yaml"
+- data="{project-root}/{bmad_folder}/{{target_module}}/data/data-file.yaml"
   </action>
-  <action>Save to: bmad/{{target_module}}/agents/{{agent_name}}.agent.yaml (physical location)</action>
+  <action>Save to: {bmad_folder}/{{target_module}}/agents/{{agent_name}}.agent.yaml (physical location)</action>
   <action>Note: The build process will later compile this to .md with XML format</action>
   <goto step="6">Continue to Validation</goto>
   </step>
@@ -172,7 +172,7 @@ For Modules:
 - Any special behaviors
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-agent/workflow.yaml
+  workflow: {project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.yaml
   inputs:
     - agent_name: {{extracted_name}}
     - agent_purpose: {{extracted_purpose}}
@@ -193,7 +193,7 @@ For Modules:
 
 2. Convert template sections to instructions.md:
    - Each YAML section → workflow step
-   - `elicit: true` → `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` tag
+   - `elicit: true` → `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>` tag
    - Conditional sections → `if="condition"` attribute
    - Repeatable sections → `repeat="for-each"` attribute
    - Section instructions → step content
@@ -212,7 +212,7 @@ For Modules:
 
 ```yaml
 # Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+config_source: '{project-root}/{bmad_folder}/{{target_module}}/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
@@ -220,7 +220,7 @@ date: system-generated
 ```
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
+  workflow: {project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{template_name}}
     - workflow_type: document
@@ -239,7 +239,7 @@ date: system-generated
 <action>Create module blueprint with all components</action>
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-module/workflow.yaml
+  workflow: {project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.yaml
   inputs:
     - module_name: {{module_name}}
     - components: {{component_list}}
@@ -277,7 +277,7 @@ date: system-generated
    </check>
 
 4. Handle special v4 patterns:
-   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
    - Agent permissions → note in instructions
    - YOLO mode → autonomous flag or optional steps
    - Critical notices → workflow.yaml comments
@@ -286,7 +286,7 @@ date: system-generated
 
 ```yaml
 # Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+config_source: '{project-root}/{bmad_folder}/{{target_module}}/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
@@ -294,7 +294,7 @@ date: system-generated
 ```
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
+  workflow: {project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{task_name}}
     - workflow_type: {{confirmed_workflow_type}}

package/src/modules/bmb/workflows/convert-legacy/workflow.yaml

@@ -4,30 +4,26 @@ description: "Converts legacy BMAD v4 or similar items (agents, workflows, modul
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 
-# Optional docs that can be provided as input
-recommended_inputs:
-  - legacy_file: "Path to v4 agent, workflow, or module to convert"
-
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/convert-legacy"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/convert-legacy"
 template: false # This is an action/meta workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 
 # Output configuration - Creates converted items in appropriate module locations
-default_output_folder: "{project-root}/bmad/{{target_module}}/{{item_type}}/{{item_name}}"
+default_output_folder: "{project-root}/{bmad_folder}/{{target_module}}/{{item_type}}/{{item_name}}"
 
 # Sub-workflows that may be invoked for conversion
 sub_workflows:
-  - create_agent: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
-  - create_workflow: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
-  - create_module: "{project-root}/bmad/bmb/workflows/create-module/workflow.yaml"
+  - create_agent: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.yaml"
+  - create_workflow: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml"
+  - create_module: "{project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.yaml"
 
 standalone: true
 

package/src/modules/bmb/workflows/create-agent/agent-validation-checklist.md

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