tdd-workflow

Enforce test-driven development with unit, integration, and E2E tests.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/caobingsheng/skills --skill tdd-workflow-caobingsheng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/caobingsheng/skills/tree/main/tdd/tdd-workflow
Command: npx skills add https://github.com/caobingsheng/skills --skill tdd-workflow-caobingsheng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces test-driven development governance to ensure new code comes with tests and high coverage, reducing regressions and defects.

Core Features & Use Cases

  • TDD enforcement: ensure tests precede implementation across unit, integration, and E2E.
  • Coverage tracking: maintains 80%+ overall coverage and guards edge cases.
  • Guided workflow: stepwise process from writing user journeys to RED/GREEN checkpoints.

Quick Start

Define a user journey, write failing tests (RED), then implement just enough code to pass (GREEN), and repeat until coverage goals are met.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce test-driven development across unit, integration, and E2E tests?

To enforce test-driven development, you follow a structured workflow starting with user journeys, writing failing tests, then implementing code to pass. This ensures tests precede implementation across unit, integration, and E2E levels.

How do I maintain 80% or higher code coverage during refactoring?

To maintain 80% or higher code coverage during refactoring, use a guided TDD workflow with RED/GREEN checkpoints. This stepwise process guards edge cases and ensures overall test coverage remains consistently above 80%.

What is the best way to structure a TDD workflow for feature development?

The best way to structure a TDD workflow for feature development is by following stepwise RED/GREEN checkpoints. You define a user journey, write failing tests, implement just enough code to pass, and repeat until coverage goals are met.

Does TDD workflow support bug fixes and refactoring or only new feature development?

TDD workflow supports bug fixes and refactoring alongside new feature development. It enforces test-driven development and comprehensive test coverage across codebases during all three cycles to reduce regressions and defects.

Why do I need Git checkpoint discipline in test automation?

You need Git checkpoint discipline in test automation to enforce TDD governance and track RED/GREEN cycle progress. This discipline maintains 80%+ overall coverage and ensures new code comes with tests, reducing regressions.

When should I not use a strict TDD workflow with 80% coverage requirements?

You should carefully consider using a strict TDD workflow with 80% coverage requirements when working on rapid prototypes or exploratory code. The enforced governance and comprehensive test coverage requirements are designed for reducing defects in production codebases.