I’ve been using AI coding tools for a time now, and its become clear that the approach to managing the AI coder is itself an application. I know this isn’t a revolutionary idea, but I’m interested in building something that suits my purposes.
Currently I have a dedicated role for each stage of the development :
– Epic Analyst
– Requirements Analyst
– Bug Analyst
– Architect
– Front-end Coder
– Back-end Coder
– Test Writer
– Documenter
– Reviewer
– Integrator
Each rule references documentation and standards for architecture, security, testing, coding practices etc, and they also each generate logs for their work.
I also have MemoryBank files that are updated and managed with each task.
I go through the process of switching each rule on and off as I go, and reflectively improving each rule after each execution, so they get better and better. However this is becoming tedious, and the absence of an orchestrator is getting frustrating.
Instead I am imagining a supporting application that sits alongside my AI Coder. It has a database where all my standards are maintained, where all of my documentation lives, and where each development “step” is in fact realized as an accessible pre-prompted AI.
As a consequence each build also generates this artifact that is used to manage and support the AI coder. It can be shared by multiple users building on the same code-base and therefore maintain a standard around development.
It is abstracted away from the AI coder, so enables migration across different coding tools.
It supports persistence, continuous improvement and versioning of all standards, documentation, and changes.
The interface would leverage MPC or A2A standards for integration with AI coders.
Anyway, something for me to work on one day when I ahve time!
Leave a Reply