tdd

To enforce test-first development, this Skill coordinates the RED/GREEN/REFACTOR cycle within the Anvil dev-agent workflow. It drives feature development by requiring explicit, reproducible steps: writing a failing test, implementing minimal code to pass, and refactoring while preserving behavior.

The RED/GREEN/REFACTOR cycle is a test-first development process where RED writes a failing test specifying desired behavior, GREEN implements minimal production code to pass, and REFACTOR cleans up code while preserving test results. This cycle drives disciplined feature development.

Yes, this TDD process works across any programming language and project setup. It provides a language-agnostic blueprint that coordinates test-first cycles within the Anvil dev-agent workflow without requiring specific frameworks or dependencies.

You integrate the test-driven development cycle into ticket workflows by triggering the RED/GREEN/REFACTOR steps for each feature. This yields two commits per feature—one for tests and one for implementation—maintaining test coverage and ensuring commit hygiene.

No, this test-first approach requires no specific dependencies or components. It functions as a discipline reference and blueprint that aligns with metadata-driven discovery to enforce the TDD process across any existing project environment.

You should not use a strict test-driven development cycle when a feature requires exploratory prototyping without defined behavior specifications. The cycle mandates explicit, reproducible steps starting with a failing test, which suits structured feature development over open-ended experimentation.