skills.rest
ucasYToo
ucasYTooCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforces test-driven development with 80% test coverage across unit, integration, and end-to-end tests.

Updated Apr 5, 2026
Search Tags:#workflow#testing#tdd#e2e#playwright#unit-tests#integration-tests
One-click install
npx skills add https://github.com/ucasYToo/claude-code-configs --skill tdd-workflow-ucasytoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/ucasYToo/claude-code-configs/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/ucasYToo/claude-code-configs --skill tdd-workflow-ucasytoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a test-driven development workflow to ensure code changes are driven by tests, promoting safer refactors and clearer expectations.

Core Features & Use Cases

  • Test-driven development enforcement: ensures developers write tests before coding across new features, bug fixes, and refactors.
  • Comprehensive coverage targets: requires minimum 80% test coverage across unit, integration, and end-to-end tests, including edge cases and failure scenarios.
  • Structured workflow: guides from user journeys to tests, implementation, and refactoring with clear stage gates and reviews.

Quick Start

Start by writing a failing test for a new feature, then implement the code to make it 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 test-driven development for new features and bug fixes?▼

To enforce test-driven development, you must write failing tests before implementation and follow a structured workflow from user journeys to refactoring. This ensures code changes are driven by tests and promotes safer refactors with clear expectations.

What is the best way to achieve 80% test coverage across unit, integration, and e2e tests?▼

Achieving 80% test coverage requires crafting comprehensive tests before implementation across unit, integration, and end-to-end tests. You must include edge cases and failure scenarios while progressing through clear stage gates and reviews.

How do I write unit tests before coding using a structured TDD workflow?▼

Start by writing a failing test for a new feature, then implement the code to make it pass. The structured TDD workflow guides you from user journeys to tests, implementation, and refactoring with clear stage gates and reviews.

Does TDD discipline work with Playwright for end-to-end testing?▼

Yes, TDD discipline works with Playwright for end-to-end testing by requiring comprehensive tests before implementation. The workflow ensures minimum 80% test coverage across unit, integration, and e2e tests including edge cases and failure scenarios.

Can I use a TDD workflow for refactoring existing code safely?▼

Yes, you can use a TDD workflow for refactoring existing code safely by ensuring changes are driven by tests. This promotes safer refactors by maintaining comprehensive test coverage and clear expectations throughout the process.

What are the limitations of enforcing test-driven development across all code changes?▼

Enforcing test-driven development requires crafting comprehensive tests before implementation for all new features, bug fixes, and refactors. This demands significant upfront effort to maintain 80% coverage across unit, integration, and e2e tests.

Related Skills

Explore More Software Engineering Skills→
devantler-techdevantler-tech
3

test-driven-development

Enforce a test-first workflow with failing automated tests before implementation.

Official
Intermediate
Davie521Davie521
7

tdd-workflow

Enforce tests-first workflow with 80%+ coverage across unit, integration, and E2E tests.

Community
Advanced
zenobi-uszenobi-us
68

test-driven-development

Enforce Test-Driven Development with failing tests before implementation.

Official
Intermediate
CUexterCUexter
2

test-driven-development

Enforce test-first development with failing tests before production code.

Community
Advanced