用规格说明书驱动开发，让代码变成可生成验证的产物。
Spec-Driven Development:From Code to Contract in the Age of AI Coding Assistants
- 以规格书为源头，代码由其生成或验证，颠覆传统编码流程。
- 提出三种规格严谨度层级，适配不同开发场景与需求。
- 适合高可靠性系统开发，如嵌入式、企业级应用，需权衡成本。
AI编程助手的兴起重新唤起了一个古老理念：为何不将规格说明书而非代码作为软件开发的核心产物？规格驱动开发（SDD）反转了传统工作流，将规格说明书视为真理源，代码则作为生成或验证的次级产物。本文为实践者提供完整的SDD指南，涵盖其原则、工作流模式及支持工具。我们提出三个规格严谨度层级——规格优先、规格锚定、规格即源，并明确各层级的适用场景。通过分析从行为驱动开发框架到现代AI辅助工具包（如GitHub Spec Kit）等工具，展示规格优先理念的实际实现路径。案例研究涵盖API开发、企业系统和嵌入式软件，揭示不同领域如何应用SDD。最后，我们提出决策框架，帮助开发者判断何时采用SDD能带来价值，何时更简单方法更合适。
原文摘要 · Abstract (English)
The rise of AI coding assistants has reignited interest in an old idea: what if specifications-not code-were the primary artifact of software development? Spec-driven development (SDD) inverts the traditional workflow by treating specifications as the source of truth and code as a generated or verified secondary artifact. This paper provides practitioners with a comprehensive guide to SDD, covering its principles, workflow patterns, and supporting tools. We present three levels of specification rigor-spec-first, spec-anchored, and spec-as-source-with clear guidance on when each applies. Through analysis of tools ranging from Behavior-Driven Development frameworks to modern AI-assisted toolkits like GitHub Spec Kit, we demonstrate how the spec-first philosophy maps to real implementations. We present case studies from API development, enterprise systems, and embedded software, illustrating how different domains apply SDD. We conclude with a decision framework helping practitioners determine when SDD provides value and when simpler approaches suffice.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品；中文卡片由大模型生成，请以原文为准。