# Spec Kit

> GitHub's open-source toolkit for spec-driven development — the specify CLI and /speckit slash commands that walk any coding agent from constitution to implementation.

Spec Kit (GitHub, MIT, ~111k stars since its September 2025 launch) productized spec-driven development: specify init scaffolds a project, then /speckit.constitution, .specify, .plan, .tasks, and .implement walk your coding agent through the pipeline — each phase emitting a markdown artifact that feeds the next. Works with 30+ agents including Claude Code, Copilot, and Cursor.

Website: https://github.com/github/spec-kit

Spec Kit is GitHub's answer to the chaos question of agentic coding — *piecemeal prompting produces piecemeal software* — and the answer landed: ~111k stars in nine months made it the standard expression of [spec-driven development](/guides/workflow/spec-driven-development). It doesn't replace your agent; it gives your agent a process.

## Highlights

- **The five-phase pipeline** — `/speckit.constitution` (principles) → `.specify` (the what/why, deliberately no tech stack) → `.plan` (architecture and stack) → `.tasks` (actionable, checkable list) → `.implement` — each phase a reviewed markdown artifact feeding the next.
- **Quality gates** — `/speckit.clarify` interrogates vague specs before planning; `/speckit.analyze` cross-checks artifacts for drift; `/speckit.checklist` generates requirement checklists; `.taskstoissues` turns tasks into GitHub issues.
- **Agent-agnostic** — 30+ integrations (Claude Code, Copilot, Gemini CLI, Codex, Cursor, Windsurf…); commands install as the agent's native slash commands or as skills.
- **Extensible** — extensions add commands/workflows (Jira, code review), presets override templates for compliance formats or house terminology, with project-local overrides.
- **Brownfield too** — built for greenfield, parallel exploratory implementations, and iterative modernization of existing systems.

## In an AI-assisted workflow

```bash
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@v0.10.2
specify init my-project --integration claude
# then, inside Claude Code:
# /speckit.specify → /speckit.plan → /speckit.tasks → /speckit.implement
```

The artifacts are the point: a `spec.md` and `plan.md` you review before code exists, and that re-anchor any future session — the [persistence that prompts lack](/guides/configuration/claude-code-memory-context).

> [!NOTE]
> It moves fast: releases ship weekly-ish (v0.10.x as of June 2026), templates change between them, and the old `--ai` flag is gone — pin a tag, and prefer `specify self upgrade` for updates. Community extensions are third-party; review before installing.

## Good to know

MIT, Python 3.11+ with `uv`, launched September 2, 2025 via the GitHub blog and snowballed as the antidote-to-vibe-coding narrative took hold. The methodology it implements — when specs pay, when they're theater — is our [Spec-Driven Development guide](/guides/workflow/spec-driven-development); the lighter-weight in-Claude-Code version of the same instinct is [plan mode plus plan-feature](/commands/plan/plan-feature).

---

_Source: https://agentscamp.com/tools/spec-kit — Tool on AgentsCamp._