TDD Enforcement

Guide software tasks through the RED-GREEN-REFACTOR cycle with a self-checklist.

3|Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Sheldon-92/TAD --skill tdd-enforcement-sheldon-92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: TDD Enforcement
Source: https://github.com/Sheldon-92/TAD/tree/main/.tad/skills/tdd-enforcement
Command: npx skills add https://github.com/Sheldon-92/TAD --skill tdd-enforcement-sheldon-92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide Blake through RED-GREEN-REFACTOR cycle for each implementation unit. Opt-in via config.yaml — disabled by default.

Core Features & Use Cases

  • Guided RED-GREEN-REFACTOR workflows for each task/AC
  • Per-task application with a structured self-checklist to ensure tests exist and are run
  • Opt-in via configuration, enabling controlled adoption

Quick Start

Enable the TDD Enforcement feature in your project configuration and start applying the RED-GREEN-REFACTOR cycle to each implementation task.

Frequently Asked Questions about TDD Enforcement

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

FAQPage Schema
How do I enforce test-driven development cycles in my software workflow?

You can enforce test-driven development cycles by applying a structured RED-GREEN-REFACTOR sequence to each new feature, API change, or complex logic task during implementation.

What is the best way to guide developers through the red-green-refactor sequence?

The best way to guide developers through red-green-refactor is using a per-task self-checklist that verifies tests exist, run successfully, and pass before moving to the next implementation unit.

How do I opt-in to TDD discipline enforcement for my project?

You opt-in to TDD discipline enforcement by configuring the feature in your project's config.yaml file, as the workflow remains disabled by default until explicitly enabled.

Does TDD workflow enforcement apply to existing code or only new features?

TDD workflow enforcement primarily applies to new features, API changes, and complex logic, guiding each specific implementation task through a structured testing sequence.

Why does my test-driven development workflow lack discipline across implementation tasks?

Your test-driven development workflow lacks discipline because it lacks a deterministic cycle that requires tests to exist and pass for each unit before proceeding to the next task.

Can I control the adoption rate of TDD enforcement across different projects?

You can control the adoption rate of TDD enforcement across different projects by managing the opt-in configuration file, allowing for controlled and gradual implementation.