Enforce test-driven development workflow — scaffold interfaces, generate tests FIRST, then implement minimal code to pass
From superpowers-eccnpx claudepluginhub aman-2709/superpowers-ecc --plugin superpowers-ecc/tddLegacy shim invoking tdd-workflow skill for strict RED-GREEN-REFACTOR TDD: failing tests first, minimal passing code, then refactor with test evidence.
/tddEnforces TDD workflow on a given feature: scaffolds interfaces, generates failing tests first, implements minimal passing code, refactors, and verifies 80%+ coverage.
/tddStarts TDD workflow: ensures main branch, creates feature branch, follows Red-Green-Refactor cycle, keeps notes, commits changes, pushes to GitHub, and creates PR.
/tddStarts TDD workflow: ensures main branch, creates feature branch, follows Red-Green-Refactor cycle, keeps notes, commits changes, pushes to GitHub, and creates PR.
/tddGuides TDD cycle for a feature: Red phase writes failing test, Green adds minimal passing code, Refactor cleans up, then repeats for next behavior.
This command invokes the superpowers-ecc:test-driven-development skill to enforce test-driven development methodology.
Use /tdd when:
RED -> GREEN -> REFACTOR -> REPEAT
RED: Write a failing test
GREEN: Write minimal code to pass
REFACTOR: Improve code, keep tests passing
REPEAT: Next feature/scenario
DO:
DON'T:
Unit Tests (Function-level):
Integration Tests (Component-level):
/plan first to understand what to build/tdd to implement with tests/build-fix if build errors occur/code-review to review implementation/test-coverage to verify coverage