tag · 8 essays
All essays tagged spec-driven-development.
My personal delivery pipeline runs on three Claude agents, three nested loops, and two explicit human approval gates. The gates sit where judgment is cheapest and most consequential, and the real bottleneck moved upstream to the clarity of the ask.
★A field report on building Inkwell, a pure-CSS design system that turns taste into repeatable constraints for people, teams, and coding agents.
A year of writing, one argument, and a working theory of where software is going
★Code used to be the durable asset. In an agentic SDLC, that changes. Code becomes the regeneratable output of a system that runs on something more important: a clear, versioned, reviewable specification. That shift changes what engineering organizations invest in, how they govern delivery, who they hire, and what they actually ship.
★The strategy posts say AI software development is a system. Here is the working loop I run inside that system: a refined specification, a layer of standards, and a coordinated set of specialists doing the work.
★After thirteen months of daily Claude Code use, I stopped treating AI coding as a prompt discipline problem and started treating it like an engineering system: configurable, layered, observable, and built to learn.
Every tool in your product development life cycle is now an AI agent trying to do everything. Here is how to stop the chaos, draw the right boundaries, and build an orchestrated pipeline that actually works.
★A decade-old side project, six major features, one week. How spec-driven AI-assisted development compressed months of work into a focused sprint on a real codebase with real constraints — and where the AI got it wrong.
browse other tags