Test-Driven Development
SkillDev toolsDrive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.
Then ask your AI: use the Test-Driven Development skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.
What this skill tells your AI
The instructions your AI receives, as published by kbwen/agentic-os in .agents/skills/test-driven-development/SKILL.md and read by Ahel’s review.
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.
Signals
- GitHub stars
- 207
- Forks
- 44
- Last commit
- Oct 2026
Ahel recommends instead
Advanced
- Item type
- skill
- Key
test-driven-development-2- Source
- github.com/kbwen/agentic-os