Phase 1: Spec-Driven Development · 40 min · GitHub Spec Kit · Claude Code · Python

Spec-Kit and the SDD Toolchain

The tool doesn't make you spec-driven. Whether anything checks the spec against the code, continuously, does.

Real-world application: Being able to name which SDD maturity level your team actually operates at — not just 'we write specs' — shows you understand that the tool is secondary to whether anything enforces the spec-code relationship.

What you will learn

Name the three SDD maturity levels: spec-first, spec-anchored, spec-as-source
Map real tools (GitHub Spec Kit, Amazon Kiro, Tessl) to the maturity level they primarily target
Diagnose when a team's claimed 'spec-first' practice is hollow because nothing checks specs against code after the first draft
Assess a team's actual SDD maturity and recommend a concrete next step

Introduction

Spec-Kit and the SDD Toolchain

Objective

Classify a team's actual SDD practice into spec-first, spec-anchored, or spec-as-source based on concrete yes/no facts, and recommend a specific next step to reach the level above.

Unlock the full lesson

You've read the first 2 sections. The rest of this lesson covers The Problem, The Concept, Build, Check Yourself, Key Terms & Next — plus a hands-on lab, quiz, and project artifact.

Create a free account — the opening phases of 29 of 35 courses are free, no credit card.