tdd-workflow

Enforce test-driven development by mandating tests before implementation.

2|Updated Jan 11, 2026

Search Tags:#testing #tdd #playwright #quality-assurance #unit-tests #integration-tests #e2e-tests

Ready to run

npx skills add https://github.com/jarrodmedrano/jarrod-claude-skills --skill tdd-workflow-jarrodmedrano

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/jarrodmedrano/jarrod-claude-skills/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/jarrodmedrano/jarrod-claude-skills --skill tdd-workflow-jarrodmedrano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams implement test-driven development by enforcing tests first, reducing defects, and improving long-term maintainability.

Core Features & Use Cases

Guided TDD process: defines steps to write user journeys, create tests, implement code, and refactor with confidence.
Coverage discipline: promotes 80%+ test coverage across unit, integration, and end-to-end tests.
Quality gate for changes: ensures new features, bug fixes, and refactors adhere to the TDD workflow.

Quick Start

Use the tdd-workflow to structure your next feature's development with a test-first approach.

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 for features and bug fixes?▼

To enforce test-driven development, this workflow mandates writing tests before implementation for features, bug fixes, and refactors. It guides you through defining user journeys, generating test cases, and implementing code to satisfy those tests.

Can I use this TDD workflow to maintain 80%+ test coverage across unit and integration tests?▼

Yes, this TDD workflow enforces 80%+ overall test coverage across unit, integration, and end-to-end tests. It acts as a quality gate to ensure new features and refactors adhere to strict coverage discipline.

What is the step-by-step process for writing tests before implementation?▼

The step-by-step TDD process involves defining clear user journeys, generating specific test cases, executing those tests, writing implementation code to satisfy the tests, and verifying that overall coverage meets the 80%+ threshold.

Does this TDD workflow apply to end-to-end tests using Playwright?▼

Yes, this TDD workflow applies to end-to-end tests, including those written with Playwright. It ensures test-first development across all testing layers, from unit and integration to end-to-end user journeys.

Why should I write tests before implementation code?▼

Writing tests before implementation code reduces defects and improves long-term maintainability. This test-driven approach provides a guided process to create tests, implement code to satisfy them, and refactor with confidence.

What are the limitations of enforcing a strict 80%+ test coverage threshold?▼

Enforcing an 80%+ test coverage threshold requires writing tests before any implementation code for all features, bug fixes, and refactors. This strict quality gate may slow down initial development speed to ensure long-term maintainability.