Greg
fa8acef423
- Initialize Git repository with main branch - Create comprehensive .gitignore for Node.js, React, and environment files - Set up directory structure (frontend/, backend/, docs/) - Create detailed README.md with project overview and setup instructions - Add .env.example with all required environment variables - Configure Prettier for consistent code formatting All acceptance criteria met: ✅ Git repository initialized with appropriate .gitignore ✅ Directory structure matches Technical Assumptions ✅ README.md created with project overview and setup docs ✅ .env.example file with all required environment variables ✅ Prettier config files added for code formatting consistency 🤖 Generated with Claude Code (https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
72 lines
1.7 KiB
Markdown
72 lines
1.7 KiB
Markdown
<!-- Powered by BMAD™ Core -->
|
|
|
|
# Workflow Management
|
|
|
|
Enables BMad orchestrator to manage and execute team workflows.
|
|
|
|
## Dynamic Workflow Loading
|
|
|
|
Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
|
|
|
|
**Key Commands**:
|
|
|
|
- `/workflows` - List workflows in current bundle or workflows folder
|
|
- `/agent-list` - Show agents in current bundle
|
|
|
|
## Workflow Commands
|
|
|
|
### /workflows
|
|
|
|
Lists available workflows with titles and descriptions.
|
|
|
|
### /workflow-start {workflow-id}
|
|
|
|
Starts workflow and transitions to first agent.
|
|
|
|
### /workflow-status
|
|
|
|
Shows current progress, completed artifacts, and next steps.
|
|
|
|
### /workflow-resume
|
|
|
|
Resumes workflow from last position. User can provide completed artifacts.
|
|
|
|
### /workflow-next
|
|
|
|
Shows next recommended agent and action.
|
|
|
|
## Execution Flow
|
|
|
|
1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
|
|
|
|
2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
|
|
|
|
3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
|
|
|
|
4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
|
|
|
|
## Context Passing
|
|
|
|
When transitioning, pass:
|
|
|
|
- Previous artifacts
|
|
- Current workflow stage
|
|
- Expected outputs
|
|
- Decisions/constraints
|
|
|
|
## Multi-Path Workflows
|
|
|
|
Handle conditional paths by asking clarifying questions when needed.
|
|
|
|
## Best Practices
|
|
|
|
1. Show progress
|
|
2. Explain transitions
|
|
3. Preserve context
|
|
4. Allow flexibility
|
|
5. Track state
|
|
|
|
## Agent Integration
|
|
|
|
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
|