One thing I'd add from the product side is that the reason we went spec-driven is because we observed (and personally experienced) desire to build FAST but then hit a wall trying to make it better.
The problem stems from nobody sharing a good document of "what this is what the app is supposed to do." The codebase became the only record of intent, and it was written by AI.
Spec-driven development fixes that. You can hand it to a new teammate, read & understand it, and actually understand the system. The agent reads the same document and generates from it. When something needs to change, you change the spec, not a pile of files you didn't write that become messy later.
We're really early and want feedback from people actually building things. If you try it, please share your experience!
One thing I'd add from the product side is that the reason we went spec-driven is because we observed (and personally experienced) desire to build FAST but then hit a wall trying to make it better.
The problem stems from nobody sharing a good document of "what this is what the app is supposed to do." The codebase became the only record of intent, and it was written by AI.
Spec-driven development fixes that. You can hand it to a new teammate, read & understand it, and actually understand the system. The agent reads the same document and generates from it. When something needs to change, you change the spec, not a pile of files you didn't write that become messy later.
We're really early and want feedback from people actually building things. If you try it, please share your experience!