Skip to content
osickPublic

About

Benchmarking spec driven development frameworks

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

Β 

History

28 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Awesome Spec-Driven Development

A curated and benchmarked list of frameworks, tools, helpers, articles, talks, courses, books, and reports for spec-driven development (SDD) β€” the practice of putting a written specification at the centre of AI-assisted software engineering.

Last refreshed: 2026-05-12. Star history, scores, and dates are based on the primary repositories and the Sources section at the bottom.

Spec-driven development is the counter-movement to vibe coding: instead of throwing prompts at an LLM and hoping, you write a structured, versioned spec first and let agents work against it. SpecBench provides two things:

  • This list β€” every tool, helper, article, paper, podcast, and report we've found that meaningfully advances SDD. Curated, opinionated, annotated.
  • BENCHMARK.md + benchmark/ β€” a reproducible 8-dimension benchmark with an automated runner (benchmark/runner/) that produces objective, machine-readable scorecards for every framework. See the aggregated results.

Inclusion criteria — a resource is listed if it does at least one of: defines a structured spec artefact; provides a phased intent→spec→plan→tasks→code workflow; offers conventions that let humans and agents agree on "done"; or — for articles, books, talks — meaningfully informs the practice. Pure prompt collections, generic agent SDKs, and "rules files" with no methodology are out of scope.

Legend: 🟒 active Β· 🟑 maintained but slow Β· πŸ”΄ archived Β· 🏒 vendor-backed Β· 🌱 community Β· πŸ”’ closed source Β· ⭐ flagship in its category Β· πŸŽ“ educational Β· πŸ“„ paper Β· πŸ“˜ book Β· 🎀 talk Β· 🎧 podcast Β· πŸ“Š report.

Table of contents

Frameworks & tools

  1. End-to-end SDD frameworks
  2. Lightweight spec frameworks
  3. Vendor-IDE SDD platforms
  4. Multi-agent / role-play frameworks
  5. Context and convention files
  6. Spec languages and notations
  7. Planning, plan/act, architect modes
  8. Task management and orchestration
  9. PRD / intent capture
  10. Verification, contracts, formal methods
  11. Helpers, linters, validators
  12. MCP servers and dashboards
  13. Prompt and skill libraries
  14. Adjacent and supporting tools

Learning & community 15. Courses and trainings πŸŽ“ 16. Books πŸ“˜ 17. Articles and essays 18. Academic papers πŸ“„ 19. Talks and videos 🎀 20. Podcasts 🎧 21. Industry reports and statistics πŸ“Š 22. Historical lineage 23. Other awesome lists 24. Communities

Contributing Β· Sources


1. End-to-end SDD frameworks

Cover the full intent β†’ spec β†’ plan β†’ tasks β†’ code lifecycle.

  • ⭐ GitHub Spec Kit 🟒🏒 β€” Python CLI toolkit. Four-phase slash-command flow: /specify, /plan, /tasks, /implement. Supports 30+ coding agents (Claude Code, Copilot, Cursor, Gemini CLI, Codex). The most adopted open-source SDD reference implementation; ~93k stars as of May 2026.
  • BMAD-METHOD 🟒🌱 β€” "Breakthrough Method for Agile AI-Driven Development". MIT, ~46k stars. 21 named-persona agents (Mary the Analyst, Preston the PM, Winston the Architect, Sally the PO, Simon the SM, Devon the Dev, Quinn the QA …) and 50+ workflows. "Party Mode" puts multiple personas in one session.
  • Agent OS 🟒🌱 β€” Three-layer context (Standards / Product / Specs). v3 defers spec writing to the host agent's plan mode and adds /shape-spec and /discover-standards. Works with Claude Code, Cursor, Antigravity.
  • Claude Code Spec Workflow (Pimzino) 🟒🌱 β€” Requirements β†’ Design β†’ Tasks β†’ Implementation flow for Claude Code, with a parallel bug-fix workflow (Report β†’ Analyze β†’ Fix β†’ Verify).
  • cc-sdd 🟒🌱 β€” A minimal, adaptable SDD harness packaged as Agent Skills. Supports Claude Code, Codex, Cursor, Copilot, Windsurf, OpenCode, Gemini CLI, Antigravity. Phase-gated: agents write the spec, humans approve the contract.
  • MoAI-ADK 🟒🌱 β€” Agentic Development Kit for Claude Code with 24 specialised agents and 52 skills. Auto-applies TDD on greenfield, DDD on brownfield-with-no-tests.
  • Colign 🟒🌱 β€” AI-powered spec-writing and team-alignment platform. Exposes specs as an MCP server so Claude Code, Cursor, Windsurf, and VS Code Copilot can all read/write them.
  • SPARC / SPARC2 / claude-flow 🟒🌱 β€” Specification β†’ Pseudocode β†’ Architecture β†’ Refinement β†’ Completion. Integrated with Roo Boomerang orchestration and claude-flow swarm mode.
  • cc-spex 🟒🌱 β€” SDD based on Spec Kit, extended with custom traits.

