joycraft-implement

Automating the TDD workflow involves parsing spec paths, writing failing tests, and guiding code changes until all tests pass. This enforces red-green-refactor discipline by validating spec metadata and acceptance criteria.

Yes, you can coordinate multiple specs in a single TDD session. The process parses each spec path, enforces test-first discipline across all provided files, and validates progress against individual acceptance criteria and test plans.

To start test-driven development for atomic specs, you need a valid spec path input containing defined Acceptance Criteria, a Test Plan, and Constraints. The workflow validates this metadata before initiating the red-green-refactor cycle.

Yes, the TDD cycle validates progress against spec acceptance criteria. It parses the metadata, writes failing tests first, verifies the failures, and then guides code implementation until all tests reach green status.

The best way to enforce red-green-refactor discipline is to automate the end-to-end workflow: parse specs, write failing tests, verify the failures, and guide code changes until all tests pass and acceptance criteria are met.

TDD spec execution requires validating spec metadata and constraints to ensure the generated tests align with the Acceptance Criteria and Test Plan. This validation prevents implementation drift and reports accurate progress status.