What problem does it solve?
During test-driven development, once failing tests exist, someone must write production code that satisfies them without over-engineering or breaking existing behavior. This Skill automates the green phase of red-green-refactor by interpreting failing test output and producing focused, convention-consistent implementation code.
Core Features & Use Cases
- Test-driven implementation: Reads failing test output and test files to derive exact signatures, types, and behaviors the production code must provide.
- Convention discovery: Inspects build files and existing source code to match the codebase's module layout, naming, error handling, and coding style before writing anything.
- Compile and parse verification: Runs language-appropriate checks (cargo check, tsc --noEmit, py_compile, go build) and fixes errors before reporting completion.
- Use Case: Given a Rust test failure reporting that
validate_token is missing from the auth module, the Skill studies sibling functions, adds the function with the expected signature and error types, and verifies the crate compiles cleanly.
Quick Start
Given these failing test results and test file paths, write the minimal production code needed to make all the tests pass and verify it compiles.