Documentation seems a bit misleading

[cleankode]

Intro states the following two points which I think seems a bit of stretch and misleading:

1. For decades, code has been king — specifications were just scaffolding we built and discarded once the "real work" of coding began.

Isn't code still the king after all? And more over, spec although evolves as product changes over time as it should and always the case since requirement evolves over time anyways, i don't think it was thrown away especially as coding begins.

2. Spec-Driven Development changes this: specifications become executable, directly generating working implementations rather than just guiding them.

This too, spec is still a spec and its really not an executable that you can ship. Yes, AI uses it to help scaffold the code helping dev's productivity but spec by no means is executable at all. This too seems a stretch and misleading.

Both taken here. I think, its good to keep an objective look at what things are and present them as such than presenting them with a bit of stretch that misleads reader.

---

Spec-Driven Development flips the script on traditional software development. For decades, code has been king — specifications were just scaffolding we built and discarded once the "real work" of coding began. Spec-Driven Development changes this: specifications become executable, directly generating working implementations rather than just guiding them.