as a builder, I have various projects going all the time and the all-the-time driver is claude, with chatgpt/codex creeping up in usage, and various other models that I’ll write about later.
every week – shoot – nearly everyday there is updates and improvements, so embracing the new and the change with these tools is the way to go. yes its all about tokens, and that continues to ramp up exponentially as the frontier models burn thru them like high-test gasoline.
how do I track everything in the age of various contexts / full-stacking / solo-builder-prenuering?
ai
š
all jokes aside, a handful of the thing I do
- plan everything – like really – work thru initial idea by creating document(s) of what you are doing. I built my scaffolding
grovv-stackto walk me thru my idea and build out a brief, product spec, tech spec, and further documents to lay foundations. - use an issue/item tracker of some-kind – text file in the repository, GitHub issues, linear, whatever … make sure you can track things per project.
- then of course connect your model of choice to that tracker. chat to go thru your project to summarize status, re-focus priorities, or any way you work best.
- I have agents and skills that make sure to keep documentation & the tracker up-to-date, and in some cases also have a simple HTML “board” listing out everything – including a focus and blocker list. will have to share some of this in future post
sounds simple, but it goes a long way to have your knowledge graph documented instead of just figuring it out as you go (whatever works best for you tho, I engineer.
have fun
š
DĆøn
















