My main gripe with AI-assisted software development has always been its inconsistency. Things would go smoothly for long stretches, only to be followed by a sudden nosedive in quality and outcome. Upon closer inspection, the culprits were usually “context” and complexity.
The OpenSpec approach (or Spec-Driven Development) isn’t exactly new, but it’s a game-changer for AI. It helps the model keep only the strictly relevant information in its memory—its context window. By using a system of agents (Agent OS) and hooks, I can finally force Claude Code into sticking to a rigid workflow.
For example, I kick things off with a /user-story, a /feature, or a /bug, which then triggers a specific chain of skills. Hooks prevent the AI from jumping the gun—like starting to modify code before the necessary tests (TDD-RED) are written.
I don’t develop this framework as a standalone project, but rather inside my actual active projects. I then regularly use the Agent OS OpenSpec Framework to update itself based on these improvements, and conversely, propagate those core updates back to the individual projects. Naturally, I don’t do any of this by hand — I let Claude Code handle the heavy lifting.