文档驱动开发
原名：spec-driven-development
在编码前创建规格说明。适用于启动新项目、功能或重大变更且尚无规格文档时，或在需求不明确、模糊或仅停留在初步构想阶段时使用。
- 分类
- 开发提效
- 版本
- v1.0.0
- 作者
- 孙怡(@user15fkr4)
- 下载
- 1
- 收藏
- 0
- 发布
- 2026-08-08
- 更新
- 2026-08-14
- TRACE 评分
- 3.4 / 5
内容概览
Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing. - Starting a new project or feature - Requirements are ambiguous or incomplete - The change touches multiple files or modules - You're about to make an architectural decision - The task would take more than 30 minutes to implement When NOT to use: Single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained. Spec-driven development has four phases. Do not advance to the next phase until the current one is validated. Start with a high-level vision. Ask the human clarifying questions until requirements are concrete. Surface assumptions immediately. Before writing any spec content, list what you're assuming: Don't silent…