tdd-workflow

Guide software engineers through the RED-GREEN-REFACTOR cycle and TDD principles.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/DaytimeBlues/ADHD-CADDI --skill tdd-workflow-daytimeblues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/DaytimeBlues/ADHD-CADDI/tree/main/.agent/skills/tdd-workflow
Command: npx skills add https://github.com/DaytimeBlues/ADHD-CADDI --skill tdd-workflow-daytimeblues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill codifies the principles of Test-Driven Development (TDD), guiding users through the RED-GREEN-REFACTOR cycle to improve code quality and reduce bugs.

Core Features & Use Cases

  • TDD Cycle Explanation: Details the RED (write failing test), GREEN (write minimal code to pass), and REFACTOR (improve code quality) phases.
  • Core Principles: Outlines the Three Laws of TDD and the AAA (Arrange, Act, Assert) pattern.
  • Use Case: A developer new to TDD can use this Skill to understand and apply the methodology to their daily coding tasks, ensuring tests are written before implementation.

Quick Start

Explain the RED phase of the TDD cycle.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
What is the RED-GREEN-REFACTOR cycle in Test-Driven Development?

The RED-GREEN-REFACTOR cycle in Test-Driven Development consists of writing a failing test (RED), writing minimal code to pass the test (GREEN), and improving code quality (REFACTOR).

How do I apply the AAA pattern when writing tests?

To apply the AAA pattern, structure your tests into Arrange, Act, and Assert sections. This pattern is a core principle of TDD that organizes test setup, execution, and verification for reliable code validation.

What are the Three Laws of TDD?

The Three Laws of TDD are core principles that enforce writing tests before implementation, ensuring no production code is written without a failing test and driving development through structured test cycles.

When should I use Test-Driven Development to improve code quality?

Use Test-Driven Development when you need to improve code quality and reduce bugs through a structured testing approach. It is applicable for software engineers seeking reliable code by writing tests before implementation.

Can I use Test-Driven Development for refactoring existing code?

Yes, Test-Driven Development supports refactoring existing code. The REFACTOR phase of the TDD cycle specifically focuses on improving code quality after tests pass, ensuring changes do not break existing functionality.