skills.rest
derHaken
derHakenCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce a red-green-refactor workflow with failing tests before implementation.

437|13|Updated Feb 25, 2026
Search Tags:#testing#tdd#quality#red-green-refactor#software-engineering#test-driven-development
One-click install
npx skills add https://github.com/derHaken/SuperAntigravity --skill test-driven-development-derhaken
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/derHaken/SuperAntigravity/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/derHaken/SuperAntigravity --skill test-driven-development-derhaken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures code correctness by forcing tests to drive development, preventing regressions and unclear requirements from slipping into production.

Core Features & Use Cases

  • Red-Green-Refactor workflow: write a failing test, implement minimal code to pass, then refactor while keeping tests green.
  • Behavior-first design: ensures APIs meet real-world expectations by codifying them in tests before implementation.
  • Broad applicability: suitable for feature development, bug fixes, and refactoring across software projects.

Quick Start

Write a failing test for the intended behavior, 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 guarantee code correctness?▼

Test-driven development guarantees correctness by forcing you to write failing tests for intended behavior before implementing minimal code, preventing unclear requirements and regressions from reaching production.

What is the red-green-refactor workflow in software engineering?▼

The red-green-refactor workflow involves writing a failing RED test, implementing minimal code to pass it as GREEN, and then refactoring while maintaining green tests to ensure behavior remains correct.

How do I apply test-driven development to bug fixes and refactoring?▼

Apply test-driven development to bug fixes and refactoring by first writing a failing test that captures the expected behavior, then changing the minimal code required to pass that test before refactoring.

When should I use test-driven development in my software project?▼

Use test-driven development across software projects for feature development, bug fixes, and refactoring to ensure APIs meet real-world expectations by codifying requirements in tests before implementation.

How do I write a failing test for intended behavior before implementation?▼

Write a failing test for intended behavior by codifying real-world API expectations into a test case, run it to observe the RED failure, and then implement the minimal code required to turn it GREEN.

Related Skills

Explore More Software Engineering Skills→
qq824045252-ship-itqq824045252-ship-it

superpowers-test-driven-development

Write failing tests before implementing features to enforce the red-green-refactor cycle.

Community
Advanced
jacardljacardl

test-driven-development

Enforce failing tests before production code in Python projects.

Community
Intermediate
ReinaMacCredyReinaMacCredy
223

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Community
Intermediate
scute-shscute-sh
3

bdd-with-approvals

Create executable BDD specifications using approval files with domain-specific language.

Official
Intermediate