2. Lightweight spec frameworks

Minimal ceremony, plain markdown, designed to graft onto any repo.

  • ⭐ OpenSpec 🟒🌱 β€” Three-phase state machine (propose β†’ apply β†’ archive) and delta specs (ADDED / MODIFIED / REMOVED markers). Explicitly designed for brownfield. Each change becomes a folder with proposal.md, specs/, design.md, tasks.md. Companion list: awesome-openspec.
  • LeanSpec 🟒🌱 β€” Five first principles: context economy (specs < 2k tokens), signal-to-noise, intent over implementation, bridge the human/AI gap, progressive disclosure. Targets <100 lines per spec.
  • fspec 🌱 β€” Gherkin-based spec system that auto-generates tests and links code to business rules.
  • spec-driver 🌱 β€” small community framework from the spec-driven topic.
  • Shotgun / get-shit-done / MetaSpec / quint-code / adversarial-spec 🌱 β€” smaller experimental frameworks tracked by the Engineering4AI list.

3. Vendor-IDE SDD platforms

Tightly integrated, IDE-bound, vendor-stewarded.

  • ⭐ Kiro πŸŸ’πŸ’πŸ”’ β€” AWS agentic IDE. Spec is "the unit of work": requirements.md (EARS notation), design.md, tasks.md per feature, plus cross-cutting steering docs. Builds a dependency graph from tasks and runs independent tasks in concurrent "waves". Agent Hooks and MCP integration.
  • ⭐ Tessl πŸŸ’πŸ’πŸ”’ β€” Agent Enablement Platform. Installs "tiles" into .tessl/; any MCP-compatible agent reads them. The spec-driven-development tile forces interview-first then spec-first behaviour. The Tessl Spec Registry has 10k+ pre-built specs of OSS libraries so agents don't hallucinate APIs.
  • Zencoder πŸŸ’πŸ’πŸ”’ β€” IDE assistant with a documented spec-driven workflow.

4. Multi-agent / role-play frameworks

Use named personas to model a real product team.

  • BMAD-METHOD (see Β§1) β€” the canonical example with 21 personas.
  • Roo Code Orchestrator / Boomerang Tasks 🟒🌱 β€” An "Orchestrator" mode breaks a complex task into sub-tasks, each delegated to a specialised mode (Code / Architect / Debug). Each sub-task runs in isolated context; only summaries return to the parent ("boomerang").
  • CrewAI 🟒🌱 β€” Framework for orchestrating role-playing autonomous agents β€” each agent has a role, goal, and backstory. Not SDD-specific but widely used to build SDD pipelines.
  • Microsoft AutoGen 🟒🏒 β€” Conversational multi-agent framework with the classic Solver/Critic pattern. Often the substrate under custom SDD orchestrations.
  • awesome-claude-code-subagents 🟒🌱 β€” 100+ specialised Claude Code subagents covering many development use cases.
  • claude-flow swarm mode 🟒🌱 β€” Parallel SPARC sub-tasks with a swarm coordinator.

