Conductor TDD Workflow FAQs

Question 1

What is the Conductor TDD workflow?

Accepted Answer

It is a structured 11-step process for implementing software tasks, focusing on writing failing tests first (RED), followed by minimal implementation (GREEN), and finally code improvement (REFACTOR).

Question 2

What happens if a task deviates from the original plan?

Accepted Answer

The workflow includes a systematic deviation handling protocol to document scope additions, technical changes, or requirement shifts directly in the project's documentation.

Question 3

How does this skill handle git commits?

Accepted Answer

It enforces a standardized format including type, scope, and subject, while using git notes to attach rich metadata and implementation decisions to your version history.

Question 4

What are phase checkpoints?

Accepted Answer

Checkpoints are verified milestones at the end of a project phase that require full test suite passes, 80% coverage targets, and explicit user approval before proceeding.

Question 5

Can I use this for projects with existing tests?

Accepted Answer

Yes, the skill includes specific protocols for extending existing test suites, ensuring regressions are prevented, and safely migrating tests during refactoring.

Conductor TDD Workflow

主要功能

使用场景

Conductor TDD Workflow

主要功能

使用场景