builder

To turn failing tests into production-ready code, use this Skill to read failing test assertions and implement the smallest correct changes within declared file ownership boundaries. It enforces styleguide compliance and performs a self-audit before handing off.

The best way to implement code changes without modifying tests is to apply edits strictly within /src and /lib directories. This Skill enforces file ownership rules, ensuring tests define expected behavior while only production code changes.

Test-driven development with strict file ownership works by reading failing test signals to implement required changes only in allowed /src and /lib files. The Skill prevents test modifications, ensuring behavior-driven tests dictate production code implementation.

Yes, you can use this for behavior-driven tests on Cloudflare Workers. The Skill processes failing test assertions to generate maintainable production code, applying structured logging and safe error handling suitable for Cloudflare Workers environments.

Your code fails the styleguide compliance check during handoff if it lacks structured logging, safe error handling, or contains silent failures. The Skill performs a checklist-based self-audit to enforce these rules before generating a commit message draft.

Limitations of automated test-to-code implementation include strict file ownership boundaries, preventing any modifications to test files, and requiring repository documentation and sprint plan files to be read before implementing allowed edits in /src and /lib.