Update from Sync Service
This commit is contained in:
58
wiki/Resources/方法论/SDD规格驱动开发.md
Executable file
58
wiki/Resources/方法论/SDD规格驱动开发.md
Executable file
@@ -0,0 +1,58 @@
|
|||||||
|
---
|
||||||
|
created: 2026-04-21
|
||||||
|
updated: 2026-04-28
|
||||||
|
type: concept
|
||||||
|
tags: [SDD, 规格驱动开发, AI-Engineering, spec-first]
|
||||||
|
---
|
||||||
|
|
||||||
|
# SDD 规格驱动开发
|
||||||
|
|
||||||
|
> 整理自 Thoughtworks Radar、GitHub spec-kit、OpenSpec 等 11 份资料
|
||||||
|
|
||||||
|
## 核心定义
|
||||||
|
|
||||||
|
**规格驱动开发 (Spec-Driven Development)**:以结构化的功能规格说明为起点,再经过多步骤分解为更小片段、解决方案和任务的开发工作流。
|
||||||
|
|
||||||
|
### 核心理念
|
||||||
|
- 规格说明优先于代码 (spec-first)
|
||||||
|
- 规格是人与 AI 的共同真相来源
|
||||||
|
- 代码是派生产物,规格是主制品
|
||||||
|
|
||||||
|
### 核心公式
|
||||||
|
|
||||||
|
```
|
||||||
|
传统模式:思考 → 编码 → 文档
|
||||||
|
SDD模式:规格 → 生成 → 验证
|
||||||
|
```
|
||||||
|
|
||||||
|
## 规格层级
|
||||||
|
|
||||||
|
| 层级 | 说明 |
|
||||||
|
|------|------|
|
||||||
|
| Spec-first | 任务开始时写规格,完成后可丢弃 |
|
||||||
|
| Spec-anchored | 任务完成后保留规格,后续演继续使用 |
|
||||||
|
| Spec-as-source | 规格是持续维护的主制品,代码完全由规格生成 |
|
||||||
|
|
||||||
|
## 工作流阶段
|
||||||
|
|
||||||
|
| 来源 | 阶段划分 |
|
||||||
|
|------|----------|
|
||||||
|
| Kevin Ryan / Papalini | Specify → Plan → Tasks → Implement |
|
||||||
|
| GitHub spec-kit | Constitution → Specify → Plan → Tasks → Implement |
|
||||||
|
| Kiro (AWS) | Requirements → Design → Tasks |
|
||||||
|
|
||||||
|
## 与其他方法的关系
|
||||||
|
|
||||||
|
| 方法 | 关系 |
|
||||||
|
|------|------|
|
||||||
|
| [[Harness Engineering]] | SDD 关注规格,Harness 关注运行时环境 |
|
||||||
|
| [[Superpowers]] | 互补:SDD 关注规格,Superpowers 关注执行流程 |
|
||||||
|
| [[AgenticSE智能体软件工程]] | AI 队友场景下的工程方法论 |
|
||||||
|
|
||||||
|
## 原文档
|
||||||
|
|
||||||
|
- PDF: `/obsidian/参考资料/SDD_规格驱动开发/什么是SDD_规格驱动开发.pdf`
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
*整理自用户 Obsidian vault*
|
||||||
Reference in New Issue
Block a user