SPECMINE: A Large-Scale Corpus of Spec-Driven Development Artifacts
Source
Shyam Agarwal, Bogdan Vasilescu
Author
Shyam Agarwal, Bogdan Vasilescu
Date
Terms in this piece · Glossary
spec-driven development — Writing and agreeing the specification first, then having an agent implement against it — the spec, not the code, becomes the artifact you maintain.
Why it matters
spec-driven developmentWriting and agreeing the specification first, then having an agent implement against it — the spec, not the code, becomes the artifact you maintain.Full definition → now has an evidence base instead of vendor advocacy: a census of half a million spec files across 73k repos, tool-attributed, with the pull requests that turn a spec into code captured alongside them.
articleGrounding AI Agents in Contracts: An Empirical Evaluation of Spec-Driven Test GenerationMichele Tufano, James McClure, Jos\'e Cambronero, Runxiang Cheng, Sherry Y. Shi, Renyao Wei, Dorothy Chen, Franjo Ivan\v{c}i\'c, Livio Dalloro, Pat Rondon
articleSpecification-first convergence with an AI coding agent: a case study of dismantling a core architectural invariant across 189 files in a 717k-line codebase with no test oracle and no human code reviewJoel Abenhaim
articleCodeSpec: Dual Executable Specifications for Agentic Long-Horizon Feature DevelopmentPeiding Wang, Li Zhang, Fang Liu, Taichuan Li, Yinghao Zhu