skills.rest
jsloat
jsloatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-driven-development

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing tests before code to ensure correct behavior and prevent regressions, guiding teams toward reliable, maintainable software.

Core Features & Use Cases

  • Red-Green-Refactor workflow: write a failing test, implement minimal code to pass, then refactor safely.
  • Mandatory tests for new features and bug fixes to guarantee behavior and prevent regressions.
  • Clear guidelines for when to apply TDD, reducing risk during refactors and design changes.

Quick Start

Write a small failing test for a new feature, then implement the simplest code required to make it 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 test-driven development workflow for writing new features?▼

Test-driven development enforces a strict Red-Green-Refactor workflow: write a failing test, implement minimal production code to pass it, then refactor safely to guarantee behavior and prevent regressions.

How do I start using test-driven development for bug fixes?▼

To apply test-driven development to bug fixes, write a real test that fails and reproduces the bug, then implement the minimal code required to make the test pass and prevent future regressions.

When should I use test-driven development during refactoring?▼

Use test-driven development during refactoring and design changes to reduce risk, ensuring mandatory tests verify existing behavior before you modify the underlying production code.

Does test-driven development require writing tests before any implementation?▼

Yes, test-driven development requires real tests that fail first, guiding you to write minimal production code only after a test exists to ensure correct behavior and maintainable software.

What's the difference between test-driven development and writing tests after implementation?▼

Test-driven development mandates failing tests before implementation to shape design, whereas testing afterward only verifies code already written, missing the preventive regression coverage of the Red-Green-Refactor cycle.

Why does test-driven development help prevent software regressions?▼

Test-driven development prevents regressions by mandating tests for new features and bug fixes upfront, ensuring every piece of production code is validated by a failing test that passed before it.

Related Skills

Explore More Software Engineering Skills→
AlexiosBluffMaraAlexiosBluffMara
2

test-driven-development

Guide teams through the Red-Green-Refactor cycle for test-first development.

Community
Intermediate
parcadeiparcadei
3.9k

test-driven-development

Enforce test-first development using Red-Green-Refactor with failing tests before production code.

Community
Basic
desafindesafin

moai-workflow-tdd

Guide the RED-GREEN-REFACTOR cycle to build features from tests.

Community
Advanced
nimeshgurungnimeshgurung

test-driven-development

Guide the Red-Green-Refactor cycle for Test-Driven Development.

Community
Advanced