drill-tdd

Enforces Red-Green-Refactor drill with mandatory failing tests before production code.

71|9|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/kucherenko/gangsta --skill drill-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drill-tdd
Source: https://github.com/kucherenko/gangsta/tree/main/skills/drill-tdd
Command: npx skills add https://github.com/kucherenko/gangsta --skill drill-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Drill enforces a strict test-first workflow for feature work, requiring a failing test before any production code.

Core Features & Use Cases

  • Enforces the Red-Green-Refactor drill with mandatory failing tests before production code.
  • Guides developers through a deterministic test cycle (Red → Green → Refactor) with explicit verification gates.
  • Provides practical guidance for applying the drill to bug fixes and feature work, including examples and best practices.

Quick Start

Write a failing test for the new behavior, then implement the minimal code to pass it and refactor for clarity.

Frequently Asked Questions about drill-tdd

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

FAQPage Schema
How do I enforce strict test-first discipline for feature work and bug fixes?

Test-first discipline is enforced by applying a deterministic Red-Green-Refactor cycle that prevents writing any production code until a failing test exists for the new behavior. This drill applies across languages and project types.

What is the Red-Green-Refactor cycle in test-driven development?

The Red-Green-Refactor cycle is a test-driven development workflow where you write a failing test, implement the minimal production code to pass it, and then refactor for clarity. Explicit verification gates ensure each phase is complete before progressing.

How do I write a failing test before writing production code?

Write a failing test for the new behavior, then implement the minimal code to satisfy it and refactor for clarity. The drill requires explicit verification gates during the Red phase to confirm the test actually fails before production code is introduced.

Can I apply test-driven development to refactoring existing code?

Yes, test-driven development applies to refactoring across languages and projects. You guide the process through a deterministic Red-Green-Refactor cycle, ensuring minimal production code changes satisfy the tests and improve clarity.

Do I need a specific testing framework to follow this test-driven development drill?

No specific testing framework is required. The drill applies to feature work, bug fixes, and refactors across languages and projects, relying on the deterministic test cycle rather than specific dependencies or components.

Why should I use minimal production code to satisfy tests?

Minimal production code prevents over-engineering and keeps the test-driven development cycle focused. By writing only what is necessary to pass the failing test, you maintain strict verification gates and refactor safely for clarity.