GitHub Spec Kit enables spec-first workflow for coding agents

GitHub has put out Spec Kit, an open source toolkit built around an idea it calls Spec-Driven Development, and the pitch is a genuine reversal of how software has worked for decades. Code has always been the finished product, with specs treated as throwaway scaffolding. Spec Kit tries to make the specification itself the thing that matters, generating the implementation directly from it rather than using it as a rough guide a developer eventually ignores.

The mechanics run through a command-line tool called Specify CLI, installed via a package manager called uv (or from PyPI), and a project workflow built on slash commands. A developer starts a project, runs a command to set governing principles for the codebase, then describes what they want built with a focus on the what and why rather than the tech stack. From there separate commands handle the technical plan, break the plan into tasks, and finally execute the implementation. There are also optional commands for clarifying vague requirements, checking consistency across the spec and plan, and generating checklists to catch gaps before code gets written.

What stands out is how agent-agnostic the whole thing is. Spec Kit says it works with more than 30 AI coding agents, spanning both command-line tools and IDE-based assistants, and some integrations even support a skills mode instead of the usual slash-command prompts. That's a deliberate bet that the workflow matters more than which specific AI model or tool a team happens to use.

GitHub also built in a layered customization system: extensions add entirely new capabilities like external tool integrations, presets change the format or terminology of existing outputs, and bundles package both together into role-based setups so an entire team persona, say a product manager or a security researcher, can be provisioned with a single command. The project explicitly separates greenfield work, starting an app from a blank slate, from brownfield work, where the goal is adding features or modernizing legacy systems without breaking existing behavior. It even flags that developers should treat tooling upgrades and evolving spec content as separate concerns, which suggests GitHub has already run into teams conflating the two.

There's a community layer too, with independently maintained extensions, presets, and walkthroughs that GitHub explicitly says to review before installing, since it isn't vetting third-party contributions itself.