An English Concise Overview of Spec-Driven Development ― Released on Zenodo

in

Introduction

A few weeks ago, I wrote two posts on this blog: “What is Spec-Driven Development — its three technical elements, four principles, and seven processes,” and “Spec-Driven Architecture: extending Spec-Driven Development into management.”

Following that thread, I’ve now published an English-language concise overview of the methodology on Zenodo. This post is a short report on that.

The paper compresses the Japanese book Spec-Driven Development: A Practical Introduction (Nikkei BP, 2026) into a single, self-contained English primer. It carries a DOI and is published under CC BY 4.0 — citation, translation, and reuse are all welcome.

What I wrote

The title is “Spec-Driven Development: A Concise Overview ― An English-Language Primer on a Methodology that Treats the Specification as the Primary Artifact.”

It walks through the same backbone as the book — three technical elements, four principles, and seven processes — structured in vocabulary and framing that English-speaking readers can use directly.

  • Three technical elements ── Markdown / Git & GitHub / AI
  • Four principles ── Living documents / Single source of truth / Change and iteration as the default / AI-driven cost reduction
  • Seven processes ── Principle setting → Planning & requirements → Design planning → Task decomposition → Implementation → Verification & acceptance → Migration & operation

The book’s central message — combining the stability of waterfall with the flexibility of agile, reconciled by AI — fits compactly into this single English piece.

Why I wrote it in English

The Spec-Driven Development conversation has been growing fast in English-speaking circles. GitHub and several others now ship implementations and frameworks under the “Spec-Driven” label.

Meanwhile, the version of the methodology I’ve been systematizing through the Japanese book has been hard for English-speaking readers to reach. We’ve been using the same words without aligning on what they mean, or how the threads relate.

This paper is meant to close that gap — a concise overview, written so that the English-speaking SDD community can engage with the Japanese line of thinking directly.

It also serves as a foundation for receiving my recent piece on Spec-Driven Architecture — extending the methodology into management — in English. Foundation (this paper) and application (the architecture post), read side by side.

Where to read it

The paper is free to read on Zenodo:

CC BY 4.0 means as long as you preserve the credit, you may translate, quote, and reuse the work freely — commercial use included. For academic citations, please use the DOI (10.5281/zenodo.20519019).

What’s next

This English preprint is a first step in carrying the work I’ve been doing through the Japanese book, blog, OSS, and YouTube to English-speaking readers.

I plan to keep expanding the English-language output — foundations → applications → case studies — bit by bit.

References