skills.rest
kkingsbe
kkingsbeCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforces a Red-Green-Refactor cycle for feature development, bug fixes, and refactors in software projects.

Updated Feb 22, 2026
Search Tags:#workflow#testing#tdd#qa#quality#red-green-refactor#software-development
One-click install
npx skills add https://github.com/kkingsbe/tempest --skill test-driven-development-kkingsbe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/kkingsbe/tempest/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/kkingsbe/tempest --skill test-driven-development-kkingsbe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams ensure code quality by enforcing a tests-first approach for features and bugfixes.

Core Features & Use Cases

  • Red-Green-Refactor cycle to drive development with failing tests as the starting point.
  • Mandatory test-driven discipline: no production code without a failing test first.
  • Clear workflow guidance for new features, bug fixes, and refactors.

Quick Start

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

Test-driven development (TDD) is a software development technique that enforces a tests-first approach using the red-green-refactor cycle. You write a failing test for desired behavior, implement minimal code to pass it, then refactor to improve design.

How do I start writing tests first for a new feature or bug fix?▼

To start writing tests first, write a failing test that defines the desired behavior for your feature or bug fix. Then implement the minimal production code required to make that test pass before refactoring.

Can I use test-driven development for refactoring existing software projects?▼

Yes, you can use test-driven development for refactoring existing software projects. The discipline applies across features, bug fixes, and refactors, requiring a failing test first to guarantee code quality before modifying production code.

What's the best way to enforce a mandatory test-first discipline in team settings?▼

The best way to enforce test-first discipline in team settings is adopting a strict workflow where no production code is written without a failing test first. This TDD approach guarantees code quality across all team development.

Why does writing minimal code to pass failing tests improve software quality?▼

Writing minimal code to pass failing tests improves software quality by preventing over-engineering and ensuring every piece of production code is directly validated by a test. This TDD workflow drives development strictly through verified behavior.

Related Skills

Explore More Software Engineering Skills→
webdevtodayjasonwebdevtodayjason

test-driven-development

Implement Test-Driven Development by writing failing tests before production code.

Community
Advanced
cskirocskiro
7

e2e-testing

Automate Playwright end-to-end test setup, generation, and regression detection.

Community
Advanced
jackmcintyrejackmcintyre

python-refactoring

Analyze Python code for complexity, duplication, and best practices.

Community
Intermediate
soo-kate-yeonsoo-kate-yeon

moai-workflow-tdd

Implement the RED-GREEN-REFACTOR cycle for test-first software development.

Community
Advanced