tdd-workflow

Enforce the Test-Driven Development workflow through the Red-Green-Refactor cycle.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/riddopic/cc-tools --skill tdd-workflow-riddopic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/riddopic/cc-tools/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/riddopic/cc-tools --skill tdd-workflow-riddopic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces the Test-Driven Development (TDD) methodology, ensuring that all new code is written in response to a failing test, thereby improving code quality and preventing regressions.

Core Features & Use Cases

  • Enforces TDD: Mandates the Red-Green-Refactor cycle for all development.
  • Bug Prevention: Ensures bugs are fixed with a corresponding failing test first.
  • Use Case: When implementing a new user authentication feature, you must first write a test that fails because the feature doesn't exist, then write the minimal code to pass, and finally refactor.

Quick Start

Follow the TDD cycle to implement the next piece of functionality.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce a test-driven development workflow for new features?

To enforce a test-driven development workflow, you must follow the Red-Green-Refactor cycle, writing a failing test before any production code. This ensures code quality and prevents regressions by mandating strict testing protocols for all new features.

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

The Red-Green-Refactor cycle in test-driven development is a strict workflow where you first write a failing test, then write minimal code to pass it, and finally refactor. This process guides development and ensures robust code quality.

Can I implement production code without writing a failing test first?

No, you cannot implement production code without writing a failing test first. The workflow mandates that all development requires adherence to strict testing protocols, ensuring every piece of production code is written only in response to a failing test.

Does the TDD workflow require specific testing frameworks or dependencies?

The TDD workflow itself does not require specific testing frameworks or dependencies. It enforces the test-driven development methodology and bug fixing processes, guiding users through the cycle regardless of the underlying platform.

What is the best way to fix bugs using test-driven development?

The best way to fix bugs using test-driven development is to mandate that all bug fixes start with a corresponding failing test. This ensures the bug is captured before writing code, preventing regressions and maintaining robust code quality.