** Overview **
Tasks, Sub-Workflows, and Agent Customizations seem to be possible however the BMB doesn't seem to natively know about these concepts so task some coercion. Tasks do exist within the core module as an example so it would be nice if the bmb workflow-builder was able to create these with consistency. Same with references to sub-workflows.
** Thoughts on Tasks ** :
- /create-task workflow exists to create a single file execution (smallest building block). Not step-based or multi-file
- Tasks follow .md standard of others versus XML would be ideal
- workflow-builder knows about create-task workflow
- Maintain ability to be standalone (resolves as command) or requires being invoked by agent/workflow
** Thoughts on Agent Customizations **
Often if i tell the agent-builder to custom the agent, it will go to the direct .md file of the agent rather than the agent's .customize.yaml file. It would be good if it was better trained to look there first.
** Overview **
Tasks, Sub-Workflows, and Agent Customizations seem to be possible however the BMB doesn't seem to natively know about these concepts so task some coercion. Tasks do exist within the core module as an example so it would be nice if the bmb workflow-builder was able to create these with consistency. Same with references to sub-workflows.
** Thoughts on Tasks ** :
** Thoughts on Agent Customizations **
Often if i tell the agent-builder to custom the agent, it will go to the direct .md file of the agent rather than the agent's .customize.yaml file. It would be good if it was better trained to look there first.