sd-tdd

Enforce test-first development with Red-Green-Refactor for regression protection.

2|2|Updated Jul 10, 2024
One-click install
npx skills add https://github.com/kslhunter/simplysm --skill sd-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sd-tdd
Source: https://github.com/kslhunter/simplysm/tree/main/.claude/skills/sd-tdd
Command: npx skills add https://github.com/kslhunter/simplysm --skill sd-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing production code without confirmed behavior leads to defects; TDD forces tests before implementation to catch regressions early and guide clean design. It emphasizes the Red-Green-Refactor cycle, ensuring tests drive architecture and provide living documentation.

Core Features & Use Cases

  • Enforce writing failing tests first to define expected behavior.
  • Guide minimal production code to pass tests, enabling safe refactoring.
  • Applicable to new features, bug fixes, and refactors to maintain regression safety.

Quick Start

Start by writing a failing test that defines the desired behavior, then implement the minimal production code to pass it.

Frequently Asked Questions about sd-tdd

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

FAQPage Schema
How do I start test-driven development for a new software feature?▼

Test-driven development starts by writing a failing unit test that defines the desired software behavior, then implementing minimal production code to pass that test before refactoring.

What is the Red-Green-Refactor cycle in unit testing?▼

The Red-Green-Refactor cycle is a test-driven development discipline where you write a failing test, implement minimal code to pass it, and then safely refactor while maintaining regression protection.

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

Yes, test-driven development applies to bug fixes and refactoring by requiring you to write tests that confirm expected behavior first, ensuring safe code changes and maintaining regression safety.

Why should I write failing tests before production code?▼

Writing failing tests before production code validates expected software behavior early, catches regressions, and guides clean architecture by ensuring tests drive the implementation.

Does test-first development require any specific testing frameworks?▼

No specific testing frameworks are required to apply test-first development; the focus is on the Red-Green-Refactor discipline and writing real tests to validate behavior across feature work and bug fixes.