test-driven-development

Installation
SKILL.md

Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more.

Test-Driven Development

Overview

Write a failing test first, then implement the minimum code to pass, then refactor. Tests are proof that the system behaves as intended. This is the canonical Build-phase testing skill.

When to Use

  • Implementing new logic or features
  • Fixing bugs (write a failing test that reproduces the bug)
  • Refactoring existing behavior
  • Changing any code that has correctness requirements

Test Pyramid

Installs
4
GitHub Stars
8
First Seen
May 7, 2026
test-driven-development — v1truv1us/ai-eng-system