
OpenSpec (Part 1): Spec-Driven Development, One Change at a Time
Why I picked OpenSpec after reading the Thoughtworks Technology Radar, and how it works in theory: specs, changes, deltas, archive, and the loop that ties them together.
Tag archive

Why I picked OpenSpec after reading the Thoughtworks Technology Radar, and how it works in theory: specs, changes, deltas, archive, and the loop that ties them together.

I was talking to a friend the other day regarding how you should approach spec work and realized...

I ran the whole BMAD workflow on a real app, step by step: brainstorming, PRD, UX, architecture, a clickable prototype, 22 stories and 7 retrospectives.

Following the SMS architecture discussion and product decisions, I asked Claude Code to turn the agreed plan into a spec baseline. This article reconstructs the prompt, scope confirmation, and generation results, covering six core documents, a boundary ADR, a supplier runbook, and derived charts—and the distinction between planning, design approval, implementation, and runtime acceptance.

Why I care about spec-driven development whatever the framework, and how BMAD handles both a single change and a product from scratch around a human-approved intent.

In the second article I built RoomBook with Spec Kit: an Angular frontend, a Spring Boot backend,...

In the first article I stayed on the theory: the specification as a contract, the Spec Kit workflow,...

Hacer desarrollo asistido por IA hoy en día suele caer en dos extremos: o bien el llamado vibe coding...
A real text I got from a friend of mine yesterday: Do you think spec-driven dev is...

Contexto Antes de se aprofundar nos pareceres de "beber da água" da IA alguns pontos...

Exploring Spec-Driven Development and GitHub Spec Kit from a software architecture perspective.

Apliqué Spec-Driven Development a un MVP en React Native que lista los sismos del mundo: la especificación decide qué entra en la lista y sus criterios de aceptación se convierten en los tests.