tdd-workflow

Enforce test-driven development workflows with 80%+ coverage across unit, integration, and end-to-end tests.

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/Ying-Kai-Liao/TouchStone --skill tdd-workflow-ying-kai-liao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Ying-Kai-Liao/TouchStone/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/Ying-Kai-Liao/TouchStone --skill tdd-workflow-ying-kai-liao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams enforce test-driven development across software projects, ensuring tests are written before code and coverage targets are met.

Core Features & Use Cases

  • Enforces writing tests before code for new features, fixes, and refactors.
  • Specifies 80%+ coverage across unit, integration, and end-to-end tests with edge-case coverage.
  • Provides a structured TDD workflow from user journeys to test execution and refactoring.

Quick Start

Outline a user journey and implement unit, integration, and end-to-end tests to achieve 80%+ overall 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 test-driven development practices across my software projects?

To enforce test-driven development, you need a structured workflow that mandates writing tests before code for new features, bug fixes, and refactoring, ensuring reliable and maintainable code.

What is the best way to achieve 80% test coverage across unit, integration, and E2E tests?

Achieving 80% test coverage requires defining specific unit, integration, and end-to-end test types with edge-case coverage, establishing a repeatable workflow from user journeys to test execution.

How do I structure a TDD workflow from user journeys to test implementation?

Structuring a TDD workflow involves outlining a user journey first, then implementing the corresponding unit, integration, and end-to-end tests before writing the actual code to achieve 80% overall coverage.

Does test-driven development apply to bug fixes and refactoring existing code?

Yes, test-driven development applies to bug fixes and refactoring by enforcing that tests are written before the code changes, ensuring that fixes and refactors maintain 80%+ coverage and reliability.

Why do I need to define unit, integration, and E2E test types for my workflow?

Defining unit, integration, and E2E test types is required to establish a repeatable workflow from user journeys to test execution, ensuring comprehensive edge-case coverage and promoting maintainable code.