test-driven-development

Enforce a failing test before implementation using the Red-Green-Refactor cycle.

Updated Mar 22, 2026

Search Tags:#workflow #testing #tdd #refactoring #red-green-refactor #unit-testing #software-quality

Ready to run

npx skills add https://github.com/AndrewChang-cpu/vibe-coding-configuration --skill test-driven-development-andrewchang-cpu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/AndrewChang-cpu/vibe-coding-configuration/tree/main/general-plugin/skills/test-driven-development
Command: npx skills add https://github.com/AndrewChang-cpu/vibe-coding-configuration --skill test-driven-development-andrewchang-cpu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams adopt test-driven development by guiding coders to write a failing test before implementation, reducing defects and clarifying requirements early.

Core Features & Use Cases

Enforces the Red-Green-Refactor cycle to structure feature work, bug fixes, and refactoring.
Provides clear rules, examples, and expectations to prevent skipping tests and to encourage minimal, verifiable code.
Applies across projects and languages with a repeatable workflow that improves code quality and maintainability.

Quick Start

Begin by writing a failing test for the desired behavior, then implement the minimal code to pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema

What is test-driven development and how does the red-green-refactor cycle work?▼

Test-driven development (TDD) is a workflow where you write a failing test before implementation. The red-green-refactor cycle means writing a failing test, implementing minimal code to pass it, then refactoring while maintaining passing tests.

How do I start practicing test-driven development for a new feature or bug fix?▼

To start test-driven development, write a failing test defining the desired behavior, implement the minimal code required to pass that test, and then refactor the code for quality while keeping the test green.

Can I apply test-driven development across different programming languages and projects?▼

Yes, test-driven development applies across projects and languages. It provides a repeatable workflow using the red-green-refactor cycle to improve code quality and maintainability regardless of the specific tech stack.

What is the best way to enforce automated testing discipline during refactoring?▼

The best way to enforce automated discipline during refactoring is using a structured test-driven development workflow that requires a failing test before any implementation, ensuring minimal verifiable code and preventing skipped tests.

When should I not use a strict test-first development approach?▼

You should not use strict test-first development when exploring rapid prototypes where requirements are highly volatile, because the overhead of writing failing tests before minimal implementation can slow down immediate exploratory coding.