bee:test-driven-development

Enforce a RED-GREEN-REFACTOR cycle with mandatory failing tests.

2|1|Updated Mar 3, 2026

Search Tags:#code quality #testing #tdd #refactoring #regression prevention #development methodology

Ready to run

npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-test-driven-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bee:test-driven-development
Source: https://github.com/luanrodrigues/ia-frmwrk/tree/main/default/skills/test-driven-development
Command: npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-test-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces the Test-Driven Development (TDD) methodology, ensuring that all production code is written only after a failing test has been created, thereby preventing regressions and improving code quality.

Core Features & Use Cases

Mandatory Failing Test: Guarantees that no production code is written without a preceding, failing test.
Strict Deletion Policy: Enforces the deletion of any code written before its corresponding test.
Use Case: When starting a new feature, you first write a test that defines the expected behavior. This test will fail initially. Then, you write the minimal amount of code necessary to make the test pass. Finally, you refactor the code while ensuring the test still passes.

Quick Start

Use the bee:test-driven-development skill to implement a new feature by writing a failing test first.

Frequently Asked Questions about bee:test-driven-development

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

FAQPage Schema

How does test-driven development prevent production regressions?▼

The TDD methodology mandates a failing test before any production code is written, ensuring new features and bug fixes are validated upfront to prevent untested code from causing production incidents.

How do I implement the RED-GREEN-REFACTOR cycle when writing a new feature?▼

To implement the RED-GREEN-REFACTOR cycle, write a failing test defining expected behavior, write minimal code to make the test pass, then refactor the code while ensuring the test continues to pass.

What is the TDD approach for handling code written before its corresponding test?▼

The TDD approach enforces a strict deletion policy, requiring the deletion of any production code written before its corresponding test to maintain methodology compliance and ensure code quality.

Can I use test-driven development for both new features and bug fixes?▼

Yes, you can use test-driven development for both new features and bug fixes. The methodology mandates a test-first approach for all development to prevent regressions and improve overall code quality.

When should I refactor code in the test-driven development workflow?▼

You should refactor code during the final REFACTOR phase of the RED-GREEN-REFACTOR cycle, after the failing test passes, ensuring you improve code structure while maintaining passing test coverage.