test-driven-development

Name: test-driven-development
Availability: InStock
Author: Wilder1222

Enforce test-driven development with red-green-refactor cycles and gated THINK/PLAN stages.

2|Updated Mar 25, 2026

Search Tags:#automation #red-green-refactor #code-quality #quality-assurance #software-engineering #test-driven-development

Ready to run

npx skills add https://github.com/Wilder1222/superomni --skill test-driven-development-wilder1222

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Wilder1222/superomni/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/Wilder1222/superomni --skill test-driven-development-wilder1222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a test-driven development process for code changes to improve reliability.

Core Features & Use Cases

Enforces red-green-refactor cycle and Delete Untested Code rule.
Provides gated progression through THINK/PLAN and auto-advance.
Supports artifact generation and traceability for audits.

Quick Start

Describe a feature or bug, then let the skill write a failing test and implement the minimum 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

How do I enforce test-driven development for every code change?▼

To enforce test-driven development for every code change, the Skill requires explicit tests before implementation and ensures red-green-refactor cycles. It gates progression through THINK and PLAN stages across new features, bug fixes, and refactors.

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

The red-green-refactor cycle is a test-driven development process where a failing test is written first, minimum code is implemented to pass it, and then the code is refactored. The Skill automatically enforces this cycle and deletes untested code.

How do I automate quality assurance for new features and bug fixes?▼

Automate quality assurance for new features and bug fixes by applying strict test-driven development discipline. The Skill gates code progression through THINK and PLAN stages, requiring failing tests before implementation to ensure correct, reliable code.

Does test-driven development work for refactoring existing software projects?▼

Yes, test-driven development works for refactoring existing software projects. The Skill applies red-green-refactor cycles across software projects, enforcing the deletion of untested code and requiring explicit tests before implementing any refactored changes.

How do I start writing a failing test before implementing the code?▼

To start writing a failing test before implementing code, describe a feature or bug, then let the Skill write the failing test. It will implement the minimum code required to pass the test, enforcing the red-green-refactor cycle.

Why does test-driven development require deleting untested code?▼

Test-driven development requires deleting untested code to enforce strict quality assurance and reliability. By applying the Delete Untested Code rule, the Skill ensures only verified, tested implementations progress through the red-green-refactor cycle.