tdd

Plan and execute red-green-refactor tests before coding to prevent regressions.

3|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill tdd-malinskibeniamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/malinskibeniamin/skills/tree/main/tdd
Command: npx skills add https://github.com/malinskibeniamin/skills --skill tdd-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development formalizes planning and verification, guiding code changes with explicit tests to prevent regressions.

Core Features & Use Cases

  • Structured workflow: PLAN -> RED -> GREEN -> REFACTOR with clear entry points
  • Tracer bullets, planning phase, and integrity checks to align implementation with requirements
  • Async leak detection and deep modular design to improve maintainability and resilience

Quick Start

Begin with a tracer bullet, write a failing test, implement just enough production code to pass, then refactor while keeping all tests green.

Frequently Asked Questions about tdd

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

FAQPage Schema
How does the red-green-refactor workflow guide development and prevent regressions?

The red-green-refactor workflow plans and executes tests before coding, starting with a failing test, writing just enough production code to pass, then refactoring while keeping all tests green to prevent regressions.

What is test-driven development with tracer bullets and how do I start?

Test-driven development with tracer bullets begins with a planning phase and integrity checks, writing a failing test, implementing minimal code to pass, then refactoring to align implementation with requirements.

How do I use test-driven development for async leak detection and deep module design?

Test-driven development for async leak detection and deep module design applies the red-green-refactor workflow across software modules, ensuring strong validation through coverage checks and clear failure handling in diverse scenarios.

What's the best way to structure a TDD workflow with planning and monitoring phases?

The best way to structure a TDD workflow is following a PLAN -> RED -> GREEN -> REFACTOR sequence with clear entry points, integrating coverage checks and monitor integration to ensure strong validation and prevent regressions.

When should I use test-driven development instead of writing tests after coding?

Use test-driven development when you need to formalize planning and verification, guiding code changes with explicit tests to prevent regressions and align implementation with requirements through structured integrity checks.

Does test-driven development work for complex software modules with async operations?

Test-driven development works for complex software modules by applying async leak detection, deep modular design, and coverage checks across diverse scenarios, ensuring maintainability and resilience through the red-green-refactor workflow.