tdd-red

Enforces the RED phase of TDD by requiring a failing test before implementation code.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/shynlee04/idumb-v2 --skill tdd-red-shynlee04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-red
Source: https://github.com/shynlee04/idumb-v2/tree/main/.agent/skills%20copy/tdd-red
Command: npx skills add https://github.com/shynlee04/idumb-v2 --skill tdd-red-shynlee04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces the critical "RED" phase of the Test-Driven Development (TDD) cycle, ensuring that implementation code is only written after a failing test has been established, thereby preventing premature or incorrect coding.

Core Features & Use Cases

  • Mandatory Failing Test: Guarantees that a test is written first and that it fails, confirming it tests the correct behavior.
  • Behavioral Focus: Encourages writing tests that describe desired behavior rather than implementation details.
  • Use Case: Before adding a new user authentication feature, this Skill ensures a test is written that expects authentication to fail (because the code doesn't exist yet), before any authentication logic is implemented.

Quick Start

Use the tdd-red skill to write a failing test for the new user registration functionality.

Frequently Asked Questions about tdd-red

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

FAQPage Schema
How do I enforce the RED phase in TDD before writing implementation code?

To enforce the TDD RED phase, you must create a specific, minimal failing test that validates expected behavior before any implementation code is written. This prevents untested code and maintains robust coverage.

What is the purpose of writing a failing unit test first in test-driven development?

Writing a failing unit test first in test-driven development confirms the test correctly validates desired behavior before the code exists. This behavioral focus prevents premature coding and ensures robust test coverage.

How do I write a minimal failing test for a new user authentication feature?

To write a minimal failing test for a new user authentication feature, define a test that expects authentication to fail because the logic does not exist yet. This validates the expected behavior before implementation begins.

Does test-driven development require testing implementation details or expected behavior?

Test-driven development requires testing expected behavior rather than implementation details. By focusing on behavioral outcomes, the RED phase ensures tests validate specific, minimal requirements without coupling to internal code structure.

Why does my TDD workflow allow writing implementation code without a failing test?

A TDD workflow might allow untested implementation code if it lacks a guardrail requiring a failing test first. Enforcing the RED phase mandates a behavioral test failure before any new code is introduced.