tdd-workflow

Enforce a test-driven development workflow with Jest, Vitest, and Playwright.

1|Updated Apr 11, 2026

Search Tags:#testing #tdd #refactoring #jest #playwright #coverage

Ready to run

npx skills add https://github.com/its-Basudeba/Care-HMS --skill tdd-workflow-its-basudeba

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/its-Basudeba/Care-HMS/tree/main/.agent/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/its-Basudeba/Care-HMS --skill tdd-workflow-its-basudeba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of inconsistent code quality and insufficient testing by enforcing a rigorous Test-Driven Development (TDD) lifecycle that ensures high reliability and maintainability.

Core Features & Use Cases

Structured TDD Lifecycle: Guides developers through the cycle of writing failing tests, implementing minimal code, and refactoring.
Comprehensive Coverage Enforcement: Mandates 80%+ coverage across unit, integration, and E2E test suites.
Use Case: When building a new API endpoint or refactoring a complex component, use this skill to ensure that every edge case is covered by a test before the implementation is finalized.

Quick Start

Activate the tdd-workflow skill to begin a new feature development cycle by defining your user journeys and generating the initial test suite.

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 my application stack?▼

To enforce test-driven development, follow a structured TDD lifecycle of writing failing tests, implementing minimal code, and refactoring. This ensures high reliability and maintainability across feature development and bug fixing.

How do I maintain 80% test coverage when refactoring complex components?▼

Maintain 80% test coverage during refactoring by mandating comprehensive test suites across unit, integration, and E2E tests. Define user journeys and generate initial tests to cover edge cases before finalizing implementation.

Does this TDD workflow support Jest, Vitest, and Playwright for E2E testing?▼

Yes, this TDD workflow supports Jest, Vitest, and Playwright. Integration with these testing frameworks is required to verify system behavior and maintain the minimum 80% test coverage across your application stack.

What is the best way to start a new feature cycle using TDD?▼

The best way to start a new feature cycle using TDD is to define your user journeys and generate the initial test suite. This structured approach ensures every edge case is covered before implementation begins.

When should I use a strict TDD lifecycle instead of standard testing?▼

Use a strict TDD lifecycle instead of standard testing when building new API endpoints, fixing bugs, or refactoring complex components. It addresses inconsistent code quality by ensuring insufficient testing is eliminated through rigorous coverage enforcement.