skills.rest
Epiphytic
EpiphyticOFFICIAL
Explore all skills by this author →
WebsiteGitHub

test-driven-development

Enforce test-driven development with red-green-refactor cycles before production code.

7|Updated Feb 6, 2026
Search Tags:#code quality#unit tests#testing#tdd#refactoring#software development
One-click install
npx skills add https://github.com/Epiphytic/ai-plugin-translator --skill test-driven-development-epiphytic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Epiphytic/ai-plugin-translator/tree/main/packages/core/test/fixtures/regression-output/superpowers-marketplace/superpowers/skills/test-driven-development
Command: npx skills add https://github.com/Epiphytic/ai-plugin-translator --skill test-driven-development-epiphytic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers prevent unverified implementations and regressions by enforcing a disciplined test-first workflow before production code is written.

Core Features & Use Cases

  • Red-Green-Refactor Workflow: Guides developers through writing failing tests, implementing minimal solutions, and safely improving code while keeping tests passing.
  • Testing Discipline: Reinforces behavioral testing, meaningful test names, edge case coverage, and avoiding implementation-driven tests.
  • Use Case: Apply this Skill when adding features, fixing bugs, or refactoring software to ensure every change is validated by automated tests before completion.

Quick Start

Use the test-driven-development skill to guide me through implementing a new feature by writing tests first and following the TDD cycle.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is test-driven development and how does it prevent software regressions?▼

Test-driven development prevents unverified implementations and regressions by enforcing a disciplined test-first workflow where automated tests must be written and verified before any production code is created.

How do I apply the red-green-refactor cycle when adding new features?▼

To apply the red-green-refactor cycle, first write a failing behavioral test, then implement the minimal production code required to make it pass, and finally refactor the software safely while keeping the tests green.

Can I use test-first development for bug fixes and refactoring?▼

Yes, test-first development applies to bug fixes and refactoring by requiring structured red-green-refactor execution to validate behavior changes, ensuring every code modification is verified by automated tests.

What makes a meaningful unit test in TDD?▼

A meaningful unit test in TDD focuses on behavioral testing and edge case coverage rather than implementation-driven logic, reinforced by using structured test names to clearly define the expected software behavior.

When should I avoid writing implementation-driven tests?▼

You should avoid writing implementation-driven tests during TDD whenever you are defining new features or changing behavior, because they restrict refactoring and fail to validate the actual software requirements properly.

Related Skills

Explore More Software Engineering Skills→
m16khbm16khb

test-driven-development

Guide Red-Green-Refactor cycles with failing tests before production code.

Community
Advanced
cill-i-amcill-i-am

test-driven-development

Write failing tests before implementing minimal production code in a red-green-refactor workflow.

Community
Intermediate
dhruvinrsonidhruvinrsoni

tdd-workflow

Drive software implementation through the Red-Green-Refactor cycle.

Community
Advanced
fcnatrafcnatra

bdd-with-approvals

Create executable BDD specifications and scannable approval tests.

Community
Intermediate