Testing Tdd

---
name: testing-tdd
description: "Compatibility route to the author's complete Superpowers test-driven-development skill for behavior changes and regression coverage."
---

# Test-Driven Development Route

Provider: `superpowers.test-driven-development` from the reviewed upstream
catalog. This compatibility name selects the author skill; it supplies no
replacement testing procedure.

Resolve the provider with `be skills route superpowers.test-driven-development --json`.
Reuse a compatible exposed native provider, or install the missing reviewed
dependency through the selected Bible profile. Files alone do not prove host
exposure. Read the author's complete `SKILL.md` and required references using
the actual host invocation before continuing.

Apply personal rules from the global prompt and repository instructions as a
separate policy layer. Keep the author tree unchanged. When the user's scope or
an explicit repository rule changes the required procedure, state that policy
difference. Report missing tools or pending exposure instead of using a local
summary.

For a meaningful invariant, roundtrip, idempotence or generated-input test,
select the complete original `trailofbits.property-based-testing` instead.
Resolve its reviewed provider and read the task-specific references. Preserve
the target project's dependency policy; installing a skill does not install
a PBT library or authorize an unrelated production refactor. Choose example
tests when no useful property fits. Do not load both testing authors by default.

To assess whether tests detect a selected defect, use the owner's opt-in
[mutation check](../../docs/targeted-mutation-testing.md) at validation.
This optional check supplements the author's testing procedure.