test-driven-development

Enforce a Red-Green-Refactor cycle with failing tests before code.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Ab0umar/SRV100_Acc --skill test-driven-development-ab0umar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Ab0umar/SRV100_Acc/tree/main/.codex/plugins/cache/openai-curated/superpowers/dc902811/skills/test-driven-development
Command: npx skills add https://github.com/Ab0umar/SRV100_Acc --skill test-driven-development-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stabilizes code quality by enforcing test-driven development and preventing untested changes.

Core Features & Use Cases

  • Red-Green-Refactor workflow: write failing tests, implement minimal code, refactor for clarity.
  • Bug fixes and feature work: ensures changes are driven by tests and well-scoped.
  • Cross-domain applicability: usable for frontend, backend, and service-layer work in typical software projects.

Quick Start

Provide a failing test for the new feature or bug, then write the minimal implementation to pass the test and refactor.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I start writing unit tests before implementing a new feature?

Writing unit tests before feature implementation requires a failing test first. You provide a failing test for the feature or bug, then write minimal code to pass it, and finally refactor for clarity.

What is the red-green-refactor cycle in test-driven development?

The red-green-refactor cycle is a test-driven development workflow where you write a failing test, implement the minimal code to make it pass, and then refactor the code for clarity and quality.

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

Yes, test-driven development applies to bug fixes and refactoring. It ensures changes are well-scoped and driven by tests, stabilizing code quality by preventing untested modifications across your project.

Does test-driven development work for both frontend and backend development workflows?

Test-driven development is cross-domain applicable. It can be used for frontend, backend, and service-layer work in typical software projects, enforcing test-first discipline across the entire development cycle.

Why should I require failing tests before writing implementation code?

Requiring failing tests before implementation code enforces a test-first discipline. This prevents untested changes, stabilizes code quality, and promotes minimal, incremental implementations that are well-scoped.