tddlisted

# tdd — Internal TDD Enforcement This skill is an internal Silver Bullet policy layer. It is not picker-visible and is only used by SB workflows. Canonical contract: `superpowers:test-driven-development` Before any implementation work, invoke `superpowers:test-driven-development` via the Skill tool and follow its red-green-refactor cycle exactly. This wrapper is the SB-approved Superpowers delegation point for TDD; callers enter through the SB `tdd` wrapper, not the Superpowers skill directly. Then apply the Silver Bullet-specific rules below. Activation point: SB workflows invoke this hidden gate immediately before `gsd-execute-phase --tdd` or an equivalent execution boundary for implementation work. ## The Iron Law ``` NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST ``` Violating this rule in letter violates it in spirit. No exceptions. ## Red-Green-Refactor ### RED — Write Failing Test Write one minimal test for the behavior you're about to implement. Run it. Confirm it FAILS. Confirm it fails for the RIGHT reason — "feature missing" not "syntax error". Commit: `[RED] test(<scope>): <behavior description> — N stubs` DCO: `Signed-off-by: <name> <email>` If the test passes immediately: you're testing existing behavior. The test is wrong. Fix it. ### GREEN — Write Minimal Code Write the simplest code that makes the test pass. Nothing more. No extra features. No refactoring. Minimum to go green. Run ALL tests. Confirm they all pass. Commit: `[GREEN] feat(<scope>): <de