Development
test-driven-development
Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.
KbWen · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add KbWen/agentic-os --skill test-driven-developmentAbout this skill
name: test-driven-development description: Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.
Test-Driven Development
Overview
TDD uses the Red → Green → Refactor micro-cycle. First, define expected behavior. Next, use a minimal implementation to pass the test. Finally, organize the code structure.
When to Use
- Adding or modifying core logic.
- Fixing bugs and needing regression protection.
- Requirements can be written as explicit input/output acceptance tests.
Workflow
- Red: Write a failing test describing the expected behavior.
- Green: Write the minimal code to make the test pass.
- Refactor: Clean up naming, structure, and duplication.
- Repeat the cycle until acceptance criteria are met.
Ironclad Rules
- Do NOT write massive amounts of features before writing tests.
- Focus on one small goal per cycle.
- All tests MUST pass after refactoring.