Files
gh-macroman5-claude-code-wo…/.claude/skills/test-driven-development/SKILL.md
2025-11-30 08:38:46 +08:00

952 B
Raw Blame History

name, description, version, tags, triggers
name description version tags triggers
test-driven-development Enforce RED→GREEN→REFACTOR micro-cycles and keep diffs minimal 0.1.0
testing
quality
tdd
tests first
failing test

Test-Driven Development

Purpose

Bias implementation to tests-first and small, verifiable changes.

Behavior

  1. RED: scaffold 13 failing tests targeting the smallest slice.
  2. GREEN: implement the minimum code to pass.
  3. REFACTOR: improve names/structure with tests green.
  4. Repeat in tiny increments until task acceptance criteria are met.

Guardrails

  • Block large edits unless a failing test exists.
  • Prefer small diffs spanning ≤3 files.
  • Keep test names explicit and deterministic.

Output Style

  • bullet-points for steps; markdown-focused for code blocks.

Integration

  • /lazy task-exec implementation phase; Coder/Tester agents.

Example Prompt

Apply TDD to implement input validation for prices.