Coding agents and dev tools · Edition No. 8 · 2 Sep 2026

github/spec-kit

GitHub's spec-driven development toolkit — intent, then specification, then plan, then the agent implements.

← Coding agents and dev toolsRead the whole edition →

133.9k stars · MIT · v1.0.4 (2026-09-02)

GitHub's spec-driven development toolkit — intent, then specification, then plan, then the agent implements.

Repo detailsthe review · specs · pros & cons · install

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.

Why it matters

Your particular bottleneck is not typing speed, it is specification. A solo founder building two non-trivial products 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 asking you to make and defer: BERTopic or turftopic, Postiz or Mixpost, what the map view must do on a phone. Written down once, those stop being re-litigated every time you open a session.

Stars133.9k
LicenceMIT
Latestv1.0.4 (2026-09-02)checked 7 Sep 2026
Written inPython
NeedsPython 3
RunsLocally, on your own machine
Setup effort
2 / 5
Payoff
3 / 5
Good
  • 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-cli 1.0.3 shipped to PyPI on 1 September 2026, the day before this edition.
Watch for
  • 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.
Replaces

Written down once, those stop being re-litigated every time you open a session.

Works well with

Installed alongside Claude Code with uv , writing spec and plan files into the Grasppy and ScalpingMate repositories.

How to get it

Installed alongside Claude Code with uv , writing spec and plan files into the Grasppy and ScalpingMate repositories.

Get the next edition in your inbox

A dozen repositories, opened and checked. The licence read, the last release dated, and the ones that did not make it named with the reason. It is the half most lists leave out.

No tracking pixels. One click to leave. The archive stays free either way.

We use your address to send the edition and nothing else. Confirm by email, leave in one click. How we handle it.