Spec-driven Development / Testing (SDD + TDD)¶
SDD (Spec-Driven Development) and TDD (Test-Driven Development) are both stability layers for change: they make fast iteration safer. This page organizes related articles by category.
Start here
- Concept: Why Spec-driven Development Matters Now — Moving beyond vibe coding
- Practice: Enforcing Spec-driven Dev with AI Agents — Claude Code & Copilot complete setup
What to know first¶
- SDD: clarify contracts before implementation
- TDD: clarify behavior before implementation
- With AI-assisted coding, specs and tests are what keep speed from turning into risk
Article Map¶
Spec-driven Development (SDD)¶
| Article | Description |
|---|---|
| Why Spec-driven Dev Matters Now | Amazon Kiro and moving beyond vibe coding |
| Enforcing Spec-driven Dev with AI | Claude Code & GitHub Copilot complete setup |
| LLM Programming Guide | Practical LLM-assisted development methods |
Test Automation¶
| Article | Description |
|---|---|
| Claude Code + GitHub Actions Testing | AI-driven CI/CD pipeline construction |
| Continuous Testing Patterns | Field error resolution focused |
| LLM-assisted Test Automation | Test automation methods and practices |
| GitHub Actions Script API | Script API practical usage guide |
Quality & Culture¶
| Article | Description |
|---|---|
| Agile Quality Assurance | Essential difference from waterfall |
Learning Path¶
- Why it matters: Spec-driven Dev
- Set it up: Enforcing Spec-driven Dev
- Automate tests: Claude Code + GitHub Actions
Related Topics¶
- Methodology/Culture: Development Methodology Hub
- Practices (LLM): LLM Practices Hub
- Claude Code: Claude Code Article Guide — Test automation execution environment
Tags & Navigation¶
- Tag:
pillar-spec-testing