skills.rest
Ben2pc
Ben2pcOFFICIAL
Explore all skills by this author →
GitHub

test-driven-development

Guide teams through red-green-refactor cycles with failing tests before implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD helps teams avoid shipping buggy features by ensuring tests drive the implementation from the outset, clarifying requirements and reducing regressions.

Core Features & Use Cases

  • Test-first discipline: Write a failing test before writing any production code.
  • RED-GREEN-REFACTOR cycle: Follow the cycle to iterate safely from failure to feature completion.
  • Risk reduction: Align development with verification to catch design flaws early.

Quick Start

Begin a TDD cycle by writing a failing test for the new feature, then implement the minimal code to pass it.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How does test-driven development prevent regressions during feature development?▼

Test-driven development prevents regressions by enforcing a test-first discipline, requiring teams to write a failing test before implementation to verify features and catch design flaws early.

What is the red-green-refactor cycle in TDD?▼

The red-green-refactor cycle is a TDD mechanism where you write a failing test, implement minimal production code to pass it, and then refactor safely to drive design without breaking functionality.

How do I start a TDD cycle for a new software feature?▼

To start a TDD cycle, write a failing test that defines the new feature's requirements, implement the minimal code to make it pass, and then apply disciplined refactoring practices to iterate safely.

When should I use test-first discipline for bug fixes?▼

Use test-first discipline for bug fixes across projects to clarify requirements upfront; writing a failing test that reproduces the bug ensures your minimal implementation prevents future regressions.

Does TDD work for large software engineering projects?▼

TDD works for feature development and bug fixes across projects of any scale, aligning development with verification to reduce risk and ensure reliable software delivery without shipping buggy features.

Related Skills

Explore More Software Engineering Skills→
LeandroBenjaminLLeandroBenjaminL

sdd-verify

Execute tests and validate TDD evidence for SDD implementations.

Community
Advanced
heyallencaoheyallencao
118

test-first

Generate failing tests upfront and iteratively develop code to pass them.

Community
Intermediate
haakonbullhaakonbull
5

test-refactoring

Refactor Python pytest suites by merging overlaps, parameterizing duplicates, and pruning dead coverage.

Community
Intermediate
SorinSSorinS

speckit-specify

Convert natural language descriptions into detailed software feature specifications.

Community
Advanced