test-driven-development-quick

What problem does it solve? Writing code before tests leads to unverified behavior, speculative implementation, and regressions that surface late. This Skill enforces a compact red-green-refactor discipline so every production change is preceded by a failing test with real, observed output. ## Core Features & Use Cases - Red-Green-Refactor Loop: Write one failing test, implement the minimal code to pass it, then refactor under green with the full suite run after each step. - Bug Reproduction Workflow: Reproduce bugs with a failing test at the real failure path before fixing, keeping the test as a permanent regression guard. - Escalation Guidance: Know when to step out of the loop (integration work, pure renames, no independent source of truth) and when to escalate to the full test-driven-development skill. - Use Case: You need to add a small validation rule to an existing module. State the behavior and seam, write one failing test against the project's existing runner, implement the minimal code, and commit at green. ## Quick Start Ask the assistant to build a specific behavior or fix a bug using test-driven development with the test runner already used in your project.