skills.rest
bluefishs
bluefishsCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce the red-green-refactor cycle by writing failing tests before implementation.

Updated Dec 30, 2025
Search Tags:#tdd#refactoring#red-green-refactor#quality-assurance#test-driven-development#software-testing
One-click install
npx skills add https://github.com/bluefishs/CK_Missive --skill test-driven-development-bluefishs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/bluefishs/CK_Missive/tree/main/.claude/skills/_shared/shared/superpowers/test-driven-development
Command: npx skills add https://github.com/bluefishs/CK_Missive --skill test-driven-development-bluefishs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development (TDD) ensures you write a failing test before you implement code, guaranteeing that the next implementation actually satisfies the test and exposing design flaws early.

Core Features & Use Cases

  • Red-Green-Refactor cycle
  • Always test before production code
  • Applies to new features, bug fixes, and refactoring to reduce regressions

Quick Start

Write a failing test first, 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
What is test-driven development and how does the red-green-refactor cycle work?▼

Test-driven development is a discipline requiring a failing test before any production code. The red-green-refactor cycle means writing a failing test, implementing minimal code to pass it, then refactoring safely.

How do I use test-driven development for bug fixes and refactoring?▼

Use test-driven development for bug fixes by writing a failing test that reproduces the bug, then implementing the fix to make it pass. This prevents regressions and ensures your refactoring maintains correctness.

Can I apply test-driven development across any software project?▼

Yes, you can apply test-driven development across software projects during feature development, bug fixes, and refactoring. It establishes guardrails to prevent untested changes and improves maintainability.

Why write a failing test before implementation in test-driven development?▼

Writing a failing test before implementation guarantees the next code change actually satisfies the test. This test-first approach exposes design flaws early and promotes minimal production code.

Does test-driven development enforce minimal production code?▼

Yes, test-driven development enforces minimal production code by requiring only enough implementation to pass the failing test. This test-first discipline establishes guardrails to prevent untested changes.

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
Obsidian-OwlObsidian-Owl
9

gate-build

Execute configured build and test commands to verify code integrity.

Official
Intermediate
christopherlouetchristopherlouet
5

dev-refactor

Detect code smells and generate refactoring suggestions for JavaScript files.

Community
Intermediate
atusyatusy
8

scrum-team-product-owner

Create and order Product Backlog Items with executable acceptance criteria in scrum.ts.

Community
Intermediate