SDAD: Spec-Driven Agentic Development for the AI-Native SDLC
Summary
The paper formalizes Spec-Driven Agentic Development (SDAD) to restructure the software development lifecycle with AI, emphasizing precise specifications and multi-agent verification for disciplined agentic speed.
View Cached Full Text
Cached at: 08/24/26, 04:04 AM
# SDAD: Spec-Driven Agentic Development for the AI-Native SDLC Source: [https://arxiv.org/abs/2608.20341](https://arxiv.org/abs/2608.20341) [View PDF](https://arxiv.org/pdf/2608.20341) > Abstract:Frontier coding agents backed by large language models with context windows from hundreds of thousands to millions of tokens are restructuring the Software Development Life Cycle \(SDLC\)\. Rich context handling and multi\-step reasoning now allow substantial Functional Requirement Documents \(FRDs\) and repository context to be ingested in a single workflow, making specification quality the execution fuel for autonomous delivery\. This report formalises Spec\-Driven Agentic Development \(SDAD\) as a synthesis of disciplined up\-front formalisation and high\-velocity implementation: intent capture, machine\-readable specification, agentic synthesis, and independent multi\-agent verification under human sign\-off\. We revisit the historical pendulum between Waterfall and Agile, introduce AI\-code as a fourth production paradigm, and compare Human\-Agile \(circa 2020\) with Agentic\-SDAD \(circa 2026\) across artefacts, cadence, accountability, and security posture\. Beyond process description, we extend the model to team role metamorphosis \(engineer, QA, platform, and product functions\), quantitative governance \(Ambiguity Tax, Spec Fidelity, SER, and TCI\_agentic with repair multiplier phi\), and pragmatic adoption via hybrid estimation and a staged migration blueprint\. Industrial and research evidence on AI\-augmented testing and verification is integrated to motivate separation between synthesis and release authority\. Overall, the paper argues that agentic speed does not eliminate engineering discipline; it relocates discipline upstream into specification precision, explicit gates, and auditable provenance\. ## Submission history From: Vu Hung Nguyen \[[view email](https://arxiv.org/show-email/652dbda5/2608.20341)\] **\[v1\]**Tue, 5 May 2026 22:51:56 UTC \(112 KB\)
Similar Articles
Traditional SDLC vs Agentic SDLC
This article compares the traditional Software Development Life Cycle (SDLC) with the emerging 'agentic SDLC' approach, which incorporates AI agents into the software development process.
@PawelHuryn: Spec-Driven Development was always BS. It never worked for humans. Waterfall lost to agile because you discover what yo…
This tweet argues that Spec-Driven Development is ineffective for AI agents, drawing parallels to the failure of waterfall methodology in software development. It advocates for 'intent engineering'—communicating context, strategy, and constraints to agents to handle unknown unknowns.
The AI-Native SDLC playbook (47 minute read)
The article presents an AI-native Software Development Lifecycle (SDLC) playbook, advocating for integrating AI across all stages to overcome bottlenecks and enhance productivity in software development.
entire SDLC agentic system that beats claude code
AutoDev Studio is an open-source, model-agnostic multi-agent SDLC harness that orchestrates a chain of agents to automate the software development lifecycle, reducing costs by 7–75% compared to Claude Code for similar tasks.
The Digital Apprentice: A Framework for Human-Directed Agentic AI Development
This paper presents the 'Digital Apprentice,' a framework for scalable and safe agentic AI in which autonomy is earned incrementally through observational learning, human authorization, and continuous alignment correction. It introduces ADAPT, an inference-time control plane that operationalizes graduated autonomy tiers and converts human corrections into reusable preference data.