tdd

Enforce Test-Driven Development by requiring failing tests before production code.

6|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Goblin1024/oh-my-kimi --skill tdd-goblin1024
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Goblin1024/oh-my-kimi/tree/main/skills/tdd
Command: npx skills add https://github.com/Goblin1024/oh-my-kimi --skill tdd-goblin1024

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces Test-Driven Development by requiring that tests fail before production code is written, preventing accidental overreach and guiding a disciplined workflow.

Core Features & Use Cases

  • Red-Green-Refactor cycle: ensure test-first iterations and incremental design.
  • Enforcement Rules: block writing production code before a failing test and mandate one feature per cycle.
  • Guided workflow: provides a structured sequence for running tests and implementing minimal, test-passing code.

Quick Start

Run the project's tests to observe a failing test, implement just enough code to pass, then refactor and repeat.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce test-driven development in my software engineering workflow?

Test-driven development is enforced by blocking production code creation until a failing test is written. This prevents accidental overreach and guides a disciplined Red-Green-Refactor cycle across projects and teams.

What is the Red-Green-Refactor cycle for software testing?

The Red-Green-Refactor cycle is a test-driven development process ensuring test-first iterations. You write a failing test, implement minimal code to pass it, then refactor the codebase for incremental design improvements.

How do I start a test-first iteration workflow for incremental design?

To start a test-first iteration, run the project's tests to observe a failing test. Then implement just enough production code to pass the test, refactor the result, and repeat the cycle.

Do I need a test runner environment to use test-driven development enforcement?

Yes, a test runner environment is required to enforce test-driven development. The structured, command-driven workflow relies on executing tests to validate the failing test state before production code is implemented.

Why does test-driven development mandate one feature per cycle?

Test-driven development mandates one feature per cycle to prevent accidental overreach. This enforcement rule ensures structured, incremental design by focusing on minimal, test-passing code iterations.

What are the limitations of enforcing test-driven development rules?

Enforcing test-driven development rules limits writing production code before a failing test exists. This constraint requires strict adherence to the command-driven workflow, which may slow down initial feature prototyping.