cross-posted from: https://programming.dev/post/49896390

I've used spec-kit and also rolled my own lighter version of the same idea. The framework matters less than the habit it forces, which is writing down what 'done' looks like before the agent starts. When I just prompt without that, I get something plausible that I then argue with for an hour. When the spec has acceptance criteria the agent can check itself against, most of that back-and-forth goes away. The caveat is that spec-kit can be heavier than a small change needs, so for quick work I'll write the criteria in a comment and skip the ceremony. Worth trying. For me the habit of writing the criteria first is what stuck, more than the tooling around it.