TDD Workflow Guide FAQs

Question 1

What is the Red-Green-Refactor cycle in this skill?

Accepted Answer

It is a three-step process: first, write exactly one failing test (Red); second, implement the minimal amount of code required to make that test pass (Green); and third, improve the code structure without changing behavior (Refactor).

Question 2

Does this skill support browser-level testing?

Accepted Answer

Yes, it includes specific guidelines for browser and DOM tests, such as preferring data-testid attributes over CSS classes and using proper async patterns instead of hard-coded timeouts.

Question 3

How does this skill handle task tracking?

Accepted Answer

The skill utilizes the Beads toolset (mcp__beads) for issue management and progress tracking, as internal planning files like plan.md are restricted to keep focus on the code.

Question 4

What happens during a Spike Phase?

Accepted Answer

A Spike Phase is an optional, exploratory period used when technical uncertainty is high. Code written during a Spike is considered disposable and must be deleted before the formal TDD process begins.

Question 5

Can I add multiple tests at once using this skill?

Accepted Answer

No, the skill enforces adding only one failing test at a time. This maintains strict development discipline and ensures that every line of code is justified by a specific requirement.

TDD Workflow Guide

主要功能

使用场景

TDD Workflow Guide

主要功能

使用场景