You decide what correct means
Breakspec suggests rules in plain English, like “the shares add up to the bill”, and you keep the ones you agree with. Your agent can suggest rules but can’t approve them.
Compare · Checked 12 October 2026
Your coding agent can write tests, and you should keep them. The catch is that the same agent wrote the code. If it misunderstood what you wanted, its tests make the same mistake, and they pass.
Breakspec suggests rules in plain English, like “the shares add up to the bill”, and you keep the ones you agree with. Your agent can suggest rules but can’t approve them.
The agent tests the four or five examples it came up with. Breakspec tries hundreds, then shows you the simplest one that breaks, like split_bill(1, 2).
If the agent “fixes” a bug by special-casing the one example that failed, or edits a rule so it passes, Breakspec flags it and doesn’t count it as fixed.
| Your agent’s own tests | Breakspec | |
|---|---|---|
| Who writes them | The agent that wrote the code | The agent suggests rules, you approve them |
| How many examples | A handful the agent picked | Hundreds, including the awkward ones |
| If the agent misunderstood you | The tests misunderstand too, and pass | A rule fails and shows you an example |
| Can the agent edit them until they pass? | Yes | No. Changes to rules are flagged |
Keep them. Add Breakspec for the rules that matter, so the agent isn’t the only one checking its own work.