skills.rest
Mark393295827
Mark393295827COMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-driven development with 80% coverage across unit, integration, and E2E tests.

1|Updated Jan 23, 2026
Search Tags:#testing#tdd#unit-testing#integration-testing#quality-assurance#e2e-testing
One-click install
npx skills add https://github.com/Mark393295827/house-maint-ai --skill tdd-workflow-mark393295827
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Mark393295827/house-maint-ai/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/Mark393295827/house-maint-ai --skill tdd-workflow-mark393295827

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing maintainable software often suffers from unclear requirements and insufficient test coverage, leading to bugs and fragile code that regressions later.

Core Features & Use Cases

  • Enforces writing tests before implementation to guide design and catch defects early
  • Targets 80%+ test coverage across unit, integration, and end-to-end tests
  • Provides a structured workflow for generating test cases, executing tests, and performing safe refactors
  • Supports consistent verification when adding features, fixes, or refactors to ensure code remains well-tested

Quick Start

Draft a user journey and the initial failing test, then implement the minimum code to make the test pass

Frequently Asked Questions about tdd-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does test-driven development improve software quality and prevent regressions?▼

Test-driven development improves software quality by enforcing that tests are written before implementation, guiding design and catching defects early. This structured workflow ensures consistent verification when adding features, fixes, or refactors to prevent fragile code.

What is the best way to structure a TDD workflow for unit, integration, and E2E tests?▼

The best way to structure a TDD workflow is to follow a step-by-step approach: draft a user journey, create the initial failing test, implement the minimum code to pass, and then refactor safely across unit, integration, and E2E tests.

What minimum test coverage should I target for maintaining reliable software projects?▼

You should target a minimum of 80% test coverage for maintaining reliable software projects. This coverage threshold applies across unit, integration, and end-to-end tests to ensure code remains well-tested during features and refactors.

Can I use TDD workflows for refactoring existing code safely?▼

Yes, you can use TDD workflows for refactoring existing code safely. The workflow provides consistent verification by running tests before and after code changes, ensuring that refactors do not introduce regressions or break existing functionality.

When do I need to write integration tests versus unit tests in a TDD workflow?▼

You need to write integration tests when verifying interactions between multiple components, while unit tests target isolated logic. A complete TDD workflow requires both, alongside E2E tests, to achieve 80% coverage across the entire software project.

Related Skills

Explore More Software Engineering Skills→
caobingshengcaobingsheng
1

tdd-workflows-tdd-red

Generate failing tests to define expected behavior in the TDD red phase.

Community
Advanced
rube-derube-de
10

test

Detect test frameworks, run suites with coverage, and report findings as a GitHub issue.

Community
Advanced
ruxelionruxelion

coverage

Generate code coverage reports for Rust applications via cargo.

Official
Intermediate
steven-3steven-3

tdd

Enforce test-driven development through a strict RED-GREEN-REFACTOR cycle.

Community
Advanced