tdd-workflow

Enforce test-first development with coverage tracking across unit, integration, and E2E tests.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Jialong6/Cursor-OEM-backpack-factory --skill tdd-workflow-jialong6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Jialong6/Cursor-OEM-backpack-factory/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/Jialong6/Cursor-OEM-backpack-factory --skill tdd-workflow-jialong6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers to adopt Test-Driven Development by enforcing tests before code and ensuring 80%+ coverage across unit, integration, and end-to-end tests.

Core Features & Use Cases

  • Enforces a TDD workflow for feature development, bug fixes, refactoring, and API changes.
  • Provides a repeatable process: write user journeys, generate test cases, run tests, implement code, and verify coverage.
  • Improves code quality, reduces regressions, and speeds up maintenance by aligning team practices around tests.

Quick Start

Activate the tdd-workflow skill to start writing tests first, define clear acceptance criteria, and follow the steps from test generation to refactoring to maintain high coverage.

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 bug fixes?

You can enforce a test-driven development workflow by following a structured process: write user journeys, generate test cases, run tests, implement code, and verify coverage. This test-first methodology ensures 80%+ coverage across unit, integration, and E2E tests.

What is the best way to maintain high test coverage during refactoring and API changes?

The best way to maintain high test coverage during refactoring and API changes is to adopt a test-first methodology. By generating deterministic tests from user journeys before changing code, you align team practices and reduce regressions throughout the workflow.

How do I structure unit, integration, and E2E tests when adopting a test-first methodology?

To structure unit, integration, and E2E tests in a test-first methodology, start by defining clear acceptance criteria through user journeys. Generate deterministic test cases spanning these layers, run them, implement the code, and verify 80%+ coverage before completing the workflow.

Does this TDD workflow apply to component changes and refactoring?

Yes, this TDD workflow applies directly to component changes, refactoring, feature development, and bug fixes. It provides a repeatable process spanning unit, integration, and E2E tests to ensure high coverage and verify every change.

When do I need a structured workflow for test generation and verification?

You need a structured workflow for test generation and verification when your team struggles with regressions and inconsistent testing practices. Enforcing a test-first methodology with deterministic tests and 80%+ coverage tracking improves code quality and speeds up maintenance.