tdd-cycle

What problem does it solve? Teams practicing TDD often run Red-Green-Refactor cycles without systematic coverage, skipping edge cases and error paths, refactoring unsafely, or losing track of which behaviors remain untested. This Skill adds t-wada style discipline on top of the standard TDD cycle so coverage is driven by an explicit test list tied to a T-ID ledger. ## Core Features & Use Cases - Test-list-first planning: Enumerate normal, boundary, and error cases as a checklist before writing any code, with completeness checks against equivalence partitioning, boundary values, and state transitions. - Safe Refactor phase rules: Keep tests green while restructuring code one small step at a time, applying the Rule of Three for deduplication and never changing tests and production code simultaneously. - T-ID ledger integration: Map each Red-Green-Refactor cycle to exactly one ledger item, verify the failure reason matches the item's intent, and close items only when generalized implementation passes. - Use Case: When implementing a new uint parser in TypeScript with vitest, write the test list covering zero, leading zeros, empty input, negative signs, and overflow first, then drive each item through one TDD cycle until the list is empty. ## Quick Start Ask the AI to apply the tdd-cycle skill to plan a test list and drive Red-Green-Refactor cycles for the new feature you are about to implement.