fix: optimize agent compiler and complete handler cleanup

- Add deployment-aware handler generation (filters web-only/ide-only commands)
- Remove unused run-workflow handler type (ghost handler cleanup)
- Implement missing validate-workflow and data handler generation
- Update schema validation to support exactly 6 active handler types
- Clean up activation templates and web bundler logic
- Prevent generation of unused handler instructions for better performance
- All 62 tests pass with backward compatibility maintained
This commit is contained in:
Brian Madison
2025-11-23 21:28:50 -06:00
parent cd98a7f5bb
commit 3740a554f0
15 changed files with 56 additions and 59 deletions

View File

@@ -38,7 +38,7 @@
- [ ] Config values use {config_source}: pattern
- [ ] Agent follows naming conventions (kebab-case for files)
- [ ] ALL paths reference {project-root}/{bmad_folder}/{{module}}/ locations, NOT src/
- [ ] exec, data, run-workflow commands point to final BMAD installation paths
- [ ] exec, data, workflow commands point to final BMAD installation paths
### For Template/Workflow Conversions

View File

@@ -156,7 +156,7 @@ For Modules:
<action>Example path conversions:
- exec="{project-root}/{bmad_folder}/{{target_module}}/tasks/task-name.md"
- run-workflow="{project-root}/{bmad_folder}/{{target_module}}/workflows/workflow-name/workflow.yaml"
- 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_folder}/{{target_module}}/agents/{{agent_name}}.agent.yaml (physical location)</action>

View File

@@ -20,19 +20,19 @@ agent:
menu:
- trigger: brainstorm-project
workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml"
description: Guided Brainstorming
description: Guided Brainstorming scoped to product development ideation and problem discovery
- trigger: research
workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml"
description: Guided Research
description: Guided Research scoped to market and competitive analysis of a product or feature
- trigger: product-brief
workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.yaml"
description: Create a Product Brief
description: Create a Product Brief, a great input to then drive a PRD
- trigger: document-project
workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
description: Generate comprehensive documentation of an existing Project
description: Generate comprehensive documentation of an existing codebase, including architecture, data flows, and API contracts, and other details to aid project understanding.
- trigger: party-mode
workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"

View File

@@ -24,7 +24,6 @@ agent:
- trigger: validate-architecture
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
checklist: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/checklist.md"
description: Validate Architecture Document
- trigger: implementation-readiness

View File

@@ -25,13 +25,11 @@ agent:
- trigger: validate-prd
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.yaml"
checklist: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/checklist.md"
document: "{output_folder}/PRD.md"
description: Validate PRD + Epics + Stories completeness and quality
description: Validate PRD
- trigger: create-epics-and-stories
workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.yaml"
description: Break PRD requirements into implementable epics and stories after the architecture is defined
description: Create Epics and User Stories from PRD (Its recommended to not do this until the architecture is complete)
- trigger: correct-course
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"

View File

@@ -19,7 +19,6 @@ agent:
- Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md ``
menu:
# Quick-Flow workflows - Barry owns the entire quick-flow path from spec to ship
- trigger: create-tech-spec
workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
description: Architect a technical spec with implementation-ready stories

View File

@@ -25,12 +25,10 @@ agent:
menu:
- trigger: create-ux-design
workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
description: Conduct Design Thinking Workshop to Define the User Specification
description: Conduct Design Thinking Workshop to Define the User Specification with PRD as input
- trigger: validate-design
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
checklist: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
document: "{output_folder}/ux-spec.md"
description: Validate UX Specification and Design Artifacts
- trigger: create-excalidraw-wireframe

View File

@@ -83,7 +83,7 @@ Master storyteller with 50+ years crafting compelling narratives across multiple
All CIS agents are **Module Agents** with:
- Integration with CIS module configuration
- Access to workflow invocation via `run-workflow` or `exec` attributes
- Access to workflow invocation via `workflow` or `exec` attributes
- Standard critical actions for config loading and user context
- Simple command structure focused on workflow facilitation