tdd-workflow

Enforce test-driven development with RED-GREEN checkpoints and 80%+ coverage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing code without strict testing and coverage targets is common; this skill codifies a disciplined TDD workflow and enforces measurable test coverage across the project.

Core Features & Use Cases

  • Enforce writing tests before code
  • Target 80%+ coverage across unit, integration, and E2E tests
  • Provide RED-GREEN checkpoint guidance and a structured workflow to guide refactors

Quick Start

Describe a new feature, write failing tests first, implement the minimal code to pass, and create a RED-GREEN checkpoint on the active branch.

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 feature work and refactors?

You enforce test-driven development by codifying a structured RED-GREEN workflow with checkpoint commits, requiring failing tests before implementation and targeting 80%+ test coverage across unit, integration, and E2E stages.

What is the RED-GREEN cycle in TDD and how does it guide refactoring?

The RED-GREEN cycle in TDD requires writing a failing test first, implementing minimal code to pass it, and creating explicit checkpoint commits on the current branch to safely guide subsequent refactoring.

Can I use this TDD workflow with my existing Git repository and CI pipelines?

Yes, this TDD workflow applies directly to codebases using Git, CI pipelines, and common testing frameworks, integrating checkpoint commits into your active branch to enforce coverage.

How do I start writing failing tests first to achieve 80% test coverage?

You start by describing a new feature, writing failing tests first, implementing the minimal code required to pass those tests, and creating a RED-GREEN checkpoint on your active branch.

Does this TDD workflow require separate unit, integration, and E2E test stages?

Yes, this TDD workflow requires clearly defined test stages across unit, integration, and E2E testing to ensure robust validation and enforce measurable 80%+ test coverage.

What's the best way to maintain code quality during bug fixes using TDD?

The best way to maintain code quality during bug fixes is applying a disciplined TDD workflow with reproducible RED-GREEN cycles and checkpoint commits to ensure robust validation and 80%+ coverage.