Enforce a failing-first test-driven workflow for code changes.
npx skills add https://github.com/zeikar/hyperclaude --skill hyper-tdd
Please help me install this Agent Skill. Skill: hyper-tdd Source: https://github.com/zeikar/hyperclaude/tree/main/skills/hyper-tdd Command: npx skills add https://github.com/zeikar/hyperclaude --skill hyper-tdd
hyper-tdd helps you prevent broken behavior from slipping into production by forcing a failing test before you write the production code that will satisfy it.
Use case: You’re about to change business logic (or fix a bug) and want confidence that the new behavior is real, not accidental—start from a test that demonstrates the missing behavior.
When you’re about to change behavior-bearing code, invoke the skill as /hyperclaude:hyper-tdd and follow the failing-first loop until the test passes and the behavior is covered.
High-intent search queries and answers about installing and using this skill.
Use a failing-first test-driven workflow by writing a behavior-named failing test, verifying the failure source is correct, implementing the minimum code to pass, and iterating with passing test confirmation to reduce the risk of incorrect behavior.
Failing-first TDD discipline requires writing a behavior-focused test first, confirming it fails for the right reason, and implementing only what the current failing test requires. This prevents scope creep by avoiding unnecessary work during code changes.
To write a behavior-named failing test before modifying business logic, define the expected behavior in a test, run it to verify the failure source is correct, then implement the minimum production code required to make that specific test pass.
You can refactor code while maintaining commit discipline by making one behavior-focused change per commit, then refactoring only when the tests still pass. This ensures your behavior-driven tests confirm correctness throughout the process.
Test-driven development works for both writing new functions and modifying business logic, as well as bug fixes where you want to confirm the failure reason and implementation correctness through a failing-first workflow.
IntelliTectWrite failing xUnit tests that reproduce bug behavior in C# projects.
tim-hubEnforce test-first development with failing tests before implementation.
bobmatnycEnforce test-first development with RED/GREEN/REFACTOR workflows.
takusaotomeGuide Test-Driven Development through red-green-refactor cycles with failing tests and minimal code.
