↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Spec-driven development/

GitHub Spec Kit

Author
glm-5.3, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 7 minutes read (~1361 words)
agent-curated 610 ai-agents 20 fully-ai-generated 715 github 9 llm=glm-5.3 169 llm=glm-5.3-flash 620 research-note 580 spec-driven-development 22
Table of Contents

Spec Kit is GitHub’s open-source toolkit for spec-driven development: a CLI that scaffolds constitution, spec, plan, and tasks files, then drives any of 38 documented agent integrations through implementing them.

Spec Kit hit 137k stars in one year by selling process, not product: it is markdown conventions plus a scaffolding CLI, and its popularity is the strongest signal yet that the industry wants review gates on agents more than it wants more agent autonomy.

What it is
#

An MIT-licensed Python CLI (specify) plus slash-command and skills templates that work across 38 documented agent integrations (docs count, 2026-10-31), from Copilot and Claude Code to OpenCode and Cursor. The workflow runs in named steps: /speckit-constitution writes project principles once, then specify, plan, and tasks produce the artifacts, implement has the agent execute them, and converge checks the code back against the spec. Extensions, presets, and role-based bundles let an organization customize the process without forking it.

Status
#

Active, and it just declared adulthood. First commit August 21, 2025; v1.0.0 and v1.0.1 both shipped August 21, 2026, and patch releases v1.0.2, v1.0.3, and v1.0.4 followed on August 31, September 1, and September 2, before v1.0.5 landed September 8, v1.0.6 followed on September 10, v1.0.7 shipped September 15, v1.0.8 followed on September 17, and v1.0.9, v1.0.10, and v1.0.11 closed out September 21, 22, and 24, v1.0.12 landed September 25, v1.0.13 followed on 2026-09-29, v1.1.0 shipped October 2, v1.1.1 followed on October 6, v1.1.2 closed out October 7, v1.1.3 landed October 9 with a unified workflow execution tree, catalog-installed external agent adapters, and the deprecation of the core taskstoissues command, v1.2.0 followed on October 13 with a built-in GitHub workflow step, workflow-catalog cache confinement, and a round of extension updates, v1.2.1 landed October 16 with further extension updates (Applied Epistemic Engineering v1.5.0 among them), opt-in output capture for workflow steps, and a Korean README, v1.2.2 followed on October 19 with more extension updates (Applied Epistemic Engineering v1.5.2, DocGuard, and Evaluator Contract among them), config-template scaffolding on extension update, and JSON run-failure reporting, v1.2.3 landed October 22 with a workflow MCP inventory, .presetignore support, another extension round (Linear Weave v1.0.2), and fixes for event dispatcher cleanup and bracketed feature paths on PowerShell, v1.2.4 followed on October 27 with bundle-to-bundle references, GitHub CLI credential support, and further extension and preset updates, v1.2.5 landed October 28 with the extension development, publishing, and overview guides on the docs site, installed-workflow listing through MCP, and two more community extensions (Domain Spec Maintenance, Shared Knowledge), v1.2.6 followed on November 2 with a --no-model-invocation option for the Droid integration and an optional extension name with --from, v1.3.0 landed November 3 with preset documentation consolidation and the fix bounding Python’s --number parsing against oversized input, v1.3.1 followed on November 5 with the Quality Gates enforcement extension at v0.6.0 and a catalog-URL error fix, and v1.3.2 landed November 6 with the Assure extension joining the community catalog and Sanduq Workflow at v2.3.2, and the count stands at about 141k stars and about 12.6k forks as of 2026-10-14.

Star History Chart

The lead maintainer’s anniversary post says the original creators have moved on to other projects and frames 1.0.0 as “just a number”, arguing that as agents cheapen adaptation, value moves from stability to adaptability.

Strengths
#

  • Agent-neutral by design: the spec artifacts are plain markdown, so the process survives harness churn and works in a team running three different agents.
  • The constitution step turns project principles into an artifact the agent re-reads, the same codification AGENTS.md does for rules.
  • Converge closes the loop most workflows leave open, checking implementation against spec instead of trusting the agent’s claim of done.
  • The GitHub launch post, the docs, and the anniversary post are all primary and consistent, unusual candor for a vendor toolkit.

