## Major Features Added - **Step-file workflow architecture**: Transform monolithic workflows into granular step files for improved LLM adherence and consistency - **Multi-menu handler system**: New `handler-multi.xml` enables grouped menu items with fuzzy matching - **Workflow compliance checker**: Added automated compliance validation for all workflows - **Create/edit agent workflows**: New structured workflows for agent creation and editing ## Workflow Enhancements - **Create-workflow**: Expanded from 6 to 14 detailed steps covering tools, design, compliance - **Granular step execution**: Each workflow step now has dedicated files for focused execution - **New documentation**: Added CSV data standards, intent vs prescriptive spectrum, and common tools reference ## Complete Migration Status - **4 workflows fully migrated**: `create-agent`, `edit-agent`, `create-workflow`, and `edit-workflow` now use the new granular step-file architecture - **Legacy transformation**: `edit-workflow` includes built-in capability to transform legacy single-file workflows into the new improved granular format - **Future cleanup**: Legacy versions will be removed in a future commit after validation ## Schema Updates - **Multi-menu support**: Updated agent schema to support `triggers` array for grouped menu items - **Legacy compatibility**: Maintains backward compatibility with single `trigger` field - **Discussion enhancements**: Added conversational_knowledge recommendation for discussion agents ## File Structure Changes - Added: `create-agent/`, `edit-agent/`, `edit-workflow/`, `workflow-compliance-check/` workflows - Added: Documentation standards and CSV reference files - Refactored: `create-workflow/steps/` with detailed granular step files ## Handler Improvements - Enhanced `handler-exec.xml` with clearer execution instructions - Improved data passing context for executed files - Better error handling and user guidance This architectural change significantly improves workflow execution consistency across all LLM models by breaking complex processes into manageable, focused steps. The edit-workflow transformation tool ensures smooth migration of existing workflows to the new format. |
||
|---|---|---|
| .. | ||
| README.md | ||
| security-engineer.agent.yaml | ||
| trend-analyst.agent.yaml | ||
README.md
Module Agent Examples
Reference examples for module-integrated agents.
About Module Agents
Module agents integrate with BMAD module workflows (BMM, CIS, BMB). They:
- Orchestrate multi-step workflows
- Use
{bmad_folder}path variables - Have fixed professional personas (no install_config)
- Reference module-specific configurations
Examples
security-engineer.agent.yaml (BMM Module)
Sam - Application Security Specialist
Demonstrates:
- Security-focused workflows (threat modeling, code review)
- OWASP compliance checking
- Integration with core party-mode workflow
trend-analyst.agent.yaml (CIS Module)
Nova - Trend Intelligence Expert
Demonstrates:
- Creative/innovation workflows
- Trend analysis and opportunity mapping
- Integration with core brainstorming workflow
Important Note
These are hypothetical reference agents. The workflows they reference (threat-model, trend-scan, etc.) may not exist. They serve as examples of proper module agent structure.
Using as Templates
When creating module agents:
- Copy relevant example
- Update metadata (id, name, title, icon, module)
- Rewrite persona for your domain
- Replace menu with actual available workflows
- Remove hypothetical workflow references
See /src/modules/bmb/docs/agents/module-agent-architecture.md for complete guide.