Specification-Driven Development

In specification-driven development, code becomes an implementation detail rather than the source of truth. A human-written specification should capture the what and why before AI touches implementation. Generated implementation should be verified against the specification rather than only compilation or superficial tests. Specifications should capture intent, architecture, constraints, quality expectations, tests, security requirements, and task sequencing. The proposed fix is to change the primary artifact of development rather than simply use less AI by default.