tdd-workflow

Name: tdd-workflow
Availability: InStock
Author: phantian2026

Enforce a test-driven development workflow with 80%+ test coverage.

Updated Apr 28, 2026

Search Tags:#workflow #testing #tdd #code-coverage #unit-tests #integration-tests #e2e-tests

Ready to run

npx skills add https://github.com/phanTian2026/mobiletrading --skill tdd-workflow-phantian2026

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/phanTian2026/mobiletrading/tree/main/trae/skills/tdd-workflow
Command: npx skills add https://github.com/phanTian2026/mobiletrading --skill tdd-workflow-phantian2026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a test-driven development workflow, ensuring tests drive implementation and maintainability across features, bugs, and refactors.

Core Features & Use Cases

TDD-first development: Write unit, integration, and E2E tests before coding.
Coverage targets: Achieve and verify 80%+ test coverage across all test types.
Guided workflow: Step-by-step process from user journeys to refactoring and verification.

Quick Start

Write unit tests first, then implement the minimal code to satisfy them and verify 80%+ 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 when creating new features?▼

Achieving 80%+ test coverage requires writing unit, integration, and E2E tests before implementation, then verifying that the combined test suite covers at least 80% of the executed code paths.

What is the best way to structure unit tests and integration tests during refactoring?▼

The best way to structure tests during refactoring is to follow a step-by-step workflow from user journeys to verification, ensuring comprehensive coverage across unit, integration, and end-to-end tests.

Does writing tests before implementation work for both bug fixes and new features?▼

Yes, writing tests before implementation works for both bug fixes and new features. It drives the implementation process, ensuring maintainability and comprehensive coverage across all test types.

How do I verify E2E tests and unit tests maintain 80% code coverage?▼

To verify E2E tests and unit tests maintain 80% code coverage, implement minimal code to satisfy the tests first, then run a coverage analysis to confirm the threshold is met across the project.

When should I not use a strict TDD workflow for software projects?▼

You should not use a strict TDD workflow when rapid prototyping without immediate test coverage constraints is required, as this workflow demands writing unit tests first and maintaining 80%+ coverage.