Do I understand correctly that this software does not yet have many users? Are you trying to set this software up as an open source project? If so, you might want to word your announcement differently. For example, your points 3, 4, and 6 sound like a "help wanted" ad. On the other hand, your points 1, 2, 7 are the kind of things that interested users would contribute to an open source project anyway (bug fixes, enhancements, etc.). A long list of "things that need to be done" is the kind of thing one might write to an established user base, but it's not marketing material :-) To put it a little more plainly, until you've actually got the users, you're on your own...

As a hypothetical new user, I'm missing some kind of "getting started" guide, or even just a quick example (like a typical Perl module's SYNOPSIS section). I gotta say that the current summary is difficult to read, it needs less angle brackets and better formatting. Also, ease of installation is important nowadays, the lower the hurdles the better :-) For example, why not publish the software to CPAN in the App:: namespace? New users could type cpan App::bld, then perldoc bld, and get started much easier.

Lastly, I don't understand the relationship of this tool with git, SVN, systemd and the kernel. Does it somehow enhance those projects? All I'm getting at the moment is that it replaces their build process, but why? How is it better? I think a better description there would help.