skills.rest
boparaiamrit
boparaiamritCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforces RED-GREEN-REFACTOR cycles for test-driven software development.

5|1|Updated Feb 7, 2026
Search Tags:#tdd#red-green-refactor#quality-assurance#software-engineering#test-driven-development#regression-testing
One-click install
npx skills add https://github.com/boparaiamrit/skills-by-amrit --skill test-driven-development-boparaiamrit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/boparaiamrit/skills-by-amrit/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/boparaiamrit/skills-by-amrit --skill test-driven-development-boparaiamrit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating development so every feature, bug fix, or refactor starts from a failing test and ends with a passing implementation, ensuring real behavioral guarantees and preventing regressions.

Core Features & Use Cases

  • Enforces the RED-GREEN-REFACTOR cycle to guarantee tests drive implementation decisions.
  • Prevents production code from being added without a failing test first, reducing regressions.
  • Supports iterative development, refactoring discipline, and regression protection across software projects.

Quick Start

Write a failing test first to anchor every feature, then implement production code only to make that test pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is the red-green-refactor cycle in test-driven development?▼

The red-green-refactor cycle in test-driven development is writing a failing test first, implementing code to make it pass, and then refactoring. This enforces strict test discipline and prevents regressions across software projects.

How do I start test-driven development for a new feature?▼

To start test-driven development for a new feature, write a failing test first to anchor the expected behavior. You then implement production code only to make that specific test pass before refactoring.

Does test-driven development work for bug fixes and refactoring?▼

Yes, test-driven development works for bug fixes and refactoring. It applies the red-green-refactor cycle to any behavior change, requiring a failing test before implementation to ensure real behavioral guarantees and prevent regressions.

Why should I write a failing test before writing production code?▼

You should write a failing test before writing production code to guarantee tests drive implementation decisions. This strict discipline prevents untested production code from being added and reduces potential regressions across your software project.

Can I add production code without a failing test in test-driven development?▼

No, you cannot add production code without a failing test in test-driven development. The process actively prevents production code from being added without a failing test first, ensuring iterative development maintains strict behavioral guarantees.

Related Skills

Explore More Software Engineering Skills→
timbuchingertimbuchinger
1

test-driven-development

Enforce writing failing tests before implementing minimal code to pass.

Community
Basic
GainInsightDevGainInsightDev

af-analyse-test-coverage

Analyze test coverage reports to identify untested code paths and gaps.

Official
Intermediate
sandgardenhqsandgardenhq
130

test-driven-development

Write failing tests before production code using a red-green-refactor cycle.

Official
Intermediate
AsiaOstrichAsiaOstrich
70

ATDD 助手

Guide teams through ATDD workflows with Given-When-Then acceptance criteria.

Community
Intermediate