Google’s Android Bench 2.0 (Sept 17) swaps small patches for 30 week-sized engineering tasks, and the top pass rate falls from roughly 91% to 28%. The gap is a useful map of where autonomous agents still need a human-written spec and a good harness.
Spaii Labs launched EasySpecs.ai on Sept 12, a platform that documents a codebase into a knowledge tree, grounds change requests against it, and ships every spec with machine-checkable oracles and human rubrics before an agent writes code. It’s a paid, SaaS bet on the same problem OpenSpec — a free, open-source, 27,000-star YC alum — is already solving with a markdown folder in your repo.
Atlassian launched Jira Planner on July 15 — a spec-generation tool that pulls codebase, Jira, and Confluence history into a structured technical spec before any coding agent touches a task. Atlassian’s own numbers: AI usage among engineering teams is up 65%, but velocity gains have plateaued around 15%, because coding is only 15-16% of the SDLC. Claude Code and Cursor are now GA as first-class agents inside Jira; Codex is still ‘coming soon.’
GitLab’s AI Accountability Report (June 23, 2026; Harris Poll, 1,528 developers and tech buyers across six countries) finds 78% code faster and 73% see better quality — but overall software delivery hasn’t sped up, because 85% say the bottleneck moved from writing code to reviewing it, and 92% report governance gaps managing AI-generated code.
CodePlain argues that code should be regenerated from specs, not maintained. The core insight — specs as the canonical artifact, code as ephemeral output — is exactly right. But treating full regeneration as the solution is naive for anything beyond greenfield toys.
Five production engineering teams — from a 23,000-person Latin American e-commerce giant to a 50-person legal AI startup — show what spec-driven development looks like at real scale. The numbers: 90% autonomous code generation, 6x task completion rates, 500K engineer-hours reclaimed. The patterns behind the numbers are more interesting than the numbers.
Research on 20,574 real agentic coding sessions found ~42% of agent failures trace back to specification quality, not model capability. EARS notation — a 50-year-old aerospace standard — is emerging as the format that best bridges human intent and AI execution. Here’s what the data says about writing specs AI can actually use.
A growing number of engineering teams are ditching Markdown for HTML when writing specs — not because they enjoy writing more verbose documents, but because HTML’s semantic structure gives AI agents significantly richer context when implementing from a spec. Here is where the tradeoff makes sense and how to do it well.
Writing specs instead of code is the core premise of SDD — but a bad spec produces bad code just as reliably as a bad prompt does. Here’s what separates specs that AI can execute reliably from the ones that waste hours of compute and your afternoon.
Spec-Driven Development has crossed from niche methodology to recognized category — with 30+ competing frameworks, a conference track at Agentic Conf Hamburg, AWS Kiro as the first commercial SDD IDE, and enterprise backing from McKinsey and Anthropic’s own trend reports. Here’s what’s happening and what it means.