TDD Issues Workflow FAQs

Question 1

What does the TDD Issues Workflow skill do?

Accepted Answer

This skill automates a rigorous Test-Driven Development process within Claude Code. It systematically works through an issues list, writing failing tests before implementation, verifying 100% code coverage, and performing visual browser checks for UI updates.

Question 2

When should I use this skill?

Accepted Answer

Use this skill when you need to resolve bugs or implement new features listed in your documentation. It is ideal for projects requiring high reliability, strict testing standards, and documented visual proof of frontend changes.

Question 3

How does it improve my development workflow?

Accepted Answer

It removes the manual overhead of issue tracking and regression testing. By automating the pre-flight checks, environment validation, and documentation updates, it ensures your codebase remains stable and your 'docs/ISSUES.md' is always up to date.

Question 4

How does it handle CSS and UI changes?

Accepted Answer

For CSS-only updates, the skill bypasses traditional logic tests and instead uses automated browser devtools to navigate to your local environment, capture screenshots of the changes, and verify the visual output manually before committing.

Question 5

What are the requirements for non-CSS code changes?

Accepted Answer

The skill enforces a strict 'test-first' rule: it must write and fail a test before modifying any logic. Furthermore, it will not proceed unless the full test suite passes with 100% coverage across statements, functions, lines, and branches.

TDD Issues Workflow

TDD Issues Workflow

Key Features

Use Cases

Key Features

Use Cases