Executing TDD Cycles

Overview

Transform a cycle task list into implemented code via strict red/green/refactor discipline. Parse tasks from tasks.md, write failing tests first, implement code to pass them, refactor, mark tasks complete, and produce a structured cycle-report.md. This skill governs both normal cycle execution and retry/fix modes.

Violating the letter of the rules is violating the spirit of the rules.

TDD discipline exists to catch failures before they compound. Every shortcut in this process is a regression waiting to happen.

When to Use

• Executing a cycle's task list from tasks.md
• Retry after checkpoint failure (targeted rework)
• Fix mode after final-validation failure (unconstrained by cycle boundaries)
• Any task with [EXTEND] or [MODIFY] markers (invoke brownfield-integration skill alongside)
• Writing cycle-report.md after cycle completion

When NOT to Use