convergence-tdd

Enforce a red-green-refactor test-driven development cycle for features, bug fixes, and refactors.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/c-sonnier/convergence --skill convergence-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convergence-tdd
Source: https://github.com/c-sonnier/convergence/tree/main/plugins/convergence/skills/tdd
Command: npx skills add https://github.com/c-sonnier/convergence --skill convergence-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a test-driven development cycle to prevent production bugs by requiring tests to define expected behavior before code is written.

Core Features & Use Cases

  • Test-driven workflow: write a failing test before implementing functionality to guide design.
  • Continuous feedback: run tests frequently to validate behavior as code evolves.
  • Applicable to features, bug fixes, and refactors in small, repeatable iterations.

Quick Start

Write a failing test for the desired behavior, then implement the minimal code to pass and refactor.

Frequently Asked Questions about convergence-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 begins by writing a failing test that defines the desired behavior, then implementing the minimal code required to pass that test. You finish by refactoring the code while keeping the test green.

What is the red-green-refactor cycle in software engineering?

The red-green-refactor cycle is a test-driven development discipline where you write a failing test, implement the minimal code to make it pass, and then clean up the code without breaking the test.

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

Yes, test-driven development applies to bug fixes and refactors by running tests in small, repeatable iterations to validate behavior as code evolves, preventing production bugs before they happen.

Why does test-driven development require a failing test before writing production code?

Test-driven development requires a failing test first to ensure the test accurately defines expected behavior and to guide the software design before any production code is written.

What is the best way to prevent production bugs with test-first coding?

Test-first coding prevents production bugs by enforcing continuous feedback, requiring you to run tests frequently and validate software behavior in small iterative cycles as the codebase evolves.

When should I not use test-driven development for software engineering?

Test-driven development is less suited for exploratory prototyping where behavior is undefined, as it requires writing a failing test to define expected behavior before implementing the functionality.