tdd

Enforce test-driven development workflows with a red-green-refactor cycle.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Eotel/claude-marketplace --skill tdd-eotel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Eotel/claude-marketplace/tree/main/plugins/base/skills/tdd
Command: npx skills add https://github.com/Eotel/claude-marketplace --skill tdd-eotel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a disciplined test-driven development workflow by guiding teams to write tests before implementation, reducing defects and improving code reliability.

Core Features & Use Cases

  • Enforces the red-green-refactor cycle with explicit guidance.
  • Promotes 80%+ test coverage targets and best-practice coding standards.
  • Supports feature development, refactoring, and bug fixes with structured workflows.

Quick Start

Run the tdd-guide agent to scaffold interfaces, generate failing tests first, and implement minimal code to pass.

Frequently Asked Questions about tdd

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

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

To enforce a test-driven development workflow, you need a structured red-green-refactor cycle that guides you to write failing tests before implementing minimal code. This approach ensures defects are reduced and code reliability improves.

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

The red-green-refactor cycle is a test-driven development practice where you write a failing test, implement minimal code to pass it, then refactor. This structured workflow improves code quality by ensuring continuous test coverage and best-practice standards.

Can I use test-driven development for bug fixes and refactoring?

Yes, test-driven development workflows apply directly to bug fixes and refactoring. They guide you to scaffold interfaces and generate failing tests first, ensuring the fix or refactored code meets the required threshold for test coverage.

What is the best way to maintain high test coverage during software engineering?

The best way to maintain high test coverage is to enforce a strict test-driven development workflow with an 80%+ coverage target. Writing tests first during feature development and refactoring ensures consistent quality assurance and reliable code.

Does strict test-driven development slow down feature development?

Strict test-driven development requires writing failing tests before implementation, which adds initial structure to feature development. However, this guided workflow ultimately reduces defects and improves overall code reliability throughout the software engineering process.