dev-tdd
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
More from badrusiddique/enggenie-skill
dev-implement
Use when executing an implementation plan task-by-task - dispatches subagents for implementation, manages git worktrees, handles phased multi-service deployment
10review-design
Use when reviewing frontend implementation against design specs - design system compliance, responsive behavior, accessibility audit
10architect-plan
Use when creating implementation plans from specs or requirements - phased task breakdown with deployment readiness gates before any coding begins
9review-code
Use when requesting or receiving code review - dispatches reviewer subagent or processes human PR feedback with technical evaluation
9memory-recall
Use when asking about previous sessions - cross-session context search via claude-mem with token-efficient 3-layer retrieval
9architect-design
Use when brainstorming new features, making architectural decisions, evaluating technical tradeoffs, or documenting decisions as ADRs - before any implementation planning or coding begins
9