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:
Brian Madison
@@ -0,0 +1,222 @@
|
||||
---
|
||||
name: 'step-11-celebrate'
|
||||
description: 'Celebrate completion and guide next steps for using the agent'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-11-celebrate.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/agent-completion-{project_name}.md'
|
||||
agentFile: '{{output_file_path}}'
|
||||
compiledAgentFile: '{{compiled_agent_path}}'
|
||||
|
||||
# Template References
|
||||
completionTemplate: '{workflow_path}/templates/completion-summary.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 11: Celebration and Next Steps
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Celebrate the successful agent creation, provide activation guidance, and explore what to do next with the completed agent while marking workflow completion.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: Read the complete step file before taking any action
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a celebration coordinator who guides users through agent activation and next steps
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring deployment expertise, user brings their excitement about their new agent, together we ensure successful agent activation and usage
|
||||
- ✅ Maintain collaborative celebratory tone throughout
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus only on celebrating completion and guiding next steps
|
||||
- 🚫 FORBIDDEN to end without marking workflow completion in frontmatter
|
||||
- 💬 Approach: Celebrate enthusiastically while providing practical guidance
|
||||
- 📋 Ensure user understands activation steps and agent capabilities
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎉 Celebrate agent creation achievement enthusiastically
|
||||
- 💾 Mark workflow completion in frontmatter
|
||||
- 📖 Provide clear activation guidance and next steps
|
||||
- 🚫 FORBIDDEN to end workflow without proper completion marking
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Complete, validated, and built agent from previous steps
|
||||
- Focus: Celebration, activation guidance, and workflow completion
|
||||
- Limits: No agent modifications, only usage guidance and celebration
|
||||
- Dependencies: Complete agent ready for activation
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Grand Celebration
|
||||
|
||||
Present enthusiastic celebration:
|
||||
|
||||
"🎉 Congratulations! We did it! {{agent_name}} is complete and ready to help users with {{agent_purpose}}!"
|
||||
|
||||
**Journey Celebration:**
|
||||
"Let's celebrate what we accomplished together:
|
||||
|
||||
- Started with an idea and discovered its true purpose
|
||||
- Crafted a unique personality with the four-field persona system
|
||||
- Built powerful capabilities and commands
|
||||
- Established a perfect name and identity
|
||||
- Created complete YAML configuration
|
||||
- Validated quality and prepared for deployment"
|
||||
|
||||
### 2. Agent Capabilities Showcase
|
||||
|
||||
**Agent Introduction:**
|
||||
"Meet {{agent_name}} - your {{agent_type}} agent ready to {{agent_purpose}}!"
|
||||
|
||||
**Key Features:**
|
||||
"✨ **What makes {{agent_name}} special:**
|
||||
|
||||
- {{unique_personality_trait}} personality that {{communication_style_benefit}}
|
||||
- Expert in {{domain_expertise}} with {{specialized_knowledge}}
|
||||
- {{number_commands}} powerful commands including {{featured_command}}
|
||||
- Ready to help with {{specific_use_cases}}"
|
||||
|
||||
### 3. Activation Guidance
|
||||
|
||||
**Getting Started:**
|
||||
"Here's how to start using {{agent_name}}:"
|
||||
|
||||
**Activation Steps:**
|
||||
|
||||
1. **Locate your agent files:** `{{agent_file_location}}`
|
||||
2. **If compiled:** Use the compiled version at `{{compiled_location}}`
|
||||
3. **For customization:** Edit the customization file at `{{customization_location}}`
|
||||
4. **First interaction:** Start by asking for help to see available commands
|
||||
|
||||
**First Conversation Suggestions:**
|
||||
"Try starting with:
|
||||
|
||||
- 'Hi {{agent_name}}, what can you help me with?'
|
||||
- 'Tell me about your capabilities'
|
||||
- 'Help me with [specific task related to agent purpose]'"
|
||||
|
||||
### 4. Next Steps Exploration
|
||||
|
||||
**Immediate Next Steps:**
|
||||
"Now that {{agent_name}} is ready, what would you like to do first?"
|
||||
|
||||
**Options to Explore:**
|
||||
|
||||
- **Test drive:** Try out different commands and capabilities
|
||||
- **Customize:** Fine-tune personality or add new commands
|
||||
- **Integrate:** Set up {{agent_name}} in your workflow
|
||||
- **Share:** Tell others about your new agent
|
||||
- **Expand:** Plan additional agents or capabilities
|
||||
|
||||
**Future Possibilities:**
|
||||
"As you use {{agent_name}}, you might discover:
|
||||
|
||||
- New capabilities you'd like to add
|
||||
- Other agents that would complement this one
|
||||
- Ways to integrate {{agent_name}} into larger workflows
|
||||
- Opportunities to share {{agent_name}} with your team"
|
||||
|
||||
### 5. Final Documentation
|
||||
|
||||
#### Content to Append (if applicable):
|
||||
|
||||
```markdown
|
||||
## Agent Creation Complete! 🎉
|
||||
|
||||
### Agent Summary
|
||||
|
||||
- **Name:** {{agent_name}}
|
||||
- **Type:** {{agent_type}}
|
||||
- **Purpose:** {{agent_purpose}}
|
||||
- **Status:** Ready for activation
|
||||
|
||||
### File Locations
|
||||
|
||||
- **Agent Config:** {{agent_file_path}}
|
||||
- **Compiled Version:** {{compiled_agent_path}}
|
||||
- **Customization:** {{customization_file_path}}
|
||||
|
||||
### Activation Guidance
|
||||
|
||||
[Steps for activating and using the agent]
|
||||
|
||||
### Next Steps
|
||||
|
||||
[Ideas for using and expanding the agent]
|
||||
```
|
||||
|
||||
Save this content to `{outputFile}` for reference.
|
||||
|
||||
### 6. Workflow Completion
|
||||
|
||||
**Mark Complete:**
|
||||
"Agent creation workflow completed successfully! {{agent_name}} is ready to help users and make a real difference."
|
||||
|
||||
**Final Achievement:**
|
||||
"You've successfully created a custom BMAD agent from concept to deployment-ready configuration. Amazing work!"
|
||||
|
||||
### 7. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Complete"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF A: Execute {advancedElicitationTask}
|
||||
- IF P: Execute {partyModeWorkflow}
|
||||
- IF C: Save content to {outputFile}, update frontmatter with workflow completion, then end workflow gracefully
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY complete workflow when user selects 'C'
|
||||
- After other menu items execution, return to this menu
|
||||
- User can chat or ask questions - always respond and then end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [C complete option] is selected and [workflow completion marked in frontmatter], will the workflow end gracefully with agent ready for activation.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Enthusiastic celebration of agent creation achievement
|
||||
- Clear activation guidance and next steps provided
|
||||
- Agent capabilities and value clearly communicated
|
||||
- User confidence in agent usage established
|
||||
- Workflow properly marked as complete in frontmatter
|
||||
- Future possibilities and expansion opportunities explored
|
||||
- Content properly saved to output file
|
||||
- Menu presented with completion option
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Ending without marking workflow completion
|
||||
- Not providing clear activation guidance
|
||||
- Missing celebration of achievement
|
||||
- Not ensuring user understands next steps
|
||||
- Failing to update frontmatter completion status
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user