tdd

Execute test-driven development workflows through red-green-refactor cycles.

112|10|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/mycelium-io/mycelium --skill tdd-mycelium-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/mycelium-io/mycelium/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/mycelium-io/mycelium --skill tdd-mycelium-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development (TDD) introduces a disciplined workflow that reduces debugging time by ensuring features start from tests.

Core Features & Use Cases

  • Structured workflow: Guides a red-green-refactor cycle to validate behavior before implementation.
  • Early failure detection: Encourages failing tests early for clearer requirements.
  • Incremental design: Supports building features in small, verifiable steps.

Quick Start

Propose a feature, write a minimal failing test, and run the test suite to see the red result.

Frequently Asked Questions about tdd

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

FAQPage Schema
What is test-driven development and how does the red-green-refactor cycle work?

Test-driven development (TDD) is a workflow that reduces debugging time by validating behavior before implementation. The red-green-refactor cycle enforces writing a failing test first, implementing minimal code to pass, and validating through the test suite with optional refactoring.

How do I start feature implementation with a TDD workflow?

To start feature implementation with TDD, propose a feature, write a minimal failing test, and run the test suite to see the red result. Then implement the minimal code required to pass the test and validate the full suite.

Does test-driven development help with early failure detection in software engineering?

Yes, test-driven development encourages failing tests early for clearer requirements. This structured workflow supports building features in small, verifiable steps to detect failures before full implementation.

Can I use this TDD workflow for incremental design in any software project?

This TDD workflow applies to feature development in software projects where tests guide implementation. It supports incremental design by building features in small, verifiable steps across red-green-refactor cycles.

What's the best way to enforce writing a failing test before implementation?

The best way to enforce writing a failing test first is to follow a structured test-driven development workflow. It coordinates the red-green-refactor cycle, ensuring you write a failing test, implement minimal code to pass, and validate through the full test suite.