workflow-patterns

You can structure a TDD workflow by applying an 11-step lifecycle that enforces the red-green-refactor cycle, establishes phase checkpoints, and generates formal commit messages to track task implementation progress.

You can enforce TDD checkpoints by applying structured workflow patterns that define phase checkpoints and quality assurance gates across tracks, ensuring disciplined progression through the red-green-refactor cycle.

You start a plan-driven TDD task from a plan.md file by instructing the system to apply Conductor's TDD workflow to the next task and begin at Step 1 of the 11-step lifecycle to guide execution from plan intake to final acceptance.

Yes, the TDD workflow pattern requires clear frontmatter metadata in SKILL.md, concrete steps for each phase, and documentation of verification and quality gates to ensure consistent task execution and acceptance.

Conductor handles verification and quality gates in a TDD cycle by enforcing phase checkpoints throughout the 11-step lifecycle, requiring documentation of verification standards and quality gates to achieve final task acceptance.