cc-tdd-cycle

Automate red/green/refactor TDD cycles with explicit phase sequencing.

Updated May 7, 2026
One-click install
npx skills add https://github.com/lgzarturo/codeconductor --skill cc-tdd-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-tdd-cycle
Source: https://github.com/lgzarturo/codeconductor/tree/main/.agents/skills/cc-tdd-cycle
Command: npx skills add https://github.com/lgzarturo/codeconductor --skill cc-tdd-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a strict Red-Green-Refactor TDD workflow to ensure tests drive design decisions and reduce defects.

Core Features & Use Cases

  • Enforces a RED phase to write a failing test before implementation
  • Guides the GREEN phase with minimal, verifiable changes to satisfy tests
  • Facilitates the REFACTOR phase to clean up while preserving test guarantees
  • Clarifies Tester and Implementer roles to define responsibilities

Quick Start

Begin a RED-GREEN-REFACTOR cycle by writing a failing test that targets the behavior, then implement the minimum code to pass and finally refactor while keeping tests green.

Frequently Asked Questions about cc-tdd-cycle

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

FAQPage Schema
How do I enforce a strict TDD red-green-refactor cycle in my software workflow?

The TDD cycle is enforced by applying explicit phase sequencing with distinct tester and implementer roles, automating the progression from a failing RED test to minimal GREEN code and final REFACTOR cleanup.

What is the red-green-refactor cycle and how does it reduce software defects?

The red-green-refactor cycle is a testing workflow where you write a failing test, implement the minimum code to pass it, then refactor safely. Driving design decisions through tests reduces defects and preserves test guarantees throughout development.

How do I start a TDD cycle for unit and integration testing?

Start a TDD cycle by writing a failing test targeting the specific behavior of your software component. Once the RED phase confirms the failure, implement the minimum verifiable changes to reach GREEN, then refactor while keeping tests green.

Do I need external dependencies or specific testing frameworks to run the TDD cycle?

No external dependencies are required beyond standard testing tooling. You only need your project's existing test runner to enforce the RED-GREEN-REFACTOR discipline across unit, integration, and refactor tasks within typical codebases.

When should I not use a strict TDD workflow for software engineering?

A strict TDD workflow may not suit exploratory coding or throwaway prototypes where design decisions are fluid. The discipline of writing failing tests first adds overhead that is best applied to components requiring high reliability and defect reduction.