test-driven-development
Follow TalkPipe TDD workflow when making code changes. Use when implementing features, fixing bugs, or refactoring. Enforces write-fail-fix-pass order and test placement conventions.
85
87%
Does it follow best practices?
Impact
67%
0.83xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
20%Add Batch Processing to the Data Pipeline
TDD new feature strict order
Test written first
100%
100%
Fail verified before fix
100%
100%
Pass verified after fix
100%
100%
Uses .venv environment
0%
100%
Coverage command used
100%
100%
Tests in tests/ directory
100%
100%
Existing test file augmented
100%
100%
Specific test targeted first
0%
100%
batch_process implemented
100%
100%
Test is concise
100%
100%
51%
-17%Fix the Message Truncation Bug
TDD bug fix with existing test augmentation
Test written before fix
0%
0%
Fail step verified
0%
0%
Pass step verified
100%
50%
Uses .venv environment
100%
0%
Existing test file augmented
100%
100%
Tests in tests/ directory
100%
100%
Boundary condition tested
100%
100%
Bug correctly fixed
100%
100%
Coverage command used
0%
0%
Concise test
100%
100%
52%
-41%Update the Project README and Version Bump Script
TDD exemption notification and confirmation
README change acknowledged as untestable
100%
100%
Script identified as untestable
100%
0%
Reason provided for README
100%
100%
Reason provided for script
100%
0%
Confirmation sought
50%
0%
No spurious tests created
100%
0%
README change made
100%
100%
Script created
100%
100%
No silent skip
100%
100%
- Repository
- sandialabs/talkpipe
- Commit
0cf1686
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.