dev-tddlisted

# dev-tdd ## Overview No production code without a failing test first. This is a discipline overlay, not a workflow step. It fires during ANY coding task - whether you're working from a plan, fixing a bug, adding a feature, or refactoring. There is no entry gate and no exit gate. If you're writing code, TDD rules are active. The cycle is simple. The discipline is what matters. ## Announcement When this skill is active, announce: > "I'm using enggenie:dev-tdd to enforce test-driven development." --- ## Hard Rule: No Production Code Without a Failing Test First If you catch yourself writing production code before a test: **stop**. Delete it. Write the test first. No exceptions. No "just this once." No "I'll circle back." The test comes first or the code doesn't get written. --- ## Violating the Letter of TDD Is Violating the Spirit There is no distinction between the letter and the spirit of TDD. The spirit IS the letter. Writing a test that you know will pass is not TDD. Writing two tests before implementing is not TDD. Writing production code and then backfilling a test is not TDD. These aren't "close enough." They're a different practice entirely. The value of TDD comes from the discipline of the cycle. Skip a step and you lose the feedback loop that makes it work. --- ## The Cycle: RED -> GREEN -> REFACTOR Every piece of new behavior follows this cycle. Every time. No shortcuts. ### RED - Write a Failing Test 1. Write ONE minimal test that describes the