tdd

Enforce failing tests before production code across RED, GREEN, and REFACTOR phases.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/lpjhelder/kronon-forge --skill tdd-lpjhelder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/tdd
Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill tdd-lpjhelder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often write production code before tests, leading to low test coverage and fragile implementations. This skill enforces a strict test‑first workflow to improve code quality.

Core Features & Use Cases

  • RED phase guidance: Prompts you to write a failing test before any implementation.
  • GREEN phase assistance: Helps create minimal code that passes the test.
  • REFACTOR phase checks: Ensures code is cleaned up while keeping all tests green.
  • Enforcement rules: Automatically stops and warns when the TDD process is violated.
  • Use case: Ideal for teams adopting TDD or individuals seeking disciplined development practices.

Quick Start

Ask the tdd skill to start a new TDD cycle for the feature "user login validation".

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce test-driven development to prevent writing production code before tests?

To enforce test-driven development, apply a strict test-first workflow that stops and warns when the process is violated. This requires writing a failing test before any implementation, validating single-test per feature adherence.

What is the red green refactor cycle and how does it guide code quality?

The red green refactor cycle is a test-driven workflow guiding you to write a failing test first, create minimal code to pass it, and then clean up the implementation. This process ensures continuous test passing while improving code quality.

How do I start a TDD cycle for a specific software feature?

To start a TDD cycle for a specific feature, prompt the cycle initiation with your feature description. The workflow then enforces the RED phase by requiring a failing test before any production code is written.

Can I use test-driven development enforcement for team software engineering workflows?

Yes, test-driven development enforcement is ideal for teams adopting TDD workflows or individuals seeking disciplined development practices. It ensures low test coverage and fragile implementations are prevented through strict phase enforcement.

Why does test-driven development require a failing test before implementation?

Test-driven development requires a failing test before implementation to validate that the test actually checks the new feature. This failing-first validation ensures production code is minimal and specifically targeted to pass the test.

What are the limitations of strict test-first enforcement during refactoring?

A limitation of strict test-first enforcement is that it requires continuous test passing after refactoring. If code is cleaned up without keeping all tests green, the enforcement rules will automatically stop the process and warn the developer.