AI Coding Market Map
Supporting Capabilities

Spec-Driven Development Tools

Nascent
Emerging
Growth
Maturing
Mature

Frameworks and tools that structure how AI agents receive and execute work — through specifications, task graphs, and phase-gated workflows rather than ad-hoc prompts. Teams that adopt spec-driven development get more predictable output from agents and reduce the rework cycle.

Overview Recommendations Trends and Strategic Signals Tools Adoption and Traction New Entrants & Watch List

Overview

Category maturity: Emerging. The SDD category has moved past proof-of-concept — multiple tools have achieved stable releases, enterprise training materials exist, and at least one integrated IDE (Kiro) has reached general availability. Team-scale adoption remains uneven, and no tool has published verified data on sustained multi-team deployment.

Direction of travel: Over the next 6-12 months, two dynamics will reshape the category:

  • Consolidation around a small set of durable artifact formats (requirements.md with EARS notation, architecture.md, tasks.json with dependency graphs) and cleaner integration between methodology overlays and coding agents as those agents build native spec support
  • The boundary between methodology overlay and integrated spec tool will continue blurring: Kiro built spec generation into the IDE, and coding agents like Claude Code and Cursor are adding hooks that frameworks like BMAD, GSD, and gstack can leverage

Expect the category to absorb tooling pressure from both directions.

Coalesced patterns: The industry has converged on a clear artifact hierarchy and workflow:

  • A requirements document (often structured with EARS notation), a design or architecture document, and a task list with dependency tracking form the standard artifact set
  • Phase-gated workflows (discuss, plan, implement, verify) are now standard across both methodology overlays and integrated tools
  • Persistent Markdown files checked into version control are the dominant format for durable specs, ensuring documentation travels with the codebase
  • Integration via MCP (Model Context Protocol) is becoming the standard hook for connecting spec frameworks to coding agents

Unsolved problems: Several gaps limit adoption at team scale:

  • Spec drift during implementation is the most cited failure mode: agents deviate from approved specs as implementation unfolds, and there is no reliable automated mechanism for detecting or reconciling that drift in real time
  • Team-scale adoption continues to lag individual developer adoption; most published case studies describe single-developer or small team (2-3 person) workflows
  • Brownfield codebases remain difficult to spec retroactively at scale, and the tooling for reconciling existing code with new specs is still immature
  • Documentation durability as code evolves is largely manual: tools create the initial spec artifact, but keeping it synchronized with a codebase that changes daily remains a human responsibility

Recommendations

1. Allocate time to experiment with popular SDD tools and frameworks. The category has matured enough that tools like gstack (50,000+ stars in its first two weeks, MIT-licensed, documented production workflows) and GitHub Spec Kit (formal Microsoft Learn training, 22+ agent platforms supported) are ready for serious evaluation. The goal is to understand their capabilities and determine whether the techniques or tools might improve your use of AI agents. Start with a well-scoped feature and one team — the risk of not starting is higher than the risk of starting.

2. Solve the context rot problem before optimizing for speed. Every tool on this map exists because AI agents lose track of intent across long sessions. GSD's .planning/ directory is one of the most practical solutions currently available. Teams that deploy it will find their AI-assisted development sessions more predictable and their code review cycles shorter. This is the single most accessible near-term win in the category.

3. For brownfield codebases, start with OpenSpec. Most teams are not building 0-to-1. They have existing codebases, and their AI agents are making changes to production systems. OpenSpec's three-phase state machine (propose, review, apply) and delta markers provide the change-control layer that brownfield AI development needs.

1. The category has achieved mainstream visibility and is accelerating into team adoption. The SDD category crossed a meaningful threshold this week: what began as individual developer experiments with structured prompting has accumulated enough critical mass that enterprise developer platforms are publishing formal training modules on spec-first workflows. Microsoft Learn now offers a dedicated course on spec-driven development using GitHub Spec Kit, targeting enterprise developers. Thoughtworks published a landmark analysis treating SDD as one of 2025's defining engineering practices, and a Medium survey mapped 30+ agentic coding frameworks under the SDD banner. This is no longer frontier territory; it is becoming standard curriculum.

