tdd-workflow

Orchestrate RED-GREEN-REFACTOR cycles for TDD workflow guidance.

Updated Mar 3, 2025
One-click install
npx skills add https://github.com/cyhinverse/YiBu --skill tdd-workflow-cyhinverse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/cyhinverse/YiBu/tree/main/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/cyhinverse/YiBu --skill tdd-workflow-cyhinverse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to adopt a consistent TDD workflow, leading to unclear tests, flaky releases, and lower code quality.

Core Features & Use Cases

  • Defines a repeatable RED-GREEN-REFACTOR cycle to guide feature development.
  • Provides concrete rules and patterns for test naming, scope, and refactoring discipline.
  • Useful for onboarding new developers and maintaining long-term software quality.

Quick Start

Start by writing a failing test for a small feature, then implement the minimum code to pass.

Frequently Asked Questions about tdd-workflow

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

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

The red-green-refactor cycle in test-driven development is a repeatable workflow where you write a failing test, implement the minimum code to pass it, then refine the design. This cycle guides feature development and maintains long-term software quality.

How do I start writing a failing test for a small feature?

To start writing a failing test for a small feature, define a specific test case that captures the desired behavior before any implementation exists. You then write the minimum code required to make that failing test pass.

Can I use test-driven development for maintaining existing software?

Yes, you can use test-driven development for maintaining existing software. The workflow applies to maintenance scenarios by guiding teams through structured cycles that clarify test scope and enforce refactoring discipline to prevent flaky releases.

What is the best way to establish test naming and scope in agile projects?

The best way to establish test naming and scope in agile projects is to apply concrete rules and patterns that enforce refactoring discipline. This ensures tests remain clear and targeted throughout the development cycle.

Why does inconsistent test-driven development lead to flaky releases?

Inconsistent test-driven development leads to flaky releases because teams lack a repeatable workflow to guide feature implementation. Without structured refactoring discipline and clear test scope, code quality degrades and releases become unreliable.