4.8 KiB
Workflow Management
This utility enables the BMAD orchestrator to manage and execute team workflows.
Workflow Commands
/workflows
Lists all available workflows for the current team.
Example response:
Available workflows:
1. greenfield-mvp - Complete workflow for building a new MVP from scratch
2. fullstack-app - Comprehensive workflow for production-ready applications
3. api-only - API-first development workflow
4. brownfield-enhancement - Enhance existing applications
5. frontend-only - Frontend application development
Use /workflow-start {number or id} to begin a workflow.
/workflow-start {workflow-id}
Starts a specific workflow and transitions to the first agent.
Example: /workflow-start greenfield-mvp
/workflow-status
Shows current workflow progress, completed artifacts, and next steps.
Example response:
Current Workflow: Greenfield MVP Development
Stage: Product Planning (2 of 6)
Completed:
✓ Discovery & Requirements
- project-brief (completed by Mary)
In Progress:
⚡ Product Planning
- Create PRD (John) - awaiting input
Next: Technical Architecture
/workflow-resume
Resumes a workflow from where it left off, useful when starting a new chat.
User can provide completed artifacts:
User: /workflow-resume greenfield-mvp
I have completed: project-brief, PRD
BMad: I see you've completed Discovery and part of Product Planning.
Based on the greenfield-mvp workflow, the next step is:
- UX Strategy with Sally (ux-expert)
Would you like me to load Sally to continue?
/workflow-next
Shows the next recommended agent and action in the current workflow.
Workflow Execution Flow
1. Starting a Workflow
When a workflow is started:
- Load the workflow definition
- Identify the first stage and step
- Transition to the required agent
- Provide context about expected inputs/outputs
- Guide artifact creation
2. Stage Transitions
After each artifact is completed:
- Mark the step as complete
- Check transition conditions
- If stage is complete, move to next stage
- Load the appropriate agent
- Pass relevant artifacts as context
3. Artifact Tracking
Track all created artifacts:
workflow_state:
current_workflow: greenfield-mvp
current_stage: planning
current_step: 2
artifacts:
project-brief:
status: completed
created_by: analyst
timestamp: 2024-01-15T10:30:00Z
prd:
status: in-progress
created_by: pm
started: 2024-01-15T11:00:00Z
4. Workflow Interruption Handling
When user returns after interruption:
- Ask if continuing previous workflow
- Request any completed artifacts
- Analyze provided artifacts
- Determine workflow position
- Suggest next appropriate step
Example:
User: I'm working on a new app. Here's my PRD and architecture doc.
BMad: I see you have a PRD and architecture document. Based on these artifacts,
it looks like you're following the greenfield-mvp workflow and have completed
stages 1-3. The next recommended step would be:
Stage 4: Validation & Refinement
- Load Sarah (Product Owner) to validate all artifacts
Would you like to continue with this workflow?
Workflow Context Passing
When transitioning between agents, pass:
- Previous artifacts created
- Current workflow stage
- Expected outputs
- Any decisions or constraints identified
Example transition:
BMad: Great! John has completed the PRD. According to the greenfield-mvp workflow,
the next step is UX Strategy with Sally.
/ux-expert
Sally: I see we're in the Product Planning stage of the greenfield-mvp workflow.
I have access to:
- Project Brief from Mary
- PRD from John
Let's create the UX strategy and UI specifications. First, let me review
the PRD to understand the features we're designing for...
Multi-Path Workflows
Some workflows may have multiple paths:
conditional_paths:
- condition: "project_type == 'mobile'"
next_stage: mobile-specific-design
- condition: "project_type == 'web'"
next_stage: web-architecture
- default: fullstack-architecture
Handle these by asking clarifying questions when needed.
Workflow Best Practices
- Always show progress - Users should know where they are
- Explain transitions - Why moving to next agent
- Preserve context - Pass relevant information forward
- Allow flexibility - Users can skip or modify steps
- Track everything - Maintain complete workflow state
Integration with Agents
Each agent should be workflow-aware:
- Know which workflow is active
- Understand their role in the workflow
- Access previous artifacts
- Know expected outputs
- Guide toward workflow goals
This creates a seamless experience where the entire team works together toward the workflow's objectives.