2. gstack's explosive launch signals a shift from individual methodology to role-based team simulation. Garry Tan's gstack, open-sourced in mid-March 2026, surpassed 50,000 GitHub stars within 16 days, topping Product Hunt in its first week. The project attracted 33,000 stars and 4,000 forks within its first week alone. The velocity signals genuine practitioner demand for role-based AI workflows that mirror engineering org structures, not just task decomposition. The "CEO rethinks the product" framing resonates because it maps directly to how PE-backed teams think about shipping velocity without adding headcount.

3. BMAD-METHOD V6 has achieved stable release, marking a maturity milestone for the methodology overlay category. BMAD v6.0.4 shipped in early March 2026 as the first officially stable release, with 75 commits, 61 PRs, and changes across 306 files. The npm package shrank 91% (from 6.2 MB to 555 KB), and the tool count expanded from 18 to 28 agents covering nearly every major AI coding assistant. The V6 stable release is significant: it moves BMAD from experimental to production-endorsed, and the community has 29,600+ GitHub stars to demonstrate adoption depth.

4. Integrated spec tools are expanding platform integrations aggressively. Kiro added SageMaker Studio remote connectivity in March 2026, deepening its AWS ecosystem play. OpenSpec 1.2 (released February 25, 2026) added native support for Pi and Kiro in addition to Claude Code, Cursor, and Windsurf, while introducing a bulk archive workflow and AI tool auto-detection. GitHub Spec Kit expanded agent support to 22+ platforms including Amp, Roo Code, Kilo Code, Qwen Code, and Amazon Q Developer CLI. The pattern: integrated tools are competing on breadth of agent compatibility, signaling that no single coding agent will dominate and that spec frameworks must be portable.

5. A counter-narrative is emerging around "spec fatigue" and brownfield friction. Community discussion on Hacker News and Reddit r/LocalLLaMA reflects a growing tension: spec-first workflows add front-loaded overhead that solo developers and early-stage teams find onerous. OpenSpec's brownfield-first positioning (published March 10, 2026 as a formal guide) is responding to this directly, as is GSD's emphasis on "lightweight" meta-prompting. The community is converging on a recognition that the discipline pays off at team scale but requires cultural change to sustain past the first sprint.

Tools

GitHub Spec Kit logoGitHub Spec Kit

  • Maker: GitHub (Microsoft)
  • Archetype: Integrated spec tool (spec generation templates, CLI, and prompts; agent-agnostic)
  • Works with: Claude Code, GitHub Copilot, Cursor, Gemini CLI, Windsurf, Codex CLI, Amp, Roo Code, Kilo Code, Qwen Code, Amazon Q Developer CLI, and 10+ additional agents (22+ total)
  • Access: Free, open-source (MIT)
  • Strengths:
    • Backed by GitHub (Microsoft), providing institutional support, long-term maintenance confidence, and credibility with enterprise procurement teams
    • Microsoft Learn training module for enterprise developers makes this the most formally supported SDD framework for enterprise onboarding
    • constitution.md establishes non-negotiable project principles that persist across agent sessions, directly addressing governance and auditability requirements
    • Agent-agnostic architecture means teams are not locked into a specific coding agent; the spec layer is portable across the full ecosystem
    • 71,000+ stars and 50-country contributor base demonstrate genuine community depth beyond the Microsoft ecosystem
  • Limitations:
    • The toolkit is intentionally lightweight and guideline-oriented; teams needing automated spec enforcement or agent orchestration need to build those layers themselves or combine with a methodology overlay
    • Current documentation and examples lean toward greenfield projects; brownfield integration requires more manual adaptation
    • The Microsoft/GitHub backing is also a consideration for teams with multi-cloud or non-Microsoft stack commitments; the spec format is portable but the integration examples are .NET-centric
  • Enterprise readiness: Enterprise-ready. Institutional backing, formal training, MIT license, and 22+ agent support make this the safest starting point for enterprise teams.
  • Best for: Enterprise engineering teams that want institutional backing, formal governance via constitution.md, and agent-agnostic spec infrastructure
  • This week: IBM published iac-spec-kit, an infrastructure-as-code variant extending GitHub Spec Kit's methodology to IaC workflows. No changes to the core toolkit this week.