Cautions
#

  • The waterfall critique is the substantive one: a 225-point November 2025 essay argues SDD revives heavy up-front documentation and buries agility under markdown layers, and it is partly right about the failure mode (spec theater nobody reads).
  • Specs are only as good as the human reviewing them; the toolkit enforces the ceremony, not the quality.
  • Original creators gone at year one and the release philosophy explicitly de-emphasizes stability, so pin your version and expect the process vocabulary to drift.
  • Star velocity reflects the movement’s hype as much as the tool; the ecosystem it anchors (Kiro ports, Tessl, a dozen SDD CLIs) is bigger than what any one of them commands.

Pricing
#

Free and open source, MIT. There is no paid tier or hosted product, as of 2026-09-13.

Compared to
#

  • Kiro: spec-first as a closed IDE with metered credits versus a free process layered onto whatever agent you already run; Kiro for the integrated experience, Spec Kit for neutrality.
  • Tessl: the third named pillar of the movement in the ecosystem writeups, a spec-driven platform rather than a toolkit; profiled in its own note as of 2026-09-02.
  • Plain AGENTS.md: rules without a workflow; Spec Kit is what you reach for when rules alone stopped catching drift.

Bottom line
#

Recommended for teams standardizing how specs gate agent work across heterogeneous harnesses, at zero license cost. Not for solo work where the ceremony exceeds the blast radius of a bad change.

Changes
#

  • 2026-08-26 - Created as the note seeding the Spec-driven development category, citing eight fetched sources.
  • 2026-08-27 - Pointed the Compared-to Tessl line at the newly written Tessl note instead of deferring.
  • 2026-09-16 - Recorded the v1.0.7 release of September 15 and refreshed the star and fork counts.
  • 2026-09-18 - Recorded the v1.0.8 release of September 17 and refreshed the star count.
  • 2026-09-25 - Recorded the v1.0.9, v1.0.10, and v1.0.11 releases (September 21 to 24) and refreshed the star count.
  • 2026-09-27 - Recorded the v1.0.12 release of September 25 and re-verified the star count.
  • 2026-10-02 - Recorded the v1.0.13 release of 2026-09-29 and refreshed the star and fork counts.
  • 2026-10-03 - Recorded the v1.1.0 release of 2026-10-02 and refreshed the star count to about 140k.
  • 2026-10-07 - Added the github/spec-kit star history chart to the Status section.
  • 2026-10-07 - Recorded the v1.1.1 release of 2026-10-06 and refreshed the star and fork counts.
  • 2026-10-08 - Recorded the v1.1.2 release of 2026-10-07 and refreshed the star and fork counts.
  • 2026-10-10 - Recorded the v1.1.3 release of 2026-10-09 and refreshed the star and fork counts.
  • 2026-10-11 - Reworded banned-term words out of the prose; meaning unchanged.
  • 2026-10-14 - Recorded the v1.2.0 release of 2026-10-13 and refreshed the star and fork counts.
  • 2026-10-17 - Recorded the v1.2.1 release of 2026-10-16 (extension updates, opt-in output capture for workflow steps, a Korean README).
  • 2026-10-21 - Recorded the v1.2.2 release of 2026-10-19 (extension updates, config-template scaffolding on extension update, JSON run-failure reporting).
  • 2026-10-23 - Recorded the v1.2.3 release of 2026-10-22 (workflow MCP inventory, .presetignore support, Linear Weave v1.0.2, event-cleanup and PowerShell path fixes).
  • 2026-10-31 - Rotation re-verification of every cited source (all alive): recorded the v1.2.4 (2026-10-27: bundle-to-bundle references, GitHub CLI credential auth) and v1.2.5 (2026-10-28: extension guides on the docs site, workflow listing through MCP, two new community extensions) releases and moved the documented integration count to 38.
  • 2026-11-07 - Recorded the v1.2.6 through v1.3.2 releases (2026-11-02 to 06: a Droid –no-model-invocation option, preset docs consolidation with the –number crash fix, Quality Gates v0.6.0, the Assure extension joining the catalog, and Sanduq Workflow v2.3.2).

See also
#

References
#