Comment by vidarh

I'm building an "improvement agent" that kinda embraces that. It starts out by running exploration across a codebase or set of documents and extract possible goals, and a vision from that. It then starts producing improvement plans (tickets, effectively). If it gets things wrong, I nudge it in the right direction, and it gets incorporated into revisions of the documents via a review stage. It's an experiment for now, but it is both doing semi-self-directed implementation and helping me identify where my thoughts haven't been crystallised enough by seeing where it fails to understand what I want.

I'm not just running it on code, but on my daily journal, and it produces actionable plans for building infrastructure to help me plan and execute better as a result.