OpenSpec logoOpenSpec

  • Maker: Fission AI (open-source)
  • Archetype: Integrated spec tool (spec framework with CLI and state machine)
  • Works with: Claude Code, Cursor, GitHub Copilot, Cline, Windsurf, Pi, Kiro (added in v1.2)
  • Access: Free, open-source (MIT); Y Combinator-backed
  • Strengths:
    • Brownfield-first architecture is a genuine differentiator: delta markers (ADDED/MODIFIED/REMOVED) track what changes relative to existing functionality, making this the strongest choice for teams iterating on legacy codebases
    • Three-phase state machine (propose, apply, archive) enforces a human approval gate before any code generation, directly supporting auditability and change control requirements
    • Specifications are stored as Markdown in version control, making the spec a first-class citizen of the codebase that survives developer turnover
    • Y Combinator backing and 28,000+ GitHub stars signal institutional credibility and active maintenance
  • Limitations:
    • The three-phase workflow adds deliberate overhead: teams under acute shipping pressure will need to internalize the approval gate as a quality investment rather than a bottleneck
    • The v1.2 bulk archive and profile management features address workflow ergonomics, but the framework still requires more ceremony than methodology overlays like GSD or gstack
    • Greenfield teams may find BMAD-METHOD or GitHub Spec Kit a better starting point; OpenSpec's brownfield strengths shine most on teams with existing codebases of meaningful size
  • Enterprise readiness: Developing. YC-backed, MIT license, strong spec hygiene; team-scale enterprise adoption cases are not yet widely published.
  • Best for: Engineering teams iterating on existing codebases who need a formal change proposal and approval workflow before AI agents touch production code
  • This week: v1.2.0 released February 25, 2026 (most recent major release). No new releases this week. Brownfield adoption guide published March 10, 2026.

Superpowers logoSuperpowers

  • Maker: Jesse Vincent (obra), open-source
  • Archetype: Methodology overlay
  • Works with: Claude Code, Cursor, Codex CLI, OpenCode, Gemini CLI, and other agent runtimes
  • Access: Free, open-source
  • Strengths:
    • 124,000+ GitHub stars make this the highest-star SDD framework in the category, reflecting genuine practitioner adoption velocity
    • Auto-triggering skill modes (planning, implementing, debugging) enforce TDD and design-first flows automatically, without requiring developers to remember to invoke them
    • Strict RED-GREEN-REFACTOR TDD enforcement generates failing tests before implementation, directly addressing code quality concerns
    • Socratic design-first flow (brainstorm, spec, implementation plan, execution) produces durable artifacts as a natural side effect of the workflow
  • Limitations:
    • The framework is optimized for individual developers or small teams running a single primary agent; multi-developer coordination with shared spec state requires additional process design on top of the framework
    • The TDD enforcement is a feature for quality-focused teams and a friction point for teams under shipping pressure who are not already practicing test-first development
    • Framework conventions are implicit in skill triggers; teams benefit from a brief onboarding investment to understand how skills compose
  • Enterprise readiness: Developing. Exceptional community traction; limited published enterprise deployment case studies.
  • Best for: Individual developers or small teams who want enforced TDD, structured planning, and quality guardrails without a heavyweight process overhead
  • This week: Trending at #2 on GitHub in mid-March 2026; 1,867 stars gained in a single day on March 16. No structural changes to the framework this week.

