Define behavior before coding and validate changes through a red-green-refactor workflow.
npx skills add https://github.com/hylarucoder/hai-stack --skill hai-tdd
Please help me install this Agent Skill. Skill: hai-tdd Source: https://github.com/hylarucoder/hai-stack/tree/main/skills/hai-tdd Command: npx skills add https://github.com/hylarucoder/hai-stack --skill hai-tdd
This Skill prevents unreliable implementations by making behavior explicit before coding and ensuring changes are validated through evidence-based testing instead of assumptions.
Use the hai-tdd skill to implement this feature with a red-green-refactor cycle and provide the completed test evidence report.
High-intent search queries and answers about installing and using this skill.
The red-green-refactor workflow in test-driven development requires writing a failing test first, implementing minimal production code to pass it, and then safely refactoring while validating behavior changes through evidence-based reporting.
To implement a feature using test-first development, define the expected behavior upfront, prove the test constraint by showing failing-test evidence, write minimal passing code, and validate refactoring decisions through structured test command reporting.
Yes, test-driven development applies to bug fixes and regression prevention by defining expected behavior before patching code, proving the test constraint fails on the bug, and delivering a verified implementation through validated red-green-refactor cycles.
Yes, test-driven development requires failing-test evidence before writing production code to ensure the test constraint is proven, followed by minimal implementations and refactor validation to guarantee reliable behavior verification.
The best way to verify behavior changes during unit testing refactoring is to capture refactor decisions and validate them against test commands and outcomes, ensuring the red-green-refactor workflow maintains reliable behavior without assumptions.
Test-first development may not suit software development scenarios where rapid prototyping without behavior verification is prioritized, as it mandates failing-test evidence, minimal implementations, and structured reporting of test outcomes before delivering features.
jmstar85Enforce red-green-refactor cycles by writing failing tests before implementation.
AxelooooRequire failing tests before production implementation across backend, frontend, and smart-contract workflows.
Marshall-HallenbeckDiagnose and repair failing test suites across multiple language ecosystems.
wzserImplement test-driven development practices with unit and integration tests.
