Theory
Spec-kit is an open-source toolkit from GitHub that operationalizes Spec-Driven Development inside a standard GitHub workflow.
What Spec-kit provides
- A structured template set: spec files, plan files, and task checklists
- PR workflow integration specs live alongside code and are reviewed like code
- Review gates that keep product intent aligned with what's actually shipped
- A lightweight, file-based approach that works in any repo without additional tooling
The Spec-kit workflow
- Specify Write a spec file describing intent, constraints, and acceptance criteria
- Plan Generate or author a plan file with the implementation approach
- Tasks Break the plan into atomic, checkable tasks
- PR Open a pull request; the spec is the contract reviewers check against
When Spec-kit shines
Spec-kit works well for teams that want a low-ceremony, Git-native SDD approach without adopting a full framework. It integrates naturally into existing GitHub workflows and is a good starting point before evaluating heavier frameworks like BMAD.
Practice
Run this in a repository you already know, not a toy project. The point is to feel where the practice helps and where it gets in the way on code that has history.
- Install Spec-kit in a test repository following the official getting-started guide.
- Pick a small, real feature (a new API endpoint, a UI component, or a CLI command).
- Use Spec-kit's templates to write a spec, generate a plan, and break it into tasks.
- Hand the tasks file to an AI agent and have it implement the first task.
- Open a draft PR and verify the spec is visible in the PR description.