test-driven-development

Enforce the Red-Green-Refactor cycle for all feature development and bug fixes.

Updated May 5, 2026

Search Tags:#testing #tdd #software engineering #quality assurance #refactoring #unit testing

Ready to run

npx skills add https://github.com/iani-kuli/harness_bro --skill test-driven-development-iani-kuli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/curated/test-driven-development
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill test-driven-development-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the common pitfalls of writing code without verification, such as untested edge cases, over-engineering, and the accumulation of technical debt.

Core Features & Use Cases

Red-Green-Refactor Cycle: Provides a structured workflow to ensure every line of production code is backed by a failing test.
Anti-Pattern Prevention: Includes rigorous guidelines to avoid common testing mistakes like mocking behavior instead of real logic.
Use Case: When implementing a new feature or fixing a bug, this skill guides you to write a failing test first, ensuring the requirement is clearly defined and the fix is verified before any production code is finalized.

Quick Start

Apply the test-driven-development skill to guide the implementation of the new user authentication module by enforcing the red-green-refactor cycle.

Frequently Asked Questions about test-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce a strict test-driven development workflow for feature development?▼

Test-driven development workflow enforces the Red-Green-Refactor cycle to ensure reliable code. It prohibits production code implementation without a preceding failing test, preventing untested edge cases and technical debt accumulation.

What is the Red-Green-Refactor cycle in unit testing?▼

The Red-Green-Refactor cycle is a structured unit testing workflow ensuring high code quality. You write a failing test to define requirements, implement code to pass it, and refactor to prevent technical debt accumulation.

How do I fix bugs using TDD without accumulating technical debt?▼

Fix bugs using TDD by writing a failing test first that clearly defines the bug. This verifies the fix before production code is finalized, directly addressing untested edge cases and preventing technical debt accumulation.

Does TDD prevent anti-patterns like mocking behavior instead of real logic?▼

Yes, TDD includes rigorous guidelines for anti-pattern prevention. It helps avoid common testing mistakes like mocking behavior instead of real logic, ensuring tests validate actual software requirements accurately.

When should I not use test-driven development for software engineering tasks?▼

You should not use test-driven development when rapid prototyping without verification is required. TDD strictly prohibits production code implementation without a preceding failing test, which slows down immediate exploratory coding.