TDD Workflow Conductor FAQs

Question 1

How are task summaries and metadata stored?

Accepted Answer

Detailed task summaries, including modified files and the rationale for changes, are attached to Git commits using 'git notes' for permanent, non-cluttered documentation.

Question 2

How does this skill track project progress?

Accepted Answer

It uses a local 'plan.md' file as the source of truth, updating task statuses from pending to in-progress and finally complete with associated Git commit SHAs.

Question 3

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

Accepted Answer

It is a three-step TDD process where Claude first writes a failing test (Red), implements the minimum code to pass (Green), and then optimizes the code (Refactor) while ensuring tests remain passing.

Question 4

Is this skill compatible with different programming languages?

Accepted Answer

Yes, it includes standardized commands and verification protocols for Python (pytest), JavaScript/TypeScript (npm/vitest), and Go.

Question 5

What are the quality gates enforced by this workflow?

Accepted Answer

The workflow requires all tests to pass, code coverage to exceed 80%, adherence to style guidelines, proper documentation of public functions, and type safety enforcement.

TDD Workflow Conductor

Key Features

Use Cases

TDD Workflow Conductor

Key Features

Use Cases