implement_skill

Overview

This skill makes failing tests pass by writing the minimal code changes required after tests are generated. It runs the test suite iteratively, applies the smallest possible fixes, and stops once all tests pass. Use it as the “Green” step in a test-driven workflow to convert failing tests into a correct implementation.

How this skill works

The implementer inspects the most recent failing tests produced by /write-tests and derives the exact behavior required. It applies the minimal code changes to satisfy assertions, runs tests after each change, and repeats until every failing test is green. It never adds features beyond what tests require and avoids refactoring.

When to use it

• After running /write-tests that produced failing tests
• When you need focused, minimal implementation to satisfy tests
• When you want to convert test specifications into executable code quickly
• When refactoring is not desired and behavior must match tests exactly

Best practices

• Read failing tests first and identify exact expectations before coding
• Make the smallest change that makes a test pass; avoid broad edits
• Run the test suite frequently to confirm progress and avoid regressions
• Do not add new tests or refactor existing code during this step
• Keep changes focused on making assertions pass; leave cleanup for a later pass

Example use cases

• Implement missing methods referenced by newly generated tests (e.g., client.reset or client.step)
• Add minimal input validation required by tests that exercise edge cases
• Fix small integration mismatches between code and test expectations
• Complete TODOs that tests target without expanding API surface