bk-tdd

To start test-driven development (TDD), you first write a failing test that captures a specific acceptance criterion, then implement the minimal code to pass it, and finally refactor for quality. This structured workflow ensures robust software implementation.

The Red Green Refactor cycle is a test-driven development workflow where you write a failing test (Red), implement the minimum code required to pass the test (Green), and then refactor the code for quality without changing its behavior.

You can link acceptance criteria to your testing workflow by using a provided plan path. The TDD process directly maps your tests to the requirements defined in the plan, ensuring that every piece of implemented code fulfills a specific acceptance criterion.

Yes, the TDD workflow supports external dependency mocking and property-based testing for robust validation. This allows you to isolate components and thoroughly test code behavior against a wide range of inputs during implementation.

You should use test-driven development when you need to ensure robust, reliable code by strictly adhering to predefined acceptance criteria. It is particularly effective for guiding software implementation through a structured Red-Green-Refactor cycle before writing functional code.

Yes, the bk-tdd skill operates with no dependencies. It facilitates the test-driven development workflow entirely through its internal references and structured process, guiding you from writing failing tests to final code refactoring.