Awesome Spec-Driven Development (SDD)

A curated list of awesome tools for Spec-Driven Development (SDD) - the practice of writing specifications first to guide development, testing, and documentation.

Spec-Driven Development is a methodology where comprehensive specifications are created before implementation begins. This approach ensures better alignment between requirements and delivery, improves code quality, and facilitates better testing and documentation.

Introductions

• Awesome Agent Workflows - 41 copy-paste workflow cards for coding agents, from spec-to-plan and task contracts with scope and stop conditions to verification gates and fresh-context review, plus real failure stories with the guardrail each produced.

• How to write a good spec for AI agents - Explores why specifications are becoming the most important skill in the age of AI agents.

• Internal tool blueprints - 37 worked example specs for internal business tools (data model, numbered rules with worked examples, seed data, phased prompts and acceptance checks), 13 of them build-tested with the spec gaps each build exposed.

• Spec-Driven Development: the book - Free open book on SDD with AI agents (EN, pt-BR), with an SDD kit for Claude Code.

• Spec-first development: brainstorm, spec, plan, implement - Workflow for writing the spec before an agent codes, with the artifact each step produces, common pitfalls, and an as-built example from the author's own repo.

• What Is Spec-Driven Development? A Practitioner's Guide - Practitioner guide to SDD: what a spec is, the four pillars, the EARS format, a full worked spec, and when to skip it.

Standards

• agents.md - Markdown-based specification format for defining AI agent behaviors and capabilities.

• ANSS - Open specification standard for AI coding agents: invariants with verifiable checks, agent-first sections, and a spec review before any code is written.

• FPF - First Principles Framework - Rigorous specification framework for modeling systems, methods, and knowledge with auditable assurance levels and machine-readable patterns.

Specification Tools

• adversarial-spec - Iteratively refines product specifications by facilitating a debate among multiple LLMs.

• Archcore - Spec-driven development and context engineering for Claude Code, Cursor, Codex, and GitHub Copilot — backed by project context in Git.

• Cage - Deterministic contract harness for TypeScript that keeps specifications, implementations, tests, and agent review state in sync.

• dotdog - CLI tool for structured software specs. Write .dog files, compile to .dag graphs, query via MCP. Validate completeness, detect drift. 94% token savings.

• DriftWire - CLI that detects API contract drift: validate a live API against its OpenAPI spec, or diff two spec versions for breaking changes.

• gsd-core - Light-weight meta-prompting, context engineering, and spec-driven development system for AI coding agents.

• idea-to-blueprint - Agent skill for Claude Code, Codex and claude.ai that turns a raw idea into one evidence-backed build spec (web-researched stack with pinned versions, epics, Given/When/Then acceptance criteria, tests), then has the agent build one epic per fresh session.

• intent-verify - Deterministic, model-free CLI that checks whether a repository still lexically covers the acceptance items in a Markdown spec before human review; a token-overlap signal, not a semantic judgment.

• Kibi - Keeps requirements connected to code and tests, and checks for missing links as AI agents work.

• lean-spec - Lightweight framework for focused specifications under 2,000 tokens designed for humans and AI assistants.

• MetaSpec - Meta-specification framework enabling AI agents to auto-generate spec-driven toolkits.

• MySpec - Spec-driven development platform compiling guided developer discovery interviews into deterministic 4-file bundles (constitution.md, requirements.md, solution.md, tasks.md) with MCP server integration.

• OpenSpec - Aligns developers and AI assistants on specifications before code is written.

• openspec-scaffold - CLI that writes the four OpenSpec change files (proposal, spec, design, tasks) for you.

• quint-code - Structured reasoning framework for AI coding tools implementing hypothesis-driven spec development with automated design rationale records.

• reqlan - Language for a requirements graph next to the code: named .rq ideas, LSP, links to symbols and tests, MCP for agents.

• Reqode - Connects branch-aware requirements, architecture, code, and tests, with MCP context and Findings for external coding and QA agents.

• Shotgun - Codebase-aware spec writing tool that keeps AI coding agents on track.

• spec-driver - Reimagines specs as evergreen truth systems that emit deltas to conform code to vision.

• Spec Kit - Focuses developers on product scenarios and predictable outcomes over ad-hoc coding.

• Squelette - Repository-level governance for coding agents: work items declare the file paths they may touch, a pre-commit gate refuses anything outside them, human decisions are recorded in the repo, and a task cannot close without evidence verified against its artifacts.

• vibe-coding-prompt-template - Staged prompts and a CLI that produce a PRD, a technical design, and AGENTS.md before implementation begins.

Development Frameworks

• agent-skills - Production-grade skill pack for AI coding agents with explicit spec-to-plan-to-build workflows and quality gates.

• AI Unified Process - Requirements-first methodology inspired by the Rational Unified Process, with Skill plugins that go from requirements and use case specs to code and tests with full traceability. See unifiedprocess.ai.

• BMAD-METHOD - Breakthrough Method for AI-driven Agile Development, providing a modular framework for agile AI workflows.

• cc-sdd ![](https://img.shields.io/git