tdd-workflow

Automate the TDD workflow to enforce tests before implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to maintain consistent test coverage during rapid iterations. This skill provides a structured workflow that enforces writing tests before code, tracks coverage goals, and aligns team practices.

Core Features & Use Cases

  • Guided TDD workflow: define user journeys, generate test cases, run tests, and refactor while maintaining green coverage.
  • End-to-end workflow: unit, integration, and E2E tests with coverage targets and reporting.
  • Step-by-step templates for writing tests and managing test data.

Quick Start

Describe a feature and follow the prompts to write tests before coding and verify 80%+ coverage.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce TDD and maintain test coverage during rapid feature development?

You can enforce TDD by automating the workflow to require tests before implementation, tracking coverage goals, and aligning practices to maintain a minimum 80% test threshold during feature development.

What is the best way to guide writing unit, integration, and E2E tests before coding?

The best way to guide writing tests before coding is using step-by-step templates that define user journeys, generate test cases, run tests, and refactor while validating green coverage across unit, integration, and E2E levels.

Can I apply TDD workflow automation to bug fixes and refactoring?

Yes, TDD workflow automation applies across bug fixes and refactors by providing test scaffolding guidance, stepwise test generation, and workflow validation with clear examples to maintain green coverage.

How do I start writing tests first when describing a new feature?

To start writing tests first, describe the feature and follow the guided prompts to write tests before coding, then verify implementation against the 80% coverage target using the provided templates.

Does strict test-first workflow automation work for managing test data and scaffolding?

Yes, strict test-first workflow automation works for managing test data and scaffolding by providing structured templates and guardrails that align team practices and track coverage goals.

Why does maintaining consistent test coverage fail during rapid iterations without a structured workflow?

Maintaining consistent coverage fails without a structured workflow because developers lack enforced test generation steps and guardrails to track minimum 80% coverage targets across the codebase.