tdd-workflow

Enforce a test-driven development lifecycle with 80% minimum coverage.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill tdd-workflow-thejanajayalath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/ThejanaJayalath/Niolla-PM-system/tree/main/.cursor/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill tdd-workflow-thejanajayalath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of fragile, untested code by enforcing a strict Test-Driven Development (TDD) lifecycle that ensures high reliability and maintainability.

Core Features & Use Cases

  • Coverage Enforcement: Guarantees a minimum of 80% test coverage across unit, integration, and E2E tests.
  • Workflow Standardization: Provides a clear, step-by-step process for writing tests before implementation to prevent regression and logic errors.
  • Use Case: When building a new API endpoint or refactoring a complex component, this skill guides you to define expected behaviors through tests first, ensuring the final implementation is bug-free and fully verified.

Quick Start

Activate the tdd-workflow skill to generate a comprehensive test suite for the new user authentication module before writing any implementation 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 a test-driven development workflow for feature development and refactoring?

Test-driven development requires writing tests to define expected behavior before creating any implementation code. This approach prevents regression and logic errors during feature development, bug fixing, and refactoring tasks across the codebase.

What is the minimum test coverage threshold required for reliable code?

A minimum coverage threshold of 80% is required to ensure code reliability and maintainability. This coverage is enforced across unit, integration, and E2E testing frameworks during feature development and refactoring.

How do I write tests before implementation for a new API endpoint?

To write tests before implementation for a new API endpoint, you generate a comprehensive test suite defining expected behaviors first. This ensures the final implementation is bug-free and fully verified before deployment.

Does this TDD workflow work with Jest and Playwright for E2E testing?

Yes, the TDD workflow supports E2E testing using frameworks like Playwright and Jest. It guides you to define expected behaviors through tests first, ensuring the final implementation is bug-free and fully verified.

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

You should use a strict TDD lifecycle instead of standard refactoring when working with fragile, untested code to prevent regressions. It is essential for guaranteeing high reliability and maintainability across complex component updates.