(October 2025) Understanding Spec-Driven-Development: Kiro, spec-kit, and Tessl

This article from Martin Fowler's site explores the emerging concept of Spec-Driven Development (SDD) by examining three tools that claim to implement it: Kiro, GitHub's spec-kit, and the Tessl Framework. The author defines SDD as a "documentation-first" approach where a structured specification is written before code and serves as a source of truth. The tools vary significantly in their implementation, from lightweight workflows to more elaborate artifact generation, and in their ambition—ranging from "spec-first" to "spec-anchored" (maintaining the spec over time) to "spec-as-source" (where the spec is the primary artifact). The author raises critical questions about the practical utility of these tools, noting that their rigid workflows may be overkill for small tasks, the generated markdown files can be tedious to review, and the approach risks creating a false sense of control due to LLM non-determinism. The article concludes by drawing parallels to past failures of Model-Driven Development, suggesting that while the "spec-first" principle is valuable, the current tool implementations may be over-engineering the problem. 

https://martinfowler.com/articles/exploring-gen-ai/sdd-3-tools.html

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

SecObserve: Simplified Vulnerability and License Management for CI/CD Pipelines

 SecObserve is an open-source tool for managing vulnerabilities and licenses in software development and cloud environments. It integrates various vulnerability scanners into CI/CD pipelines using GitLab CI templates and GitHub Actions for streamlined setup. It offers a centralized dashboard for assessing and reporting vulnerabilities, with tools for filtering, sorting, and evaluating results. SecObserve supports automation and manual assessments to focus on resolving critical issues.  https://github.com/MaibornWolff/SecObserve/tree/dev
Read more

OWASP ZAP 2.16.0 Introduces Key Updates and Enhancements

 In January 2025, OWASP ZAP released version 2.16.0 with several key updates. A redesigned spidering method improves the crawling of modern web applications, particularly those using JavaScript frameworks. The new version also introduces detachable tabs for a more flexible workspace. The minimum Java version required has been updated to Java 17. Additionally, the Client Spider was introduced to enhance crawling by capturing events, DOM changes, and user interactions in modern web apps. The project welcomed new contributors and updated its roadmap for ongoing development. https://www.zaproxy.org/blog/2025-02-04-zap-updates-january-2025/
Read more