tdd-workflow

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

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill tdd-workflow-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/tdd-workflow
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill tdd-workflow-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing high-quality software can be hindered by a lack of disciplined testing; this skill enforces test-driven development with strict coverage targets.

Core Features & Use Cases

  • Enforces tests written first for features, bugs, and refactors.
  • Tracks and validates unit, integration, and end-to-end test coverage (target 80%+).
  • Provides a structured workflow for adding tests, writing code, and maintaining quality across teams.

Quick Start

Start by writing tests for a new feature before implementing any code.

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 testing?

You enforce test-driven development by adopting a workflow that requires writing tests first for features, bugs, and refactors, then validating them across unit, integration, and e2e testing before code changes pass.

What is the best way to maintain 80%+ test coverage during code refactoring?

Maintaining 80%+ test coverage during refactoring requires a structured workflow that tracks and validates unit, integration, and end-to-end test coverage, ensuring all modified code passes existing tests before approval.

Can I use this TDD workflow for both new features and bug fixes?

Yes, this TDD workflow supports creation, modification, and refactoring tasks by enforcing a reproducible strategy where tests are written first for features, bugs, and refactors across typical software projects.

How does a strict test-first workflow improve code quality?

A strict test-first workflow improves code quality by requiring a defined test strategy and 80%+ coverage targets, preventing untested code changes from passing validation across the software project.

Do I need a predefined test strategy to start writing tests first?

Yes, you need a defined test strategy and a reproducible workflow for running and validating tests to effectively enforce test-driven development and achieve the required 80%+ coverage target.