My biggest coding headache this weekend was managing the docs, specs and plans
Documentation is the code you write when working with LLMs. The Agent is the compiler. Specs used to be written once and ignored. With LLMs in the loop, they become shared state - drafted, revised, and reconciled by humans and agents every time the system changes. Developer work in LLM-assisted development increasingly lives upstream of the editor: brainstorming, writing plans, and authoring skills. In practice, most of my time goes into shaping the problem so agents can take it from there—implementing features, generating tests, drafting documentation, and carrying parts of the SDLC forward without constant hand-holding. That upstream focus produces a growing body of specification: documents that explain not just what the system does, but why it is built the way it is. Every new brainstorming session, plan, or skill tends to spawn new docs and force updates to existing ones—merging overlapping specs, splitting bloated documents into sharper scopes, or retiring plans that no longer m...
