Overview
I want to be able to leverage the BMM v6 4 Phased process however there are cases where I want my custom module's workflows/agents involved to extend phase(s) or replace steps within a phase so that it executes my own custom implementation. I'd like to have this encapsulated in my custom module so that installing it automatically gets picked up and a custom version of the bmad process is created.
I'd imagine there could be a yaml file that defines a custom method like BMaD vs Enterprise Method. I could have {My Org} Method which requires the phases and steps with a disposition of insert before, insert after, or override.
The tricky part that I don't know how to solve would be to ensure that these custom steps are creating proper artifacts that are compatible with the downstream steps in the BMAD process. Would there need to be required input/output specifications to adhere to?
Why is this needed?
Solves the problem of not customizing first-party modules that could break compatibility in the future. Also, addresses the problem of having to clone all of the BMM phases as custom content which increases maintenance efforts.
Overview
I want to be able to leverage the BMM v6 4 Phased process however there are cases where I want my custom module's workflows/agents involved to extend phase(s) or replace steps within a phase so that it executes my own custom implementation. I'd like to have this encapsulated in my custom module so that installing it automatically gets picked up and a custom version of the bmad process is created.
I'd imagine there could be a yaml file that defines a custom method like BMaD vs Enterprise Method. I could have {My Org} Method which requires the phases and steps with a disposition of insert before, insert after, or override.
The tricky part that I don't know how to solve would be to ensure that these custom steps are creating proper artifacts that are compatible with the downstream steps in the BMAD process. Would there need to be required input/output specifications to adhere to?
Why is this needed?
Solves the problem of not customizing first-party modules that could break compatibility in the future. Also, addresses the problem of having to clone all of the BMM phases as custom content which increases maintenance efforts.