Staging environment

Spec-Driven Development: Coding Agents That Ship

Hosted by Ehsan Gazar

59 students

In this video

What you'll learn

Write an executable spec, not a prompt

Turn vague intent into an interface, acceptance tests, and constraints the agent has to satisfy.

Guardrail the agent below its output

Set allowed paths and a test gate so a plausible diff cannot merge until it is actually correct.

Leave with a template for your repo

Take the spec-driven starter and point it at your own codebase in about ten minutes.

Why this topic matters

Coding agents produce a plausible diff for almost anything, and plausible is not mergeable. As agent-authored volume grows, review becomes the bottleneck, and most teams still prompt ad-hoc and hope. This lesson shows the fix: an executable spec plus a guardrail file that constrain the agent to what correct means in your codebase. You leave with a template you point at your own repo the same day.

You'll learn from

Ehsan Gazar

Staff Software Engineer at Tipalti

I'm a Staff Software Engineer with 16 years building and scaling production systems across fintech, SaaS, and enterprise software. I've made hundreds of architectural decisions in systems that had to survive real traffic, incidents, and org politics.

I've run 500+ mentorship sessions with senior engineers at a 5.0 rating, helping them close the gap between writing code and thinking at the architectural level. I've also taught 10,000+ students and distilled what separates engineers who get promoted from those who stay stuck.

I'm not an academic. Every framework here comes from real decisions or mistakes I had to recover from. I’ll teach you to think like a Staff Software Engineer: not “what’s the right answer,” but “what are the trade-offs, and what survives contact with reality.”

See all products from Gaz

Go deeper with a course

Production-Ready Systems with LLMs and Agents: An Intensive for Engineers
Ehsan Gazar
View syllabus