Originally published at tddbuddy.com.
Gherkin was never really a test format. It was a coordination format.
The testing part was almost incidental, a side effect of needing the artifact to be executable so it couldn't silently drift. The actual purpose was something else: getting product, QA, and engineering to agree, in writing, on what the software was supposed to do. The feature file was a treaty document between three roles with different vocabularies, different calendars, and different incentives.
Once you see that, the decline makes sense. Treaties live and die with the coordination cost they were built to reduce. When the cost changes, the treaty becomes ceremony.
This is the second post in a three-part arc on TDD in the agentic era. The first, "TDD Already Does BDD, Without the Gherkin", made the **craft case* at the code level: disciplined TDD with builders, factories, and mock-driven collaboration tests already delivers what BDD promised. This post makes the org case. Even teams that legitimately needed BDD for coordination reasons are watching that need get repriced. The third, "The Bar for TDD Just Moved", names the new expected level and why agentic coding makes it non-negotiable. If you were paying the tax for craft reasons, the first post says stop. If you were paying it for coordination reasons, this one says notice that the coordination just got cheaper. The third says what you now need in its place.*
