The first bit that really annoyed me was the lack of tracking prompts. There are lot's of little inputs that inform the what the system should do and it seems to be very ephemeral. I've since started tracking the prompts in the codebase.
Another observation is that if you want to have good agentic output, you need to provide lot's of signal into the context window. It seems that being disciplined about what goes into the context window is key. Using AI to generate input files can be dangerous because it adds entropy/noise to the human signal.
One practice I have started to do is organize my projects in a certain way:
- /specs - Pure human signal such as product vision, requirements, designs, etc. - /prompts - Agentic recipes such as skills, jobs, AI patterns. - /references - References that can be used in the context window (brand assets, documents, figma exports, data sets, etc.) - /plans - The agentic plans for a project. Ususually there are iterations on these plans. - /build - The codebases and traditional mono repos that are built from plans and prompt interactions.
(I have the above with an AGENTS.md as a public GH repo at rekallai/craft)
I'm not fully satisfied yet with this structure. I think /plans is a bit of a misnomer the more I use it (e.g. I often have reports that I want to generate on top of the codebase or other data sets).
I am really curious how other developers (that embrace agentic coding) here organize their projects. My goal is to standardize this in my teams.