Agent
A test-building step that turns approved Gherkin scenarios into feature files, runners, and layered acceptance-test code. Acceptance tests check complete behaviour from an outside user's viewpoint, while the layers separate steps, protocol handling, and the system under test.
Agent
A code-cleanup step based on the Composed Method approach, which arranges a method into clear, smaller parts. It applies a sequence of local edits such as adding guard clauses, reorganising code, naming values, splitting loops, and trimming excess code.
Agent
A TDD planning step that drafts domain rules and user stories in a template. Domain rules describe business behaviour, while a user story describes a user's goal; the step also checks that the stories meet the INVEST criteria for useful requirements.
Agent
A TDD planning step that turns domain rules and user stories into key Gherkin examples. Gherkin is a readable format for describing software behaviour, and the step checks limits involving values, sizes, states, time, and totals.
Agent
A TDD agent handles the Green phase by adding the smallest implementation that makes the current test pass. TDD, or test-driven development, is a write-test, make-it-pass, then improve cycle.
Agent
A read-only TDD plan critic tries to break a test plan by looking for missing source-of-truth decisions, contradictions, duplicate coverage, and missing boundaries. TDD means test-driven development, where tests guide implementation.
Agent
A TDD agent handles the Red phase by writing only a test that fails. TDD, or test-driven development, uses a cycle of writing a failing test, making it pass, and then improving the code.
Agent
A TDD step that builds the thinnest working slice through a real HTTP request, application, and database. TDD, or test-driven development, is a way of building software from expected behaviour and tests; this step also settles how database loading and transactions cross application boundaries.
Agent
A TDD test-list planner drafts unit tests for detailed branches and internal interactions that are not covered by Gherkin scenarios. TDD, or test-driven development, means writing tests before the implementation.