Verified:GitHub

test-driven-development

Enforce test-first development with RED-GREEN-REFACTOR sequencing across .NET, Node, Python, and Kotlin projects.

140|20|Updated Jun 20, 2026

Search Tags:#tdd #unit testing #test-driven development #software quality #red-green-refactor #regression testing #test-first

Ready to run

npx skills add https://github.com/zekiriabd/SDD-Pro --skill test-driven-development-zekiriabd

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents untested production code and reduces regressions by requiring a failing test before implementation begins.

Core Features & Use Cases

RED-GREEN-REFACTOR Enforcement: Guides development from a failing test to the minimal passing implementation and a safe refactor.
Regression Protection: Requires a failing regression test before fixing reported bugs.
Scope-Aware Guidance: Applies test-first rules to new functions, classes, endpoints, components, and production files across .NET, Node, Python, and Kotlin projects.

Quick Start

Use the test-driven-development skill to define and run a failing test before implementing the requested production behavior.

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 test-driven development when writing new functions and classes?▼

Test-driven development enforces a RED-GREEN-REFACTOR sequence, requiring a failing test before any production code. You write a test defining the desired behavior, confirm it fails correctly, implement minimal code to pass it, and then safely refactor.

Can I use test-first development for bug fixes and refactoring across .NET and Node projects?▼

Yes, test-first development applies to bug fixes, refactors, and new components across .NET, Node, Python, and Kotlin. For reported bugs, it requires writing a failing regression test before applying the actual code fix to prevent future regressions.

What is the RED-GREEN-REFACTOR cycle in unit testing?▼

The RED-GREEN-REFACTOR cycle is a unit testing sequence where RED means creating a failing test for new behavior, GREEN is writing minimal implementation code to make it pass, and REFACTOR is improving the code structure while keeping tests green.

How do I add regression testing coverage before fixing reported software bugs?▼

Regression testing for reported bugs requires writing a failing test that reproduces the specific defect before changing production code. Once the minimal fix is applied and the test passes, the regression coverage ensures the same bug cannot reoccur later.

Does test-first development require validating that a test fails correctly before writing implementation code?▼

Yes, test-first development requires correct failure validation. You must confirm the test fails for the exact expected reason before writing production code, ensuring accurate test coverage and preventing false positives during the minimal implementation phase.