I think of it this way. I believe the CLI should be able to reach out and access templates, rather than only having the templates generated inside the CLI itself (in code) which poses maintainability and extensibility challenges.
I started to look at the CLI project source as I had a below average experience a few weeks ago when I revisited Aurelia. My expectation of tooling is that when I install and run the commands it should ‘just work’. This was not my experience. On looking into it, and a few fixes later, I saw that the templates are actually generated conditionally and thought maybe it would make sense to have the template code external to the CLI. This led to these experiments. So my aim was not a “super CLI” rather than having a more maintainable and possibly extensible way of handling Aurelia CLI templates.