feature-planning-tdd

To plan a feature using test-driven development, you define acceptance criteria and generate a list of failing tests before writing any code. This enforces a Red-Green-Refactor workflow to guide implementation.

The Red-Green-Refactor cycle in TDD involves writing failing tests first, creating minimal implementation steps to pass those tests, and then cleaning up the code. This ensures structured feature planning.

You assess documentation impact before implementing an API endpoint by generating a TDD plan that identifies necessary updates to documentation and diagrams alongside test cases and implementation steps.

Yes, you can use TDD planning for bug fixes and milestone tasks. It generates a comprehensive plan with acceptance criteria, failing tests, minimal code steps, and documentation updates before development begins.

You write failing tests before implementation code by pre-computing test cases during the RED phase of the TDD workflow. The Skill generates these tests based on defined acceptance criteria.

A limitation of enforcing a TDD workflow for feature planning is that it requires defining acceptance criteria and failing tests upfront, which may not suit rapid prototyping or highly exploratory development tasks.