arXiv AI By Shyam Agarwal, Anmol Singhal, Andrew Macvean, Bogdan Vasilescu, Travis Breaux

Spec-Driven Development as Prescribed and as Practiced

Read the original on arXiv AI →

Spec-Driven Development (SDD) is a practice where developers and AI coding agents write specifications to guide software implementation, aiming to preserve the intent behind natural‑language instructions. This study analyzes SDD through Reddit discussions, interviews with 21 practitioners (including eight tool makers), and a large corpus of 470,795 spec files from 73,030 GitHub repositories. Findings reveal that while specs often include implementation details that aid agents, they also risk decay; tool-specific structures influence perception, and benefits vary between individuals and teams, with SDD mainly used for new features and involving higher planning and review costs.

Machine-generated by The Flow from the publisher's headline and feed description — not written or checked by a human. The full article lives at arXiv AI.

arXiv AI
Sep 3

SpecMine: A Large-Scale Corpus of Spec-Driven Development Artifacts

SpecMine is a large-scale corpus that documents Spec-Driven Development (SDD) artifacts in public GitHub repositories. It includes a broad census of 470,795 spec files from 73,030 repositories linked to 17 tools, a focused census of 98,574 Kiro layout files from 12,910 repositories, and a sweep of 5,992 pull requests across 581 repositories that modify specs. The dataset provides enriched metadata, full commit histories, parsed document structures, and over 2.4 million typed references connecting specs to code, sibling documents, PRs, branches, and issues.

By Shyam Agarwal, Anmol Singhal, Travis Breaux, Bogdan Vasilescu
Hugging Face Trending Papers
Aug 20

From Agent Behaviour to Agent-Friendly Documentation: An Empirical Study of How Coding Agents Discover, Read, and Write Technical Documentation

The study investigates how autonomous coding agents interact with technical documentation, analyzing 557 coding sessions and 33,097 pull requests. Findings reveal that agents primarily engage with agent-facing artefacts, show weak links between documentation consultation and code editing, lack explicit validation sequences, and tend to consult documentation after code changes. The authors propose a two‑lobed cycle model of agent‑documentation interaction and challenge assumptions about actionability and verifiability of agent‑friendly documentation.