---
title: "Discussion on \"Spec-Driven Development: Capture Intent Before You Build\" | Hashnode"
description: "Discussion on \"Spec-Driven Development: Capture Intent Before You Build\". AI has reduced the cost of implementation. It has not reduced the cost of misunderstanding. Why specifications matter more than ever in AI-assisted software development."
url: "https://hashnode.com/posts/spec-driven-development-capture-intent-before-you-build/6a4c247a8194c19eb51cdddd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Spec-Driven Development: Capture Intent Before You Build](https://remcokoedoot.hashnode.dev/spec-driven-development-capture-intent-before-you-build?utm_source=hashnode&utm_medium=feed)

AI has reduced the cost of implementation. It has not reduced the cost of misunderstanding. Why specifications matter more than ever in AI-assisted software development.

Jul 6 · 5 min read · remcokoedoot.hashnode.dev  
Read the article

-   [#software-engineering](https://hashnode.com/tag/software-engineering)
-   [#spec-driven-development](https://hashnode.com/tag/spec-driven-development)
-   [#ai](https://hashnode.com/tag/ai)
-   [#architecture](https://hashnode.com/tag/architecture)
-   [#agile](https://hashnode.com/tag/agile)

## Written by

[Remco Koedoot](https://hashnode.com/@remcokoedoot)

@remcokoedoot · Amsterdam, Netherlands

  
[View profile](https://hashnode.com/@remcokoedoot)

On domain understanding, engineering discipline, and moving fast without losing control

Software engineer and architect. For more than twenty years I’ve been building software for complex domains. Along the way I’ve learned that good software starts with understanding the domain, not the technology. This blog is where I share ideas about software architecture, engineering discipline, AI-assisted development and the lessons learned from building systems that have to work in the real world.

## Responses 4

Markdown supported · ⌘↵ to post

[Adam Lewis](https://hashnode.com/@nark3d)

[Jul 10](https://hashnode.com/posts/spec-driven-development-capture-intent-before-you-build/6a4c247a8194c19eb51cdddd/comment/6a5101a44197470861c54a93)

The clarification step is the one I see skipped most often, so it is good to see it named as work rather than overhead. I keep the questions and their answers in the spec itself, and the agent checks back against them as it builds. A surprising amount of review argument disappears when the ambiguity was settled in writing first.

[Remco Koedoot](https://hashnode.com/@remcokoedoot)

[Jul 10](https://hashnode.com/posts/spec-driven-development-capture-intent-before-you-build/6a4c247a8194c19eb51cdddd/comment/6a5101a44197470861c54a93#reply-6a5108dd19188bcf12ed3a33)

Adam, that's a good point. Keeping the questions and their answers in the specification makes it a living reference instead of something everyone read once and then worked from memory.

I've also found that many code review discussions aren't really about code. They're about intent that was never made explicit.

[Adam Lewis](https://hashnode.com/@nark3d)

[Jul 12](https://hashnode.com/posts/spec-driven-development-capture-intent-before-you-build/6a4c247a8194c19eb51cdddd/comment/6a5101a44197470861c54a93#reply-6a535deb40bdbdb240c71f41)

Most of the review arguments I've sat through were two people discovering they'd assumed different requirements, so settling that in the spec first has cut most of them off. I've written up how I approach it here: [https://prickles.org/tenet/spec-first-execution/P2](https://prickles.org/tenet/spec-first-execution/P2)

[Remco Koedoot](https://hashnode.com/@remcokoedoot)

[Jul 15](https://hashnode.com/posts/spec-driven-development-capture-intent-before-you-build/6a4c247a8194c19eb51cdddd/comment/6a5101a44197470861c54a93#reply-6a57a445f2b4831c26f5f5a0)

Read through it. The "most popular implementation, not what the business needs" line is exactly the failure mode I mean. And you've already pre-empted the obvious objection: the risk isn't AC first, it's AC without the conversation. Thanks for the pointer btw. Bookmarking the rest of your canon.
