spec-driven-development 29
- Three Months of Spec-Driven Development: A Retrospective
- Generating Documentation from Specs Instead of Code Comments
- Spec-Driven Database Migrations
- Spec-Driven API Design Before Writing a Single Endpoint
- Spec-Driven Infrastructure-as-Code
- From Vibe Coding to Spec-Driven Development: A Migration Playbook
- Spec Failures: Three Case Studies and What Went Wrong
- Pair Programming with an Agent Under a Spec-Driven Workflow
- Spec-Driven Development vs Test-Driven Development
- GitHub Spec-Kit vs Kiro: Two Approaches to Spec-Driven Development Compared
- Walking Through Kiro's Requirements Notation
- Kiro IDE: Specs, Steering, and Hooks for Production-Grade Agentic Coding
- Keeping Specs Consistent Across a Multi-Repo Codebase
- Spec-Driven Refactors of Code Nobody Wants to Touch
- Handling Genuine Ambiguity in a Spec
- Code Review for Spec-Driven Changes: What to Look For
- Kiro Steering Files: A Deep Dive
- GitHub Spec-Kit: A Practical Guide to Spec-Driven Development with Coding Agents
- A Starter Library of Spec Templates
- Measuring SDD Adoption Across a Team
- Onboarding New Engineers with Spec-Driven Workflows
- Version-Controlling Specs Alongside Code
- Agent-Authored Specs vs Human-Authored: Who Should Write the First Draft?
- Writing Specs for a Legacy Migration, Not Just Greenfield Code
- Vibe Coding vs. Spec-Driven Development: Why Agentic Coding Agents Need Specs
- Spec-Driven Testing: Deriving Test Cases from the Spec Itself
- Detecting Spec Drift Before It Becomes Tech Debt
- A Spec Review Checklist for Agentic Coding Sessions
- Writing a Constitution Doc an Agent Will Actually Follow