test-driven-development
A red-green-refactor workflow for making an agent prove behavior before changing code.
30-Second Summary
This skill makes tests the starting point rather than an afterthought.
It asks the agent to write a failing test, make it pass with minimal code, and refactor only while tests stay green.
Use it for behavior changes or bug fixes where proof matters more than a quick patch.
1-Minute Read
What it is
A SKILL.md workflow for red-green-refactor development, bug reproduction tests, and test pyramid judgment. It gives an agent a concrete sequence for proving behavior before claiming a change works.
When to use it
Use it when modifying logic, fixing a bug, adding edge cases, or changing behavior that could regress later. It pairs well with small, focused tests and existing repo test commands.
How to test it first
Ask the agent to write one failing test for a small bug or new behavior before implementing anything. Confirm that the test fails for the right reason, then let it make the smallest passing change.
Watch out
Do not force it onto static content or pure config changes that have no behavior to test. Also avoid mock-heavy tests that only prove implementation details.