test-driven-development

Implement Test-Driven Development workflows using the Red-Green-Refactor cycle.

Updated Apr 19, 2026

Search Tags:#testing #tdd #debugging #refactoring #unit testing #software quality

Ready to run

npx skills add https://github.com/dmarins/sdd --skill test-driven-development-dmarins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/dmarins/sdd/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/dmarins/sdd --skill test-driven-development-dmarins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the lack of confidence in code changes by enforcing a rigorous Test-Driven Development (TDD) cycle, ensuring that every feature and bug fix is backed by verifiable proof.

Core Features & Use Cases

TDD Cycle Enforcement: Guides the user through the Red-Green-Refactor loop to ensure code quality and prevent regressions.
Bug Reproduction: Provides a structured "Prove-It" pattern to isolate and fix bugs using failing tests as the primary evidence.
Use Case: When tasked with implementing a new business logic module, use this skill to write the failing test case first, ensuring the implementation meets the exact requirements without over-engineering.

Quick Start

Use the test-driven-development skill to guide the implementation of the new user authentication module by writing a failing test first.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema

How do I implement new features using the Test-Driven Development workflow?▼

The Test-Driven Development workflow implements new features by enforcing the Red-Green-Refactor cycle, starting with a failing test case to ensure the implementation meets exact requirements without over-engineering.

How can I reproduce and fix bugs using unit testing?▼

Unit testing isolates and fixes bugs using a structured 'Prove-It' pattern, which creates failing tests as primary evidence to reproduce the bug and validate the corrected logic.

Does Test-Driven Development work for refactoring existing code across various programming languages?▼

Test-Driven Development supports refactoring across various programming languages by applying the Red-Green-Refactor cycle to validate logic and infrastructure boundaries, preventing regressions during code changes.

What is the best way to prevent code regressions when building software?▼

Preventing code regressions is achieved by enforcing a rigorous Test-Driven Development cycle, ensuring every feature and bug fix is backed by verifiable proof through project-specific testing frameworks.

When do I need to use the Red-Green-Refactor cycle for software quality?▼

The Red-Green-Refactor cycle is needed when implementing new business logic modules, fixing bugs, or refactoring, ensuring code correctness and providing confidence in code changes through verifiable tests.

Why does test-driven development require project-specific testing frameworks to validate logic?▼

Test-driven development requires project-specific testing frameworks to accurately validate logic and infrastructure boundaries, ensuring the tests correctly reflect the exact project requirements and environment.