tdd-workflow

Enforce test-driven development with tests written before code and 80% coverage.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/anton-dovnar/cursor --skill tdd-workflow-anton-dovnar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/anton-dovnar/cursor/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/anton-dovnar/cursor --skill tdd-workflow-anton-dovnar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams enforce a Test-Driven Development workflow, reducing defects by ensuring code changes are driven by tests and validated with high coverage.

Core Features & Use Cases

  • Tests BEFORE Code: Always write unit tests first to define expected behavior and guardrails.
  • 80%+ Coverage: Targets minimum 80% coverage across unit, integration, and E2E tests to sustain quality.
  • Lifecycle Coverage: Applies during feature development, bug fixes, refactoring, API changes, and component creation to maintain discipline.

Quick Start

Begin by writing a failing unit test that captures the desired behavior, then implement the code to make the test pass.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce a test-driven development workflow with high code coverage?

To enforce test-driven development, you write failing unit tests first to define expected behavior, implement code to pass them, and maintain a minimum of 80% coverage across unit, integration, and E2E tests.

How do I write tests before code during feature development?

Writing tests before code involves creating a failing unit test that captures desired behavior, implementing the code to make it pass, and refactoring. This test-driven approach applies to feature development, bug fixes, and API changes.

Does TDD require unit, integration, and E2E tests to maintain 80% coverage?

Yes, test-driven development here requires unit, integration, and end-to-end tests to sustain consistent test discipline. The workflow targets a minimum of 80% overall coverage across these test types.

What is the best way to apply TDD during refactoring and API changes?

The best way to apply TDD during refactoring and API changes is to write tests first that define guardrails, run them, implement the code changes, and refactor while maintaining the 80% coverage target.

Can I use this TDD workflow for bug fixes and component creation?

Yes, you can use this TDD workflow for bug fixes and component creation. It ensures code changes are driven by tests with high coverage throughout the lifecycle to reduce defects.