~/blog · filtered by category

sdd.

10 entries filed under this signal. ← back to all entries

[blog/category/sdd] · reverse chronological$ ls -la --filter=sdd

2026-07-20sddAdding specs to an existing codebase without stopping the worldMost software already exists. Spec-driven development has to meet a living repository where it is, not where a greenfield tutorial pretends it is.#spec-driven-development#existing-codebase#legacy-code#ai-coding#agentic-development#paelladoc7 min./read →2026-07-20sddSpec vs PRD: what each one is for (and what agents need)People use the words interchangeably. An agent needs different things from each, and confusing them is why so much AI-built work misses the point.#spec-vs-prd#spec-driven-development#product-requirements#ai-coding#agentic-development6 min./read →2026-07-20sddReviewing specs before agents build: the cheapest review you will ever doReviewing a diff means arguing with code that already exists. Reviewing a spec means fixing the mistake before it costs anything to fix.#spec-review#spec-driven-development#code-review#ai-coding#verification#paelladoc7 min./read →2026-07-20sddSpec-driven vs test-driven: rivals or layers?The framing of a fight is wrong. Tests pin down behavior. Specs pin down intent. You lose the moment you only have one.#spec-driven-development#test-driven-development#testing#ai-coding#verification#paelladoc7 min./read →2026-07-20sddSpec drift: why your spec and your code stop telling the same storyYou wrote a spec. Forty agent runs later it describes a product that no longer exists. That gap has a name, and a cost.#spec-drift#spec-driven-development#ai-coding#agentic-development#living-specs6 min./read →2026-07-20sddThe spec is the contract: what that means in practiceEveryone repeats that the spec is the contract. Almost nobody can say who signs it, who breaks it, or how the break gets caught.#spec-driven-development#acceptance-criteria#contract#ai-coding#verification#paelladoc7 min./read →2026-07-20sddLiving specs: specifications that update with the codeA spec you write once is wrong by the second commit. A living spec earns its keep because it changes when the code changes.#living-specs#spec-driven-development#ai-coding#agentic-development#spec-drift7 min./read →2026-07-20sddSpec-driven without the overhead: a lightweight workflowThe complaint is real: the ceremony can cost more than the code it guards. Here is the smallest spec that still does the job.#lightweight-sdd#spec-driven-development#ai-coding#agentic-development#acceptance-criteria7 min./read →2026-07-20sddBeyond Spec Kit: what spec-driven needs after the spec is writtenSpec Kit gets you a clean spec on day one. The hard part is everything that happens on day thirty.#spec-kit#spec-driven-development#living-specs#ai-coding#agentic-development#paelladoc6 min./read →2026-07-20sddAcceptance criteria agents can actually verify"Fast and user-friendly" is not a criterion an agent can check. It is a criterion an agent can claim to have met. Here is the difference, and why it matters now.#acceptance-criteria#spec-driven-development#verification#ai-coding#agentic-development7 min./read →

— end of log · 10 entries in sdd —