GitHub Spec-Kit: Turn English Into Production-Ready Specs

The Problem With Starting From Code I've been watching a pattern repeat across teams adopting AI coding tools: someone opens a blank file, writes a vague comment like // build a user auth system, and asks Copilot to fill in the rest. The code that comes back often looks fine. It compiles. It might even pass a few tests. But three days later, you're untangling authentication logic that doesn't match your security requirements, a session model that contradicts your database schema, and edge cases nobody thought through. This is "vibe coding" at its worst — not the fun kind where you're exploring a prototype, but the kind where production-bound features get built on interpretations of half-formed ideas. The AI isn't to blame. It's filling in the gaps you left with plausible-sounding defaults. The real problem is that we skipped the spec. And context engineering tells us exactly why that matters: AI output quality is directly proportional to what the model sees before it generates a single