test-driven-development

Enforce the RED-GREEN-REFACTOR cycle for test-driven development.

20|Updated Jan 7, 2026

Search Tags:#tdd #red-green-refactor #best-practices #unit-testing #quality-assurance #software-engineering #test-driven-development

Ready to run

npx skills add https://github.com/bostonaholic/rpikit --skill test-driven-development-bostonaholic

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rigorous TDD methodology enforcing RED-GREEN-REFACTOR discipline. Use during the implement phase to ensure changes are guided by tests; tests must be written before production code with no exceptions.

Core Features & Use Cases

Enforces a strict test-first cycle (RED: write a failing test, GREEN: implement just enough to pass, REFACTOR: improve quality while green).
Drives implementation by definition, preventing production code without verification, and supporting bug fixes and feature work.
Provides guidance for maintaining test discipline across refactoring and feature growth.

Quick Start

Write a failing test for the desired behavior, then implement the minimum code to make it pass, and finally refactor while keeping all tests green.

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-first discipline during feature implementation?▼

Test-first discipline is enforced through the RED-GREEN-REFACTOR cycle, requiring you to write a failing test before any production code, implement just enough to pass, then refactor while keeping tests green.

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

The RED-GREEN-REFACTOR cycle is a test-driven development practice where you write a failing test, implement the minimum code to turn it green, and then refactor to improve quality while maintaining green tests.

Can I use test-driven development for both bug fixes and new features?▼

Test-driven development applies to both bug fixes and feature implementation, guiding teams to write failing tests that verify the desired behavior before writing or modifying production code.

How do I start writing failing tests before production code?▼

Start by writing a failing test for the desired behavior, implement the minimum production code to pass that test, and finally refactor the code while ensuring all tests remain green.

Why does test-driven development require tests before production code?▼

Test-driven development requires tests before production code to drive implementation by definition, preventing unverified production code and ensuring all features and bug fixes are guided by tests with no exceptions.