Those checked-in specs become the requirements for the system. So the next time you ask the AI to make a fix, it can use those specs as part of the solution and not break another requirement. Basically the code underneath keeps getting rewritten over and over, but that doesn't matter as long as it hits the required specs.
replyDo you rewrite the specs with new requirement changes if they've already been implemented? How do you supercede a spec?
replyI've been using LLMs daily and I spun up a few spec driven flows once or twice but like the person above I think the code is the source of truth.
Also why wouldn't you use TDD to enforce the 'spec' then?
I value traceability, and I value understanding the "why" of the code. For me, the prompts are useful for both.
reply