Skip to content

Commit 46830cc

Browse files
committed
Use Specification by Example cover
1 parent b2f201c commit 46830cc

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

_posts/2026-05-13-executable-markdown-specs-agentic-coding.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,11 +61,11 @@ Generating a plan from a spec is useful. Keeping the spec correct as the system
6161

6262
That problem remains unsolved at scale.
6363

64-
## 3. The proven pattern already exists
64+
## 3. A proven practice already exists
6565

66-
![Tool-card image showing Specification by Example, BDD, Cucumber, Gauge, Gherkin, and Markdown specs as executable contracts](/assets/article_images/2026-05-13-executable-markdown-specs-agentic-coding/section-3-executable-contracts.svg)
66+
![Specification by Example book cover](https://m.media-amazon.com/images/I/61K4UV59xyL._SY522_.jpg)
6767

68-
The proven pattern already exists: **behaviour-driven, example-based specifications**.
68+
A proven practice already exists: **behaviour-driven, example-based specifications**.
6969

7070
This is the core idea behind BDD and the [Specification by Example](https://gojko.net/books/specification-by-example/) book:
7171

0 commit comments

Comments
 (0)