Continue with your current work on toeb/cmakepp repo. Whatever feature/issue we can help with, refer to your repo, use PRs, etc. Again, let's decouple bii completely from cmakepp
Enter on biicode/biicode repo and share your thoughts there. The code is at biicode/client and biicode/client repos. Feel free to discuss any existing feature (please be critic with our work!), suggest new ideas, etc. Even you will be able to implement your own features (That depends on your python skills only, and the time you have to learn how bii works under the hood)
Since bii runs on top of the build system, it has many information regarding dependencies that you doesn't have at the cmake level. For example, in a CMakeList.txt you cannot "look down" and see who is depending on you, but bii knows perfectly the complete dependency graph of the project. Consider what this kind of information can do for cmakepp features. We first should think about how the API between bii and the cmake side should look like (Again, ask biis about how bii works).