133.9k stars · MIT · v1.0.4 (2026-09-02) · Track this in Scout
GitHub's spec-driven development toolkit — intent, then specification, then plan, then the agent implements.
▶Repo detailsthe review · specs · pros & cons
What it is
GitHub's open-source toolkit for spec-driven development: a small set of commands and templates that walk you from an intent, through a written specification and a technical plan, to a task list an AI agent implements. It works with Claude Code and about thirty other agents.
What it is good for. With an agent doing the typing, the bottleneck is not typing speed, it is specification. A solo founder building a non-trivial product through an AI agent produces excellent code for whatever was described and quietly accumulates features that half-fit each other, because the description lived in a chat window and then scrolled away. Spec Kit puts the specification in a file in the repository, where it can be argued with, revised, and reused — and it is the natural home for exactly the decisions this radar keeps raising and deferring: BERTopic or turftopic, Postiz or Mixpost, what a map view must do on a phone. Written down once, those stop being re-litigated at the start of every session.
- Agent-agnostic and MIT — no lock-in to a particular tool or vendor, and it moves with you if your tooling changes.
- Forces the specification and the plan to be separate artefacts, which is precisely the discipline a non-programmer building through an agent most lacks.
- Extremely active:
specify-cli1.0.3 shipped to PyPI on 1 September 2026, the day before this edition.
- It is process, and process only pays back on work large enough to need it. Using it for a one-file change is pure overhead.
- Genuinely opinionated about workflow. If it does not match how you think, you will fight it, and the fix is to take the templates and drop the rest.
- Moving fast in a way that shows: the GitHub tag reads v0.9.4 (4 June 2026) while PyPI is on 1.0.3. Expect the commands to change under you between versions.
Written down once, those stop being re-litigated every time you open a session.
Installed alongside Claude Code with uv , writing spec and plan files into your own repositories.
