The Paperwork Outweighed the Product: What Testing My Own Pipeline Cost

Part 7 of Building My Agentic Workflow in Public. Part 6 said do not be obedient, verify, because your own context window is small. This is the first time I turned that rule on my own process. Over six parts I built a pipeline that can design, plan, and ship a batch of features mostly on its own. Then I finally pointed it at two real repos, back to back, on the same day. One of them took about ten hours and burned close to ten million tokens to ship roughly five features. I sat with that for a minute. Ten hours. Ten million tokens. Five features. ...

Read blog post ›
aiagentic-workflowclaude-codeguardrailsai-toolsbuild-in-public

Two Ways to Run a Loop: Portable Agents vs Dynamic Workflows

Part 5 of Building My Agentic Workflow in Public, and the open end of it. Part 4 got me an autonomous build loop. This one is about a fork I am standing at right now, with no final answer yet. The last four parts had endings. This one has one, but a provisional one. I am still in the middle of it, and the whole reason I write these in public is to think out loud while the question is still live. ...

Read blog post ›
aiagentic-workflowclaude-codearchitectureai-toolsbuild-in-publicmulti-agentautonomous-ai

From Prompts to a Process: Making Claude Code Repeatable

This is Part 1 of Building My Agentic Workflow in Public, a series on how I actually work with Claude Code day to day. It starts with the problem from AI Fatigue: the tools got faster, my brain didn’t. This post is the first thing I did about it. For a while, every session with Claude started the same way. I re-explained the project. I re-explained how I like things named, where files go, what “done” means. The model was capable. I was the bottleneck, retyping the same context over and over. Then the session ended, and all of it died with it. ...

Read blog post ›
aiagentic-workflowclaude-codeproductivityai-toolsbuild-in-public