5. Context and convention files

Single-file or single-folder conventions any agent can consume.

  • ⭐ AGENTS.md 🟒🌱 β€” Vendor-neutral "README for agents". Adopted by OpenAI Codex, GitHub Copilot, Cursor, Aider, Continue, Google Jules, Factory, Amp. Stewarded by the Agentic AI Foundation under the Linux Foundation; 60k+ open-source projects.
  • CLAUDE.md 🟒🏒 β€” Claude Code's project-memory convention; hierarchical user/project/local scopes.
  • Cursor Rules .mdc 🟒🏒 β€” YAML frontmatter (description, globs, alwaysApply). Four activation modes: Always / Auto-Attached / Agent-Requested / Manual. Replaces the older single-file .cursorrules. Reference list: awesome-cursor-rules-mdc.
  • GitHub Copilot custom instructions 🟒🏒 β€” .github/copilot-instructions.md repo-level guidance.
  • Aider CONVENTIONS.md 🟒🌱 β€” Plain-markdown conventions loaded via /read CONVENTIONS.md or .aider.conf.yml.
  • Cline Memory Bank 🟒🌱 β€” Six-file structured memory (projectBrief.md, productContext.md, systemPatterns.md, techContext.md, activeContext.md, progress.md) that survives context resets. Pairs with Cline Plan/Act.
  • Continue.dev rules 🟒🌱 β€” Composable rule files attached per workspace or model.

6. Spec languages and notations

Formal-ish languages designed for human + AI consumption.

  • ⭐ EARS 🟒🌱 β€” Easy Approach to Requirements Syntax. "WHEN … THE SYSTEM SHALL …" patterns developed at Rolls-Royce; used by Kiro and many newer frameworks.
  • Gherkin / Cucumber 🟒🌱 β€” Given/When/Then BDD scenarios. Predates AI; re-emerging as spec input.
  • SpecFlow / Reqnroll 🟒🌱 β€” .NET BDD framework (Reqnroll is the maintained fork of SpecFlow).
  • TLA+ 🟒🌱 β€” Formal spec language for state machines; increasingly paired with LLMs for safety-critical systems.
  • Alloy 🟑🌱 β€” Lightweight formal modelling.
  • Spec# / JML / OCL β€” Design-by-Contract heirs to Eiffel.
  • OpenAPI / AsyncAPI / JSON Schema / Protocol Buffers / GraphQL SDL 🟒🌱 β€” Structural contracts embedded as the "interface" layer of many spec frameworks.
  • FPF β€” First Principles Framework 🌱 β€” Rigorous specification framework for modelling systems and knowledge.

7. Planning, plan/act, architect modes

Turn an approved spec into an executable plan before any edit lands.

  • Claude Code plan mode 🟒🏒 β€” Read-only plan phase; the default planning slot for many other frameworks.
  • Cline Plan / Act 🟒🌱 β€” Plan evaluates Memory Bank completeness, Act executes and documents.
  • Aider architect / editor mode 🟒🌱 β€” Two-model split: smart "architect" proposes, cheaper "editor" emits diffs.
  • Roo Code Architect mode 🟒🌱 β€” Dedicated planning mode; entry point to Boomerang orchestration.
  • Goose plan mode 🟒🌱 β€” Block's open-source agent with a separate planning step.

8. Task management and orchestration

Spec β†’ task graph β†’ execution.

  • TaskMaster (claude-task-master) 🟒🌱 β€” PRD-to-task system, MCP-served. parse-prd, list, next. Topologically ordered, dependency-aware. Works in Cursor, Lovable, Windsurf, Roo.
  • Backlog.md 🟒🌱 β€” Markdown-first task tracking.
  • Spec Kitty 🌱 β€” Workflow helper for spec-driven repos.
  • vibe-kanban 🌱 β€” Kanban UI tuned for AI workflows.

