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