What is the difference between vibe coding and spec coding?
Vibe coding gives an AI agent a plain-language prompt and judges the result by whether it runs and looks right, so the model makes the product decisions while it writes the code. Spec coding writes the outcome, non-goals, acceptance criteria and evidence down first, so people make those decisions and the agent builds against them.
Is vibe coding bad?
No. In our recorded runs, one-line prompts usually produced working code on small repos. The risk is that the same prompt can produce different products on different runs, and nobody reviews those decisions before they ship. It suits prototypes and exploration, not changes to money, permissions, data or shared APIs.
Is spec coding the same as spec-driven development?
Yes, in practice. Spec coding, spec-driven development and spec-first development all mean writing a short spec for a change before an AI agent implements it. Tools such as Spec Kit, OpenSpec and Kiro add structure around that idea; our tool comparison covers the main ones.
Does spec coding slow teams down?
The run itself barely changes: in our tests a spec run cost a few cents more than a one-line prompt and took somewhat longer (Opus 5.5 averaged 63 seconds instead of 47). The real cost is the time a person spends writing the spec, usually minutes to an hour for a typical change, which is paid back if it prevents one rework cycle.
When should I switch from vibe coding to spec coding?
Switch when the output will change production behavior, money, permissions, user data, a database schema, a public API or a shared helper, or when people who were not in the chat will maintain the code.