A comprehensive research and comparison of spec-driven development (SDD) tools for AI-assisted coding, including analysis of git worktree support, architectural approaches, and practical recommendations.
This repository contains in-depth research comparing spec-driven development tools, agent orchestration, and the emerging execution layer for AI-assisted coding.
- GitHub Spec-Kit - Open-source CLI toolkit for greenfield projects
- Spec Kitty - Community fork with built-in git worktree orchestration
- BMad Method - Enterprise framework with 21 specialized AI agents
- OpenSpec - Lightweight change-management for brownfield projects
- Kiro - AWS-backed agentic IDE with multimodal input
- Tessl - Experimental spec-as-source platform
- GSD - Meta-prompting SDD system with wave-based context management (11.9K stars)
- Ralph Loop - Stateless iterative execution pattern by Geoffrey Huntley
- Zencoder/Zenflow - Commercial SDD-as-a-Service platform
- Kilo Code - Open-source agentic platform with Memory Bank ($8M seed, 1.5M users)
- Conductor - macOS parallel agent runner using git worktrees
- PromptX - AI agent context platform via MCP (gap entry)
Critical Gap: Most SDD tools excel when requirements are clear upfront but struggle with iterative changes like "change button from blue to green."
- OpenSpec - Purpose-built for modifications with delta format (ADDED, MODIFIED, REMOVED)
- Tessl - Spec-as-source enables edit-and-regenerate (but closed beta)
- Spec-Kit - Requires
/speckit.clarifyworkaround, not optimized for small changes - Kiro/BMad - "Sledgehammer to crack a nut" problem for trivial changes
See Iterative Development Analysis and Use Case Scoring for details.
Spec Kitty is the only tool with built-in git worktree support, enabling:
- Automatic worktree creation per feature
- Parallel feature isolation without branch switching
- Automated cleanup on merge
- Spec-First: Specs precede coding but are discarded (Spec-Kit, Kiro, BMad)
- Spec-Anchored: Specs persist and evolve (OpenSpec, Spec Kitty)
- Spec-as-Source: Only specs are edited, code auto-generates (Tessl)
The research is organized into focused, digestible documents:
- GitHub Spec-Kit - Open-source CLI toolkit
- Spec Kitty - Community fork with worktree support
- BMad Method - Enterprise framework with 21 agents
- OpenSpec - Lightweight change management
- Kiro - AWS-backed agentic IDE
- Tessl - Experimental spec-as-source platform
- GSD (Get Shit Done) - Context-engineered SDD for solo developers
- Ralph Loop - Stateless iterative execution pattern
- Comparison Matrices - Side-by-side feature comparisons (incl. AGENTS.md support)
- Use Case Scoring - 12 real-world scenarios graded + expanded 11-tool heatmap
- Iterative Development - Spec modification workflows
- Git Worktree Support - Detailed worktree analysis (updated with Beads, Conductor)
- Recommendations - Decision frameworks by use case
- Critical Analysis - Concerns, critiques, and future outlook
- Sources - All citations and references
- Orchestration Landscape - 30+ multi-agent tools surveyed, including Claude Code Agent Teams
- Beads, Agent Mail & Gas Town - Agent memory, messaging, and multi-agent villages
- Gaps: New Frameworks - Zencoder, Kilo Code, Conductor, PromptX (GSD & Ralph Loop promoted to full profiles)
- Beads + OpenSpec Cheatsheet - Practical setup and daily workflow
| Tool | License | Git Worktrees | Best For | Maturity |
|---|---|---|---|---|
| Spec-Kit | Open Source | No | Greenfield projects | Production |
| Spec Kitty | Open Source | Yes | Parallel development | Active Dev |
| BMad Method | Open Source | No | Enterprise workflows | Stable (v6.0.2) |
| OpenSpec | MIT | No | Brownfield changes | Production |
| Kiro | Proprietary | No | IDE experience | Preview |
| Tessl | Proprietary | No | Spec-as-source | Beta |
Use Spec Kitty - Only tool with built-in worktree management and parallel feature isolation.
Use OpenSpec - Lightweight change management without excessive overhead.
Use BMad Method - Comprehensive workflows with 21 specialized agents.
Use Spec-Kit - Battle-tested, constitution-driven development.
Try Kiro or Tessl - Cutting-edge approaches with free preview/beta access.
The research includes analysis of:
- The Waterfall Question: Does SDD reintroduce waterfall bureaucracy?
- AI Adherence Issues: Agents frequently ignore specifications
- Scalability Concerns: Unclear when SDD adds value vs. overhead
- Historical Parallels: Similarities to failed Model-Driven Development (MDD)
- 25% of Y Combinator Winter 2025 cohort has 95% AI-generated codebases
- Industry leaders predict developers won't look at code by 2027
- Specifications becoming "the fundamental unit of programming"
See CONTRIBUTING.md for contribution guidelines.
See CHANGELOG.md for version history and changes.
This project is licensed under the MIT License - see the LICENSE file for details.
All research is compiled from publicly available sources including:
- Official tool documentation and repositories
- Industry blog posts and articles
- Comparative analyses from Martin Fowler, Medium, and others
- Critical perspectives from Marmelab, RedMonk, and Thoughtworks
Full source citations are available in docs/sources.md.
For questions, issues, or suggestions, please open an issue on GitHub.
Last Updated: 2026-02-24
