I think, at least in an MVP, the focus should be on making it easy for frameworks to ship starter templates to users to give users the dependencies, stubs etc that they need. This use case diverges from user-driven templates, in which a user develops their own template for re-use (and possibly shares it with others in a more ad hoc fashion). That's what projects like kickstart and cookiecutter seem better aimed toward.
I also think the MVP should just not try to support interactive functionality at all. The user passes the name of their project in the command and gets a new project with that name, no y/n questions about what things they want set up (at least for now).