@GergelyOrosz: Both AWS’s Kiro and GitHub Workflows was built on the idea of spec-driven development (you or the agent writes a spec f…
Summary
A tweet discusses why spec-driven development, as used in AWS Kiro and GitHub Workflows, failed to gain traction, referencing an analysis by @dexhorthy.
View Cached Full Text
Cached at: 07/25/26, 10:04 AM
Both AWS’s Kiro and GitHub Workflows was built on the idea of spec-driven development (you or the agent writes a spec first, then it implements it). And it just… hasn’t stuck.
Good take from @dexhorthy on why not
The Pragmatic Engineer (@Pragmatic_Eng): Why did spec-driven development never take off - the workflow tools like Amazon’s Kiro or GitHub Workspaces encouraged? @dexhorthy, founder of HumanLayer:
“These projects have a really interesting idea: you maintain a set of specifications for your software, and then you
Similar Articles
@zachlloydtweets: https://x.com/zachlloydtweets/status/2071670840660533393
Zach Lloyd details how to build a spec-driven development agent within a cloud software factory, using triage and spec agents to handle ambiguous or complex issues by generating product and tech specs before implementation.
@PawelHuryn: Spec-Driven Development was always BS. It never worked for humans. Waterfall lost to agile because you discover what yo…
This tweet argues that Spec-Driven Development is ineffective for AI agents, drawing parallels to the failure of waterfall methodology in software development. It advocates for 'intent engineering'—communicating context, strategy, and constraints to agents to handle unknown unknowns.
@zachlloydtweets: https://x.com/zachlloydtweets/status/2065154860337508577
The article outlines a five-step workflow for spec-driven development using Warp skills: write a product spec (PRODUCT.md), write a tech spec (TECH.md), implement with any AI agent, validate implementation matches specs, and validate using computer use with Oz. The skills are open-sourced and can be installed via npx.
@Fluyeporlaweb: Github just fucked up the vibe coding Just released spec-kit and in a few days it has 95k stars and 8.3k forks This isn…
GitHub released spec-kit, a tool that structures AI coding workflows by enforcing a specification-first approach before code generation, gaining rapid traction with 95k stars.
@rohanpaul_ai: GitHub recently published this repo SpecKit, an open-source toolkit to fix a big weakness of vibe coding: that AI often…
GitHub released SpecKit, an open-source toolkit that addresses a weakness in AI coding by enforcing a spec-first workflow, turning product specs into executable development contracts for AI agents.