tdd-workflow

Name: tdd-workflow
Availability: InStock
Author: Eotel

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

Updated Jan 16, 2026

Search Tags:#workflow #testing #tdd #best-practices #unit-testing #integration-testing #e2e-testing

Ready to run

npx skills add https://github.com/Eotel/claude-marketplace --skill tdd-workflow-eotel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Eotel/claude-marketplace/tree/main/plugins/base/skills/tdd-workflow
Command: npx skills add https://github.com/Eotel/claude-marketplace --skill tdd-workflow-eotel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces test-driven development discipline by ensuring tests are written before code and coverage goals are met.

Core Features & Use Cases

Unit tests guiding code design and validation
Integration and E2E test structure for end-to-end quality
Clear workflow documentation and guardrails for consistent practice

Quick Start

Tell me how to start a TDD process for a new feature by writing tests first and then implementing the 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 discipline and ensure tests are written before code?▼

To enforce test-driven development discipline, you must follow a structured workflow that requires writing tests first and then implementing the code to pass them. This ensures tests guide code design and validation from the start.

How do I structure integration and E2E tests to meet an 80% coverage target?▼

Structuring integration and E2E tests to meet an 80% coverage target requires applying explicit coverage goals across all test scopes. You must generate structured tests for feature development, bug fixes, and refactors to ensure end-to-end quality.

Can I use TDD workflow practices for refactoring existing code and fixing bugs?▼

Yes, you can apply test-driven development practices to refactoring and bug fixes. The workflow enforces writing validating tests before altering existing code, ensuring that refactors and fixes maintain end-to-end quality and meet coverage goals.

What is the best way to start a TDD process for a new feature?▼

The best way to start a TDD process for a new feature is to write unit tests first to guide code design and validation. You then implement the code to pass those tests, following structured test-generation steps and documenting the workflow.

Does test-driven development require explicit coverage goals for unit and E2E testing?▼

Yes, enforcing test-driven development requires explicit 80%+ coverage targets across unit, integration, and E2E testing scopes. These coverage goals act as guardrails to ensure consistent practice and validate that code meets end-to-end quality standards.