Spec-driven Development (OpenSpec)

AdoptFactorial rates Spec-driven development as Adopt (2026). OpenSpec is now how we work on our own products: Subtool, FlowDrop, our controlling app and even this tech radar keep their changes as specs in the repository.

In spec-driven development, a change is first written down as a specification (what and why, then the tasks), reviewed by a person, and only then implemented by an agent. OpenSpec keeps this lightweight with a propose → apply → archive cycle stored in the repository; Spec Kit is a more elaborate alternative.

Updates

Adopt

OpenSpec is now how we work on our own products: Subtool, FlowDrop, our controlling app and even this tech radar keep their changes as specs in the repository. A good spec turned out to be portable: a strong model writes it and a cheaper or open-weight model implements it with good results. Specs capture the what well, but design decisions that only live in a developer's head still need an explicit conversation before the spec is locked.