{
  "id": 20192772,
  "title": "OpenSpec (Part 1): Spec-Driven Development, One Change at a Time",
  "url": "https://urgent.news/2026/11/15/openspec-part-1-spec-driven-development-one-change-at-a-time",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-15T15:21:34.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/rosidotidev/openspec-part-1-spec-driven-development-one-change-at-a-time-17pa"
  },
  "original_language": "en",
  "account": "The Thoughtworks Technology Radar is a twice-yearly publication written by a group of senior technologists who meet and discuss what they have seen on real projects. It is not a survey or a vendor ranking, but the opinion of people who build software for clients. The Radar helps identify which tools and technologies are worth assessing, and one of the tools that has recently gained attention is OpenSpec. OpenSpec is an open-source framework that adds a lightweight specification layer to coding agents. It aims to improve predictability and maintainability when requirements live only in ephemeral chat histories. OpenSpec proposes a workflow that includes three steps: propose, apply, and archive. It works well on existing codebases and provides a persistent source-of-truth spec, allowing changes to be deltas against that spec. However, the Radar also notes that the key challenge is keeping the persistent spec healthy, as Markdown files generated by agents can become large and unwieldy if not properly managed.",
  "summary": "At the end of the second BMAD article I asked you what to write next. One of the options was \"other SDLC frameworks for agents, such as OpenSpec\". I was still undecided, so before choosing I looked around, and one source settled it for me: the Thoughtworks Technology Radar. This article is the first of a short series on OpenSpec. I stay on the theory: what problem it solves, the project context,…",
  "key_points": [
    "OpenSpec is an open-source framework adding a lightweight spec layer to coding agents",
    "Workflow includes propose, apply, and archive steps",
    "Key challenge is maintaining health of persistent Markdown spec files"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}