tdd-enforcement

This skill enforces genuine test-first development by requiring you to define expected behavior and write failing tests before implementation, ensuring edge cases are captured early and tests guide architecture.

The best way to guide architecture during a refactor is to maintain readable, deterministic tests that apply the FCIS pattern, separating decisions from effects to improve testability and guard against regressions.

You systematically identify edge cases by defining the desired behavior upfront and writing failing tests early in development, which catches critical failure modes before implementation begins.

Yes, you can use this TDD workflow across feature development, bug fixes, and refactors. It applies the define behavior, write failing tests, implement, and refactor cycle to ensure stable, readable tests.

Yes, this test-driven development skill operates with no external dependencies, focusing on the core TDD process of defining behavior, writing failing tests, implementing minimal code, and refactoring.

You should avoid a strict test-first approach when you cannot clearly define the desired behavior upfront, as the process relies on writing failing tests to drive implementation and guide architectural decisions.