Radberi-TDD

Enforce test-first development with failing tests before production code.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Shade666/huml-dotnet --skill radberi-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Radberi-TDD
Source: https://github.com/Shade666/huml-dotnet/tree/main/.claude/skills/Radberi-TDD
Command: npx skills add https://github.com/Shade666/huml-dotnet --skill radberi-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that code changes are driven by failing tests first, preventing production code from being written without a verification baseline and encouraging early detection of design flaws.

Core Features & Use Cases

  • Enforces the RED-GREEN-REFACTOR loop to drive design decisions through tests.
  • Applies to features, bug fixes, and refactors, providing a repeatable, disciplined workflow.
  • Improves long-term maintainability by documenting expected behavior via tests and guiding incremental improvements.

Quick Start

Write a failing test for the feature you want to implement, then write the minimal production code to pass that test.

Frequently Asked Questions about Radberi-TDD

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

FAQPage Schema
How do I enforce test-first development in my .NET workflow?

Test-first development is enforced by requiring a failing test before writing any production code, guiding you through red-green-refactor cycles to verify behavior using a .NET testing framework like xUnit.

What is the red-green-refactor cycle and when should I use it?

The red-green-refactor cycle is a test-driven development loop where you write a failing test, implement minimal code to pass it, then refactor. Use it for feature work, bug fixes, and refactors to ensure reliable code.

Can I use this TDD workflow for bug fixes and refactoring existing code?

Yes, this TDD workflow applies to bug fixes and refactoring by guiding you through red-green-refactor cycles, ensuring expected behavior is documented and verified before modifying production code.

Does this test-driven development approach work with standard .NET project structures and CI workflows?

Yes, this test-driven development approach assumes a .NET testing framework like xUnit and integrates with standard project structures and existing CI workflows to verify behavior continuously.

What's the best way to start writing code using a test-first methodology?

The best way to start test-first development is to write a failing test for the feature you want to implement, then write the minimal production code required to make that test pass.

Why does test-driven development prevent design flaws in production code?

Test-driven development prevents design flaws by establishing a verification baseline through failing tests before any production code is written, encouraging early detection of structural issues and improving long-term maintainability.