Spec-Driven Infrastructure — GitHub Spec Kit at 84K Stars, Karpathy Declares Vibe Coding Over #
- Vibe Coding vs Spec-Driven Development in 2026 (InterCode, 2026-06) — The framing is now clearly defined: vibe coding is prompt-driven (chat → code → iterate by prompting); spec-driven development treats the spec as the source of truth and code as compiled output. GitHub Spec Kit — an open-source spec-driven workflow toolkit — has accumulated 84,000 GitHub stars, supports 14 AI agent platforms, and has shipped 130 releases. This is the first major open-source infrastructure specifically for spec-driven workflows across multiple coding agents; it signals the community is treating spec-driven development as a durable pattern rather than a vendor-specific feature (contrast with AWS Kiro’s integrated approach). Andrej Karpathy, who coined “vibe coding” in February 2025, stated in June 2026 that “this era is ending” and that we are entering the age of agentic engineering — orchestrating agents against detailed specifications with human oversight.
Cross-links #
- Applications of Vibe Coding The spec-driven vs. vibe-coding distinction maps onto the enterprise adoption pattern — “vibe coding” for prototypes, spec-driven for production systems at scale.
- Team & Org Use of Claude Spec-driven methodology (particularly the Martin Fowler “Encoding Team Standards” pattern) is the team-level application of what GitHub Spec Kit operationalises at the tooling level.
- Quality signal: Karpathy declaring “vibe coding’s era is ending” is a meaningful pivot signal — he coined the term; his public distancing marks a cultural transition point worth tracking.