As AI coding brokers develop extra succesful, a structural downside has emerged: velocity with out readability. Builders generate working code in minutes, solely to find days later that it doesn’t match what the system really wanted. Spec-driven growth (SDD) addresses this immediately — by treating a structured specification because the supply of fact and code as its generated output, slightly than the opposite method round.
This record covers the 9 AI instruments that builders are literally utilizing to implement SDD workflows in 2026.
AWS Kiro
🔗 kiro.dev | Docs | Fashions
Kiro is an agentic IDE constructed round spec-driven growth, designed to take builders from idea to manufacturing with structured rigor as a substitute of iterative prompting. Fairly than writing code and asking an AI to assist alongside the best way, Kiro requires builders to formalize intent first. It guides them via a three-phase course of — Necessities, Design, and Duties — producing three structured artifacts: necessities.md, design.md, and duties.md. A notable technical element: Kiro generates person tales utilizing EARS (Simple Method to Necessities Syntax) notation, which produces structured acceptance standards overlaying edge instances that builders would in any other case deal with manually.
A significant differentiator is its agent hooks system — event-driven automations that fireplace when information are saved or created, dealing with duties like take a look at updates, README refreshes, and safety scans with out handbook prompting. For mannequin choice, Kiro’s default is an Auto router that mixes a number of frontier fashions — together with Claude Sonnet, Qwen, DeepSeek, GLM, and MiniMax — and selects the optimum mannequin per activity to stability high quality and value. Builders also can pin a selected mannequin for constant habits. Constructed on Code OSS, VS Code customers will really feel at residence instantly. Kiro additionally helps a CLI and an internet interface, and doesn’t require an AWS account to make use of. Finest for groups that want formal spec workflows in a well-recognized growth surroundings.
GitHub Spec Package
🔗 github.com/github/spec-kit | Weblog Publish
GitHub Spec Package is probably the most community-adopted open-source choice for spec-driven growth — a Python CLI with 93,000+ stars, the newest launch being v0.8.7 (Might 7, 2026), supporting 30+ AI coding brokers together with Claude Code, GitHub Copilot, Amazon Q, and Gemini CLI. The workflow runs via 4 phases with clear checkpoints: Specify (captures enterprise context and success standards), Plan (interprets specs into architectural choices), Duties (decomposes plans into testable, reviewable models), and Implement (runs AI brokers below these constraints).
On the basis of each Spec Package workflow is a “structure” — a markdown guidelines file containing high-level immutable rules that apply to each change throughout each session. This turns into the persistent contract between the developer and the agent. Spec Package’s philosophy, as GitHub framed it, is that code is now the last-mile output: intent is the supply of fact, and specs are executable. It’s the default start line for groups new to SDD and probably the most transportable choice for groups that need to hold their present IDE.
BMAD-METHOD
🔗 github.com/bmad-code-org/BMAD-METHOD | Docs
BMAD-METHOD (Construct Extra Architect Desires) is an MIT-licensed open-source framework that orchestrates 12+ specialised AI brokers throughout the complete software program growth lifecycle. Model 6.6.0 shipped on April 29, 2026, with the challenge reaching 46,700+ GitHub stars and greater than 5,500 forks. The 12+ brokers cowl distinct SDLC roles — together with product administration, structure, UX, growth, QA, and scrum grasp capabilities — and work collectively via structured, file-based handoffs: every agent reads the earlier agent’s output doc and writes its personal, sustaining a traceable chain from necessities via supply.
V6 launched the Cross Platform Agent Crew, permitting the identical agent configuration to function throughout Claude Code, Cursor, Codex, and different hosts with out reconfiguration. The V6 structure additionally separates issues into three layers: BMad Core (the common human-AI collaboration framework), BMad Technique (the agile growth module constructed on Core), and BMad Builder (which lets groups create and share customized brokers and workflows). BMAD is the go-to framework for groups that need extremely structured, role-separated multi-agent workflows with out vendor lock-in. The framework is solely free with no paywalls.
Increase Code
🔗 augmentcode.com | SDD Information
Increase Code approaches spec-driven growth from the context layer slightly than the spec authoring layer. Its Context Engine maintains a persistent architectural understanding throughout 400,000+ information — addressing the cross-repository context hole that breaks most specification workflows at scale, notably in multi-service brownfield codebases. Increase experiences 70.6% on SWE-bench (in comparison with a 54% business common) and a 59% F-score on an AI code overview benchmark; these figures are vendor-reported and ought to be handled accordingly.
Its BYOA (Carry Your Personal Agent) mannequin lets groups plug in Claude Code, Codex, or OpenCode alongside its native Auggie agent. Increase Code doesn’t creator specs natively — groups nonetheless want a device like Spec Package or Kiro for structured spec administration — however it gives the semantic basis that makes these specs correct throughout massive codebases. Finest suited to enterprise groups working complicated multi-service architectures the place context drift, not spec creation, is the first failure mode.
Claude Code
🔗 claude.ai/code | Docs
Claude Code is Anthropic’s agentic command-line device, and in contrast to instruments equivalent to Cursor or GitHub Copilot that increase a developer’s workflow, it’s designed for totally autonomous growth — planning, orchestrating multi-step workflows, and asking follow-up questions with out fixed prompting. For spec-driven workflows, Claude Code handles massive specification paperwork nicely inside a single session, processing full requirement units and producing implementations in a single coherent go.
Builders sometimes use CLAUDE.md information because the spec layer — a light-weight method that enforces persistent challenge context, coding requirements, and architectural constraints throughout each session. This implies many builders are already training a type of SDD with Claude Code with out formally labeling it as such. Claude Code additionally serves as a generally supported execution agent throughout SDD frameworks together with BMAD, GSD, and GitHub Spec Package.
GSD (Get Shit Performed)
🔗 github.com/gsd-build/get-shit-done
GSD is a spec-driven meta-prompting and context engineering framework constructed primarily for Claude Code and suitable brokers, positioning itself because the lean, low-ceremony different to BMAD. The challenge has crossed 61,000 GitHub stars — rising from zero to that determine in below 5 months since its December 2025 preliminary commit. It installs through npx get-shit-done-cc@newest and works throughout Claude Code, OpenCode, Gemini CLI, Codex, Copilot, Cursor, Windsurf, Increase, and Cline.
Its multi-agent orchestration spawns parallel researchers, planners, executors, and verifiers, every working in a recent context window with as much as 200K tokens devoted to implementation. The model-agnostic design — together with help for OpenRouter and native fashions — decouples the workflow from any single LLM vendor. The place BMAD provides dash ceremonies and stakeholder coordination, GSD’s philosophy is that complexity ought to stay within the system, not the workflow. It additionally fills a spot that Claude Code itself doesn’t cowl natively: context rotation, high quality gates, and planning state persistence throughout classes.
Cursor (with Plan Mode + Challenge Guidelines)
🔗 cursor.com | Agent Finest Practices
Cursor stays one of the extensively used AI editors, and its Plan Mode makes it a sensible entry level for groups adopting spec-first habits with out switching toolchains. Plan Mode creates an in depth implementation plan earlier than any code is written — asking clarifying questions, mapping affected information, and producing a reviewable plan that the developer approves earlier than the agent acts. This prevents untimely code era for options that contact a number of information or require architectural choices.
For persistent spec-like context, Cursor’s present guidelines system makes use of challenge guidelines saved below .cursor/guidelines/ (the older .cursorrules conference is now thought of legacy). When mixed with challenge guidelines, Cursor helps a light-weight, transportable spec workflow for medium-to-large greenfield options. The tradeoff is that Cursor’s spec help shouldn’t be native to its structure the best way Kiro’s is — there is no such thing as a built-in spec lifecycle, drift detection, or living-spec synchronization. For groups that need structured AI growth inside a well-recognized, high-quality editor with out full SDD overhead, Cursor with Plan Mode is a succesful center floor.
OpenSpec
🔗 github.com/Fission-AI/OpenSpec
OpenSpec targets a selected and underserved use case: groups the place change administration requires specific, auditable documentation earlier than any implementation begins. It makes use of a proposal-centered workflow with structured artifacts for adjustments, and particularly addresses brownfield iteration with delta markers (ADDED/MODIFIED/REMOVED) that monitor what adjustments relative to present performance slightly than greenfield descriptions. Importantly, OpenSpec’s personal documentation positions it as light-weight and versatile slightly than a inflexible phase-gated system — it gives construction with out imposing laborious approval gates between phases.
In a February 2026 unbiased analysis run throughout 13 scoring classes on a medium-sized serverless Python backend, OpenSpec scored highest general — although that rating shifts considerably with totally different priorities. Groups for whom change accountability and documentation trails outweigh living-spec synchronization will discover it one of the best match. For bigger multi-service initiatives, pairing OpenSpec with a living-spec platform is really useful, since its proposal-based construction produces static paperwork that may drift throughout prolonged implementation.
Tessl
🔗 tessl.io | Spec Registry | Docs
Tessl is a language-agnostic agent enablement platform constructed round two distinct merchandise. The Tessl Framework installs as “tiles” right into a challenge’s .tessl/ listing and teaches any MCP-compatible agent — together with Claude Code, Cursor, and others — to comply with a spec-driven workflow no matter stack: brokers ask clarifying questions first, write structured specification paperwork, watch for developer approval, then implement. Specs stay within the codebase as long-term reminiscence, giving choices an audit path and permitting the agent to evolve the app coherently over time.
The Tessl Spec Registry is the platform’s clearest differentiator: an open registry of over 10,000 specs describing learn how to appropriately use exterior open-source libraries, immediately focusing on the API hallucinations and model mix-ups that brokers ceaselessly produce in manufacturing codebases. Consider it as npm for specs — groups set up each a strategy tile (learn how to work) and library tiles (what instruments to make use of appropriately) to forestall each course of chaos and documentation hallucination. The 2-layer structure — course of context plus library context — is Tessl’s core perception: structured workflow alone isn’t sufficient if the agent nonetheless hallucinates the APIs it’s constructing with.
Be at liberty to comply with us on Twitter and don’t neglect to affix our 150k+ ML SubReddit and Subscribe to our E-newsletter. Wait! are you on telegram? now you’ll be able to be part of us on telegram as nicely.
Must associate with us for selling your GitHub Repo OR Hugging Face Web page OR Product Launch OR Webinar and so on.? Join with us
