Through the last few weeks, I've distilled my nearly 20 years as a software engineer, technology leader, data scientist, hackathoner and craftsman into a minimal set of tools that I use to push swarms of agents to implement all sorts of projects.
It's Claude plugin that contains a set of skills and agents that emulate the different roles / skills I look for in a team of engineers and presents an opinionated approach to the SDLC. It's not a reinvention of the wheel -- this is simply my preferred way of interacting with code as a team, built out using Claude as a stand-in for the individuals that make up a successful engineering team.
There's a white paper on the process in the repo under /docs.
NOTE: this does _not_ cover requirements definition as a whole. There are definitely some useful tools here to help talk through a problem and break that problem down into smaller tasks, but the idea is that these tools are focused on the actual process of building software, not defining it.
Let me know what you think! Fork it, open a PR, throw an issue at me. It's definitely WIP, but this, along with a few other tools I've built around tmux / juicing up my terminal, has increased my productivity immensely. I hope it does for you too!
Through the last few weeks, I've distilled my nearly 20 years as a software engineer, technology leader, data scientist, hackathoner and craftsman into a minimal set of tools that I use to push swarms of agents to implement all sorts of projects.
It's Claude plugin that contains a set of skills and agents that emulate the different roles / skills I look for in a team of engineers and presents an opinionated approach to the SDLC. It's not a reinvention of the wheel -- this is simply my preferred way of interacting with code as a team, built out using Claude as a stand-in for the individuals that make up a successful engineering team.
There's a white paper on the process in the repo under /docs.
NOTE: this does _not_ cover requirements definition as a whole. There are definitely some useful tools here to help talk through a problem and break that problem down into smaller tasks, but the idea is that these tools are focused on the actual process of building software, not defining it.
Let me know what you think! Fork it, open a PR, throw an issue at me. It's definitely WIP, but this, along with a few other tools I've built around tmux / juicing up my terminal, has increased my productivity immensely. I hope it does for you too!