crush/skills/ecc-tdd/SKILL.md
# ECC TDD Workflow Default cycle: 1) Write/extend tests (failing) 2) Implement minimal code to pass 3) Refactor (only after green) 4) Re-run tests and lint Checklist: - Tests cover: happy path, edge cases, error cases - Deterministic: no time/network flakes unless mocked - Clear assertions; avoid over-mocking If tests are expensive: - Add a fast unit layer first - Add integration/E2E only where needed
npx skillsauth add e2ec-it/pub-xifan-crush-best-practices crush/skills/ecc-tddInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Default cycle:
Checklist:
If tests are expensive:
content-media
SUPERPOWERS-style implementation planning: turn an approved design into 2–5 minute tasks with exact file paths, commands, verifications, and frequent commits.
development
SUPERPOWERS TDD enforcement: NO production code without a failing test first. Delete code written before tests.
development
Execute plan per task with role separation and review loops (spec then quality). In Crush, simulate subagents via role prompts / new sessions.
development
Request review between tasks and before merge. Use git SHAs to scope changes and produce actionable findings.