[mrloba]

I really doubt spec driven development is gonna last. As before, creating working software and iterating on it is faster and makes it easier to understand what you thought you wanted but don't, even if it's vibe coded. So, hello agile, welcome back.

[jeremyjh]

The point is the agent writes the specs and the human reviews and revises or asks for another rewrite that takes 90 seconds or less. So specs are both cheaper and better than anything I've seen before. They still get a lot wrong and it is hard to review them very carefully, but its easier than reviewing code to suss out design intent.

[ytoawwhra92]

The point is that sometimes you don't know the spec is wrong until you've built the software and it's being used.

[9dev]

Still though, that cycle can be iterated many times in a single day. Write a spec, let the agent build it, use the software, evaluate results, repeat.

[ytoawwhra92]

Yes, that's agile software development.

[9dev]

No, not quite. The specifications we use for agents make any ticket written before them pale in comparison. That enables a hybrid workflow that is both spec-driven and "agile", in the sense that you're doing very rapid development cycles.

[zelphirkalt]

Until the agents start touching things that already worked well before and break them.

[jeremyjh]

They do need a competent developer operating them. That has nothing to do with whether nor not specs have value.

[DeathArrow]

I think there is some good middle ground between spec driven development and iterations, like Compound Engineering. https://github.com/EveryInc/compound-engineering-plugin