oag-tdd-standards

To enforce the red-green-refactor cycle in test-driven development, define strict standards for each phase: write a failing test, implement minimal code to pass, then refactor. This Skill codifies those steps to ensure clean, testable code.

Breaking down software development tasks for effective TDD involves sizing iterations into manageable slices. This Skill provides specific criteria for iteration sizing to maintain development discipline and prevent scope creep.

Choosing the right test doubles in TDD depends on the specific testing scenario and behavior being validated. This Skill offers guidance on selecting appropriate test double types to test behavior rather than code shape.

Common TDD anti-patterns to avoid include premature abstractions and allowing scope creep to disrupt the test cycle. This Skill lists specific mistakes to prevent, ensuring tests shape design discipline rather than hinder it.

A TDD cycle is complete when code passes established quality gates and an exit test. This Skill helps determine cycle completion by ensuring only high-quality, fully tested code is considered done.