test-driven-development
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Violating the letter of the rules is violating the spirit of the rules.
When to Use
Always:
- New features
- Bug fixes
- Refactoring
- Behavior changes
Exceptions (ask your human partner):
More from camacho/ai-skills
bail
Reflects, updates GitHub Issue, closes PR if open, cleans up worktree/branch.
566plan-review
Auto-assembles review panel using deterministic rules, dispatches agents against plan file, collects verdicts.
547archive
Fills Outcomes & Learnings in a plan file and renames it to .done.md.
542orient
Fetches issue context, auto-detects task type, maps to branch prefix, presents brief.
537capture
Creates a draft GitHub Issue with triage label from natural language description.
535reflect
Use after merging a branch or completing a task to consolidate learnings into memory layers, close out issues, and verify the phase gate.
500