Write the failing test first, then the minimum code to pass it, before implementing any feature or fix.
Visit skill This is mine — claim it
Source: https://github.com/obra/superpowers-skills/tree/main/skills/testing/test-driven-development
Listing URL: https://wingmanprotocol.com/skills/test-driven-development/
Show your listing is live — the card backlinks here and picks up the verified badge automatically once you claim it.
<iframe src="https://wingmanprotocol.com/embed/card/test-driven-development" width="340" height="170" style="border:0;border-radius:10px" loading="lazy" title="Test-Driven Development (TDD) — live on WingMan Protocol"></iframe>
Or the one-line script:
<script src="https://wingmanprotocol.com/embed/card.js" data-slug="test-driven-development" async></script>
Or a README badge:
[](https://wingmanprotocol.com/directory/test-driven-development?utm_source=badge)
Replaces flaky arbitrary sleep/timeout calls in async tests with polling for the actual condition.
Applies systematic root-cause debugging instead of guess-and-check when a test, build, or behavior breaks.
Captures and analyzes Windows usermode/kernel debug output from the command line via Sysinternals DebugView.
Adds validation at every layer data flows through so a whole class of downstream bugs becomes structurally impossible.
Runs mutation testing to measure whether a test suite actually catches introduced bugs, not just achieves coverage.
Writes property-based tests (Hypothesis-style) that check invariants across generated inputs instead of fixed examples.