If you’ve spent any time working with AI coding agents, you know the routine. You describe what you want. The agent generates code that looks right. You run it. It breaks — or worse, it works but solves the wrong problem.
This frustrating pattern has earned a name: Vibe coding. You give the AI a vague idea and hope it guesses correctly. For quick prototypes, that’s fine. For production software, it’s a real problem.
GitHub’s answer is Spec Kit — a new open-source toolkit for spec-driven development that provides a structured process to bring spec-driven development to your coding agent workflows with tools including GitHub Copilot, Claude Code, and Gemini CLI.
The core idea is simple: Write the spec first.
Specs as the Source of Truth
For decades, code has been king. Specifications served code — they were the scaffolding we built and then discarded once the “real work” of coding began. We wrote PRDs to guide development, created design docs to inform implementation, and drew diagrams to visualize architecture. But these were always subordinate to the code itself.
Spec-Driven Development (SDD) flips that. Instead of coding first and writing docs later, you start with a spec. This contract defines how your code should behave and serves as the source of truth for your tools and AI agents to generate, test, and validate code. The result is less guesswork, fewer surprises, and higher-quality code.
Spec Kit packages templates, a CLI, and prompts to center work around a specification first, then a technical plan, then a set of small, testable tasks that AI agents implement.
“GitHub’s Spec Kit signals AI-assisted coding is shifting from prompts to durable, versioned specifications. Vendors are competing to own the artifact that governs intent across Copilot, Claude Code, and Gemini CLI,” according to Mitch Ashley, VP and practice lead for software lifecycle engineering at The Futurum Group.
“For engineering leaders, the specification becomes the unit of governance across agents and contributors. Teams treating spec-driven development as optional will accumulate AI-generated technical debt no agent capability can refactor away, and verification at each checkpoint cannot be deferred to the agent producing it.”
How it Works
At the heart of Spec Kit is what GitHub calls a “constitution” — a document that captures the non-negotiable principles for a project. Think of it as a permanent rules file that every subsequent command references. From there, the workflow follows four phases: Specify, plan, tasks, and implement.
Each of Spec Kit’s seven slash commands represents a key stage in the spec-driven workflow — from defining your project’s core principles to generating the final implementation. Developers interact with these commands directly inside their coding agent of choice.
Spec Kit is distributed as a CLI that can create workspace setups for a wide range of common coding assistants. Once that structure is set up, you interact with Spec Kit via slash commands in your coding assistant. Because all of its artifacts are put right into your workspace, it’s the most customizable approach.
Your primary role is to steer; the coding agent does the bulk of the writing. But steering is an active job. GitHub is explicit about this: your job isn’t just to prompt and approve. It’s to verify at each checkpoint before moving to the next phase.
Where it Makes the Most Sense
GitHub highlights three scenarios where Spec Kit is most helpful: Greenfield projects, feature work in existing systems, and legacy modernization. In each case, the spec captures the stable “what,” while the plan and tasks drive the flexible “how,” reducing rework and making changes predictable.
Instead of starting from scratch with each prompt, Spec Kit maintains a persistent understanding of your project. Every AI interaction adheres to the same constitution, specifications, and technical plans, ensuring consistent output aligned with your project’s goals. Multiple developers can work with the same AI assistant using the same project context. New team members can quickly understand the project by reading the spec files.
That last point matters specifically for DevOps teams. Consistency across a shared codebase — especially when multiple contributors are using different AI tools — is one of the hardest things to maintain. Spec Kit gives everyone a common reference point.
Still Early, But Worth Watching
Not everyone is sold. Gojko Adzic, a consultant and author of several books covering software delivery and specification practices, frames spec-driven development as both a logical evolution and a potential overcorrection, warning that its structure could reintroduce some of the rigidity agile methods sought to escape. It’s a fair concern. Heavyweight spec processes have been tried before.
But Spec Kit isn’t asking you to write 80-page requirements documents. The spec is meant to be lean and living — something you update as the project evolves, not something you waterfall your way through before anyone writes a line of code.
GitHub open-sourced the Spec Kit because this approach is bigger than any one tool or company. The real innovation is the process.
It’s still early days for Spec Kit, and it won’t fix the challenges of AI-assisted coding overnight. But it points to where the next wave of tools might be headed: systems that don’t just generate code but also understand what that code is meant to achieve.
For DevOps teams already wrestling with how to govern AI-assisted development at scale, that’s a conversation worth having now — before the vibe-coded technical debt starts piling up.