9. PRD / intent capture

Front-of-the-funnel: capturing what we want before we spec it.

  • ChatPRD πŸŸ’πŸ’πŸ”’ β€” AI PM co-pilot; drafts and iterates PRDs from briefs. ~100k PM users.
  • Amazon PRFAQ / Working Backwards 🟒🌱 β€” Press-release-first product definition. Cultural ancestor of much SDD.
  • Vibe Coding Prompt Template 🟒🌱 β€” Templates and workflow for generating PRDs, tech designs, MVPs via LLMs.
  • BMAD Analyst persona (Mary) β€” structured discovery phase.

10. Verification, contracts, formal methods

Closing the loop: mechanically proving the spec is satisfied.

  • ⭐ Schemathesis 🟒🌱 β€” Property-based API testing generated from OpenAPI / GraphQL. Built on Hypothesis. Finds 500s, schema violations, validation bypasses, stateful bugs.
  • Pact 🟒🌱 β€” Consumer-driven contract testing β€” HTTP and message integrations. JavaScript, .NET, JVM, Python, Ruby, Go.
  • Hypothesis / fast-check / PropEr 🟒🌱 β€” Property-based testing libraries; pair well with spec-derived invariants.
  • Stainless 🟒🏒 β€” Code generation from OpenAPI; the "code-from-spec" half.
  • TLA+ model checker (TLC) 🟒🌱 β€” Exhaustive checking for critical state machines.
  • Reqnroll / SpecFlow 🟒🌱 β€” .NET acceptance test runners for Gherkin specs.
  • BMAD QA persona (Quinn) β€” workflow-encoded verification gate.

11. Helpers, linters, validators

Quality gates for the spec itself.

12. MCP servers and dashboards

  • ⭐ spec-workflow-mcp (Pimzino) 🟒🌱 β€” MCP server exposing the Requirements β†’ Design β†’ Tasks β†’ Implementation workflow. Real-time web dashboard (port 5000), VS Code sidebar extension, approval workflow, task progress bars. Works with Claude Desktop, Cursor, Continue, Cline, and others.
  • mcp-server-spec-driven-development 🌱 β€” Generic MCP server for SDD.
  • Glama MCP catalogue β€” index of MCP servers including several SDD-relevant ones.

13. Prompt and skill libraries

Reusable building blocks.

14. Adjacent and supporting tools

  • Model Context Protocol (MCP) 🟒🌱 β€” Transport many spec frameworks expose themselves over.
  • Specstory 🟒🏒 β€” Captures and curates agent session history; raw material for after-the-fact specs.
  • VibeDoc 🌱 β€” Documentation companion for spec-driven repos.

15. Courses and trainings πŸŽ“

16. Books πŸ“˜

  • AI Engineering β€” Chip Huyen, O'Reilly 2025 β€” Foundation-model app engineering; relevant chapters on evaluation, prompt engineering, agents. Companion repo: chiphuyen/aie-book.
  • Working Backwards β€” Colin Bryar & Bill Carr, 2021 β€” Authoritative account of Amazon's PR/FAQ method. The cultural ancestor of intent-first SDD.
  • Specification by Example β€” Gojko Adzic, 2011 β€” How successful teams deliver the right software via collaborative spec workshops; the foundational ATDD text.
  • Bridging the Communication Gap β€” Gojko Adzic, 2009 β€” Original ATDD / "agile acceptance testing" book.
  • ATDD by Example β€” Markus GΓ€rtner, 2012 β€” Practical guide to acceptance-test-driven development.
  • Object-Oriented Software Construction β€” Bertrand Meyer, 1997 (2nd ed.) β€” Design by Contract; pre + post conditions and class invariants. The intellectual ancestor of executable specs.
  • The PRFAQ Framework β€” Marcelo Calbucci, 2024 β€” Modern, opinionated guide to running the PR/FAQ at non-Amazon companies.

17. Articles and essays