BMAD-METHOD logoBMAD-METHOD

  • Maker: bmad-code-org (open-source community)
  • Archetype: Methodology overlay
  • Works with: Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI, Pi, and 28 total supported tools as of V6
  • Access: Free, open-source (MIT); no paywalls
  • Strengths:
    • V6 stable release (March 2026) delivers a fully production-endorsed, actively maintained framework with a clear upgrade path
    • 21 specialized agents and 50+ guided workflows covering the full development lifecycle from ideation through agentic implementation
    • "Party Mode" enables multi-agent collaboration within a single session, a meaningful capability for teams exploring agent orchestration
    • Scale-adaptive intelligence that adjusts workflow depth from single bug fixes to enterprise system design
  • Limitations:
    • The framework rewards teams willing to invest time learning its agent roles and workflow conventions; teams looking for drop-in simplicity are best served starting with the quick-start path and expanding from there
    • Most published adoption stories are individual developers or small teams; teams adopting for multi-developer workflows should plan for a shared conventions phase
    • Best results come from greenfield projects where the full workflow sequence can be followed from the start
  • Enterprise readiness: Developing. V6 stable release and broad agent coverage are positive signals; documented team-scale deployments are still sparse.
  • Best for: Engineering teams that want a comprehensive, role-based AI workflow framework and are willing to invest in learning a well-structured methodology
  • This week: BMAD v6.0.4 stable release shipped in early March 2026. No additional changes this week.

gstack logogstack

  • Maker: Garry Tan (YC President, open-source)
  • Archetype: Methodology overlay
  • Works with: Claude Code (primary); skill files are Markdown-based and portable
  • Access: Free, open-source (MIT); no SaaS dependency
  • Strengths:
    • Role-based virtual team model (CEO, Engineering Manager, Designer, QA, Security Officer, Release Engineer, and 18 others across 23 specialists) maps directly to how engineering teams think about quality gates and sign-off
    • Fastest-growing SDD framework by star velocity in 2026, with 50,000+ stars in 16 days, signaling strong practitioner resonance
    • All skills are readable and editable Markdown files; no vendor lock-in, no telemetry, MIT licensed
    • Concrete productivity claim from creator: 600,000+ production lines of code (35% tests) in 60 days, part-time, while running YC, providing a credible reference point for output expectations
  • Limitations:
    • Currently optimized for Claude Code; teams using other primary agents will need to adapt skill files, though the Markdown format makes this tractable
    • The framework reflects one person's opinionated workflow; teams should review and adapt the role definitions to match their own engineering culture and quality standards
    • The very recent launch (March 2026) means there are limited multi-developer adoption stories available; teams adopting now are early adopters
  • Enterprise readiness: Early. Extraordinary community signal; no documented team-scale or enterprise deployments yet.
  • Best for: Engineering teams already using Claude Code who want to simulate a full virtual development team with role-based quality gates and opinionated workflows
  • This week: Launch week. gstack was open-sourced in mid-March 2026 and hit 50,000+ stars within 16 days. Still actively accumulating community feedback and contributions.

GSGSD (Get Shit Done)

  • Maker: TÂCHES (open-source)
  • Archetype: Methodology overlay
  • Works with: Claude Code, OpenCode, Cursor, Windsurf; gsd-2 runs on the Pi SDK as a standalone CLI
  • Access: Free, open-source; distributed as an npm package
  • Strengths:
    • Externalizes all project state into persistent Markdown files (.planning/ directory), directly solving context rot across long AI sessions by giving agents a fresh, complete context on every task
    • Aggressive atomicity: each plan is sized to fit approximately 50% of a fresh context window, ensuring agents never exceed their reliable reasoning horizon
    • Phase hierarchy (Project, Milestone, Phase, Plan, Task) maps cleanly to how engineering teams already track work, making it understandable to non-developer stakeholders
    • Used by engineers at Amazon, Google, Shopify, and Webflow, providing credible signal of professional adoption
  • Limitations:
    • The framework's strength (comprehensive state management) requires teams to maintain the .planning/ directory as code evolves; the discipline of keeping state files current is a human responsibility
    • GSD-2 (Pi SDK standalone) and the Claude Code version have separate development paths; teams should align on which variant to adopt before committing
    • Parallel research agents (spawned during the initialize phase) add setup time that faster-moving teams may find front-heavy
  • Enterprise readiness: Developing. Professional engineering adoption is documented; team-scale governance patterns are not yet formalized.
  • Best for: Engineering teams that need disciplined context management across multi-session AI development workflows, particularly on longer-running features or complex system work
  • This week: v1.28 released with forensics, milestone summaries, workstreams, assumptions mode, UI auto-detect, and a manager dashboard. New gsd-researcher and gsd-debugger agents shipped.

