[KongchangAI]
ConceptSDD / 规范驱动开发

Spec-Driven Development

Spec-Driven Development is an AI programming methodology in which detailed specification documents are written before an AI agent begins execution. This approach decouples "defining what" from "implementing how," constraining and guiding the agent's behavior to improve intent fidelity and reduce the disorder associated with unsupervised AI-generated code.

Timeline (last 90 days)

Oct 5

The pauses between phases in spec-driven development are an intentional safety gate/checkpoint design

Unverified50%
Oct 4

The essence of SDD is decoupling the specification that describes 'what to do and why' from the implementation of 'how to do it'.

Unverified50%
Oct 4

SDD is also applicable to existing brownfield projects, where agents can reverse-engineer SDD artifacts by exploring the existing codebase.

Unverified50%
Oct 4

In SDD, each feature follows a repeatable cycle of plan → implement → validate and is developed on an independent branch.

Unverified50%
Oct 4

The three major benefits of SDD are controlling large changes with small modifications, eliminating context decay, and improving intent fidelity.

Unverified50%
Oct 4

SDD compensates for the stateless nature of models by using persistent specification documents as external memory.

Unverified50%
Sep 29

The Constitution consists of three pillars: Mission, Tech Stack, and Roadmap

Unverified50%
Sep 29

SDD advises developers to review small changes with a human-in-the-loop, and to let agents modify files rather than editing them manually, in order to keep all artifacts in sync and avoid drift

Unverified50%
Sep 22

The basic idea of SDD (Spec-Driven Development) is to fully describe requirements, architecture, interface contracts, and test expectations in structured documents before AI writes code, and then have AI generate code step by step according to the specification.

Unverified50%
Sep 12

The spec-first philosophy aligns with the rising industry trend of Spec-Driven Development.

Unverified50%

5 more timeline events

All Facts (17)

Unverified

GSD的规范驱动开发遵循三阶段工作流:规范起草、规范审查和规范执行

90%
Unverified

SDD(Spec-Driven Development,规范驱动开发)在日常小迭代中写Spec的成本远高于直接写代码,且Spec基本是一次性的难以积累价值

70%
Unverified

The pauses between phases in spec-driven development are an intentional safety gate/checkpoint design

50%
Unverified

SDD compensates for the stateless nature of models by using persistent specification documents as external memory.

50%
Unverified

The three major benefits of SDD are controlling large changes with small modifications, eliminating context decay, and improving intent fidelity.

50%
Unverified

In SDD, each feature follows a repeatable cycle of plan → implement → validate and is developed on an independent branch.

50%
Unverified

SDD is also applicable to existing brownfield projects, where agents can reverse-engineer SDD artifacts by exploring the existing codebase.

50%
Unverified

The essence of SDD is decoupling the specification that describes 'what to do and why' from the implementation of 'how to do it'.

50%
Unverified

The Constitution consists of three pillars: Mission, Tech Stack, and Roadmap

50%
Unverified

SDD advises developers to review small changes with a human-in-the-loop, and to let agents modify files rather than editing them manually, in order to keep all artifacts in sync and avoid drift

50%
Unverified

The basic idea of SDD (Spec-Driven Development) is to fully describe requirements, architecture, interface contracts, and test expectations in structured documents before AI writes code, and then have AI generate code step by step according to the specification.

50%
Unverified

The spec-first philosophy aligns with the rising industry trend of Spec-Driven Development.

50%
Unverified

The three core advantages of SDD are: controlling large-scale code changes with small modifications, eliminating context decay between sessions, and improving intent fidelity.

50%
Unverified

The SDD workflow is divided into two levels: the project layer (establishing a "constitution" that defines immutable standards) and the feature layer (the feature development loop).

50%
Unverified

The feature development loop follows three steps—plan, implement, and verify—with each feature isolated on an independent branch.

50%
Unverified

The SDD workflow is applicable to both Greenfield (brand-new projects) and Brownfield (existing codebases) projects.

50%
Unverified

Andrew Ng partnered with JetBrains to launch the course "Spec-Driven Development (SDD)".

50%

Source Articles