18. Academic papers πŸ“„

  • Large Language Models for Requirements Engineering: A Systematic Literature Review β€” 74 primary studies (2023–2024). Arxiv: 2509.11446.
  • Using LLMs in Software Requirements Specifications: An Empirical Evaluation β€” Arxiv: 2404.17842.
  • LLM-Assisted Repository-Level Generation with Structured Spec-Driven Engineering β€” Arxiv: 2605.02455.
  • Leveraging LLMs for Formal Software Requirements: Challenges and Prospects (VERIFAI project) β€” Arxiv: 2507.14330.
  • Exploring the Use of LLMs for Requirements Specification in an IT Consulting Company β€” Arxiv: 2507.19113.
  • Aligning Requirements for LLM Code Generation (Specine) β€” Arxiv: 2509.01313.
  • Improving LLM Code Generation via Requirement-Aware … β€” Arxiv: 2605.00433.
  • Vibe Coding: Programming through Conversation with AI β€” Arxiv: 2506.23253.
  • From Online User Feedback to Requirements: Evaluating LLMs for … β€” Arxiv: 2510.23055.
  • Design by Contract β€” Bertrand Meyer, IEEE Computer, 1992 (ACM DL). The foundational paper for executable specifications.

19. Talks and videos 🎀

20. Podcasts 🎧

21. Industry reports and statistics πŸ“Š

22. Historical lineage

SDD didn't appear from nothing. Useful prior art:

23. Other awesome lists

24. Communities

  • r/ChatGPTCoding β€” large active community on AI coding workflows, including SDD discussions.
  • BMAD Discord β€” linked from the BMad Method docs.
  • OpenSpec / Spec Kit issue trackers β€” primary venue for framework questions.
  • Cursor Forum β€” practitioner threads on rules, planning, SDD recipes.

Contributing

PRs welcome. Each entry needs: name, link, status emojis, one sentence on what makes it spec-driven, and β€” if proposing a new category β€” a one-line definition. See CONTRIBUTING.md. Promotional language, sponsored placements, and entries that are only "AI assisted" without an SDD angle will be rejected.

Sources

This refresh was built from May 2026 web research; full per-section sources in commit history. Key primary sites:

  • Framework repos: github/spec-kit, bmad-code-org/BMAD-METHOD, Fission-AI/OpenSpec, buildermethods/agent-os, eyaltoledano/claude-task-master, Pimzino/claude-code-spec-workflow + spec-workflow-mcp, gotalab/cc-sdd, modu-ai/moai-adk, colign/colign, codervisor/lean-spec, tesslio/spec-driven-development-tile, RooCodeInc/Roo-Code, Aider-AI/aider, schemathesis/schemathesis, jonverrier/RequirementLinter, crewaiinc/crewai, microsoft/autogen, anthropics/skills.
  • Docs sites: kiro.dev/docs, docs.cline.bot, docs.roocode.com, docs.tessl.io, aider.chat/docs, agents.md, chatprd.ai, lean-spec.dev, cucumber.io, reqnroll.net, modelcontextprotocol.io, schemathesis.io, pact.io.
  • Surveys & comparisons: MarkTechPost, Augment Code, Medium (Vishal Mysore, Tim Wang), Martin Fowler, Microsoft for Developers, Class Central, DeepLearning.AI, Anthropic engineering blog.
  • Academic: arXiv 2509.11446, 2404.17842, 2605.02455, 2507.14330, 2507.19113, 2509.01313, 2605.00433, 2506.23253, 2510.23055.
  • Existing awesome lists (linked above).

Project artefacts

This list is one of two artefacts in SpecBench. The other:

  • BENCHMARK.md β€” Methodology, 8-dimension rubric, five reproducible tasks (CRUD-from-PRD, add-feature, refactor, handover, model-swap), per-framework scorecards, aggregated results, and an automated runner that produces objective, machine-readable scorecards so the comparison is reproducible across frameworks and over time.

License: content CC-BY-4.0; code samples MIT.

About

Benchmarking spec driven development frameworks

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages