tdd-strict

Name: tdd-strict
Availability: InStock
Author: freitasp1

Enforce Red-Green-Refactor cycles by blocking code generation without failing tests.

Updated Aug 27, 2026

Search Tags:#code quality #testing #tdd #development workflow #refactoring #red-green-refactor

Ready to run

npx skills add https://github.com/freitasp1/claude-code-skills --skill tdd-strict-freitasp1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-strict
Source: https://github.com/freitasp1/claude-code-skills/tree/main/skills/tdd-strict
Command: npx skills add https://github.com/freitasp1/claude-code-skills --skill tdd-strict-freitasp1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) process, ensuring that code is only generated after corresponding tests have been written and have failed, thereby preventing regressions and improving code quality.

Core Features & Use Cases

Red-Green-Refactor Enforcement: Guarantees adherence to the TDD cycle by blocking code generation until a failing test is present.
Invalid Rationalization Documentation: Lists and explains 13 common excuses for skipping TDD, reinforcing best practices.
Use Case: When developing a new critical feature, activate this Skill to ensure that every piece of logic is covered by a test before it's implemented, leading to more reliable and maintainable code.

Quick Start

Activate this skill to enforce the Red-Green-Refactor cycle for all new code development.

Frequently Asked Questions about tdd-strict

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

FAQPage Schema

How do I enforce strict test-driven development during new feature development?▼

To enforce strict test-driven development, you must mandate the Red-Green-Refactor cycle by blocking code generation until a prior failing test is present, ensuring test coverage and robust code. This prevents regressions during new feature development.

What are common rationalizations for skipping TDD and how do I avoid them?▼

Common rationalizations for skipping TDD include various excuses to bypass test-first workflows. Documenting and recognizing these 13 common rationalizations reinforces best practices and prevents developers from skipping tests during refactoring or bug fixes.

Can I use strict TDD for bug fixes and refactoring existing code?▼

Yes, strict TDD is applicable during bug fixes and refactoring. Activating this enforcement ensures every logic change is covered by a failing test before implementation, leading to reliable and maintainable code updates.

Does strict test-driven development prevent code generation without failing tests?▼

Strict test-driven development prevents code generation without prior failing tests. By guaranteeing adherence to the Red-Green-Refactor cycle, it blocks implementation until test coverage is established, thereby improving overall code quality.

When should I not use strict TDD enforcement in my development workflow?▼

Strict TDD enforcement should not be used when rapid prototyping requires unblocked code generation without prior failing tests. Enforcing the Red-Green-Refactor cycle during exploratory phases may hinder speed and disrupt the development workflow.