Kiro logoKiro (profiled in IDE Agents)

Kiro is the only IDE in the landscape with built-in spec-driven development — requirements, architecture, and task generation happen inside the IDE before code is written. Agent Hooks trigger automated spec compliance checks on filesystem changes. See the full profile in the IDE Agents market map. Kiro is included here because its spec-first architecture makes it a significant reference point for the SDD category, even though its primary classification is as an IDE.

Adoption and Traction

  • gstack: 50,000+ GitHub stars in 16 days post-launch (March 12, 2026); 33,000 stars and 4,000 forks in the first week; topped Product Hunt at launch. Reported output of 600,000+ production lines of code in 60 days by creator Garry Tan.

  • Superpowers: 124,400 GitHub stars and 10,100 forks as of April 1, 2026; trending at #2 on GitHub in mid-March 2026; gained 1,867 stars in a single day on March 16.

  • GitHub Spec Kit: 71,000-72,700 GitHub stars; 3,460 forks; 22+ AI agent platforms supported; Microsoft Learn course launched for enterprise developers; IBM published an infrastructure-as-code variant (iac-spec-kit) demonstrating enterprise extension.

  • BMAD-METHOD: 29,600+ GitHub stars; V6.0.4 stable release shipped March 2, 2026; npm package size reduced 91%; 75 commits and 61 PRs in the V6 release.

  • OpenSpec: 28,000+ GitHub stars; v1.2.0 released February 25, 2026; Y Combinator launch listing active; brownfield guide published March 10, 2026.

  • GSD: 23,000+ GitHub stars; v1.28 shipped with forensics, milestone summaries, workstreams, and a manager dashboard; gsd-2 standalone CLI and gsd-opencode variant (for OpenCode) also active; trusted by engineers at Amazon, Google, Shopify, and Webflow.

  • Kiro: General availability since November 17, 2025; SageMaker Studio remote connectivity added March 2026; AWS HealthOmics Kiro extension launched January 2026; featured at AWS re:Invent 2025.

New Entrants & Watch List

Tessl (Agent Enablement Platform) is a commercially-backed integrated spec tool that warrants close attention. Tessl has launched two products: the Tessl Framework (teams define specs as "long-term memory" in the codebase, guiding agents across sessions) and the Tessl Spec Registry (10,000+ pre-built specs for open-source libraries, preventing AI API hallucinations and version mixups). The Spec Registry is a genuinely novel capability in the category: rather than generating specs for custom application logic, it provides pre-verified specs for known libraries, reducing a common failure mode in AI-assisted development. Tessl is commercial (pricing not publicly listed), and it was listed alongside GitHub Spec Kit, Kiro, and OpenSpec in the "three major platforms" summary from Augment Code's 2026 SDD overview. Archetype: Integrated spec tool. Reason to watch: the Spec Registry concept, if it achieves scale and currency, could become a dependency for any team running AI-assisted development against popular open-source libraries.

GSD-2 is a standalone CLI variant of GSD built on the Pi SDK, enabling autonomous long-running agents without context loss. It represents a meaningful architectural evolution from the original GSD (which is a Claude Code overlay) into a portable agent runtime. Archetype: Methodology overlay (Pi SDK variant). Reason to watch: if Pi SDK gains adoption, GSD-2 could become the reference implementation for spec-driven autonomous agents outside the Claude Code ecosystem.

No pure coding agents without spec-first architecture were identified as new entrants this week.

← Previous Cloud Agents Agents Next → Community Extensions Supporting Capabilities