So let's talk about Busy again. It's come quite a ways, in the 6.5 years of coding time since... two weeks ago.
Right now, I'm thinking of it as the most intelligent cli there's ever been. Use it, like a terminal interface. It handles design discussions, implementation phases, deployment, and metrics data on code bases written in Go.
It's designed to work with a formal high velocity methodology I came up with called "Robot Kanban" that wraps a kanban style iterative process around a velocity scheme that will make your head spin. At least today.
I think the data driven approach I'm using solves all the problems with doing that. Every file loads up with cognitive and complexity metrics, which you can review at a glance, and understand where your modules and individual sections of code need rethinking or refactoring.
And it uses state of the art pattern matching to use your file system as a vector database, with distance patterns that allow for complex searches using fuzzy algorithms and either tight or loose pattern matching. Tracking down circular dependencies and code quality issues has never been simpler. This is the only right way to do it.
The cool thing about doing it this way is all the extremely formal ISO documentation that just manifests as a result of using the system.
Reports, proposals, QA, post mortems, all of it. In my 30 years of working in code, I've never seen a human team consistently produce formal documentation this good.
It's truly fucking perfect, and provides a complete audit trail, and assessment mechanism that would be next to impossible to do today by hand.
Basic client works.
The whole thing is powered with IRC style commands like /git, /deploy, /regenerate, /tellmeajoke, and so on.
Infrastructure package for logic trees, some tokenizing, and complexity mapping still needs to be converted from PHP (where I prototyped it over the weekend) into Go.
QA system needs to be moved from the earlier version of the project into the current one.
To run it, all you're going to need is a claude API key.
Support for multiple models after mvp.
This is an entire paradigm shift.
Please don't be mean to your project managers when you tell them they're obsolete.
More this weekend.