Enforce a red-green-refactor TDD loop with failing tests before production code changes.
npx skills add https://github.com/testdouble/han --skill tdd-testdouble
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/testdouble/han/tree/main/han-coding/skills/tdd Command: npx skills add https://github.com/testdouble/han --skill tdd-testdouble
This TDD skill enforces a disciplined red-green-refactor loop, ensuring changes happen only after a failing test is observed and guiding production code to pass a single test at a time.
Begin by listing the behaviors you want to validate, then convert one into a failing test and implement the minimal production code to make it pass.
High-intent search queries and answers about installing and using this skill.
A strict red-green-refactor loop enforces an observed-failure gate, requiring a failing test before any production code changes. You write a failing test first, implement minimal code to pass it, then refactor while keeping tests green.
The observed-failure gate in TDD ensures no production code changes happen until a failing test is actually observed. It prevents writing speculative code by guaranteeing every line of production code is driven by a validated test failure.
You manage acceptance and unit behavior cycles in test-driven development by using an outer and inner loop approach. The outer loop drives end-to-end acceptance tests while the inner loop applies the red-green-refactor cycle to individual unit behaviors.
No, this TDD cycle manages one behavior per loop iteration. Focusing on a single behavior ensures minimal production code implementation and maintains traceable alignment between the failing test and the specific feature being validated.
The best way to start test-driven development for a new feature is listing the behaviors you want to validate. You then convert one behavior into a failing test and implement the minimal production code required to make it pass.
You should avoid strict test-driven development when doing exploratory prototyping or working in environments where formal test coverage is not required. It is designed for projects needing formal test-driven development and adherence to canonical TDD processes.
daikichiba9511Guide development through the RED-GREEN-REFACTOR cycle for TDD workflows.
RawToastWrite failing tests before implementing code using the red-green-refactor cycle.
pluginagentmarketplaceRun Python-based prompt-injection and adversarial security tests in CI/CD pipelines.
scute-shGuide implementation from acceptance tests inward using Given/When/Then scenarios.
