mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
feat: implement granular step-file workflow architecture with multi-menu support
## 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.
This commit is contained in:
@@ -0,0 +1,140 @@
|
||||
# Workflow Compliance Report Template
|
||||
|
||||
**Workflow:** {workflow_name}
|
||||
**Date:** {validation_date}
|
||||
**Standards:** BMAD workflow-template.md and step-template.md
|
||||
**Report Type:** Comprehensive Compliance Validation
|
||||
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
**Overall Compliance Status:** {compliance_status}
|
||||
**Critical Issues:** {critical_count} - Must be fixed immediately
|
||||
**Major Issues:** {major_count} - Significantly impacts quality/maintainability
|
||||
**Minor Issues:** {minor_count} - Standards compliance improvements
|
||||
|
||||
**Compliance Score:** {compliance_score}% based on template adherence
|
||||
|
||||
**Workflow Type Assessment:** {workflow_type} - {type_appropriateness}
|
||||
|
||||
---
|
||||
|
||||
## Phase 1: Workflow.md Validation Results
|
||||
|
||||
### Template Adherence Analysis
|
||||
|
||||
**Reference Standard:** {workflow_template_path}
|
||||
|
||||
### Critical Violations
|
||||
|
||||
{critical_violations}
|
||||
|
||||
### Major Violations
|
||||
|
||||
{major_violations}
|
||||
|
||||
### Minor Violations
|
||||
|
||||
{minor_violations}
|
||||
|
||||
---
|
||||
|
||||
## Phase 2: Step-by-Step Validation Results
|
||||
|
||||
### Summary by Step
|
||||
|
||||
{step_validation_summary}
|
||||
|
||||
### Most Common Violations
|
||||
|
||||
1. {most_common_violation_1}
|
||||
2. {most_common_violation_2}
|
||||
3. {most_common_violation_3}
|
||||
|
||||
### Workflow Type Appropriateness
|
||||
|
||||
**Analysis:** {workflow_type_analysis}
|
||||
**Recommendations:** {type_recommendations}
|
||||
|
||||
---
|
||||
|
||||
## Phase 3: Holistic Analysis Results
|
||||
|
||||
### Flow Validation
|
||||
|
||||
{flow_validation_results}
|
||||
|
||||
### Goal Alignment
|
||||
|
||||
**Stated Goal:** {stated_goal}
|
||||
**Actual Implementation:** {actual_implementation}
|
||||
**Alignment Score:** {alignment_score}%
|
||||
**Gap Analysis:** {gap_analysis}
|
||||
|
||||
### Optimization Opportunities
|
||||
|
||||
{optimization_opportunities}
|
||||
|
||||
---
|
||||
|
||||
## Meta-Workflow Failure Analysis
|
||||
|
||||
### Issues That Should Have Been Prevented
|
||||
|
||||
**By create-workflow:**
|
||||
{create_workflow_failures}
|
||||
|
||||
**By edit-workflow:**
|
||||
{edit_workflow_failures}
|
||||
|
||||
### Recommended Meta-Workflow Improvements
|
||||
|
||||
{meta_workflow_improvements}
|
||||
|
||||
---
|
||||
|
||||
## Severity-Ranked Fix Recommendations
|
||||
|
||||
### IMMEDIATE - Critical (Must Fix for Functionality)
|
||||
|
||||
{critical_recommendations}
|
||||
|
||||
### HIGH PRIORITY - Major (Significantly Impacts Quality)
|
||||
|
||||
{major_recommendations}
|
||||
|
||||
### MEDIUM PRIORITY - Minor (Standards Compliance)
|
||||
|
||||
{minor_recommendations}
|
||||
|
||||
---
|
||||
|
||||
## Automated Fix Options
|
||||
|
||||
### Fixes That Can Be Applied Automatically
|
||||
|
||||
{automated_fixes}
|
||||
|
||||
### Fixes Requiring Manual Review
|
||||
|
||||
{manual_fixes}
|
||||
|
||||
---
|
||||
|
||||
## Next Steps Recommendation
|
||||
|
||||
**Recommended Approach:**
|
||||
{recommended_approach}
|
||||
|
||||
**Estimated Effort:**
|
||||
|
||||
- Critical fixes: {critical_effort}
|
||||
- Major fixes: {major_effort}
|
||||
- Minor fixes: {minor_effort}
|
||||
|
||||
---
|
||||
|
||||
**Report Generated:** {timestamp}
|
||||
**Validation Engine:** BMAD Workflow Compliance Checker
|
||||
**Next Review Date:** {next_review_date}
|
||||
Reference in New Issue
Block a user