Master Test-Driven Development with deterministic red-green-refactor workflows, test-first feature delivery, bug reproduction through failing tests, behavior-focused assertions, and refactoring safety; use when implementing new functions, changing APIs, fixing regressions, or restructuring code under test.
Does it follow best practices?
Evaluation — 86%
↑ 1.05xAgent success when using this tile
Validation for skill structure
RetailPlus has outgrown their simple order system and needs a sophisticated multi-step order processing workflow. Orders now require inventory validation, payment processing, fraud detection, shipping calculation, and warehouse notification. Each step can fail independently and requires different retry and rollback strategies.
The business team has defined a complex workflow: orders start in "pending" status, move to "validated" after inventory and fraud checks, then "paid" after payment processing, then "fulfilled" after shipping arrangements, and finally "completed" when shipped. Failed steps should move orders to appropriate error states with clear failure reasons.
The existing system has grown organically with several issues: tests that combine multiple workflow steps making failures hard to diagnose, shared test data that causes tests to affect each other, and complex test scenarios that are difficult to understand and maintain.
Implement a comprehensive order processing system with:
System should handle:
Required files:
Install with Tessl CLI
npx tessl i pantheon-ai/test-driven-development@0.2.4evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
references