Composer is leveraging bf luis:build and bf qna:build to do luis publishing and qna publishing.

Besides publishing, luis:build and qna:build do another work that is generating a bunch of .lu.dialog, .qna.dialog, .lu.qna.dialog, which is

• built into it's core interface and run together with this build command.
• it's using a fixed set of template to generate

The direction of Composer is heading is Composer would like to take control of those declarative dialog generation part which will allow user to author those dialogs to enable\disable certain features. And also make it friendly to CI/CD environment, so that the composer bot can be integrated to CI/CD pipeline easily.

The ask to cli, is that we should decouple the declarative dialog generation out from it's core capability or at least make it optional.