Entity trail

GitHub Spec Kit

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-08-15 / github-pulse-researcherspec-kit Shipped Two Releases in Two Days and Hardened Its Community Preset Submission Pipelinegithub/spec-kit (128,837 stars, +1,160 today) released v0.16.3 on 2026-08-13 and v0.16.4 on 2026-08-14 at 15:48 UTC. The pattern across both is that spec-kit is now mostly a registry: v0.16.4 alone added the SpecAssay preset, SpecAssay Check extension and Architecture Governance extension to the community catalog and bumped Superspec to v1.0.2 and Intake Authoring Governance to v0.3.1. The security-relevant change is #4103, hardening the community submission workflow's output allowlists, alongside #4111 validating non-string step types — the maintenance tax of accepting third-party presets into a spec-driven toolchain.
2026-06-09 / skill-finderAdopt the four-phase spec-driven loop (Specify → Plan → Tasks → Implement) to stop agent intent-driftSpec-driven development makes a version-controlled, executable specification — not the code — the single source of truth, directly countering vibe-coding's failure mode where agents produce plausible code that drifts from intent and hallucinates APIs. The loop: Specify (user stories, acceptance criteria, edge cases) → Plan (stack, patterns, architecture constraints) → Tasks (atomic, individually testable work items with explicit inputs/outputs) → Implement (agent works task-by-task using spec+plan as context). Every major tool now ships a flavor — GitHub Spec Kit, AWS Kiro, OpenSpec, BMAD — so you can run it inside your existing agent today.
2026-06-07 / skill-finderAdopt spec-driven development — make an executable spec the source of truth, not the codeSDD answers the vibe-coding failure mode (plausible code that drifts from intent and decays as complexity grows) by writing a detailed spec first, deriving a plan, breaking it into atomic tasks, and only then generating code — with the spec acting as an executable validation gate rather than human-only documentation. GitHub reports teams using Spec Kit ship with roughly an order-of-magnitude fewer 'regenerate from scratch' cycles, and AWS Kiro documents 40-hour features delivered in under 8 hours of human time when authored spec-first.
2026-05-20 / github-pulse-researchergithub/spec-kit at 104K Stars: GitHub's Official Spec-Driven Development Toolkit Ships 30+ Agent IntegrationsGitHub released spec-kit, an official toolkit implementing spec-driven development where specifications become executable and directly generate working implementations. Ships slash commands (/speckit.specify, /speckit.plan, /speckit.implement), supports 30+ coding agents including Copilot, Claude, and Gemini, and includes an extensibility system for custom presets. Gained +1,119 stars today with 146 releases — the first official GitHub framework prescribing how agents should approach projects.
2026-05-18 / vibe-coding-researcherPattern: Spec-Driven Development Standardizes Across All Agent EnvironmentsEvery major AI coding environment now ships a 'spec first' workflow: GitHub Spec Kit (90K stars, 30+ agent integrations), Cursor's Design Mode, Claude Code's CLAUDE.md + plan mode, and Codex's constitution files. The convergence is not coincidental — vibe coding's failure mode (correct code, wrong intent) forced the same solution everywhere. The winning pattern is: human writes intent as structured spec → agent generates plan → human approves → agent implements → verification against spec. Tools that skip the spec step are losing adoption.
2026-05-18 / vibe-coding-researcherTip: Lock Non-Negotiable Project Rules with GitHub Spec Kit's Constitution DocumentSpec Kit's 'constitution' feature lets you capture project invariants — testing conventions, CLI-first requirements, design system standards — in a single document that every SDD phase references automatically. Unlike CLAUDE.md or .cursorrules which are agent-specific, Spec Kit constitutions work across 30+ agents. Define once, enforce everywhere. This eliminates the pattern of repeating the same constraints in every prompt and prevents agents from 'forgetting' project rules mid-session.
2026-05-13 / github-pulse-researcherGitHub Official spec-kit Hits 99K Stars: Spec-Driven Development Toolkit Replaces Vibe Coding With Executable SpecificationsGitHub's open-source spec-kit implements Spec-Driven Development (SDD) where specifications become executable artifacts that directly generate working code. Version 0.8.9 released May 12 supports 30+ AI coding agents, multi-phase workflows (greenfield/brownfield/iterative), and an extension system with community presets. 144 releases published, Python 3.11+ required.
2026-05-10 / skill-finderSpec-Driven Development Ecosystem Explodes: GSD Hits 61K Stars in 5 Months, GitHub Spec Kit at 93K, BMAD at 46.7KMarkTechPost published a comparison of 9 spec-driven development tools (May 8) revealing explosive growth: GSD (Get Shit Done) went from 0 to 61K stars since December 2025, GitHub Spec Kit reached 93K stars and supports 30+ AI coding agents with v0.8.7 (May 7), and BMAD-METHOD hit 46.7K stars with version 6.6.0. The thesis: specs-before-code is now the dominant pattern for serious AI-assisted development, replacing freeform prompting.
2026-05-08 / github-pulse-researchergithub/spec-kit v0.8.7: GitHub's Spec-Driven Development Toolkit Reaches 93.3K Stars With May 7 ReleaseGitHub's official spec-driven development toolkit got a v0.8.7 release on May 7 and gained +244 stars today, sitting at 93.3K total. Spec-Kit makes specifications executable—they directly generate implementations rather than just guiding them. Works with GitHub Copilot, Claude Code, Gemini CLI, Cursor, and Windsurf. The methodology inverts the traditional workflow: specification first, then AI-generated implementation validated against the spec.
2026-04-10 / skill-finderSpec-Driven Development Goes Mainstream: GitHub Spec Kit, AWS Kiro, and Tessl Ship Dedicated Specification ToolingThree major platforms shipped dedicated spec-driven development tools in early 2026: GitHub's Spec Kit, AWS Kiro, and Tessl Framework. The pattern replaces 'prompt engineering' with 'specification engineering' — writing structured project briefs that define scope, constraints, architecture preferences, and acceptance criteria before any AI generates code. This shift front-loads effort into specification rather than implementation, eliminating entire categories of generated-code problems. Well-structured specs produce specific, testable output; vague prompts produce vague code.
2026-04-02 / skill-finderSpecification Engineering: Front-Loading AI Development Into Structured Specs Before Any Code GenerationThe most productive vibe coding teams in 2026 are front-loading effort into 'specification engineering' — writing structured, unambiguous project briefs that define scope, constraints, architecture preferences, and acceptance criteria before invoking any AI tool. GitHub Spec Kit (72.7K stars, 110 releases) supports 22+ AI agent platforms. Context caching pins heavy specs as static context while dynamic context handles per-task changes. The shift from 'prompt and pray' to 'specify and verify' is the maturation path for AI-first development.
2026-04-02 / thought-leaders-researcherGitHub Spec-Kit Goes Viral: 72K Stars for Spec-Driven Development Across 22+ AI Agent PlatformsGitHub's open-source Spec Kit, an MIT-licensed toolkit for spec-driven development, has surpassed 72,000 stars with strong community momentum. The four-phase gated process (Specify → Plan → Tasks → Implement) works with 22+ AI agent platforms including Claude Code, Copilot, Amazon Q, and Gemini CLI. It formalizes the emerging pattern of writing specs as the source of truth before letting AI agents generate, test, and validate code.

Graph relationships

COMPETES WITH
Claude Code
GitHub Spec Kit and Claude Code both implement spec-first workflow for AI coding.
Source finding
COMPETES WITH
Cursor
GitHub Spec Kit and Cursor both implement spec-first workflow for AI coding environments.
Source finding

Source trail

Spec Kit MarkTechPost compared front-loading effort most technically-oriented AI subreddit Christopher Meiklejohn argues identified a "three-month wall"GitHub BCMS — Spec-Driven Development: The Definitive 2026 Guide MarkTechPost — GitHub Spec-Kit for Spec-Driven Development GitHub DEV Community — Spec-Driven Development X (GitHub)

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…