GitHub open-sourced Spec Kit, a toolkit for spec-driven development that has over 110,000 stars. The idea is simple: instead of vibe coding and hoping AI guesses your intent, you write a clear spec first, then AI implements according to that spec.
GitHub open-sourced Spec Kit, a toolkit for spec-driven development that has over 110,000 stars. The idea is simple: instead of vibe coding and hoping AI guesses your intent, you write a clear spec first, then AI implements according to that spec.
Spec Kit is an open-source toolkit maintained by GitHub that helps you practice Spec-Driven Development. Instead of telling an AI agent to "code this feature" and hoping it guesses the main flow, data model, error handling, and definition of done correctly, you write a structured spec that defines what to build, why it matters, what the constraints are, and what the acceptance criteria are. The spec then becomes executable, meaning it directly generates implementation code rather than just sitting in a document.
The toolkit includes a CLI called specify, installed via uv, and a seven-step workflow: constitution, specify, plan, tasks, implement, and converge. Each step corresponds to a slash command that you run inside your AI coding agent. Spec Kit is compatible with over 30 AI coding agents, including Claude Code, GitHub Copilot, Codex CLI, Cursor, Windsurf, Cline, and Aider, so you are not locked into one tool.
specify bundle install command sets up everything for your role.The workflow has seven steps. Constitution defines project principles. Specify describes what to build. Plan chooses the tech stack. Tasks breaks the work into a task list. Implement has the AI code according to the plan. Converge checks whether the code matches the spec. Each step is a slash command: /speckit.constitution, /speckit.specify, /speckit.plan, /speckit.tasks, /speckit.implement. You run these inside your AI coding agent, and Spec Kit generates the appropriate context and instructions for the agent to follow.
To get started, you install the CLI with uv tool install specify-cli, initialize a project with specify init, choose your integration, and the slash commands appear in the agent you are using.
Spec Kit is a toolkit, not a magic button. It does not generate code by itself; it requires an AI coding agent to run. If your spec is vague, has no non-goals, and no acceptance criteria, the AI will still guess like before. Spec quality determines code quality. The multi-step workflow can also feel heavy for small tasks or quick prototypes where vibe coding is faster. Installing uv and the specify CLI is an extra setup step compared to just opening a chat and typing a prompt.
Spec Kit is for developers who are using AI coding agents for real work and want more predictable results. If you find that AI often misses your intent, produces inconsistent code, or needs multiple rounds of correction, the spec-driven approach can help. It is not for someone who just wants a quick prototype or a one-off script.
If you are using AI to code for real, try changing your workflow. Do not tell AI to "code this feature." Write a spec first, then tell AI to implement according to that spec. GitHub Spec Kit helps you do exactly that.