tdd-workflow

Enforces test-driven development workflows requiring minimum 80% code coverage across Jest/Vitest, API integration, and Playwright tests.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill tdd-workflow-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/luongldptit/move-ticket --skill tdd-workflow-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing code without prior tests leads to inconsistent quality, hard-to-fix production bugs, and low test coverage that makes refactoring risky and slows down development velocity.

Core Features & Use Cases

  • Test-First Enforcement: Guides you to write failing tests before implementing any code for new features, bug fixes, or refactoring tasks.
  • Comprehensive Coverage Requirements: Mandates minimum 80% coverage across unit, integration, and end-to-end tests to catch edge cases, error scenarios, and boundary conditions.
  • Pre-Built Test Patterns: Includes ready-to-use templates for Jest/Vitest unit tests, API integration tests, and Playwright E2E tests for common use cases like component testing, endpoint validation, and user flow automation.
  • Use Case Example: When adding a new market search feature, this skill walks you through writing user journey tests, implementing the feature to pass those tests, and verifying coverage meets the 80% threshold before deployment.

Quick Start

Use the tdd-workflow skill to write failing tests for your new user authentication feature before implementing the corresponding code logic.

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 practices for new features and refactoring?

Test-driven development enforcement guides you to write failing tests before implementing code for features, bug fixes, or refactoring. This eliminates production bugs and reduces technical debt by validating logic prior to implementation.

What's the best way to achieve 80% code coverage across unit and integration tests?

Achieving 80% code coverage requires mandating minimum thresholds across unit, integration, and end-to-end tests. This catches edge cases, error scenarios, and boundary conditions before deployment while ensuring safe refactoring.

Does this test-driven development workflow include pre-built patterns for Jest and Playwright?

Yes, this test-driven development workflow includes ready-to-use templates for Jest/Vitest unit tests, API integration tests, and Playwright E2E tests. These patterns cover component testing, endpoint validation, and user flow automation.

How do I write tests before code when adding a new API endpoint or UI component?

Writing tests before code involves creating user journey tests and endpoint validation tests first, then implementing the API endpoint or UI component logic to pass those tests, and finally verifying coverage meets the 80% threshold.

Why does writing code without prior tests lead to inconsistent quality and risky refactoring?

Writing code without prior tests leads to inconsistent quality because low test coverage makes refactoring risky and slows development velocity. Test-first enforcement eliminates hard-to-fix production bugs by validating behavior upfront.